April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2987) Literal expression not possible in constraint

by Wolfgang Laun (JIRA)

Literal expression not possible in constraint --------------------------------------------- Key: JBRULES-2987 URL: https://issues.jboss.org/browse/JBRULES-2987 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 3.0-beta3 Reporter: Wolfgang Laun Assignee: Mark Proctor declare Article artid : int; artname : String; custid : int; end declare Customer custid : int endrule "articles of a customer" when $c: Customer( $custid: custid ) $a: Article( $artid: artid, artname == "mou" + "se", $custid : custid == $custid ) then end This produces the (misleading) error message below, but should work according to Mark Proctor. Notice that artname == ("mou" + "se") works correctly. Unable to return Declaration for identifier '"mou" + "se"' : [Rule name='articles of a customer'] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2878) NPE due to session.update with 1 or 2 invalid operands

by Wolfgang Laun (JIRA)

NPE due to session.update with 1 or 2 invalid operands ------------------------------------------------------ Key: JBRULES-2878 URL: https://issues.jboss.org/browse/JBRULES-2878 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.1.1.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Counter counter = new Counter( initial ); this.session.insert( counter ); And now each of these calls session.update( session.getFactHandle( null ), null ); session.update( session.getFactHandle( counter ), null ); session.update( session.getFactHandle( null ), counter ); results in a NPE Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at org.drools.common.ObjectTypeConfigurationRegistry.getObjectTypeConf(ObjectTypeConfigurationRegistry.java:58) at org.drools.common.NamedEntryPoint.update(NamedEntryPoint.java:382) at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:981) at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:954) at org.drools.impl.StatefulKnowledgeSessionImpl.update(StatefulKnowledgeSessionImpl.java:266) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3002) Invalid comparison operator (=) causes EmptyStackException in DRLParser/ParserHelper

by Wolfgang Laun (JIRA)

Invalid comparison operator (=) causes EmptyStackException in DRLParser/ParserHelper ------------------------------------------------------------------------------------ Key: JBRULES-3002 URL: https://issues.jboss.org/browse/JBRULES-3002 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.2.0.M2 Reporter: Wolfgang Laun Assignee: Mark Proctor class Customer { int custid; //... } rule x when $c: Customer( custid = 100 ) // Typo, wanted: "==" then end [0,0]: Line 47:0 unexpected exception at input 'rule'. Exception: java.util.EmptyStackException. Stack trace: java.util.EmptyStackException at java.util.Stack.peek(Stack.java:102) at java.util.Stack.pop(Stack.java:84) at org.drools.lang.ParserHelper.popParaphrases(ParserHelper.java:409) at org.drools.lang.ParserHelper.end(ParserHelper.java:723) at org.drools.lang.DRLParser.rule(DRLParser.java:915) at org.drools.lang.DRLParser.statement(DRLParser.java:248) at org.drools.lang.DRLParser.compilationUnit(DRLParser.java:143) at org.drools.compiler.DrlParser.compile(DrlParser.java:225) at org.drools.compiler.DrlParser.parse(DrlParser.java:136) at org.drools.compiler.DrlParser.parse(DrlParser.java:141) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:292) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:471) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:28) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2222) Rule silently discarded if RHS calls an undefined DRL function

by Wolfgang Laun (JIRA)

Rule silently discarded if RHS calls an undefined DRL function -------------------------------------------------------------- Key: JBRULES-2222 URL: https://jira.jboss.org/jira/browse/JBRULES-2222 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.0.1.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor If a function bar is called on a RHS of a rule in the same .drl file without being defined in the same .drl file, the .drl is compiled without kBuilder.getErrors() returning an error, and the rule is silently discarded (not firing, although it should). - Note that this error occurred when there was a function bar defined in another .drl file of the same package. Eclipse does indicate an error. -- 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

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2761) Restriction operator parameters should be strings, not token sequences

by Wolfgang Laun (JIRA)

Restriction operator parameters should be strings, not token sequences ---------------------------------------------------------------------- Key: JBRULES-2761 URL: https://jira.jboss.org/browse/JBRULES-2761 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Wolfgang Laun Assignee: Mark Proctor User defined operators (similar to "matches" or the temporal ops) may have parameters, written in '[' and ']' after the identifier denoting the relational operator. Text between the brackets is currently parsed as a "chunk", requiring the text to be composed from tokens recognized by the lexer. This is too restrictive since all Unicode characters that aren't letters (and this part of an identifier) are simply dropped. It should be simple to parse the text between '[' and ']' as a special form of recursive string, with brackets as delimiters. This means that op[foo[1]] is OK, but op{bar[[] is not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2954) parser issues with metadata & type NT

by Wolfgang Laun (JIRA)

parser issues with metadata & type NT ------------------------------------- Key: JBRULES-2954 URL: https://issues.jboss.org/browse/JBRULES-2954 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Wolfgang Laun Assignee: Mark Proctor (This is just to get a JIRA-number, never mind the sloppy reporting): - @meta( key = "key", num = "num" ) causes NPE - type names with "<x>" or "[]" cause crashes -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1923) Rule order counts when adding inheriting rules

by Toni Rikkola (JIRA)

Rule order counts when adding inheriting rules ---------------------------------------------- Key: JBRULES-1923 URL: https://jira.jboss.org/jira/browse/JBRULES-1923 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: FUTURE Reporter: Toni Rikkola Assignee: Mark Proctor When inheriting rules, the order they are written to DRL counts. dward noticed this when using Guvnor. There is no way to control the order of the rules in Guvnor, so because of this inheritance doesn't always work. This works: rule A when ... then end rule B extends A when ... then end This doesn't work: rule B extends A when ... then end rule A when ... then 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

14 years, 9 months

5
11
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1855) Failed fail-over doesn't trigger client's ExceptionListener

by Justin Bertram (JIRA)

Failed fail-over doesn't trigger client's ExceptionListener ----------------------------------------------------------- Key: JBMESSAGING-1855 URL: https://issues.jboss.org/browse/JBMESSAGING-1855 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP09 Reporter: Justin Bertram Assignee: Yong Hao Gao If the cluster node to which a client is connected is dropped gracefully and the cluster is using FailoverOnNodeLeave = false then the client's connection will die and its exception listener will not be triggered so it may manually reconnect to another node of the cluster. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
12
0 / 0

[JBoss JIRA] Created: (SECURITY-74) Policy Management Console using JBoss SEAM

by Anil Saldhana (JIRA)

Policy Management Console using JBoss SEAM ------------------------------------------ Key: SECURITY-74 URL: http://jira.jboss.com/jira/browse/SECURITY-74 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossXACML-Console Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 Need for a progressive Policy Management console using JBoss SEAM. The JAXB2 object model provided with JBoss XACML can be used to construct the policies. -- 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

14 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-693) Incorporate MultithreadedTestCase (MTC) usage into JGroups testsuite

by Richard Achmatowicz (JIRA)

Incorporate MultithreadedTestCase (MTC) usage into JGroups testsuite -------------------------------------------------------------------- Key: JGRP-693 URL: http://jira.jboss.com/jira/browse/JGRP-693 Project: JGroups Issue Type: Task Environment: JGroups testsuite test cases Reporter: Richard Achmatowicz Assigned To: Bela Ban Fix For: 2.7 MultithreadedTestCase (MTC) is an open-source testing framework which supports the writing of multithreaded test cases. It introduces a global tick-counter which provides a deterministic form of thread synchronization, based on the number of times all threads in a test case are blocked. The tool works well ina debugger, unlike other approximate forms of synchronization (e.g. sleep()) This issue concerns using MTC in order to simplify and improve test cases in the JGroups test suite in which concurrency and blocking are at issue. -- 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

14 years, 9 months

2
2
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 2011