Livro Java EE - Aproveite toda a plataforma para construir aplicações (resolvido)

No capitulo 2, a pasta indicada para criar armazenar o resource XHTML referente ao primeiro formulário:
WebContent/produtos/form.xhtml não existe e, mesmo criando a mesma na raiz do projeto o JSF não consegue localizar o arquivo.
Onde criá-la? Por que o Forge não a criou na geração do projeto?

Crie a pasta produtos na pasta webapp:
webapp/produtos/form.xhtml

1 curtida

Obrigado, Gracyane.

Já havia feito.

Agora estou recebendo esta mensagem quando tento configurar a conexão ao banco de acordo com o capítulo 03 (aparentemente não tenho a lib do hibernate necessária, mas segui todos os passos):

Alguma dica?

No seu arquivo persistence.xml na linha onde tem:

<provider> org.hibernate.ejb.HibernatePersistence </provider>

Deixe tudo em uma única linha.

<provider>org.hibernate.ejb.HibernatePersistence</provider>

No stackoverflow algumas pessoas dizem que isso resolve.

1 curtida

Oi, Gracyane

Antes de tudo obrigado pela ajuda:) Retirei as quebras de linha, mas não deu certo( De acordo com o log abaixo ele não consegue carregar o datasource casadocodigoDS) :
12:07:05,114 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
12:07:08,031 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
12:07:08,245 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) starting
12:07:19,820 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
12:07:19,873 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
12:07:19,904 INFO [org.xnio] (MSC service thread 1-7) XNIO version 3.4.0.Final
12:07:19,917 INFO [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.4.0.Final
12:07:20,157 INFO [org.jboss.as.webservices] (ServerService Thread Pool – 62) WFLYWS0002: Activating WebServices Extension
12:07:20,163 INFO [org.jboss.as.security] (ServerService Thread Pool – 59) WFLYSEC0002: Activating Security Subsystem
12:07:20,174 INFO [org.jboss.as.naming] (ServerService Thread Pool – 52) WFLYNAM0001: Activating Naming Subsystem
12:07:20,187 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool – 41) WFLYCLINF0001: Activating Infinispan subsystem.
12:07:20,157 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.
12:07:20,206 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool – 42) WFLYIIOP0001: Activating IIOP Subsystem
12:07:20,209 INFO [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Current PicketBox version=4.9.6.Final
12:07:20,480 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
12:07:20,498 INFO [org.jboss.as.connector] (MSC service thread 1-6) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final)
12:07:20,520 INFO [org.jboss.as.jsf] (ServerService Thread Pool – 48) WFLYJSF0007: Activated the following JSF Implementations: [main]
12:07:20,677 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 1.4.0.Final starting
12:07:20,823 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool – 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
12:07:20,828 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = h2
12:07:20,866 INFO [org.jboss.as.naming] (MSC service thread 1-8) WFLYNAM0003: Starting Naming Service
12:07:20,868 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
12:07:21,010 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool – 61) WFLYUT0014: Creating file handler for path ‘C:\Desenvolvimento\wildfly-10.1.0.Final/welcome-content’ with options [directory-listing: ‘false’, follow-symlink: ‘false’, case-sensitive: ‘true’, safe-symlink-paths: ‘[]’]
12:07:21,485 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0012: Started server default-server.
12:07:21,493 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0018: Host default-host starting
12:07:21,556 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool – 36) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 6.0)
12:07:21,558 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = mysql
12:07:21,584 INFO [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 4.0.21.Final
12:07:21,631 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.
12:07:21,632 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) 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.
12:07:21,855 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
12:07:22,051 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-1) Error during the deployment of java:jboss/datasources/casadocodigoDS: javax.resource.ResourceException: IJ031103: At least one connection property must be defined for datasource-class: com.mysql.jdbc.Driver
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createConnectionFactory(LocalManagedConnectionFactory.java:108)
at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:772)
at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:312)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:371)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:149)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

12:07:22,060 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.data-source.casadocodigoDS: org.jboss.msc.service.StartException in service org.wildfly.data-source.casadocodigoDS: WFLYJCA0033: Error during the deployment of casadocodigoDS
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:163)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:151)
… 5 more

12:07:22,070 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
12:07:22,740 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0001: AIO wasn’t located on this platform, it will fall back to using pure Java NIO.
12:07:22,942 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:\Desenvolvimento\wildfly-10.1.0.Final\standalone\data\activemq\journal,bindingsDirectory=C:\Desenvolvimento\wildfly-10.1.0.Final\standalone\data\activemq\bindings,largeMessagesDirectory=C:\Desenvolvimento\wildfly-10.1.0.Final\standalone\data\activemq\largemessages,pagingDirectory=C:\Desenvolvimento\wildfly-10.1.0.Final\standalone\data\activemq\paging)
12:07:23,084 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore C:\Desenvolvimento\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
12:07:23,095 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: java.net.BindException: Address already in use: bind localhost/127.0.0.1:9990
at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:273)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

12:07:23,124 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221013: Using NIO Journal
12:07:23,160 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of “casadocodigo.war” (runtime-name: “casadocodigo.war”)
12:07:23,166 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Desenvolvimento\wildfly-10.1.0.Final\standalone\deployments
12:07:23,660 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
12:07:24,346 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
12:07:24,361 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
12:07:24,364 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
12:07:24,689 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-8) ISPN000128: Infinispan version: Infinispan ‘Chakra’ 8.2.4.Final
12:07:24,915 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool – 71) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
12:07:24,918 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.
12:07:24,925 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool – 73) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
12:07:24,924 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool – 71) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
12:07:24,925 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.
12:07:24,926 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool – 73) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
12:07:25,774 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-2) WFLYIIOP0009: CORBA ORB Service started
12:07:25,854 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
12:07:25,854 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
12:07:25,854 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
12:07:25,854 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
12:07:25,951 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221007: Server is now live
12:07:25,953 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-017 [nodeID=063a5134-f335-11e6-aacb-7fb8f7847d55]
12:07:25,976 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool – 64) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
12:07:26,039 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 71) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue
12:07:26,050 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool – 72) AMQ221003: trying to deploy queue jms.queue.DLQ
12:07:26,056 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool – 73) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
12:07:26,063 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA
12:07:26,130 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-4) Resource adaptor started
12:07:26,131 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatoractivemq-ra
12:07:26,133 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
12:07:26,134 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
12:07:26,201 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
12:07:27,546 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.6)
12:07:28,023 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Read persistence.xml for casadocodigo-dev
12:07:29,655 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment casadocodigo.war
12:07:30,686 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-5) HV000001: Hibernate Validator 5.2.4.Final
12:07:31,206 INFO [org.jboss.weld.Version] (MSC service thread 1-6) WELD-000900: 2.3.5 (Final)
12:07:31,591 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation (“add”) failed - address: ([
(“core-service” => “management”),
(“management-interface” => “http-interface”)
]) - failure description: {
“WFLYCTL0080: Failed services” => {“jboss.serverManagement.controller.management.http” => “org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: java.net.BindException: Address already in use: bind localhost/127.0.0.1:9990”},
“WFLYCTL0412: Required services that are not installed:” => [“jboss.serverManagement.controller.management.http”],
“WFLYCTL0180: Services with missing/unavailable dependencies” => undefined
}
12:07:31,594 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation (“deploy”) failed - address: ([(“deployment” => “casadocodigo.war”)]) - failure description: {“WFLYCTL0180: Services with missing/unavailable dependencies” => undefined}
12:07:31,595 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation (“add”) failed - address: ([
(“subsystem” => “datasources”),
(“data-source” => “casadocodigoDS”)
]) - failure description: {
“WFLYCTL0080: Failed services” => {“org.wildfly.data-source.casadocodigoDS” => “org.jboss.msc.service.StartException in service org.wildfly.data-source.casadocodigoDS: WFLYJCA0033: Error during the deployment of casadocodigoDS
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf”},
“WFLYCTL0412: Required services that are not installed:” => [“org.wildfly.data-source.casadocodigoDS”],
“WFLYCTL0180: Services with missing/unavailable dependencies” => undefined
}
12:07:31,597 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation (“add”) failed - address: ([
(“subsystem” => “datasources”),
(“data-source” => “casadocodigoDS”)
]) - failure description: {
“WFLYCTL0080: Failed services” => {“org.wildfly.data-source.casadocodigoDS” => “org.jboss.msc.service.StartException in service org.wildfly.data-source.casadocodigoDS: WFLYJCA0033: Error during the deployment of casadocodigoDS
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf”},
“WFLYCTL0412: Required services that are not installed:” => [
“org.wildfly.data-source.casadocodigoDS”,
“org.wildfly.data-source.casadocodigoDS”
],
“WFLYCTL0180: Services with missing/unavailable dependencies” => undefined
}
12:07:31,807 INFO [org.jboss.as.server] (ServerService Thread Pool – 37) WFLYSRV0010: Deployed “casadocodigo.war” (runtime-name : “casadocodigo.war”)
12:07:31,810 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service org.wildfly.data-source.casadocodigoDS: org.jboss.msc.service.StartException in service org.wildfly.data-source.casadocodigoDS: WFLYJCA0033: Error during the deployment of casadocodigoDS
service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: java.net.BindException: Address already in use: bind localhost/127.0.0.1:9990

12:07:32,008 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled
12:07:32,009 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled
12:07:32,009 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started (with errors) in 28284ms - Started 446 of 721 services (24 services failed or missing dependencies, 420 services are lazy, passive or on-demand)
12:07:32,354 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment casadocodigo.war (runtime-name: casadocodigo.war) in 275ms
12:07:32,599 WARN [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []
12:07:32,601 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Undeployed “casadocodigo.war” (runtime-name: “casadocodigo.war”)
12:07:32,603 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.WeldInitialListener”.WeldInstantiator, service jboss.deployment.unit.“casadocodigo.war”.component.“javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV”.WeldInstantiator]
service jboss.deployment.unit.“casadocodigo.war”.WeldStartService (missing) dependents: [service jboss.deployment.unit.“casadocodigo.war”.component.“org.jboss.weld.servlet.WeldTerminalListener”.WeldInstantiator, service jboss.undertow.deployment.default-server.default-host./casadocodigo.UndertowDeploymentInfoService, service jboss.deployment.unit.“casadocodigo.war”.component.“com.sun.faces.config.ConfigureListener”.WeldInstantiator, service jboss.deployment.unit.“casadocodigo.war”.CdiValidatorFactoryService, WFLYCTL0208: … and 6 more ]
service jboss.deployment.unit.“casadocodigo.war”.beanmanager (missing) dependents: [service jboss.persistenceunit.“casadocodigo.war#casadocodigo-dev”]
service jboss.deployment.unit.“casadocodigo.war”.component.“com.sun.faces.config.ConfigureListener”.CREATE (missing) dependents: [service jboss.deployment.unit.“casadocodigo.war”.component.“com.sun.faces.config.ConfigureListener”.START]
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.“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]
service jboss.deployment.unit.“casadocodigo.war”.component.“javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV”.CREATE (missing) dependents: [service jboss.deployment.unit.“casadocodigo.war”.component.“javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV”.START]
service jboss.deployment.unit.“casadocodigo.war”.component.“javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV”.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.“javax.servlet.jsp.jstl.tlv.ScriptFreeTLV”.CREATE (missing) dependents: [service jboss.deployment.unit.“casadocodigo.war”.component.“javax.servlet.jsp.jstl.tlv.ScriptFreeTLV”.START]
service jboss.deployment.unit.“casadocodigo.war”.component.“javax.servlet.jsp.jstl.tlv.ScriptFreeTLV”.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.“org.jboss.weld.servlet.WeldInitialListener”.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.“org.jboss.weld.servlet.WeldTerminalListener”.CREATE (missing) dependents: [service jboss.deployment.unit.“casadocodigo.war”.component.“org.jboss.weld.servlet.WeldTerminalListener”.START]
service jboss.deployment.unit.“casadocodigo.war”.component.“org.jboss.weld.servlet.WeldTerminalListener”.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.“org.jboss.weld.servlet.WeldTerminalListener”.WeldInstantiator (missing) dependents: [service jboss.deployment.unit.“casadocodigo.war”.component.“org.jboss.weld.servlet.WeldTerminalListener”.START]
service jboss.deployment.unit.“casadocodigo.war”.ee.ComponentRegistry (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./casadocodigo.UndertowDeploymentInfoService]
service jboss.deployment.unit.“casadocodigo.war”.jndiDependencyService (missing) dependents: [service jboss.deployment.unit.“casadocodigo.war”.component.“javax.servlet.jsp.jstl.tlv.ScriptFreeTLV”.START, service jboss.deployment.unit.“casadocodigo.war”.WeldStartService, service jboss.deployment.unit.“casadocodigo.war”.component.“org.jboss.weld.servlet.WeldInitialListener”.START, service jboss.deployment.unit.“casadocodigo.war”.component.“org.jboss.weld.servlet.WeldTerminalListener”.START, WFLYCTL0208: … and 3 more ]
service jboss.persistenceunit.“casadocodigo.war#casadocodigo-dev” (missing) dependents: [service jboss.deployment.unit.“casadocodigo.war”.component.“javax.servlet.jsp.jstl.tlv.ScriptFreeTLV”.START, service jboss.undertow.deployment.default-server.default-host./casadocodigo.UndertowDeploymentInfoService, service jboss.deployment.unit.“casadocodigo.war”.WeldStartService, service jboss.deployment.unit.“casadocodigo.war”.deploymentCompleteService, WFLYCTL0208: … and 4 more ]
service jboss.undertow.deployment.default-server.default-host./casadocodigo.UndertowDeploymentInfoService (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./casadocodigo]
service jboss.undertow.deployment.default-server.default-host./casadocodigo.codec (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./casadocodigo.UndertowDeploymentInfoService]
service jboss.undertow.deployment.default-server.default-host./casadocodigo.session (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./casadocodigo.UndertowDeploymentInfoService]
service org.wildfly.request-controller.control-point.“casadocodigo.war”.undertow (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./casadocodigo.UndertowDeploymentInfoService]
WFLYCTL0186: Services which failed to start: service org.wildfly.data-source.casadocodigoDS: org.jboss.msc.service.StartException in service org.wildfly.data-source.casadocodigoDS: WFLYJCA0033: Error during the deployment of casadocodigoDS
service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: java.net.BindException: Address already in use: bind localhost/127.0.0.1:9990

12:07:36,858 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

 <datasource jndi-name="java:jboss/datasources/casadocodigoDS" pool-name="casadocodigoDS">
                <connection-url>jdbc:mysql://localhost:3306/casadocodigo</connection-url>
                <driver>mysql</driver>
                <security>
                    <user-name>root</user-name>
                    <password>Sab8ath</password>
                </security>
            </datasource>
            <drivers>
                <driver name="h2" module="com.h2database.h2">
                    <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
                </driver>
                <driver name="mysql" module="com.mysql">
                    <datasource-class>com.mysql.jdbc.Driver</datasource-class>
                </driver>
            </drivers>

:cry:

Deixei minha configuração desta forma:

o connector do mysql que eu uso não é extenção .bin.jar, mas apenas .jar.

1 curtida

Gracyane,

Deu certo \o/

Mas somente quando eu removi esta linha do stantalone-full.xml:
<datasource-class>com.mysql.jdbc.Driver</datasource-class>

E criei o banco casadocodigo previamente.

Muito obrigado pela ajuda :smiley: