Re: [aspectj-users] ReflectionWorld.resolve(String) and Dynamic Proxy Cl

[Andy Clement <andrew.clement@xxxxxxxxx>]

Hi Jens,

I wasn't aware of that spring aop forum post (there are too many forums to track...). If either you or Dustin comes up with a testcase I can take a proper look at the situation.  There was a lot of change that went in around 1.6.7 (although 1.6.7 itself wasn't a great build, 1.6.8 was released pretty soon after to address some issues).  I probably wouldn't recommend attempting to turn off fast matching as running the old matching algorithms isn't really supported (and no testing is done to confirm the old matching algorithms still work in more recent builds).

cheers,

Andy

On 7 January 2013 22:34, jborrmann <Jens.Borrmann@xxxxxxxxxxxxxxxx> wrote:

Hi Andy and Dustin,

interesting that you stumbled upon the same issue as we did (see
http://forum.springsource.org/showthread.php?95314-ReflectionWorldExpression-when-upgrading-Aspectj).
If I understand your description right, you are also not only confronted with an
irritating error message but with spring contexts not being initialized, right?

Cheers,
Jens

_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users