[prev in list] [next in list] [prev in thread] [next in thread]
List: myfaces-dev
Subject: [jira] [Resolved] (MYFACES-3258) Improve logging and exception handling for UILeaf
From: "Thomas Andraschko (Jira)" <dev () myfaces ! apache ! org>
Date: 2020-05-25 17:15:00
Message-ID: JIRA.12517834.1312402727000.106033.1590426900234 () Atlassian ! JIRA
[Download RAW message or body]
[ https://issues.apache.org/jira/browse/MYFACES-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]
Thomas Andraschko resolved MYFACES-3258.
----------------------------------------
Resolution: Fixed
> Improve logging and exception handling for UILeaf
> -------------------------------------------------
>
> Key: MYFACES-3258
> URL: https://issues.apache.org/jira/browse/MYFACES-3258
> Project: MyFaces Core
> Issue Type: Sub-task
> Components: General
> Reporter: Martin Kočí
> Assignee: Martin Kočí
> Priority: Minor
> Fix For: 2.3-next-M3
>
>
> If #{} (without a component tag) throws a exception (mainly in render response), it \
> is practically impossible for user to find out which element was the source. \
> Suggestions:
> * use Location and TagAttributeAware EL context wrappers from MYFACES-3202 in \
> ELText
> * put UIComponent.VIEW_LOCATION_KEY into UILeaf during VDL.buildView
> * improve toString for UIInstructions (output sometimes spans over three or more \
> lines)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic