Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: conflict two aop and mvc:annotation-driven

  1. #11
    Join Date
    Jun 2005
    Posts
    4,241

    Default

    OK, that's a little clearer, but you still didn't say what the problem is really. Most of the problems I listed in my first response are still there, though, so maybe you should clean things up a bit before we go any deeper. A lot of weirdness will go away if you remove the extra ConetxtLoaderListener, but that won't get you to a working app until you fix the other stuff. For instance, if you use ContextLoaderListener to load your security context you need to use the default Spring Security filter configuration.

  2. #12
    Join Date
    Mar 2012
    Posts
    10

    Default

    If I use <mvc:annotation-driven /> in my app,it will cann’t get aop intercept log.If I note, aop will get intercept log.This is the problem in my app.Thaks….

  3. #13
    Join Date
    Mar 2012
    Posts
    10

    Default

    I removed my first ContextLoaderListener ,But the problem remain.

  4. #14
    Join Date
    Jun 2005
    Posts
    4,241

    Default

    OK, so did you fix the other problems? The <mvc:annotation-driven/> has to go in the servlet context, which you haven't defined unless I'm missing something, and the security filter needs its default settings (so remove the <init-param/>). You might be better off asking in the Spring Security or Spring MVC forums for general help on how to set up a Spring Security app with MVC, then come back here when you need more help with the OAuth filters.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •