[jboss-jira] [JBoss JIRA] Created: (JBRULES-2010) multibyte characters in drl fails with "no viable alternative at character"

Yusuke Yamamoto (JIRA) jira-events at lists.jboss.org
Tue Mar 17 08:07:22 EDT 2009


multibyte characters in drl fails with "no viable alternative at character"
---------------------------------------------------------------------------

                 Key: JBRULES-2010
                 URL: https://jira.jboss.org/jira/browse/JBRULES-2010
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-compiler
    Affects Versions: 5.0.0.M5,  5.0.0.M4, 5.0.0.M3,  5.0.0.M2, 5.0.0.M1, 4.0.7
            Reporter: Yusuke Yamamoto
            Assignee: Mark Proctor


When multi-byte characters are used for rule name, field name, or function name, compiler reports "no viable alternative at character".

Additionally, multi-byte characters are normalized into "_" and compiler fails to differenciate names when their length are same.
------
org.drools.rule.InvalidRulePackage: Rule Compilation error : [Rule name=日本語ルール2, agendaGroup=MAIN, salience=0, no-loop=false]
	org/drools/compiler/Rule_________0.java (3:43) : The type Rule_________0 is already defined

	at org.drools.rule.Package.checkValidity(Package.java:424)
	at org.drools.common.AbstractRuleBase.addPackage(AbstractRuleBase.java:394)
	at org.drools.compiler.MultibyteDRLTest.executeTestFor(MultibyteDRLTest.java:90)
	at org.drools.compiler.MultibyteDRLTest.testmultibyteRuleName2(MultibyteDRLTest.java:78)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40)
-------
This issue is reproducible both on Drools 4.0.7 and 5.0.0.

Drools Version: 5.0.0.CR1 , 4.0.7

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

       




More information about the jboss-jira mailing list