Thanks for that clarification, you are indeed correct:

Bean provider must not expose the get and set methods for container-managed relationship fields or the persistent Collection classes that are used in CMR through the remote interface of the bean.

With that said though, the Value Object documentation at the XDoclet site needs to change.

Rupp, Heiko wrote:

Hi,



I seem to have found an interesting issue with xdoclet's code generation and using remote interfaces with entity relationships.



Afair, this is not allowed per EJB 2.0 spec. See 10.3.10 of the spec.


------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id%62&alloc_ida84&opĚk _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user






------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to