[cdi-dev] [JBoss JIRA] Commented: (CDI-10) Add ability to access a bean instance from a proxy
Mark Struberg (JIRA)
jira-events at lists.jboss.org
Sat Apr 30 15:39:18 EDT 2011
[ https://issues.jboss.org/browse/CDI-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599254#comment-12599254 ]
Mark Struberg commented on CDI-10:
----------------------------------
Think this is not really needed.
If an Extension hacker really needs such a hardcore hack, then he might as well take the direct route:
{code}
@Inject BeanManager bm;
..
Context ctx = bm.getContext(SessionScoped.class);
Bean bean = bm.resolve(bm.getBeans(type, qualifiers);
Object instance = ctx.get(bean);
{code}
So I see no need for such a hack via the proxy...
> 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: TBD
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the cdi-dev
mailing list