alex soto commented on JBRULES-2253:
Not sure what changed in 5.2.0.M1 but my rule file fails to compile with error:
[229,27]: [ERR 101] Line 229:27 no viable alternative at input 'FROM' in rule
This DRL rule is working fine with version 5.1.1. I can't even pass the unit tests
with this new version, so I can't run this test as of now.
ClassNotFound when ASM optimizer kicks in in MVEL consequence
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.0.1.FINAL
Reporter: Michael Neale
Assignee: Tihomir Surdilovic
Fix For: 5.2.0.M1
(ok if the subject is really confusing, perhaps this bug isn't for you).
In chasing down JBRULES-2234 I found this. Instructions (apologies for relying on Guvnor
To reproduce is not
easy, but here are some instructions:
* Run latest Guvnor (if you are able to, if not, then the rest is moot !).
* Import the attached repo (unzip it first).
* browse to KnowledgeBases/org/acme/insurance/pricing/
- press "build package"
* shut it down, restart (flushes caches etc...)
* browse to KnowledgeBases/org/acme/insurance/pricing/Test Scenarios
* open PolicyQuotePackageTest
* run it:
Now you should see an exception like this:
Caused by: java.lang.NoClassDefFoundError: org/acme/insurance/Policy
at ASMAccessorImpl_62408281250565694450.setValue(Unknown Source)
This is due to it loading a previously serialized version of the KB.
If it was to run off a freshly compiled one, its all fine. Also, if I
tell MVEL to NOT use ASM optimizer, it works fine (using reflection).
So clearly the stuff is available to the classpath in the right
places... its only to do with ASM in mvel post deserialization. (and
for that to happen, MVEL has to execute the compiled expression enough
to kick in the JIT).
MVELCompilationUnit in drools is worth examining too... still not sure where the problem
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira