Postgre Datasource no JBoss

Aí galera,

Alguém já fez deploy de datasourde Postgre no JBoss.

Estou me virando e não consigo, o exemplo “default” do JBoss não tá rolando.

Estou usando Postgre 8.0 e JBoss 3.2.3. Estou usando os drivers JDBC j2ee do Postgre.

Valeu, t+

Olá
vou postar o arquivo de configuração do DS no JBoss 3.0.8 o driver que eu uso é o pg74jdbc3.jar

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

<mbean code=“org.jboss.resource.connectionmanager.LocalTxConnectionManager”

name=“jboss.jca:service=LocalTxCM,name=PostgresDS”>

<!-- You must include a login module configuration named PostgresDbRealm
in your login-conf.xml, here is an example for a
ConfiguredIdentityLoginModule:

<application-policy name = "PostgresDbRealm">
   <authentication>
      <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
         <module-option name = "principal">yourprincipal</module-option>
         <module-option name = "userName">yourusername</module-option>
         <module-option name = "password">yourpassword</module-option>
         <module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=PostgresDS</module-option>
      </login-module>
   </authentication>
</application-policy>

NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the 
  module-option name = "managedConnectionFactoryName"
must match the object name of the ConnectionManager you are configuring here.
-->
<!-- ===================================================================== -->
<!--uncomment out this line if you are using the PostgresDbRealm above
<attribute name="SecurityDomainJndiName">PostgresDbRealm</attribute>
-->

<depends optional-attribute-name="ManagedConnectionFactoryName">
  <!--embedded mbean-->
  <mbean code="org.jboss.resource.connectionmanager.RARDeployment" name="jboss.jca:service=LocalTxDS,name=PostgresDS">
    <attribute name="JndiName">PostgresDS</attribute>
    <attribute name="ManagedConnectionFactoryProperties">
      <properties>
        <config-property name="ConnectionURL" 

type=“java.lang.String”>jdbc:postgresql://servidor:5432/bancodedados
org.postgresql.Driver

postgres

    </attribute>
    <!--hack-->
    <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC 

Wrapper

    <!--real attributes-->
  </mbean>
</depends>

<depends optional-attribute-name="ManagedConnectionPool">
  <!--embedded mbean-->
  <mbean code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool" 

name=“jboss.jca:service=LocalTxPool,name=PostgresDS”>

    <attribute name="MinSize">0</attribute>
    <attribute name="MaxSize">50</attribute>
    <attribute name="BlockingTimeoutMillis">5000</attribute>
    <attribute name="IdleTimeoutMinutes">15</attribute>
    <!--criteria indicates if Subject (from security domain) or app supplied
        parameters (such as from getConnection(user, pw)) are used to distinguish
        connections in the pool. Choices are 
        ByContainerAndApplication (use both), 
        ByContainer (use Subject),
        ByApplication (use app supplied params only),
        ByNothing (all connections are equivalent, usually if adapter supports
          reauthentication)-->
    <attribute name="Criteria">ByContainer</attribute>
  </mbean>

</depends>
<depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager</depends>

<depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager</depends>

<attribute name="TransactionManager">java:/TransactionManager</attribute>
<!--make the rar deploy! hack till better deployment-->
<depends>jboss.jca:service=RARDeployer</depends>
[/code]

Valeu a dica,

Como eu estava utilizando uma configuração alternativa “ports-01” através de binding-manager, eu precisava configurar umas portas a mais no jboss-service.xml. Esse era o erro.

A configuração default do JBoss funcionou.

t+