Hi Vishal, It was a while ago but I think the main problems were NullPointerExceptions on compilation errors. We also wanted to use Java 5 syntax. I recall seeing something from Michael or Mark suggesting Janino was not as good as Eclipse so maybe search the list as well.
cheers Steve On 1/29/07, Vishal Joshi <[EMAIL PROTECTED]> wrote:
Thanks Steve, What kind of problem have you seen (or you anticipate) with JANINO? cheers, Vishal Steven Williams-3 wrote: > > Hi Vishal, > > We found the JANINO compiler to be less than ideal (plus we wanted to use > Java 5 syntax which only JDT supports). > > I think WebSphere has gone to 6.1.0.5 just recently. > > cheers > Steve > > On 1/22/07, Vishal Joshi <[EMAIL PROTECTED]> wrote: >> >> >> Thanks Steve, >> I tried PARENT_LAST option, but that did not help. I will consider >> upgrading >> to 6.1.0.3. >> in the meanwhile i have the solution to this, by using JANINO instead of >> ECLIPSE. >> >> cheers, >> Vishal >> >> Steven Williams-3 wrote: >> > >> > Hi Vishal, >> > >> > We had similar problems which we resolved by upgrading to WebSphere >> > 6.1.0.3. >> > This version uses the same 3.2 jars as jboss rules. An alternative >> > solution >> > to this is to make sure that you are using the PARENT_LAST classloading >> > policy for your application and making sure the required jars are in >> your >> > ear (depending on how far along you are in development I would suggest >> > making this change anyway as it ensures the application jars are used >> in >> > preference to the server's). I'll put something up on the wiki for >> > troubleshooting with WebSphere. >> > >> > cheers >> > Steve >> > >> > On 1/19/07, Vishal Joshi <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> 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 >> >> >> > >> > >> > >> > -- >> > Steven Williams >> > >> > Supervising Consultant >> > >> > Object Consulting >> > Office: 8615 4500 Mob: 0439 898 668 Fax: 8615 4501 >> > [EMAIL PROTECTED] >> > www.objectconsulting.com.au >> > >> > consulting | development | training | support >> > our experience makes the difference >> > >> > _______________________________________________ >> > 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#a8483889 >> 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 >> > > > > -- > Steven Williams > > Supervising Consultant > > Object Consulting > Office: 8615 4500 Mob: 0439 898 668 Fax: 8615 4501 > [EMAIL PROTECTED] > www.objectconsulting.com.au > > consulting | development | training | support > our experience makes the difference > > _______________________________________________ > 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#a8685187 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
-- Steven Williams Supervising Consultant Object Consulting Office: 8615 4500 Mob: 0439 898 668 Fax: 8615 4501 [EMAIL PROTECTED] www.objectconsulting.com.au consulting | development | training | support our experience makes the difference
_______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
