Failed to publish web application: problem with SpringSource Tool Suite?

Question

I have an existing, fully functional Spring 2.5.6 based Web application - developed using the SpringSource Tool Suite 2.1.0.SR1.

Because I would like to use REST, I decided to upgrade to Spring 3.0.0.M4. After editing the dependencies in pom.xml and changing my code to reflect the API changes in Spring 3.0, I tried to publish my web application on a local server (SpringSource tc - Tomcat derivation).

The result is an almost empty web application folder, and therefore a non-functional application. The application folder contains only WEB-INF/lib with all the libraries required for Maven dependencies.

Realizing that something was broken, I created a new Spring MVC project (based on the default 2.5.6) and published it on the same server. No problems. I tried to adapt my project files ( .settings/* , .project , .classpath , .springBeans ), but that didn't change anything.

I'm lost right now. I assume that STS does not correctly handle 3.0 applications. Any suggestions?

PS: I do not want to return to 2.5, if this is not absolutely necessary. I do not need STS and tc, so I have no problems using other tools, but so far it has worked fine.

Answer 1

The problem has disappeared with newer versions of STS. Also, my development environment has changed a bit since I posted this question, so I can't say what caused the problem. To me, it looked like a weird hiccup inside STS.

Answer 2

I come across this all the time using Eclipse Galileo and m2eclipse 0.9.8 and Tomcat with WTP. I think this is a criminal. The problem is switching from Ganymede. The work around is to run mvn to create a war, and then copy the contents of the war from "target" to the WTP directory "wtpwebapps". You can easily find this terribly long way by double-clicking on the server in the "Servers" view and selecting "Open launch configuration", from there click on the "Arguments (?)" Tab, and I think that copy the java property of the .home catalina, which is defined as an argument is.

Answer 3

Spring Tool Suite 2.1.0 requires partial support for Spring 3.0, although not for REST features. According to the release, future releases will provide full support. From the statement of issue:

Functions

Support for Spring 3.0 milestones, including editing and XML validation, support for @Configuration and @Bean annotations

Future

Full support for Spring 3.0, including RESTful web development tools

Answer 4

Try installing the application on the built-in pier. "mvn jetty: run", with which you confirm that there is nothing wrong with your assembly (that all the correct manifestations and depots are in place)