> 2. created the jaws.xml and jbosscmp-jdbc.xml in the META-INF dir of my ejb jar.
What do you have in your jbosscmp-jdbc.xml?
Have you set the datasource correctly in there?
my jbosscmp-jdbc.xml has the following:
It looks like the settings in this file are ignored.
Have you checked the debug output from the server log file to see that it is loading your jbosscmp-jdbc file and overriding the default settings?
the server log didn't said that my properties were override, but when I added the DOCTYPE in the jboss-cmp-jdbc.xml the properties were overridden (and the log said it too).
I did the same in the jaws.xml but it didn't worked. I'll try to figure out what is happening.
Thanks for your reply
Why have you got a jaws.xml file in there as well - I didn't think it was relevant for the CMP 2 engine?
I had a problem with configuring Oracle with JBoss 3.0alpha and then I switched to JBoss 3.0beta and it worked fine w/o any changes in conf files.
I guess that the holiday was good for my brain. You are right, I was putting the configuration in jaws.xml instead of jbosscmp-jdbc.xml.
Now everything is up and running. Thanks again for your information.
now that you solved the problem i have 2 questions: did you make any changes to the standardjbosscmp-jdbc.xml in the conf directry of jboss? my problem is, that jboss seems to ignore the standardjbosscmp-jdbc.xml in my META-INF directory.
could you help me??
After greping the source code I've noticed that jboss check the DOCTYPE tag in the jboss-cmpjdbc.xml file.
So I added the following DOCTYPE declaration:
<!DOCTYPE jbosscmp-jdbc PUBLIC
"-//JBoss//DTD JBOSSCMP-JDBC 3.0//EN"
And jboss started to read my configuration. Just pay attention to the spelling.
I didn't changed anything in the standardjbosscmp-jdbc.xml that is located in the conf/default directory.
Hope this help