On Tue, Dec 10, 2002 at 03:23:31PM -0500, Jim Crossley wrote: > The app I'm currently working on is very CRUD-ish; it does simple > read/write maintenance on a bunch of related objects. I don't want the > web tier to access the Entity beans directly -- this would violate the > transactional requirements -- so they go through a Session Facade. > Creating additional POJO's through which the session beans interact with > the entities only adds an unnecessary layer of complexity IMHO. > > The app is currently implemented using OJB, and I'm interested in > refactoring it to use CMP EJB's, which IMHO are much easier to create > and maintain (with Xdoclet, of course) than OJB.
Interesting. Isn't there a extention to xdoclet for OJB then? If that is all that make it hard to maintain, I can't understand what you are talking about. I am in fact considering moving from CMP EJBs to hibernate, or other similar products like OJB, because of the complexity of CMPs. What I find complex and hard to create and maintain is the CMP-beans and the corresponding VO-objects. As I have read, you can work with ordinary java objects when using OJB/hibernate and use them as VO-objects. It is also annoying that you have to rerun xdoclet for every change in the CMP beans to have the clients (SL Session Beans for instance) that are using the CMPs to compile. Not at least is one reason to move away from CMP the slow performance. I am not sure other O/R-products are better but I think it is worth a try. -- MVH Marius Kotsbak Boost communications AS ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
