[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (SRAMP-37) Batch Processing: Response construct is not correct
[ http://tools.oasis-open.org/issues/browse/SRAMP-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30049#action_30049 ]
Radek Pospisil commented on SRAMP-37:
--------------------------------------
Proposal:
Response will refer to the corresponding request part (in case of Batch POST)/file (in case of package publishing) that was used to create/update the result by the server:
* Batch POST:
Request already contains client generated Content-ID headers for both parts - atom:entry and document content. The server will choose either atom:entry's of document content's Content-ID in the response to identify the corresponding request
* package publishing
Request is composed of files carrying either atom:entry or document content. The Content-ID used in the response is constructed from the file path w/o leading '/' and @package string - e.g., a.wsdl@package, a.wsdl.atom@package, a/b/c/x.xsd@package ,... As in case of Batch POST, the server will choose either atom:entry's of document content's Content-ID in the response to identify the corresponding request .
If there are created artifact instances indirectly connected to the artifact instances created from the request (like in case of derived model artifacts), then they are not part of the response.
Example:
REQUEST:
POST /s-ramp/xsd HTTP/1.1
Host: example.org
Content-Length: nnnn
Content-Type: multipart/related;version 1.1;msgtype=request;boundary=example-bound;type="application/atom+xml;type=entry";start="<12@example.org>"
Slug: The Beach
MIME-Version: 1.0
--example-bound—
Content-Type: application/atom+xml;type=entry
Content-ID: <12@example.org >
<entry xmlns="http://www.w3.org/2005/Atom";
xmlns:s-ramp="http://s-ramp.org/xmlns/2010/s-ramp";>
<id>urn:uuid:aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaa6a</id>
<updated>2009-05-26T13:13:55.014+02:00</updated>
<title type="text">A.xsd</title>
<published>2009-05-26T13:13:55.013+02:00</published>
<author>
<name>Bellwood</name>
</author>
<contributor>
<name>Pospisil</name>
</contributor
<summary type="text">A.xsd schema document</summary>
<link href="<56@example.org>" type="application/atom+xml;type=entry"
rel="related" title="Imported XSD"/>
<content src="<34@example.org>"/>
<!—
S-RAMP defined categorizations identifying class of data represented by
this entry
-->
<category term="XsdDocument" label="XML Schema"
scheme="urn:x-s-ramp:2010:type" />
<s-ramp:artifact
...rest of artifact definition goes here...
</ s-ramp:artifact>
</entry>
--example-bound--
Content-Type: application/xml
Content-Description: The root XSD document
Content-Transfer-Encoding: base64
Content-ID: <34@example.org>
...XML content for A.xsd...
--example-bound--
Content-Type: application/atom+xml;type=entry
Content-ID: <56@example.org>
<entry xmlns="http://www.w3.org/2005/Atom";
xmlns:s-ramp="http://s-ramp.org/xmlns/2010/s-ramp";>
<id>urn:uuid:bbbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbb6b</id>
<title type="text">B.xsd</title>
<content src="<78@example.org>"/>
...rest of entry document goes here...
</entry>
--example-bound--
Content-Type: application/xml
Content-Description: The imported XSD document
Content-Transfer-Encoding: base64
Content-ID: <78@example.org>
...XML content for B.xsd...
--example-bound--
RESPONSE:
HTTP/1.1 200 OK
Date: Tues, 26 May 2009 13:13:55 GMT+02:00
Content-Length: 1234520
Content-Type: multipart/http;version=1.1;msgtype=response;boundary=batch
Mime-Version: 1.0
--batch
Content-ID: <12@example.org>
HTTP/1.1 201 Created
Date: Tues, 26 May 2009 13:13:55 GMT+02:00
{Updated/created Atom:entry for Resource A omitted for clarity}
--batch
Content-ID: <78@example.org>
HTTP/1.1 201 Created
Date: Tues, 26 May 2009 13:13:55 GMT+02:00
{Updated/created Atom:entry for Resource B omitted for clarity}
> Batch Processing: Response construct is not correct
> ---------------------------------------------------
>
> Key: SRAMP-37
> URL: http://tools.oasis-open.org/issues/browse/SRAMP-37
> Project: OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
> Issue Type: Bug
> Components: Atom Binding
> Affects Versions: 1.0
> Reporter: Vincent Brunssen
> Assignee: Radek Pospisil
> Fix For: 1.0
>
>
> During the discussion of issue SRAMP-8 it was discovered that Batch Processing has some issues regarding the construction of the response. The response does not contain any information regarding the actual document that was created during the batch post. It instead uses the UUID that was created. During the meeting of March 27, 2012, Radek Pospisil made the suggestion that we use a construct similar to his proposal for zip package processing in SRAMP-8. The members present felt that this was the correct way to proceed and a similar proposal will be put forward for batch processing.
--
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]