that should be pretty straightforward to do:
just model an event out of the page, model the parameter on this transition's trigger; make sure the transition leads into an action state which defers to a controller operation, this operation should take a parameter with the same name and type; model a second transition from that action state back into the page, again model a trigger on this transition and put the same parameter on there as before; also, model one or more tagged values on this second transition: @andromda.struts.action.success.message=My success message (for example) (this message will be i18n'ed, so you'll find it in )application-resources.properties To answer your second question: you could still reuse the same controller operation, but you could for example put the result in the session once you got the result the first time, after that don't go to the back end but just reuse it again; when you leave the use-case you simply remove it from the session -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2735#2735 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
