Configuração Eclipse + JSF + JBoss

28 de junho de 2011 1 resposta

Ivan_Oliveira 28 de junho de 2011

Pessoal,

Boa tarde!

Estou iniciando no mundo Java e estou tentando criar uma aplicação do zero utilizando JSF + JBoss apartir do Eclipse. Sendo que quando crio uma aplicação Web e levanto o servidor, apresenta a mensagem abaixo:

16:51:19,953 INFO [Version] Hibernate Validator 4.1.0.Final
16:51:19,984 INFO [DefaultTraversableResolver] Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
16:51:20,062 INFO [ExternalSpecifications] MyFaces Bean Validation support enabled
16:51:20,078 WARNING [DefaultAnnotationProvider] AnnotationConfigurator does not found classes for annotations in /WEB-INF/classes/ . This could happen because maven jetty plugin is used (goal jetty:run). Try configure org.apache.myfaces.annotation.SCAN_PACKAGES init parameter or use jetty:run-exploded instead.
16:51:21,218 INFO [ApplicationImpl] Couldn’t discover the current project stage, using Production
16:51:21,218 INFO [FacesConfigurator] Serialization provider : class org.apache.myfaces.shared_impl.util.serial.DefaultSerialFactory
16:51:21,234 INFO [DefaultLifecycleProviderFactory] Using LifecycleProvider java.lang.String
16:51:21,328 INFO [AbstractFacesInitializer] ServletContext ‘D:\Utilitarios\jboss-6.0.0.Final\server\default\tmp\vfs\automount3eb9a0603f51ff6a\MyApp.war-1a9a00bc6b05a3a2’ initialized.
16:51:21,343 INFO [config] Initializing Mojarra 2.0.3 ( b05) for context ‘/MyApp’
16:51:22,515 INFO [config] Unsanitized stacktrace from failed start…: com.sun.faces.config.ConfigurationException:
Source Document: vfs:/D:/Utilitarios/jboss-6.0.0.Final/server/default/deployers/jsf.deployer/Mojarra-2.0/jsf-libs/jsf-impl-2.0.3-b05.jar/com/sun/faces/jsf-ri-runtime.xml
Cause: Unable to create a new instance of ‘com.sun.faces.application.resource.ResourceHandlerImpl’: java.lang.NullPointerException
at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:289) [:2.0.3-]
at com.sun.faces.config.processor.ApplicationConfigProcessor.setResourceHandler(ApplicationConfigProcessor.java:748) [:2.0.3-]
at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:306) [:2.0.3-]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110) [:2.0.3-]
at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:112) [:2.0.3-]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:110) [:2.0.3-]
at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:212) [:2.0.3-]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:332) [:2.0.3-]
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:220) [:2.0.3-]
at org.jboss.web.jsf.integration.config.JBossMojarraConfigureListener.contextInitialized(JBossMojarraConfigureListener.java:58) [:1.0.3]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3369) [:6.0.0.Final]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3828) [:6.0.0.Final]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:294) [:6.0.0.Final]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) [:6.0.0.Final]
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:477) [:6.0.0.Final]
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [:6.0.0.Final]
at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.0.Final]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) [:1.6.0_26]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [:1.6.0_26]
at java.lang.reflect.Method.invoke(Unknown Source) [:1.6.0_26]

Alguém poderia me dar uma luz do que está faltando configurar ?

Desde já agradeço a todos.

1 Resposta

tiagoz 15 de jun. de 2012

Só para engrossar o coro do Ivan sobre o problema reportado, estou passando pela mesma situação!
Estou usando um JBoss 6.1, JSF 2.0.2 e tenho esse mesmo erro quando tento rodar a aplicação, apesar de ter a lib do JSF e do JSFT adicionadas aos projeto e de ter o JSF com a configuração padrão do Eclpse criada bem como o web.xml auto gerado também configurado para o JSF.
O erro sugere que eu tenha algum problema com a configuração da minha aplicação quanto ao JSF, mas como é minha primeira aplicação não tenho como entender onde seria.
Eu acredito que eu estava com algum problema de conflito das versões do JSF e as suportadas no meu Eclise Indigo.
Vou postar alguns códigos abaixo para ver se ajudar a esclarecer:
faces-config.xml

&lt;?xml version="1.0" encoding="UTF-8"?&gt;

&lt;faces-config
    xmlns="http://java.sun.com/xml/ns/javaee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd"
    version="2.0"&gt;

&lt;/faces-config&gt;

web.xml

<?xml version="1.0" encoding="UTF-8"?> <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" version="3.0"> <display-name>FirstPrimefacesJSFProject</display-name> <servlet> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>/faces/*</url-pattern> </servlet-mapping> <context-param> <param-name>javax.servlet.jsp.jstl.fmt.localizationContext</param-name> <param-value>resources.application</param-value> </context-param> <context-param> <description>State saving method: 'client' or 'server' (=default). See JSF Specification 2.5.2</description> <param-name>javax.faces.STATE_SAVING_METHOD</param-name> <param-value>client</param-value> </context-param> <context-param> <description> This parameter tells MyFaces if javascript code should be allowed in the rendered HTML output. If javascript is allowed, command_link anchors will have javascript code that submits the corresponding form. If javascript is not allowed, the state saving info and nested parameters will be added as url parameters. Default is 'true'</description> <param-name>org.apache.myfaces.ALLOW_JAVASCRIPT</param-name> <param-value>true</param-value> </context-param> <context-param> <description> If true, rendered HTML code will be formatted, so that it is 'human-readable' i.e. additional line separators and whitespace will be written, that do not influence the HTML code. Default is 'true'</description> <param-name>org.apache.myfaces.PRETTY_HTML</param-name> <param-value>true</param-value> </context-param> <context-param> <param-name>org.apache.myfaces.DETECT_JAVASCRIPT</param-name> <param-value>false</param-value> </context-param> <context-param> <description> If true, a javascript function will be rendered that is able to restore the former vertical scroll on every request. Convenient feature if you have pages with long lists and you do not want the browser page to always jump to the top if you trigger a link or button action that stays on the same page. Default is 'false' </description> <param-name>org.apache.myfaces.AUTO_SCROLL</param-name> <param-value>true</param-value> </context-param> <listener> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class> </listener> </web-app>

A imagem dos includes do meu classpath segue em enexo.

Criado 28 de junho de 2011

Ultima resposta 15 de jun. de 2012

Respostas 1

Participantes 2

1 Resposta

Topicos relacionados