Hi, all.

Submitted this as a bug on sf:

https://sourceforge.net/tracker/index.php?func=detail&aid=577891&group_id=31602&atid=402704

but here's a copy/paste for good measure:

When using @ejb:bean use-soft-locking="true" and
creating an <entitycmp/> class and a <valueobject/>
class, there seems to be a mixup on the version
primitive type.

The generated value-object has signatures:
public long getVersion() and
public void setVersion(long version).

However, the generated XXXCMP entity bean has signatures:
public abstract int getVersion() and
public abstract void setVersion( int version ).

The generated getXXXData() method in the XXXCMP bean
class still works, as java allows some interoperability
of those primitive types (I'm assuming as long as the
long doesn't outscope the int) - however this should be
fixed so that the primitive types match. I would
suggest long for both, to be safe.

Oh, yeah - my env:
Sun Linux JDK 1.4.0_01
Red Hat 7.1, Linux 2.4.9-31
Ant 1.5Beta3
XDoclet CVS version from 7-5-2002 10:00 AM 'ish.

Thanks,
David



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Bringing you mounds of caffeinated joy.
http://thinkgeek.com/sf
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to