It is a hibernate issue. The reveng.xml is from Hibernate Tools, and it isn't used to store mappings either.
The answer is that hibernate-tools isn't perfect, and sometimes makes mistakes (like this) which you have to correct by hand. If you come across such a problem you need to (1) fix it in your app, (2) report it in the hibernate tools forum so they can add it to the mapping files which come with hibernate tools.
You can also ask about reveng.xml on the hibernate tools forum.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114578#4114578
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114578
Ok, I've been trying to reproduce this behaviour for the past 3 hours! I've managed to find the concrete circumstances of when this happens. It's weird:
What works: create a connection profile with correct settings. Start the seam project wizard and select that connection profile. No problem at all.
What is broken: edit an existing connection profile and make a change to its settings (e.g. the JDBC connection URL). Start the seam project wizard and you'll see that the "Driver Class" error occurs.
I'm filing bug reports for this and the typo right now.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114577#4114577
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114577