[
https://issues.jboss.org/browse/WELD-888?page=com.atlassian.jira.plugin.s...
]
Jan Groth commented on WELD-888:
--------------------------------
No exception, the interceptor is simply not executed if defined in EAR\lib (scenario 2).
Code works fine in scenario 1.
(To be more precise: beanManager.resolveInterceptors(...) resolves to Null in scenario 2)
Both scenarios work correctly if I disable separate war-classloading by commenting out the
"WarClassLoaderDeployer" in
deployers/jbossweb.deploy/META-INF/war-deployers-jboss-beans.xml
Interceptors not resolvable from a WAR-module which is part of an
EAR-deployment
--------------------------------------------------------------------------------
Key: WELD-888
URL:
https://issues.jboss.org/browse/WELD-888
Project: Weld
Issue Type: Bug
Components: Interceptors and Decorators
Affects Versions: 1.1.1.Final
Environment: - Weld 1.1.1. Final on JBoss 6.0 GA and JBoss 6.1 nightly
- tested and confirmed on Vista 32 and Linux 64
Reporter: Jan Groth
Attachments: probear-jar.zip, probear.zip
It seems like CDI interceptors cannot be accessed from inside a WAR-module of an EAR
deployment if the interceptor is defined inside a dependent JAR which is located in the
EAR/lib directory.
BUT:
- Managed beans and producers from the same JAR work without problems.
- Moving the dependency from EAR/lib to WAR/WEB-INF/lib makes the interceptor work
without problems.
I consider that a serious problem, because this is a substantial restriction for
enterprise applications.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira