0 Replies Latest reply on Apr 10, 2006 4:21 PM by Kabir Khan

    Failing introduction tests

    Kabir Khan Master

      I've fixed the introduction tests, they didn't have the repository set up, and I made a few other changes to the tests themselves.

      The interceptor handling the introduction was calling invokeNext(), which obviously won't work since the target method does not exisit in the target class, only in the proxy. However, as there can be more than one interceptor handling an invocation, maybe I need another MethodInvocation subclass used for introductions that simply returns at the end of the chain without trying to call the target method?

      The "NotAdvised" and "Advised" test are pretty much the same. I am guessing you would like one where the introduction is done in the bean xml? I don't think we have any nice xml for this yet?