[JBoss JIRA] (SRAMP-160) Change artifact's 'delete' action to be a logical delete
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-160?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-160:
--------------------------------
Fix Version/s: 0.3.0 JBPM6 Integration
(was: 0.2.0 Security)
> 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
> 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
11 years, 8 months
[JBoss JIRA] (SRAMP-160) Change artifact's 'delete' action to be a logical delete
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-160?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-160:
--------------------------------
Priority: Minor (was: Major)
> 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: Minor
> 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
11 years, 8 months
[JBoss JIRA] (SRAMP-188) Auditing: handle phase2 commits for artifact creates
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-188?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-188:
--------------------------------
Fix Version/s: 0.3.0 JBPM6 Integration
(was: 0.2.0 Security)
> Auditing: handle phase2 commits for artifact creates
> ----------------------------------------------------
>
> Key: SRAMP-188
> URL: https://issues.jboss.org/browse/SRAMP-188
> Project: S-RAMP
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.3.0 JBPM6 Integration
>
>
> When artifacts are added to the s-ramp repository the JCR nodes are written in two phases. In the case of non-derived artifacts, the second phase will updated the JCR node with any meta-data added to it by the Deriver.
> In the case of derived artifacts, the second phase will update the JCR node with most of the primary artifact meta-data.
> In both cases, the audit handler should update the appropriate audit entry JCR node with information recorded during the second phase commit. It should not create a new audit entry.
--
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
11 years, 8 months