[jboss-dev-forums] [Design of POJO Server] - Re: Implicit container dependencies

[adrian@jboss.org]

In general we should be trying to simplify the platform.
We should be letting each area get on with what it does best.

EJB3 is not an integration api, JCA is.

The JBoss EJB3 implementation is still doing far too much integration work itself
which is continually a problem both in terms of not reusing code that is known
to work, but also in terms of the portablity as these integration details change.

In some cases, constraints are being imposed on other projects
where EJB3 is using api that was never intended for external use.

Webservices has the exact same problem which is why I was complain about
them breaking the build all the time.

It should be the AS (or in future "JBoss Embedded") that defines a 
portable integration api for EJB3/Webservices
to hook into not EJB3/Webservices each doing their own "broken" integrations
with every other project including the AS itself.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033107#4033107

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033107