hello, I was trying to avoid putting tagged values in the UML model if possible, I think they are cumbersome and due to the fact they are not show on screen all the time make them hard to discover.
by extending from the abstract class we would indeed, as you indicate, introduce some overhead and possible refactoring issues: most of the time an implementation class would simple call the super method and add some Javadoc-style attributes, and this feels wrong somehow I see that most of us don't really mind (coarse-grained) andromda.xxx tagged values, so I'll also go with them thanks for the feedback Wouter :) > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Walter > Mourão > Sent: Friday, January 09, 2004 3:14 PM > To: Pieter Van Gorp > Cc: Wouter Zoons; [EMAIL PROTECTED] > Subject: Re: [Andromda-user] Struts cartridge (bpm4struts) > > > You're Definitively right. > Walter > > > Pieter Van Gorp <[EMAIL PROTECTED]> grava: > >Shouldn't we try to map the xDoclet tags in more course grained, > >quality oriented tagged values where possible? I'm sure this is not > >possible in every case, but simply copying all xDoclet tags in the UML > >models seems like not utilizing a great strength of MDA to me ... or > >weren't you implying such usage of tagged values? > > > >(= my 0.02) > > > >Kind regards, > >Pieter. > > > >On vrijdag, jan 9, 2004, at 13:07 Europe/Brussels, Walter Mourão wrote: > > > >> Hi Woulter, > >> > >> Are you going to repeat the getters and setters on the form > >> implementation > >> class ? It seens a bit confusing in case of refactoring... > >> > >> I know I'm insisting, but what do you think about using XDoclets tags, > >> like the hibernate cartridge ? > >> > >> I like this way very much because, despite formal discussions, we can > >> improve the generated code using "tagged values" to create XDoclets > >> tags/parameters... Just as an example, I changed the hibernate > >> cartridge > >> the following way: > >> - if you insert the tagged value "@hibernate.column.unique=true", the > >> Java/XDoclet code is generated with "* unique = true" to that property. > >> > >> - if you insert the tagged value "@property.validation.maxIntValue = 5" > >> the template generates validation code inside the java class that > >> raises > >> an exception avoiding the save/update in case that property has a value > >> above 5. > >> > >> In struts case I think it could be used in many ways, primary in > >> validations (java and struts) and completing the struts-config.xml, > >> inserting plug-ins (I have this trouble now), external forms, actions > >> and > >> so on... If you use the XDoclets I will make the improvements. > >> > >> Regards, > >> > >> Walter > >> > >> > ----------------------------------------------------------------------- > >> ---- > >> Walter Itamar Mourão - Diretor de Tecnologia e Projetos - Arcadian S/A > >> www.arcadian.com.br > >> ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
