November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16096) JSF Code completion does not support http://xmlns.jcp.org/jsf/* namespaces

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16096?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16096: ---------------------------------------- Fix Version/s: 4.1.1.CR1 (was: 4.2.0.Alpha1) > JSF Code completion does not support http://xmlns.jcp.org/jsf/* namespaces > -------------------------------------------------------------------------- > > Key: JBIDE-16096 > URL: https://issues.jboss.org/browse/JBIDE-16096 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Labels: respin-a > Fix For: 4.1.1.CR1 > > > 1. Create a JSF 2.2 project. > 2. Create an xhtml file with using new jsf namespaces: > {code} > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core"> > </html> > {code} > 3. Try Ctrl+Space for <h: and <f: tags. > 4. FAILURE: There is no CA for h: and f: tags. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16093) NPEs when compiling wildfly codebase

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16093: ------------------------------------------ Could avoid the errors by disabling the validation in the preferences (see workaround) > NPEs when compiling wildfly codebase > ------------------------------------ > > Key: JBIDE-16093 > URL: https://issues.jboss.org/browse/JBIDE-16093 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Snjezana Peco > Attachments: .log, npes-building-wildfly-2.png, npes-building-wildfly.png > > > When having arquillian org.jboss.tools.arquillian.core_1.0.5.CR1-v20131116-1823-B79 installed and building the wildfly workspace I run into several NPEs caused by arquillian. > !npes-building-wildfly.png! > !npes-building-wildfly-2.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15982) jst/jsf New and Noteworthy for 4.1.1.CR1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15982?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15982: --------------------------------------------- pr's applied. > jst/jsf New and Noteworthy for 4.1.1.CR1 > ---------------------------------------- > > Key: JBIDE-15982 > URL: https://issues.jboss.org/browse/JBIDE-15982 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html source editing > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.1.CR1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If jst/jsf is not listed here check if there are issues that should be added and add them. > Document the ones relevant for jst/jsf by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15997) Forge New and Noteworthy for 4.1.1.CR1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15997?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15997: --------------------------------------------- pr's applied. > Forge New and Noteworthy for 4.1.1.CR1 > -------------------------------------- > > Key: JBIDE-15997 > URL: https://issues.jboss.org/browse/JBIDE-15997 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.1.CR1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Forge is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16096) JSF Code completion does not support http://xmlns.jcp.org/jsf/* namespaces

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16096?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16096: ----------------------------------- Priority: Critical (was: Major) > JSF Code completion does not support http://xmlns.jcp.org/jsf/* namespaces > -------------------------------------------------------------------------- > > Key: JBIDE-16096 > URL: https://issues.jboss.org/browse/JBIDE-16096 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.2.0.Alpha1 > > > 1. Create a JSF 2.2 project. > 2. Create an xhtml file with using new jsf namespaces: > {code} > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core"> > </html> > {code} > 3. Try Ctrl+Space for <h: and <f: tags. > 4. FAILURE: There is no CA for h: and f: tags. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16096) JSF Code completion does not support http://xmlns.jcp.org/jsf/* namespaces

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-16096: -------------------------------------- Summary: JSF Code completion does not support http://xmlns.jcp.org/jsf/* namespaces Key: JBIDE-16096 URL: https://issues.jboss.org/browse/JBIDE-16096 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsf, jsp/jsf/xml/html source editing Affects Versions: 4.2.0.Alpha1 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.2.0.Alpha1 1. Create a JSF 2.2 project. 2. Create an xhtml file with using new jsf namespaces: {code} <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://xmlns.jcp.org/jsf/facelets" xmlns:h="http://xmlns.jcp.org/jsf/html" xmlns:f="http://xmlns.jcp.org/jsf/core"> </html> {code} 3. Try Ctrl+Space for <h: and <f: tags. 4. FAILURE: There is no CA for h: and f: tags. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16093) NPEs when compiling wildfly codebase

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16093: ------------------------------------- Workaround Description: Turn off Arquillian validation in the preferences: Preferences->Arquillian Validation->[ ] Enable Validation (uncheck) > NPEs when compiling wildfly codebase > ------------------------------------ > > Key: JBIDE-16093 > URL: https://issues.jboss.org/browse/JBIDE-16093 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Snjezana Peco > Attachments: .log, npes-building-wildfly-2.png, npes-building-wildfly.png > > > When having arquillian org.jboss.tools.arquillian.core_1.0.5.CR1-v20131116-1823-B79 installed and building the wildfly workspace I run into several NPEs caused by arquillian. > !npes-building-wildfly.png! > !npes-building-wildfly-2.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16095) seam 2.3 seem to need guava in jboss-deployment descriptor

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16095?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-16095. ----------------------------------------- Resolution: Rejected [~snjeza] found this seem to only occur in Seam 2.3.1, Seam 2.3.2 have it fixed thus rejecting. > seam 2.3 seem to need guava in jboss-deployment descriptor > ---------------------------------------------------------- > > Key: JBIDE-16095 > URL: https://issues.jboss.org/browse/JBIDE-16095 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.1.CR1, 4.1.1.Final > > > from [~snjeza]: > I have tried to run a seam 2.3 project on EAP 6.1 using the Seam Web project wizard. > It fails with the following exception: > Source Document: vfs:/C:/jbdev-710cr1/runtimes/jboss-eap/standalone/deployments/seam23.war/WEB-INF/lib/richfaces-core-impl.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.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_45] > at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_45] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] > 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.7.0_45] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_45] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_45] > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_45] > at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:263) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > ... 19 more > Caused by: java.lang.NoClassDefFoundError: com/google/common/base/Function > at org.richfaces.resource.ResourceHandlerImpl.<init>(ResourceHandlerImpl.java:63) [richfaces-core-impl.jar:4.3.3.Final] > ... 24 more > Caused by: java.lang.ClassNotFoundException: com.google.common.base.Function from [Module "deployment.seam23.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.2.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.2.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.2.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.2.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.2.Final-redhat-1] > ... 25 more > Adding the line > <module name="com.google.guava" export="true"/> > in the jboss-deployment-structure.xml file fixes the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16022) Seam Portlet deployment error on JPP 6

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16022?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-16022. ----------------------------------------- Resolution: Rejected Seam 2.2 is not supported on EAP 6 - should be using Seam 2.3 (preferably from WFK) > Seam Portlet deployment error on JPP 6 > -------------------------------------- > > Key: JBIDE-16022 > URL: https://issues.jboss.org/browse/JBIDE-16022 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein, seam2 > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1-v20131116-1929-B543, JPP 6.1 (also JPP 6.0) and Seam 2.2.2 > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Priority: Blocker > Labels: respin-a > Fix For: 4.1.1.CR1 > > Attachments: jpp-seam-server.log > > > Deployment of Seam Portal Project with Seam Portlet ends with error on JPP 6. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16095) seam 2.3 seem to need guava in jboss-deployment descriptor

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-16095: ------------------------------------------- Summary: seam 2.3 seem to need guava in jboss-deployment descriptor Key: JBIDE-16095 URL: https://issues.jboss.org/browse/JBIDE-16095 Project: Tools (JBoss Tools) Issue Type: Bug Components: seam2 Reporter: Max Rydahl Andersen Priority: Blocker Fix For: 4.1.1.CR1, 4.1.1.Final from [~snjeza]: I have tried to run a seam 2.3 project on EAP 6.1 using the Seam Web project wizard. It fails with the following exception: Source Document: vfs:/C:/jbdev-710cr1/runtimes/jboss-eap/standalone/deployments/seam23.war/WEB-INF/lib/richfaces-core-impl.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.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_45] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] 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.7.0_45] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_45] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_45] at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_45] at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:263) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] ... 19 more Caused by: java.lang.NoClassDefFoundError: com/google/common/base/Function at org.richfaces.resource.ResourceHandlerImpl.<init>(ResourceHandlerImpl.java:63) [richfaces-core-impl.jar:4.3.3.Final] ... 24 more Caused by: java.lang.ClassNotFoundException: com.google.common.base.Function from [Module "deployment.seam23.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.2.Final-redhat-1] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.2.Final-redhat-1] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.2.Final-redhat-1] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.2.Final-redhat-1] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.2.Final-redhat-1] ... 25 more Adding the line <module name="com.google.guava" export="true"/> in the jboss-deployment-structure.xml file fixes the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2013