[seam-issues] [JBoss JIRA] Assigned: (JBSEAM-4789) State in org.jboss.seam.ui.renderkit.DecorateRendererBase

[Marek Novotny (JIRA)]

     [ https://issues.jboss.org/browse/JBSEAM-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny reassigned JBSEAM-4789:
-------------------------------------

    Assignee: Nicklas Karlsson


Nicklas, could you look at it?

> State in org.jboss.seam.ui.renderkit.DecorateRendererBase
> ---------------------------------------------------------
>
>                 Key: JBSEAM-4789
>                 URL: https://issues.jboss.org/browse/JBSEAM-4789
>             Project: Seam
>          Issue Type: Bug
>          Components: JSF Controls
>    Affects Versions: 2.2.1.Final
>            Reporter: Nicholas Oxhøj
>            Assignee: Nicklas Karlsson
>
> Using several facelet templates, I accidentally ended up nesting two <s:decorate> tags. This led to some very strange errors with inputs showing up as required, when they weren't...
> After quite a bit of debugging, I think the error is caused by an error in org.jboss.seam.ui.renderkit.DecorateRendererBase. When [JBSEAM-3471|https://issues.jboss.org/browse/JBSEAM-3471] was resolved, it was done by introducing a bit of state in the renderer, to store the attributes "required" and "invalid". Since the renderer is shared between all the <s:decorate> tags, when you start nesting them, the state for the innermost tag is going to overwrite the previous state, and strange errors start to happen...
> Aren't renderers supposed to be stateless, since they are shared?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira