[ 
https://jira.jboss.org/browse/WELD-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Allen resolved WELD-546.
------------------------------

    Resolution: Done


The problem was really with the names of the proxy classes and in particular, 
it was uncovered by specific ordering of events with producers and their 
products.  The naming of the proxy classes has been changed to correct this 
overall.  Now the producer bean and its product always have distinct proxy 
class names that are differentiated based on types.

> Beans producing stuff have their proxies proxying the product
> -------------------------------------------------------------
>
>                 Key: WELD-546
>                 URL: https://jira.jboss.org/browse/WELD-546
>             Project: Weld
>          Issue Type: Bug
>          Components: Producers (Methods, Fields and Disposers)
>    Affects Versions: 1.0.1.Final
>            Reporter: Nicklas Karlsson
>            Assignee: David Allen
>             Fix For: 1.0.2.CR1
>
>
> Given
> @Model
> public class GreetingBean {
>       @Produces
>       @Model
>       Greeting greeting = new Greeting();
>       public void ping() {
>       }
> }
> #{greetingBean.ping} gives an "Method not found" exception because the 
> GreetingBean_$$_WeldProxy is actually proxing Greeting

-- 
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

        
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues

Reply via email to