My understanding of the EJB 2.0 spec is that remote entity beans are "deprecated". You should only use local entity beans.
Data objects were invented mainly to avoid calling remote entity beans and reduce network traffic. Therefore, if remote entity beans are not used, I don't see the reason to use data objects either. Just use the local entity beans (which have the CMR support, right?). In other words, my understanding of EJB 2.0 is that data objects go down the drain with remote entity beans. You'll never need them again. Would this work for you? I know you're a local-fan ;-) My 2 cents on J2EE patterns ;-) Aslak >From: "James Higginbotham" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Subject: [Xdoclet-user] Data Objects and CMR >Date: Wed, 12 Dec 2001 20:23:28 -0600 > >Anyone out there using CMP 2.0 and container managed relationships (CMRs) >with XDoclet? How are you handling the data objects being generated without >relationships? My guess is that I would write a simple class to wrap my >master and detail objects, but this somehow seems wrong. > >For example, I have a UserAccountData, UserPhoneData, and UserAddressData. >Right now, it is a 1-1 mapping, so I would create a UserAccountModel, which >held 1 reference to an instance of each. My stateless session bean would >then accept the model in its createAccount() method and create the 3 CMPs >appropriately. > >Anyone have any suggestions on this? > >Thanks, >James _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
