Thanks for your help. You wrote:
-----------------------------------------------------------------------------
Always better to be too much than not enough.
At a quick glance I see two errors.
One make
<Context
path="/APLRegistration"
docBase="/usr/local/webapps/aplregistration/exploded"
<Context
path="/APLRegistration"
docBase="/usr/local/webapps"
this for the root of the app. When the war or root folder resides.
-----------------------------------------------------------------------------
I'm confused by this. First, I found that to get the datasource to work at all
I had to use a context file with a docbase pointing to an exploded war file
rather than just installing a complete war file into Tomcat's webapps
directory. Thinking that there might be other such occasions coming up, I
invented a directory outside of the Tomcat tree to hold such context files and
exploded wars and chose /usr/local/webapps for that directory. My current
application, APLRegistration, appears there, in the subdirectory
aplregistration. In this location I have my context file and also the
exploded war file in a directory named 'exploded'. I.e.,
/usr/local/webapps/
aplregistration/
context.xml
exploded/
<a bunch of jsp files>
WEB-INF/
etc.
That's why the context file points to that exploded directory. I tried
your suggestion, but the app wouldn't work at all then.
This brings up a more general question. Is there a way to use global
datasources with just a war file? After several failed attempts, I finally hit
upon the scheme of using an exploded war file and a context file with the
<ResourceLink> tag. I deploy using the web app manager page and giving
a file: URL pointing to the context file.
But this sounds crazy! Surely there should be some way to just deploy a war
file and still use a global datasource. But how?
Your second suggestion was:
----------------------------------------------------------------------
Two make
<!-- Catch FacesException -->
<resource-ref>
<description>Rave generated DataSource Reference</description>
<res-ref-name>jdbc/APLregistration</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
should be
<!-- Catch FacesException -->
<resource-ref>
<description>Rave generated DataSource Reference</description>
<res-ref-name>jdbc/APLregistration</res-ref-name>
<res-ref-type>javax.sql.DataSource</res-ref-type>
res-ref-type.
----------------------------------------------------------------------
I did that in my web.xml file in the exploded directory (i.e., in
/usr/local/webapps/aplregistration/exploded/WEB-INF/web.xml)
It didn't help. But it didn't hurt either, so I'll leave it. On the other
hand, JSCreator wrote the original web.xml file, as is obvious from the
<description>Rave generated DataSource Reference</description> tag. If I
ever need to change something in JSCreator and rebuild, then I'll have to
re-explode the war and re-edit the web.xml file. I don't know if there's a way
to get into the Creator-generated web.xml file directly and make changes that
will "stick".
> Change these and see if that helps.
No such luck. I still have the situation that after a Tomcat 5.0.28
shutdown/restart, I have to go into the Tomcat admin page, delete the
datasource, and then recreate it. My guess is that something somewhere other
than conf/server.xml must be being changed by the admin interface and that
that something doesn't persist across restarts for some reason. But what and
where?
Thanks again for your interest.
Johnny S. Tolliver
Oak Ridge National Laboratory
[EMAIL PROTECTED], 865-574-1305
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
