You probably put the wrong DTD in jbosscmp-jdbc.xml
I don't remember the details.
Make sure you have
<!DOCTYPE jbosscmp-jdbc PUBLIC
"-//JBoss//DTD JBOSSCMP-JDBC 3.2//EN"
(or its 3_0 equivalent).
I still have the same problem as lithous2 - also JBoss 3.2.5 seems to ignore the EJB's own DS directives, even with dtd:s updated to 3.2 (at least in jboss.xml and jbosscmp-jdbc.xml). Even the JNDI tree shows that the EJB properly links to MySqlDS, and the DS itself was deployed OK.
My workaround is indeed to change
in standardjaws.xml and standardjbosscmp-jdbc.xml to MySqlDS and mySQL .
There must be a better way due to the points (pilhuhn) mentioned, but googling shows that many use the same workaround...
Perhaps this is helpful for you:
When JBoss deploys an EJB jar file, the DOCTYPE of the ejb jar.xml deployment descriptor is used to determine the version of the EJB jar. If the public identifier of the DOCTYPE is " //Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN", JBoss will use the JBossCMP persistence engine, otherwise the old JAWS CMP 1.1 persistence engine will be used.
Upgrading my CMP version in the ejb-jar.xml was necessary. Not sure if that was all. I changed the CMP version and tried to deploy but it still appeared not to read in the jbosscmp-jdbc. Then I cleaned house on all the files to make sure all the CMP 2.0 necessary tags were there and changed my finder method declarations to query tags, etc. Deleted old files to make sure all would be fresh and then I got past that - the jbosscmp-jdbc.xml appears to be read in now.
Now my problem is with bcel. I have looked at the solutions on this forum and they don't seem to help me get past the bcel problem. I started another topic because it looks like different symptoms of the bcel problem. Though, I could be wrong.
Thanks for steering me in the right direction for CMP 2.x!