You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@isis.apache.org by "Andi Huber (Jira)" <ji...@apache.org> on 2022/08/02 06:32:00 UTC

[jira] [Updated] (ISIS-3015) [Wicket Viewer] Property Edit via FormExecutorDefault, will not display Recoverable Exception

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

Andi Huber updated ISIS-3015:
-----------------------------
    Fix Version/s: 2.0.0-RC1
                       (was: 2.0.0-M8)

> [Wicket Viewer] Property Edit via FormExecutorDefault, will not display Recoverable Exception
> ---------------------------------------------------------------------------------------------
>
>                 Key: ISIS-3015
>                 URL: https://issues.apache.org/jira/browse/ISIS-3015
>             Project: Isis
>          Issue Type: Improvement
>          Components: Wicket Viewer
>    Affects Versions: 2.0.0-M7
>            Reporter: Miklós Győrfi
>            Assignee: Andi Huber
>            Priority: Major
>             Fix For: 2.0.0-RC1
>
>
> During property edit, FormExecutorDefault does not display database error, because it checks 
> {code:java}
> !formExecutorContext.isWithinInlinePrompt(){code}
>  condition. 
> It would be nice if ExceptionRecognizerService/ExceptionRecognizer could mark the exception in Recognition if:
>  * The exception should be displayed as message in Action/Property/Inline edit.
>  * This feature default to configuration
> This protocol should be supported in FormExecutorDefault.
> Anyway, the current protocol does not work at all, it forwards the exception, but does not display the error page neither due to the WebRequestCycleForIsis and the JGrowlUtil bug. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)