mhhhm... actually i don't think its possible to define a server-wide
resource inside the context configuration.
the globalnamingresources tag is nested within the server tag, the
context.xml file is based on the
context element which doesn't allow the globalnamingresources
element within.
another try: =)
how does the xml structure look like in your context.xml file? i think
you have to omit the
globalnamingresources tag if you haven't already done so.
the xml file should look like this:
-
Context path=
Resource name= .
ResourceParams name=
alu, artifex wrote:
another try: =)
how does the xml structure look like in your context.xml file? i think
you have to omit the
globalnamingresources tag if you haven't already done so.
Sorry, but no. I specifically want to use a server-wide JNDI resource
instead of redefining the same resource
where did you place your driver .jar-file in? i think you placed it
into CATALINA_HOME/server/lib - for your configuration
(resource is defined in the context) it should be placed in
CATALINA_HOME/common/lib i think.
mfg
alu
Mark Woon wrote:
Hi all.
According to the docs, it's possible to stick
alu, artifex wrote:
where did you place your driver .jar-file in? i think you placed it
into CATALINA_HOME/server/lib - for your configuration
(resource is defined in the context) it should be placed in
CATALINA_HOME/common/lib i think.
I've tried it in both places with no luck.
If you look at the
Hi all.
According to the docs, it's possible to stick Context specific data
into it's own config file in the
|$CATALINA_HOME/conf/[enginename]/[hostname] |directory. Unfortunately,
I'm having problems when using it with JNDI resources. When I take the
Context element from my server.xml and
