December 2014 - overlord-issues - Jboss List Archives

[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: ------------------------------ Description: {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. was: {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. > 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

1
0
0 / 0

[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: ------------------------------ Summary: Batch upload through linked artifacts in a multipart POST/PUT (was: Batch upload through linked artifacts in a multipart POST) > 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. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-630) SRAMP-626 broke the ability to pull from the S-RAMP wagon

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-630?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-630. ------------------------------- Resolution: Done > SRAMP-626 broke the ability to pull from the S-RAMP wagon > --------------------------------------------------------- > > Key: SRAMP-630 > URL: https://issues.jboss.org/browse/SRAMP-630 > Project: S-RAMP > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.8.0.Final > > > SRAMP-626 was a little overzealous and broke the ability to pull from the Maven Wagon. Remove the exclusion of commons-compress -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-630) SRAMP-626 broke the ability to pull from the S-RAMP wagon

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-630?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-630: ------------------------------ Fix Version/s: 0.8.0.Final > SRAMP-626 broke the ability to pull from the S-RAMP wagon > --------------------------------------------------------- > > Key: SRAMP-630 > URL: https://issues.jboss.org/browse/SRAMP-630 > Project: S-RAMP > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.8.0.Final > > > SRAMP-626 was a little overzealous and broke the ability to pull from the Maven Wagon. Remove the exclusion of commons-compress -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-630) SRAMP-626 broke the ability to pull from the S-RAMP wagon

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-630: --------------------------------- Summary: SRAMP-626 broke the ability to pull from the S-RAMP wagon Key: SRAMP-630 URL: https://issues.jboss.org/browse/SRAMP-630 Project: S-RAMP Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer SRAMP-626 was a little overzealous and broke the ability to pull from the Maven Wagon. Remove the exclusion of commons-compress -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-638) Warning messages/exceptions about Errai classes not found

by Gary Brown (JIRA)

Gary Brown created RTGOV-638: -------------------------------- Summary: Warning messages/exceptions about Errai classes not found Key: RTGOV-638 URL: https://issues.jboss.org/browse/RTGOV-638 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Beta1 Appears that some Errai client side classes are being scanned for by weld: Caused by: java.lang.ClassNotFoundException: org.jboss.errai.marshalling.client.api.Marshaller from [Module "deployment.overlord-rtgov-ui.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.3.Final-redhat-1] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final-redhat-1] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-637) Kibana console not working on EAP with KeyCloak

by Gary Brown (JIRA)

Gary Brown created RTGOV-637: -------------------------------- Summary: Kibana console not working on EAP with KeyCloak Key: RTGOV-637 URL: https://issues.jboss.org/browse/RTGOV-637 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-636) Enable integration tests to run on EAP and/or Wildfly

by Gary Brown (JIRA)

Gary Brown created RTGOV-636: -------------------------------- Summary: Enable integration tests to run on EAP and/or Wildfly Key: RTGOV-636 URL: https://issues.jboss.org/browse/RTGOV-636 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Beta2 Currently integration tests only run against a pre-downloaded EAP. Now that Wildfly is supported, enable integration tests to be run against it, and download Wildfly if not available. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-628) Completely remove Fuse/Jetty/OSGi concepts

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-628?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-628: ------------------------------ Fix Version/s: (was: 1.0) > Completely remove Fuse/Jetty/OSGi concepts > ------------------------------------------ > > Key: SRAMP-628 > URL: https://issues.jboss.org/browse/SRAMP-628 > Project: S-RAMP > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > SRAMP-620 deprecated Fuse and Jetty support. In 1.0, take it further: > 1.) completely remove the modules > 2.) remove all OSGi dependencies > 3.) remove Felix annotations > 4.) replace "bundle" packaging with "jar" -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-628) Completely remove Fuse/Jetty/OSGi concepts

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-628?page=com.atlassian.jira.plugin.... ] Work on SRAMP-628 started by Brett Meyer. ----------------------------------------- > Completely remove Fuse/Jetty/OSGi concepts > ------------------------------------------ > > Key: SRAMP-628 > URL: https://issues.jboss.org/browse/SRAMP-628 > Project: S-RAMP > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > SRAMP-620 deprecated Fuse and Jetty support. In 1.0, take it further: > 1.) completely remove the modules > 2.) remove all OSGi dependencies > 3.) remove Felix annotations > 4.) replace "bundle" packaging with "jar" -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues December 2014