Discussoes de Programacao e Tecnologia

Jboos as7 + postgres driver + maven = No suitable driver found for jdbc:postgresql:postgres:543

1 resposta
R
rafael_jesus

Pessoal,

É um parto configurar o driver de banco de dados usando Jboos 7 e maven..

Eu segui essses tutoriais [url]https://docs.jboss.org/jbossas/7/plugins/maven/latest/examples/add-resource-example.html#a.add-resource-mojo.html[/url] mais não consigo fazer com que o Jboos enchergue o bendito driver,

Quando subo a aplicação eu vejo no console: No suitable driver found for jdbc:postgresql:postgres:5432/postgres

Meu procedimento é o seguinte:

Eu subo a aplicação, e dou um mvn install ele da um succcess porém aoarece um erro no console de: 
org.jboss.remoting3.remote.RemoteConnection handleException
ERROR: JBREM00200: Remote connection failed: java.io.IOException: Window open for non-existent channel
Meu pom.xml 
<plugin>
				<groupId>org.jboss.as.plugins</groupId>
				<artifactId>jboss-as-maven-plugin</artifactId>
				<version>7.0.2.Final</version>
				<executions>
					<execution>
						<id>deploy-driver</id>
						<phase>package</phase>
						<configuration>
							<name>postgresql.jar</name>
							<groupId>postgresql</groupId>
							<artifactId>postgresql</artifactId>
							<!-- <version>9.1-901.jdbc4</version> -->
						</configuration>
						<goals>
							<goal>deploy-artifact</goal>
						</goals>
					</execution>
					<execution>
						<id>add-datasource</id>
						<phase>install</phase>
						<configuration>
							<address>subsystem=datasources,data-source=postgresDS</address>
							<properties>
								<connection-url>jdbc:postgresql:postgres:5432/postgres</connection-url>
								<jndi-name>java:jboss/postgresDS</jndi-name>
								<enabled>true</enabled>
								<pool-name>postgresPool</pool-name>
								<user-name>postgres</user-name>
								<password>minhaSenha</password>
								<driver-name>postgresql.jar</driver-name>
							</properties>
						</configuration>
						<goals>
							<goal>add-resource</goal>
						</goals>
					</execution>
				</executions>
			</plugin>
Console quando subo o aplicação: 
12:50:47,699 INFO  [org.jboss.modules] JBoss Modules version 1.0.2.GA
12:50:49,350 INFO  [org.jboss.msc] JBoss MSC version 1.0.1.GA
12:50:49,428 INFO  [org.jboss.as] JBoss AS 7.0.2.Final "Arc" starting
12:50:54,415 WARN  [org.jboss.as] No security realm defined for native management service, all access will be unrestricted.
12:50:54,542 INFO  [org.jboss.as] creating http management service using network interface (management) port (9990)
12:50:54,544 WARN  [org.jboss.as] No security realm defined for http management service, all access will be unrestricted.
12:50:54,567 INFO  [org.jboss.as.logging] Removing bootstrap log handlers
12:50:54,703 INFO  [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
12:50:54,793 INFO  [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
12:50:55,064 INFO  [org.jboss.as.naming] (Controller Boot Thread) JBAS011800: Activating Naming Subsystem
12:50:55,096 INFO  [org.jboss.as.naming] (MSC service thread 1-7) JBAS011802: Starting Naming Service
12:50:55,157 INFO  [org.jboss.as.osgi] (Controller Boot Thread) JBAS011910: Activating OSGi Subsystem
12:50:55,226 INFO  [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
12:50:55,244 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.0.Beta2
12:50:55,298 INFO  [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.0.Beta3
12:50:55,319 INFO  [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.0.Beta3
12:50:55,858 INFO  [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-7) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
12:50:55,987 INFO  [org.jboss.as.remoting] (MSC service thread 1-6) Listening on /127.0.0.1:9999
12:50:55,993 INFO  [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-3) Starting remote JMX connector
12:50:56,131 INFO  [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
12:50:57,095 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-7) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
12:50:57,115 INFO  [org.jboss.as.connector] (MSC service thread 1-3) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)
12:50:57,425 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) Bound data source [java:jboss/datasources/ExampleDS]
12:51:00,856 INFO  [org.jboss.as.deployment] (MSC service thread 1-5) Started FileSystemDeploymentService for directory /home/rafael/Development/Servers/jboss.7.0.2/standalone/deployments
12:51:00,944 WARN  [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Deployment of 'agile.war' requested, but the deployment is not present
12:51:00,945 INFO  [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found scrum.war in deployment directory. To trigger deployment create a file called scrum.war.dodeploy
12:51:00,945 INFO  [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found frasys.war in deployment directory. To trigger deployment create a file called frasys.war.dodeploy
12:51:00,982 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) Starting deployment of "postgresql.jar"
12:51:01,342 INFO  [org.jboss.as.jpa] (MSC service thread 1-2) added javax.persistence.api dependency to postgresql.jar
12:51:01,428 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.0)
12:51:01,436 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) Bound data source [java:/postgresDS]
12:51:01,439 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) Bound data source [java:/myDatasource]
12:51:01,448 INFO  [org.jboss.as.server.controller] (Controller Boot Thread) Deployed "postgresql.jar"
12:51:01,458 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "scrum.war"
12:51:04,330 WARN  [org.jboss.as.server.deployment.service-loader] (MSC service thread 1-5) Encountered invalid class name "com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor" for service type "com.sun.faces.spi.injectionprovider"
12:51:04,331 WARN  [org.jboss.as.server.deployment.service-loader] (MSC service thread 1-5) Encountered invalid class name "com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection" for service type "com.sun.faces.spi.injectionprovider"
12:51:04,769 INFO  [org.jboss.jpa] (MSC service thread 1-5) read persistence.xml for scrum
12:51:04,774 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) added javax.persistence.api, javaee.api, org.jboss.as.jpa, org.javassist dependencies to scrum.war
12:51:04,775 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) added (default provider) org.hibernate dependency to application deployment (since 1 PU(s) didn't specify jboss.as.jpa.providerModule)
12:51:04,776 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) added org.hibernate dependency to application deployment
12:51:04,988 INFO  [org.jboss.weld] (MSC service thread 1-2) Processing CDI deployment: scrum.war
12:51:05,857 INFO  [org.jboss.as.jpa] (MSC service thread 1-5) Deployment has its own Persistence Provider class org.hibernate.ejb.HibernatePersistence 
12:51:06,774 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.0)
12:51:06,781 INFO  [org.jboss.weld] (MSC service thread 1-5) Starting Services for CDI deployment: scrum.war
12:51:06,834 INFO  [org.jboss.weld.Version] (MSC service thread 1-5) WELD-000900 1.1.2 (Final)
12:51:06,887 INFO  [org.jboss.jpa] (MSC service thread 1-7) starting Persistence Unit Service 'scrum.war#scrum' 
12:51:07,194 INFO  [org.hibernate.annotations.common.Version] (MSC service thread 1-7) HCANN000001: Hibernate Commons Annotations {4.0.0.CR2}
12:51:07,200 INFO  [org.hibernate.Version] (MSC service thread 1-7) HHH00412:Hibernate Core {4.0.0.CR2}
12:51:07,203 INFO  [org.hibernate.cfg.Environment] (MSC service thread 1-7) HHH00206:hibernate.properties not found
12:51:07,206 INFO  [org.hibernate.cfg.Environment] (MSC service thread 1-7) HHH00021:Bytecode provider name : javassist
12:51:07,238 INFO  [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-7) HHH00204:Processing PersistenceUnitInfo [
	name: scrum
	...]
12:51:07,685 WARN  [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-7) HHH00022:c3p0 properties were encountered, but the org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider provider class was not found on the classpath; these properties are going to be ignored.
12:51:07,686 INFO  [org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl] (MSC service thread 1-7) HHH00402:Using Hibernate built-in connection pool (not for production use!)
12:51:07,686 INFO  [org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl] (MSC service thread 1-7) HHH00115:Hibernate connection pool size: 20
12:51:07,686 INFO  [org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl] (MSC service thread 1-7) HHH00006:Autocommit mode: true
12:51:07,687 INFO  [org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl] (MSC service thread 1-7) HHH00401:using driver [org.postgresql.Driver] at URL [jdbc:postgresql:postgres:5432/postgres]
12:51:07,687 INFO  [org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl] (MSC service thread 1-7) HHH00046:Connection properties: {user=postgres, password=****, autocommit=true, release_mode=auto}
12:51:07,723 WARN  [org.hibernate.engine.jdbc.internal.JdbcServicesImpl] (MSC service thread 1-7) HHH00342:Could not obtain connection to query metadata : No suitable driver found for jdbc:postgresql:postgres:5432/postgres
12:51:07,730 INFO  [org.hibernate.dialect.Dialect] (MSC service thread 1-7) HHH00400:Using dialect: org.hibernate.dialect.PostgreSQLDialect
12:51:07,736 INFO  [org.hibernate.engine.jdbc.internal.LobCreatorBuilder] (MSC service thread 1-7) HHH00422:Disabling contextual LOB creation as connection was null
12:51:07,741 INFO  [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC service thread 1-7) HHH00268:Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
12:51:07,765 INFO  [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-7) HHH00397:Using ASTQueryTranslatorFactory
12:51:07,892 INFO  [org.hibernate.validator.util.Version] (MSC service thread 1-7) Hibernate Validator 4.2.0.Final
12:51:08,547 INFO  [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-7) HHH00228:Running hbm2ddl schema update
12:51:08,548 INFO  [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-7) HHH00102:Fetching database metadata
12:51:08,548 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-7) HHH00319:Could not get database metadata: java.sql.SQLException: No suitable driver found for jdbc:postgresql:postgres:5432/postgres
	at java.sql.DriverManager.getConnection(DriverManager.java:602) [:1.6.0_26]
	at java.sql.DriverManager.getConnection(DriverManager.java:154) [:1.6.0_26]
	at org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl.getConnection(DriverManagerConnectionProviderImpl.java:171) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.prepare(SuppliedConnectionProviderConnectionHelper.java:50) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:194) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:178) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:443) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1722) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:76) [hibernate-entitymanager-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:899) [hibernate-entitymanager-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:884) [hibernate-entitymanager-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73) [hibernate-entitymanager-4.0.0.CR2.jar:4.0.0.CR2]
	at org.jboss.as.jpa.service.PersistenceUnitService.createContainerEntityManagerFactory(PersistenceUnitService.java:143) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final]
	at org.jboss.as.jpa.service.PersistenceUnitService.start(PersistenceUnitService.java:77) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
	at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]

12:51:08,552 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-7) HHH00299:Could not complete schema update: java.sql.SQLException: No suitable driver found for jdbc:postgresql:postgres:5432/postgres
	at java.sql.DriverManager.getConnection(DriverManager.java:602) [:1.6.0_26]
	at java.sql.DriverManager.getConnection(DriverManager.java:154) [:1.6.0_26]
	at org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl.getConnection(DriverManagerConnectionProviderImpl.java:171) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.prepare(SuppliedConnectionProviderConnectionHelper.java:50) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:194) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:178) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:443) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1722) [hibernate-core-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:76) [hibernate-entitymanager-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:899) [hibernate-entitymanager-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:884) [hibernate-entitymanager-4.0.0.CR2.jar:4.0.0.CR2]
	at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73) [hibernate-entitymanager-4.0.0.CR2.jar:4.0.0.CR2]
	at org.jboss.as.jpa.service.PersistenceUnitService.createContainerEntityManagerFactory(PersistenceUnitService.java:143) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final]
	at org.jboss.as.jpa.service.PersistenceUnitService.start(PersistenceUnitService.java:77) [jboss-as-jpa-7.0.2.Final.jar:7.0.2.Final]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
	at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]

12:51:08,783 INFO  [org.jboss.weld] (MSC service thread 1-5) Starting weld service
12:51:09,622 INFO  [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
12:51:09,627 INFO  [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
12:51:09,744 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-5) Initializing Mojarra 2.1.3 (SNAPSHOT 20110825) for context '/scrum'
12:51:13,468 INFO  [org.primefaces.webapp.PostConstructApplicationEventListener] (MSC service thread 1-5) Running on PrimeFaces 3.1.1
12:51:13,972 INFO  [org.jboss.web] (MSC service thread 1-5) registering web context: /scrum
12:51:13,974 INFO  [org.jboss.as] (MSC service thread 1-6) JBoss AS 7.0.2.Final "Arc" started in 26873ms - Started 552 of 611 services (59 services are passive or on-demand)
12:51:14,112 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "scrum.war"
13:05:50,037 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) Stopped deployment postgresql.jar in 44ms
13:05:50,043 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "postgresql.jar"
13:05:50,104 INFO  [org.jboss.as.jpa] (MSC service thread 1-8) added javax.persistence.api dependency to postgresql.jar
13:05:50,112 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.0)
13:05:50,134 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) Bound data source [java:/myDatasource]
13:05:50,134 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) Bound data source [java:/postgresDS]
13:05:50,142 INFO  [org.jboss.as.server.controller] (pool-1-thread-1) Redeployed "postgresql.jar"
13:05:50,143 INFO  [org.jboss.as.server.controller] (pool-1-thread-1) Undeployed "postgresql.jar"
13:05:50,143 INFO  [org.jboss.as.server.controller] (pool-1-thread-1) Replaced deployment "postgresql.jar" with deployment "postgresql.jar"
13:05:50,739 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) Bound data source [java:jboss/postgresDS]
13:33:09,849 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) Stopped deployment postgresql.jar in 6ms
13:33:09,851 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) Starting deployment of "postgresql.jar"
13:33:09,881 INFO  [org.jboss.as.jpa] (MSC service thread 1-7) added javax.persistence.api dependency to postgresql.jar
13:33:09,887 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) Stopped deployment postgresql.jar in 35ms
13:33:09,889 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "postgresql.jar"
13:33:09,921 INFO  [org.jboss.as.jpa] (MSC service thread 1-3) added javax.persistence.api dependency to postgresql.jar
13:33:09,936 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.0)
13:33:09,943 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) Bound data source [java:/myDatasource]
13:33:09,944 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) Bound data source [java:jboss/postgresDS]
13:33:09,957 INFO  [org.jboss.as.server.controller] (pool-1-thread-3) Redeployed "postgresql.jar"
13:33:09,958 INFO  [org.jboss.as.server.controller] (pool-1-thread-3) Undeployed "postgresql.jar"
13:33:09,958 INFO  [org.jboss.as.server.controller] (pool-1-thread-3) Replaced deployment "postgresql.jar" with deployment "postgresql.jar"
13:33:10,319 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) Bound data source [java:jboss/postgresDS]

Eu fiquei com duvidas no pool name, eu coloquei auilo mesmo, nao sei se esta certo..

Alguém ai sabe o que mais teenho que fazer, já estou 2 dias nisso e nada...

Abrcs!

Rafael

Alura Análise de Dados Desenvolva hard skills técnicas e soft skills essenciais para trabalhar de forma colaborativa,...

1 Resposta

F
furlaneto

Oi Boa tarde Rafael. Estou começando a testar uma aplicação com Arquillian onde o meu próprio teste com maven starta o jboss. Mas parei no driver configurado pelo maven.
Criei um arquivo dataSource e adiciono ele pela classe de teste mesmo, não consegui fazer ele achar o ds configurando pelo pom como vc fez. Mas seguinte, estou com um problema que não consigo instalar o driver do postgre através do pom.sml.
Você conseguiu resolver seu problema?

Outra pergunta:
o que vc coloca nesse campo no dataSource é exatamente o mesmo que vc coloca no campo no persistence.xml

exemplo:
java:jboss/datasources/swaDS
java:jboss/datasources/swaDS

Obrigado.

Criado 1 de abril de 2012
Ultima resposta 7 de fev. de 2013
Respostas 1
Participantes 2

Topicos relacionados

Qual você prefere a liberdade do C++ ou a administração da JVM no Java 66 respostas Quais problemas na nossa vida de programador? 128 respostas Vagas de emprego em TI encalham. Saiba o motivo 98 respostas Enade 2011 6 respostas JPA + Hibernate + getSingleResult 7 respostas
Alura Git Flow: entenda o que é, como e quando utilizar Entenda o que é Git Flow, como funciona seu fluxo com branches como Master, Develop, Feature, Release e Hotfix, além de vantagens e desvantagens.
Casa do Codigo Casa do Codigo — Livros de tecnologia Livros de programacao, infraestrutura e inovacao