March 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-356) Move checkstyle config from rtgov to overlord-commons

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-356?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-356. ------------------------------ Resolution: Done > Move checkstyle config from rtgov to overlord-commons > ----------------------------------------------------- > > Key: RTGOV-356 > URL: https://issues.jboss.org/browse/RTGOV-356 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: David virgil naranjo > Fix For: 2.0.0.M1 > > > Currently the checkstyle configuration is in rtgov repo. But should be moved to overlord-commons so can be shared across all overlord projects. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-391) Support EAP 6.2

by Gary Brown (JIRA)

Gary Brown created RTGOV-391: -------------------------------- Summary: Support EAP 6.2 Key: RTGOV-391 URL: https://issues.jboss.org/browse/RTGOV-391 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 Add support for EAP 6.2. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-382) Support EAP 6.2

by Gary Brown (JIRA)

Gary Brown created SRAMP-382: -------------------------------- Summary: Support EAP 6.2 Key: SRAMP-382 URL: https://issues.jboss.org/browse/SRAMP-382 Project: S-RAMP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Kurt Stam Fix For: 0.5.0 - API Management Add support for EAP 6.2. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-356) Move checkstyle config from rtgov to overlord-commons

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/RTGOV-356?page=com.atlassian.jira.plugin.... ] David virgil naranjo updated RTGOV-356: --------------------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/28, https://github.com/Governance/overlord-commons/pull/52 > Move checkstyle config from rtgov to overlord-commons > ----------------------------------------------------- > > Key: RTGOV-356 > URL: https://issues.jboss.org/browse/RTGOV-356 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: David virgil naranjo > Fix For: 2.0.0.M1 > > > Currently the checkstyle configuration is in rtgov repo. But should be moved to overlord-commons so can be shared across all overlord projects. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-356) Move checkstyle config from rtgov to overlord-commons

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/RTGOV-356?page=com.atlassian.jira.plugin.... ] Work on RTGOV-356 started by David virgil naranjo. > Move checkstyle config from rtgov to overlord-commons > ----------------------------------------------------- > > Key: RTGOV-356 > URL: https://issues.jboss.org/browse/RTGOV-356 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: David virgil naranjo > Fix For: 2.0.0.M1 > > > Currently the checkstyle configuration is in rtgov repo. But should be moved to overlord-commons so can be shared across all overlord projects. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-356) Move checkstyle config from rtgov to overlord-commons

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/RTGOV-356?page=com.atlassian.jira.plugin.... ] David virgil naranjo commented on RTGOV-356: -------------------------------------------- Done the pull request in the overlord-commons project. Not done the change in rtgov, because in this project it is point to overlord-commons released artifacts and the overlord-commons-build project is not yet released. In the moment overlord-commons-build is released in the repository I ll make the small change in the parent rtgov pom and remove the build project from rtgov repository. > Move checkstyle config from rtgov to overlord-commons > ----------------------------------------------------- > > Key: RTGOV-356 > URL: https://issues.jboss.org/browse/RTGOV-356 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: David virgil naranjo > Fix For: 2.0.0.M1 > > > Currently the checkstyle configuration is in rtgov repo. But should be moved to overlord-commons so can be shared across all overlord projects. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-390) Autogenerate features.xml for Karaf

by Gary Brown (JIRA)

Gary Brown created RTGOV-390: -------------------------------- Summary: Autogenerate features.xml for Karaf Key: RTGOV-390 URL: https://issues.jboss.org/browse/RTGOV-390 Project: RTGov (Run Time Governance) Issue Type: Sub-task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 Currently the features.xml is manually created, but when supporting RESTeasy this will increase the number of third party dependencies, so need to autogenerate the features.xml. -- 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, 10 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 updated RTGOV-365: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/18 > 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, 10 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 updated RTGOV-366: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/19 > 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, 10 months

1
0
0 / 0

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

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-367?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-367: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/20 > 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, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues March 2014