[cdi-dev] [JBoss JIRA] (CDI-10) Add ability to access a bean instance from a proxy

Romain Manni-Bucau (JIRA) issues at jboss.org
Thu Nov 12 10:32:00 EST 2015

    [ https://issues.jboss.org/browse/CDI-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128352#comment-13128352 ] 

Romain Manni-Bucau commented on CDI-10:

About the need: a not cdi proxy friendly lib will not identify the class of the proxied instance and fields if not forwarded so the user type instance can be needed to do vallidation, state update etc...we can argue the lib can become cdi bit the opposite should be doable, ie let a dev integrate cdi with a not cdi lib IMO.

Technically I agree with Mark we need a way to define the unwrapping level we want.

> 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

More information about the cdi-dev mailing list