[JBoss JIRA] (SRAMP-601) Support deleting an artifact's content
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-601?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-601:
--------------------------------
Description: 2.3.5.5 requires that we support deleting an artifact's *content*, which should remove its media link. We currently only support deleting the artifact itself. (was: 2.3.5.5 requires that we support deleting an artifact's *content*, which should remove it's media link. We currently only support deleting the artifact itself.)
> Support deleting an artifact's content
> --------------------------------------
>
> Key: SRAMP-601
> URL: https://issues.jboss.org/browse/SRAMP-601
> Project: S-RAMP
> Issue Type: Sub-task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> 2.3.5.5 requires that we support deleting an artifact's *content*, which should remove its media link. We currently only support deleting the artifact itself.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (SRAMP-601) Support deleting an artifact's content
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-601?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-601:
-----------------------------------
[~eric.wittmann], this will be similar to the updateContent discussion. And really, same question for deleting an artifact itself. Presumably, updateContent and deleteContent will both delete the derived artifacts in some fashion. What should happen if relationships *target* something that's deleted or swapped out? Should the relationships automatically get deleted? Should we throw some sort of constraint exception and block the delete?
I'd vote for the latter -- less risky and *far* less complicated. Thoughts?
> Support deleting an artifact's content
> --------------------------------------
>
> Key: SRAMP-601
> URL: https://issues.jboss.org/browse/SRAMP-601
> Project: S-RAMP
> Issue Type: Sub-task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> 2.3.5.5 requires that we support deleting an artifact's *content*, which should remove it's media link. We currently only support deleting the artifact itself.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (SRAMP-596) Set urn:x-s-ramp:2013:kind atom category
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-596?page=com.atlassian.jira.plugin.... ]
Brett Meyer resolved SRAMP-596.
-------------------------------
Fix Version/s: 0.7.0.Final
Resolution: Done
> Set urn:x-s-ramp:2013:kind atom category
> ----------------------------------------
>
> Key: SRAMP-596
> URL: https://issues.jboss.org/browse/SRAMP-596
> Project: S-RAMP
> Issue Type: Sub-task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 0.7.0.Final
>
>
> urn:x-s-ramp:2013:kind
> Indicates the kind of the entry
> Occurs in Artifact Entry, Relationship Target Entry, Relationship Type Entry, and Property Entry documents, except as noted below.
> Legal values for the term attribute are
> "derived"
> Indicates entry is part of a Derived Model
> "modeled"
> Indicates entry is pre-defined and is part of the SOA or Service Implementation Models or is part of an extended artifact model
> "generic"
> Indicates entry is ad-hoc
> Does not occur in Artifact Entry documents.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (SRAMP-596) Set urn:x-s-ramp:2013:kind atom category
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-596?page=com.atlassian.jira.plugin.... ]
Work on SRAMP-596 started by Brett Meyer.
-----------------------------------------
> Set urn:x-s-ramp:2013:kind atom category
> ----------------------------------------
>
> Key: SRAMP-596
> URL: https://issues.jboss.org/browse/SRAMP-596
> Project: S-RAMP
> Issue Type: Sub-task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 0.7.0.Final
>
>
> urn:x-s-ramp:2013:kind
> Indicates the kind of the entry
> Occurs in Artifact Entry, Relationship Target Entry, Relationship Type Entry, and Property Entry documents, except as noted below.
> Legal values for the term attribute are
> "derived"
> Indicates entry is part of a Derived Model
> "modeled"
> Indicates entry is pre-defined and is part of the SOA or Service Implementation Models or is part of an extended artifact model
> "generic"
> Indicates entry is ad-hoc
> Does not occur in Artifact Entry documents.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month