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
Given the following code: @Controller @RequestMapping(param="ex")
public class BookController {
@RequestMapping
public void index() { }
@RequestMapping(param="id")
public void show() { }
}
one would expect that in order to invoke either request mapping that an "ex" parameter woud need to be present in the request. so /book/index?ex=a or /book/show?id=1&ex=a . however testing this out, the param requires are as expected for the show method... however a simple /book/index works without a parameter on the index. As I think this through, it is the only default request mapping, however given the restriction on the type shouldn't this request fail with no matching mapping?
Affects: 3.0 M1
The text was updated successfully, but these errors were encountered:
The primary problem was that for non-singleton controllers, the checking of type-level constraints was accidentally bypassed. It should work consistently now as of 3.0 M2.
Ken Sipe opened SPR-5421 and commented
Given the following code:
@Controller
@RequestMapping
(param="ex")public class BookController {
}
one would expect that in order to invoke either request mapping that an "ex" parameter woud need to be present in the request. so /book/index?ex=a or /book/show?id=1&ex=a . however testing this out, the param requires are as expected for the show method... however a simple /book/index works without a parameter on the index. As I think this through, it is the only default request mapping, however given the restriction on the type shouldn't this request fail with no matching mapping?
Affects: 3.0 M1
The text was updated successfully, but these errors were encountered: