6 Replies Latest reply on Jun 20, 2013 10:45 AM by mashama

Does Richfaces 4.3.2 work with EAP 6.1(BETA|FINAL)?

mashama Jun 14, 2013 12:34 PM

I am trying to use the CDI push capability in Richfaces 4.3.2. I am encountering errors upon deployment:

12:23:27,608 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 168) Initializing Mojarra 2.1.19-jbossorg-1 20130304-0420 for context '/ValueQuestReportsRest'
12:23:27,983 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 168) Critical error during deployment: : com.sun.faces.config.ConfigurationException:
Source Document: vfs:/C:/Users/mmcfarlane/Downloads/jboss-eap-6.1.0.Beta/jboss-eap-6.1/standalone/deployments/valuequest-reports-rest.war/WEB-INF/lib/richfaces-core-impl-4.3.2.Final.jar/META-INF/faces-config.xml
Cause: Unable to create a new instance of 'org.richfaces.resource.ResourceHandlerImpl': java.lang.reflect.InvocationTargetException
          at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:293) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
          at com.sun.faces.config.processor.ApplicationConfigProcessor.setResourceHandler(ApplicationConfigProcessor.java:766) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
          at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:313) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
          at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
          at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
          at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
          at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:222) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
          at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:361) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
          at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:216) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
          at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
          at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
          at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Final-redhat-4.jar:7.2.0.Final-redhat-4]
          at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Final-redhat-4.jar:7.2.0.Final-redhat-4]
          at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Final-redhat-4.jar:7.2.0.Final-redhat-4]
          at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [rt.jar:1.6.0_29]
          at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [rt.jar:1.6.0_29]
          at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.6.0_29]
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_29]
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_29]
          at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_29]
          at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: java.lang.reflect.InvocationTargetException
          at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.6.0_29]
          at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) [rt.jar:1.6.0_29]
          at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) [rt.jar:1.6.0_29]
          at java.lang.reflect.Constructor.newInstance(Unknown Source) [rt.jar:1.6.0_29]
          at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:263) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1]
          ... 20 more
Caused by: org.jboss.modules.ModuleLoadError: org.apache.lucene:main
          at org.jboss.modules.ModuleLoadException.toError(ModuleLoadException.java:78) [jboss-modules.jar:1.2.0.CR1-redhat-1]
          at org.jboss.modules.Module.getPathsUnchecked(Module.java:1180) [jboss-modules.jar:1.2.0.CR1-redhat-1]
          at org.jboss.modules.Module.loadModuleClass(Module.java:513) [jboss-modules.jar:1.2.0.CR1-redhat-1]
          at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182) [jboss-modules.jar:1.2.0.CR1-redhat-1]
          at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.2.0.CR1-redhat-1]
          at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.2.0.CR1-redhat-1]
          at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) [jboss-modules.jar:1.2.0.CR1-redhat-1]
          at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.2.0.CR1-redhat-1]
          at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.2.0.CR1-redhat-1]
          at org.richfaces.resource.ResourceUtils.readMappings(ResourceUtils.java:100) [richfaces-core-impl-4.3.2.Final.jar:4.3.2.Final]
          at org.richfaces.resource.ResourceFactoryImpl.<init>(ResourceFactoryImpl.java:93) [richfaces-core-impl-4.3.2.Final.jar:4.3.2.Final]
          at org.richfaces.resource.ResourceHandlerImpl.<init>(ResourceHandlerImpl.java:63) [richfaces-core-impl-4.3.2.Final.jar:4.3.2.Final]
          ... 25 more

It looks like it is a dependency issue as EAP 6.1.Beta comes with org.apache.lucence:3.6.2 so I tried to explicitly resolve this dependency in the jboss-deployment-structure.xml file:

<jboss-deployment-structure>
          <deployment>
                    <dependencies>
                              <module name="org.freemarker" />
                              <module name="org.apache.commons.io" />

                              <module name="org.apache.lucene" slot="3.6.2"/>

                              <module name="javax.jcr" />
                              <module name="org.modeshape.jcr.api" services="import" />
                              <module name="org.modeshape" services="import" />

                    </dependencies>
          </deployment>
</jboss-deployment-structure>

Unfortunately it still looks like upon deployment EAP 6.1 is attempting to load the 'main' slot and not the '3.6.2' slot.

1. Re: Does Richfaces 4.3.2 work with EAP 6.1(BETA|FINAL)?

lfryc Jun 14, 2013 2:53 PM (in response to mashama)

Hey Mashama, do you bundle guava.jar in your WAR?

According to the sources, your app fails when RichFaces (bundled in the WAR?) tries to use (and load) Guava class
https://github.com/richfaces4/core/blob/4.3.2.20130513-Final/impl/src/main/java/org/richfaces/resource/ResourceUtils.java#L100

Do you run just your app on EAP 6 with a WAR with RichFaces and Guava inside?

Don't you remember any special setup?
Actions
2. Re: Does Richfaces 4.3.2 work with EAP 6.1(BETA|FINAL)?

mashama Jun 17, 2013 12:52 PM (in response to lfryc)

Thanks for the prompt response Lukas! Yes I am bundling RF with my application being packaged as a WAR. Because Guava is a maven dependency of RF I was also bundling Guava in the WAR deployment. I added the necessary exclusions to my POM, confirmed that Guava is no longer deployed with the application, and I am still getting the same exception on startup.

I was pretty hard for me to read the stacktrace and intuit the issue as being related to the Guava bundling even though I already saw a JIRA issue pertaining to the bundling of Guava. If this is not the issue why am I still getting the following ModuleLoadError?

Caused by: org.jboss.modules.ModuleLoadError: org.apache.lucene:main
Actions
3. Re: Does Richfaces 4.3.2 work with EAP 6.1(BETA|FINAL)?

lfryc Jun 18, 2013 2:01 AM (in response to mashama)

Hey Mashama, just to be clear - RichFaces doesn't require Lucene in any way. RichFaces require just Guava.

According to provided stacktrace, it seems Lucene is tried to be resolved when RichFaces uses Guava classes.

Are you really using unmodified EAP 6.1 Beta installation? Have you tried EAP 6.1 Final as well?
Actions
4. Re: Does Richfaces 4.3.2 work with EAP 6.1(BETA|FINAL)?

mashama Jun 18, 2013 11:51 AM (in response to lfryc)

Thanks for the clarification. Technically I have modified the EAP 6.1 Beta install by installing Modeshape 3.3 as a module. I need to migrate my app to EAP 6.1 Final so I will see if I can deploy a vanilla Richfaces application to it before I make any modifications to the install. Thanks for your help on this.
Actions
5. Re: Does Richfaces 4.3.2 work with EAP 6.1(BETA|FINAL)?

jaikiran Jun 18, 2013 12:17 PM (in response to mashama)

Mashama McFarlane wrote:

Thanks for the clarification. Technically I have modified the EAP 6.1 Beta install by installing Modeshape 3.3 as a module.
Maybe this https://community.jboss.org/message/819263#819263?
Actions
6. Re: Does Richfaces 4.3.2 work with EAP 6.1(BETA|FINAL)?

mashama Jun 20, 2013 10:45 AM (in response to jaikiran)

Thanks!!!! It was a ModeShape issue the whole time. It did not manifest itself until I added the Richfaces dependency though!
Actions

Go to original post