[Dave S-B]

I quite often have struts forwards that look like this;

<forward
name=”drilldown”
path=”showSomeData.do?id={0}”
redirect=”true” />

…for example, in a form that contains a list of items, this forward would be fired on clicking a specific item (to go to it’s detail page) passing in the relevant id.

If the path doesn’t contain the parameter(s) then the visual designer shows a nice connection between one action and the next (great – how it should be). As soon as you put parameters in, the designer creates what looks like a HTML link named after the forward’s path (i.e. showSomeData.do?id={0}) and loses any connection to the destination Action.

I’m not sure if I should be reporting this as a bug, or if I’m just going about things in an odd way…

[Dave S-B]

OK – so it’s just odd! I’m using a UI framework called CommonControls which provids a Struts adapter and extensions to Action/ActionForm etc. They have some helper methods to construct ActionForwards to return from the execute function that take the Forward name and a list of parameters. It presumably replaces the placeholder in the path with the parameters you pass in and forwards on…
Not your problem (but it would be nice if parameters were ignored by the visual editor 🙂 )

[Author]

Posts