Na configuração do servidor wildFly com a aplicação esta informando um erro:
No navegador mostra a pagina inicial do wildFly, mas na hora de compilar o projeto ele da outro erro, não consegue encontrar a pagina form.jsf, da o erro 404 page not found.
Tem alguma configuração q eu posso ta fazendo para resolver estes 2 problemas?
É porque seu Eclipse está configurado para usar a JRE e não a JDK. Altere isso na opção “Runtime JRE” e escolha a JDK.
deu certo eu trocar para o JDK gracyane_oliveira, só q agora na hora de compilar não esta achando a pagina. Esta retornando o erro 404 - not found.
Na verdade seu projeto está compilando. O que está acontecendo é que ele não encontra a página form.jsf ao executar.
Você tem certeza que no caminho digitado precisa do /faces?
Coloque aqui todo o erro que aparece no console para que eu tenha mais informações.
Se você colocou o projeto no github, coloca o link.
Mesmo eu colocando o caminho direto: http://localhost:8080/casadocodigo/produtos/form.jsf
ocorre o mesmo erro.
No projeto do github você tem um arquivo form.xhtml e você está testando na url com form.jsf, atenção pra isso.
Se não me engano no capitulo 2 do livro é onde o autor executa o projeto com o arquivo form.xhtml dentro da pasta produtos.
A URL, portanto, fica assim: http://localhost:8080/casadocodigo/produtos/form.xhtml
Vamos continuar investigando…testa aí na url com a extensão do arquivo como .xhtml (se for desta forma que está seu arquivo.).
Mesmo executando o caminho com:
http://localhost:8080/casadocodigo/produtos/form.xhtml
ou http://localhost:8080/casadocodigo/faces/produtos/form.xhtml
ocorre o mesmo erro, 404 not found
O seu projeto do github está rodando normalmente aqui.
Deve ser alguma coisa na configuração do seu projeto junto a IDE.
Você associou o server Widfly que nem o livro mostra nas páginas 23 a 25 ?
Print do meu projeto: [Perspectiva Java]
Fiz igual ta no livro, ja refiz umas 3x para ver se tinha esquecido de alguma coisa, mesmo assim retornar o mesmo erro.
Console
17:15:06,014 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
17:15:06,440 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
17:15:06,576 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) starting
17:15:09,239 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found casadocodigo-1.0.0-SNAPSHOT.war in deployment directory. To trigger deployment create a file called casadocodigo-1.0.0-SNAPSHOT.war.dodeploy
17:15:09,337 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
17:15:09,373 INFO [org.xnio] (MSC service thread 1-3) XNIO version 3.4.0.Final
17:15:09,394 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.4.0.Final
17:15:09,514 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool – 41) WFLYCLINF0001: Activating Infinispan subsystem.
17:15:09,565 INFO [org.jboss.as.jsf] (ServerService Thread Pool – 48) WFLYJSF0007: Activated the following JSF Implementations: [main]
17:15:09,827 WARN [org.jboss.as.txn] (ServerService Thread Pool – 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
17:15:09,843 INFO [org.jboss.as.webservices] (ServerService Thread Pool – 62) WFLYWS0002: Activating WebServices Extension
17:15:09,847 INFO [org.jboss.as.security] (ServerService Thread Pool – 59) WFLYSEC0002: Activating Security Subsystem
17:15:09,868 INFO [org.jboss.as.connector] (MSC service thread 1-8) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final)
17:15:09,964 INFO [org.jboss.as.naming] (ServerService Thread Pool – 52) WFLYNAM0001: Activating Naming Subsystem
17:15:10,026 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool – 42) WFLYIIOP0001: Activating IIOP Subsystem
17:15:10,032 INFO [org.jboss.as.security] (MSC service thread 1-8) WFLYSEC0001: Current PicketBox version=4.9.6.Final
17:15:10,037 INFO [org.wildfly.extension.io] (ServerService Thread Pool – 40) WFLYIO001: Worker ‘default’ has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
17:15:10,240 INFO [org.jboss.as.naming] (MSC service thread 1-5) WFLYNAM0003: Starting Naming Service
17:15:10,298 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
17:15:10,377 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0003: Undertow 1.4.0.Final starting
17:15:10,394 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool – 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
17:15:10,407 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
17:15:10,601 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
17:15:10,607 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
17:15:10,806 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool – 61) WFLYUT0014: Creating file handler for path ‘C:\wildfly-10.1.0.Final/welcome-content’ with options [directory-listing: ‘false’, follow-symlink: ‘false’, case-sensitive: ‘true’, safe-symlink-paths: ‘[]’]
17:15:11,310 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 4.0.21.Final
17:15:11,320 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0012: Started server default-server.
17:15:11,335 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0018: Host default-host starting
17:15:11,497 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
17:15:11,681 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore C:\wildfly-10.1.0.Final\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
17:15:11,747 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) WFLYDS0013: Started FileSystemDeploymentService for directory C:\wildfly-10.1.0.Final\standalone\deployments
17:15:11,669 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0001: AIO wasn’t located on this platform, it will fall back to using pure Java NIO.
17:15:11,820 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of “casadocodigo-1.0.0-SNAPSHOT.war” (runtime-name: “casadocodigo-1.0.0-SNAPSHOT.war”)
17:15:12,334 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=C:\wildfly-10.1.0.Final\standalone\data\activemq\journal,bindingsDirectory=C:\wildfly-10.1.0.Final\standalone\data\activemq\bindings,largeMessagesDirectory=C:\wildfly-10.1.0.Final\standalone\data\activemq\largemessages,pagingDirectory=C:\wildfly-10.1.0.Final\standalone\data\activemq\paging)
17:15:12,468 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221013: Using NIO Journal
17:15:12,516 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-8) ISPN000128: Infinispan version: Infinispan ‘Chakra’ 8.2.4.Final
17:15:12,700 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool – 65) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
17:15:12,708 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool – 65) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
17:15:12,694 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool – 66) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
17:15:12,710 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool – 66) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
17:15:12,714 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool – 72) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
17:15:12,718 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool – 72) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
17:15:12,788 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
17:15:13,383 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
17:15:13,723 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
17:15:13,737 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
17:15:13,794 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
17:15:13,797 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
17:15:13,858 INFO [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.6)
17:15:14,015 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started
17:15:14,558 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
17:15:14,559 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
17:15:14,558 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
17:15:14,561 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
17:15:14,896 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221007: Server is now live
17:15:14,896 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-017 [nodeID=b7fe376f-c194-11e6-aaee-d3f7612c8e7e]
17:15:14,902 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221003: trying to deploy queue jms.queue.DLQ
17:15:14,964 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool – 66) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
17:15:14,967 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool – 72) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
17:15:14,968 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 73) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue
17:15:15,074 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0007: Registered connection factory java:/JmsXA
17:15:15,183 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-2) Resource adaptor started
17:15:15,194 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatoractivemq-ra
17:15:15,204 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
17:15:15,205 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
17:15:15,301 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment casadocodigo-1.0.0-SNAPSHOT.war
17:15:15,442 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 5.2.4.Final
17:15:15,983 INFO [org.jboss.weld.Version] (MSC service thread 1-8) WELD-000900: 2.3.5 (Final)
17:15:17,835 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool – 66) Inicializando Mojarra 2.2.13.SP1 20160303-1204 para o contexto ‘/casadocodigo-1.0.0-SNAPSHOT’
17:15:18,817 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool – 66) WFLYUT0021: Registered web context: /casadocodigo-1.0.0-SNAPSHOT
17:15:18,874 INFO [org.jboss.as.server] (ServerService Thread Pool – 37) WFLYSRV0010: Deployed “casadocodigo-1.0.0-SNAPSHOT.war” (runtime-name : “casadocodigo-1.0.0-SNAPSHOT.war”)
17:15:19,158 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
17:15:19,160 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
17:15:19,160 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in 13844ms - Started 472 of 719 services (419 services are lazy, passive or on-demand)
Pelo mensagem do console a sua aplicação está subindo normalmente.
O problema é que ele não encontra o arquivo form.xhtml para carregar.
O que tem na aba Error Log?
Outra coisa, eu estou usando o Wildfly 8.2.0.
Veja se o contexto da sua aplicação está com o nome do projeto:
Botão direito em cima do projeto > Properties > Web Projetc Settings
Se não tiver, coloque o nome do projeto no contexto, depois remova o projeto do Wildfly para ele “perder” o contexto antigo, após isso coloque novamente o projeto no Wildlfy.
As vezes é bom da um clean no server, pois pode acontecer dele não reconhecer alterações que acabamos de fazer e fica com coisas antigas.
O nome do contexto ta certo, aki eu estou utilizando a ultima versão do WildFly, e eu atualizei a versão do java também. Será pode ser alguma coisa relacionada com a versão do java com a versão do WildFly?
O log de erro ta com alguns erros:
Na versão do WildFly que estou usando funciona com a jdk7 e jdk8.
Segue meu projeto no github https://github.com/gracyaneoliveira/casacodigo
Faz um teste.
gracyane_oliveira com o seu projeto executou blz, será onde q esta o erro? olhei as pastas dois 2 projetos, esta praticamente igual, a diferença é q o meu esta com a runtime do wildFly.
Seu projeto rodou aqui sem problema. Com a runtime do wildFly , e depois sem, ela executou normal.
Usei o forge 2.20.1 para criar meu projeto. Segui o livro nestes passos.
Estou usando a IDE Red Hat JBoss Developer Studio 8.1.0.GA.
Curioso meu projeto executar em seu ambiente e o seu não executar,
As diferenças estão nas versões da IDE e do forge.
Você pode criar o projeto pela IDE mesmo, depois é só copiar o conteúdo para pom.xml
Vou fazer isso, muito obrigado pela ajuda e pela paciência gracyane_oliveira
