• Type: Sub-task
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 0.6.0.Final
    • Component/s: None
    • Labels:


      Section 4.5 of the S-RAMP spec discusses stored queries. We need to add support for them.

      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.

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  brmeyer Brett Meyer
                  eric.wittmann Eric Wittman
                • Votes:
                  0 Vote for this issue
                  1 Start watching this issue


                  • Created: