October 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (OVERLORD-140) Ensure consistent fav icon for all overlord apps

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-140?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on OVERLORD-140: -------------------------------------------------- Eric Wittmann <eric.wittmann(a)redhat.com> changed the Status of [bug 1048779|https://bugzilla.redhat.com/show_bug.cgi?id=1048779] from NEW to MODIFIED > Ensure consistent fav icon for all overlord apps > ------------------------------------------------ > > Key: OVERLORD-140 > URL: https://issues.jboss.org/browse/OVERLORD-140 > Project: Overlord > Issue Type: Enhancement > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: Overlord-Commons-2.0.9.Final > > > Ensure that all UI apps (s-ramp, dtgov, rtgov) share a common favicon. Presumably we should use the overlord icon currently included in overlord-commons-uiheader. This can be accomplished by simply including this markup in the gwt host page: > {code} > <link rel="icon" type="image/png" href="images/favicon.png"></link> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-592) Filtering situations by status "Unresolved" is not working

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-592?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-592: ----------------------------- Fix Version/s: 2.1.0.Final > Filtering situations by status "Unresolved" is not working > ---------------------------------------------------------- > > Key: RTGOV-592 > URL: https://issues.jboss.org/browse/RTGOV-592 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Affects Versions: 2.0.0.Final > Environment: Fuse 6.1 + switchyard 2.0.0.Alpha3 + overlord 2.0.0.Final > Reporter: Andrej Vano > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Filtering by status "Unresolved" always return No situations found. even if there are unresolved situations. All other statuses (resolved, in progress..) are working correctly -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-592) Filtering situations by status "Unresolved" is not working

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-592?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated RTGOV-592: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1150158 > Filtering situations by status "Unresolved" is not working > ---------------------------------------------------------- > > Key: RTGOV-592 > URL: https://issues.jboss.org/browse/RTGOV-592 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Affects Versions: 2.0.0.Final > Environment: Fuse 6.1 + switchyard 2.0.0.Alpha3 + overlord 2.0.0.Final > Reporter: Andrej Vano > Assignee: Gary Brown > > Filtering by status "Unresolved" always return No situations found. even if there are unresolved situations. All other statuses (resolved, in progress..) are working correctly -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-592) Filtering situations by status "Unresolved" is not working

by Andrej Vano (JIRA)

Andrej Vano created RTGOV-592: --------------------------------- Summary: Filtering situations by status "Unresolved" is not working Key: RTGOV-592 URL: https://issues.jboss.org/browse/RTGOV-592 Project: RTGov (Run Time Governance) Issue Type: Bug Components: User Interface Affects Versions: 2.0.0.Final Environment: Fuse 6.1 + switchyard 2.0.0.Alpha3 + overlord 2.0.0.Final Reporter: Andrej Vano Assignee: Gary Brown Filtering by status "Unresolved" always return No situations found. even if there are unresolved situations. All other statuses (resolved, in progress..) are working correctly -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-589) Create Karaf Commands to configure Fuse

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-589?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-589. ------------------------------ Resolution: Done > Create Karaf Commands to configure Fuse > --------------------------------------- > > Key: RTGOV-589 > URL: https://issues.jboss.org/browse/RTGOV-589 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 2.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-589) Create Karaf Commands to configure Fuse

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-589?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-589: ----------------------------- Fix Version/s: 2.0.0.Final (was: 2.1.0.Final) > Create Karaf Commands to configure Fuse > --------------------------------------- > > Key: RTGOV-589 > URL: https://issues.jboss.org/browse/RTGOV-589 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 2.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-555) EPNs not properly registered after rtgov refresh in Fuse

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-555?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-555: ----------------------------- Fix Version/s: 2.1.0.Final (was: 2.0.0.Final) > EPNs not properly registered after rtgov refresh in Fuse > -------------------------------------------------------- > > Key: RTGOV-555 > URL: https://issues.jboss.org/browse/RTGOV-555 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When installing rtgov followed by switchyard in fuse, the EPNs are not all re-registered. > It appears that the activators are being called, which establishes service listeners on the EPNManager, but only some of the EPNs are then called back when the EPNManager is available. > Firstly need to consider adding some form of timer on the activators, to log an error if the EPN is not eventually registered. But need to find out why some activators are called, while others are not. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-575) endex custom loading of index mappings per .epn deployment

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-575?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-575: ----------------------------- Fix Version/s: 2.1.0.Final (was: 2.0.0.Final) > endex custom loading of index mappings per .epn deployment > ----------------------------------------------------------- > > Key: RTGOV-575 > URL: https://issues.jboss.org/browse/RTGOV-575 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Event Processor > Reporter: ivan mckinley > Assignee: Gary Brown > Labels: elasticsearch > Fix For: 2.1.0.Final > > > Prior to the karaf integration it was possible to deploy a epn with a elasticsearch store configured for a separate index as rtogv. > 1: developer would deploy a custom epn with a ElasticsearchKeyValueStore configured for a custom index and type. > 2: the elastisearchclient class would look for a file name $index-mapping.json on the path > The concept is developers can store business data they extracted from the activity events and store in ES for later analysis via kibana or what ever > unfortunately the following line > Thread.currentThread().setContextClassLoader(TransportClient.class.getClassLoader()); > in ElasticsearchClient that was added for the karaf intergration means that the classloader can not longer see any bundled $index-mappings.json file that accompany the deployed epns (.war) > one solution would be to switch to the same mechanism used to to load ip.json or epn.json files -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-589) Create Karaf Commands to configure Fuse

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-589?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-589: ----------------------------- Fix Version/s: 2.1.0.Final (was: 2.0.0.Final) > Create Karaf Commands to configure Fuse > --------------------------------------- > > Key: RTGOV-589 > URL: https://issues.jboss.org/browse/RTGOV-589 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 2.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-591) Support Fabric deployment using karaf commands

by David virgil naranjo (JIRA)

David virgil naranjo created RTGOV-591: ------------------------------------------ Summary: Support Fabric deployment using karaf commands Key: RTGOV-591 URL: https://issues.jboss.org/browse/RTGOV-591 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: David virgil naranjo Assignee: David virgil naranjo Support Fuse/Fabric deployment using karaf commands -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 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 October 2014