I'm out then. I'm fine with the way tomcat operates and don't feel
anything in the way context xml files are associated with webapps is
ambiguous. It's really simple:
1. If you just want to deploy a webapp and don't need to define any
resources like db pools, just drop the webapp in the weba
2008/9/3 David Smith <[EMAIL PROTECTED]>:
> There's an implicit association based on the context path. myWebApp.xml in
> conf/Catalina/localhost is implicitly associated with the webapp myWebApp in
> the webapps directory, whether it be as a .war or expanded folder.
Yes, I agree that the docs rea
> From: Paul Pepper [mailto:[EMAIL PROTECTED]
> Subject: Re: Problem with JNDI environment entry resources
>
> Besides, I don't see any other documented way of associating
> each application with its associated element within
> server.xml.
Because you're not
There's an implicit association based on the context path. myWebApp.xml
in conf/Catalina/localhost is implicitly associated with the webapp
myWebApp in the webapps directory, whether it be as a .war or expanded
folder.
Illegal may be a strong word -- it implies that tomcat will flat out
reje
> I'll have to check the docs again. However, docBase is only legal when the
> webapp is stored outside of the
> appBase directory. Otherwise, you risk ending up with double deployment.
I don't see docBase described that way in the docs - at this moment
I'm referring to
http://tomcat.apache.or
contained within this transmission.
> Date: Wed, 3 Sep 2008 14:42:24 +0100
> From: [EMAIL PROTECTED]
> To: users@tomcat.apache.org
> Subject: Re: Problem with JNDI environment entry resources
>
> Martin,
>
> Thanks for the suggestion, though I think there may have
> From: Paul Pepper [mailto:[EMAIL PROTECTED]
> Subject: Re: Problem with JNDI environment entry resources
>
> Tomcat 6 docs states that docBase is a valid attribute
> in this situation.
I'll have to check the docs again. However, docBase is only legal when the
webapp is s
Martin,
Thanks for the suggestion, though I think there may have been some
misunderstanding. I'm attempting to access a simple java.lang.String,
not a DataSource. elements are used to place String
resources in an application's environment, not elements,
AFAIK.
Paul.
2008/9/3 Martin Gainty <[EM
Thanks Chuck,
I just tested this by creating a context element in its own file under
conf/Catalina/localhost/jnditest.xml and that worked. (BTW, Tomcat 6
docs states that docBase is a valid attribute in this situation. It is
only illegal when the element is defined within
META-INF/context.xml.):
http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html
/WEB-INF/web.xml contents which contain a jndi reference http://java.sun.com/xml/ns/j2ee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.
> From: Paul Pepper [mailto:[EMAIL PROTECTED]
> Subject: Problem with JNDI environment entry resources
>
> Can anyone suggest what I might have missed?
What happens if you follow the (strongly) recommended practice of not putting
elements in server.xml? If you don't want to put the
inside you
11 matches
Mail list logo
