March 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-353) Default kibana dashboard for RTGov UI

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-353?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-353. ------------------------------ Resolution: Done > Default kibana dashboard for RTGov UI > ------------------------------------- > > Key: RTGOV-353 > URL: https://issues.jboss.org/browse/RTGOV-353 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Need to define a suitable default dashboard for kibana, to provide access to services and the activity/response time information associated with them. -- 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] (SRAMP-234) The Derived Property Is Not Displaying Correctly For Derived Artifacts

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-234?page=com.atlassian.jira.plugin.... ] Eric Wittmann reassigned SRAMP-234: ----------------------------------- Assignee: Eric Wittmann (was: Kurt Stam) > The Derived Property Is Not Displaying Correctly For Derived Artifacts > ---------------------------------------------------------------------- > > Key: SRAMP-234 > URL: https://issues.jboss.org/browse/SRAMP-234 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.3.0 - JBPM6 Integration > Environment: OS X 10.8.4, Chrome 29.0.1547.65 > Reporter: Dan Florian > Assignee: Eric Wittmann > Fix For: 0.4.0 - Tomcat Support > > Attachments: wrongDerivedValue.png > > > The "Derived" core property for derived artifacts is being displayed with a value of "false." -- 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] (SRAMP-267) Migrate gwt/bootstrap widgets to overlord-commons

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-267?page=com.atlassian.jira.plugin.... ] Eric Wittmann reassigned SRAMP-267: ----------------------------------- Assignee: Eric Wittmann (was: Kurt Stam) > Migrate gwt/bootstrap widgets to overlord-commons > ------------------------------------------------- > > Key: SRAMP-267 > URL: https://issues.jboss.org/browse/SRAMP-267 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Eric Wittmann > Fix For: 0.4.0 - Tomcat Support > > > Some of the common bootstrap/gwt related widgets have been moved to overlord-commons, to be shared across overlord projects. This issue is to: > 1) Move any remaining widgets that are still only in sramp repo > 2) Migrate sramp (and possibly dtgov) across to use the overload-commons version of the widgets, and remove the sramp copy. -- 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)

[ https://issues.jboss.org/browse/RTGOV-367?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-367. ------------------------------ Resolution: Done > 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] (SRAMPUI-109) Move common UI widgets and services to overlord-commons

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-109?page=com.atlassian.jira.plugi... ] Eric Wittmann updated SRAMPUI-109: ---------------------------------- Fix Version/s: 0.4.0 (was: Future (Unscheduled)) > Move common UI widgets and services to overlord-commons > ------------------------------------------------------- > > Key: SRAMPUI-109 > URL: https://issues.jboss.org/browse/SRAMPUI-109 > Project: S-RAMP UI > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.4.0 > > > I currently replicate a fair bit of functionality between s-ramp-ui and dtgov-ui. For example, the notification service is basically a copy/paste job between those two projects. > I should move anything that's common/shared into overlord-commons to better share them between the 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, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-259) Remove modeshape BOM once modeshape is synched with integration platform bom

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-259?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-259. --------------------------------- Resolution: Done All projects are now using the integration bom. > Remove modeshape BOM once modeshape is synched with integration platform bom > ---------------------------------------------------------------------------- > > Key: SRAMP-259 > URL: https://issues.jboss.org/browse/SRAMP-259 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Kurt Stam > Fix For: 0.4.0 - Tomcat Support > > > All the projects should be aligning with the jboss integration platform BOM, which should force all projects to use common versions of libraries. Once modeshape has been aligned with the BOM, s-ramp won't need to import the modeshape BOM anymore. > Note: s-ramp imports the modeshape BOM in the root pom.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, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-259) Remove modeshape BOM once modeshape is synched with integration platform bom

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-259?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-259. ------------------------------- > Remove modeshape BOM once modeshape is synched with integration platform bom > ---------------------------------------------------------------------------- > > Key: SRAMP-259 > URL: https://issues.jboss.org/browse/SRAMP-259 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Kurt Stam > Fix For: 0.4.0 - Tomcat Support > > > All the projects should be aligning with the jboss integration platform BOM, which should force all projects to use common versions of libraries. Once modeshape has been aligned with the BOM, s-ramp won't need to import the modeshape BOM anymore. > Note: s-ramp imports the modeshape BOM in the root pom.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, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-259) Remove modeshape BOM once modeshape is synched with integration platform bom

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-259?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-259: -------------------------------- Fix Version/s: 0.4.0 - Tomcat Support (was: 0.6.0 - Future) > Remove modeshape BOM once modeshape is synched with integration platform bom > ---------------------------------------------------------------------------- > > Key: SRAMP-259 > URL: https://issues.jboss.org/browse/SRAMP-259 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Kurt Stam > Fix For: 0.4.0 - Tomcat Support > > > All the projects should be aligning with the jboss integration platform BOM, which should force all projects to use common versions of libraries. Once modeshape has been aligned with the BOM, s-ramp won't need to import the modeshape BOM anymore. > Note: s-ramp imports the modeshape BOM in the root pom.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, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-266) on tomcat password is in two places

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-266?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-266: -------------------------------- Fix Version/s: 0.4.0 - Tomcat Support (was: 0.5.0 - API Management) > on tomcat password is in two places > ----------------------------------- > > Key: SRAMP-266 > URL: https://issues.jboss.org/browse/SRAMP-266 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Governance > Environment: tomcat > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: 0.4.0 - Tomcat Support > > > This maybe a commons issue, but the admin/pw is in tomcat-users.xml as well as in tomcat-users-overlord.xml. One file should be sufficient I think? -- 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] (SRAMP-265) persist s-ramp data on tomcat

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-265?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-265: -------------------------------- Fix Version/s: 0.4.0 - Tomcat Support (was: 0.5.0 - API Management) > persist s-ramp data on tomcat > ----------------------------- > > Key: SRAMP-265 > URL: https://issues.jboss.org/browse/SRAMP-265 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Persistence > Environment: tomcat > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: 0.4.0 - Tomcat Support > > > Need a different modeshape json config file to turn on persistence -- 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