[
https://jira.jboss.org/jira/browse/WELDSE-25?page=com.atlassian.jira.plug...
]
Pete Muir commented on WELDSE-25:
---------------------------------
Yes, this was the exact intent of providing a pluggable ResourceLoader. Can you describe
how you are trying to specify the service?
Pete R, we should reuse the ResourceLoader stuff when doing reflections in Weld SE.
Morten, can you describe why you want to pass a CL to the Weld class?
Weld SE ignores org.jboss.weld.resources.spi.ResourceLoader
-----------------------------------------------------------
Key: WELDSE-25
URL:
https://jira.jboss.org/jira/browse/WELDSE-25
Project: Weld support for Java SE
Issue Type: Bug
Affects Versions: 1.0.1.Final
Environment: Weld SE + Java 6
Reporter: Morten Christensen
Priority: Critical
According to the docs "org.jboss.weld.resources.spi.ResourceLoader" is
responsible for resource loading/class creation and if it worked it would appear to solve
a lot of potential integration problems, f.x. with OSGI (see issue 520).
Unfortunately, Weld SE does not apper to use ResourceLoaders and it ignores any
implementations of this service that the Java SE app supplies. Even worse, Weld SE
classloading behavior is hardcoded in
"org.jboss.weld.environment.se.util.Reflections". This makes it impossible to
use Weld SE where classloading does not work with the Thread's context class loader
such as OSGI etc.
Weld SE should be changed to look for service implementations of
"org.jboss.weld.resources.spi.ResourceLoader" (i.e. actually work according to
its own documentation).
P.S: It would also be nice if Weld SE would allow users to supply a Classloader to the
constructor for org.jboss.weld.environment.se.Weld
--
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