May 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-161) S-RAMP Client: obey endpoints found in /servicedocument

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-161?page=com.atlassian.jira.plugin.... ] Kurt Stam updated SRAMP-161: ---------------------------- Fix Version/s: 0.3.1 - jBPM - bugfix 1 (was: 0.3.0 - JBPM6 Integration) > S-RAMP Client: obey endpoints found in /servicedocument > ------------------------------------------------------- > > Key: SRAMP-161 > URL: https://issues.jboss.org/browse/SRAMP-161 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: S-RAMP API > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 0.3.1 - jBPM - bugfix 1 > > > Currently we use the non-normative URL formats suggested in the S-RAMP Atom Binding document as presumptive endpoints for the various artifact types. Instead, the Atom API Java client should obey the endpoints it finds in the /servicedocument. This means it will *always* query that service document. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-161) S-RAMP Client: obey endpoints found in /servicedocument

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-161?page=com.atlassian.jira.plugin.... ] Kurt Stam updated SRAMP-161: ---------------------------- Issue Type: Bug (was: Feature Request) > S-RAMP Client: obey endpoints found in /servicedocument > ------------------------------------------------------- > > Key: SRAMP-161 > URL: https://issues.jboss.org/browse/SRAMP-161 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: S-RAMP API > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 0.3.0 - JBPM6 Integration > > > Currently we use the non-normative URL formats suggested in the S-RAMP Atom Binding document as presumptive endpoints for the various artifact types. Instead, the Atom API Java client should obey the endpoints it finds in the /servicedocument. This means it will *always* query that service document. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-171) Enable WSLA artifacts to be associated with a service

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-171?page=com.atlassian.jira.plugin.... ] Kurt Stam commented on SRAMP-171: --------------------------------- Add a WSLADocument Extented Artifact > Enable WSLA artifacts to be associated with a service > ----------------------------------------------------- > > Key: SRAMP-171 > URL: https://issues.jboss.org/browse/SRAMP-171 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Kurt Stam > Fix For: 0.3.0 - JBPM6 Integration > > > WSLA will be used to represent the service level agreement properties related to response time and availability for a service. Therefore it should be possible to represent these documents in the repository and establish a relationship between them and the service contracts. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-189) Upload Switchyard SCA diagram automatically from maven

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-189?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-189: -------------------------------- Fix Version/s: 0.4.0 - API Management (was: 0.3.0 - JBPM6 Integration) > Upload Switchyard SCA diagram automatically from maven > ------------------------------------------------------ > > Key: SRAMP-189 > URL: https://issues.jboss.org/browse/SRAMP-189 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.4.0 - API Management > > > Switchyard is planning on generating an SCA diagram for applications during build. When uploading the application to s-ramp this diagram should be included and appropriately linked. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-186) Auditing: properly audit relationship changes

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-186?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-186. ------------------------------- > Auditing: properly audit relationship changes > --------------------------------------------- > > Key: SRAMP-186 > URL: https://issues.jboss.org/browse/SRAMP-186 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Critical > Fix For: 0.3.0 - JBPM6 Integration > > > The auditing implementation currently doesn't properly handle changes to relationships. The impl should be enhanced to include relationships. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-187) Auditing: properly audit classifiers

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-187?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-187. ------------------------------- > Auditing: properly audit classifiers > ------------------------------------ > > Key: SRAMP-187 > URL: https://issues.jboss.org/browse/SRAMP-187 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Critical > Fix For: 0.3.0 - JBPM6 Integration > > > The auditing implementation currently doesn't properly handle classifiers (because it's a multi-value property in JCR). The impl should be enhanced to handle classifiers in an appropriate way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-188) Auditing: handle phase2 commits for artifact creates

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-188?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-188. --------------------------------- Resolution: Won't Fix I have decided to re-implement auditing without using the jcr observer pattern. This decision deprecates this task. > Auditing: handle phase2 commits for artifact creates > ---------------------------------------------------- > > Key: SRAMP-188 > URL: https://issues.jboss.org/browse/SRAMP-188 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.0 - JBPM6 Integration > > > When artifacts are added to the s-ramp repository the JCR nodes are written in two phases. In the case of non-derived artifacts, the second phase will updated the JCR node with any meta-data added to it by the Deriver. > In the case of derived artifacts, the second phase will update the JCR node with most of the primary artifact meta-data. > In both cases, the audit handler should update the appropriate audit entry JCR node with information recorded during the second phase commit. It should not create a new audit entry. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-186) Auditing: properly audit relationship changes

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-186?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-186. --------------------------------- Resolution: Done I have decided to re-implement auditing without using the jcr observer pattern. This decision deprecates this task. > Auditing: properly audit relationship changes > --------------------------------------------- > > Key: SRAMP-186 > URL: https://issues.jboss.org/browse/SRAMP-186 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Critical > Fix For: 0.3.0 - JBPM6 Integration > > > The auditing implementation currently doesn't properly handle changes to relationships. The impl should be enhanced to include relationships. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-187) Auditing: properly audit classifiers

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-187?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-187. --------------------------------- Resolution: Done I have decided to re-implement auditing without using the jcr observer pattern. This decision deprecates this task. > Auditing: properly audit classifiers > ------------------------------------ > > Key: SRAMP-187 > URL: https://issues.jboss.org/browse/SRAMP-187 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Critical > Fix For: 0.3.0 - JBPM6 Integration > > > The auditing implementation currently doesn't properly handle classifiers (because it's a multi-value property in JCR). The impl should be enhanced to handle classifiers in an appropriate way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-188) Auditing: handle phase2 commits for artifact creates

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-188?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-188. ------------------------------- > Auditing: handle phase2 commits for artifact creates > ---------------------------------------------------- > > Key: SRAMP-188 > URL: https://issues.jboss.org/browse/SRAMP-188 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.0 - JBPM6 Integration > > > When artifacts are added to the s-ramp repository the JCR nodes are written in two phases. In the case of non-derived artifacts, the second phase will updated the JCR node with any meta-data added to it by the Deriver. > In the case of derived artifacts, the second phase will update the JCR node with most of the primary artifact meta-data. > In both cases, the audit handler should update the appropriate audit entry JCR node with information recorded during the second phase commit. It should not create a new audit entry. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues May 2013