hi Alain,
the parameters are indeed encapsulated using a form, which is a simple bean that provides getters and setters to the request parameters if you want to be able to access parameters in your application you will have to model an action state with a controller operation inside () any arguments modeled into this operation will represent the field of the form to which you have access, mind you, it is only possible to model arguments to which the form can have access (meaning the arguments must actually reach the action state with the operation inside) example: if you have a <<FrontEndView>> state with an outgoing transition on which you have the 'id' parameter, then you can model an action state which accepts this transition, and in this action state the operations will be able to see the 'id' field. Just make sure that not only the name but also the type of the parameters match. anyway, AndroMDA will tell you if you didn't properly do this. make sure you have read the bpm4struts howto, and check out the online-store sample, it's only using the bpm4struts cartridge to generate a deployable application good luck, feel free to ask more questions if you're not certain how to do something -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1794#1794 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
