[jboss-dev-forums] [Design of POJO Server] - Re: Missing EAR/WAR Isolation

[scott.stark@jboss.org]

"jason.greene at jboss.com" wrote : 
  | Ah I see, I was confused since currently, EARStructure is parsing jboss-app.xml.
  | 
  | The issue is the lack of a default if there is no jboss-app.xml (or no loader-repository-config). In the past we had a global isolation setting directly on the ear deployer. So I assumed we are keeping that. I take it we are moving away from it?
  | 
No, the global setting should be coming in from the AppParsingDeployer as a default. Its just not been ported over. I created this issue for that:
http://jira.jboss.com/jira/browse/JBAS-4214

"jason.greene at jboss.com" wrote : 
  | Ah I see. Yes,  the issue is that the WS deployer has to inspect every war (WS or not) by loading all servlet classes (and related WS classes if it is in fact a WS deployment). If the DeploymentUnit CL is not isolated, there is the possibility of a conflict with multiple deployments. 
  | 
  | That said, fixing EAR isolation will resolve the WS TCK issues, since they separate the client and server side components in individual EARs.
  | 
I created this issue for the externalization of the war class loader.
http://jira.jboss.com/jira/browse/JBAS-4215



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

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