URGENT, Please help

[divine_comedy]

We just upgraded to 3.0.4. Managed to get all our entity beans (1.1) working. I am currently experimenting with converting some ( actually just 1 ) of our entity beans to 2.0, but encountered the following :
WARN [JawsApplicationMetaData] Warning: data found in jaws.xml for entity xxx but bean is not a jaws-managed cmp entity in ejb-jar.xml

The stupid thing is that not all our entity beans (1.1) complained, it's just some.

Has somebody encountered this before ? I took a look at the difference between ones that deploy and those that do not and simply could not figure it out.

Setup :
I took out the lonesome 2.x entity bean from jaws.xml to jbosscmp-jdbc.xml, and made some addition to ejb-jar.xml as required. I also marked the cmp-version correctly ( 1.x or 2.x ).

[divine_comedy]

OK I think this is a bug in JBoss, but I could be wrong.

I created a deployment unit for that one CMP 2.0 bean ( its own ejb-jar, jbosscmp-jdbc, and jboss )
and everything works like a charm.

My question then is : what's the use of the <cmp-version> tag ? My assumption ( and a possibly wrong one at that ) was that the tag would help JBoss to determine whether to use jaws or jbosscmp-jdbc

[juhalindfors]

Do you have the correct DTD declaration at the beginning of your 1.1 CMP entities?