Jetspeed 2
  1. Jetspeed 2
  2. JS2-1078

Review Page Manager copy/merge API usage

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.2.1
    • Fix Version/s: 2.2.1
    • Component/s: Admin Portlets, PSML
    • Labels:
      None
    • Environment:
      Portal Site admin portlets

      Description

      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.

        Activity

        Hide
        Woonsan Ko added a comment -

        Fixed.

        Show
        Woonsan Ko added a comment - Fixed.
        Hide
        Woonsan Ko added a comment -

        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.

        Show
        Woonsan Ko added a comment - 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.

          People

          • Assignee:
            Woonsan Ko
            Reporter:
            Randy Watler
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development