You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we have the following configuration, that works fine with dm-server 1.0.1 (spring 2.5.6), but fails with dm-server-ee-1.0.1 (imported lib org.springframework.spring.instrumented)
class com.foo.api.FooController
@Controller("fooController")
public class FooController extends MultiActionController implements HandlerExceptionResolver {
@RequestMapping("/name")
public ModelAndView listTags(@RequestParam(required=false, value="aVar") String aVar) {
....
/name was not resolved
[2008-12-16 18:54:50.351] TP-Processor2 org.springframework.web.servlet.PageNotFound.unknown W No mapping found for HTTP request with URI [/name] in DispatcherServlet with name 'foo-DispatcherServlet'
currently i am uncertain, if it is false configuration on our side, a dm-server bug or springframework issue, so creating this issue here first
Affects: 2.5.6
The text was updated successfully, but these errors were encountered:
I cannot reproduce this against Spring 3.0 M3, at least not for the "implements HandlerExceptionResolver" case. This works just fine. It does not work, however, when extending MultiActionController! This is indicating the wrong kind of contract... An @RequestMapping-based controller should never extend that base class. Have you actually tried the case where you implement HandlerExceptionResolver but do not extend MultiActionController? If you can reproduce this against Spring 3.0 M3 (e.g. on plain Tomcat), let me know.
Thomas Koeppen opened SPR-5366 and commented
we have the following configuration, that works fine with dm-server 1.0.1 (spring 2.5.6), but fails with dm-server-ee-1.0.1 (imported lib org.springframework.spring.instrumented)
application-web.xml
/name was not resolved
currently i am uncertain, if it is false configuration on our side, a dm-server bug or springframework issue, so creating this issue here first
Affects: 2.5.6
The text was updated successfully, but these errors were encountered: