Hello all. If I have an object, Foo, that is stored in an object database (not a relational one), and I wish to make it an EJB, what do I do with the ejbLoad(), ejbStore(), and ejbRemove() methods? They make perfect sense for RDB-stored objects, as this is where you'd call your SELECT, INSERT or UPDATE, and DELETE statements, respectively. However, if the object is stored in an ODB, these methods just don't make any sense, unless your ODB vendor allows you to instantiate a new Foo, then use some vendor-specific utility to effectively link this Foo object with an instance that's stored in the database. Should only container-managed persistence be used to load, store, and remove entity beans? If so, then I must wait until my ODB vendor supplies an EJB server that has a container that can do this. If not, then do I thinly wrap the Foo object in a FooBean that has as a Foo as a private attribute (wrapping all necessary public methods), so that if ejbLoad() is called, I can get the ObjectId object as the primary key, do a lookup by ObjectId, and set the FooBean's Foo reference to the Foo returned from the lookup? Has anyone hit this problem? The O'Reilly book "Enterprise JavaBeans" by Monson-Haefel just skims right over this topic, giving no substantial thought to the problem. TIA, Matthew _____________________________________________________________ Do You Yahoo!? Free instant messaging and more at http://messenger.yahoo.com =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
