This content has been marked as final.
Show 4 replies
-
1. Re: Deploy the same webapp twice on different paths.
sbyrne Oct 26, 2005 9:18 AM (in response to sbyrne)I see two things that might do this to put in jboss-web.xml:
<jboss-web> <class-loading> <loader-repository> dot.com:loader=unique-archive-name </loader-repository> </class-loading> </jboss-web>
andUseJBossWebLoader=false
which should I use? -
2. Re: Deploy the same webapp twice on different paths.
sbyrne Oct 26, 2005 9:28 AM (in response to sbyrne)The second option is going to cause problems using jboss's managed connection pool for the database.
-
3. Re: Deploy the same webapp twice on different paths.
sbyrne Oct 26, 2005 10:09 AM (in response to sbyrne)What I watn to do is have WEB-INF/jboss-web.xml with:
<jboss-web> <class-loading> <loader-repository> dot.com:loader=njportal </loader-repository> </class-loading> </jboss-web>
This causes problems with common-logging libraries, resulting in the infamouscannot find setter method setdocbase null
.
I need the commons-logging.jar in my WEB-INF/lib for struts. -
4. Re: Deploy the same webapp twice on different paths.
sbyrne Oct 26, 2005 10:57 AM (in response to sbyrne)Fixed in jboss 4.0.2.