[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (SRAMP-20) Publishing of Multiple Artifact Entries
[ http://tools.oasis-open.org/issues/browse/SRAMP-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30050#action_30050 ]
Vincent Brunssen commented on SRAMP-20:
---------------------------------------
Comments on the 3 possible answer above and a proposal for how to solve this issue:
Possible Answers with comment
1) Fail the transaction and require that the publisher of the artifacts publish in such an order that the references can be verified
Attempts to publish an artifact that has references to other artifacts that are not yet published should return an error condition. The system can not complete the relationships that are required and therefore would have the possibility of creating an artifact that is orphaned or simply incorrect. So, the artifact should not be published and an error should be returned.
2) Set a flag on the first publish that denotes that we will not verify the relationships until the end of the publish of all artifacts. Then on the publish of the last artifact the flag would not be set and the verification would take place at that time.
This is a possibility, but adds a complexity that is not necessary. If a user were to set this "flag" and then unset the flag on the last publish, what happens if the entire set of artifacts still does not validate and there are still relationships that are invalid. Now there is a need for an accounting of all the artifacts that were published and then those artifacts would need to be removed and an error returned to the user to denote that the publish was not successful. This is a lot of extra work for the implementer of S-RAMP and it also steps in to the realm of dictating how to publish artifacts to a deeper level and we already have several different methods for publishing artifacts.
3) Publish the initial A.wsdl artifact and return a warning that some of the references could not be verified.
This is also a possibility, but there is the issue of what happens if the publisher of the artifact that a warning is returned for does not come back at a future time to publish the other related artifacts. Now we have in essence provided a mechanism for publishers of artifacts to "dirty" the repository with a bunch of artifacts that are incomplete. It also makes for more accounting on the server side to keep track of such incomplete artifacts.
Proposal for solution:
Based on the descriptions above, the best route for solving this issue would be just to fail the publish transaction if the artifacts are not complete. After all, the specification does provide a mechanism for batch processing and publishing a zip package. Both of these methods would solve this problem without issue. So, inventing a way to do individual posts that have incomplete relationships would not make sense, when the user could just as easily publish the artifacts in the proper order to resolve the relationships.
The spec should be updated to reflect this assessment to make sure that when we talk about the publishing of individual artifacts that we point to batch and zip publishing if there is a need to publish a set of artifacts that have dependencies on each other. The spec should also be explicit in the order of publishing to make sure that the implementer is clear that these rules should be enforced.
> Publishing of Multiple Artifact Entries
> ---------------------------------------
>
> Key: SRAMP-20
> URL: http://tools.oasis-open.org/issues/browse/SRAMP-20
> Project: OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
> Issue Type: Improvement
> Components: Atom Binding
> Affects Versions: 1.0
> Environment: N/A
> Reporter: Vincent Brunssen
> Assignee: Vincent Brunssen
> Fix For: 1.0
>
>
> Issue-020 from the contributed issues document
> Section 2.3.5.2 of Atom Doc - Publishing of multiple artifact entries. How to properly deal with relatively
> referenced imported artifacts when not doing a batch POST. Further clarification is needed.
--
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]