Uploaded image for project: 'JBRULES'
  1. JBRULES
  2. JBRULES-2749

Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 5.1.1.FINAL
    • Fix Version/s: 5.4.0.Final
    • Labels:
      None
    • Environment:

      Environment 1: Fedora Core 12 x86_64, Sun JVM 1.6.0_20 64-bit Server VM
      Environment 2: Windows XP Professional, Service Pack 3, 32 bit; Sun JVM 1.6.0_20 32-bit Server VM

    • Steps to Reproduce:
      Hide

      1. Unpack attached git repository.
      2. Run "mvn test" on the command line
      OR
      2.1: Open IntelliJ IDEA module file drools-boundary-tests.iml
      2.2: locate test file RuleDoesNotFireIfUsingDeclaredFunctionAndTooManyPackages
      2.3: create TestNG run configuration for this test class
      2.4: set working directory to directory drools-boundary-tests.git
      2.5: run this run configuration from within IDEA

      Show
      1. Unpack attached git repository. 2. Run "mvn test" on the command line OR 2.1: Open IntelliJ IDEA module file drools-boundary-tests.iml 2.2: locate test file RuleDoesNotFireIfUsingDeclaredFunctionAndTooManyPackages 2.3: create TestNG run configuration for this test class 2.4: set working directory to directory drools-boundary-tests.git 2.5: run this run configuration from within IDEA

      Description

      A certain rule suddenly stops firing when adding more and more rules to the knowledge base, which (not only?) on first sight have nothing to do with the rule in question.

      We created a few unit tests which show the faulty behaviour.

      What we observed so far:

      • when using declared functions plus declared data types, this error occurrs.
      • sometimes, one can work around this problem by renaming a package. We're not sure if this is a reliable workaround, i. e. works in all situations.
      • one can work around this problem by not using declared functions. We're not sure if this is a reliable workaround.

      Find attached a ZIPed git repository containing:

      • a Maven 2.1+ pom.xml suitable to trigger the unit tests via mvn test
      • Java source files for a TestNG-based unit test
      • example drools source files to illustrate the problem (used by the unit tests)

      Please have a look at java file RuleDoesNotFireIfUsingDeclaredFunctionAndTooManyPackages.java. This should make quite clear what we're expecting of the drools library and where it fails to fulfil these expectations.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  mark.proctor Mark Proctor
                  Reporter:
                  akonermann Ansgar Konermann
                • Votes:
                  2 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: