On Fri, 2003-09-05 at 21:53, Johnson, Erik J (Erik) wrote:
> (This is using XDoclet v.1.2b3)
> For example, test.interfaces.AddressData has the copy constructor:
>
> public AddressData( AddressData otherData )
> {
> setId(otherData.getId());
> this.street = street;
> this.city = city;
> setCreationDate(otherData.getCreationDate());
> }
>
> Shouldn't the generated code look something like:
> setStreet(otherData.getStreet());
> setCity(otherData.getCity());
> Otherwise, the assignment of street to itself won't do anything.
>
> Can anyone shed some light on the situation?
Looks like a bug to me. The reason some lines use setters and some use
"this.foo = ..." looks to be that it checks first whether a setter
method exists; it only includes setters in the data class for fields
that have a setter in the EJB. However, you're right that the copy
constructor should still use otherData.getFoo(). Please raise a bug
report in JIRA.
Andrew.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
