[weld-issues] [JBoss JIRA] Commented: (WELD-520) Weld SE does not work in OSGI container's classloader (and lacks OSGI bundles by the way)
[
https://jira.jboss.org/jira/browse/WELD-520?page=com.atlassian.jira.plugi...
]
Morten Christensen commented on WELD-520:
-----------------------------------------
What do you mean that Weld itself does work with OSGi ? If I create and OSGI bundle, and
start weld SE inside it to wire my classes inside, I will get this error so I can't
see how Weld should support OSGI unless there are a third Weld-OSGI runtime in addition to
Weld SE and Weld EE that I do not know about ?
As for bundles, are you talking about "weld-osgi-bundle-1.0.1-Final.jar" which
can be found in glassfish?
1. It does not contain Weld SE features !
2. Is there anything else special about it ?
Weld SE does not work in OSGI container's classloader (and lacks
OSGI bundles by the way)
-----------------------------------------------------------------------------------------
Key: WELD-520
URL: https://jira.jboss.org/jira/browse/WELD-520
Project: Weld
Issue Type: Bug
Components: OSGi support
Affects Versions: 1.0.1.Final
Environment: Java SE, Weld 1.01 SE, Felix 2.02
Reporter: Morten Christensen
Weld SE will does not work inside an OSGI bundle. If you try to start WeldSE from within
a OSGI bundle, you will get.
Error loading Weld bootstrap, check that Weld is on the classpath
at org.jboss.weld.environment.se.Weld.<init>(Weld.java:59)
Looking at the cause, it seems org.jboss.weld.environment.se.util.Reflections only works
with Thread context classloaders and plain Class.forname both of which are NO-NO in osgi.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira