This is the expected behavior given the current ear deployer. EJB classes
are made available to wars and if you put you servlets in the ejb-jar archive
it will be seen there first as this is ahead of the war classes. If you don't
want this behavior only include the servlet in the war.

----- Original Message ----- 
From: "Remus Jivcu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 20, 2001 4:37 AM
Subject: [JBoss-user] Classloader problem in ear


> Hi,
> 
> During deploying some applications on JBoss I've discovered following
> interesting thing :
> 
> Suppose I have this structure in my ear file :
> - test.jar (simple session bean - not used at all in this case)
> - test.war (one simple servlet)
> - META-INF folder with application.xml file.
> 
> 1) If my servlet class is placed ONLY in test.war, then the classloader
> for the servlet is : AdaptiveClassLoader (normal case, I assume);
> 2) If I place my servlet ALSO in test.jar (let's say by mistake), then
> the classloader for the servlet is : java.net.URLClassLoader@4df764
> 3) If I place my servlet ONLY in test.jar, then the classloader for the
> servlet is (again) : java.net.URLClassLoader@4df764
> 
> Question is : why servlet is taken from .jar and not from .war archive
> for case #2 ? Why servlet is found in case #3 after all ?
> 
> Is there anything that I'm missing here, or is this a bug ?
> 
> I hope someone could help me.
> 
> I'm using : Windows NT 4.0, JDK 1.3.1, JBoss 2.2.1-Tomcat (and also
> JBoss 2.2.2-Tomcat).
> 



_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to