ok - I'm completly agree with you. Now, I need more technical details because I'm a new OBJ user.
We are agree that the "EJB/OJB integration design pattern" is : Session beans which are accessing direclty OJB broker(s) without entity bean usage. My first reflexion expose me to 2 different scenarios : 1. Using OBJ in client/server mode. Sessions beans are "OJB clients" and they uses different remote OJB servers. Load balancing, synchro are completly managed by OJB servers. I'm not motivate by this approach for a EJB integration. and you ? 2. Session beans want to call local "OJB data objects". I don't see how to integrate something like a "PersistenceBrokerServer" in a J2EE server. Can you point me to usefull info ? How to support clustering, data cache, connection pool ... in this case ? 3. (?) I have to make a demo application and a small doc for my customer. If you want I will send it to this mailing list. What do you think about that ? It should be nice to find this design pattern in the OJB doc. Regards, Christophe -----Original Message----- From: Mahler Thomas [mailto:[EMAIL PROTECTED]] Sent: vendredi 27 septembre 2002 9:35 To: 'OJB Users List' Subject: AW: OJB/JDO in a EJB context Hi, > -----Original Message----- > From: Thomas Mahler [mailto:[EMAIL PROTECTED]] > Sent: jeudi 26 septembre 2002 19:10 > To: OJB Users List > Subject: Re: OJB/JDO in a EJB context > > > > >Do you expect SUN to admit that entity beans are an obsolete concept? > > No - And you personnaly, do you admit that the entity beans > are obsolete ? > Sure! The failure of EJB entity beans (Performance, inheritance hierarchies, ugly finder code) in one of my customer projects was one of the main reasons to start the OJB project! cheers, Thomas > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
