On Thu, 15 Nov 2001, David Jencks wrote: > 3. (with jars separate, not in jetty.sar, just a plain jetty-service.xml) > Remove the out of date jar, jetty-service.xml will suspend all its mbeans, > redeploy new jar, jetty-service.xml will automatically redeploy all its > mbeans. This is supposed to work now, although I haven't tested it > extensively with the new mbean-refs in place. If you try and find it > doesn't work PLEASE let me know. I think at the moment just copying a new > jar over the old one doesn't work-- IMHO notifying to undeploy old version > and redeploy new version is the job of the autodeployer, but I haven't had > a chance to update it yet. It is also possible that you have to explicitly > undeploy the old jar with the ServiceDeployer.
For 2.4.3, I had a symlnk from the deploy folder, into my build directory, at the jar that is created. When I would update said jar, jboss would undeploy then redeploy automatically. I hope this feature hasn't gone away. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
