> BTW: Thinking about the user and the need for documentation, how about the > UML profile of bpm4struts? I think it would be a good idea to display it > as a UML model (one class per stereotype, one attribute per tagged value, > one dependency from each stereotype to the metaclass to which the > stereotype can be applied, you know what I mean). > >
good idea, I was wondering what would be a good way to document this in a way that is easy to understand. consider it done btw, I have already something like that in the bpm4struts user guide, but I'm afraid some people might think the page's too long to read if they want information quickly > And it would also be very good to display the PSM metamodel in UML, too: A > JSP page that puts values into a form and sends a request to an action > that calls the controller that invokes a service that returns a value that > is written into a form that is displayed on the next JSP page... you know > what I mean. :-) > > what would be the preferred way of modelling ? static or dynamic [s/D] ? Wouter. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Andromda-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-devel
