September 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1725) Time and length batch window support

by Heiko Braun (JIRA)

Time and length batch window support ------------------------------------ Key: JBRULES-1725 URL: https://jira.jboss.org/jira/browse/JBRULES-1725 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Heiko Braun Assignee: Mark Proctor Fix For: FUTURE Support for time and length batch windows in drools fusion. I.e. when $event: Alert() length_batch(10) then // process batch of 10 Alert events end or when $event: Alert() time_batch(60sec) then // process of n Alert events that did occur within 60 sec end -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-540) Create a Java Interface to allow JavaBeans to work more seamlessly as Facts

by Mark Proctor (JIRA)

Create a Java Interface to allow JavaBeans to work more seamlessly as Facts ----------------------------------------------------------------------------- Key: JBRULES-540 URL: http://jira.jboss.com/jira/browse/JBRULES-540 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Assemply/SPI Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m1 We want to move management of the bean and its working memory up a layer. When a bean is instantiated by an IoC framework it should weave in an interface to provide better background interoprability between the bean and working memories. further the IoC container should control the life cycle, assert and retract, of that bean in various working memories. -- 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, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1430) Improve Function feature

by longDuck dong (JIRA)

Improve Function feature ------------------------ Key: JBRULES-1430 URL: http://jira.jboss.com/jira/browse/JBRULES-1430 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Affects Versions: 4.0.4 Environment: all Reporter: longDuck dong Priority: Minor The current design of the Function is a bit limiting. for example, if I want to write a function to insert, update or retract facts, the current design does not support it. According to the docs http://downloads.jboss.com/drools/docs/4.0.4.17825.GA/html/ch06s04.html, functions are just helper methods. It would be more powerful if the function always passes the workingmemory to the function. This way, the functions can easily access the globals or access the rule engine. Basically, something similar to JESS funcall http://herzberg.ca.sandia.gov/docs/70/api/jess/Funcall.html. It also makes it easier for developers to encapsulate common actions in the consequence in a function and use it easily from a DSL. The pattern is well proven in CLIPS, JESS and haley. -- 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, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (JBRULES-1777) org.drools.reteoo.SchedulerTest.testDoLoopScheduledActivation failing on HP JVM (ia64)

by Lukas Petrovicky (JIRA)

org.drools.reteoo.SchedulerTest.testDoLoopScheduledActivation failing on HP JVM (ia64) -------------------------------------------------------------------------------------- Key: JBRULES-1777 URL: https://jira.jboss.org/jira/browse/JBRULES-1777 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 4.0.7 Reporter: Lukas Petrovicky Assignee: Mark Proctor org.drools.reteoo.SchedulerTest.testDoLoopScheduledActivation test is consistently failing on HP JVM. Only ia64, RISC is fine. Can be seen here: http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa43-rules-os-hp1... The reason it gives is: junit.framework.AssertionFailedError: expected:<4> but was:<3> at org.drools.reteoo.SchedulerTest.testDoLoopScheduledActivation(SchedulerTest.java:187) I'm testing with the version in SOA-P 4.3.0.GA_IR4. The version found in SOA-P 4.2.0 seems not to have such problem. -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1559) Ability to negate a constraint group

by Dirk Bergstrom (JIRA)

Ability to negate a constraint group ------------------------------------ Key: JBRULES-1559 URL: http://jira.jboss.com/jira/browse/JBRULES-1559 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: FUTURE Reporter: Dirk Bergstrom Assigned To: Mark Proctor Priority: Minor I want to write a rule that says "Find all long-eared dogs that do not have short, black hair". This seems like the simple way to do it: collect( Dog( ears=="long", not (hair=="short" && color=="black") ) But that doesn't parse. Some digging through the archives unearthed a mention of De Morgan's laws, which leads to: http://en.wikipedia.org/wiki/De_Morgan's_laws Which explains that I can instead write: collect( Dog( ears=="long", (hair!="short" || color!="black") ) Which, after some mental effort, turns out to be the right thing. However, had I not found the reference to De Morgan's Law, it would have taken me a long time to get there (if indeed I ever would have). The end result is also quite difficult to parse if you're not a logician, and thus not very user-friendly. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1662) Tomcat Debugging of Rules

by Paul Ryan (JIRA)

Tomcat Debugging of Rules ------------------------- Key: JBRULES-1662 URL: http://jira.jboss.com/jira/browse/JBRULES-1662 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Environment: Tomcat 5+ and Eclipse IDE Reporter: Paul Ryan Assigned To: Mark Proctor The ability to debug rules while running from a tomcat instance. This would be helpful for those of us that have services wrapping the rules so that we can debug into running rule sets. This feature should be capable of running its own instance of tomcat as well as attaching to a debug version of an externally running tomcat to allow for flexibility based on the users socket needs. This feature would be a huge selling point for enterprise applications of Drools. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1671) org.drools.integrationtests.DynamicRulesTest.testDynamicFunction fails with jrockit

by Jaroslaw Kijanowski (JIRA)

org.drools.integrationtests.DynamicRulesTest.testDynamicFunction fails with jrockit ----------------------------------------------------------------------------------- Key: JBRULES-1671 URL: http://jira.jboss.com/jira/browse/JBRULES-1671 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.7 Environment: http://anonsvn.labs.jboss.com/labs/jbossrules/tags/DROOLS_SOA_4_2_19937_CP2 Reporter: Jaroslaw Kijanowski Assigned To: Mark Proctor Please see SOA-621 for details, it affects the SOA branch -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1670) org.drools.agent.RuleAgentTest.testDirectory fails on windows on jrockit

by Jaroslaw Kijanowski (JIRA)

org.drools.agent.RuleAgentTest.testDirectory fails on windows on jrockit ------------------------------------------------------------------------ Key: JBRULES-1670 URL: http://jira.jboss.com/jira/browse/JBRULES-1670 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.7 Environment: http://anonsvn.labs.jboss.com/labs/jbossrules/tags/DROOLS_SOA_4_2_19937_CP2 Reporter: Jaroslaw Kijanowski Assigned To: Mark Proctor Please see SOA-620 for details, it affects the SOA branch -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1675) Xpath Default Constraint Evaluations

by Paul Ryan (JIRA)

Xpath Default Constraint Evaluations ------------------------------------ Key: JBRULES-1675 URL: http://jira.jboss.com/jira/browse/JBRULES-1675 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder, Eclipse IDE, Rule Assemply/SPI, Solver, Verifier, xml Reporter: Paul Ryan Assigned To: Mark Proctor A default set of constraint matchers for xpath based on loaded w3c DOMs would be very helpful. For our project we have alot of facts that are just an xml file (this seems to be the way the industry in general is going) that is calculated and being able to load that in to working memory and have constraint based node evaluations would be a very nice and attractive feature. I would suggest as a start a basic content equals (on elements it would match against text content and on attributes it would match against the node value) as well as a basic check for exists based on given xpath. Potential syntax: Fact( xml.xpath("/document//fragment[@id='myid']")) // Checks if the xpath exists in the property xml or Fact( xml.xpath("/document//fragment[@id='myid']") == "myvalue") // Checks if the text content of the fragment with the given id is "myvalue" or Fact( xml.xpath("/document//fragment[@id='myid']/@attr1") == "myattr") // Checks if the node value of the attribute attr1 in the given fragment is "myattr" with the property xml having been defined in the fact. I would suggest implementing this using the latest DOM stuff that has been recently released with xerces 2.9 and up as it has a very fast and efficient xpath evaluator. If you would like I think I can draw up some examples, however I don't think I know enough about drools core code to write this feature myself yet, maybe with some help. Also this constraint module may need a new interface for configuring the size limit (or other constraint) around when to load the xml into working memory. Maybe a annotation based solution in the fact is a good idea (e.g. put an annotation @LoadDOM on xml property in the fact for properties that should be loaded into DOM), or the other option is that the designer has to set the property up as an org.w3c.dom.Document for it to be consider pre-loadable. -- 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, 2 months

5
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1769) Improvements to pluggable operator framework

by Edson Tirelli (JIRA)

Improvements to pluggable operator framework -------------------------------------------- Key: JBRULES-1769 URL: https://jira.jboss.org/jira/browse/JBRULES-1769 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Edson Tirelli Assignee: Edson Tirelli e-mail from Michel Zimmermann: ----------- Hi Edson, I think I got it working :-) Edson Tirelli wrote: > For an example, look at the file SetEvaluatorsDefinition and look at > the BaseMemberOf inner class. So, all the logic is in there, but we > still used subclasses just to set the constructor attributes and > override the toString() method, but you could still implement > everything in a single class I guess. Yes, this approach makes sense as long as you don't need to use the different VariableContextEntry subclasses for handling double, char etc. Yet, this can be handled, too. toString(): You can avoid subclassing from your BaseMyEvaluatorClass to override toString() by using a string method like: public String toString() { return getValueType().getName() + " " + getOperator().getOperatorString(); } Regarding the evaluator API: If you only need one evaluator class (subclassed from BaseEvaluator), personally I don't like the > 10 static calls to addEvaluator(type, operator, myEvaluatorInstance) in the EvaluatorDefinition class. So, how about adding the method addDefaultEvaluator(operator, evaluatorClass) to EvaluatorCache, see attachment? This would allow you to register a evaluator as default and only overide the special cases... PS: If you are interested I will write some small tutorial about custom evaluators / operators in drools trunk. This might take a week or two, though. Any preferences regarding the format? Thanks for the help.... cu, Michael @SuppressWarnings("unchecked") public void addDefaultEvaluator(final Operator operator, Class evaluatorClass) { // define the constructor Class[] evaluatorParameters = new Class[2]; evaluatorParameters[0] = ValueType.class; evaluatorParameters[1] = Operator.class; // get the constructor try { Constructor<BaseEvaluator> constructor; constructor = evaluatorClass.getConstructor( evaluatorParameters ); // add feault operators addEvaluator(ValueType.ARRAY_TYPE, operator, constructor.newInstance(ValueType.ARRAY_TYPE, operator)); addEvaluator(ValueType.BIG_DECIMAL_TYPE, operator, constructor.newInstance(ValueType.BIG_DECIMAL_TYPE, operator)); addEvaluator(ValueType.BIG_INTEGER_TYPE, operator, constructor.newInstance(ValueType.BIG_INTEGER_TYPE, operator)); addEvaluator(ValueType.BOOLEAN_TYPE, operator, constructor.newInstance(ValueType.BOOLEAN_TYPE, operator)); addEvaluator(ValueType.PBOOLEAN_TYPE, operator, constructor.newInstance(ValueType.PBOOLEAN_TYPE, operator)); addEvaluator(ValueType.BYTE_TYPE, operator, constructor.newInstance(ValueType.BYTE_TYPE, operator)); addEvaluator(ValueType.PBYTE_TYPE, operator, constructor.newInstance(ValueType.PBYTE_TYPE, operator)); addEvaluator(ValueType.CHAR_TYPE, operator, constructor.newInstance(ValueType.CHAR_TYPE, operator)); addEvaluator(ValueType.PCHAR_TYPE, operator, constructor.newInstance(ValueType.PCHAR_TYPE, operator)); addEvaluator(ValueType.DATE_TYPE, operator, constructor.newInstance(ValueType.DATE_TYPE, operator)); addEvaluator(ValueType.DOUBLE_TYPE, operator, constructor.newInstance(ValueType.DOUBLE_TYPE, operator)); addEvaluator(ValueType.PDOUBLE_TYPE, operator, constructor.newInstance(ValueType.PDOUBLE_TYPE, operator)); addEvaluator(ValueType.FLOAT_TYPE, operator, constructor.newInstance(ValueType.FLOAT_TYPE , operator)); addEvaluator(ValueType.PFLOAT_TYPE, operator, constructor.newInstance(ValueType.PFLOAT_TYPE, operator)); addEvaluator(ValueType.INTEGER_TYPE, operator, constructor.newInstance(ValueType.INTEGER_TYPE, operator)); addEvaluator(ValueType.PINTEGER_TYPE, operator, constructor.newInstance(ValueType.PINTEGER_TYPE, operator)); addEvaluator(ValueType.LONG_TYPE, operator, constructor.newInstance(ValueType.LONG_TYPE, operator)); addEvaluator(ValueType.PLONG_TYPE, operator, constructor.newInstance(ValueType.PLONG_TYPE, operator)); addEvaluator(ValueType.OBJECT_TYPE, operator, constructor.newInstance(ValueType.OBJECT_TYPE, operator)); addEvaluator(ValueType.SHORT_TYPE, operator, constructor.newInstance(ValueType.SHORT_TYPE, operator)); addEvaluator(ValueType.PSHORT_TYPE, operator, constructor.newInstance(ValueType.PSHORT_TYPE, operator)); addEvaluator(ValueType.STRING_TYPE, operator, constructor.newInstance(ValueType.STRING_TYPE, operator)); } catch (SecurityException e) { // TODO Auto-generated catch block e.printStackTrace(); } catch (NoSuchMethodException e) { // TODO Auto-generated catch block e.printStackTrace(); } catch (IllegalArgumentException e) { // TODO Auto-generated catch block e.printStackTrace(); } catch (InstantiationException e) { // TODO Auto-generated catch block e.printStackTrace(); } catch (IllegalAccessException e) { // TODO Auto-generated catch block e.printStackTrace(); } catch (InvocationTargetException e) { // TODO Auto-generated catch block e.printStackTrace(); } } -- 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

2
13
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 September 2008