I don't know what you mean with master detail, but you will be able to model individual input elements with their validation attributes when the cartridge is released, this feature is new and is not supported by the (current and never officially released) bpm4struts CVS version
maybe you can explain in more details what you have in mind ?
thanks Wouter.
Walter Mour�o wrote:
Hi folks,
I was thinking about a UML way to represent the 'master detail' behavior inside a form, and started designing a association between a the form class ( <<FrontEndModel>> ) and a class representing the detail item. So I have:
FormClass --------- Grid -------- ItemClass
where Grid is an one to many association between the FormClass and the ItemClass.
It looks good... but the bpm4struts cartridge does not understand that.
First of all: is this a good way to represent the 'master detail' behavior
? if so my suggestion is the generation of the ItemClass and the grid
property inside the FormClass.
Regards,
--------------------------------------------------------------------------- Walter Itamar Mour�o - Diretor de Tecnologia e Projetos - Arcadian S/A www.arcadian.com.br
------------------------------------------------------- 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-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
------------------------------------------------------- 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-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
