problem deploying ear on jboss as7.1.2

[alginbel]

I'm using JBoss AS 7.1.2 (I migrate my application from from Jboss5 to Jboss AS7) , with JSF 1.2 version

I follow this Documentation:https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application+from+AS5+or+AS6+to+AS7

when I deploy a war  which is located within ear application

I get This Error Page:

note The full stack trace of the root cause is available in the JBoss Web/7.0.16.Final logs.

type Exception report

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: Servlet.init() for servlet faces threw exception

org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397)

org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)

org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)

org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)

org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679)

org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931)

java.lang.Thread.run(Thread.java:722)

root cause

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:725)

javax.faces.FactoryFinder.getFactory(FactoryFinder.java:239)

javax.faces.webapp.FacesServlet.init(FacesServlet.java:164)

org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397)

org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)

org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)

org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)

org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679)

org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931)

java.lang.Thread.run(Thread.java:722)

note The full stack trace of the root cause is available in the JBoss Web/7.0.16.Final logs.

Can Someone help me

Thank you

Kader

[nickarls]

do you have any faces or servlet api or implementations bundled in your war?

[alginbel]

Thank you Nicklas for your response, but I have no servlet api or impl in my war

[nickarls]

In what way have you configured the application to use JSF 1.2?

[alginbel]

In jboss-deployment-structure.xml file in the EAR META-INF/ directory

I have subdeployment

<sub-deployment name="workflows-base-web-1.7.9-SNAPSHOT.war">

        <exclusions>

                <module name="javax.faces.api" slot="main"/>

                <module name="com.sun.jsf-impl" slot="main"/>

        </exclusions>

        <dependencies>

            <module name="javax.faces.api" slot="1.2" export="true"/>

            <module name="com.sun.jsf-impl" slot="1.2" export="true"/>

            <module name="deployment.workflows.ear.activemq.rar" />

       </dependencies>

  </sub-deployment>

I have also put the jars in modules directory of jboss

[nickarls]

You could try bundling the JSF 1.2 JARs and use the WAR_BUNDLES_JSF_IMPL context parameter in web.xml

[alginbel]

Thanks Nicklas,

I use this declaration in context-param of web.xml

<param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>

<param-value>true</param-value>

[nickarls]

And you have the JSF libs included in the lib?

[alginbel]

the jsf libs are not included in the lib because they are in jboss-as-7.1.2 modules

jboss-as-7.1.2.Final/modules/javax/faces/api/1.2

and

jboss-as-7.1.2.Final/modules/com/sun/jsf-impl/1.2

is'nt like that, or I'm wrong?

[nickarls]

I think you need to bundle them physically when you use that context parameter. And take out the references to the JSF modules in the jboss-deployments-structure.

[alginbel]

ok, thank you Nicklas

I'll try

[alginbel]

Nicklas;

I just tried your suggestion

the error is gone, but another error appeared:

ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-3) Error listenerStart

[nickarls]

Full stack trace, please

[piotr.guziorski]

I was also migrating from JBoss 4.2.3 (EE5 compatible ear) to JBoss 7.1.1 (EE6 compatible ear).

My build script was adding application.xml to the ear which caused this exception to raise at deployment. When I removed application.xml from EarContent/META-INF error did not occur anymore.

I know it sounds weird but It helped. Check this out and let me know.

EDIT:

to be clear, my project facets: JSF 2.0 (impl. provided by server), JAX-RS, JAX-WS... executed on jdk1.7 anf jboss 7.1.1.Final (on Win7 x64)

What is also interesting: typical ant task for creating ear (EAR task) uses appxml as required param unless you add option update="true" and leave appxml=" " (space).

<ear destfile="..." basedir="..." manifest="..." update="true" appxml=" "></ear>

[wdfink]

Hello Piotr,

this is a bit less information,

you should create a new thread and attach the log, application.xml and if you can the EAR.