Hi Hammett, > > > 1) Developers in that environment have special needs: > > > > a) ease of use. This is the most important thing! They do not > > want to care about technical things - they want to concentrate on > > business logic. No factories, no xml, even no connection handling, no > > SQL if possible. Just POJOs - all as easy as possible. > > Yes, yes!!! I'm looking forward to this, too! >
:-) let's join forces > > Losing? Where? The imperative level of transactional management I'm > proposing here is the same offered by EJB. It is clean and works. Don't > see > why it would be a problem. > If you have complex object models, you will use BMP - and have to manage your own transactions there. The problem here is that you have to know which objects are covered by a transaction. For the component interface (service) this is done by the interceptor framework. That's ok. But the domain objects? And what's about if you have a query and get a collection of domain objects?. Or if you navigate from one object to an other. How do you know, whether this object is "persistable" and covered by a transaction? In my experience, Hibernate is doing an excellent job here. EJB is a poor solution for such problems. Andreas > > regards, > hammett > > > --------------------------------------------------------------------- > 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]
