--- Marcus Brito <[EMAIL PROTECTED]> wrote: >
Charlene Mitchell wrote:
>
> > I already tried that and the log files got huge,
> and the memory was
> > crippled because the application server got stuck
> in a loop going back
> > and forth between the 2 same entities
>
>
> Value Objects currently have a little(?) deficiency
> in which they can't
> be used in a circular way. So, if you have
> aggregate/composed addresses
> in your Employee value object, *don't* add an
> aggregate/composed
> employee in your Address value object.
>
> We've discussed this situation for a while, but it's
> still without
> solution. Any suggestions and patches are surely
> welcome.
Well, that explains why the following is commented out
in the samples I guess?
* @ejb:value-object match="*"
compose="test.interfaces.AddressValue"
compose-name="AddressValue"
*/
// public abstract test.interfaces.AddressLocal
getAddress();
Charlene
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
-------------------------------------------------------
This sf.net email is sponsored by: Are you worried about
your web server security? Click here for a FREE Thawte
Apache SSL Guide and answer your Apache SSL security
needs: http://www.gothawte.com/rd523.html
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
