[
https://issues.apache.org/jira/browse/TRINIDAD-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745131#comment-13745131
]
Jeanne Waldman commented on TRINIDAD-2409:
------------------------------------------
Sending content:
C:\Trinidad\Trunk\trinidad-api\src\main\java\org\apache\myfaces\trinidad\webapp\UIXComponentELTag.java
Sending content:
C:\Trinidad\Trunk\trinidad-api\src\main\xrts\org\apache\myfaces\trinidad\resource\LoggerBundle.xrts
Completed: At revision: 1515879
> improve diagnostics during tag execution component binding failures
> -------------------------------------------------------------------
>
> Key: TRINIDAD-2409
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2409
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Affects Versions: 2.0.1-core
> Reporter: Pavitra Subramaniam
> Attachments: jira-2409.patch
>
>
> 2 places where error reporting can be improved is in
> 1. UIXComponentELTag.doStartTag()
> We could add a try/catch around the super.doStartTag(), do some severe
> logging (eg.log a scoped id) in response to exceptions, and re-throw.
> 2. UIXComponentELTag.createComponent()
> This might be a reasonable place to detect the cases where a component that
> you pull out of a component binding during createComponent() is already
> attached to some component tree- and thus the (severe) error is justified.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
