April 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-650) A Situation is always resubmitted to localhost:8080

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-650?page=com.atlassian.jira.plugin.... ] Werner Müller commented on RTGOV-650: ------------------------------------- And another one: Given a list of resubmit URLs with only one entry that points to an active server. This however does not implement the resubmit target service (returning code 404). When resubmitting, the UI shows 'success'. However, the message was not processed by any server. It gets status RESOLVED suggesting to the user that everything went fine - which is actually not the case. > A Situation is always resubmitted to localhost:8080 > --------------------------------------------------- > > Key: RTGOV-650 > URL: https://issues.jboss.org/browse/RTGOV-650 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Documentation > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-650) A Situation is always resubmitted to localhost:8080

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-650?page=com.atlassian.jira.plugin.... ] Werner Müller commented on RTGOV-650: ------------------------------------- Resubmitting a SoapFault with no change, so the same SoapFault is triggered again. A NPE is thrown in org.switchyard.serial.graph.Factory.getFactory(Class<T>), because the 'type' parameter is null - see stack trace below. >From the user's standpoint this causes the following strange behaviour: If you have the correct resubmit URL together with a not reachable URL in your list, you get a "connection failed" message on the UI, even though the Situation was properly submitted. Also, a new Situation for the SoapFault was correctly created. Top of the stack strace: Daemon Thread [http-localhost/127.0.0.1:8180-4] (Suspended (exception NullPointerException)) Factory.getFactory(Class<T>) line: 51 DefaultAccessNode(AccessNode).decompose(Graph) line: 132 Graph.decomposeReference(Integer) line: 166 AccessNode$1.run() line: 148 Graph.decomposeRoot() line: 152 GraphSerializer.deserialize(InputStream, Class<T>) line: 61 HttpInvoker.invoke(RemoteMessage) line: 99 SwitchYardResubmitActionProvider.resubmit(String, String, MessageBean) line: 124 RTGovSituationsProvider.resubmitInternal(Situation, MessageBean, String) line: 671 RTGovSituationsProvider.resubmit(String, MessageBean, String) line: 631 SituationsProviderServiceImpl.resubmit(String, String, String) line: 174 SituationsProviderServiceImpl$Proxy$_$$_WeldClientProxy.resubmit(String, String, String) line: not available SituationsService$Proxy$_$$_WeldSubclass(SituationsService).resubmit(String, String) line: 82 SituationsService$Proxy$_$$_WeldSubclass.resubmit(String, String) line: not available [...] > A Situation is always resubmitted to localhost:8080 > --------------------------------------------------- > > Key: RTGOV-650 > URL: https://issues.jboss.org/browse/RTGOV-650 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Documentation > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-649) Status handling for Situations

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-649?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-649. ------------------------------ Resolution: Done Hopefully should be full working now. > Status handling for Situations > ------------------------------ > > Key: RTGOV-649 > URL: https://issues.jboss.org/browse/RTGOV-649 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > This relates to https://issues.jboss.org/browse/RTGOV-645. To support the Resubmit feature, the handling of the Situation's Status field shall be changed: > - Only 3 Status values shall be available: UNRESOLVED, IN PROGRESS, RESOLVED: > Either remove other values, or provide means to configure the values. > - The default entry for the Status filter on the Situations page shall be (the new value) OPEN: > This includes all Status values other than RESOLVED. > > - A Situation's Status should be changed only programmatically (see below): > Either remove the status change buttons on the "Details" tab or provide means to hide them by configuration. > > - The "Assign" button shall be available all the time. It potentially overwrites an existing value for 'assignedTo'. > (This is to be consistent with the resubmit behaviour as defined below.) > - The initial state of a (root) Situation is UNRESOLVED. > When a Situation is resubmitted: > (1) 'assignedTo' is set to the current user (overriding the current value) > (2a) If no failure is encountered (no child situation is created), > the Status is changed to RESOLVED. > (2b) If a failure is encountered (and a child situation is created), > the Status is changed to IN_PROGRESS. > - A Situation in Status RESOLVED must not be resubmitted anymore: > (1) The Resubmit button on the "Message" tab is disabled. > (2) The Situation is excluded from a bulk resubmit. > > As already stated in the requirements for RTGOV-645, assignedTo and Status shall have the same value for all Situations in a "resubmit tree". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-649) Status handling for Situations

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-649?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-649: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/291, https://github.com/Governance/rtgov/pull/292, https://github.com/Governance/rtgov/pull/299 (was: https://github.com/Governance/rtgov/pull/291, https://github.com/Governance/rtgov/pull/292) > Status handling for Situations > ------------------------------ > > Key: RTGOV-649 > URL: https://issues.jboss.org/browse/RTGOV-649 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > This relates to https://issues.jboss.org/browse/RTGOV-645. To support the Resubmit feature, the handling of the Situation's Status field shall be changed: > - Only 3 Status values shall be available: UNRESOLVED, IN PROGRESS, RESOLVED: > Either remove other values, or provide means to configure the values. > - The default entry for the Status filter on the Situations page shall be (the new value) OPEN: > This includes all Status values other than RESOLVED. > > - A Situation's Status should be changed only programmatically (see below): > Either remove the status change buttons on the "Details" tab or provide means to hide them by configuration. > > - The "Assign" button shall be available all the time. It potentially overwrites an existing value for 'assignedTo'. > (This is to be consistent with the resubmit behaviour as defined below.) > - The initial state of a (root) Situation is UNRESOLVED. > When a Situation is resubmitted: > (1) 'assignedTo' is set to the current user (overriding the current value) > (2a) If no failure is encountered (no child situation is created), > the Status is changed to RESOLVED. > (2b) If a failure is encountered (and a child situation is created), > the Status is changed to IN_PROGRESS. > - A Situation in Status RESOLVED must not be resubmitted anymore: > (1) The Resubmit button on the "Message" tab is disabled. > (2) The Situation is excluded from a bulk resubmit. > > As already stated in the requirements for RTGOV-645, assignedTo and Status shall have the same value for all Situations in a "resubmit tree". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-653) Persistent filter criteria on Situations page

by Werner Müller (JIRA)

[ https://issues.jboss.org/browse/RTGOV-653?page=com.atlassian.jira.plugin.... ] Werner Müller closed RTGOV-653. ------------------------------- Resolution: Done We can live without that, if it's hard to implement. > Persistent filter criteria on Situations page > --------------------------------------------- > > Key: RTGOV-653 > URL: https://issues.jboss.org/browse/RTGOV-653 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > The filter criteria on the "Situations" page should be preserved during the session. > Currently they are cleared when you navigate away from that page. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-656) Please make necessary changes to allow RTGov to work with other databases

by Rick Wagner (JIRA)

Rick Wagner created RTGOV-656: --------------------------------- Summary: Please make necessary changes to allow RTGov to work with other databases Key: RTGOV-656 URL: https://issues.jboss.org/browse/RTGOV-656 Project: RTGov (Run Time Governance) Issue Type: Enhancement Components: Gadgets Environment: As used in Fuse Service Works. Reporter: Rick Wagner Assignee: Gary Brown Fix For: 1.0.0.Final Users attempting to make use of Oracle 12 report that EntityManagers fail at startup time. Analysis reveals that org.overlord.gadgets.server.Bootstrap is constructing objects without a way to influence the Hibernate dialect. (Other EMs constructed through a persistence.xml do properly construct when told to use Oracle10 dialect.) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-650) A Situation is always resubmitted to localhost:8080

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-650?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-650: ---------------------------------- No problem - so can this issue be marked resolved? > A Situation is always resubmitted to localhost:8080 > --------------------------------------------------- > > Key: RTGOV-650 > URL: https://issues.jboss.org/browse/RTGOV-650 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: Documentation > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > A Situation is always resubmitted to localhost:8080. Instead, it should be resubmitted to the original target address of the request. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-653) Persistent filter criteria on Situations page

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-653?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-653: ---------------------------------- Although not ideal - how important is this requirement (i.e. to persist across browser refresh). If important, then I think the only option would be to use html5 storage (http://www.gwtproject.org/doc/latest/DevGuideHtml5Storage.html). > Persistent filter criteria on Situations page > --------------------------------------------- > > Key: RTGOV-653 > URL: https://issues.jboss.org/browse/RTGOV-653 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Werner Müller > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > The filter criteria on the "Situations" page should be preserved during the session. > Currently they are cleared when you navigate away from that page. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-655) Situations page only partially refreshed

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-655?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-655. ------------------------------ Fix Version/s: 2.1.0.Beta2 Resolution: Done > Situations page only partially refreshed > ---------------------------------------- > > Key: RTGOV-655 > URL: https://issues.jboss.org/browse/RTGOV-655 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Werner Müller > Assignee: Gary Brown > Priority: Minor > Fix For: 2.1.0.Beta2 > > > After a bulk delete, the UI is not fully refreshed: The "Displaying" on the top right as well as the paging buttons stay as they are. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-655) Situations page only partially refreshed

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-655?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-655: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/297 > Situations page only partially refreshed > ---------------------------------------- > > Key: RTGOV-655 > URL: https://issues.jboss.org/browse/RTGOV-655 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Werner Müller > Assignee: Gary Brown > Priority: Minor > Fix For: 2.1.0.Beta2 > > > After a bulk delete, the UI is not fully refreshed: The "Displaying" on the top right as well as the paging buttons stay as they are. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 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 April 2015