Not sure what you are asking.
In sever.xml you have various contexts or webapps
If you set reloadable to true the classloader when tomcat
restarts (the key word is restarts - you must stop then restart tomact)
checks to see if changes are made to the .class files. If they are then they
are reloaded into main memory. If this is wrong then someone correct
me please. P.S. You probably already know this and your question
is about connection pooling - if so clarify.
<Context path="/myapps"
docBase="webapps/myapps"
crossContext="false"
debug="0"
reloadable="true" > ******* This works!*******
</Context>
----- Original Message -----
From: "Senthil Vaiyapuri" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 02, 2001 12:36 PM
Subject: Reloading .. Wassup ?
> Kindered Folks:
>
> What is up with Servlet Reloading servlets Tomcat. Anybody doing
> some
> serious servlet app. development needs auto reloading on. (in dev
> environments, just
> for the sake of webadmins sanity in the least :-)) Vanilla apps,
> without the
> need to share (prestarted, preloaded) common objects
> (ConnectionPool, SessionPool etc.) seems
> to be OK. Has anybody made it work ? Any help is appreciated.
>
> We tried putting the SessionPool, ConnectionPool etc. in a non
> reloadable
> app. as mentioned in one of the mails in the list, but it did'nt
> help also.
>
> Is this going to be fixed any time soon ?
>
> Thanks for your help.
> -senthil
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
