If you're just deploying war files, you can just omit the jboss-web.xml 
and rename the war file to whatever you want, and that will be the 
context-root.

For example, with not context-root in jboss-web.xml, naming a war file 
foobar.war and dropping it in the deploy directory will give your web 
app a contex-root of /foobar/.  The name myapp.war will have a 
context-root of /myapp/, etc.

Regards,
David

--

LaBanca, Rick wrote:
> I take it 3.0.1's goals are stability/fixes. Where should suggestions get
> submitted?
> 
> One I have is this, up for discussion/opinion. Right now it seems the way to
> say the context name war is mapped to is in jboss-web.xml (<context-root>).
> But this resides inside the war. 
> 
> For me, I would expect generally anything server specific to be externally
> defined, or mapped. Right now it seems like a delivered app/war would have
> to have my admin open and edit a jar to change the context mapping, which
> seems wrong. 
> 
> So for this particular case,  wouldn't it make sense to have some external
> config (not sure which file) allowing the mapping of what's in jboss-web.xml
> for context name to something else?  
> 
> Of course I hope I just missed something and there is a way, I did look thru
> the dtd's and couldn't see where I would do it... But I'm very new to jboss.
> 
> 
> rick



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to