You will also likely need a jboss-ejb3.xml file (which replaces the old jboss.xml file).
But developing CMP entity beans instead of using JPA is certainly not "best practice" in any sense as it requires a much higher degree of technical knowledge (amongst other things).
I can see lot of difference EJB2.0, EJB3.0 Entity beans, In EJB3.0 each Entity bean is required one stateless session bean. EJB3.0 is good for new implementation projects because EJB configuration files are avoid in this release. Entity beans are deprecated in this release. Server migration is also flexible in future with EJB3.0.
I feel, EJB migration not good, when work on server migration projects until forcibly EJB migration is required because code has to be updated and plenty unit testing is required and JPA knowledge is required.
Hope I am sync with you.
So you are really migrating an existing application, rather than developing something new?
If so, from which server implementation are you migrating?
Yes, it is existing application.
How many CMP entity beans do you have?
I know from past experience that migrating CMP between vendors can be challenging to say the least.
Are they marked up with xdoclet by any chance? That would make it easier.
Not used xdoclets.
How complicated is/are your weblogic-cmp-jar.xml file/s? The content of this would need to be converted/translated to corresponding jbosscmp-jdbc.xml (schema available at https://github.com/jbossas/jboss-as/blob/master/cmp/src/main/resources/standardjbosscmp-jdbc.xml).
Do you need 100% compatibility with your existing database?
Yes 100% is required.
Our CMP's are completly mapped to DB.Even AUTO key generation and table relalation.