[
https://issues.jboss.org/browse/CDI-702?page=com.atlassian.jira.plugin.sy...
]
Matej Novotny commented on CDI-702:
-----------------------------------
From the comments I gather that people agree on current spec
interpretation (that extensions are now allowed to observe everything) and the discussion
is about changing that in spec.
However, if we do that and twist it the other way around, you can then come back saying we
_obviously failed_ by imposing unnecessary restrictions on extension observers.
I am pretty sure other users would come back saying they have _real world problem_ because
they now cannot observe events "globally" where they previously could (say hello
to backwards compat. problems).
To me it seems like it's just going one way or the other but you can always complain
that the opposite should be go-to option...
Besides I see current wording and interpretation as better because it allows you to
integrate on a wider scale; being able to observe events from other WARs can be handy.
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.
e.g.
myApp.ear
lib\myLib.jar (LibExtensionA.class, LibOne.class)
myWarA.war (WarAExtension.class, myWarAServlet.class)
myWarB.war (WarBExtension.class, myWarBServlet.class)
In this example,LibExtensionA, WarAExtension and WarBExtension can observe the classes of
LibOne, myWarAServlet and myWarBServlet.
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.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)