|
Heiko,
>> XDoclet 1.2 seems to be even less capable than 1.2b3 with respect to = generating value=20
>> objects. Using 1.2, generated entity facades reference value objects = named <bean_name> >> Data, which I believe is a carry over from the deprecated <dataobject> = ejbdoclet subtask. > 1.2b3 uses the correct <bean_name>Value names for ="">value objects, which has motivated my=20 >> decision to use it. >Hm. >1.2 release appeared after 1.2b(eta)3. We use the ValueObjects like this ><valueobject pattern=3D"{0}VO"> >for a year now without problem. >>From looking at valueobject.xdt, "Data" is not even mentioned there. > Heiko The problem with generated entity facades results
from errors within entityfacade.xdt, rather than valueobject.xdt. The
entityfacade.xdt template references XDtEjbDataObj rather than
XDtEjbValueObj, and contains strings like getData() rather than
getValue() in it. The copy of entityfacade.xdt within
XDoclet1.2b3-MIDDLEGENVO seems to work better. I'll take your
recommendation though regarding XDoclet 1.2, and try using 1.2b3's
entityfacade.xdt.
Shaun
|
- [Xdoclet-user] Value object generation for an entity with ... Shaun
- RE: [Xdoclet-user] Value object generation for an ent... Rupp, Heiko
- Re: [Xdoclet-user] Value object generation for an ent... foad_momtazi
- RE: [Xdoclet-user] Value object generation for an ent... Shaun
- RE: [Xdoclet-user] Value object generation for an ent... Rupp, Heiko
- RE: [Xdoclet-user] Value object generation for an ent... Shaun
- RE: [Xdoclet-user] Value object generation for an ent... Harkness, David
