You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2015/06/02 00:15:18 UTC

[jira] [Closed] (TAP5-2421) VerifyError when adding advice to method with Error or RuntimeException in throws signature

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

Howard M. Lewis Ship closed TAP5-2421.
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 5.4

> VerifyError when adding advice to method with Error or RuntimeException in throws signature
> -------------------------------------------------------------------------------------------
>
>                 Key: TAP5-2421
>                 URL: https://issues.apache.org/jira/browse/TAP5-2421
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: plastic, tapestry-core
>    Affects Versions: 5.4
>            Reporter: Jochen Kemnade
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.4
>
>
> I have annotated a method in a page class with {{@Operation}}. When the method is called, a {{VerifyError}} is thrown:
> {code}
> 2014-11-24 13:19:46,685 [ajp-nio-9209-exec-33] ERROR o.a.t.m.T.RequestExceptionHandler - Processing of request failed with uncaught exception: java.lang.VerifyError: (class: pages/PageName$Invocation_methodName_1d10f8d1d549bc, method: proceedToAdvisedMethod signature: ()V) Incompatible argument to function
> {code}.
> The problem occurs with Java 7 as well as with Java 8 and regardless of whether the operation description contains a {{%}} or not.
> Unfortunately, I cannot reproduce the problem on a different machine.
> If I use {{OperationTracker}} "manually", no {{VerifyError}} is thrown.
> The advised method throws multiple checked exceptions and an {{Error}}.
> I'm not entirely sure what the error means, but I assume, the {{proceedToAdvisedMethod}} method is invoked with parameters, so it might be an issue with plastic rather than with tapestry-core.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)