> > <property name="bar" type="serializable" ....> > > <meta attribute="description"> > > JavaDoc comment for getBar() > > </meta> > > <meta attribute="java-type">java.lang.Object</meta> > > </property> > > ..... > > But this one ? Isn't this a bit "cloudy".... > If I understand this correctly you want that if "java-type" > is provided the codegenerator should use that type instead of > the type specified in the property....Just curious, when is > that usefull ?
>For example: ><property name="date" type="date"/> >currently generates: >public java.sql.Date getDate(); >what if you wanted >public java.util.Date getDate(); hmm - ok, I see your point...will look into it... >Hey, I just thought of another <meta> that would be *very* useful: ><property name="bar" type="String" ....> ><meta name="scope">protected</meta> ><meta attribute="description"> >JavaDoc comment for getBar() ></meta> ></property> >surprised I didn't think of that before.... I actually think about this before, but could not come to term with me in what the scope should mean... Its it the actual field, the getX() or the setX() that should be modified ? (The same actually goes for the "description" tag...) How about having "description-get", "description-set" and just "description" for the actual field ? (or should it be "description-field" And then similarily "scope-get", "scope-set" and "scope"/"scope-field" for the actual field ? Maybe "scope" and "description" should just apply for both set, get and field if nothing else is specified ? Any thoughts ? /max ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
