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

Declared imports should override the default java.lang.* imports

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 3.0.5
    • Fix Version/s: 3.0.6, 3.1-m1
    • Component/s: None
    • Labels:
      None
    • Environment:

      MS Windows XP SP2

      Description

      The use of a java.lang.* Class in the LHS of a rule causes Exception in thread "XXX" java.lang.Error: Unable to find unambiguously defined class 'XXX' errors when rules are loaded for parsing. Workaround is to use fully qualified Class name in LHS. For example:-

      package some.rules

      import a.package.name.Process

      rule "A rule"
      when
      p:Process( )
      then
      System.out.println(p.toString());
      end

      JIRA raised at the request of Mark Proctor:-

      From: rules-users-bounces@lists.jboss.org
      rules-users-bounces@lists.jboss.org On Behalf Of Mark Proctor
      Sent: 20 January 2007 13:50
      To: Rules Users List
      Subject: Re: [rules-users] Exception in thread "main" java.lang.Error:
      Unableto find unambiguously defined class

      Actually this is also a bug, if you declare something as an import, it
      should override the default java.lang.* imports - can you open a JIRA
      for this bug.

      Thanks

      Mark

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                tirelli Edson Tirelli
                Reporter:
                manstis1 manstis1 (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: