[
https://jira.nuxeo.com/browse/NXP-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anahide Tchertchian resolved NXP-5725.
--------------------------------------
Resolution: Fixed
Impact type: [API change]
Upgrade notes: include the widget/row/layout tag id (see new methods
getTagConfigId()) when creating facelet handlers
Now layouts, rows and widgets use a unique identifier (corresponding to their
definition) for the components/converters, etc... that are created (instead of
always using the original tag id):
http://hg.nuxeo.org/nuxeo/nuxeo-services/rev/0aa186db8219
http://hg.nuxeo.org/nuxeo/nuxeo-jsf/rev/d8a263464c32
http://hg.nuxeo.org/nuxeo/nuxeo-jsf/rev/9b31b6a548b9
http://hg.nuxeo.org/nuxeo/nuxeo-features/rev/0bff65650949
> Fix layouts re-render in ajax
> -----------------------------
>
> Key: NXP-5725
> URL: https://jira.nuxeo.com/browse/NXP-5725
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Affects Versions: 5.4
> Reporter: Anahide Tchertchian
> Assignee: Anahide Tchertchian
> Fix For: 5.4.2
>
>
> When re-displaying layouts using ajax calls, sometimes layout is not
> re-rendered as expected.
> This is due to some facelets cache that does not re-create component when
> found in the existing tree of JSF components.
> This is true for widgets, but also for any component in the layout template
> for instance: it keeps its old values (and value expressions with the old
> variable mapper) so display is not correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
