Hi,
This behaviour is specific for JBoss and it is intentional. Indeed, JBoss
uses one (master) classloader for all applications.
You can specify however that you want JBoss tu use *another* classloader on
a per-ear basis. For this, you must write a file called jboss-app.xml and
put it next to the application.xml file of the EAR. The contents of the
jboss-app.xml file look like this:
<jboss-app>
<loader-repository>
hello:service=LoaderRepository
</loader-repository>
</jboss-app>
Where hello is the name under which your classloader will be known. Both
"hello" and "LoaderRepository" are names that you can invent.More info in
this fine article:
http://ramya.bhaavana.net/chaitanya/archives/000021.htmlGood luck,Tom
Vekemans----- Original Message -----
From: "Brad Balmer" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Thursday, May 06, 2004 6:03 PM
Subject: Re: JBoss two Web Apllications Actions overlapping
> I believe I had this same issue where JBoss (or Tomcat actually) shares
> the same classloader for all web applications?
>
> Anyway, I fixed this by adding the following to my jboss-service.xml
> inside the jbossweb-tomcat41.sar\META-INF directory.
>
> *<attribute name="UseJBossWebLoader">false</attribute>*
>
> I added it directly under:
> <attribute name="LenientEjbLink">true</attribute>
>
> Hope this helps.
>
> --Brad Balmer
>
> Mathies, R. (Ronald) wrote:
>
> >Hi All,
> >
> >I've got a JBoss 3.2.3 server that is running two applications and i've
> >got a problem with the action/form objects:
> >
> >ApplicationA has an action called
> >"/main/application/StartApplicationAction"
> >ApplicationB has an action called
> >"/main/application/StartApplicationAction"
> >
> >And the applications sometimes use each others action objects.
> >
> >The implementation of these actions can be different but the
> >ActionSerlvet doesn't seem to notice that.
> >
> >Does anybody know a solid solution to this problem? So i'm looking for a
> >solution to seperate the applications from each other, i've already
> >found a solution for the .jsp files by changing the scratch dir of
> >tomcat:
> >
> > <servlet>
> > <servlet-name>JspServlet</servlet-name>
> >
> ><servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
> > <init-param>
> > <param-name>logVerbosityLevel</param-name>
> > <param-value>WARNING</param-value>
> > </init-param>
> > <init-param>
> > <param-name>scratchdir</param-name>
> > <param-value>../combisearch/__generatedJSPs</param-value>
> > </init-param>
> > <load-on-startup>3</load-on-startup>
> > </servlet>
> >
> >This will make shure that ApplicationA can't use ApplicationB's JSP
> >files.
> >
> >I've you need more information i'll be happy to hand it.
> >
> >Thanx in advance.
> >Ronald
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
