April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2915) Dynamic salience expression: incorrect evaluation of Integer.MIN_VALUE

by Wolfgang Laun (JIRA)

Dynamic salience expression: incorrect evaluation of Integer.MIN_VALUE ---------------------------------------------------------------------- Key: JBRULES-2915 URL: https://issues.jboss.org/browse/JBRULES-2915 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.M1 Reporter: Wolfgang Laun Assignee: Mark Proctor Using salience (Integer.MIN_VALUE) does not result in a very low-priority rule. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2966) Drools Examples: mortgage-example gives 401 http status in drools 5.1.1

by feuertod feuertod (JIRA)

Drools Examples: mortgage-example gives 401 http status in drools 5.1.1 ----------------------------------------------------------------------- Key: JBRULES-2966 URL: https://issues.jboss.org/browse/JBRULES-2966 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.1.1.FINAL Environment: Any Reporter: feuertod feuertod Assignee: Mark Proctor Problem occurrs in drools-examples downloadable distro available @ http://download.jboss.org/drools/release/5.1.1.34858.FINAL/drools-5.1.1-e... The mortgage examples properties file doesn't support basic authentication when attempting to retrieve a package, and gives a HTTP status of 401. http://drools.46999.n3.nabble.com/guvnor-integration-gives-401-error-td24... http://drools.46999.n3.nabble.com/rules-users-Can-t-Get-Rules-To-Modify-O... An xml configuration using the changeset-xml defined with the drools schema overcomes this problem, but is not present in mortgage-examples Also, the mortgage-examples says it is for drools 5.1.1 (file name of drools-5.1.1-examples.zip), but the mortgage examples uses the drools 5.0.1 JARs: drools-api-5.0.1.SNAPSHOT.jar drools-core-5.0.1.SNAPSHOT.jar -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2863) Tuple is null when firing an activation

by Edson Tirelli (JIRA)

Tuple is null when firing an activation --------------------------------------- Key: JBRULES-2863 URL: https://issues.jboss.org/browse/JBRULES-2863 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL Reporter: Edson Tirelli Assignee: Edson Tirelli Priority: Critical Fix For: 5.2.0.M1 For some reason, an activation is firing with a nulled tuple, i.e., it seems the activation is being created, but not properly removed from the agenda. There are not many details but the rule in question uses both ruleflow-group and no-loop. Reported by Dan Quinn. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1647) @Resource injection of primitive types from JNDI

by Dennis Reed (JIRA)

@Resource injection of primitive types from JNDI ------------------------------------------------ Key: EJBTHREE-1647 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1647 Project: EJB 3.0 Issue Type: Bug Components: injection Affects Versions: AS 4.2.1.GA Reporter: Dennis Reed The following does not work to inject an arbitrary JNDI entry for primitive/primitive wrapper/String fields: @Resource( mappedName = "java:/blah/blah" ) String myVar; In older versions, a "NYI" exception was thrown (then changed to a different exception before getting to the user). In newer versions, the literal value in mappedName is injected. For all other types, the JNDI entry injection works. For example, the following does inject that same String from JNDI: @Resource( mappedName = "java:/blah/blah" ) Object myVar; -- 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

5
13
0 / 0

[JBoss JIRA] Created: (JBRULES-2588) Error creates null package without generating error message

by Thomas Hehl (JIRA)

Error creates null package without generating error message ----------------------------------------------------------- Key: JBRULES-2588 URL: https://jira.jboss.org/browse/JBRULES-2588 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.0.1.FINAL Environment: Windows XP/Eclipse Ganymeade Reporter: Thomas Hehl Assignee: Mark Proctor Priority: Minor Fix For: 5.0.2, 5.1.0.CR1, FUTURE PackageBuilder contains the following method: public void addPackageFromDrl(final Reader reader) throws DroolsParserException, IOException { this.resource = new ReaderResource( reader ); final DrlParser parser = new DrlParser(); final PackageDescr pkg = parser.parse( reader ); this.results.addAll( parser.getErrors() ); if ( !parser.hasErrors() ) { addPackage( pkg ); } this.resource = null; } The problem is that if the parser generates errors, then the package is null and my application blows up later on with a null pointer exception, but the error messages are lost. To fix this problem I recommend a code change like: public void addPackageFromDrl(final Reader reader) throws DroolsParserException, IOException { this.resource = new ReaderResource( reader ); final DrlParser parser = new DrlParser(); final PackageDescr pkg = parser.parse( reader ); this.results.addAll( parser.getErrors() ); if ( parser.hasErrors() ) { System.err.println("Parser errors generating null package:" + this.results.toString()); else{ addPackage( pkg ); } this.resource = null; } This will cause an error dump in the log without changing any functionality. -- 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

15 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2343) Context assist in DSLR Editor

by Hamza Bakkali (JIRA)

Context assist in DSLR Editor ----------------------------- Key: JBRULES-2343 URL: https://jira.jboss.org/jira/browse/JBRULES-2343 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.1.FINAL Environment: Eclipse 3.4 Ganymede Reporter: Hamza Bakkali Assignee: Mark Proctor Fix For: 4.0.8 I have been using drools 4 for couple of months now and I am starting to get the hang of it. We recently decided to move to Dools 5 with Eclipse 3.4.2 (Ganymede). We unfortunately hit a major 'show stopper' (for us). In the DSLR editor: Context Assist + space + enter removes/replaces the whole line, not only the place holder. In other words: DSL: [*][]Log : {msg}=System.out.println("{msg}"); [*][]id1="some id label" DSLR: rule "MyRule" when then end If I Press L , control space --> the line Log:{msg} appears in the context menu. Hit enter I get Log :{msg} Now, If want to replace msg by id1. I position the cursor in the {msg}, hit ctrl space, id1 shows in the list. I hit enter the whole line disappear, and I am left with id1 instead of Log : id1 Is this a setting somewhere in eclipse itself?? I doubt it. The same thing use to work as expected in Drools 4. thanks. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2330) Add support to effective dated models in Drools

by Edson Tirelli (JIRA)

Add support to effective dated models in Drools ----------------------------------------------- Key: JBRULES-2330 URL: https://jira.jboss.org/jira/browse/JBRULES-2330 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 5.1.0.M1 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.1.0.M2 Effective dated models are models where the facts themselves have effective and expiration dates. Activations should only be created between facts that have an effective date range intersection and the intersection boundaries are meaningful attributes to the activation itself. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2218) Unknown error while parsing. This is a bug. Please contact the Development team.

by Udo Klinkmüller (JIRA)

Unknown error while parsing. This is a bug. Please contact the Development team. -------------------------------------------------------------------------------- Key: JBRULES-2218 URL: https://jira.jboss.org/jira/browse/JBRULES-2218 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse Affects Versions: 5.0.0.FINAL Environment: Eclipse 3.5 (Galileo), Mac OS X Reporter: Udo Klinkmüller Assignee: Mark Proctor rule "Arrival-Delayed-Upd" salience 1000 when #conditions VisitPair( $ov: oldVisit != null, $nv: visit ) $oaf: ArrivalFlight( onBlock == null, $ost: scheduledTime != null, $op: position != null ) from $ov.arrivalFlight $naf: ArrivalFlight( onBlock == null, (($nst: scheduledTime != null, != $ost) || ($np: position != null, != $op)) ) from $nv.arrivalFlighT then #actions Date vf = addMinutes($nst, 15); ResourceEvent re = eventBuilderFactory.getResourceVisitEventBuilder(EventType.ARRIVAL_DELAYED, $naf.getPositionKey(), vf) .visitKey($nv.getKey()) .build(); eventHandler.handleEvent(re); 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

7
12
0 / 0

[JBoss JIRA] Created: (JBRULES-2151) Parser exceptions

by Edson Tirelli (JIRA)

Parser exceptions ----------------- Key: JBRULES-2151 URL: https://jira.jboss.org/jira/browse/JBRULES-2151 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.0.1.FINAL Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.1.0.M1 Parser errors that raise the "Contact the development team" message. ================= a similar "contact-developers-bug" occurs when you write an empty not CE: not( ) ================= -- 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
7
0 / 0

[JBoss JIRA] Created: (JBRULES-2106) Allow "implicit" operators in the language

by Edson Tirelli (JIRA)

Allow "implicit" operators in the language ------------------------------------------ Key: JBRULES-2106 URL: https://jira.jboss.org/jira/browse/JBRULES-2106 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 5.0.1.FINAL Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.1.0.M1 It would be cool if we could develop and enable "implicit" operators. By that I mean, a method that returns a boolean and take 1 parameter could be used automatically. Example: Person( name startsWith "Edson" ) The engine would understand the "startsWith" implicit operator, and would call the method on the name String. -- 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
5
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