[
https://issues.jboss.org/browse/CDI-10?page=com.atlassian.jira.plugin.sys...
]
Bauke Scholtz edited comment on CDI-10 at 3/12/16 11:20 AM:
------------------------------------------------------------
I understand that, but those beans are not part of public API. It's an implementation
detail and not supposed to be intercepted/injected/whatever by enduser.
Arjan Tijms suggested a potential alternate solution: a producer with a package private
qualifier. I will try that sooner or later.
was (Author: bauke):
I understand that, but those beans are not part of public API. It's an implementation
detail and not supposed to be intercepted/injected/whatever by enduser.
Arjan Tijms suggested an alternate solution: a producer with a package private qualifier.
I will try that sooner or later.
Add ability to access a bean instance from a proxy
--------------------------------------------------
Key: CDI-10
URL:
https://issues.jboss.org/browse/CDI-10
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Beans
Affects Versions: 1.0
Reporter: Stuart Douglas
Fix For: 2.0 (discussion)
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 was sent by Atlassian JIRA
(v6.4.11#64026)