I'm not sure if this is 100% correct. I don't think JBOSS uses JDO to implement CMP. I think they used their CMP code to implement JDO.
as for OJB being able to use the benefits of the J2EE server; yes and no. OJB can be configured to use container managed transactions (either through the transactionmanager hack, or the JCA adapter). pooling; really the only thing would be connections which is supported internal to OJB using the apache pooling code. load balancing; if you use OJB in a J2EE load balanced environment, you need to configure to use a distributed cache and lock manager. security; OJB only uses a login for the back end db. Not sure the advantage of using j2ee security here. -----Original Message----- From: Jim Moore [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2003 9:34 AM To: OJB Users List Subject: RE: about OJB relationship with J2EE OJB fits into the J2EE world in the same way JDO does, and there's lots of articles and the like on that. Short answer: OJB/JDO offers persistance and either offers or supports the rest. For example, Oracle 9IAS and JBoss both use JDO to implement their CMP. Jim Moore -----Original Message----- From: Lu Cui [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2003 3:30 AM To: OJB Users List Subject: about OJB relationship with J2EE Hi All I am not clear about OJB's relationship with J2EE, especially the relationship with Entity Beans. J2EE container can offer many services such as load balancing, pooling, catching and security. Can OJB use all these benefits? Or the programmers have to take care of those things themselves? Is there any articles about how OJB fit into J2EE structure? Best regards Cui Lu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
