I guess for now the best thing to do is ignore the generated source :-)
as you will probably already know you might corrupt the generated sources doing so,sources such as struts-config.xml for example, this file contains all the process flow logic and will have a hole for every state that is not processed
but it is good you raise the issue, I will keep it in mind
Wouter.
Walter Mour�o wrote:
I didn't make myself clear... I'm talking about action states as just "UML model elements", without
screens or code generation. Suppose the developer wants to add an action
state just to make the model more clear, without generating code. I'm not
sure if it is needed, so don't waste your time with that. If I really
think it is needed I will ask.
Thank you.
Walter
[EMAIL PROTECTED] grava:
using 'ObjectFlowStates'
<quote>
/ 7. each time something in the business layer must change, create an object flow state
</quote>
/that should do the trick
Wouter.
Walter Mour�o wrote:
It is clear, my doubt is: how to model "non screen" action states ?
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Andromda-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-devel
