one question about jboss db conf

[abyss]

what can i do when i need build many pool in the oracle-service.xml

[davidjencks]

If you mean that you need to connect to many database instances, you need a configuration for each database instance you wish to connect to. You might consider using 3.2 and the simpler *-ds.xml configuration format. You can include many configurations in the same *-service.xml or *-ds.xml file.

[abyss]

Thanks~~~
But my mean is one oracle-db, and many pool.Because our proj that is in the weblogic has three pool(oraclePool, escmPool, ejbPool), but all of pools point at only one oracle db, when i replant our proj from weblogic to jboss, how can i build those pools in the oracle-service.xml?
(we use toplink to contact cmp and db, in toplink-cmp-*.xml must use those pools)

[abyss]

Thanks~~~
But my mean is one oracle-db, and many pool.Because our proj that is in the weblogic has three pool(oraclePool, escmPool, ejbPool), but all of pools point at only one oracle db, when i replant our proj from weblogic to jboss, how can i build those pools in the oracle-service.xml?
(we use toplink to contact cmp and db, in toplink-cmp-*.xml must use those pools)

[davidjencks]

Talk about pools is imprecise. An application will not deal with a pool but a datasource bound in jndi. For each datasource bound in jndi you need a datasource configuration. In 3.0 these are just mbean configurations, as in the example *-service.xml files. You can have as many configurations in one file as you wish. Be sure the object name for each mbean is unique.

In 3.2 I recommend the *-ds.xml format since it is so much simpler. Again, you can have as many configurations in one file as you wish.

Note that if you are using local (non-xa) database drivers, and more than one datasource in a transaction is not read only, you are risking database inconsistency problems in case of failure during commit.

[abyss]

thank you