That is also my workaround right now but I don't believe it's normal behaviour. Since it is a dependant child, I would like to only be able to modify it from its associated bean.
Thanks for your answer, Francois -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathaniel Rahav Sent: March 27, 2003 10:01 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [Xdoclet-user] RE: Value Objects for one to one CMR composition I have also encountered this problem and posted to this list last week about it (see http://sourceforge.net/mailarchive/message.php?msg_id=4165010 ) Could this be a bug in XDoclet's source code generation ? My current workaround is to create the dependent value object's bean by hand in the relevant Session Bean and then set the parent's value object to point to the already existing dependent value object. Nat ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
