This content has been marked as final. Show 2 replies
I tried adding a jbosscmp-jdbc.xml descriptor to the CMP EJBs with just
a default defined:
<jbosscmp-jdbc> <defaults> <datasource>java:/SonusSMSDS</datasource> </defaults> </jbosscmp-jdbc>
This seems to have fixed the problem. Is this what has to be done in
JBoss 3.2.x, even though I'm using 1.1 CMP EJBs ?
The reason the data source couldn't be found is because we are using
a custom DeploymentSorter which was used in 3.0.7; this class didn't
recognize the new ds.xml suffix, so data sources were being deployed
So the question still remains, do I need to have both jaws.xml and
jbosscmp-jdbc.xml present for 1.1 CMP EJBs in JBoss 3.2 ? Or is there
a better way to do this (less deployment descriptors).
Yes, because in 3.2.6 JBossCMP is the default CMP engine for all CMP specs.
<container-configuration> <container-name>Standard CMP EntityBean</container-name> ... <persistence-manager>org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager</persistence-manager> <!-- <persistence-manager>org.jboss.ejb.plugins.jaws.JAWSPersistenceManager</persistence-manager>--> ...
If you want to use JAWS, switch back to JAWS persistence manager.