This is resolved now. For benefit of others, i added the system variable in websphere console drools.compiler=JANINO This at runtime uses janino compiler api instead of using eclipse compiler, which seems to have conflict with the websphere app server's internal eclipse API.
Vishal Joshi wrote: > > or alternatively can we configure jboss rules to use janino compiler > instead of eclipse compiler? > > > Vishal Joshi wrote: >> >> Just to re-iterate >> commons-jci-core-1.0-406301.jar has this class CompilationResult (with >> different packaging) which does NOT have getProblems() method. >> But I have another jar core-3.2.0.666.jar in my application, which has >> org.eclipse.jdt.internal.compiler.CompilationResult class with >> getProblems() method as expected. >> so this class with the required method is definitely there in the >> classpath. >> >> is there any other jar that is missing? or anything else? >> >> >> Vishal Joshi wrote: >>> >>> It is working fine with websphere 6.0.2.3 and the same application's >>> rule engine module does not work with websphere 6.1. >>> >>> My application has all these JCI jars bundled: >>> commons-jci-core-1.0-406301.jar >>> commons-jci-eclipse-3.2.0.666.jar >>> commons-jci-janino-2.4.3.jar >>> >>> anything that is missing? >>> >>> >>> >>> Mark Proctor wrote: >>>> >>>> Have you included all the JCI jars and the correct versions? >>>> >>>> Mark >>>> Vishal Joshi wrote: >>>>> posting it again after successfule subscription. >>>>> I have deployed my application on websphere 6.1, which contains Rule >>>>> engine >>>>> as one of the module using JBoss Rule 3.0.1. When i am trying to >>>>> invoke >>>>> drools api from my class >>>>> ==================================== >>>>> final PackageBuilder builder = new PackageBuilder(); >>>>> builder.addPackageFromDrl(new StringReader(drl)); >>>>> ==================================== >>>>> >>>>> it throws this exception: >>>>> >>>>> java.lang.NoSuchMethodError: >>>>> org/eclipse/jdt/internal/compiler/CompilationResult >>>>> .getProblems()[Lorg/eclipse/jdt/core/compiler/CategorizedProblem; >>>>> at >>>>> org.apache.commons.jci.compilers.EclipseJavaCompiler$2.acceptResult(E >>>>> clipseJavaCompiler.java:237) >>>>> at >>>>> org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:335) >>>>> >>>>> at >>>>> org.apache.commons.jci.compilers.EclipseJavaCompiler.compile(EclipseJ >>>>> avaCompiler.java:268) >>>>> at org.drools.compiler.PackageBuilder.compile(Unknown Source) >>>>> at org.drools.compiler.PackageBuilder.compileRule(Unknown >>>>> Source) >>>>> at org.drools.compiler.PackageBuilder.addRule(Unknown Source) >>>>> at org.drools.compiler.PackageBuilder.addPackage(Unknown >>>>> Source) >>>>> at >>>>> org.drools.compiler.PackageBuilder.addPackageFromDrl(Unknown >>>>> Source) >>>>> >>>>> >>>>> I have checked that class >>>>> org.eclipse.jdt.internal.compiler.CompilationResult is available with >>>>> my >>>>> application war in core-3.2.0.666.jar (which is part of drools >>>>> distributable) and it has getProblems() method also. >>>>> >>>>> any help will be greatly appreciated. >>>>> >>>> >>>> _______________________________________________ >>>> rules-users mailing list >>>> [email protected] >>>> https://lists.jboss.org/mailman/listinfo/rules-users >>>> >>>> >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/class-loading-issue-with-websphere-6.1-tf3027390.html#a8430930 Sent from the drools - user mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
