[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (SRAMP-9) Dependencies
[ http://tools.oasis-open.org/issues/browse/SRAMP-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29442#action_29442 ]
Vincent Brunssen commented on SRAMP-9:
--------------------------------------
Section 2.3.5.5 of the Atom Binding Document is the section that this issue calls in to question. The text from that section is included below:
Deletion of an Artifact Entry is accomplished using HTTP DELETE, with this sample syntax:
To delete an Artifact Entry (for media link entries, this implicitly deletes the corresponding content as well):
DELETE /s-ramp/{artifactModel}/{artifactType}/{uuid:artifact} HTTP/1.1
Host: example.org
To delete content (this implicitly deletes the corresponding media link entry as well):
DELETE /s-ramp/{artifactModel}/{artifactType}/{uuid:artifact}/media HTTP/1.1
Host: example.org
The above URL for the entry with the indicated Artifact Entry uuid property MUST already resolve to an existing Artifact Entry in the repository in order for it to be deleted. All artifacts not belonging to a Derived Model can be deleted by a client. The deletion of an Artifact Entry also removes all of its relationships. Additional information on how this affects reporting of backward relationship feeds in the Fine Grained View can be found in Section 2.4.1.7.
If an artifact is deleted which is the Target Entry of a relationship instance owned by some other Source Entry, then that relationship instance is also deleted in that Source Entry.
The following HTTP errors MAY be returned:
404 Not Found (no matching Artifact Entry uuid property in repository)
403 Forbidden (returned in response to an attempted delete of a Derived Artifact)
This section specifically calls out section 2.4.1.7 which then goes in to detail on how to delete relationships.
The question here is: How do we treat the deleting of artifacts? Do we constrain it is such a way that only the artifact to be deleted is deleted and all referenced artifacts are left in the repository in essence orphaning those artifacts, or do we delete the specific artifact and all related artifacts as the spec is currently written today?
We need to have a member of the TC take a closer look at these two sections and make a proposal on how this should be resolved.
> Dependencies
> ------------
>
> Key: SRAMP-9
> URL: http://tools.oasis-open.org/issues/browse/SRAMP-9
> Project: OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
> Issue Type: Improvement
> Components: Foundation
> Affects Versions: 1.0
> Environment: N/A
> Reporter: Vincent Brunssen
> Fix For: 1.0
>
>
> Issue-009 from the contributed issues document
> Dependencies required first? If X depends on Y, can you delete Y? But should X and Y exist independently. The spec as written today requires dependency resolutions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]