hello bpm4struts users,
I just finished implementing an improvement that will allow you to more easily send parameters to another use-case, I have documented this here: http://docs.andromda.org/andromda-bpm4struts-cartridge/howto2.html#Sending_parameters_across_use-cases previously it was only possible to have *event parameters* survive the trip to the next use-case (only if the event would eventually target a final state), but now you can do the same with 'page-variables' (technically they are just variables since they aren't entering any page) by simply modeling them explicitely on the transition going into the final state you won't need to model them on the initial transition of the target use-case, this will be handled automatically by the cartridge now, this all works fine for me and for the projects and I am currently working on, but it can happen that some of you notice weird behaviour all of a sudden (I'm not excpecting it, but you never know) if you notice input fields keep getting populated out of nowhere, or all of a sudden pages appear in a different order then please let me know so I can fix it! I still expect the update to be backwards compatible -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1107#1107 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
