File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes JSF and the fly likes Cannot deploy my JSF 1.2 application in JBoss AS 7 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » JSF
Bookmark "Cannot deploy my JSF 1.2 application in JBoss AS 7" Watch "Cannot deploy my JSF 1.2 application in JBoss AS 7" New topic
Author

Cannot deploy my JSF 1.2 application in JBoss AS 7

Anish Antony
Greenhorn

Joined: Sep 30, 2013
Posts: 1
hen i deploy my JSF 1.2 war on deployment directory of JBoss AS7 server i got following exception and warnings

12:57:12,530 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
12:57:12,531 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
12:57:12,532 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
12:57:12,532 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
12:57:12,533 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'
12:57:12,534 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'
12:57:12,535 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeFromStringEnum' for service type 'com.sun.jersey.spi.StringReaderProvider'
12:57:12,536 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeValueOf' for service type 'com.sun.jersey.spi.StringReaderProvider'
12:57:12,537 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeFromString' for service type 'com.sun.jersey.spi.StringReaderProvider'
12:57:12,538 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$StringConstructor' for service type 'com.sun.jersey.spi.StringReaderProvider'
12:57:12,539 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$DateProvider' for service type 'com.sun.jersey.spi.StringReaderProvider'
12:57:12,540 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.JAXBStringReaderProviders$RootElementProvider' for service type 'com.sun.jersey.spi.StringReaderProvider'
12:57:13,798 ERROR [org.jboss.web] (MSC service thread 1-5) JBAS018211: Could not load JSF managed bean class: com.myimpl.view.bean.AgObjectBean
12:57:13,949 ERROR [org.jboss.web] (MSC service thread 1-5) JBAS018211: Could not load JSF managed bean class: com.myimpl.view.bean.EventCoGroupsBean
12:57:14,053 ERROR [org.jboss.web] (MSC service thread 1-5) JBAS018211: Could not load JSF managed bean class: com.myimpl.view.bean.JMXInfoBean
12:57:14,055 ERROR [org.jboss.web] (MSC service thread 1-5) JBAS018211: Could not load JSF managed bean class: com.myimpl.reports.view.bean.TrendBean
12:57:14,056 ERROR [org.jboss.web] (MSC service thread 1-5) JBAS018211: Could not load JSF managed bean class: com.myimpl.view.bean.SnmpInfoBean
12:57:14,072 ERROR [org.jboss.web] (MSC service thread 1-5) JBAS018211: Could not load JSF managed bean class: com.myimpl.view.bean.LinuxInfoBean
12:57:14,534 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."myimpl.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."myimpl.war".POST_MODULE: Failed to process phase POST_MODULE of deployment "myimpl.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_37]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_37]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_37]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011232: Only one JAX-RS Application Class allowed. com.sun.jersey.api.core.WebAppResourceConfig com.sun.jersey.api.core.DefaultResourceConfig com.sun.jersey.api.core.ScanningResourceConfig com.sun.jersey.api.core.ClasspathResourceConfig com.sun.jersey.api.core.ApplicationAdapter com.sun.jersey.api.core.ClassNamesResourceConfig com.sun.jersey.api.core.ResourceConfig com.sun.jersey.api.core.PackagesResourceConfig com.sun.jersey.server.impl.application.DeferredResourceConfig
at org.jboss.as.jaxrs.deployment.JaxrsScanningProcessor.scan(JaxrsScanningProcessor.java:209)
at org.jboss.as.jaxrs.deployment.JaxrsScanningProcessor.deploy(JaxrsScanningProcessor.java:105)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more


12:57:14,544 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015951: Admin console listening on http://127.0.0.1:9990
12:57:14,545 ERROR [org.jboss.as] (MSC service thread 1-2) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 121295ms - Started 1422 of 1572 services (3 services failed or missing dependencies, 138 services are passive or on-demand)
12:57:14,551 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "myimpl.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"myimpl.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"myimpl.war\".POST_MODULE: Failed to process phase POST_MODULE of deployment \"myimpl.war\""}}
12:57:14,552 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "WfAPI.jar" was rolled back with no failure message
12:57:14,580 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment WfAPI.jar in 27ms
12:57:14,651 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment myimpl.war in 99ms

But it working fine on JBoss 6.
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 15641
    
  15

Since about JBoss 4, JSF has been an integral part of the JBoss server itself (per the JEE standards). In fact, one of the salient differences between JEE and J2EE is that J2EE only supports JSF using add-on modules that must be included in the WAR.

The version of JSF in JBoss, however, is not JSF1, it's JSF2. So you are getting conflicts.

There are basically 2 ways to remedy this.

1. Upgrade the app to JSF2. Which isn't that hard, usually.

2. Continue to use JSF 1.2, but add appropriate instructions to JBoss in your web.xml file telling it to not include its internal JSF JARs in the application classpath. These instructions are listed as part of the JBoss/Wildfly documentation. For more specifics you might want to inquire in the JBoss Forum.


Customer surveys are for companies who didn't pay proper attention to begin with.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Cannot deploy my JSF 1.2 application in JBoss AS 7
 
Similar Threads
Issue while deploying Application in Jboss 7.1
Web Service Deployment Failed
unable to run jsf richfaces fileupload example from "exadel.com"
Activiti Issues
How to deploy open cms on jboss as 7