Hi Wouter,
I had been looking at your changes, and there is one thing in the new version that does not convince me. It is about the needed of model attributes on Transitions and model them again in the controller operation. This is also a problem, because as you told to Stefan last 28.9, one of the limitations of AndroMda for the UML is that it must have triggers on transitions and parameters on triggers.
My idea is that if an operation can be deferred only in one action State, you could change the method to take the parameters from the operation and not from the transition, in this way, also the tagged values should be specified on the parameters of the operation.
For the collections cases, if the operation return a collection and it is invoqued in an operation with an outgoing transition, then this will be mapped as a display tag....
I don't know if it is possible.....
Carlos
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
