facebook

Struts config designer bugs [Closed]

  1. MyEclipse Archived
  2.  > 
  3. Bugs
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #215563 Reply

    kinjalsonpal
    Member

    Hi,

    I’m currently using MyEclipse with following details on a Win2K SP4 box

    Version: 3.8.1
    Build id: 200408201200-3.8.1

    and Eclipse with following details

    Version: 3.0.0
    Build id: 200406251208

    I’m having following difficulties/Wish-list with the Struts config editor
    1) When I fire print command, it always prints design rather than code, even when the code tab is open and visible. Am I missing something?
    2) The ForwardAction’s only work is to forward to another resource. It does not show connected to the specifed forward, rather it hangs loose.
    3) When I imported my project from 3.7.x (not sure about version no.) the designer simply went for a toss showing many unnessary boxes for all the forwards within each action-mapping. I had to manually delete all of them, while keeping my fingers crossed that it does not do anything silly.
    4) If the forwards are parameterised (mostly in case of forward to a DispatchAction), it does not recognise as a valid connectable node and it again hangs in air.
    5) There’s very little detailing in the Visual design. Maybe you people can have a look at Struts-studio for a whiff of inspiration.

    Please note that I’m not cribbing about what’s not there. I fully understand that the designer looks to be still in it’s infancy and it’s still better to show a design to the top guys, instead of showing a complicated code to them. In all senses, it’s still a great work.

    I also hope that I’ve posted this in correct forum.

    Thanks and regards,
    Kinjal

    #215578 Reply

    Riyad Kalla
    Member

    Moving to bugs

    #215585 Reply

    support-michael
    Keymaster

    2) The ForwardAction’s only work is to forward to another resource. It does not show connected to the specifed forward, rather it hangs loose.

    Can you describe a concrete example? For example, design model depcits Fwd1->myFoo.jsp as just Fwd1 node w/o connection to myFoo.jsp.

    3) When I imported my project from 3.7.x (not sure about version no.) the designer simply went for a toss showing many unnessary boxes for all the forwards within each action-mapping.

    Can you provide more info about the nodes you deleted? For example, did they only show up in the designer and not the outline or src views? Also were these global-forwards or action-specific local forwards that were depcited? There was a format change to the <config-file>.mex but it should have been backward comaptible with all but an early beta version of ME.

    4) If the forwards are parameterised (mostly in case of forward to a DispatchAction), it does not recognise as a valid connectable node and it again hangs in air.

    Could you share your struts-config.xml file with me to further understand the issues you observe. If yes, please send it to support@genuitec.com to the attention of Michael.

    #215659 Reply

    kinjalsonpal
    Member

    @support-michael wrote:

    Can you describe a concrete example? For example, design model depcits Fwd1->myFoo.jsp as just Fwd1 node w/o connection to myFoo.jsp.

    No. Actually, I’m referring to SomeForwardActionMapping -> SomeOtherActionMapping kind of forward.

    Can you provide more info about the nodes you deleted? For example, did they only show up in the designer and not the outline or src views?

    None of them were visible in any other view except the Designer View.

    Also were these global-forwards or action-specific local forwards that were depcited?

    I think all of them were rather action-mapping boxes. They were all colored as Others in the New designer.

    Could you share your struts-config.xml file with me to further understand the issues you observe. If yes, please send it to support@genuitec.com to the attention of Michael

    I’ll check with my boss in an informal way and see if I can pass it along. Btw, just to correct myself, I was earlier using 3.8 Beta-2.

    @kinjalsonpal wrote:

    4) If the forwards are parameterised (mostly in case of forward to a DispatchAction), it does not recognise as a valid connectable node and it again hangs in air.

    I’ll try to give an example. I have a Mapping for a MenuAction. This has forwards for various sections of the application, which are all mapped as heirs of DispatchAction. To simplify the jsp development, I put the forward in MenuAction as a url like this : “/xyz.do?method=abc”, where “/xyz” is an ActionMapping. If I remove the parameter from the Url, it properly connects the node for “/xyz”.

    Btw, I’m still wondering how do I print my struts-config.xml code within eclipse.

    Thanks and regards,
    Kinjal Sonpal

    #215673 Reply

    support-michael
    Keymaster

    Kinjal,

    I have a Mapping for a MenuAction. This has forwards for various sections of the application, which are all mapped as heirs of DispatchAction. To simplify the jsp development, I put the forward in MenuAction as a url like this : “/xyz.do?method=abc”, where “/xyz” is an ActionMapping. If I remove the parameter from the Url, it properly connects the node for “/xyz”.

    Thanks for providing this example. I have entered a problem report (PR) regarding how the proper interpretation of a forward URL to a dispatch-action.

    I’m referring to SomeForwardActionMapping -> SomeOtherActionMapping kind of forward.

    I’ll do more testing on this type of scenario.

    #216435 Reply

    Riyad Kalla
    Member

    Fixed in 3.8.2

Viewing 6 posts - 1 through 6 (of 6 total)
Reply To: Struts config designer bugs [Closed]

You must be logged in to post in the forum log in