September 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-23) Statically validate a parsed S-RAMP Query

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-23?page=com.atlassian.jira.plugin.s... ] Brett Meyer updated SRAMP-23: ----------------------------- Parent: (was: SRAMP-21) Issue Type: Feature Request (was: Sub-task) > Statically validate a parsed S-RAMP Query > ----------------------------------------- > > Key: SRAMP-23 > URL: https://issues.jboss.org/browse/SRAMP-23 > Project: S-RAMP > Issue Type: Feature Request > Components: Core > Affects Versions: 0.6.0 > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 0.6.0 > > > Implement a validator that can take an S-RAMP Query and ensure that it is valid (does not violate any of the restrictions imposed by the S-RAMP Query API specification). > The result should simply be a validator that accepts a parsed S-RAMP Query and throws an exception if the Query is invalid. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-23) Statically validate a parsed S-RAMP Query

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-23?page=com.atlassian.jira.plugin.s... ] Brett Meyer commented on SRAMP-23: ---------------------------------- Moving out of SRAMP-21 -- not required by spec > Statically validate a parsed S-RAMP Query > ----------------------------------------- > > Key: SRAMP-23 > URL: https://issues.jboss.org/browse/SRAMP-23 > Project: S-RAMP > Issue Type: Sub-task > Components: Core > Affects Versions: 0.6.0 > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 0.6.0 > > > Implement a validator that can take an S-RAMP Query and ensure that it is valid (does not violate any of the restrictions imposed by the S-RAMP Query API specification). > The result should simply be a validator that accepts a parsed S-RAMP Query and throws an exception if the Query is invalid. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-29) Add support for Stored Queries

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-29?page=com.atlassian.jira.plugin.s... ] Brett Meyer resolved SRAMP-29. ------------------------------ Resolution: Done > Add support for Stored Queries > ------------------------------ > > Key: SRAMP-29 > URL: https://issues.jboss.org/browse/SRAMP-29 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > Fix For: 0.6.0 > > > Section 4.5 of the S-RAMP spec discusses stored queries. We need to add support for them. > {quote} > S-RAMP provides support for storing queries in the repository using the StoredQuery Artifact Type. This can be convenient because it allows quick execution of a frequently performed query. The syntax associated with creation, retrieval, update and deletion of a Stored Query is binding specific. Refer to the appropriate binding document of this specification for details. > > The StoredQuery Artifact Type does NOT extend BaseArtifactType as do most other Artifact Types in S-RAMP, which means it is simpler and possesses only these built-in attributes: > queryName: The name of the Stored Query instance. This must be unique. > queryExpression: The specification of the query expression. > > A StoredQuery MAY also contain a list of propertyName values. These are used to indicate to the server that the results returned from the execution of the query SHALL include values for those property names when they are present in the artifact instance(s) returned. This can be valuable in bindings that may not necessarily return the complete artifact in query results. The actual format of the query response is binding specific. > {quote} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-566) [resubmit] RemoteMessage#context is empty

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-566?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-566: ----------------------------------------------- Rick Wagner <rwagner(a)redhat.com> changed the Status of [bug 1146207|https://bugzilla.redhat.com/show_bug.cgi?id=1146207] from NEW to ASSIGNED > [resubmit] RemoteMessage#context is empty > ----------------------------------------- > > Key: RTGOV-566 > URL: https://issues.jboss.org/browse/RTGOV-566 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Michael Clay > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > because RemoteMessage#context is empty/not used there is no way to pass > properties required for the implementation of the resubmitted/retried service invocation (e.g. SOAPHeader are stored as message properties) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-566) [resubmit] RemoteMessage#context is empty

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-566?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated RTGOV-566: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1146207 > [resubmit] RemoteMessage#context is empty > ----------------------------------------- > > Key: RTGOV-566 > URL: https://issues.jboss.org/browse/RTGOV-566 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Michael Clay > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > because RemoteMessage#context is empty/not used there is no way to pass > properties required for the implementation of the resubmitted/retried service invocation (e.g. SOAPHeader are stored as message properties) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-556) RTGov UI no longer working on FSW 6.0

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-556?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-556: ----------------------------------------------- Rick Wagner <rwagner(a)redhat.com> changed the Status of [bug 1146206|https://bugzilla.redhat.com/show_bug.cgi?id=1146206] from NEW to ASSIGNED > RTGov UI no longer working on FSW 6.0 > ------------------------------------- > > Key: RTGOV-556 > URL: https://issues.jboss.org/browse/RTGOV-556 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Attachments: overlord-rtgov-elasticsearch.properties > > > RTGov UI beta 1 worked on FSW 6.0, but subsequent changes to rtgov have caused it to stop working. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-556) RTGov UI no longer working on FSW 6.0

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-556?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated RTGOV-556: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1146206 > RTGov UI no longer working on FSW 6.0 > ------------------------------------- > > Key: RTGOV-556 > URL: https://issues.jboss.org/browse/RTGOV-556 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Attachments: overlord-rtgov-elasticsearch.properties > > > RTGov UI beta 1 worked on FSW 6.0, but subsequent changes to rtgov have caused it to stop working. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-29) Add support for Stored Queries

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-29?page=com.atlassian.jira.plugin.s... ] Brett Meyer updated SRAMP-29: ----------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/494 > Add support for Stored Queries > ------------------------------ > > Key: SRAMP-29 > URL: https://issues.jboss.org/browse/SRAMP-29 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > Fix For: 0.6.0 > > > Section 4.5 of the S-RAMP spec discusses stored queries. We need to add support for them. > {quote} > S-RAMP provides support for storing queries in the repository using the StoredQuery Artifact Type. This can be convenient because it allows quick execution of a frequently performed query. The syntax associated with creation, retrieval, update and deletion of a Stored Query is binding specific. Refer to the appropriate binding document of this specification for details. > > The StoredQuery Artifact Type does NOT extend BaseArtifactType as do most other Artifact Types in S-RAMP, which means it is simpler and possesses only these built-in attributes: > queryName: The name of the Stored Query instance. This must be unique. > queryExpression: The specification of the query expression. > > A StoredQuery MAY also contain a list of propertyName values. These are used to indicate to the server that the results returned from the execution of the query SHALL include values for those property names when they are present in the artifact instance(s) returned. This can be valuable in bindings that may not necessarily return the complete artifact in query results. The actual format of the query response is binding specific. > {quote} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-395: ----------------------------------------------- Rick Wagner <rwagner(a)redhat.com> changed the Status of [bug 1114732|https://bugzilla.redhat.com/show_bug.cgi?id=1114732] from VERIFIED to CLOSED > S-RAMP allows artifacts to be created with invalid characters in the Artifact Type > ---------------------------------------------------------------------------------- > > Key: SRAMP-395 > URL: https://issues.jboss.org/browse/SRAMP-395 > Project: S-RAMP > Issue Type: Bug > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Alpha1 > > > There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI: > {code} > s-ramp:upload /path/to/file.ext "Invalid Type" > s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here." > {code} > The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up. > We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer). > For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-569) Create maven plugin to merge .properties files

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-569?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-569. ------------------------------- Resolution: Done > Create maven plugin to merge .properties files > ---------------------------------------------- > > Key: SRAMP-569 > URL: https://issues.jboss.org/browse/SRAMP-569 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: David virgil naranjo > Fix For: 0.6.0 > > > SRAMP-566 removes Fuse from s-ramp-installer. Instead, Fuse configuration is scripted through s-ramp-karaf-commands. That project currently controls its own versions of sramp.properties, sramp-ui.properties, etc. This was originally done since some of the values are static and *specific* to Fuse. > However, several values remain unchanged when compared to the other platforms. It would be better if s-ramp-karaf-commands/pom.xml was able to pull ../s-ramp-installer/**/*.properties and merge it with .properties still controlled in s-ramp-karaf-commands. However, the s-ramp-karaf-commands version would contain *only* the Fuse specific values. > Essentially, we're relying on s-ramp-installer's versions during buildtime, but overriding with any necessary Fuse values in s-ramp-karaf-commands. A custom Maven plugin to support this should be incredibly easy. Use Java's Properties, load the first version, then load and override with the 2nd. See http://beardedgeeks.googlecode.com/svn/docs/maven-merge-properties-plugin... for inspiration. > Note that this is also needed for overlord-commons-karaf-commands (configure.dtd, overlord.properties, etc.) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues September 2014