[
https://issues.jboss.org/browse/CDI-10?page=com.atlassian.jira.plugin.sys...
]
Martin Kouba reopened CDI-10:
-----------------------------
I believe this issue is valid and should be reopened. Recently, we've run into
problems with two integration scenarios where having this portable way to detect a client
proxy and access the bean instance would allow to implement portable
"workarounds".
h3. Bean Validation
The spec does not forbid the *field access strategy* to be used for normal-scoped CDI
beans. However, this doesn't work because injectable references for normal-scoped
beans are client proxies and not direct references to contextual instances. See also
https://forum.hibernate.org/viewtopic.php?f=26&t=1039523.
h3. JAX-RS
Weld client proxies lose generic type information which screws up injection of generic
params into RESTEasy resource methods. See also WELD-1539.
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
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.3.15#6346)