Yep, you can't mix client and server interceptors when using the around and
within attributes of @Interceptor.
@Interceptor(type=InterceptorType.CLIENT,
around=AsynchronousInterceptor.class, within =
RollbackInterceptor.class)
SecurityInterceptor is a client interceptor, RollbackInterceptor is a server
interceptor.
Looks like the fix has been made.
In regards to the original problem and how it was fixed, I don't understand
why any interceptor runs for hashCode() and equals(), or at least I would
think it would be a rule to intercept these methods rather than an
exception. I think perhaps the root interceptor should have an opt-in policy
for methods on java.lang.Object.
-Dan
On Mon, Apr 20, 2009 at 4:47 AM, Christian Bauer
<christian.bauer(a)gmail.com>wrote:
A change in 2.1 branch in the last 10 days or so had this effect on
wiki
test run, It's probably Shane's change on SecurityInterceptor r10137 related
to
https://jira.jboss.org/jira/browse/JBSEAM-4003:
[testng] WARN [org.jboss.seam.Component] Interceptor class
org.jboss.seam.security.SecurityInterceptor has different type than within
interceptor class org.jboss.seam.transaction.RollbackInterceptor
[testng] WARN [org.jboss.seam.Component] Interceptor class
org.jboss.seam.security.SecurityInterceptor has different type than within
interceptor class org.jboss.seam.transaction.RollbackInterceptor
[testng] WARN [org.jboss.seam.Component] Interceptor class
org.jboss.seam.security.SecurityInterceptor has different type than within
interceptor class org.jboss.seam.transaction.RollbackInterceptor
[testng] WARN [org.jboss.seam.Component] Interceptor class
org.jboss.seam.security.SecurityInterceptor has different type than within
interceptor class org.jboss.seam.transaction.RollbackInterceptor
[testng] WARN [org.jboss.seam.Component] Interceptor class
org.jboss.seam.security.SecurityInterceptor has different type than within
interceptor class org.jboss.seam.transaction.RollbackInterceptor
[testng] WARN [org.jboss.seam.Component] Interceptor class
org.jboss.seam.security.SecurityInterceptor has different type than within
interceptor class org.jboss.seam.transaction.RollbackInterceptor
[testng] WARN [org.jboss.seam.Component] Interceptor class
org.jboss.seam.security.SecurityInterceptor has different type than within
interceptor class org.jboss.seam.transaction.RollbackInterceptor
[testng] WARN [org.jboss.seam.Component] Interceptor class
org.jboss.seam.security.SecurityInterceptor has different type than within
interceptor class org.jboss.seam.transaction.RollbackInterceptor
[testng] WARN [org.jboss.seam.Component] Interceptor class
org.jboss.seam.security.SecurityInterceptor has different type than within
interceptor class org.jboss.seam.transaction.RollbackInterceptor
[testng] WARN [org.jboss.seam.Component] Interceptor class
org.jboss.seam.security.SecurityInterceptor has different type than within
interceptor class org.jboss.seam.transaction.RollbackInterceptor
[testng] WARN [org.jboss.seam.Component] Interceptor class
org.jboss.seam.security.SecurityInterceptor has different type than within
interceptor class org.jboss.seam.transaction.RollbackInterceptor
[testng] WARN [org.jboss.seam.Component] Interceptor class
org.jboss.seam.security.SecurityInterceptor has different type than within
interceptor class org.jboss.seam.transaction.RollbackInterceptor
[testng] WARN [org.jboss.seam.Component] Interceptor class
org.jboss.seam.security.SecurityInterceptor has different type than within
interceptor class org.jboss.seam.transaction.RollbackInterceptor
...
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.