[jboss-dev-forums] [Design of POJO Server] - Re: New classloaders in AS 5

[adrian@jboss.org]

Soon and yes I know.

The crappy classloader integration has been an outstanding issue for too long.

http://jira.jboss.com/jira/browse/JBMICROCONT-31
and
http://jira.jboss.com/jira/browse/JBAOP-107

It's not just AOP. :-)

The same broken (reverse integration) strategy where the integratee
defines the integration point and then just goes ahead and uses 
implementation details of other projects without 
regard as to whether they are intended to be used that way
is endemic (EJB3, webservices, jboss-aspects, etc.) and raised here:
http://jira.jboss.com/jira/browse/JBAS-1796

We had the same discussion about EJB3 and Security on Friday.
Eventually, laziness and thoughtlessness comes back to bite you! :-)

In general all integrations should have three components.
1) An implementation neutral api/spi that defines what needs to be
achieved NOT how you achieve it.
2) Implements of (1), i.e. how you achieve it
3) Users
Except for simple cases these should be in three different projects with
the only dependency being on 1 never on 2 - except for integration testing. :-)

Once this is done it will also be relatively trivial to run in A.N.Other appserver
by reimplementing the integration points for that server.

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

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