[JBoss JIRA] (SRAMPUI-45) Filtering - classifications
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMPUI-45:
------------------------------------
Summary: Filtering - classifications
Key: SRAMPUI-45
URL: https://issues.jboss.org/browse/SRAMPUI-45
Project: S-RAMP UI
Issue Type: Task
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: Milestone 4
Filter by classifications. This requires that there be a way to query the server for the list of ontologies, then pull them all down and display them in the UI (so that the user can pick 0 or more classes in the ontology).
--
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, 7 months
[JBoss JIRA] (SRAMPUI-44) Filtering - custom properties
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMPUI-44:
------------------------------------
Summary: Filtering - custom properties
Key: SRAMPUI-44
URL: https://issues.jboss.org/browse/SRAMPUI-44
Project: S-RAMP UI
Issue Type: Task
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: Milestone 4
Implement filtering by custom properties. This includes the ability of an administrator to configure the custom properties that can be used for filtering and (optionally) the list of possible values (to show in a drop-down).
--
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, 7 months
[JBoss JIRA] (SRAMP-161) S-RAMP Client: obey endpoints found in /servicedocument
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-161:
-----------------------------------
Summary: S-RAMP Client: obey endpoints found in /servicedocument
Key: SRAMP-161
URL: https://issues.jboss.org/browse/SRAMP-161
Project: S-RAMP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: S-RAMP API
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: 0.2.0 - Milestone 4
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, 7 months