-
1. Re: Hot Deploy Seam Apps on Tomcat?
gavin.king Jul 18, 2006 1:26 PM (in response to davidgeary)It is possible (but fiddly) to set up eclipse to build to an exploded directory structure, and point JBoss to that expolded directory.
-
2. Re: Hot Deploy Seam Apps on Tomcat?
davidgeary Jul 18, 2006 1:32 PM (in response to davidgeary)I'm not familiar with the English adjective "fiddly"--perhaps it comes from the same place that "outjection" comes from. 8-)
Anyway, thanks for the quick response: what you describe is exactly what I'm doing with Tomcat. I've got IDEA set up to create an exploded directory that I access via Tomcat. But it doesn't work.
I'd really like to stick with Tomcat instead of switching to JBoss. Is there any obvious reason why hot deploy should work with JBoss but not with Tomcat? Does it have something to do with embedded EJB?
Thanks,
david geary -
3. Re: Hot Deploy Seam Apps on Tomcat?
gavin.king Jul 18, 2006 1:37 PM (in response to davidgeary)Tomcat hotdeploy is basically completely broken and AFAIK can't be made to work reliably.
http://encarta.msn.com/dictionary_1861673867/fiddly.html -
4. Re: Hot Deploy Seam Apps on Tomcat?
jboss-nth-fan Jul 18, 2006 8:49 PM (in response to davidgeary)"gavin.king@jboss.com" wrote:
Tomcat hotdeploy is basically completely broken and AFAIK can't be made to work reliably.
Sorry for xposting,
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=86515
but can you elaborate more on what it is that badly broken?
Thx -
5. Re: Hot Deploy Seam Apps on Tomcat?
robjellinghaus Jul 28, 2006 1:44 AM (in response to davidgeary)Basically Tomcat just can't reliably shut down a running webapp, because they are sloppy with their classloaders. You wind up with all kinds of static class references that aren't cleaned up properly, and the reloading of your webapp may or may not work. You can get weird ClassCastExceptions post-reloading because the old classloader's classes are still hanging around.
At least that's been my experience....
Cheers,
Rob -
6. Re: Hot Deploy Seam Apps on Tomcat?
christian.bauer Jul 28, 2006 7:54 AM (in response to davidgeary)For future reference in case anybody finds this thread:
public class SomeServlet extends HttpServlet {
private static ClassLoader myClassloader;
public init(ServletConfig cfg) {
myClassloader = getClass().getClassLoader();
}
}
This servlet breaks context reloading in Tomcat, the context leaks a WebappClassloader per reload (and therefore other static variable values, so it can be a lot of memory that is never freed). Since many frameworks (Hibernate, Struts, etc.) use such a pattern, reloading in Tomcat can be considered currently broken.