[jboss-dev-forums] [Design of POJO Server] - Re: DeploymentContext needs attachments

[scott.stark@jboss.org]

"adrian at jboss.org" wrote : Can't you add that to the deployment context of the war?
  | 
  | i.e.
  | 
  |   | if (moduleTypeIsWar)
  |   | {
  |   |    DeploymentContext warDeploymentContext = ...
  |   |    if (contextRoot != null)
  |   |    {
  |   |       ContextRootMetaData crmd = ...
  |   |       warDeploymentContext.getTransientManagementObjects().addAttachment(crmd);
  |   |    }
  |   |    earDeploymentContext.addChild(warDeploymentContext);
  |   | }
  |   | 
  | 
  | Then it is just a case of getting the war deployer to check it.
  | It must already check it now from the DeploymentInfo in JBoss4?

Currently the war deployer looks to the DeploymentInfo.webContext for an ear level override. 

while the web context-root could be pushed to the associated war context, other info like security roles apply to every component, and potentially needs to be merged. Same situation exists for standardjboss.xml/jboss.xml. To me this is getting more to needing the metadata repository to be able to access scope based overrides.


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

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