Thanks Dmitriy. I'll try that again.
As for slow test startup, I try to design so that much of the interesting
logic can be tested in vanilla unit tests (not extending SeamTest) with
dependencies filled via JMock. Because you're right, waiting 15 seconds for
the test to start up slows things
I had the same problem and went by second way proposed ellenzhao (thank you :) )
Just add to /resources/META-INF file drools.default.packagebuilder.conf
with next contents:
drools.dialect.default = java
| drools.dialect.java =
org.drools.rule.builder.dialect.java.JavaDialectConfiguration
|
There are two solutions:
1.delete the Janino compiler in Seam lib and use Eclipse compiler. You can get
the Eclipse compiler after downloading the Drools 4.0 binary. In the
drools/lib, you see a core-.jar. That is Eclipse compiler. Drop it into
your Seam lib folder, edit your build.xml,
ellenzhao wrote : There are two solutions:
|
| 1.delete the Janino compiler in Seam lib and use Eclipse compiler. You can
get the Eclipse compiler after downloading the Drools 4.0 binary. In the
drools/lib, you see a core-.jar. That is Eclipse compiler. Drop it into
your Seam lib
Oh, and after doing the above, drools is now not working when I startup the app
for real - so obviously I've done something wrong. Here's what I see:
Caused by: java.lang.NoSuchMethodError:
org.drools.compiler.PackageBuilderConfiguration.setCompiler(I)V
| at
Update to latest CVS - setCompiler() is no longer called in RuleBase.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4068586#4068586
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4068586
Thanks Shane. It works fine from within JBoss, but when I run the unit test
here's what I see:
FAILED CONFIGURATION: @BeforeMethod begin
| org.drools.RuntimeDroolsException: Unable to load dialect
'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
| at