thebugslayer wrote: > Hi, > I understand this problem is more of Eclipse related, but it also > involves Maven setup, so I thought maybe one of users here would have > come across the same problem and give me some help. > > I have a webapp project setup in Eclipse Europa with Tomcat6.0, and I > am using m2eclipse plugin. In my part of my pom.xml I have the > following: > > <dependency> > <groupId>javax.servlet</groupId> > <artifactId>servlet-api</artifactId> > <version>2.5</version> > <scope>provided</scope> > </dependency> > <dependency> > <groupId>javax.servlet.jsp</groupId> > <artifactId>jsp-api</artifactId> > <version>2.1</version> > <scope>provided</scope> > </dependency> > > When I run it inside eclipse, the webapp startup fine, but when I hit > any jsp page I get the following: > > SEVERE: Servlet.service() for servlet jsp threw exception > org.apache.jasper.JasperException: Unable to compile class for JSP: > > An error occurred at line: 22 in the generated java file > The method getJspApplicationContext(ServletContext) is undefined for > the type JspFactory
Part of the issue may be that the 2.0 jsp-api is erroneously published under two different names in the central Maven2 repository: * javax.servlet.jsp:jsp-api * javax.servlet:jsp-api thus causing Maven to potentially put one of each name on the classpath. It would be necessary to add a dependency exclusion for the javax.servlet:jsp-api version to any dependencies which are transitively pulling it in. Max.
signature.asc
Description: OpenPGP digital signature
