|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I don't think it's a completely separate concern. Again, in this scenario OWB registers/instantiates a Weld-specific CDI extension which expects Weld to be initialized (seems logical to me). Afterwards when OWB delivers AfterBeanDiscovery event the invocation of registerWeldSEContexts() method fails and this results in definition error per the spec. So Weld is not "listening" at all. There's just an extension component on the classpath and OWB picks it up (also seems logical to me). Unfortunately this component requires Weld container. So my assumption is: if a module with OWB has an isolated classloader, is wouldn't see Weld classes.