okay I see now what you mean, you are right, this would definitely benefit from a workflow cartridge for the Spring framework (or possibly integrated into the already existing Spring cartridge)
like Chad said, we don't have that, but as you're example clearly shows, it would be a really powerful feature: you model the workflow and the only thing left to implement are the generated method calls I think this is not too hard to do, especially if the modeling convention of the bpm4struts cartridge can be reused you know bpm4struts, right ? if you have the time could you briefly check whether or not the modeled process logic for bpm4struts is compatible with the kind of stuff you are thinking about for the Spring cartridge ? if so I might start working on it (since I need something similar at work :-) ) -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=946#946 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 Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
