[JBoss JIRA] Created: (WELD-311) Producer field behavior differs from producer method
by alberto Gori (JIRA)
Producer field behavior differs from producer method
----------------------------------------------------
Key: WELD-311
URL: https://jira.jboss.org/jira/browse/WELD-311
Project: Weld
Issue Type: Bug
Components: Producers (Methods, Fields and Disposers)
Affects Versions: 1.0.0.CR1
Environment: Ubuntu 9.10, Java 6.
Reporter: alberto Gori
This producer field inject a Temp object into the request scope, corretly.
@Named @SessionScoped
public class HelloWorld implements Serializable {
@Produces @RequestScoped @TenTemp
public Temp getTemp() {
return new Temp(10);
}
}
The same producer written as a field create a session scoped object (note that the main bean is session scoped too) instead of request scoped.
@Named @SessionScoped
public class HelloWorld implements Serializable {
@Produces @RequestScoped @TenTemp Temp t = new Temp(10);
}
--
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
15 years, 6 months
[JBoss JIRA] Created: (WELD-523) Weld SE ignores org.jboss.weld.resources.spi.ResourceLoader
by Morten Christensen (JIRA)
Weld SE ignores org.jboss.weld.resources.spi.ResourceLoader
-----------------------------------------------------------
Key: WELD-523
URL: https://jira.jboss.org/jira/browse/WELD-523
Project: Weld
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
15 years, 7 months
[JBoss JIRA] Created: (WELD-521) Support for dual SE and EE applications that uses weld
by Morten Christensen (JIRA)
Support for dual SE and EE applications that uses weld
------------------------------------------------------
Key: WELD-521
URL: https://jira.jboss.org/jira/browse/WELD-521
Project: Weld
Issue Type: Feature Request
Environment: Java SE and Java EE + weld
Reporter: Morten Christensen
Better support for dual SE and EE applications. I have some weld-using jar's that can be deployed on a Java EE and work standalone. It is possible to get this to work using both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE and weld EE OR there should at least be some support for having weld ignoring some of my classes/packages depending on which environment it is running under.
--
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
15 years, 7 months