This content has been marked as final.
Show 4 replies
-
1. Re: client interceptor - ejb3-interceptors-aop.xml
alrubinger Nov 24, 2008 10:20 AM (in response to torstenknopp)JBossAS / EJB3 Version? Stack trace?
Client interceptors, on invocation, must be available on the client's CP.
S,
ALR -
2. Re: client interceptor - ejb3-interceptors-aop.xml
torstenknopp Nov 24, 2008 10:41 AM (in response to torstenknopp)In EJB2.1 and JBoss 4.0.x I put it on Client's CP and added the Interceptor in standardjboss.xml or jBoss.xml.
But in EJB3 and JBoss4.2.x the ClientInterceptor must be availiable on Servers CP when I add the new ClientInterceptor-Class in ejb3-interceptors-aop.xml in delopy directory!
Is there another way to define an new Client-Interceptor as in ejb3-interceptors-aop.xml? -
3. Re: client interceptor - ejb3-interceptors-aop.xml
alrubinger Nov 24, 2008 10:52 AM (in response to torstenknopp)There's not much we can do about Community AS 4.2.x.
In current trunk I see your problem:10:47:58,654 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} StatelessSessionClientInterceptors -> StatelessSessionClientInterceptors$4{Configured:Instantiated} StatelessSessionClientInterceptors$4 -> com.alrubinger.Test{Configured:** NOT FOUND Depends on 'com.alrubinger.Test' **} *** CONTEXTS IN ERROR: Name -> Error com.alrubinger.Test -> ** NOT FOUND Depends on 'com.alrubinger.Test' **
Though this isn't really within the EJB3 domain; this file's processed by the AOP AspectManager and I'll have to ask AOP team why these classes declared on the stack must be available immediately.
Please raise an EJBTHREE JIRA and I'll dig around.
S,
ALR -
4. Re: client interceptor - ejb3-interceptors-aop.xml
alrubinger Nov 24, 2008 11:05 AM (in response to torstenknopp)Addressed on AOP User's Forum:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191805
S,
ALR