Nov 26th, 2007, 06:32 PM
No "hot deploy" capability for @Controller?
Hello. I am working with Spring 2.5 and the new @Controller annotation. I've gotten everything to work fine, but I had a question about how often any changes to the class are detected?
When using Spring MVC 2.0 in the past, I would make a change to my controller class, and through the MyEclipse Web Application builder, my changes would automagically be deployed to Tomcat. In this way, I would see my changes to my controller method immediately by making a new request to the controller via the browser.
However, when using the new @Controller stereotype, when I make a change to my class and issue a new request in this manner, I do not see my changes. I do see my changes if I stop and start Tomcat however.
Is there something about @Components, etc. that does not allow for a reloading/recompiling of the controller class to be seen by Spring?
Looking for guidance please. And congrats on the new release Spring team!