[
https://issues.jboss.org/browse/SRAMP-160?page=com.atlassian.jira.plugin....
]
Eric Wittmann resolved SRAMP-160.
---------------------------------
Resolution: Done
Changed artifact delete to be a logical rather than a hard delete. The
artifact JCR node is now stripped of its sramp mixin type and moved from
/s-ramp/ to /s-ramp-trash/. The move isn't strictly necessary but it
was an easy way to make sure getArtifact wouldn't be able to find it.
Change artifact's 'delete' action to be a logical delete
--------------------------------------------------------
Key: SRAMP-160
URL:
https://issues.jboss.org/browse/SRAMP-160
Project: S-RAMP
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Core
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Priority: Critical
Fix For: 0.3.0 - JBPM6 Integration
The reason for doing this is that we should not allow duplicate UUIDs, even for deleted
artifacts. Currently a delete will remove the artifact from the repository. Instead, we
should either move the artifact to some alternate collection or simply tag it as deleted
(and then augment all incoming queries with a predicate that will exclude deleted
artifacts).
Do we need a way to actually for-real delete an artifact?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira