[jboss-dev-forums] [Design of POJO Server] - Re: Deployers and classloading - stumbling block

[adrian@jboss.org]

That's fine as long as the deployers are playing by the rules
and are self-contained or semi-self-contained (only reference
other deployers metadata).

If they reference the runtime then you are going to leak
everything into the bootstrap classloaders.
Once one gets in there, the rest will follow like dominos.

The ideal should be to have two packages:
1) That is the deployer and its metadata, e.g. the WebDeployer
2) That is the runtime implementation e.g. web deployment and server

i.e. The deployer parses the metadata and creates a
ServiceMetaData or BeanMetaData with only string references
to the runtime classes

In practice, our implementations are a long way from this currently.

Having something that is closer to JBoss4 as an incremental step
is probably going to help us get things done faster?

I think some form of hotdeployment of deployers is going to
be done at some stage anyway.
e.g. to support people playing with profiles where the results
are more dynamic than a full reboot. :-)

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

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