1
resposta

CDI e Wildfly configura e não inseriu noBD

Após todas as configurações não insere no bd e nao da erro

17:16:26,941 INFO  [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 73) HHH000204: Processing PersistenceUnitInfo [
    name: casadocodigo-dev
    ...]
17:16:26,945 INFO  [org.hibernate.orm.deprecation] (ServerService Thread Pool -- 73) HHH90000001: Found usage of deprecated setting for specifying Scanner [hibernate.ejb.resource_scanner]; use [hibernate.archive.scanner] instead
17:16:26,960 INFO  [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment casadocodigo.war
17:16:26,997 INFO  [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0006: Starting Services for CDI deployment: casadocodigo.war
17:16:26,999 INFO  [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0009: Starting weld service for deployment casadocodigo.war
17:16:27,008 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 73) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'casadocodigo.war#casadocodigo-dev'
17:16:27,010 INFO  [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 73) HHH000400: Using dialect: org.hibernate.dialect.MySQL5InnoDBDialect
17:16:27,015 INFO  [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 73) Envers integration enabled? : true
17:16:27,036 INFO  [org.hibernate.tool.hbm2ddl.SchemaUpdate] (ServerService Thread Pool -- 73) HHH000228: Running hbm2ddl schema update
17:16:27,297 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 73) Inicializando Mojarra 2.2.12-jbossorg-2 20150729-1131 para o contexto '/casadocodigo'
17:16:27,436 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0021: Registered web context: /casadocodigo
17:16:27,466 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "casadocodigo.war" (runtime-name : "casadocodigo.war")
1 resposta

Oi José

Confirma se você está usando o MySQL 5 ao invés do MySQL 8, já tive um problema similar por conta do driver JDBC do MySQL do projeto.