[JBoss JIRA] (SRAMP-464) Docker image
by Brett Meyer (JIRA)
Brett Meyer created SRAMP-464:
---------------------------------
Summary: Docker image
Key: SRAMP-464
URL: https://issues.jboss.org/browse/SRAMP-464
Project: S-RAMP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Brett Meyer
Assignee: Brett Meyer
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (SRAMP-169) Organization hierarchy
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-169?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated SRAMP-169:
------------------------------
Parent: SRAMP-462
Issue Type: Sub-task (was: Feature Request)
> Organization hierarchy
> ----------------------
>
> Key: SRAMP-169
> URL: https://issues.jboss.org/browse/SRAMP-169
> Project: S-RAMP
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Gary Brown
> Assignee: Kurt Stam
> Fix For: 0.6.0
>
>
> 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 was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (SRAMP-462) S-RAMP 1.0 spec compliance and TCK
by Brett Meyer (JIRA)
Brett Meyer created SRAMP-462:
---------------------------------
Summary: S-RAMP 1.0 spec compliance and TCK
Key: SRAMP-462
URL: https://issues.jboss.org/browse/SRAMP-462
Project: S-RAMP
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Brett Meyer
Assignee: Brett Meyer
Parent task for tracking all S-RAMP 1.0 spec support and TCK development.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (SRAMP-449) Ontologies Page: download icon not being pulled fully right
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-449?page=com.atlassian.jira.plugin.... ]
Brett Meyer resolved SRAMP-449.
-------------------------------
Fix Version/s: 0.5.0.Alpha1
Resolution: Done
> Ontologies Page: download icon not being pulled fully right
> -----------------------------------------------------------
>
> Key: SRAMP-449
> URL: https://issues.jboss.org/browse/SRAMP-449
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: UI
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
> Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> The Ontologies page now has a download icon for each ontology. The icon is not being pulled fully to the right, because the table column it is being displayed within is too large. In other words, the icon is being displayed at the left-most part of the "icons" column of the table. A quick fix would be to set the column width for the icons column to 1%.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-433:
-----------------------------------
Create an extendable API, but JMS will probably be the first impl. DTGov will be one subscriber (instead of the current polling).
> Create a proper Event producer for s-ramp
> -----------------------------------------
>
> Key: SRAMP-433
> URL: https://issues.jboss.org/browse/SRAMP-433
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about.
> Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ]
Brett Meyer reassigned SRAMP-433:
---------------------------------
Assignee: Brett Meyer (was: Eric Wittmann)
> Create a proper Event producer for s-ramp
> -----------------------------------------
>
> Key: SRAMP-433
> URL: https://issues.jboss.org/browse/SRAMP-433
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about.
> Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months