[krausest]

Sorry for being slightly off topic. I’d like to know which Appserver works – in your opinion – best with the development model of myeclipse regarding hot deployment (code replace for a running web app). I’m looking forward to hearing your experiences.

[dkittle]

I’ve had pretty good luck with Resin by Caucho (www.caucho.com). It picks up JSP changes no problem (but you have to wait until after the auto-rebuild in Eclipse before you refresh) and although there is a warning when you publish a class with a different interface, you can simply click continue and keep working. I havn’t quite got a good process down for Resin picking up property file changes (likely ‘touching’ web.xml would suffice) and I think you need to turn on session persistence of some sort in any container you work with or you’ll be logging in time and time again.

[krausest]

Thanks for your anwser (Though I couldn’t make my app work with Resin and gave up when the documentation drove me nuts…)

Obviously some application server are able to reload classes in cases where the debugger can’t replace the code (e.g. changes in the signature).
I had it working nicely on weblogic 8.1 where I’ve worked for hours without restarting the server.

On the other hand JBoss 4.0 doesn’t reload my classes (maybe unless I touch a deployment descriptor). Does anyone know in this special case how to enable automatic class reloading?

Other application server have even worse problems. For Websphere or Jonas it seems as if you’d have to invoke some stub compiler when the signature of an EJB changes…

[Author]

Posts