October 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-94) Handle fine-grained Atom view for relationships

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-94?page=com.atlassian.jira.plugin.s... ] Brett Meyer updated SRAMP-94: ----------------------------- Parent: SRAMP-603 Issue Type: Sub-task (was: Feature Request) > Handle fine-grained Atom view for relationships > ----------------------------------------------- > > Key: SRAMP-94 > URL: https://issues.jboss.org/browse/SRAMP-94 > Project: S-RAMP > Issue Type: Sub-task > Components: Atom Binding > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > > Relationships have their own separate Atom API endpoints. For example, you can get a feed of just the relationships for an artifact. In addition, you cn add (and I believe delete) individual relationships directly via this mechanism. This task should probably result in a new RelationshipResource RESTEasy class. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-603) Implement the Atom binding's "fine-grained views"

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-603: --------------------------------- Summary: Implement the Atom binding's "fine-grained views" Key: SRAMP-603 URL: https://issues.jboss.org/browse/SRAMP-603 Project: S-RAMP Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-110) Implement fine-grained classification view in the Atom API

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-110?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-110: ------------------------------ Parent: SRAMP-603 Issue Type: Sub-task (was: Feature Request) > Implement fine-grained classification view in the Atom API > ---------------------------------------------------------- > > Key: SRAMP-110 > URL: https://issues.jboss.org/browse/SRAMP-110 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > > The spec defines fine-grained views, including one for the classifications. This allows clients to get a manipulate (add, delete, get feed) the classifications for an artifact in the S-RAMP repository directly, removing the need to deal with the whole artifact at once. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-602) Implement fine-grained Properties view in the Atom API

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-602?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-602: ------------------------------ Parent: SRAMP-603 Issue Type: Sub-task (was: Feature Request) > Implement fine-grained Properties view in the Atom API > ------------------------------------------------------ > > Key: SRAMP-602 > URL: https://issues.jboss.org/browse/SRAMP-602 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > http://docs.oasis-open.org/s-ramp/s-ramp/v1.0/cs01/part2-atom-binding/s-r... > Although not required, the spec suggests implementing a fine-grained view for managing artifact *properties*, similar to classifications (SRAMP-110) and relationships (SRAMP-94) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-602) Implement fine-grained Properties view in the Atom API

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-602: --------------------------------- Summary: Implement fine-grained Properties view in the Atom API Key: SRAMP-602 URL: https://issues.jboss.org/browse/SRAMP-602 Project: S-RAMP Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer http://docs.oasis-open.org/s-ramp/s-ramp/v1.0/cs01/part2-atom-binding/s-r... Although not required, the spec suggests implementing a fine-grained view for managing artifact *properties*, similar to classifications (SRAMP-110) and relationships (SRAMP-94) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-601) Support deleting an artifact's content

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-601: --------------------------------- Summary: Support deleting an artifact's content Key: SRAMP-601 URL: https://issues.jboss.org/browse/SRAMP-601 Project: S-RAMP Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer 2.3.5.5 requires that we support deleting an artifact's *content*, which should remove it's media link. We currently only support deleting the artifact itself. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-600) Support batch updates

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-600: --------------------------------- Summary: Support batch 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. SRAMP-599 will support batch uploads though multipart. However, both mechanisms must also support PUT for updating artifacts. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-599) Batch upload through linked artifacts in a multipart POST

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-599: --------------------------------- Summary: Batch upload through linked artifacts in a multipart POST 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.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-603) Refreshing service list in RTGov UI waits indefinitely

by Gary Brown (JIRA)

Gary Brown created RTGOV-603: -------------------------------- Summary: Refreshing service list in RTGov UI waits indefinitely Key: RTGOV-603 URL: https://issues.jboss.org/browse/RTGOV-603 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final When refreshing the services list, it appears to wait indefinitely. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-602) Fuse: Querying Graph Dependency via REST fails with ClassNotFoundException

by Andrej Vano (JIRA)

Andrej Vano created RTGOV-602: --------------------------------- Summary: Fuse: Querying Graph Dependency via REST fails with ClassNotFoundException Key: RTGOV-602 URL: https://issues.jboss.org/browse/RTGOV-602 Project: RTGov (Run Time Governance) Issue Type: Bug Affects Versions: 2.0.0.Final Environment: fuse + switchyard 2.0.0.Alpha3 + rtgov 2.0.0.Final Reporter: Andrej Vano Assignee: Gary Brown Fix For: 2.1.0.Final Querying the graph dependency via REST on fuse fails with java.lang.ClassNotFoundException: javax.enterprise.context.spi.CreationalContext not found by rtgov-common Full error response is here: http://pastebin.test.redhat.com/240370 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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 October 2014