Erro ao criar o datasource no jboss 7

Assuntos Gerais
#1

bom dia Senhores.

Nao estou conseguindo criar o datasource no jboss 7.

crie o diretorio C:\jboss-as-web-7.0.0.Final\modules\com\mysql\main, dentro do mesmo coloquei o arquivos mysql-connector-java-5.0.7-bin.jar e module.xml

conteudo do arquivo module.xml.

<?xml version="1.0" encoding="UTF-8"?>

<module xmlns="urn:jboss:module:1.0" name="com.mysql">
  <resources>
    <resource-root path="mysql-connector-java-5.0.7-bin.jar"/>
  </resources>
  <dependencies>
    <module name="javax.api"/>
  </dependencies>
</module>

standalone.bat

<datasource jndi-name="java:/MySQLDS" pool-name="MyPool"
					enabled="true" jta="true" use-java-context="true" use-ccm="true">
					<connection-url>jdbc:mysql://localhost:3306/ss</connection-url>
					<driver>mysql</driver>
					<security>
						<user-name>root</user-name>
						<password>root</password>
					</security>
					<statement>
						<prepared-statement-cache-size>100</prepared-statement-cache-size>
						<share-prepared-statements />
					</statement>
				</datasource>

				<drivers>

					<driver name="mysql" module="com.mysql" />
                                </drivers>

log

09:33:11,388 INFO  [org.jboss.modules] JBoss Modules version 1.0.1.GA
09:33:12,105 INFO  [org.jboss.msc] JBoss MSC version 1.0.0.GA
09:33:12,272 INFO  [org.jboss.as] JBoss AS 7.0.0.Final "Lightning" starting
09:33:14,717 INFO  [org.jboss.as] creating http management service using network interface (management) port (9990) securePort (-1)
09:33:14,754 INFO  [org.jboss.as.logging] Removing bootstrap log handlers
09:33:14,839 INFO  [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
09:33:14,876 INFO  [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
09:33:15,203 INFO  [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
09:33:15,243 INFO  [org.jboss.as.naming] (MSC service thread 1-4) Starting Naming Service 
09:33:15,260 INFO  [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
09:33:15,312 INFO  [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
09:33:15,334 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.0.Beta2
09:33:15,369 INFO  [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.0.Beta3
09:33:15,409 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.0.Beta3
09:33:16,087 INFO  [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-4) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.6.0_21\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;native
09:33:16,123 INFO  [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
09:33:16,350 INFO  [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-3) Starting remote JMX connector
09:33:16,427 INFO  [org.jboss.as.remoting] (MSC service thread 1-10) Listening on /127.0.0.1:9999
09:33:16,664 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
09:33:16,853 INFO  [org.jboss.as.connector] (MSC service thread 1-16) Starting JCA Subsystem (JBoss IronJacamar 1.0.0.CR2)
09:33:16,987 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-9) Bound data source [java:jboss/datasources/ExampleDS]
09:33:17,900 INFO  [org.jboss.as.deployment] (MSC service thread 1-9) Started FileSystemDeploymentService for directory C:\jboss-as-web-7.0.0.Final\standalone\deployments
09:33:18,099 INFO  [org.jboss.as.controller] (Controller Boot Thread) Service status report
   New missing/unsatisfied dependencies:
      service jboss.jdbc-driver.mysql (missing)

09:33:18,136 ERROR [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final "Lightning" started (with errors) in 7477ms - Started 93 of 151 services (3 services failed or missing dependencies, 55 services are passive or on-demand)

aparentemente ele nao encontra o drive do mysql, alguem o que faltando para ele funcionar

Att.

#2

Experimente especificar o xa-datasource-class dentro do driver

#3

como nosso amigo ai em cima disse
utilize o xa-datasource dentro de drivers

#4

Olá, não há necessidade de utilziar xa-datasource a não ser que sua aplicação utilize esse tipo de funcionalidade… Veja abaixo um simples datasource no JBoss AS 7.1 Final…

<subsystem xmlns="urn:jboss:domain:datasources:1.0"> <datasources> <datasource jta="false" jndi-name="java:/MySQLDS" pool-name="MySQLDS" enabled="true" spy="true" use-ccm="false"> <connection-url>jdbc:mysql://localhost:3306/db_store</connection-url> <driver>mysql-connector-java-5.1.18-bin.jar</driver> <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation> <pool> <min-pool-size>50</min-pool-size> <max-pool-size>200</max-pool-size> </pool> <security> <user-name>sa</user-name> <password>sa</password> </security> <statement> <prepared-statement-cache-size>100</prepared-statement-cache-size> <share-prepared-statements>true</share-prepared-statements> </statement> </datasource> <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true"> <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url> <driver>h2</driver> <security> <user-name>sa</user-name> <password>sa</password> </security> </datasource> <drivers> <driver name="mysql-connector-java-5.1.18-bin.jar" module="com.mysql"> <driver-class>com.mysql.jdbc.Driver</driver-class> </driver> <driver name="h2" module="com.h2database.h2"> <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class> </driver> </drivers> </datasources> </subsystem>

E vez de criar o driver como módulo simplesmente , faça deploy do jar mysql (spec JDBC 4) --> http://dev.mysql.com/downloads/connector/j/ --> Connector/J 5.1.18
O deploy deve ser realizado em JBOSS_HOME/standalone/deployments

Teste a aplicação fazendo um lookup e realizando um simples select utilzando o datasource criado.

Abraço

#5