[JBoss JIRA] Created: (CDI-89) Add @Unwraps from Seam Solder
by Stuart Douglas (JIRA)
Add @Unwraps from Seam Solder
------------------------------
Key: CDI-89
URL: https://issues.jboss.org/browse/CDI-89
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Concepts
Affects Versions: 1.0
Reporter: Stuart Douglas
@Unwraps allows for an essentially stateless scope for producer methods and fields.
At injection time a dependent scoped proxy is injected into the injection point. When a methods is invoked on this proxy it calls the corresponding @Unwraps methods to get the instance to invoke the method on.
Because the proxy is @Dependent scoped, the @Unwraps method can inject the corresponding InjectionPoint.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (CDI-18) cleanup Bean Archive behaviour (BDA) of interceptors, decorators and alternatives
by Mark Struberg (JIRA)
cleanup Bean Archive behaviour (BDA) of interceptors, decorators and alternatives
---------------------------------------------------------------------------------
Key: CDI-18
URL: https://jira.jboss.org/browse/CDI-18
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Specification
Affects Versions: 1.0
Reporter: Mark Struberg
Fix For: 1.0
Currently the spec defines that <interceptors>, <decorators> and <alternatives> affect only the Bean Archives where they are configured in (via beans.xml).
Thus if you e.g. enable an Alternative in a WEB-INF/beans.xml, it does NOT count for the jars in it's WEB-INF/lib folder!
This is pretty unhandy because you would need to repackage all your jars in your WEB-INF/lib folder and add/expand the <alternatives> sections in their beans.xml.
Needless to say that this is not only hard to do in a company build but is also impossibly to handle at deploy time in an OSGi environment!
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (CDI-10) Add ability to access a bean instance from a proxy
by Stuart Douglas (JIRA)
Add ability to access a bean instance from a proxy
--------------------------------------------------
Key: CDI-10
URL: https://jira.jboss.org/browse/CDI-10
Project: CDI Specification Issues
Issue Type: Feature Request
Reporter: Stuart Douglas
There are occasions when it would be useful to access a bean instance directly from a proxy. This could be achieved by making all proxies assignable to an interface (say BeanProxy) that provides a getBeanInstance() method.
Client code that needs access to the actual instance can check if the object is assignable to the BeanProxy interface and then call getBeanInstance() to get the actual instance if required.
This is something that is probably more useful to extension writers than the end user, but there have already been a few requests on the weld forum about this so it is probably worth considering.
--
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
13 years, 11 months
[JBoss JIRA] Created: (CDI-84) Non EE modules should be able to trigger creation of a BeanManager
by Aslak Knutsen (JIRA)
Non EE modules should be able to trigger creation of a BeanManager
------------------------------------------------------------------
Key: CDI-84
URL: https://issues.jboss.org/browse/CDI-84
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Specification
Affects Versions: 1.0
Reporter: Aslak Knutsen
EE.5.19
A bean manager is only available in modules in which CDI has been enabled.
Where EE modules are defined to be; ejb-jar, rar, client jar and war.
This is a missmatch between the EE spec and the CDI spec. According to the CDI spec, any archive with a beans.xml is defined as a BeanArchive and should be included in a BeanManager, EE define it to be only EE modules should trigger BeanManager creation.
Opening this up to follow the CDI spec will let any library use the BeanManager to introspect other BeanArchives without having to involve the owning EE module in the loop.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months