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

ERRO "New missing/unsatisfied dependencies:"

Estou com um erro depois e ter configurado meu banco e tentar reiniciar a aplicação, imaginei que fosse alguma configuração errada da base de dados, porém a tabela foi criada na base, mas estou tomando esses seguintes erros:

17:05:50,677 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
17:05:50,677 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
17:05:50,678 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started (with errors) in 18500ms - Started 385 of 693 services (19 services failed or missing dependencies, 397 services are lazy, passive or on-demand)
17:05:50,748 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 21) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'casadocodigo.war#casadocodigo-dev'
17:05:50,829 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 13) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'casadocodigo.war#casadocodigo-dev'
17:05:50,864 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment casadocodigo.war (runtime-name: casadocodigo.war) in 128ms
17:05:51,111 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Undeployed "casadocodigo.war" (runtime-name: "casadocodigo.war")
17:05:51,118 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Service status report
WFLYCTL0184:    New missing/unsatisfied dependencies:
      service jboss.deployment.unit."casadocodigo.war".WeldBootstrapService (missing) dependents: [service jboss.deployment.unit."casadocodigo.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator, service jboss.deployment.unit."casadocodigo.war".WeldStartService, service jboss.deployment.unit."casadocodigo.war".CdiValidatorFactoryService, service jboss.deployment.unit."casadocodigo.war".component."javax.faces.webapp.FacetTag".WeldInstantiator, WFLYCTL0208: ... and 4 more ] 
      service jboss.deployment.unit."casadocodigo.war".WeldStartService (missing) dependents: [service jboss.deployment.unit."casadocodigo.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator, service jboss.deployment.unit."casadocodigo.war".CdiValidatorFactoryService, service jboss.deployment.unit."casadocodigo.war".component."javax.faces.webapp.FacetTag".WeldInstantiator, service jboss.deployment.unit."casadocodigo.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator, WFLYCTL0208: ... and 4 more ] 
      service jboss.deployment.unit."casadocodigo.war".component."com.sun.faces.config.ConfigureListener".JndiBindingsService (missing) dependents: [service jboss.deployment.unit."casadocodigo.war".jndiDependencyService] 
      service jboss.deployment.unit."casadocodigo.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./casadocodigo.UndertowDeploymentInfoService, service jboss.deployment.unit."casadocodigo.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./casadocodigo] 
      service jboss.deployment.unit."casadocodigo.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."casadocodigo.war".component."com.sun.faces.config.ConfigureListener".START] 
      service jboss.deployment.unit."casadocodigo.war".component."javax.faces.webapp.FacetTag".JndiBindingsService (missing) dependents: [service jboss.deployment.unit."casadocodigo.war".jndiDependencyService] 
      service jboss.deployment.unit."casadocodigo.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./casadocodigo.UndertowDeploymentInfoService, service jboss.deployment.unit."casadocodigo.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./casadocodigo]

........... Outros service ........... //fim do log 17:05:55,400 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found casadocodigo.war in deployment directory. To trigger deployment create a file called casadocodigo.war.dodeploy

2 respostas

Notei que compilar por fora com maven estourou erros em todas a anotações de persistência das classes Models e DAO,

solução!

Encontrei uma solução

No arquivo Standalone-full.xml tem uma propriedade que estava como :

(default-bindings context-service="java:jboss/ee/concurrency/context/default" datasource="java:jboss/datasources/ExampleDS" ...... )

Ao colocar o caminho correto da datasource ali em (datasource="java:jboss/datasources/ExampleDS") o erro sumiu, acredito que tenha faltado falar sobre a alteração dessa propriedade na explicação do vídeo..

Como ficou:

(default-bindings context-service="java:jboss/ee/concurrency/context/default" datasource="java:jboss/datasources/casadocodigoDS" ...... )

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