]
Khoi Nguyen reassigned GTNPORTAL-1605:
--------------------------------------
Assignee: Khoi Nguyen
Merging PageNavigations should also merge child PageNodes
---------------------------------------------------------
Key: GTNPORTAL-1605
URL:
https://jira.jboss.org/browse/GTNPORTAL-1605
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Matt Wringe
Assignee: Khoi Nguyen
Attachments: merge_pageNodes.patch
Original Estimate: 1 day
Remaining Estimate: 1 day
The PageNavigation.merge command only merges in top level PageNodes, if a PageNode with
the same name already exists, it will overwrite the previous node with a new one.
This prevents being able to add a new page node to a subnode which already exists.
For example, the administration node by default contains the app-registry and
page-management PageNodes. I cannot use the extension mechanism to add an extra PageNode
here, since the PageNavigation.merge will delete the current administration node and
overwrite it with the one I specify in the extension. In this situation I am stuck adding
it to another top level location, which is not ideal.
What should happen is that the child PageNodes get merged together, so that I can add
extra nodes anywhere in the PageNode tree.
This will however change the behaviour of how extensions work. What this means is that
you can no longer overwrite or remove PageNodes using the extension mechanism.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: