||What's Wrong with the EJB 2 Specification?|
So it seems to me that the underlying message is that finally J2EE developers agree that they needed a fine grained object model in the first place.(EJB's dependent objects, JDO spec...)
Do you guys know Apple's EOF (Enterprise Object Framework) ? It provides a better and cleaner contract than EJB...in your terminology it is a fine grained object model that manages persistence in a CMP fashion, with a lot of benefits...no deployment descriptors, local and remote (you can even split your business logic is an Enterprise Object by specifying which methods are executed locally and which are executed remotely - HTTP or IIOP) and more ...
Hear us Roar