August 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1908) updated Drools docs content from SOA 4.2.CP03 Rules Guide

by Darrin Mison (JIRA)

updated Drools docs content from SOA 4.2.CP03 Rules Guide --------------------------------------------------------- Key: JBRULES-1908 URL: https://jira.jboss.org/jira/browse/JBRULES-1908 Project: JBoss Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-docs-expert Reporter: Darrin Mison Assignee: Mark Proctor I revised the language of the "Insertion" section while fixing a couple of reported grammatical errors for the 4.2.CP03 SOA Rules Guide. The original language is the same in: http://anonsvn.jboss.org/repos/labs/labs/jbossrules/soa_tags/4.3.0.FP01_B... , so these changes would also apply to the most recent docs. Updated content below, the section ids are different but you get the idea ;-) <section id="sect-JBoss_Rules_Reference_Manual-WorkingMemory_and_StatefulStateless_Sessions-Insertion"> <title>Insertion</title> <para> <firstterm>Insertion</firstterm> is the act of telling the WorkingMemory about the facts. </para> <important> <para> In many Expert Systems the term used for this concept is <firstterm>assert</firstterm> or <firstterm>assertion</firstterm>. However as the keyword <methodname>assert</methodname> is already used in many languages, Drools uses the keyword & term <methodname>insert</methodname>. You will often encounter these terms used interchangably in discussion of Rules Engines. </para> </important> <para> When inserted, the rule is examined for matches against the rules. The work of determining what rules to fire is done during insertion, but no rules are executed at this time. The rules are executed when <methodname>fireAllRules()</methodname> is called, and it should only be called after you have inserted all your facts. </para> <para> It is a common misconception that rule matching occurs when <methodname>fireAllRules()</methodname> is called. </para> <para> When an Object is inserted it returns a FactHandle. This FactHandle is the token used to represent your inserted Object inside the WorkingMemory, it is also how you will interact with the Working Memory when you wish to retract or modify an object. </para> <programlisting language="java">Cheese stilton = new Cheese("stilton"); FactHandle stiltonHandle = session.insert( stilton );</programlisting> <para> As mentioned in <xref linkend="sect-JBoss_Rules_Reference_Manual-The_Drools_Rule_Engine-RuleBase" /> a Working Memory can operate in two assertions modes: <firstterm>equality</firstterm> and <firstterm>identity</firstterm>. Identity is the default mode. The assertion mode determines how the Working Memory stores the facts and how it compares the newly inserted fact to previously inserted ones. If the Working Memory determines the fact to "be the same" as an already inserted one it will ignore the new fact and return the FactHandle for the previously inserted one. </para> <variablelist> <varlistentry> <term>Identity</term> <listitem> <para> Identity Mode uses an <classname>IdentityHashMap</classname>to store all asserted Objects. New facts being inserted are compared to existing facts "by reference". A new FactHandle will be returned if the object being inserted is not a reference to an object that has been inserted previously. </para> </listitem> </varlistentry> <varlistentry> <term>Equality</term> <listitem> <para> Equality Mode uses a <classname>HashMap</classname> to store all asserted Objects. New facts being inserted are compared to existing facts "by value". A new FactHandle will be returned if the content of the object is not identical to that of a previously inserted object. </para> </listitem> </varlistentry> </variablelist> </section> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

5
7
0 / 0

[JBoss JIRA] Created: (JBRULES-2112) Cannot build Drools IDE w/ OpenJDK 6 (vm crashes)

by Nick Boldt (JIRA)

Cannot build Drools IDE w/ OpenJDK 6 (vm crashes) ------------------------------------------------- Key: JBRULES-2112 URL: https://jira.jboss.org/jira/browse/JBRULES-2112 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Nick Boldt Assignee: Mark Proctor Drools 5.0.x can compile with OpenJDK6; Drools 5.1 cannot. See attached logs. This prevents the JBoss Tools build from being able to run locally on Fedora w/ the out-of-box JVM (Open JDK 6). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

6
9
0 / 0

[JBoss JIRA] Created: (JBCL-84) Extend the ClassLoadingMetaData filtered package semantics

by Adrian Brock (JIRA)

Extend the ClassLoadingMetaData filtered package semantics ---------------------------------------------------------- Key: JBCL-84 URL: https://jira.jboss.org/jira/browse/JBCL-84 Project: JBoss ClassLoader Issue Type: Feature Request Components: MetaData Reporter: Adrian Brock Currently the ClassLoadingMetaData has some includedPackages and excludedPackages metadata. This is just a comma seperated list of explicit package names. This metadata should be extended to make it more flexible. e.g. using globing <classloader> <excluded type="glob">com.foo.*</included> or explicitly naming the filter <classloader> <excluded class="com.foo.MyClassFilter>...</excluded> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1135) Move generation should be described in a drl

by Geoffrey De Smet (JIRA)

Move generation should be described in a drl -------------------------------------------- Key: JBRULES-1135 URL: http://jira.jboss.com/jira/browse/JBRULES-1135 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Solver Affects Versions: 4.0.0.GA Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Fix For: FUTURE instead of MoveFactory POJO -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2049) org.drools.runtime.rule StatefulRuleSession.fireAllRules(org.drools.runtime.rule.AgendaFilter af) has no AgendaFilter implementations

by Bob Shanahan (JIRA)

org.drools.runtime.rule StatefulRuleSession.fireAllRules(org.drools.runtime.rule.AgendaFilter af) has no AgendaFilter implementations ------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2049 URL: https://jira.jboss.org/jira/browse/JBRULES-2049 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-api, drools-core Affects Versions: 5.0.0.CR1 Environment: Java 1.5 Reporter: Bob Shanahan Assignee: Mark Proctor StatefulSession.fireAllRules(org.drools.spi.AgendaFilter af) has several implementations of AgendaFilter for filtering rules. Why aren't the AgendaFilters common? Even the Activation class between them is different, so it is not simple to workaround by wrapping org.drools.spi.AgendaFilter impls. It would be handy if there were out-of-the-box AgendaFilters for implementations of StatefulRuleSession. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

6
8
0 / 0

[JBoss JIRA] Created: (JGRP-1026) Harden merge

by Bela Ban (JIRA)

Harden merge ------------ Key: JGRP-1026 URL: https://jira.jboss.org/jira/browse/JGRP-1026 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.9 Make sure that no merge is ever left hanging, e.g. due to the crash of the merge coordinator after the initial phase. This could prevent furthur merges. Analyze the code and make sure that eventually merges are always completed or aborted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2203) NullPointerException When Using Conditional Element "or" in LHS Together with a Return Value Restriction

by Christian Spurk (JIRA)

NullPointerException When Using Conditional Element "or" in LHS Together with a Return Value Restriction -------------------------------------------------------------------------------------------------------- Key: JBRULES-2203 URL: https://jira.jboss.org/jira/browse/JBRULES-2203 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.0.1.FINAL Environment: Drools 5.0.1 used in an Eclipse Drools project under Windows XP with Java 1.6 Reporter: Christian Spurk Assignee: Mark Proctor When using the conditional element "or" on the left hand side of a rule together with a return value restriction somewhere in the same rule, I get the following exception: Exception in thread "main" java.lang.NullPointerException at org.drools.rule.ReturnValueRestriction.equals(ReturnValueRestriction.java:304) at org.drools.rule.ReturnValueConstraint.equals(ReturnValueConstraint.java:121) at org.drools.reteoo.AlphaNode.equals(AlphaNode.java:218) at org.drools.reteoo.SingleObjectSinkAdapter.getMatchingNode(SingleObjectSinkAdapter.java:48) at org.drools.reteoo.builder.BuildUtils.attachNode(BuildUtils.java:130) at org.drools.reteoo.builder.PatternBuilder.attachAlphaNodes(PatternBuilder.java:295) at org.drools.reteoo.builder.PatternBuilder.attachPattern(PatternBuilder.java:117) at org.drools.reteoo.builder.PatternBuilder.build(PatternBuilder.java:70) at org.drools.reteoo.builder.GroupElementBuilder$AndBuilder.build(GroupElementBuilder.java:126) at org.drools.reteoo.builder.GroupElementBuilder.build(GroupElementBuilder.java:73) at org.drools.reteoo.builder.ReteooRuleBuilder.addSubRule(ReteooRuleBuilder.java:153) at org.drools.reteoo.builder.ReteooRuleBuilder.addRule(ReteooRuleBuilder.java:126) at org.drools.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:117) at org.drools.reteoo.ReteooRuleBase.addRule(ReteooRuleBase.java:362) at org.drools.common.AbstractRuleBase.addRule(AbstractRuleBase.java:618) at org.drools.common.AbstractRuleBase.addPackages(AbstractRuleBase.java:500) at org.drools.reteoo.ReteooRuleBase.addPackages(ReteooRuleBase.java:379) at org.drools.impl.KnowledgeBaseImpl.addKnowledgePackages(KnowledgeBaseImpl.java:121) at com.sample.DroolsTest.readKnowledgeBase(DroolsTest.java:48) at com.sample.DroolsTest.main(DroolsTest.java:26) Here is a simple test case which can be used to reproduce the issue: /* JAVA FILE TO LOAD THE RULE */ package com.sample; import org.drools.KnowledgeBase; import org.drools.KnowledgeBaseFactory; import org.drools.builder.KnowledgeBuilder; import org.drools.builder.KnowledgeBuilderError; import org.drools.builder.KnowledgeBuilderErrors; import org.drools.builder.KnowledgeBuilderFactory; import org.drools.builder.ResourceType; import org.drools.io.ResourceFactory; import org.drools.runtime.StatefulKnowledgeSession; public class DroolsTest { private int arg; public int getArg() { return this.arg; } public void setArg(int arg) { this.arg = arg; } public static final void main(String[] args) throws Exception { KnowledgeBase kbase = readKnowledgeBase(); StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession(); DroolsTest test = new DroolsTest(); test.setArg(2); ksession.insert(test); ksession.fireAllRules(); } /* taken verbatim from the Hello World sample */ private static KnowledgeBase readKnowledgeBase() throws Exception { KnowledgeBuilder kbuilder = KnowledgeBuilderFactory .newKnowledgeBuilder(); kbuilder.add(ResourceFactory.newClassPathResource("Sample.drl"), ResourceType.DRL); KnowledgeBuilderErrors errors = kbuilder.getErrors(); if (errors.size() > 0) { for (KnowledgeBuilderError error : errors) { System.err.println(error); } throw new IllegalArgumentException("Could not parse knowledge."); } KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase(); kbase.addKnowledgePackages(kbuilder.getKnowledgePackages()); return kbase; } } /* PROBLEMATIC RULE FILE */ package com.sample import com.sample.DroolsTest; rule "test" when DroolsTest( arg == (1 + 1) ); // REMOVE THE COMMENTED PARTS BELOW TO GET THE EXCEPTION: //(or eval(true); eval(true); //) then System.out.println( "it works!" ); end When the above Java file is compiled and run in combination with the given rule file, everything works fine. However, if the marked parts of the rule are uncommented, then you get the exception. PS: It seems that the issue has been existing in previous Drools versions already, see https://jira.jboss.org/jira/browse/JBSEAM-3064 for example ("Drools 4.0.7 don't like 'action == (DocumentType.USER.extendedName())' and multiple OR's - weird!"). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JGRP-955) AckSenderWindow: use ConcurrentSkipListMap instead of ConcurrentHashMap

by Bela Ban (JIRA)

AckSenderWindow: use ConcurrentSkipListMap instead of ConcurrentHashMap ----------------------------------------------------------------------- Key: JGRP-955 URL: https://jira.jboss.org/jira/browse/JGRP-955 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.0 So we have the seqnos sorted, and can implement ack(seqno) as a headSet(seqno).clear(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-403) Refactoring of MessageDispatcher, RpcDispatcher, RequestCorrelator and GroupRequest

by Bela Ban (JIRA)

Refactoring of MessageDispatcher, RpcDispatcher, RequestCorrelator and GroupRequest ----------------------------------------------------------------------------------- Key: JGRP-403 URL: http://jira.jboss.com/jira/browse/JGRP-403 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 We may be able to trash GroupRequest and RequestCorrelator, this functionality can be provided by MessageDispatcher -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2211) StatefulKnowledgeSession leaves threads running

by Edson Tirelli (JIRA)

StatefulKnowledgeSession leaves threads running ----------------------------------------------- Key: JBRULES-2211 URL: https://jira.jboss.org/jira/browse/JBRULES-2211 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.1.FINAL, 5.0.0.FINAL Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.1.0.M1 Hi all, I've downloaded Drools fusion sample and started to make some changes to the code (first of all wipe out the UI so I can test it easier). I tried to get to a minimal set so I can run a console main class and see what happens but I am facing a strange behaviour. As soon as I start pushing events into the WorkingMemoryEntryPoint ("StockTick stream") a Thread - not daemonized since it blocks shutdown from ending - is spawned and this prevents my JVM from shutting down (obviously if I call System.exit(0) it will but I am avoiding this). I've tried both to halt and dispose the session that this entry point belongs but with no success. Does anyone know how could I get rid of this thread? ================== Hi Edson! as I've already mentioned I've modified the sample so, if you get the StockTick sample and replace the Main class this will run fine. The sample shuts down fine but as I saw it sets the JFrame uses frame.setDefaultCloseOperation( WindowConstants.EXIT_ON_CLOSE ); which in turn makes the trick. Below the code of my modified main class: package org.drools.examples.broker; import org.drools.KnowledgeBase; import org.drools.KnowledgeBaseConfiguration; import org.drools.KnowledgeBaseFactory; import org.drools.builder.KnowledgeBuilder; import org.drools.builder.KnowledgeBuilderFactory; import org.drools.builder.ResourceType; import org.drools.conf.EventProcessingOption; import org.drools.examples.broker.model.Company; import org.drools.examples.broker.model.CompanyRegistry; import org.drools.examples.broker.model.StockTick; import org.drools.io.ResourceFactory; import org.drools.runtime.StatefulKnowledgeSession; import org.drools.runtime.rule.WorkingMemoryEntryPoint; public class Main { private static final String RULES_FILE = "/broker.drl"; static StatefulKnowledgeSession session; static WorkingMemoryEntryPoint tickStream; /** * @param args */ public static void main(String[] args) throws Exception { // set up and show main window CompanyRegistry companies = new CompanyRegistry(); KnowledgeBuilder builder = KnowledgeBuilderFactory.newKnowledgeBuilder(); try { builder.add( ResourceFactory.newInputStreamResource( Main.class.getResourceAsStream( RULES_FILE ) ), ResourceType.DRL); } catch ( Exception e ) { e.printStackTrace(); } if( builder.hasErrors() ) { System.err.println(builder.getErrors()); System.exit( 0 ); } KnowledgeBaseConfiguration conf = KnowledgeBaseFactory.newKnowledgeBaseConfiguration(); conf.setOption( EventProcessingOption.STREAM ); KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase( conf ); kbase.addKnowledgePackages( builder.getKnowledgePackages() ); session = kbase.newStatefulKnowledgeSession(); session.setGlobal( "services", new BrokerServices() { public void log(String message) { System.out.println(message); } }); for( Company company : companies.getCompanies() ) { session.insert( company ); } session.fireAllRules(); tickStream = session.getWorkingMemoryEntryPoint( "StockTick stream" ); for (int i=10;i>0;i--) { tickStream.insert(new StockTick("RHT", i*10, System.currentTimeMillis())); session.getAgenda().getAgendaGroup( "evaluation" ).setFocus(); session.fireAllRules(); } session.dispose(); session.halt(); System.out.println("Still running..."); } } regards, Rafael Ribeiro -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
8
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 August 2009