Solucionado (ver solução)
Solucionado
(ver solução)
2
respostas

Duvida Aula 3

Ola, fiz todo o passo a passo da aula 3, o console avisa que o sistema subiu, porém as paginás avisam de erro 404

segue o console

14:48:34,842 INFORMAÇÕES [org.jboss.modules] JBoss Modules version 1.1.1.GA
14:48:34,986 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
14:48:35,018 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
14:48:35,629 INFO  [org.xnio] XNIO Version 3.0.3.GA
14:48:35,629 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
14:48:35,641 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
14:48:35,641 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
14:48:35,657 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
14:48:35,672 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
14:48:35,672 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
14:48:35,688 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:48:35,688 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
14:48:35,704 INFO  [org.jboss.as.connector] (MSC service thread 1-7) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
14:48:35,719 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
14:48:35,719 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
14:48:35,735 INFO  [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
14:48:35,735 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
14:48:35,735 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
14:48:35,735 INFO  [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.7.Final
14:48:35,782 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
14:48:35,923 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA
14:48:35,969 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-5) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
14:48:36,126 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on localhost/127.0.0.1:4447
14:48:36,141 INFO  [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on /127.0.0.1:9999
14:48:36,141 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory C:\Users\KamuiKM\Documents\JBOSS\jboss-as-7.1.1.Final\standalone\deployments
14:48:36,141 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found livraria.war in deployment directory. To trigger deployment create a file called livraria.war.dodeploy
14:48:36,210 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
14:48:36,210 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:/livrariaDS]
14:48:36,335 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
14:48:36,335 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 1699ms - Started 137 of 213 services (74 services are passive or on-demand)
2 respostas
solução!

Vixe, por algum motivo ele não está gerando o arquivo de solicitação de deploy automático... é a mensagem que ta aparecendo no console. Não sei direito o motivo...

Eu faria o padrão: excluiria o wildfly e instalaria de novo, associando ao eclipse.

Era isso mesmo Alberto, Exclui totalmente do projeto o JBOSS anterior e coloquei 1 novo, funcionou normalmente.

vlw msm pela ajuda

Quer mergulhar em tecnologia e aprendizagem?

Receba a newsletter que o nosso CEO escreve pessoalmente, com insights do mercado de trabalho, ciência e desenvolvimento de software