November 2010 - jboss-jira - Jboss List Archives

[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

13 years, 3 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

13 years, 3 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

13 years, 3 months

5
11
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

13 years, 3 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

13 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8429) Verify log messages from OSGi bundles feed to aggreaged logfile

by Thomas Diesler (JIRA)

Verify log messages from OSGi bundles feed to aggreaged logfile --------------------------------------------------------------- Key: JBAS-8429 URL: https://jira.jboss.org/browse/JBAS-8429 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: OSGi integration Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: 7.0.0.M1 A bundle may use LogService, SLF4J, JDK, Apache Commons or JBoss Logging. All of these must feed to the common log system -- 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

13 years, 3 months

3
10
0 / 0

[JBoss JIRA] Created: (JBRULES-1778) Drools builder raises errors for non-decision tables XLS files

by Edson Tirelli (JIRA)

Drools builder raises errors for non-decision tables XLS files -------------------------------------------------------------- Key: JBRULES-1778 URL: https://jira.jboss.org/jira/browse/JBRULES-1778 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M1 Reporter: Edson Tirelli Assignee: Kris Verlaenen Fix For: FUTURE As it is now, the eclipse "drools builder" is raising errors for any XLS file that is not a decision table. For instance, in drools-examples there is the ExampleCheese.xls file used for a drools-template example that acuses the following error: No RuleTable's were found in spreadsheet. ExampleCheese.xls drools-examples/src/main/rules/org/drools/examples Unknown Drools 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

13 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2284) OutOfMemoryException at DT loading

by Sergey Vanskov (JIRA)

OutOfMemoryException at DT loading ---------------------------------- Key: JBRULES-2284 URL: https://jira.jboss.org/jira/browse/JBRULES-2284 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-decisiontables Affects Versions: 5.0.1.FINAL Environment: Core2Quad Windows XP Pro 64 Reporter: Sergey Vanskov Assignee: Mark Proctor I have created DT having 20.000 rows with 4 conditions and 1 action in CSV format and set the following parameters for JVM -Xmx3072M -XX:MaxPermSize=256M. I haveOutOfMemoryException with the following stack trace java.lang.OutOfMemoryError: Java heap space at java.lang.String.format(String.java:2558) at org.drools.lang.DroolsParserExceptionFactory.formatParserLocation(DroolsParserExceptionFactory.java:203) at org.drools.lang.DroolsParserExceptionFactory.createErrorMessage(DroolsParserExceptionFactory.java:104) at org.drools.lang.DroolsParserExceptionFactory.createDroolsException(DroolsParserExceptionFactory.java:89) at org.drools.lang.DRLParser.reportError(DRLParser.java:350) at org.antlr.runtime.BaseRecognizer.recoverFromMismatchedToken(BaseRecognizer.java:624) at org.antlr.runtime.BaseRecognizer.match(BaseRecognizer.java:115) at org.drools.lang.DRLParser.fact(DRLParser.java:9841) at org.drools.lang.DRLParser.lhs_pattern(DRLParser.java:9388) at org.drools.lang.DRLParser.pattern_source(DRLParser.java:7432) at org.drools.lang.DRLParser.lhs_unary(DRLParser.java:6582) at org.drools.lang.DRLParser.lhs_and(DRLParser.java:6229) at org.drools.lang.DRLParser.lhs_or(DRLParser.java:5877) at org.drools.lang.DRLParser.lhs(DRLParser.java:5673) at org.drools.lang.DRLParser.normal_lhs_block(DRLParser.java:5580) at org.drools.lang.DRLParser.when_part(DRLParser.java:3975) at org.drools.lang.DRLParser.rule(DRLParser.java:3769) at org.drools.lang.DRLParser.statement(DRLParser.java:993) at org.drools.lang.DRLParser.compilation_unit(DRLParser.java:484) at org.drools.compiler.DrlParser.compile(DrlParser.java:238) at org.drools.compiler.DrlParser.parse(DrlParser.java:78) at org.drools.compiler.DrlParser.parse(DrlParser.java:83) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:275) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:510) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:31) .... Is 3Gb not enough for such a problem?! How may memory requirements be estimated? -- 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

13 years, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2297) Enable marshalling of events in drools fusion

by Maciej Prochniak (JIRA)

Enable marshalling of events in drools fusion --------------------------------------------- Key: JBRULES-2297 URL: https://jira.jboss.org/jira/browse/JBRULES-2297 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core, drools-core (fusion) Affects Versions: 5.1.0.M1 Reporter: Maciej Prochniak Assignee: Mark Proctor Currently, when one tries to (un)marshall EventFactHandle an exception is thrown, as default marshaller recognizes only DefaultFactHandle. -- 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

13 years, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (JBBOOT-116) Implement a Graceful Shutdown API and Implementation

by Andrew Lee Rubinger (JIRA)

Implement a Graceful Shutdown API and Implementation ----------------------------------------------------- Key: JBBOOT-116 URL: https://jira.jboss.org/jira/browse/JBBOOT-116 Project: JBoss Bootstrap Issue Type: Feature Request Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger As identified by the Summer 2009 AS Meeting. Requirements: * Decoupled sufficiently from other Bootstrap mechanisms as to not leak out dependencies * 2-phase event-listener registration API * May be injected into MC Beans * 1st phase is a concurrent broadcast to all subsystems which have registered: "prepare for shutdown" * When all listeners have reported "ready", fire 2nd phase: "shutdown" -- 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

13 years, 4 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2010