October 2013 - jboss-jira - Jboss List Archives

[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.0.0.CR5 (was: 6.0.0.CR4) > 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.0.0.CR5 > > -- 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, 6 months

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.0.0.CR5 (was: 6.0.0.CR4) > 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.0.0.CR5 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-134) Metadata inheritance is not resolved correctly when typeDeclarations are created implicitly

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-134?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-134: ------------------------------------------ Fix Version/s: 6.0.0.CR5 (was: 6.0.0.CR4) > Metadata inheritance is not resolved correctly when typeDeclarations are created implicitly > ------------------------------------------------------------------------------------------- > > Key: DROOLS-134 > URL: https://issues.jboss.org/browse/DROOLS-134 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.1.Final > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Blocker > Fix For: 5.5.1.Final, 6.0.0.CR5 > > > Implicit TypeDeclarations do not resolve declared metadata modifiers correctly -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-126) Drools Verifier does not support Conditional Branches

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-126?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-126: ------------------------------------------ Fix Version/s: 6.0.0.CR5 (was: 6.0.0.CR4) > Drools Verifier does not support Conditional Branches > ----------------------------------------------------- > > Key: DROOLS-126 > URL: https://issues.jboss.org/browse/DROOLS-126 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.Beta2 > Reporter: Davide Sottara > Assignee: Toni Rikkola > Priority: Blocker > Fix For: 5.5.1.Final, 6.0.0.CR5 > > > Drools Verifier has not been updated since the introduction of the Conditional Branches. > Any rule with a ConditionalBranchDescr would generate an exception > when Verified. -- 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, 6 months

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.0.0.CR5 (was: 6.0.0.CR4) > 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.0.0.CR5 > > > 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-257) Past events beyond expiration are not expired

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-257?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-257: ------------------------------------------ Fix Version/s: 6.0.0.CR5 (was: 6.0.0.CR4) > Past events beyond expiration are not expired > --------------------------------------------- > > Key: DROOLS-257 > URL: https://issues.jboss.org/browse/DROOLS-257 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR3 > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Critical > Fix For: 5.5.1.Final, 6.0.0.CR5 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-254) "Exists OR" rules are compiled inconsistently

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-254?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-254: ------------------------------------------ Fix Version/s: 6.0.0.CR5 (was: 6.0.0.CR4) > "Exists OR" rules are compiled inconsistently > --------------------------------------------- > > Key: DROOLS-254 > URL: https://issues.jboss.org/browse/DROOLS-254 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR3 > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Critical > Fix For: 5.5.1.Final, 6.0.0.CR5 > > > Exists ( A or B ) is transformed into ( Exists A ) or ( Exists B ) > In case both A and B are asserted, they result in two activations, > whereas one would expect only one. > Moreover, the equivalent not ( (not A) and (not B) ) results in only > one activation. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-251) Classloader fails to resolve when annotation and declared class have the same name

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-251?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-251: ------------------------------------------ Fix Version/s: 6.0.0.CR5 (was: 6.0.0.CR4) > Classloader fails to resolve when annotation and declared class have the same name > ---------------------------------------------------------------------------------- > > Key: DROOLS-251 > URL: https://issues.jboss.org/browse/DROOLS-251 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR2 > Reporter: Davide Sottara > Assignee: Mark Proctor > Fix For: 5.5.1.Final, 6.0.0.CR5 > > > package test > declare Annot > fld : int @Annot > end > The packagebuilder type resolver will confuse the annotation with the declared class and throw exceptions (varies depending on optional import > statements) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-249) Handle conflicts when using @position in declared types

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-249?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-249: ------------------------------------------ Fix Version/s: 6.0.0.CR5 (was: 6.0.0.CR4) > Handle conflicts when using @position in declared types > ------------------------------------------------------- > > Key: DROOLS-249 > URL: https://issues.jboss.org/browse/DROOLS-249 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR2 > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Minor > Fix For: 5.5.1.Final, 6.0.0.CR5 > > > declare A > f : int @position(2) > g : int @position(1) > end > declare B extends A > h : int @position(3) > i : int @position(2) > end > The resulting field order may not be deterministic because of > - the clashes (2) > - the missing pos (0) > this is dangerous when used with positional constraints > B( $x, $y, $z, $w ; ) > Marked as minor because of the obvious workaround -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-268) Delayed rule schedules are computed erroneously

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-268?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-268. -------------------------------- Fix Version/s: 5.5.1.Final Resolution: Done > Delayed rule schedules are computed erroneously > ----------------------------------------------- > > Key: DROOLS-268 > URL: https://issues.jboss.org/browse/DROOLS-268 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR3 > Reporter: Davide Sottara > Assignee: Mario Fusco > Fix For: 5.5.1.Final, 6.0.0.Final > > > Consider the following case, where all patterns are events > $a : A() > $b : B() > not C( this after[0,N] $a ) > When the schedule time is computed, the ACTIVATION timestamp is considered > as the starting timestamp, rather than $a's timestamp. > If $b is insert after $a, the rule's schedule will be N time units after $b. -- 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, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2013