well, i didn't really expect an answer.
here is a quick and dirty example.
when i first start it all works fine.
after reload the doen't work. -> logs
g.
"Craig R. McClanahan" wrote:
> gustav spellauge wrote:
>
> > "Craig R. McClanahan" wrote:
> >
> > > gustav spellauge wrote:
> > >
> > > > thanks,
> > > >
> > > > that's what i thught but now i can be quit shure.
> > > >
> > > > do you think/know if tmcat 4.x will support hotswapping of all dependencies ?
> > > >
> > >
> > > Tomcat 4.0 supports autoreload when any class (not just a servlet) is updated, as
> > > long as that class is unpacked in WEB-INF/classes. There is a background thread
> > > that checks for updates, by default every 15 seconds.
> > >
> >
> > i just tried tomcat 4.0b1 it starts up fine but doesn't fix the restart problem.
> >
>
> Well, it works for me and lots of other folks. Can you provide a reprodicible test
> case, along with error message logs, so we can investigate?
>
> >
> > >
> > > Instead of the admin application of 3.2, there is also a manager application in
> > > 4.0 that can trigger a reload with a single request:
> > >
> > > http://localhost:8080/manager/reload?path=/myapp
> > >
> > > where "/myapp" is the context path of the application you want to reload. This
> > > works even if "autoreload" is not set on the app in server.xml, so you might find
> > > it faster to trigger reloads this way. The only thing needed to make it work is
> > > to create a user in conf/tomcat-users.xml that has the role "manager" -- you will
> > > be challenged the first time you reload for the username/password, but after that
> > > you will just need to submit.
> > >
> >
> > this does NOT work for me !
> >
>
> Again, "this does NOT work for me" gives no basis on which we can investigate. What
>are
> your configuration files set up like? What did you try? What actually happened?
>What
> did you expect to have happen? What do the log files say?
>
> Craig
Test.tgz
