April 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3161) Optimize org.jboss.as.jmx.model.RootResourceIterator

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3161?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3161: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1077536|https://bugzilla.redhat.com/show_bug.cgi?id=1077536] from ON_QA to VERIFIED > Optimize org.jboss.as.jmx.model.RootResourceIterator > ---------------------------------------------------- > > Key: WFLY-3161 > URL: https://issues.jboss.org/browse/WFLY-3161 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, JMX > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.1.0.CR1 > > > RootResourceIterator is performing an access control check on a resource before confirming that the caller is in any way interested in that resource. This results in spurious access control checks. Fixing this can speed up queryMBeans and queryNames calls. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3228) ApplyRemoteMasterDomainHandler should use values sent from DC for root resource

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3228?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3228: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1085122|https://bugzilla.redhat.com/show_bug.cgi?id=1085122] from ON_QA to VERIFIED > ApplyRemoteMasterDomainHandler should use values sent from DC for root resource > ------------------------------------------------------------------------------- > > Key: WFLY-3228 > URL: https://issues.jboss.org/browse/WFLY-3228 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Final > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.1.0.CR1 > > > This is needed to keep the slave copy of the resource model actually the same, and popped up during mixed domain testing of EAP with a 6.2.0 slave. > Connect directly to to 6.1.1 slave - gets domain version from master > {code} > [domain@localhost:19999 /] :read-resource > { > "outcome" => "success", > "result" => { > "deployment" => undefined, > "deployment-overlay" => undefined, > "management-major-version" => 1, > "management-micro-version" => 0, > "management-minor-version" => 6, > "name" => "Unnamed Domain", > "namespaces" => [], > "path" => undefined, > "product-name" => "EAP", > "product-version" => "6.3.0.Alpha3", > "profile" => undefined, > "release-codename" => "Janus", > "release-version" => "7.4.0.Final-redhat-SNAPSHOT", > {code} > Connect directly to 6.2.0 slave - does not get domain version from master > {code} > [domain@localhost:19999 /] :read-resource > { > "outcome" => "success", > "result" => { > "management-major-version" => 1, > "management-micro-version" => 0, > "management-minor-version" => 5, > "name" => "Unnamed Domain", > "namespaces" => [], > "product-name" => "EAP", > "product-version" => "6.2.0.GA", > "release-codename" => "Janus", > "release-version" => "7.3.0.Final-redhat-14", > {code} > The 6.2.0 slave should look the same as the 6.1.1 slave for these attributes. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-201) Improve Rule Removal

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-201?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-201: ------------------------------------------ Fix Version/s: 6.1.0.Beta4 (was: 6.1.0.Beta3) > Improve Rule Removal > -------------------- > > Key: DROOLS-201 > URL: https://issues.jboss.org/browse/DROOLS-201 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 6.1.0.Beta4 > > -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-88) Support generics in declared types' fields

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-88?page=com.atlassian.jira.plugin.... ] Michael Biarnes Kiefer updated DROOLS-88: ----------------------------------------- Fix Version/s: 6.1.0.Beta4 (was: 6.1.0.Beta3) > Support generics in declared types' fields > ------------------------------------------ > > Key: DROOLS-88 > URL: https://issues.jboss.org/browse/DROOLS-88 > Project: Drools > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Reporter: Davide Sottara > Assignee: Davide Sottara > Priority: Minor > Fix For: 5.5.1.Final, 6.1.0.Beta4 > > > It should be possible to write: > declare Foo > list : List<String> > end > While not supported in rules using the mvel dialect, it makes declared types much more readable, and adds some type-safety to java rules. > Notice that this ticket is NOT related to the possibility of declaring generic classes, such as Foo<T>. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-115) Add support for strong negation

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-115?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-115: ------------------------------------------ Fix Version/s: 6.1.0.Beta4 (was: 6.1.0.Beta3) > Add support for strong negation > ------------------------------- > > Key: DROOLS-115 > URL: https://issues.jboss.org/browse/DROOLS-115 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Davide Sottara > Assignee: Davide Sottara > Priority: Minor > Fix For: 6.1.0.Beta4 > > > Drools "not" operator implements a type of "negation by failure", i.e. not X() behaves as the negation of "exists" or, in other words, translates as "it is NOT asserted that ...". > However, another form of stronger negation is needed to express conditionals such as "it is asserted that NOT ..." > It should be possible, then, to assert facts both in a "positive" and "negative" way, to assert THAT and THAT NOT. > The language should also support a "neg" CE to create "negative" patterns which will match with negative facts. I.e. it should be possible to write rules such as: > when $p : Person() and Car( owner == $p ) then > // a positive, matching Car is present in the WM > when $p : Person() and neg Car( owner == $p ) then > // a negative, matching Car is present in the WM > when $p : Person() and not Car( owner == $p ) then > // neither a positive nor a negative fact exists in the WM > For a more detailed description and motivation see e.g.: > https://oxygen.informatik.tu-cottbus.de/publications/wagner/WebRules2Neg.pdf -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-198) Separate Rete and Phreak

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-198?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-198: ------------------------------------------ Fix Version/s: 6.1.0.Beta4 (was: 6.1.0.Beta3) > Separate Rete and Phreak > ------------------------ > > Key: DROOLS-198 > URL: https://issues.jboss.org/browse/DROOLS-198 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 6.1.0.Beta4 > > -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-112) Allow join constraints in sliding windows

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-112?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-112: ------------------------------------------ Fix Version/s: 6.1.0.Beta4 (was: 6.1.0.Beta3) > Allow join constraints in sliding windows > ----------------------------------------- > > Key: DROOLS-112 > URL: https://issues.jboss.org/browse/DROOLS-112 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.Alpha9, 6.0.0.Beta1 > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Critical > Fix For: 6.1.0.Beta4 > > > When using a sliding window, alpha constraints are evaluated before the window is considered, but beta (join) constraints are evaluated afterwards. > While it does not usually make a difference when time windows are concerned, > it DOES make a difference with length windows. > Imho, a clear warning should be added in the documentation to clarify > the current behavior. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-432) Types declared in a foreign package are processed one at a time

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-432?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-432: ------------------------------------------ Fix Version/s: 6.1.0.Beta4 (was: 6.1.0.Beta3) > Types declared in a foreign package are processed one at a time > --------------------------------------------------------------- > > Key: DROOLS-432 > URL: https://issues.jboss.org/browse/DROOLS-432 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.1.Final > Reporter: Davide Sottara > Assignee: Mark Proctor > Fix For: 6.1.0.Beta4 > > > The following snippet has two issues > {code} > package a; > declare b.X field : b.Y end > declare b.Y end > {code} > While processing package a, the packageBuilder will infer the existence of package b and create the appropriate typeDeclarations. > However, a partial, independent package b is created for X and Y: > - it is inefficient > - internal dependencies cannot be resolved : b.X does not (yet) see b.Y -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-332) Space Invaders and Number Guess Game

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-332?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-332: ------------------------------------------ Fix Version/s: 6.1.0.Beta4 (was: 6.1.0.Beta3) > Space Invaders and Number Guess Game > ------------------------------------ > > Key: DROOLS-332 > URL: https://issues.jboss.org/browse/DROOLS-332 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 6.1.0.Beta4 > > -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-316) Arbitrary Conflict Resolution can be confusing use LoadOrder

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-316?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-316: ------------------------------------------ Fix Version/s: 6.1.0.Beta4 (was: 6.1.0.Beta3) > Arbitrary Conflict Resolution can be confusing use LoadOrder > ------------------------------------------------------------ > > Key: DROOLS-316 > URL: https://issues.jboss.org/browse/DROOLS-316 > Project: Drools > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 6.1.0.Beta4 > > -- 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

12 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2014