this is the jboss-web dtd - it shows where you are allowed to specify
the context-root tag, amongst others....
Jules
bryan hansen wrote:
> Ok sorry for possibly not seeing the obvious, but I am
> looking at the flashline documentation, specifically
> at jboss-web.xml, and I don't see how to specify a
> context in the jboss-web.xml. If you have a sample
> that would be awesome.
>
> I wasn't struggling with the unpackaged ear or war
> file, the only thing that seemed a little strange was
> how to specify what the war file was in an
> application.xml file. If the ear and war file is
> unpacked I am actually referencing a folder and it
> wasn't seeming to work when referencing a folder.
>
> Thanks,
>
> Bryan
>
>
> --- Jules Gosnell <[EMAIL PROTECTED]> wrote:
>
>>Get over the mental hurdle of thinking of deploying
>>an unpacked war as
>>different from a packed one - they should be treated
>>in exactly the same
>>way. Unpacked is just more accessible (for
>>development) than packed (for
>>production).
>>
>>If you want to set your application context either:
>>
>>1. deploy an unpacked ear with it configured in
>>application.xml (The
>>standard J2EE way)
>>
>>2. you can configure it in
>>my.war/WEB-INF/jboss-web.xml (the proprietary
>>JBoss way)
>>
>>3. rename your war to <required-context>.war -
>>common non-standard hack?
>>
>>
>>All this and more is in :
>>
>>
>
>
>http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/contrib/jetty/FAQ?rev=HEAD&content-type=text/vnd.viewcvs-markup
>
>>Let me know if you would like anything added.
>>
>>
>>Jules
>>
>>
>>bryan hansen wrote:
>>
>>>I am trying to define the context root of an
>>>application without including it in an ear file.
>>
>>Is
>>
>>>this possible in JBoss/Jetty? About two weeks ago
>>>someone on the list recommended not packaging an
>>>application into a war to deploy, but instead
>>
>>placing
>>
>>>an unzipped directory (that would be your war) so
>>
>>that
>>
>>>you could work on JSP(s) and have them
>>
>>automatically
>>
>>>deploy and show the changes. This was a cool idea,
>>
>>but
>>
>>>then I realized we needed to change the
>>
>>context-root
>>
>>>of the application and the only way I know of
>>
>>doing
>>
>>>that is with the application.xml inside an ear. I
>>>tried including one in a META-INF directory under
>>
>>the
>>
>>>folder that we deployed, but the change didn't
>>
>>take
>>
>>>affect. Any ideas as to how we might get this to
>>
>>work?
>>
>>>Thanks,
>>>
>>>Bryan
>>>
>>>__________________________________________________
>>>Do You Yahoo!?
>>>Sign up for SBC Yahoo! Dial - First Month Free
>>>http://sbc.yahoo.com
>>>
>>>
>>>
>>
> -------------------------------------------------------
>
>>>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
>>Stuff, things, and much much more.
>>http://thinkgeek.com/sf
>>_______________________________________________
>>JBoss-user mailing list
>>[EMAIL PROTECTED]
>>
>
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
> __________________________________________________
> Do You Yahoo!?
> Sign up for SBC Yahoo! Dial - First Month Free
> http://sbc.yahoo.com
>
>
> -------------------------------------------------------
> 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)>
