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

Jeff Howard commented on WELD-840:
----------------------------------

Agreed.  That patch is simply intended to show you (the Weld developers) where 
and why things presently aren't working.  It's also sufficient to keep my 
dev/test environment running until you guys figure out a real fix.  :)

> Weld 1.1 breaks compatibility with groovy objects
> -------------------------------------------------
>
>                 Key: WELD-840
>                 URL: https://issues.jboss.org/browse/WELD-840
>             Project: Weld
>          Issue Type: Bug
>          Components: Proxies
>    Affects Versions: 1.1.0.Final
>         Environment: Groovy 1.7.6, tomcat 6, weld 1.1, JSF 2 (mojarra 2.0.3)
>            Reporter: Jeff Howard
>            Assignee: Stuart Douglas
>              Labels: groovy
>         Attachments: full_groovy_support.diff, 
> weld11_partial_groovy_support.diff
>
>
> Weld created proxies need to know how to work with groovy objects.  
> Currently, weld is attempting to proxy the methods from the 
> groovy.lang.GroovyObject interface which is confusing the groovy runtime.  
> Groovy objects have a per-class metaclass that is getting used with the wrong 
> class instances.
> Also, weld is using hyphen characters in the generated proxy class names, 
> which breaks groovy's dynamic invoke mechanism.
> The referenced forum thread contains a patch that addresses the groovy 
> incompatabilities in weld's ProxyFactory.java

-- 
This message is automatically generated by JIRA.
-
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