[jboss-dev-forums] [Design of POJO Server] - Re: Scoping of war/jar file embedded in sar service archives

[adrian@jboss.org]

http://jira.jboss.com/jira/browse/JBDEPLOY-59

Actually, I think the StructureDeployer is probably not the correct place
to add this behavour?

The issue is that we now allow greater control of what/how subdeployment classloaders
get constructed. Even to the extent that a subdeployment classloader
may not be able to see the parent deployment classloader.

e.g.
top-level: domain=foo parent=DefaultDomain
sub-deployment: domain=bar parent=DefaultDomain

Although, I'm not sure somebody would really want to do the above :-)

It would mean that sub-deployment's classloaders needs the manifest entry
even though it is already included in the top-level.

So I think the correct place to put this code would be in the usage of
ClassPathVisitor to "weed out" duplicates in sub-deployment classloader
that are already in one of the parent classloaders (if the parent deployment's classloader
is really a parent of the sub-deployment).

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

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