JSF2 + SeamFaces

[Paulo Bianchin]

Hi

I have a problem with SeamFaces

When I add it in my project, it gives the following error:

java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory
	javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:957)
	javax.faces.FactoryFinder.getFactory(FactoryFinder.java:316)
	javax.faces.webapp.FacesServlet.init(FacesServlet.java:302)
	org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139)

- I've tried to put the jsf-api.jar in the project
- It added Faces Servlet in web.xml
- I tried to put other versions


I am using JBOSS 7


My pom.xml is something like
<properties> <jboss.home>${env.JBOSS_HOME}</jboss.home> <jboss.domain>default</jboss.domain> <arquillian.version>1.0.0.Alpha5</arquillian.version> <jboss-javaee6-spec.version>1.0.0.Final</jboss-javaee6-spec.version> <seam.version>3.0.0.Final</seam.version> </properties> <dependencies> <!-- Annotation processor to generate the JPA 2.0 metamodel classes for typesafe criteria queries --> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-jpamodelgen</artifactId> <version>1.1.1.Final</version> <scope>provided</scope> <!-- Excluded because it's provided by the Java EE 6 dependencies --> <exclusions> <exclusion> <groupId>org.hibernate.javax.persistence</groupId> <artifactId>hibernate-jpa-2.0-api</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-validator</artifactId> <version>4.1.0.Final</version> <scope>provided</scope> <exclusions> <exclusion> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.jboss.arquillian</groupId> <artifactId>arquillian-junit</artifactId> <version>${arquillian.version}</version> <scope>test</scope> </dependency> <dependency> <groupId>org.primefaces</groupId> <artifactId>primefaces</artifactId> <version>3.0</version> </dependency> <dependency> <groupId>org.jboss.seam.solder</groupId> <artifactId>seam-solder</artifactId> <version>${seam.version}</version> </dependency> <dependency> <groupId>org.jboss.seam.security</groupId> <artifactId>seam-security-api</artifactId> <version>${seam.version}</version> </dependency> <dependency> <groupId>org.jboss.seam.security</groupId> <artifactId>seam-security-impl</artifactId> <version>${seam.version}</version> <scope>runtime</scope> </dependency> </dependencies>


I have no idea what is happening

Can anyone give me a hint?

Tanks

[Paulo Bianchin]

with

<dependency> <groupId>org.jboss.seam.faces</groupId> <artifactId>seam-faces</artifactId> <version>3.0.2.Final</version> </dependency> <dependency> <groupId>com.ocpsoft</groupId> <artifactId>prettyfaces-jsf2</artifactId> <version>3.2.0</version> </dependency>


shows

12:33:28,325 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (http--0.0.0.0-8888-1) Exception sending request initialized lifecycle event to listener instance of class com.ocpsoft.pretty.faces.config.PrettyConfigListener: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory
	at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:957) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
	at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:316) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1]
	at com.ocpsoft.pretty.faces.util.FacesFactory.getApplication(FacesFactory.java:30) [prettyfaces-jsf2-3.2.0.jar:]
	at com.ocpsoft.pretty.faces.config.PrettyConfigListener.requestInitialized(PrettyConfigListener.java:34) [prettyfaces-jsf2-3.2.0.jar:]

[Bharathula Venkata]

Its a wrong dependency which conflicted jar files. Try removing the culprit version of the jar file, which you included through pom.xml, and try again. Faced similar stuff some time ago. purely compatibility issue. the server support is also seems to be not there.