Bug#437136: tomcat5 (5.0.30) is not compatible with system installed ant 1.6.5
On 8/10/07, Cedric Veilleux [EMAIL PROTECTED] wrote: [...] On two different Etch installs, I had the following problem occuring when accessing JSP files that needed to be compiled: [...] What is: com.angkor.struts.filter.AngkorVersionAndLanguageFilter.doFilter(AngkorVersionAndLanguageFilter.java:109) [...] This looks like a bug in either Ant or Tomcat. I would suspect Ant, since the problem is that a NULL key is inserted into a Map inside the ant code base, which should be checked for. Does this error occured when disabling the Angkor Struts Filter? Cheers, -- Arnaud Vandyck ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#437136: tomcat5 (5.0.30) is not compatible with system installed ant 1.6.5
Package: tomcat5 Version: 5.0.30-12 Apache ships tomcat 5.0.30 with ant 1.6.2, while Debian Etch has ant 1.6.5 installed system wide. On two different Etch installs, I had the following problem occuring when accessing JSP files that needed to be compiled: org.apache.jasper.JasperException: Unable to compile class for JSP org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:520) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) com.angkor.struts.filter.AngkorVersionAndLanguageFilter.doFilter(AngkorVersionAndLanguageFilter.java:109) root cause java.lang.NullPointerException java.util.Hashtable.put(Hashtable.java:394) org.apache.tools.ant.PropertyHelper.setProperty(PropertyHelper.java:335) org.apache.tools.ant.Project.setPropertyInternal(Project.java:460) org.apache.tools.ant.Project.setSystemProperties(Project.java:800) org.apache.tools.ant.Project.init(Project.java:261) org.apache.jasper.compiler.Compiler.getProject(Compiler.java:116) org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:321) org.apache.jasper.compiler.Compiler.compile(Compiler.java:498) org.apache.jasper.compiler.Compiler.compile(Compiler.java:477) org.apache.jasper.compiler.Compiler.compile(Compiler.java:465) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) com.angkor.struts.filter.AngkorVersionAndLanguageFilter.doFilter(AngkorVersionAndLanguageFilter.java:109) A restart of tomcat would normally fix the problem, but then other pages would start having this seemingly random problem. Downgrading to ant 1.6.2 from oldstable fixed the problem completely. This looks like a bug in either Ant or Tomcat. I would suspect Ant, since the problem is that a NULL key is inserted into a Map inside the ant code base, which should be checked for. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
