April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-121) Circular dependencies are not detected in declared types

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-121: ------------------------------------- Summary: Circular dependencies are not detected in declared types Key: DROOLS-121 URL: https://issues.jboss.org/browse/DROOLS-121 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.5.0.Final Reporter: Davide Sottara Assignee: Mark Proctor Priority: Critical Fix For: 5.5.1.Final The following declarations are not recognized as errors and cause a stack overflow exception: declare Bean extends Bean end declare Bean1 extends Bean2 end declare Bean2 extends Bean1 end -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-2258) count in sliding time

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2258?page=com.atlassian.jira.plug... ] Davide Sottara commented on JBRULES-2258: ----------------------------------------- By assumption, in stream mode you should not assert "past" and "out-of-order" events. The events will be expired as soon as you advance the pseudo-clock - even by zero - but you will still get the initial activation. > count in sliding time > --------------------- > > Key: JBRULES-2258 > URL: https://issues.jboss.org/browse/JBRULES-2258 > Project: JBRULES > Issue Type: CTS Challenge > Security Level: Public(Everyone can see) > Components: drools-core (fusion) > Affects Versions: 5.0.1.FINAL > Environment: Mac os 10.5, Eclipse Galileo, Jboss 5, > Reporter: Francesco Chiarelli > Assignee: Edson Tirelli > Labels: fusion, sliding, stream, windows > Fix For: 6.0.0.Alpha1 > > > I'm trying to use a sliding time fro count a facts with a condition. > I'have set a stream mode. > In test, with pseudo clock active, set this to current Time (it's > correct?), declare a fact type in drl with > declare MyFact (i've a javabean) > @role(event) > @timestamp(myTimestamp) > end > attribute type of myTimestamp must be long or Date? I've tried with both > but nothing, engine count all fact > ex: n fact in x days ago from now, the statement over window:time(1s) > result always n fact. why? > in when: > // $o : Order(<condition>) > $nRic : Number(intValue<maxRic) from accumulate($n: Order(this==$o) > over window:time(1s),count($n)) > ps. if i set a real clock altough a pseudo, in runTime i've a ClassCastExc. to JdkTimerService > There is a test suite about count? -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-120) Add ability to trait a map

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-120?page=com.atlassian.jira.plugin... ] Davide Sottara moved JBRULES-3701 to DROOLS-120: ------------------------------------------------ Project: Drools (was: JBRULES) Key: DROOLS-120 (was: JBRULES-3701) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 5.5.0.Final (was: 5.5.0.Final) Component/s: (was: drools-core (expert)) > Add ability to trait a map > -------------------------- > > Key: DROOLS-120 > URL: https://issues.jboss.org/browse/DROOLS-120 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Reporter: Ming Fang > Assignee: Davide Sottara > > Add ability to trait a Map as described by Mark Proctor here > http://drools.46999.n3.nabble.com/rules-users-Maps-as-Object-in-Drools-td... > <quote> > //code below is illustrative of what is possible, if changes where mad for above idea. > // Create interface > Person > @Trait > String : name > int : age > end > // Identify the Map instance, and wrap it with the Person interface. > rule > $m : Map[ this['name'] != null, this['age'] != null ) > then > don( $m : Person.class ); > end > // Now the map is identified in a type safe manner. > rule > Person( name == "darth", age == 150 ) > then > …. > end > </quote> -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-119) Declared Beans and Enums can't be initialized using other declared Beans and/or Enums

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-119?page=com.atlassian.jira.plugin... ] Davide Sottara moved JBRULES-3350 to DROOLS-119: ------------------------------------------------ Project: Drools (was: JBRULES) Key: DROOLS-119 (was: JBRULES-3350) Workflow: GIT Pull Request workflow (was: jira) > Declared Beans and Enums can't be initialized using other declared Beans and/or Enums > ------------------------------------------------------------------------------------- > > Key: DROOLS-119 > URL: https://issues.jboss.org/browse/DROOLS-119 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Davide Sottara > Assignee: Mark Proctor > > Field initialization is done using MVEL, which does not use the CompositeClassLoader, where declared classes are loaded. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-116) Import PMML files as resources

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-116?page=com.atlassian.jira.plugin... ] Davide Sottara moved JBRULES-2948 to DROOLS-116: ------------------------------------------------ Project: Drools (was: JBRULES) Key: DROOLS-116 (was: JBRULES-2948) Workflow: GIT Pull Request workflow (was: jira) > Import PMML files as resources > ------------------------------ > > Key: DROOLS-116 > URL: https://issues.jboss.org/browse/DROOLS-116 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Minor > > Predictive models should be embedded and evaluated in a Drools session > Models encoded in PMML (Predictive Model Markup Language) should be imported > and translated in rules. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-117) The "from" CE does not manage @events correctly

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-117?page=com.atlassian.jira.plugin... ] Davide Sottara moved JBRULES-3637 to DROOLS-117: ------------------------------------------------ Project: Drools (was: JBRULES) Key: DROOLS-117 (was: JBRULES-3637) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: (was: 5.4.0.Final) Component/s: (was: drools-core (fusion)) Fix Version/s: (was: 6.0.0.Alpha1) > The "from" CE does not manage @events correctly > ----------------------------------------------- > > Key: DROOLS-117 > URL: https://issues.jboss.org/browse/DROOLS-117 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Davide Sottara > Assignee: Edson Tirelli > Priority: Critical > > If an event type (i.e. an instance of a class marked with @role(event)) is returned by a "from" node, it is not wrapped by an EventFactHandle as expected, so e.g. any attempt to use temporal operators will fail. > See the test case below for an example > The problem is in FromNode.java around line 200, where the new handles are created without passing an ObjectTypeConfiguration, leading to the default creation of a DefaultFactHandle. > I wonder if it's possible to simply retrieve the ObjectTypeConf: > workingMemory.getObjectTypeConfigurationRegistry().getObjectTypeConf( context.getEntryPoint(), object ) > and pass it to the handle factory method. > I tested it and it works for the test case below, but there may be other > side-effects I'm not seeing. > --------------------------------------------------------------------------- > May be related (but not the same as) #JBRULES-2423 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-118) Parser fails to read files ending with a comment

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-118?page=com.atlassian.jira.plugin... ] Davide Sottara moved JBRULES-3185 to DROOLS-118: ------------------------------------------------ Project: Drools (was: JBRULES) Key: DROOLS-118 (was: JBRULES-3185) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: (was: 5.3.0.Beta1) Component/s: (was: drools-compiler) > Parser fails to read files ending with a comment > ------------------------------------------------ > > Key: DROOLS-118 > URL: https://issues.jboss.org/browse/DROOLS-118 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Davide Sottara > Assignee: Edson Tirelli > Priority: Minor > > When the last line of a DRL file is a comment, parser fails with "no viable alternative at input ''" -- 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, 8 months

1
0
0 / 0

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

by Mark Proctor (JIRA)

[ https://issues.jboss.org/browse/DROOLS-115?page=com.atlassian.jira.plugin... ] Mark Proctor moved JBRULES-3626 to DROOLS-115: ---------------------------------------------- Project: Drools (was: JBRULES) Key: DROOLS-115 (was: JBRULES-3626) Workflow: GIT Pull Request workflow (was: jira) Fix Version/s: 6.0.0.CR1 (was: 6.0.0.Alpha1) > 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.CR1 > > > 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-113) Certainty Factors

by Mark Proctor (JIRA)

[ https://issues.jboss.org/browse/DROOLS-113?page=com.atlassian.jira.plugin... ] Mark Proctor moved JBRULES-359 to DROOLS-113: --------------------------------------------- Project: Drools (was: JBRULES) Key: DROOLS-113 (was: JBRULES-359) Workflow: GIT Pull Request workflow (was: jira) Component/s: (was: All) > Certainty Factors > ----------------- > > Key: DROOLS-113 > URL: https://issues.jboss.org/browse/DROOLS-113 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Davide Sottara > > We need a generic solution that allows Drools to support all the various forms to handle certainty: > Bayesian > Fuzzy > Argumentation > etc > A wiki page has been made to hash out the spec/design details: > http://wiki.jboss.org/wiki/Wiki.jsp?page=CertaintyFactors -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-114) Support "Defeasible" rules in Drools

by Mark Proctor (JIRA)

[ https://issues.jboss.org/browse/DROOLS-114?page=com.atlassian.jira.plugin... ] Mark Proctor moved JBRULES-3613 to DROOLS-114: ---------------------------------------------- Project: Drools (was: JBRULES) Key: DROOLS-114 (was: JBRULES-3613) Workflow: GIT Pull Request workflow (was: jira) Component/s: (was: drools-core) (was: drools-compiler) > Support "Defeasible" rules in Drools > ------------------------------------ > > Key: DROOLS-114 > URL: https://issues.jboss.org/browse/DROOLS-114 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Davide Sottara > Assignee: Davide Sottara > Priority: Critical > > Very roughly speaking, "defeasiblity" is about rules being able to prevent other rules from firing, or canceling the conclusions other rules. > It is used to manage "exceptions" or "(counter)arguments", where different rules lead to conflicting conclusions and a resolution strategy has to be applied, depending on some relative ordering (strength, salience, temporal, weight, etc..). > While an ad-hoc implementation is possible combining salience, appropriate insertions/retractions and the rule-based agenda, a more declarative approach should be provided to the user. > This lack of a feature is currently a blocker for the adoption of Drools in several medical and legal communities, just to cite some. -- 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, 8 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 April 2013