March 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-169) Organization hierarchy

by Gary Brown (JIRA)

Gary Brown created SRAMP-169: -------------------------------- Summary: Organization hierarchy Key: SRAMP-169 URL: https://issues.jboss.org/browse/SRAMP-169 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Kurt Stam Fix For: 0.3.0 - Future (Unscheduled) The SRAMP spec defines an Organization entity (derived from HumanActor) that can be related to a ServiceImplementation using the 'provides' relationship. In large organizations it may be necessary to define more of a organizational structure, to correctly associate the services with the appropriate business units, departments, etc. that are responsible for the service. The other issue is whether a 'provides' relationship is enough. This may indicate the implementers of the service, but not necessarily the support contact if there is a problem with the service. So potentially there should also be a 'supports' relationship that can optionally be used where the support is provided by a different team. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-168) Create a TCK test suite

by Kurt Stam (JIRA)

Kurt Stam created SRAMP-168: ------------------------------- Summary: Create a TCK test suite Key: SRAMP-168 URL: https://issues.jboss.org/browse/SRAMP-168 Project: S-RAMP Issue Type: Task Security Level: Public (Everyone can see) Components: Distro Reporter: Kurt Stam Assignee: Kurt Stam Adding a Technical Compatibility Kit. - add examples from spec docs - add tests to validate the implementation adheres to the spec -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-49) Artifact Details - Document source (read only)

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-49?page=com.atlassian.jira.plugin... ] Eric Wittmann closed SRAMPUI-49. -------------------------------- > Artifact Details - Document source (read only) > ----------------------------------------------- > > Key: SRAMPUI-49 > URL: https://issues.jboss.org/browse/SRAMPUI-49 > Project: S-RAMP UI > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 4 > > > Display the source for the selected Document on the Artifact Details page. There is a tab in the UI for this - the tab should only be present if the artifact is a Document with a text based content-type. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-49) Artifact Details - Document source (read only)

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-49?page=com.atlassian.jira.plugin... ] Eric Wittmann resolved SRAMPUI-49. ---------------------------------- Resolution: Done This was the last task completed on the 1.0 branch prior to merging 1.0 into master to prep for the next release. > Artifact Details - Document source (read only) > ----------------------------------------------- > > Key: SRAMPUI-49 > URL: https://issues.jboss.org/browse/SRAMPUI-49 > Project: S-RAMP UI > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 4 > > > Display the source for the selected Document on the Artifact Details page. There is a tab in the UI for this - the tab should only be present if the artifact is a Document with a text based content-type. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-49) Artifact Details - Document source (read only)

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-49?page=com.atlassian.jira.plugin... ] Work on SRAMPUI-49 started by Eric Wittmann. > Artifact Details - Document source (read only) > ----------------------------------------------- > > Key: SRAMPUI-49 > URL: https://issues.jboss.org/browse/SRAMPUI-49 > Project: S-RAMP UI > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 4 > > > Display the source for the selected Document on the Artifact Details page. There is a tab in the UI for this - the tab should only be present if the artifact is a Document with a text based content-type. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-167) Add support for one of the non-Document artifact models (e.g. ServiceImplementation)

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-167: ----------------------------------- Summary: Add support for one of the non-Document artifact models (e.g. ServiceImplementation) Key: SRAMP-167 URL: https://issues.jboss.org/browse/SRAMP-167 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: 0.2.0 - Milestone 4 We need to make sure that we can support the logical (non-document) artifact types. The mechanism for creating them is different (there's no POST of a 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, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-166) Support both ExtendedArtifactType *and* the new ExtendedDocument types

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-166: ----------------------------------- Summary: Support both ExtendedArtifactType *and* the new ExtendedDocument types Key: SRAMP-166 URL: https://issues.jboss.org/browse/SRAMP-166 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Atom Binding, Client, Core, Persistence, S-RAMP API Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: 0.2.0 - Milestone 4 We split the 'ext' model into two different types: ExtendedArtifactType and ExtendedDocument. Need to support both. Clients now should use the latter type if their custom artifact has content. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-165) Implement negation (not() function) for S-RAMP queries

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-165: ----------------------------------- Summary: Implement negation (not() function) for S-RAMP queries Key: SRAMP-165 URL: https://issues.jboss.org/browse/SRAMP-165 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: 0.2.0 - Milestone 4 We added support for negation in s-ramp queries to the spec recently. Need to implement that function. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-164) Update s-ramp-api with latest S-RAMP schema(s) (regen code)

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-164: ----------------------------------- Summary: Update s-ramp-api with latest S-RAMP schema(s) (regen code) Key: SRAMP-164 URL: https://issues.jboss.org/browse/SRAMP-164 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Components: S-RAMP API Reporter: Eric Wittmann Assignee: Kurt Stam Fix For: 0.2.0 - Milestone 4 Once we finalize the spec, we need to regen the API code based on the latest schemas. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (BAM-140) Change BAM to RTGov

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/BAM-140?page=com.atlassian.jira.plugin.sy... ] Gary Brown resolved BAM-140. ---------------------------- Resolution: Done > Change BAM to RTGov > ------------------- > > Key: BAM-140 > URL: https://issues.jboss.org/browse/BAM-140 > Project: Business Activity Monitoring > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > Rename the git repo, and any reference to bam within the repository to use the 'rtgov' sub-project name. -- 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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues March 2013