You still need to edit the JBoss' config file to use the newly added service.
For this step you will need to modify one of JBoss' config files. The file we are looking for is:
%your JBoss dir%\server\default\conf\standardjbosscmp-jdbc.xml
Once you have located this file, open the file in a simple text editor and edit the following lines of code:
Replace "DefaultDS" with the JNDI name given in the mssql-service.xml file. And replace "Hypersonic SQL" with the mapping required (i.e. "MS SQLSERVER" or "MS SQLSERVER2000").
Hope this helps,
I am using PostgreSQL 7.1.3 with jboss 3.0.1 (not RC).
I had problems to bound to my own datasource other than DefaultDS. The problem was that jboss always looks for DefaultDS even I changed standardjbosscmp-jdbc.xml as you did. I tried many ways to solve the problems, including removing hsqldb-service.xml off from the deploy directory to avoid confusion. Finally, I found the cause of the problem. I had to modify standardjaws.xml. Why?
After I modify the datasource and its mapping to my own datasource and PostgreSQL, respectively, on the standardjaws.xml file. I then can connect to my PostgreSQL datasource other than Hypersonic SQL.
Your ejb-jar.xml dtd identifies it as ejb 1.1. Use the 2.0 dtd to use the cmp2 persistence engine. Ask more questions on the persistence forum.
I am not using ejb 1.1 but 2.0 dtd. However, the problem was gone forever without knowing where it came and went.