[weld-issues] [JBoss JIRA] Commented: (WELD-840) Weld 1.1 breaks compatibility with groovy objects

[Ales Justin (JIRA)]

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

Ales Justin commented on WELD-840:
----------------------------------

Although the patch seems to work, this shouldn't be handled in such a way.
By a diff way I mean a more plugable way.
Today it is Groovy which has issues with proxies, tomorrow it something else.
(e.g. some other dynamic language)
Doing this by adding more and more logic to ProxyFactory,
we'll only end up with code that nobody can read anymore.


> 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