Hi, > we are definitely using OJB hardcore in a J2EE environment. > We use the Stateless session bean with value objects > approach. Over 350+ different classes mapped. Every type of > relationship. Non trivial. > > I'm not sure how much this will help you, but fwiw.
Thanks it encourages me to know someone already did it! > >>The first solution can be : session bean wich is using > >>direclty OBJ as a persistence manager. Entity beans are > >>completly ignored in this case. Is it make sense for you ? > > I generally recommend this approach! How does this approach work in a clustered environement. Do we have to expect problems with the PersistenceBroker? > 1. OJB proxies are portable. That is you don't have to send > large object > nets, but can use OJB proxies to provide lazy materialiation > for session > bean clients. Thats right but in some cases we need to view lists with several thousands of entites. With pure OJB no problem, we send Proxies and call getXXX methodes only for the ones you can "see". With the VO approach we need to send the complete data to the client... Anyway thanks Thimo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
