> > Live class reloading is a great feature. >> But I couldn't figure out yet how one should configure, for example, >> Tomcat 6 in development environment to avoid redeployments after each and >> every >> change in the code. Are there any solutions? >> > > Use Jetty instead: faster, simpler, more modular. :) Take a look at the > reloadable attribute in the Context tag. Try making your context not > reloadable. >
I'm totally OK with Jetty, but it demonstrates pretty the same behavior if running inside Eclipse IDE server adaptor. Probably I'm missing something obvious? -- Ilya Obshadko
