Lets assume you are using the "default" configuration
1. Put your driver jar in .../default/lib (before starting jboss)
2. Edit the appropriate settings in the *-ds.xml to fit your installation.
3. As with any deployable, put the *-ds.xml in ...default/deploy. You may want to remove hsqldb-ds.xml, but be careful of the jms persistence manager which is using it by default.
4. If you are using cmp, edit .../default/conf/standardjbosscmp-jdbc.xml to indicate the name of your datasource and the appropriate type mapping. (before starting jboss)
Personally, I thought the numerous db-specific example config files were clearer than the single example in 2.4 jboss.jcml. In fact I think the number of questions may actually have declined.
You're right, they are much easier. My problem was that I couldn't get it to work, and I couldn't find anything that said that using the *-ds.xml file was all I needed to do, so I wasn't sure if I was missing something.
Shouldn't there be way to associate these files (ds) with a specific application by puting them in the application's WAR file?
You're right, it's much easier. My problem is that I couldn't get it to work, and I couldn't find anything that said that setting up the ds file was all I needed to do, I wasn't sure if I was missing something.
Thanks for the help!
You can put *-ds.xml files in .ears if you include a jboss-app.xml file next to application.xml with
They may also get deployed from inside ejb jars and .rar with no special instructions. .war's are harder since for the most part deployment is not handled by jboss.
Awesome, thanks again for the help!