]
John Ament commented on CDI-702:
--------------------------------
The description of this issue is unclear. Are you seeing all events being fired or only
certain events? Where in the archive is the extension registered, a JAR within the
EAR's lib folder? Within the WAR file? Within a library within the WAR file?
Observers in CDI extensions can see classes they should not be able
to
----------------------------------------------------------------------
Key: CDI-702
URL:
https://issues.jboss.org/browse/CDI-702
Project: CDI Specification Issues
Issue Type: Clarification
Components: Portable Extensions
Affects Versions: 1.2.Final, 1.1.Final, 2.0 .Final
Reporter: Emily Jiang
Priority: Critical
We observe a undesired behavior on Weld, which is during CDI bootstrap, all classes from
both the EAR lib folder and all WAR lib folders are available to CDI extensions in the EAR
lib folder as well as to CDI extensions in all WAR lib folders. Basically, the extension
class can see everything in an .ear regardless where the extension class resides. It
completely ignores classloading hierarchy.
This kind of contradicts with the classloading rules, where separate .war archives
packaged under the same .ear should not be able to see each other's class by default,
unless they both use the same classloader.
We discussed with Weld dev team (Martin, Thomas, Matej) and Anotine. The feedback is that
CDI spec is unclear on the "observer resolution". I would like to relaunch the
discussion to make this clarified and fixed. Please comment.