[weld-issues] [JBoss JIRA] Commented: (WELD-557) InjectionTarget methods called with a proxied instance

Jozef Hartinger (JIRA) jira-events at lists.jboss.org
Fri Jul 30 01:48:49 EDT 2010

    [ https://jira.jboss.org/browse/WELD-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12542060#action_12542060 ] 

Jozef Hartinger commented on WELD-557:

OK, but what do you need the proxied instance for in those methods? When trying to alter how injection is performed you IMHO do not need the instance to be intercepted/decorated. What you need more is a direct access to object's fields. Why cannot the target instance be passed? (Same way as it is in interceptors invocationContext.getTarget())

> InjectionTarget methods called with a proxied instance
> ------------------------------------------------------
>                 Key: WELD-557
>                 URL: https://jira.jboss.org/browse/WELD-557
>             Project: Weld
>          Issue Type: Bug
>    Affects Versions: 1.0.1.Final
>            Reporter: Jozef Hartinger
>            Assignee: David Allen
>            Priority: Critical
>             Fix For: 1.1.0.BETA1
> Let's have a bean whose InjectionTarget is wrapped by an extension to provide additional dependency injection, etc...
> Although it is not explicitly stated in the spec, it is obvious that inject(), postConstruct() and preDestroy() methods of the InjectionTarget should be called with the actual raw bean instance and not with a client proxy.
> org.jboss.weld.tests.extensions.injectionTarget.InjectionTargetTest
> (Consider moving the test into the TCK if the presumtion can be implied)

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


More information about the weld-issues mailing list