[jboss-dev-forums] [Design of POJO Server] - Re: Why is DeploymentUnit.getDeploymentContext() deprecated?

[bill.burke@jboss.com]

"adrian at jboss.org" wrote : "bill.burke at jboss.com" wrote : 
  |   | Are the JARs within WEB-INF/lib DeploymentUnits in the new kernel?  If so, then WEB-INF/classes also needs to be a separate DeploymentUnit.
  |   | 
  | 
  | No. The deployment unit is the war.
  | WEB-INF/lib and WEB-INF/classes form part of the ClassPath.

As far as Class-path manifest goes, I think we are screwed either way.  For auto-scanning of the PU you will want to scan only the classpath manifest of one particular jar in web-inf/lib.

Another problem I see is again, what abput META-INF/persistence.xml?  In a war, it could be in multiple JARs in web-inf/lib.  I need to be able to look at the JAR as a completely contained unit.  So whether or not Class-path manifest should be scanned, I still need to know what exact JARS are in WEB-INF/lib excluding classpath manifest entries so that I can find the META-INF/persistence.xml for each of these jars.


Also, what about an EJB-JAR within an EAR?  Is the EJB-JAR a DeploymentUnit I assume?  If it is a DeploymentUnit does its ClassPath contain EAR/lib jars?  If so this is really bad as again, I need to treat the EJB-JAR as its own unit.

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

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