> Yeah that would make more sense. Do you wanna produce a patch? (Do we
> need to worry about backward compatibility on this?)
Maybe I could look this after I get some sleep, :-). Quick search to
source code gave me an idea. The feature I'm after can easily be patched
at the bottom of Basic Renderer (I think):
for (Iterator fields = classMapping.getFields().iterator();
fields.hasNext();) {
field = (Field) fields.next();
// Some code removed.
// setter
writer.println(" public void set" +
field.getAsSuffix() + "(" + getTrueTypeName(field, class2classmap)
+ " " + field.getName() + ") {");
writer.println(" this." + field.getName() +
" = " + field.getName() + ";");
writer.println(" }");
}
> P.S. We also need someone to patch CodeGenerator to handle
> <one-to-one> associations. They are ignored at present, apparently.
I have started using Hibernate just a few weeks ago, and I'm not very
confident that I know enough of this, but I can look this next week when
I have more time.
Regards
Aapo </b>ungle Laakkonen
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
