[weld-issues] [JBoss JIRA] Updated: (WELD-520) Weld SE does not work in OSGI container's classloader and lacks OSGI bundles

[Ales Justin (JIRA)]

     [ https://issues.jboss.org/browse/WELD-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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