[JBoss JIRA] (RTGOV-509) Large number of activities with the same ID in call trace gadget will not be displayed
by Gary Brown (JIRA)
Gary Brown created RTGOV-509:
--------------------------------
Summary: Large number of activities with the same ID in call trace gadget will not be displayed
Key: RTGOV-509
URL: https://issues.jboss.org/browse/RTGOV-509
Project: RTGov (Run Time Governance)
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Gary Brown
Assignee: Gary Brown
Large call traces can cause exceptions.
Issue is length of time to build the trace, if involving many queries, but also the size of the trace which then becomes impossible to display.
Need to investigate ways to cap the processing (i.e. number of subsequent queries performed to build the trace) and also ways to restrict the size of the displayed result.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (RTGOV-508) Test RTGov REST services with typed args/return values
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-508?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-508:
----------------------------------
Need to also add enunciate annotations to the JSON serializable classes for it to document them.
> Test RTGov REST services with typed args/return values
> ------------------------------------------------------
>
> Key: RTGOV-508
> URL: https://issues.jboss.org/browse/RTGOV-508
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.Final
>
>
> When initially porting RTGov onto Karaf (RTGOV-373) we used the built in JAX-RS support provided by CXF. However the version of Karaf we needed to use, to support Fuse 6.1, had some issues with the typed signature.
> The solution was to untyped the methods and just pass strings, and handle json marshalling in the REST service.
> Now that REST API docs are being generated, this causes the problem that it does not document the true types being used.
> We are now using RESTEasy to provide the JAX-RS services, so we need to retest with typed signatures in Karaf/Fuse, to see whether they now work. This will allow better API documentation to be automatically produced.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (SRAMP-471) Maven Facade: Implement maven deploy support
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-471?page=com.atlassian.jira.plugin.... ]
Eric Wittmann resolved SRAMP-471.
---------------------------------
Resolution: Done
> Maven Facade: Implement maven deploy support
> --------------------------------------------
>
> Key: SRAMP-471
> URL: https://issues.jboss.org/browse/SRAMP-471
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: S-RAMP API
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
> Fix For: 0.5.0.Final
>
>
> The maven facade currently only supports maven GET related operations (e.g. pulling artifacts out of s-ramp using the standard maven http protocol support). We should enhance the facade to also support the maven PUT/POST http protocol. In other words, support whatever maven does when you do this:
> {code}
> mvn deploy
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (SRAMP-471) Maven Facade: Implement maven deploy support
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-471?page=com.atlassian.jira.plugin.... ]
Eric Wittmann closed SRAMP-471.
-------------------------------
> Maven Facade: Implement maven deploy support
> --------------------------------------------
>
> Key: SRAMP-471
> URL: https://issues.jboss.org/browse/SRAMP-471
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: S-RAMP API
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
> Fix For: 0.5.0.Final
>
>
> The maven facade currently only supports maven GET related operations (e.g. pulling artifacts out of s-ramp using the standard maven http protocol support). We should enhance the facade to also support the maven PUT/POST http protocol. In other words, support whatever maven does when you do this:
> {code}
> mvn deploy
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years