[
https://jira.nuxeo.org/browse/NXP-4954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anahide Tchertchian resolved NXP-4954.
--------------------------------------
Resolution: Fixed
> Provide a way to invalidate NavigationTree cache from the outside
> -----------------------------------------------------------------
>
> Key: NXP-4954
> URL: https://jira.nuxeo.org/browse/NXP-4954
> Project: Nuxeo Enterprise Platform
> Issue Type: Task
> Components: Web UI
> Affects Versions: 5.3.1
> Reporter: Thierry Delprat
> Assignee: Thierry Delprat
> Fix For: 5.3.2
>
> Attachments: nuxeo-platform-webapp-5.3.1.jar,
> nuxeo-platform-webapp-base-5.3.1-SNAPSHOT-sources.jar,
> nuxeo-platform-webapp-base-5.3.1-SNAPSHOT.jar
>
>
> The TreeActionBean keeps state about the navigation tree.
> State is automatically resfresh when updated within the Seam/JSF context
> using Seam events system.
> Nevertheless, when updating Nuxeo content from the outside (external editor,
> REST API ...), the state is not refreshed and a newly created Folder may not
> be displayed correctly.
> The simple solution is to provide a REST API that "external applications"
> will have to call to mark the Tree state as invalidated.
> There are 2 cases :
> - client know the conversation ID => invalidation can be done directly at
> the right level
> - client only knows the session => invalidation will be held at session
> level and fetched in conversation on first refresh
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.nuxeo.org/secure/Administrators.jspa
-
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
