Databases
StackOverflow2013
Postsdbo
POSpring HandlerMethodArgumentResolver not executing
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSpring HandlerMethodArgumentResolver not executing
    primarykey
    data
    text
    <p>I am using Spring MVC 3.2.2</p> <p>I have defined a custom HandlerMethodArgumentResolver class like this</p> <pre><code>public class CurrentUserArgumentResolver implements HandlerMethodArgumentResolver { public CurrentUserArgumentResolver() { System.out.println("Ready"); } @Override public boolean supportsParameter(MethodParameter parameter) { return parameter.hasParameterAnnotation(CurrentUser.class); } @Override public Object resolveArgument(MethodParameter parameter, ModelAndViewContainer mavContainer, NativeWebRequest webRequest, WebDataBinderFactory binderFactory) throws Exception { Principal principal = webRequest.getUserPrincipal(); System.out.println("*** Principal ***: " + principal); return principal; } } </code></pre> <p>And added the following to my app-servlet.xml</p> <pre><code>&lt;mvc:annotation-driven&gt; &lt;mvc:argument-resolvers&gt; &lt;beans:bean class="my.package.CurrentUserArgumentResolver" lazy-init="false"/&gt; &lt;/mvc:argument-resolvers&gt; &lt;/mvc:annotation-driven&gt; </code></pre> <p>and created an annotation for CurrentUser</p> <pre><code>@Target(ElementType.PARAMETER) @Retention(RetentionPolicy.RUNTIME) public @interface CurrentUser { } </code></pre> <p>When I start the application up the class is constructed as I can see the log message "Ready" but the resolver does not execute when I annotate a controller method as such (in a class that has @Controller annotation)</p> <pre><code>@RequestMapping(method = RequestMethod.POST, value = "/update") public ModelAndView update(@RequestParam MultipartFile background, @CurrentUser Principal principal) { ... } </code></pre> <p>If I put breakpoints on either method in the CurrentUserArgumentResolver class, neither work. So not sure what I am missing?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UStereško
    1. USAyub Malik
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSpring HandlerMethodArgumentResolver not executing
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSpring HandlerMethodArgumentResolver not executing
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIt look's exactly like my answer at this question: http://stackoverflow.com/questions/8764545/best-practice-for-getting-active-users-userdetails/8769670#8769670 - I can't see any mistake in the posted code. So maybe the problem is somewhere else: check that everything complies and is deployed correctly. Check that there is only one MVC:anotationdriven. Check that the controller beam is only found by the component scan from the app-servlet.xml
      singulars
      1. POSpring HandlerMethodArgumentResolver not executing
      1. USRalph
    2. COYes my code was based on a combination of your answer and Spring docs. All the code compiles and the controller method is called correctly, its just that the principal is null. I would at least expect the breakpoint on the 'supportsParameter' to be called.
      singulars
      1. POSpring HandlerMethodArgumentResolver not executing
      1. USAyub Malik
    3. COWhat is the value of the controller method parameter (principal)? Is it null?
      singulars
      1. POSpring HandlerMethodArgumentResolver not executing
      1. USRalph
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload