You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Peter Niederwieser (JIRA)" <ji...@apache.org> on 2009/12/02 02:15:20 UTC

[jira] Updated: (TAP5-839) Tapestry should ignore (public) synthetic methods in module classes

     [ https://issues.apache.org/jira/browse/TAP5-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Niederwieser updated TAP5-839:
------------------------------------

    Attachment: fix_for_TAP5-839.patch

Here is a patch for this bug, along with a test. Hope this will speed things up. 

> Tapestry should ignore (public) synthetic methods in module classes
> -------------------------------------------------------------------
>
>                 Key: TAP5-839
>                 URL: https://issues.apache.org/jira/browse/TAP5-839
>             Project: Tapestry 5
>          Issue Type: Bug
>            Reporter: Peter Niederwieser
>         Attachments: fix_for_TAP5-839.patch
>
>
> Groovy (and probably other alternative languages as well) enriches its classes with public synthetic methods. For module classes written in Groovy, Tapestry complains that it doesn't recognize these methods. Because synthetic methods are obviously not meant for Tapestry, they should be ignored.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.