[JBoss JIRA] (SRAMP-408) Tab completion no longer works in s-ramp CLI
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-408:
-----------------------------------
Summary: Tab completion no longer works in s-ramp CLI
Key: SRAMP-408
URL: https://issues.jboss.org/browse/SRAMP-408
Project: S-RAMP
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Eric Wittmann
Assignee: David virgil naranjo
Fix For: 0.5.0 - API Management
The recent change to using AESH has broken tab-completion. For example, I typed the following:
{code}
s-ramp> conn
{code}
Then I hit "tab" and I got this:
{code}
s-ramp> connmp:connect
{code}
And the cursor was placed three spaces beyond "connect". After that tab didn't work at all because the command wasn't recognized (obviously).
If I type s-ramp:connect manually and *then* hit tab, I get this:
{code}
s-ramp> s-ramp:connect t:8080/s-ramp-server
{code}
Also tab-completion of just the namespace adds an extra space at the end. If I back up one and use tab, I get the list of commands in the namespace but it won't actually complete any of them.
So I think there is some fundamental problem with the tab completion. I tested on Windows cygwin. I will now go test on Fedora.
--
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
10 years, 8 months
[JBoss JIRA] (RTGOV-397) Include service dependency graph in new UI
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-397?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-397:
----------------------------------
Rather than obtain the service dependency graph via the REST service, the UI should retrieve it as part of the ServiceBean, in a similar way to how the CallTraceBean is used to retrieve the call trace, as part of the SituationBean.
So (for example) create a ServiceDependencyBean which is associated with the ServiceBean, and would provide the SVG image.
The way in which the bean is populated will be dealt with in a separate jira.
> Include service dependency graph in new UI
> ------------------------------------------
>
> Key: RTGOV-397
> URL: https://issues.jboss.org/browse/RTGOV-397
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Components: User Interface
> Reporter: Gary Brown
> Assignee: Michael Clay
> Fix For: 2.0.0.Final
>
>
> On the service details page, have a tab that can be used to show "Service Dependencies".
> This page should retrieve a SVG image from the REST service located at:
> http://localhost:8080/overlord-rtgov/service/dependency/overview?serviceT...<serviceType>
> When used with the older version of RTGov, the serviceType will be ignored and a complete service dependency graph returned. However in the new version of RTGov, this value will be used to focus the graph on the relevant dependencies for that service type.
--
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
10 years, 8 months
[JBoss JIRA] (RTGOV-415) ElasticSearch Activity Store implementation
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-415:
----------------------------------
Extending is fine.
> ElasticSearch Activity Store implementation
> -------------------------------------------
>
> Key: RTGOV-415
> URL: https://issues.jboss.org/browse/RTGOV-415
> Project: RTGov (Run Time Governance)
> Issue Type: Sub-task
> Reporter: Gary Brown
> Assignee: ivan mckinley
> Fix For: 2.0.0.Final
>
>
> Although it is not currently clear whether organisations would rely on ElasticSearch as a database for their activity information, it will be good to be able to offer it as an alternative.
> If configured, then it will store the ActivityUnit, and any subsequent EPN can be used to store the derived information (e.g. situations and response times).
> ElasticSearch has improved its support for backup/restore, so could potentially be used as a primary db for this type of information - although it is not transactional.
> The module should be defined in modules/activity-management/activity-store-es (or elasticsearch - whatever is consistent with RTGOV-342).
--
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
10 years, 8 months
[JBoss JIRA] (RTGOV-415) ElasticSearch Activity Store implementation
by ivan mckinley (JIRA)
[ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.... ]
ivan mckinley commented on RTGOV-415:
-------------------------------------
Hey Gary,
I have the ElasticsearchActivityStore extending ElasticSearchKeyValueStore and implementing ActivitiyStore interface.
Do you have any objections to this design or would it be preferable to simply reference ElasticSearchKeyValueStore. we basically get the CRUD operations available on KeyValueStore interface for free.
@Singleton
public class ElasticsearchActivityStore extends ElasticSearchKeyValueStore implements ActivityStore
> ElasticSearch Activity Store implementation
> -------------------------------------------
>
> Key: RTGOV-415
> URL: https://issues.jboss.org/browse/RTGOV-415
> Project: RTGov (Run Time Governance)
> Issue Type: Sub-task
> Reporter: Gary Brown
> Assignee: ivan mckinley
> Fix For: 2.0.0.Final
>
>
> Although it is not currently clear whether organisations would rely on ElasticSearch as a database for their activity information, it will be good to be able to offer it as an alternative.
> If configured, then it will store the ActivityUnit, and any subsequent EPN can be used to store the derived information (e.g. situations and response times).
> ElasticSearch has improved its support for backup/restore, so could potentially be used as a primary db for this type of information - although it is not transactional.
> The module should be defined in modules/activity-management/activity-store-es (or elasticsearch - whatever is consistent with RTGOV-342).
--
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
10 years, 8 months
[JBoss JIRA] (SRAMP-140) Create unit tests for shell commands
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-140?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-140:
-------------------------------------
Let's hold off on this task until we replace the current CLI implementation with one based on AESH.
> Create unit tests for shell commands
> ------------------------------------
>
> Key: SRAMP-140
> URL: https://issues.jboss.org/browse/SRAMP-140
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
> Priority: Minor
> Fix For: 0.5.0 - API Management
>
>
> I currently have poor junit coverage in the s-ramp-shell project. I need to create some unit tests, both for executing commands as well as for ancillary functionality like tab-completion.
--
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
10 years, 8 months
[JBoss JIRA] (RTGOV-438) Remove war plugin version from UI/fuse6 pom
by Gary Brown (JIRA)
Gary Brown created RTGOV-438:
--------------------------------
Summary: Remove war plugin version from UI/fuse6 pom
Key: RTGOV-438
URL: https://issues.jboss.org/browse/RTGOV-438
Project: RTGov (Run Time Governance)
Issue Type: Task
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.1.0.Final
Currently the RTGov UI war for fuse6 requires the 2.1.1 version of the maven war plugin, versus the default 2.3 version.
This is because version 2.3 creates a badly formatted manifest for the imported packages and classpath entries, causing it problem when installing into fuse.
Its possible that the entries just need to be defined on a single line, but initial experiment with this failed to display the UI, indicating a problem with the classpath.
--
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
10 years, 8 months