Eclipse-JDT compiler jar (core-3.2.0.666.jar) for drools creates problems/conflicts with the existing one (jasper-compiler-jdt.jar - used by tomcat for JSP compilation) ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: JBRULES-1122 URL: http://jira.jboss.com/jira/browse/JBRULES-1122 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.GA, 3.0.6 Environment: Windows XP / JDK 1.5.0_06-b05 Reporter: Suman Ghosh Assigned To: Mark Proctor I'm running a service using JBoss, which uses Drools for its various rule-based components. The propblem arises like this - when I use the JDTcompiler in Drools, tomcat crashes with the following stacktrace (when used to access JSPs - such as the JBoss JMX console).... ----------------------------------------------------START------------------------------------------------------------------- type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception javax.servlet.ServletException: org.eclipse.jdt.internal.compiler.CompilationResult.getProblems()[Lorg/eclipse/jdt/core/compiler/IProblem; org.apache.jasper.servlet.JspServlet.service(JspServlet.java:272) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) root cause java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.CompilationResult.getProblems()[Lorg/eclipse/jdt/core/compiler/IProblem; org.apache.jasper.compiler.JDTCompiler$2.acceptResult(JDTCompiler.java:345) org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:417) org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:404) org.apache.jasper.compiler.Compiler.compile(Compiler.java:297) org.apache.jasper.compiler.Compiler.compile(Compiler.java:276) org.apache.jasper.compiler.Compiler.compile(Compiler.java:264) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:303) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) note The full stack trace of the root cause is available in the Apache Tomcat/5.5.17 logs. ---------------------------------------------------END-------------------------------------------------------------------- Seems that the class CompilationResult from the new JDT distribution has a different signature for the getProblems() method - but tomcat expects the earlier one only. For my application, I *have* to use the JDT compiler for my rule base, and on the other hand, I require the jboss jmx-console, for service monitoring and method invokations :( Please suggest a solution! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira