[JBoss JIRA] (SRAMP-552) Support relationships with no target
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-552?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated SRAMP-552:
------------------------------
Parent: (was: SRAMP-90)
Issue Type: Feature Request (was: Sub-task)
> Support relationships with no target
> ------------------------------------
>
> Key: SRAMP-552
> URL: https://issues.jboss.org/browse/SRAMP-552
> Project: S-RAMP
> Issue Type: Feature Request
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> 2.1.2
> "It is possible for a relationship of a given Relationship Type not to have a target, which is termed a "relationship with no targets". In this case there is only one relationship instance with that Relationship Type for a given Source. Such relationships have a target cardinality of "0". If there is a relationship instance with a given Relationship Type that does have a target, then there CANNOT also be a relationship instance with that Relationship Type which has no target."
> Currently, this causes:
> {code}
> Caused by: javax.jcr.PathNotFoundException: No item exists at path sramp:relationshipType relative to /s-ramp/artifacts/4a/97/7b/bd-ab9b-4f00-b7b5-25f62f04eb45/sramp-relationships:null in workspace "default"
> at org.modeshape.jcr.AbstractJcrNode.getProperty(AbstractJcrNode.java:346)
> at org.modeshape.jcr.AbstractJcrNode.getProperty(AbstractJcrNode.java:108)
> at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.updateGenericRelationships(ArtifactToJCRNodeVisitor.java:267)
> at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.visitBase(ArtifactToJCRNodeVisitor.java:128)
> at org.overlord.sramp.common.visitors.HierarchicalArtifactVisitorAdapter.visit(HierarchicalArtifactVisitorAdapter.java:209)
> at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.visit(ArtifactToJCRNodeVisitor.java:310)
> at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.overlord.sramp.common.visitors.ArtifactVisitorHelper.visitArtifact(ArtifactVisitorHelper.java:41)
> at org.overlord.sramp.repository.jcr.JCRArtifactPersister.persistArtifactPhase1(JCRArtifactPersister.java:138)
> at org.overlord.sramp.repository.jcr.JCRPersistence.persistArtifact(JCRPersistence.java:177)
> ... 47 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (SRAMP-599) Batch upload through linked artifacts in a multipart POST/PUT
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-599?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated SRAMP-599:
------------------------------
Parent: (was: SRAMP-462)
Issue Type: Feature Request (was: Sub-task)
> Batch upload through linked artifacts in a multipart POST/PUT
> -------------------------------------------------------------
>
> Key: SRAMP-599
> URL: https://issues.jboss.org/browse/SRAMP-599
> Project: S-RAMP
> Issue Type: Feature Request
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> {quote}
> 2.3.5.2.1 Using Batch POST
> RFC 2387, "The MIME Multipart/Related Content-type" describes how to perform a multipart POST of binary documents. S-RAMP builds on this RFC to extend the IETF draft document "ATOM Multi-part Media Resource Creation" to support the simultaneous publishing of a collection of non-dependent and dependent resources and their associated metadata. With this approach it is possible, for example, to publish an XSD document which imports two other XSD documents by including it as well as its dependencies in a single POST to the repository.
> The Batch POST method requires an atom entry document as the root body part. This root atom entry document points to any dependent atom entry documents contained in other body parts using atom:link elements with an href attribute whose value is the Content-ID of the relevant body part. It also points at the actual document content by specifying the Content-ID of the relevant body part as the value of the src attribute in the atom:content element of the atom entry document. This approach provides complete linkage between a document and its dependencies and all corresponding binary resources.
> {quote}
> Although we implement the archive-based method of batch uploading, we do not currently support plain multipart for multiple artifacts.
> Support for both POST and updating through PUT is necessary.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (SRAMP-599) Batch upload through linked artifacts in a multipart POST/PUT
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-599?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-599:
-----------------------------------
Pulling this out of spec-compliance tracking -- going to push back on several related items with the TC.
> Batch upload through linked artifacts in a multipart POST/PUT
> -------------------------------------------------------------
>
> Key: SRAMP-599
> URL: https://issues.jboss.org/browse/SRAMP-599
> Project: S-RAMP
> Issue Type: Sub-task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> {quote}
> 2.3.5.2.1 Using Batch POST
> RFC 2387, "The MIME Multipart/Related Content-type" describes how to perform a multipart POST of binary documents. S-RAMP builds on this RFC to extend the IETF draft document "ATOM Multi-part Media Resource Creation" to support the simultaneous publishing of a collection of non-dependent and dependent resources and their associated metadata. With this approach it is possible, for example, to publish an XSD document which imports two other XSD documents by including it as well as its dependencies in a single POST to the repository.
> The Batch POST method requires an atom entry document as the root body part. This root atom entry document points to any dependent atom entry documents contained in other body parts using atom:link elements with an href attribute whose value is the Content-ID of the relevant body part. It also points at the actual document content by specifying the Content-ID of the relevant body part as the value of the src attribute in the atom:content element of the atom entry document. This approach provides complete linkage between a document and its dependencies and all corresponding binary resources.
> {quote}
> Although we implement the archive-based method of batch uploading, we do not currently support plain multipart for multiple artifacts.
> Support for both POST and updating through PUT is necessary.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (SRAMP-600) Support batch archive updates
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-600?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated SRAMP-600:
------------------------------
Description: BatchResource allows batch uploads through an archive, but supporting PUT for updating artifacts is also required. (was: BatchResource allows batch uploads through an archive. SRAMP-599 will support batch uploads though multipart.
However, both mechanisms must also support PUT for updating artifacts.)
> Support batch archive updates
> -----------------------------
>
> Key: SRAMP-600
> URL: https://issues.jboss.org/browse/SRAMP-600
> Project: S-RAMP
> Issue Type: Sub-task
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> BatchResource allows batch uploads through an archive, but supporting PUT for updating artifacts is also required.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years