[jboss-jira] [JBoss JIRA] Created: (JBCL-112) EAR classloading isolation and custom deploy directories

[C?dric Chantepie (JIRA)]

EAR classloading isolation and custom deploy directories
--------------------------------------------------------

                 Key: JBCL-112
                 URL: https://jira.jboss.org/jira/browse/JBCL-112
             Project: JBoss ClassLoader
          Issue Type: Bug
          Components: ClassLoader, ClassLoaderPolicy, ClassLoaderSystem
         Environment: JBoss 4.2.3.GA (SVNTag=JBoss_4_2_3_GA date=200807181417), JVM = ibm-java2-i386-50
            Reporter: C?dric Chantepie
            Priority: Minor


I deploy same webapp in two differents EAR, let call them A.ear and B.ear.
A.ear and B.ear are isolated in term of classloading, according ClassLoading JBoss documentation : different loader-repository specified in each META-INF/jboss-app.xml.

I haven't change JBoss global configuration (classloading is default one with this JBoss release), except I've added deploy directories (different from JBOSS/server/default/deploy) :
      <attribute name="URLs">
         deploy/,file:///...path-to-extra-deploy-1...,file:///...path-to-extra-deploy-2...
      </attribute>

All is deployed. To be sure I've changed a JSP in webapp within B.ear to be sure it's different from the one in A.ear .

The trouble is that classes from A.ear and B.ear are not isolated. That's to say when I get a webapp servlet class it's the same from A.ear and B.ear (and the same for other webapp resources).

As I can't figure what was wrong with my isolation configuration, I've moved A.ear and B.ear from their respective deploy directories to JBOSS/server/default/deploy, so that all files are in this defaut directory. In this way, and without any change to A.ear and B.ear, isolation is properly set up at deployement, and so everything work perfectly.

So this is not a major "bug", but I'd like to know whether I miss something at combining custom deploy directory and classloading isolation, or there is a real problem with that.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira