Sakai
  1. Sakai
  2. SAK-10366

Branch to develop a JSR-170 Backed Content Hosting Serivce

    Details

      Description

      We are going to make a branch to modify Content Hosting Service so that it will work ontop of JSR-170 (probablty the JCRService in contrib)

      Ian Boston
      Jim Eng
      Linda M Place

      will be involved in this patch.

      We intend to test it with the UoM dataset to ensure that it can cope with 1.5TB of data.
      Aiming to be available in 2.5

        Activity

        Hide
        David Haines added a comment -
        I'm not quite sure where to find out if JSR 170 will make easy to implement an un-delete / soft delete capability. That would make a lot of people happy.
        Show
        David Haines added a comment - I'm not quite sure where to find out if JSR 170 will make easy to implement an un-delete / soft delete capability. That would make a lot of people happy.
        Hide
        Ian Boston added a comment -
        Soft delete,
        JSR-170 has versioning of everything, so a soft delete, undelete should be relatively easy.


        Show
        Ian Boston added a comment - Soft delete, JSR-170 has versioning of everything, so a soft delete, undelete should be relatively easy.
        Hide
        Ian Boston added a comment -
        The branch is now merged into trunk.

        In the process I have separated out the JCR dependencies from the main build so that you dont have to have a) JCR running in trunk/2.5.

        In the base pom.xml for content there are 2 new projects content-impl-jrc/impl and content-impl-jrc/pack

        impl builds the JCR extension jar that provides JCR storage and depends on the sakai jcr api.
        pack is an alternative pack to the standard DB CHS pack. This pack contains both the DB CHS and the JCR CHS

        For the moment, we will build the impl but not peform the pack so the JCR jar will not appear in the running Sakai.

        As we migrate we will continue to build the DB CHS (and the JCR CHS jar) but will move to the jcr pack.

        There is no need to change what is checked out, since build configuration is now all done with the pom.xml and not as a result of the code being present on disk.
        Show
        Ian Boston added a comment - The branch is now merged into trunk. In the process I have separated out the JCR dependencies from the main build so that you dont have to have a) JCR running in trunk/2.5. In the base pom.xml for content there are 2 new projects content-impl-jrc/impl and content-impl-jrc/pack impl builds the JCR extension jar that provides JCR storage and depends on the sakai jcr api. pack is an alternative pack to the standard DB CHS pack. This pack contains both the DB CHS and the JCR CHS For the moment, we will build the impl but not peform the pack so the JCR jar will not appear in the running Sakai. As we migrate we will continue to build the DB CHS (and the JCR CHS jar) but will move to the jcr pack. There is no need to change what is checked out, since build configuration is now all done with the pom.xml and not as a result of the code being present on disk.
        Hide
        Peter A. Knoop added a comment -
        [Bulk Change] This issue is currently Unresolved, however, it has a Fix Version set. In keeping with the newly added Target Version, Fix Versions should only be set for Resolved Issues, and only after it has been merged to that version specifically. The Fix Version is being reset to Unknown for this issue. Please use the Target Version to indicate when you plan to address this issue.
        Show
        Peter A. Knoop added a comment - [Bulk Change] This issue is currently Unresolved, however, it has a Fix Version set. In keeping with the newly added Target Version, Fix Versions should only be set for Resolved Issues, and only after it has been merged to that version specifically. The Fix Version is being reset to Unknown for this issue. Please use the Target Version to indicate when you plan to address this issue.
        Hide
        Ian Boston added a comment -
        Branch is now retired, and code merged into CHS in trunk, closing item
        Show
        Ian Boston added a comment - Branch is now retired, and code merged into CHS in trunk, closing item

          People

          • Assignee:
            Ian Boston
            Reporter:
            Ian Boston
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: