March 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-258) Create a tomcat compatible deployment/package

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-258?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-258. --------------------------------- Fix Version/s: 0.4.0 - API Management (was: 0.3.1 - jBPM - bugfix 1) Resolution: Done The s-ramp installer now supports tomcat. > Create a tomcat compatible deployment/package > --------------------------------------------- > > Key: SRAMP-258 > URL: https://issues.jboss.org/browse/SRAMP-258 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.4.0 - API Management > > > Currently s-ramp is only built to deploy successfully on JBoss 7 and JBoss EAP 6.1. We need a version that runs on Tomcat so that community users can more easily get started (both running and contributing). -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-367) Set fault field when handling unexpected exception

by Gary Brown (JIRA)

Gary Brown created RTGOV-367: -------------------------------- Summary: Set fault field when handling unexpected exception Key: RTGOV-367 URL: https://issues.jboss.org/browse/RTGOV-367 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 Currently when an unexpected problem occurs with handling a request, the response is recorded without a message type or fault field value, and the content describes the exception. When displaying a chart of the various faults, to identify the percentage of each type that occurs, this only currently works for known faults, where the type is recorded in the fault field. This feature request is to define a default value in the fault field, when an unknown exception occurs. This would enable these activities to be more easily identified, as well as their results be included in the chart mentioned above. One problem is finding an appropriate value that will be human readable (and understandable in many languages), while at the same time not conflicting with any name that may be used in a real service interface fault. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-366) Update activity client to use new swyd service type format and support random customer values

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-366?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-366. ------------------------------ Resolution: Done > Update activity client to use new swyd service type format and support random customer values > --------------------------------------------------------------------------------------------- > > Key: RTGOV-366 > URL: https://issues.jboss.org/browse/RTGOV-366 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > The service type values from switchyard now put the promoted service as a main value with the non-promoted service name after a slash. Update the transaction templates, and also include a template for the 'item not known' path. > While updating the quickstart, enable a random customer name to be specified. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-366) Update activity client to use new swyd service type format and support random customer values

by Gary Brown (JIRA)

Gary Brown created RTGOV-366: -------------------------------- Summary: Update activity client to use new swyd service type format and support random customer values Key: RTGOV-366 URL: https://issues.jboss.org/browse/RTGOV-366 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 The service type values from switchyard now put the promoted service as a main value with the non-promoted service name after a slash. Update the transaction templates, and also include a template for the 'item not known' path. While updating the quickstart, enable a random customer name to be specified. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-365) Fault name no longer initialized by information processor

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-365?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-365. ------------------------------ Resolution: Done > Fault name no longer initialized by information processor > --------------------------------------------------------- > > Key: RTGOV-365 > URL: https://issues.jboss.org/browse/RTGOV-365 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > The checked exception (ItemNotFoundException) now does not carry a message type, and therefore is being treated as an unchecked exception. > The distinction now appears to be, unchecked exceptions are reported as switchyard HandlerExceptions. > So update the switchyard exchange event listener to check for missing message type: > 1) If message content is HandlerException, then leave message type as empty, so will not be handled by the information processor. > 2) Otherwise set the message type as the Java type name - then the rest will be handled by the information processor -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-365) Fault name no longer initialized by information processor

by Gary Brown (JIRA)

Gary Brown created RTGOV-365: -------------------------------- Summary: Fault name no longer initialized by information processor Key: RTGOV-365 URL: https://issues.jboss.org/browse/RTGOV-365 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 The checked exception (ItemNotFoundException) now does not carry a message type, and therefore is being treated as an unchecked exception. The distinction now appears to be, unchecked exceptions are reported as switchyard HandlerExceptions. So update the switchyard exchange event listener to check for missing message type: 1) If message content is HandlerException, then leave message type as empty, so will not be handled by the information processor. 2) Otherwise set the message type as the Java type name - then the rest will be handled by the information processor -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-362) Resubmit button layout has moved

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/RTGOV-362?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved RTGOV-362. --------------------------------- Resolution: Done Resolved with some minor changes to HTML and CSS. I also took some time to clean up a few other parts of the situation details page. > Resubmit button layout has moved > -------------------------------- > > Key: RTGOV-362 > URL: https://issues.jboss.org/browse/RTGOV-362 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Gary Brown > Assignee: Eric Wittmann > > After RTGOV-360, the resubmit button has moved above the message content in line with the "Message Details" label. > On firefox it is right next to the label, but on chrome it is over on the right hand side. > However Michael Clay has tried it on both browsers, and has the button still below the message contents. > We need to isolate what the differences are. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-362) Resubmit button layout has moved

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/RTGOV-362?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated RTGOV-362: -------------------------------- Git Pull Request: https://github.com/Governance/rtgov-ui/pull/14 > Resubmit button layout has moved > -------------------------------- > > Key: RTGOV-362 > URL: https://issues.jboss.org/browse/RTGOV-362 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Gary Brown > Assignee: Eric Wittmann > > After RTGOV-360, the resubmit button has moved above the message content in line with the "Message Details" label. > On firefox it is right next to the label, but on chrome it is over on the right hand side. > However Michael Clay has tried it on both browsers, and has the button still below the message contents. > We need to isolate what the differences are. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-362) Resubmit button layout has moved

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-362?page=com.atlassian.jira.plugin.... ] Gary Brown reassigned RTGOV-362: -------------------------------- Assignee: Eric Wittmann (was: Michael Clay) [~michaelclay] Eric has a fix for this issue, so am assigning it to him. Hope you haven't spent too much time investigating. > Resubmit button layout has moved > -------------------------------- > > Key: RTGOV-362 > URL: https://issues.jboss.org/browse/RTGOV-362 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Gary Brown > Assignee: Eric Wittmann > > After RTGOV-360, the resubmit button has moved above the message content in line with the "Message Details" label. > On firefox it is right next to the label, but on chrome it is over on the right hand side. > However Michael Clay has tried it on both browsers, and has the button still below the message contents. > We need to isolate what the differences are. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-364) Situation table sort columns no longer allows sorting by timestamp

by Gary Brown (JIRA)

Gary Brown created RTGOV-364: -------------------------------- Summary: Situation table sort columns no longer allows sorting by timestamp Key: RTGOV-364 URL: https://issues.jboss.org/browse/RTGOV-364 Project: RTGov (Run Time Governance) Issue Type: Bug Components: User Interface Reporter: Gary Brown Assignee: Michael Clay With the addition of the 'status' column in the situations table, the sort columns are now misaligned. In the org.overlord.rtgov.ui.client.local.pages.situations.SituationTable, the configureColumnSorting() method associates the column names with column indexes - which should now be updated to cater for the new column at index 2. While fixing this issue, we may want to make the Status column also sortable? -- 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, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues March 2014