October 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-298) Exception from SwitchyardEventManager when shutting down server

by Gary Brown (JIRA)

Gary Brown created RTGOV-298: -------------------------------- Summary: Exception from SwitchyardEventManager when shutting down server Key: RTGOV-298 URL: https://issues.jboss.org/browse/RTGOV-298 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-258) DroolsEventProcessor should fail deployment if rule not found

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-258?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-258: ----------------------------------------------- Jiri Pechanec <jpechane(a)redhat.com> changed the Status of [bug 1000350|https://bugzilla.redhat.com/show_bug.cgi?id=1000350] from ON_QA to VERIFIED > DroolsEventProcessor should fail deployment if rule not found > ------------------------------------------------------------- > > Key: RTGOV-258 > URL: https://issues.jboss.org/browse/RTGOV-258 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > If the named rule does not exist, or has an error, then the EPN should fail to deploy. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-258) DroolsEventProcessor should fail deployment if rule not found

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-258?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-258: ----------------------------------------------- Jiri Pechanec <jpechane(a)redhat.com> made a comment on [bug 1000350|https://bugzilla.redhat.com/show_bug.cgi?id=1000350] Verified in ER4 > DroolsEventProcessor should fail deployment if rule not found > ------------------------------------------------------------- > > Key: RTGOV-258 > URL: https://issues.jboss.org/browse/RTGOV-258 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > If the named rule does not exist, or has an error, then the EPN should fail to deploy. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-259) DroolsEventProcessor session caching not isolated or protected from redeployments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-259?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-259: ----------------------------------------------- Jiri Pechanec <jpechane(a)redhat.com> made a comment on [bug 1000393|https://bugzilla.redhat.com/show_bug.cgi?id=1000393] Verified in ER4 > DroolsEventProcessor session caching not isolated or protected from redeployments > --------------------------------------------------------------------------------- > > Key: RTGOV-259 > URL: https://issues.jboss.org/browse/RTGOV-259 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Drools sessions are cached based on rule names, which are not necessarily unique across EPNs. > When the drools event processor is initialised, it is associated with an EPNContext. However if it already exists, this is not done. Therefore the issue is when a new version of an EPN is deployed, the rule will remain associated with the original EPNContext. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-259) DroolsEventProcessor session caching not isolated or protected from redeployments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-259?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-259: ----------------------------------------------- Jiri Pechanec <jpechane(a)redhat.com> changed the Status of [bug 1000393|https://bugzilla.redhat.com/show_bug.cgi?id=1000393] from ON_QA to VERIFIED > DroolsEventProcessor session caching not isolated or protected from redeployments > --------------------------------------------------------------------------------- > > Key: RTGOV-259 > URL: https://issues.jboss.org/browse/RTGOV-259 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Drools sessions are cached based on rule names, which are not necessarily unique across EPNs. > When the drools event processor is initialised, it is associated with an EPNContext. However if it already exists, this is not done. Therefore the issue is when a new version of an EPN is deployed, the rule will remain associated with the original EPNContext. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-77) All Artifact Filters should be encoded in the URL

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-77?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on SRAMPUI-77: ------------------------------------------------ Eric Wittmann <eric.wittmann(a)redhat.com> made a comment on [bug 1018786|https://bugzilla.redhat.com/show_bug.cgi?id=1018786] Ok I made some changes to the s-ramp UI so that the filter settings are remembered. I should also make this change to the dtgov UI. I'll create a separate BZ to track that. > All Artifact Filters should be encoded in the URL > ------------------------------------------------- > > Key: SRAMPUI-77 > URL: https://issues.jboss.org/browse/SRAMPUI-77 > Project: S-RAMP UI > Issue Type: Enhancement > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Future (Unscheduled) > > > Whenever a filter is changed on the Artifacts page, it should be encoded into the URL. This will allow users to bookmark actual queries. It will also allow users to navigate back and forth without losing their place in the search. > Note: also save the page # in the URL. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-96) Remember the selected filter criteria when navigating the UI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-96?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on SRAMPUI-96: ------------------------------------------------ Eric Wittmann <eric.wittmann(a)redhat.com> made a comment on [bug 1018786|https://bugzilla.redhat.com/show_bug.cgi?id=1018786] Ok I made some changes to the s-ramp UI so that the filter settings are remembered. I should also make this change to the dtgov UI. I'll create a separate BZ to track that. > Remember the selected filter criteria when navigating the UI > ------------------------------------------------------------ > > Key: SRAMPUI-96 > URL: https://issues.jboss.org/browse/SRAMPUI-96 > Project: S-RAMP UI > Issue Type: Enhancement > Components: View > Affects Versions: 0.3.0 > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 > > > The Artifacts page allows the user to select a number of filters to narrow down the list of artifacts being viewed. However, these options are lost when the user navigates to another page and then back again. We should remember the user's filter settings as long as they stay within the s-ramp application (or perhaps beyond by storing something in browser state?). -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-77) All Artifact Filters should be encoded in the URL

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-77?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated SRAMPUI-77: ------------------------------------------- Bugzilla Update: (was: Perform) Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=1018786) > All Artifact Filters should be encoded in the URL > ------------------------------------------------- > > Key: SRAMPUI-77 > URL: https://issues.jboss.org/browse/SRAMPUI-77 > Project: S-RAMP UI > Issue Type: Enhancement > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Future (Unscheduled) > > > Whenever a filter is changed on the Artifacts page, it should be encoded into the URL. This will allow users to bookmark actual queries. It will also allow users to navigate back and forth without losing their place in the search. > Note: also save the page # in the URL. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-96) Remember the selected filter criteria when navigating the UI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-96?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on SRAMPUI-96: ------------------------------------------------ Eric Wittmann <eric.wittmann(a)redhat.com> changed the Status of [bug 1018786|https://bugzilla.redhat.com/show_bug.cgi?id=1018786] from NEW to MODIFIED > Remember the selected filter criteria when navigating the UI > ------------------------------------------------------------ > > Key: SRAMPUI-96 > URL: https://issues.jboss.org/browse/SRAMPUI-96 > Project: S-RAMP UI > Issue Type: Enhancement > Components: View > Affects Versions: 0.3.0 > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 > > > The Artifacts page allows the user to select a number of filters to narrow down the list of artifacts being viewed. However, these options are lost when the user navigates to another page and then back again. We should remember the user's filter settings as long as they stay within the s-ramp application (or perhaps beyond by storing something in browser state?). -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-77) All Artifact Filters should be encoded in the URL

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-77?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on SRAMPUI-77: ------------------------------------------------ Eric Wittmann <eric.wittmann(a)redhat.com> changed the Status of [bug 1018786|https://bugzilla.redhat.com/show_bug.cgi?id=1018786] from NEW to MODIFIED > All Artifact Filters should be encoded in the URL > ------------------------------------------------- > > Key: SRAMPUI-77 > URL: https://issues.jboss.org/browse/SRAMPUI-77 > Project: S-RAMP UI > Issue Type: Enhancement > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Future (Unscheduled) > > > Whenever a filter is changed on the Artifacts page, it should be encoded into the URL. This will allow users to bookmark actual queries. It will also allow users to navigate back and forth without losing their place in the search. > Note: also save the page # in the URL. -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues October 2013