Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-24850

Enable new TrashService

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.2
    • Component/s: Core
    • Release Notes Description:
      Hide

      Trash Service Enabled

      The new trash service has been enabled by default on the repository. It fires dedicated events documentTrashed and documentUntrashed (hold by TrashService interface). See upgrade notes for more information on migration.

      Show
      Trash Service Enabled The new trash service has been enabled by default on the repository. It fires dedicated events documentTrashed and documentUntrashed (hold by TrashService interface). See upgrade notes for more information on migration.
    • Upgrade notes:
      Hide

      API Changes

      The new TrashService fires dedicated events documentTrashed and documentUntrashed (hold by TrashService interface) instead of lifecycle_transition_event. The document model passed in the event won't be saved by Nuxeo at the end.

      Keeping Old Trash implementation

      The trash implementation has changed in 10.2. If you want to keep previous implementation relying on life cycle state, add the following contribution:

        <require>org.nuxeo.ecm.core.trash.service.migrator</require>
        <extension target="org.nuxeo.runtime.migration.MigrationService" point="configuration">
      
          <migration id="trash-storage">
            <defaultState>lifecycle</defaultState>
          </migration>
      
        </extension>
      

      If you want to migrate trash state to the new property model (ecm:isTrashed), follow the Trash migrations steps.

      Trash Migration

      To migrate trash states to the new property model:

      1. Follow the step from section Keeping old trash implementation.
      2. In the Nuxeo Platform's JSF UI, go to Admin > System Information > Migration, click the button Migrate trashed state from lifecycle to property and wait until migration is completed.
      3. Remove the contribution added at step 1.

      INFO: during migration, document in state deleted will receive the isTrashed property set to true but migrator will leave document in deleted state

      Show
      API Changes The new TrashService fires dedicated events documentTrashed and documentUntrashed (hold by TrashService interface) instead of lifecycle_transition_event . The document model passed in the event won't be saved by Nuxeo at the end. Keeping Old Trash implementation The trash implementation has changed in 10.2. If you want to keep previous implementation relying on life cycle state, add the following contribution: <require>org.nuxeo.ecm.core.trash.service.migrator</require> <extension target= "org.nuxeo.runtime.migration.MigrationService" point= "configuration" > <migration id= "trash-storage" > <defaultState>lifecycle</defaultState> </migration> </extension> If you want to migrate trash state to the new property model (ecm:isTrashed), follow the Trash migrations steps. Trash Migration To migrate trash states to the new property model: Follow the step from section Keeping old trash implementation. In the Nuxeo Platform's JSF UI, go to Admin > System Information > Migration, click the button Migrate trashed state from lifecycle to property and wait until migration is completed. Remove the contribution added at step 1. INFO: during migration, document in state deleted will receive the isTrashed property set to true but migrator will leave document in deleted state
    • Sprint:
      nxcore 10.2.3
    • Story Points:
      2

      Description

      We want to enable new TrashService based on a system property instead of life cycle state.

      We also need to write documentation about the migration steps to do.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 days, 4 hours
                  2d 4h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.