I am working on JSP/Servlets. The web app is to be deployed on Jboss 6.
I am using Java 1.6, Eclipse and Maven2. I do not refer to JSF anywhere in my code.
My pr
URL file:/home/jamshed/jboss-6.0.0.Final/server/default/tmp/vfs/automount32136eeb452eb1b9/UltimateSMS-1.war-9f7ce8e7ceadff1/
I believe this would the path to the working space for building the war file. Perhaps it is possible to take a look in there and see if you are able to find the WAR itself that it is attempting to deploy?
What I am getting at is, see if you can build or obtain your war file and try to manually deploy it to JBoss. If it doesn't work then there is something missing on your classpath for JBoss, if it does then there is something missing in Maven or your pom.
I've experienced the same problem. To resolve it I've replace in pom.xml
:
<dependency>
<groupId>javax</groupId>
<artifactId>javaee-api</artifactId>
<version>6.0</version>
<type>jar</type>
<scope>compile</scope>
</dependency>
by :
<dependency>
<groupId>javax</groupId>
<artifactId>javaee-api</artifactId>
<version>6.0</version>
<scope>provided</scope>
</dependency>
According to maven doc you should set the dependency on the Servlet API and related Java EE APIs to scope provided
because the web container provides those classes.
provided
is much like compile
, but indicates you expect the JDK or a container to provide the dependency at runtime. For example, when building a web application for the Java Enterprise Edition, you would set the dependency on the Servlet API and related Java EE APIs to scope provided because the web container provides those classes. This scope is only available on the compilation and test classpath, and is not transitive.