-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Folks,

feeling kinda ashamed asking such a (probably rather basic) question,
but nevertheless: By now, I only built applications packed to *.war
files and then thrown to a tomcat /webapps/ folder, which obviously
made / makes tomcat redeploy the application - so far, so good.

However, in order to get a JDBC resource set up and running, I added a
context definition like this ...


<Context path="/jdbclink" reloadable="true">
...
          <Resource name="jdbc/SQLDB" auth="Container" ... />
...
</Context>


... and then dumped in a jdbclink.war file. Deployment works fine the
very first time, and then never again. :o Even worse, removing the
webapps/jdbclink/ folder while the container is running doesn't make
tomcat unpack / redeploy the .war file. Likewise, even placing a new
war file in webapps and restarting the container doesn't do - I have to
stop tomcat and manually remove the unpacked web application in webapps
to get the war redeployed again. Haven't messed with any other
settings so far, the Host declaration looks like this...


      <Host name="localhost" appBase="webapps"
       unpackWARs="true" autoDeploy="true"
       xmlValidation="false" xmlNamespaceAware="false">


We're talking tomcat 5.5.20 atop Ubuntu/JDK 1.6 here. Can anyone
enlighten me why in this configuration tomcat doesn't redeploy the
application when having a new war file dropped to webapps (by removing
the Context definition from server.xml, this does work again...)? It's
not all _that_ bad the way it is now, but having to shut down tomcat
and manually remove the webapp to get it redeployed is not that fine on
a production system running more than just that very application. :)

Thanks in advance and bye,
Kristian



- -- 
Kristian Rink * http://zimmer428.net * http://flickr.com/photos/z428/
jab: [EMAIL PROTECTED] * icq: 48874445 * fon: ++49 176 2447 2771
"One dreaming alone, it will be only a dream; many dreaming together
is the beginning of a new reality." (Hundertwasser)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGMJBJcxBAPOA1m6wRAsJjAJ9HigISz9g/4YdZ1Mv2rw+7EBt21wCbBGp+
myjQt53ccWBHayGdXzCiG5U=
=fKcF
-----END PGP SIGNATURE-----

Reply via email to