[Design of JBoss Deployment Framework] - Re: SAR Deployment Deployers Ordering
by adrian@jboss.org
"richard.opalka(a)jboss.com" wrote : "richard.opalka(a)jboss.com" wrote :
| | Thus we're getting null for JBossWebMetaData ctx loader which isn't true in case we're deploying such .sar archive using hot deploy feature (JBossAS is already running). The problem is on JBossAS bootstrap when we have such .sar archive in the deploy directory.
|
| I don't see a ctx loader on JBossWebMetaData?
| That doesn't make any sense.
|
| But it sounds like your real problem is that you just want the classloader for the webapp?
| That's obtainable just by doing DeploymentUnit.getClassLoader()
|
| From AbstractWarDeployment::start()
| which obviously doesn't get invoked until the MBean has its dependencies satisfied
| (i.e. jbossweb is running)
|
| | ClassLoader warLoader = unit.getClassLoader();
| | thread.setContextClassLoader(warLoader);
| |
| | <snip/>
| |
| | webApp = new WebApplication(metaData);
| | webApp.setClassLoader(warLoader);
| |
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186720#4186720
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186720
15 years, 6 months
[Design of JBoss Deployment Framework] - Re: SAR Deployment Deployers Ordering
by richard.opalka@jboss.com
"richard.opalka(a)jboss.com" wrote :
| The problem of our deployers is it don't deal only with deployers metadata but also with services metadata that are e.g. configured when web app is deployed.
|
To clarify my problem here's one example. We have two deployers registered for POJO webservices deployments which order in deployers chain is important:
WebServicesDeployerPreJSE < WarDeployer
WarDeployer < WebServicesDeployerPostJSE
The problem is when we have .sar deployment incorporating nested war deployment (web service POJO), the WebServicesDeployerPostJSE is called before the nested war is really deployed to the real. Thus we're getting null for JBossWebMetaData ctx loader which isn't true in case we're deploying such .sar archive using hot deploy feature (JBossAS is already running). The problem is on JBossAS bootstrap when we have such .sar archive in the deployer directory.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186712#4186712
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186712
15 years, 6 months