[
https://issues.apache.org/jira/browse/TRINIDAD-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Schwartz updated TRINIDAD-2443:
------------------------------------
Resolution: Fixed
Fix Version/s: 2.1.1-core
Status: Resolved (was: Patch Available)
Reduced the logger level to INFO.
> Reduce severity of component binding reuse message
> --------------------------------------------------
>
> Key: TRINIDAD-2443
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2443
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Reporter: Andy Schwartz
> Assignee: Andy Schwartz
> Priority: Minor
> Fix For: 2.1.1-core
>
> Attachments: TRINIDAD-2443-take2.patch, TRINIDAD-2443.patch
>
>
> As part of our changes for:
> TRINIDAD-2409 improve diagnostics during tag execution component binding
> failures
> We added some logging to UIXComponentELTag.createComponent() when we detect a
> newly created component with a "stale" parent.
> The idea behind this logging is that it should help catch cases where the
> component tree is being pinned in memory, typically by using a component
> binding that references a long-lived (eg. session scope.
> However, it turns out that we're detecting (and logging the severe message
> for) other cases. For example:
> - A page fragment defines a component with a binding that points to a request
> scoped bean.
> - The page fragment is jsp:included into both page1.jspx and page2.jspx.
> - The user navigates from page1.jspx to page2.jspx (with no redirect).
> At this point we see the severe message, even though there is no risk of
> component tree pinning.
> Unfortunately, we don't just see the message once, but repeatedly on every
> navigation. And since the message is being logged as severe, it will likely
> show up in (and bloat) logs for production deployments.
> I think that this message is still useful, but more for debugging purposes
> than for production error reporting. As such, opening this issue to request
> that we crank the severity down.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
