I'm upgrading an application from jboss 3.2.5 to jboss 4.2. One of the problems I'm having is that the cmp enitity beans are not being loaded from the tables as defined in META-INF/jaws.xml file within the ejb.jar that is deployed in the ear file. This was working in jboss 3.2.5. I can see from the server.log file that the bean is being loaded with a sql statement that selects from fields and table name that are the same as the cmp-feild names and ejb name - instead of the column-names and table-name defined in the jaws.xml. Inside jaws.xml, I do see that the type-mapping value is "MS SQLSERVER" eventhough the application uses oracle; however, this worked with jboss 3.2.5. I'm not sure how important this type-mapping element is and I don't know what to change it to anyway. Here's is an exceprt from the jaws.xml:
Joined: Jun 18, 2009
According to Redhat, jaws.xml is not supported. So I used jbosscmp-jdbc.xml instead. Everything is working fine now. There is much, much work migrating the information in jaws.xml to jbosscmp-jdbc.xml.