bmuschko/gradle-tomcat-plugin — Issue #14: tomcatRun and Spring's @RequestMapping
Author: djKianoosh
Created: 2011-12-17 21:58:44+00:00
State: open

First of all, great plugin!

I thought you should know of a problem I'm having with the tomcatRun task and a Spring based Controller annotated with @RequestMapping that doesn't seem to get spun up right.

I'm playing with this [spring-backbone example](https://github.com/djKianoosh/spring-backbone-todo/tree/gradle-build) which had a maven build. I converted it over to a gradle build and everything works nice with gradle war and deploying the war manually to tomcat. It's a very simple todo app. When using your plugin, tomcatRun does run the main webapp under localhost:8080/todo, but there's another config in the [TodoController](https://github.com/djKianoosh/spring-backbone-todo/blob/gradle-build/src/main/java/org/resthub/todo/TodoController.java) that gets configured like this:

```@Controller @RequestMapping("/api/todo")
public class TodoController {
```
So this should be available at http://localhost:8080/todo/api/todo but it doesn't get wired up properly when using gradle tomcatRun. Like I said it does work with gradle war and deploying it to tomcat manually. Would be nice for tomcatRun to work though

FYI I run it with --info and --stacktrace but there's no exception. Running it with --debug has crazy neverending amounts of output in the console. That would take longer :)