Re: [Babeldoc-user] re-loading pipeline in web container

[Michael A. <mic...@ze...>]

Hi, Bill,

It's probably for the same reason that the JMX scanner has trouble
reloading configuration.  The configuration is cached in static members,
which means that until the VM is killed (by stopping Tomcat) the caches
don't clear, and the configuration is not refreshed.

I've made a start on this in the 1.3 branch, but there is still quite a
bit of work to do.  For the moment, unless anybody else has another
suggestion, I think you're stuck with restarting Tomcat.  Does Tomcat
have a way of restarting the classloader for a context?  If you can get
the classloader to restart without restarting Tomcat, then it should
clear the config info (I'm assuming here that Tomcat gives different
application contexts their own classloaders).

Cheers...


MikeA





On Fri, 2003-12-05 at 21:34, Bill Harrelson wrote:
> Hi all,
> 
> I'm trying to get a pipeline running under Tomcat (as some of you 
> know from my request for help).
> 
> 
> Is there any way to reload the pipeline for the SOAPListener (which I 
> have heavily modified) without having to stop and restart Tomcat?
> 
> I tried reloading the servlet context with the Tomcat manager, but that 
> didn't seem to work.  It's a bit of a pain having to stop and re-start all 
> the time and I can't offhand figure out why reloading the context 
> doesn't work.
> 
> Thanks in advance.
> 
> Bill
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Babeldoc-user mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-user