You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Massimo Lusetti (JIRA)" <ji...@apache.org> on 2011/08/12 17:44:27 UTC
[jira] [Closed] (TAP5-585) Some method names are not allowed in
components and pages
[ https://issues.apache.org/jira/browse/TAP5-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Massimo Lusetti closed TAP5-585.
--------------------------------
Resolution: Invalid
There are some conventions certainly please reopen this with a test case attached if that's the case as I don't see this issue bubble up frequently on the mailing list
> Some method names are not allowed in components and pages
> ---------------------------------------------------------
>
> Key: TAP5-585
> URL: https://issues.apache.org/jira/browse/TAP5-585
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.18
> Reporter: Felix Gonschorek
>
> Some method names in components and pages make tapestry throw an Exception: "StackMapTable format error: bad class index". Howard assumes this is a naming conflict to methods tapestry adds to components and pages on the fly.
> This is an example method, that throws the exception:
> @BeginRender
> boolean render(MarkupWriter writer) {
> //blubb
> return false;
> }
> When i rename the method to "boolean blubb(MarkupWriter writer)" for example, everything is fine.
> In the stack trace one can not see which method it is, or in which page/component the naming conflict occurs. It would save one some time to find the corresponding component if the stack trace or the exception message would give one a hint.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira