Corneil du Plessis wrote:
Problem I have is that it is in WebSphere/lib so it gets loaded
before
anything in my application, when the classloader is set to parent first.
When I change the class loader to parent last I run into a new set of
problem with some of the XML based libraries.
If you search the mailing list archive, I believe people have resolved
that issue. You can always switch drools to use janino too, see the wiki
for more details on that.
-----Original Message-----
From: rules-users-bounces(a)lists.jboss.org
[mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Marcus Ilgner
Sent: 03 June 2008 15:35
To: Rules Users List
Subject: Re: [rules-users] eclipse-jdtcore.jar
Hi,
just as a side note: I had one project using Eclipse which already used
another version of the JDT core. Encountering the same problem, I just put
the core-3.2.3.v_686_R32x.jar from Drools in my project, too, and it worked
without problems.
Best regards
Marcus
On Tue, Jun 3, 2008 at 3:25 PM, Augusto Rodriguez
<augusto.rodriguez(a)globant.com> wrote:
> Hi Corneil,
>
> Unluckily I've seen that error more often that I would like. It's not
> a bug in drools, but is related to the dependencies of the
>
drools-compiler.
> There's a big chance that you have a different version of the JDT core
> jar in your classpath (drools depends on version 3.2.3 - the filename
> of that jar is core-3.2.3.v_686_R32x.jar). This jar is used by drools
> to compile the rules.
>
> I hope this helps you to solve this issue.
>
>
> Cheers,
> Augusto
>
> Corneil du Plessis wrote:
>
>> I am experiencing a conflict with a deployment:
>>
>> We used WebSphere Application Server 6.0.2.x in our integration
>> testing environment and now the deployed application at a customer
>> site is reporting the following exception:
>>
>>
>> java.lang.NoSuchMethodError:
>> org.eclipse.jdt.internal.compiler.CompilationResult: method
>> getProblems()[Lorg/eclipse/jdt/core/compiler/CategorizedProblem; not
>>
found
>> at
>>
>> org.drools.commons.jci.compilers.EclipseJavaCompiler$3.acceptResult(E
>> clipseJ
>> avaCompiler.java(Compiled Code))
>> at
>>
>>
>>
org.eclipse.jdt.internal.compiler.Compiler.handleInternalException(Compiler.
>> java(Compiled Code))
>> at
>> org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java(Comp
>> iled
>> Code))
>> at
>>
>> org.drools.commons.jci.compilers.EclipseJavaCompiler.compile(EclipseJ
>> avaComp
>> iler.java(Compiled Code))
>> at
>>
>> org.drools.commons.jci.compilers.AbstractJavaCompiler.compile(Abstrac
>> tJavaCo
>> mpiler.java:51)
>> at
>>
>> org.drools.rule.builder.dialect.java.JavaDialect.compileAll(JavaDiale
>> ct.java
>> :342)
>>
>> Has anyone else comes across this?
>>
>> I am not sure where the JAR comes from because has not version info.
>>
>> _______________________________________________
>> rules-users mailing list
>> rules-users(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/rules-users
>>
>>
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-users
>
>
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users