[JBoss JIRA] Created: (WELD-520) Weld does not work in OSGI container's classloader (and lacks OSGI bundles by the way)
9:50 p.m.
Weld 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
Priority: Critical
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
10:04 p.m.
New subject: [JBoss JIRA] Updated: (WELD-520) Weld 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...
]
Pete Muir updated WELD-520:
---------------------------
Priority: Major (was: Critical)
Weld 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
10:04 p.m.
New subject: [JBoss JIRA] Updated: (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...
]
Pete Muir updated WELD-520:
---------------------------
Summary: Weld SE does not work in OSGI container's classloader (and lacks OSGI
bundles by the way) (was: Weld does not work in OSGI container's classloader (and
lacks OSGI bundles by the way))
Please note that Weld itself does work with OSGi and does have an osgi bundle.
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
10:19 p.m.
New subject: [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
5:28 a.m.
New subject: [JBoss JIRA] Updated: (WELD-520) Weld SE does not work in OSGI container's classloader (and lacks OSGI bundles by the way)
[
https://jira.jboss.org/browse/WELD-520?page=com.atlassian.jira.plugin.sys...
]
Pete Muir updated WELD-520:
---------------------------
Fix Version/s: 1.1.0.Beta2
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/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
Fix For: 1.1.0.Beta2
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:57 p.m.
New subject: [JBoss JIRA] Updated: (WELD-520) Weld SE does not work in OSGI container's classloader (and lacks OSGI bundles by the way)
[
https://jira.jboss.org/browse/WELD-520?page=com.atlassian.jira.plugin.sys...
]
Pete Muir updated WELD-520:
---------------------------
Fix Version/s: 1.1.0.CR1
(was: 1.1.0.Beta2)
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/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
Fix For: 1.1.0.CR1
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:25 a.m.
New subject: [JBoss JIRA] Updated: (WELD-520) Weld SE does not work in OSGI container's classloader (and lacks OSGI bundles by the way)
[
https://jira.jboss.org/browse/WELD-520?page=com.atlassian.jira.plugin.sys...
]
Pete Muir updated WELD-520:
---------------------------
Component/s: Java SE Support
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/browse/WELD-520
Project: Weld
Issue Type: Bug
Components: Java SE Support, OSGi support
Affects Versions: 1.0.1.Final
Environment: Java SE, Weld 1.01 SE, Felix 2.02
Reporter: Morten Christensen
Fix For: 1.1.0.CR1
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:39 a.m.
New subject: [JBoss JIRA] Updated: (WELD-520) Weld SE does not work in OSGI container's classloader and lacks OSGI bundles
[
https://issues.jboss.org/browse/WELD-520?page=com.atlassian.jira.plugin.s...
]
Pete Muir updated WELD-520:
---------------------------
Summary: Weld SE does not work in OSGI container's classloader and lacks OSGI
bundles (was: Weld SE does not work in OSGI container's classloader (and lacks OSGI
bundles by the way))
Weld SE does not work in OSGI container's classloader and lacks
OSGI bundles
----------------------------------------------------------------------------
Key: WELD-520
URL: https://issues.jboss.org/browse/WELD-520
Project: Weld
Issue Type: Bug
Components: Java SE Support, OSGi support
Affects Versions: 1.0.1.Final
Environment: Java SE, Weld 1.01 SE, Felix 2.02
Reporter: Morten Christensen
Fix For: 1.2.0.Beta1
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:49 p.m.
New subject: [JBoss JIRA] Updated: (WELD-520) Weld SE does not work in OSGI container's classloader and lacks OSGI bundles
[
https://issues.jboss.org/browse/WELD-520?page=com.atlassian.jira.plugin.s...
]
Ales Justin updated WELD-520:
-----------------------------
Fix Version/s: 1.2.0.Beta1
(was: 1.1.1.Final)
Weld SE does not work in OSGI container's classloader and lacks
OSGI bundles
----------------------------------------------------------------------------
Key: WELD-520
URL: https://issues.jboss.org/browse/WELD-520
Project: Weld
Issue Type: Bug
Components: Java SE Support, OSGi support
Affects Versions: 1.0.1.Final
Environment: Java SE, Weld 1.01 SE, Felix 2.02
Reporter: Morten Christensen
Fix For: 1.2.0.Beta1
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:37 p.m.
New subject: [JBoss JIRA] Updated: (WELD-520) Weld SE does not work in OSGI container's classloader and lacks OSGI bundles
[
https://issues.jboss.org/browse/WELD-520?page=com.atlassian.jira.plugin.s...
]
Ales Justin updated WELD-520:
-----------------------------
Fix Version/s: TBC
(was: 1.1.2.Final)
Weld SE does not work in OSGI container's classloader and lacks
OSGI bundles
----------------------------------------------------------------------------
Key: WELD-520
URL: https://issues.jboss.org/browse/WELD-520
Project: Weld
Issue Type: Bug
Components: Java SE Support, OSGi support
Affects Versions: 1.0.1.Final
Environment: Java SE, Weld 1.01 SE, Felix 2.02
Reporter: Morten Christensen
Fix For: TBC
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4675
days inactive
5112
days old
9 comments
3 participants
participants (3)
-
Ales Justin (JIRA) -
Morten Christensen (JIRA)
-
Pete Muir (JIRA)