Results 1 to 3 of 3

Thread: Upgrading to Spring 2.0.1 changed application of pointcut

  1. #1
    Join Date
    Aug 2005
    Posts
    21

    Default Upgrading to Spring 2.0.1 changed application of pointcut

    After I upgraded to Spring 2.0.1, a pointcut that I had defined and working in Spring 2.0 changed behavior. I had the following pointcut:

    <pointcut id="checkLoggedInPointcut" expression="execution(public * com.mycompany.MyBaseClass+.*(..)) AND !execution(public * com.mycompany.ClassThatExtendsBaseClass.*(..))"/>

    An aspect that uses this pointcut is applied to all methods of all classes that extend MyBaseClass and should exclude all methods in only the single class ClassThatExtendsBaseClass.

    This was working fine in Spring 2.0. Do I need to change the way I have defined my pointcut to get it to work in Spring 2.0.1? (I upgraded to Spring 2.0.1 to get some additional ehcache enhancements).

    Thanks,
    Anthony

  2. #2
    Join Date
    Jun 2006
    Location
    SF Bay Area, California
    Posts
    524

    Default

    What's the new behavior in 2.0.1 you see?

    -Ramnivas
    Ramnivas Laddad (Follow me on Twitter)
    AspectJ in Action: Enterprise AOP with Spring Applications (2nd edition). Now available!

  3. #3
    Join Date
    Aug 2005
    Posts
    21

    Default

    The new behavior is that the checkLoggedInPointcut pointcut is applied to the class ClassThatExtendsBaseClass when it should not be. Sorry, I should have mentioned that.

    Thanks,
    Anthony

Posting Permissions

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