so it is ok to associate the @tags with the class attributes, which seem more intuitive for or mapping, instead of the getXXX() methods? if not, what are the reasons for tying the @tags to the getXXX() methods?
also, is there any documentation on how to get started developing modules for xdoclet2? is xdoclet2 (in cvs) fairly stable to start using?
do any of the current or modules (i.e. jdo) currently generate the sql scripts to create and drop tables?
for the proposed or mapping "parent" task with subtasks for each specific technology (jdo/castor/hibernate/etc), should it be modeled similar to the way there is a "parent" ejb task with subtasks for each specific ejb vendor?
thanks.
At 18:09 02/11/07 +0330, you wrote:
> are the tags tied to the getXXX() methods of a class? this was one thing > that i changed with the new castor version that i was working on. since > ormapping deals with classes(tables) and attributes(dbFields), i > associated > the @tags with class attributes instead of getXXX() methods. just seemed > to make more sense. > > also, if the @tags are tied to the fields, then one can simply create a > skeleton class with just the attributes and associated @tags, then > that .java file could be used to generate getXXX() and setXXX() methods > for > each attribute... this could really minimize the work of creating tedious > entity/data objects...All IDEs generate getter/setter for you, why bother with that? Imho we should be able to put the tags on getter&setter&field. Ara.
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
