[
https://issues.apache.org/jira/browse/JS2-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846417#action_12846417
]
Woonsan Ko commented on JS2-1078:
---------------------------------
AFAIK, in portal site manager portlet, we have three categories regarding this
issue: (1) exporting, (2) importing and (3) copying or moving.
I think we'd better have the following rules with regard to copying fragment
IDs:
(1) In exporting, the fragment IDs are to be copied, without generating new
ones.
(2) In importing, we'd better provide an option check box whether copying all
existing fragment IDs or not. (The default option should be "Use existing
fragment IDs".)
(3) In copying or moving a node, we'd better provide an option check box
whether copying all existing fragment IDs or not. (The default option should be
"Generate new fragment IDs" in this case.)
I will fix this with the above rules.
> Review Page Manager copy/merge API usage
> ----------------------------------------
>
> Key: JS2-1078
> URL: https://issues.apache.org/jira/browse/JS2-1078
> Project: Jetspeed 2
> Issue Type: Task
> Components: Admin Portlets, PSML
> Affects Versions: 2.2.1
> Environment: Portal Site admin portlets
> Reporter: Randy Watler
> Assignee: Woonsan Ko
> Priority: Minor
> Fix For: 2.2.1
>
>
> Page Manager APIs have been recently extended to support copy/merge
> operations that preserve Fragment Ids. Fragment Ids should be preserved for
> all PSML move and import/export operations. The Portal Site admin portlets
> should be updated to use the new APIs where appropriate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
