Have a look at this jboss-web.dtd - all should become clear....
Jules
display name wrote:
> David,
>
> Thanks for this suggestion, Could you further explain #1. I'd like to just
> be able to use the war file for this, as the webapp doesn't use any ejb
> right now.
>
> The 2.4.x book gives no information on the context-root attribute except for
> in the application.xml file.
>
> The 3.0 getting started guide (in the jetty section) also mentions this
> method using jboss-web ("put a jboss-web.xml into your .war's WEB-INF
> directory and specify the context root in that"),
>
> I guess I really need an example on jboss-web that uses this method.
>
> Thanks again
>
> ----- Original Message -----
> From: "David Ward" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, July 09, 2002 5:06 PM
> Subject: Re: [JBoss-user] root webapp on jboss 3.x
>
>
>
>>Root.war is very different than ROOT.war. JBoss wants ROOT.war.
>>
>>Unfortunately, on Windoze, you cannot rename Root.war to ROOT.war in
>>Windows Explorer. Go to a cmd terminal (just to be safe), first rename
>>it to foobar.war, than to ROOT.war.
>>
>>You do have two other methods, though.
>>
>>1) Add a jboss-web.xml in your WEB-INF directory that specifies the
>>context as /.
>>
>>2) Instead of #1, put your war in an ear file and use the
>>application.xml to map your war to /.
>>
>>David
>>
>>--
>>
>>display name wrote:
>>
>>>I am used to the tomcat way of deploying Root.war in the webapps
>>
> directory,
>
>>>and accessing it at http://servername:8080 but when I put a war in the
>>>default/deploy directly, as you know, I have to type
>>>http://servername:8080/Root to get to it. How do I implement a root
>>>directory? Is this in a conf file? This would be nice to add in the
>>>getting started documentation as well.
>>>
>>>Thanks,
>>>
>>>Brian
>>
>>
>>
>>-------------------------------------------------------
>>This sf.net email is sponsored by:ThinkGeek
>>Stuff, things, and much much more.
>>http://thinkgeek.com/sf
>>_______________________________________________
>>JBoss-user mailing list
>>[EMAIL PROTECTED]
>>https://lists.sourceforge.net/lists/listinfo/jboss-user
>>
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Two, two, TWO treats in one.
> http://thinkgeek.com/sf
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
<?xml version='1.0' encoding='UTF-8' ?>
<!-- The JBoss specific elements used to integrate the servlet 2.3 web.xml
elements into a JBoss deployment. This version applies to the JBoss 3.x
releases.
DOCTYPE jboss-web
PUBLIC "-//JBoss//DTD Web Application 2.3//EN"
"http://www.jboss.org/j2ee/dtd/jboss-web_3_0.dtd";
-->
<!-- The jboss-web element is the root element.
-->
<!ELEMENT jboss-web (security-domain?, context-root?, virtual-host?,
resource-env-ref*, resource-ref* , ejb-ref*)>
<!-- The context-root element specifies the context root of a web
application. This is normally specified at the ear level using the standard
J2EE application.xml descriptor, but it may be given here for standalone wars.
This should not override the application.xml level specification.
-->
<!ELEMENT context-root (#PCDATA)>
<!-- The security-domain element allows one to specify a module wide
security manager domain. It specifies the JNDI name of the security
manager that implements the org.jboss.security.AuthenticationManager and
org.jboss.security.RealmMapping interfaces for the domain.
-->
<!ELEMENT security-domain (#PCDATA)>
<!-- The virtual-host element allows one to specify which virtual host the war
should be deployed to. Example, to specify that a war should be deployed to the
www.jboss-store.org virtual host add the following virtual-host element:
<virtual-host>www.jboss-store.org</virtual-host>
-->
<!ELEMENT virtual-host (#PCDATA)>
<!--The resource-env-ref element maps from the servlet ENC relative name
of the resource-env-ref to the deployment environment JNDI name of
the administered object resource.
Example:
<resource-env-ref>
<resource-env-ref-name>jms/NewsTopic</resource-env-ref-name>
<jndi-name>topic/NewsTopic</jndi-name>
</resource-env-ref>
-->
<!ELEMENT resource-env-ref (resource-env-ref-name , jndi-name)>
<!-- The resource-env-ref-name specifies the name of the web.xml
resource-env-ref-name element which this mapping applies.
-->
<!ELEMENT resource-env-ref-name (#PCDATA)>
<!--The resource-ref element maps from the servlet ENC relative name
of the resource-ref to the deployment environment JNDI name of
the resource manager connection factory.
Example:
<resource-ref>
<res-ref-name>jdbc/TheDataSource</res-ref-name>
<jndi-name>java:/DefaultDS</jndi-name>
</resource-ref>
-->
<!ELEMENT resource-ref (res-ref-name , jndi-name)>
<!-- The res-ref-name specifies the name of the web.xml res-ref-name element
which this mapping applies.
-->
<!ELEMENT res-ref-name (#PCDATA)>
<!-- The ejb-ref element maps from the servlet ENC relative name
of the ejb reference to the deployment environment JNDI name of
the bean.
Example:
<ejb-ref>
<ejb-ref-name>ejb/Bean0</ejb-ref-name>
<jndi-name>deployed/ejbs/Bean0</jndi-name>
</ejb-ref>
-->
<!ELEMENT ejb-ref (ejb-ref-name , jndi-name)>
<!-- The ejb-ref-name element gives the ENC relative name used
in the web.xml ejb-ref-name element.
Used in: ejb-ref
-->
<!ELEMENT ejb-ref-name (#PCDATA)>
<!-- The jndi-name element specifies the JNDI name of the deployed
object to which the servlet ENC binding will link to via a JNDI
LinkRef.
Used in: resource-ref, resource-env-ref, ejb-ref
-->
<!ELEMENT jndi-name (#PCDATA)>
