Judging by the commented out line in AcegiWorker:
//transformation.renameAndExtendMethod(method, newMethodName,
methodBody.toString());
I'm guessing there is an issue with renaming and extending the method. Did
that method exist at one point and suddenly go away or has method security
never been functional? I was able to somewhat get things to work by doing:
transformation.prefixMethod(method,
"System.out.println(\"PREFIX!!!!!\");\n"+
"org.acegisecurity.intercept.InterceptorStatusToken token =
"
+ interField + ".checkBefore(" + configField + ");\n");
The problem with that is that the checkAfter is never invoked. For my test
application I didn't see any negative ramifications of that, but I'm
guessing it was there for a reason.
I was also able to hack it to get the checkAfter in there as well, but then
the Tapestry injection mechanism stopped working for the methods that get
moved and replaced with the instrumented security method. If interested, I
can send you my hack... If you have other specific issues you have
encountered, let me know and I'll try to take a look.
Robin Helgelin wrote:
>
> Thanks. I've began working on this, but I got stuck and haven't had
> much time to look at it. I'll try to get time to work on it.
>
> --
> regards,
> Robin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/T5-5.0.10-Acegi-doesn%C2%B4t-work-tp15454642p15571323.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
