[JBoss JIRA] (SRAMPUI-76) Create a client-side service to queue artifact updates
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMPUI-76:
------------------------------------
Summary: Create a client-side service to queue artifact updates
Key: SRAMPUI-76
URL: https://issues.jboss.org/browse/SRAMPUI-76
Project: S-RAMP UI
Issue Type: Feature Request
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: Future (Unscheduled)
There is no save button on the Artifact Details page. Instead, each change the user makes will trigger an update of the artifact. If these are done too quickly there may be unintended consequences (updates happening out of order). Instead, add a service that will sequence the updates.
This service should also warn the end user if they try to navigate away from the browser UI app while updates are pending.
--
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, 8 months
[JBoss JIRA] (RTGOV-172) Represent switchyard service components
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-172?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-172:
----------------------------------
The benefit of representing the service type (e.g. swyd app) and components separately is that there is potential for diagrams (such as the service overview) to show the boundaries of the application.
> Represent switchyard service components
> ---------------------------------------
>
> Key: RTGOV-172
> URL: https://issues.jboss.org/browse/RTGOV-172
> Project: RTGov (Run Time Governance)
> Issue Type: Enhancement
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.M5
>
>
> Currently the individual service components included in a switchyard application are recorded as the service type in the activity events. However this means that the context (i.e. the switchyard application) is not recorded.
> However when considering switchyard applications from a management perspective, it may be more nature to consider the application as being the 'service', which exposes its capabilities via interfaces defined in the bindings.
> Therefore the switchyard app type could be recorded as the service type, and introduce a new field to define the type of the component.
> We then need to consider whether the inbound binding should be treated as a separate component? At present the binding interface is used in place of the one associated with the initial component - so the binding and the initial component are collapsed into a single set of events.
--
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, 8 months
[JBoss JIRA] (RTGOV-172) Represent switchyard service components
by Gary Brown (JIRA)
Gary Brown created RTGOV-172:
--------------------------------
Summary: Represent switchyard service components
Key: RTGOV-172
URL: https://issues.jboss.org/browse/RTGOV-172
Project: RTGov (Run Time Governance)
Issue Type: Enhancement
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M5
Currently the individual service components included in a switchyard application are recorded as the service type in the activity events. However this means that the context (i.e. the switchyard application) is not recorded.
However when considering switchyard applications from a management perspective, it may be more nature to consider the application as being the 'service', which exposes its capabilities via interfaces defined in the bindings.
Therefore the switchyard app type could be recorded as the service type, and introduce a new field to define the type of the component.
We then need to consider whether the inbound binding should be treated as a separate component? At present the binding interface is used in place of the one associated with the initial component - so the binding and the initial component are collapsed into a single set of events.
--
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, 8 months