Bugs item #561048, was opened at 2002-05-27 14:31
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=561048&group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Rainer Bieniek (rbieniek)
Assigned to: Nobody/Anonymous (nobody)
Summary: JBoss-3.0.0-RC3 ear deployment problem
Initial Comment:
While deploying an ear-file into a jboss-3.0.0-rc3
instance the context-root's which are defined in
the application.xml get ignored and a constructed
default ones are used.
This appear to happen in a deployment situation
like:
<application>
<module>
<web>
<web-uri>war/phonebook-cocoon2.war</web-
uri>
<context-
root>/phonebook/cocoon2</context-root>
</web>
</module>
</application>
The defined context root is /phonebook/cocoon2
and the the one figured out by the jboss instance
is /phonebook-cocoon2
A quick look through the RC3 sources reveals an
assumption in AbstractWebContainer.java, method
init(DeploymentInfo di), around line 229 as the
source for this problem.
The web context from the J2eeModuleMetaData
object is only handed over to the DeploymentInfo
object in case the short name in the deployment
info (phonebook-cocoon2.war) is the same as the
module's file name (war/phonebook-cocoon2.war).
The two names are not the same and therefore the
webContext stays null and a default one gets
constructed later on
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=561048&group_id=22866
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
