This is partly a helpful message for people who walk into this problem in the future and partly a feature request.

If you define a field-name in your entity bean that is a reserved word in the data base you are using, jboss will not recognise this and you will get a syntax error when jboss attempts to create the table in your data base.

This can be even more confusing as different databases have different reserved words and what might work in one will not work in another.

The solution for now is to avoid using reserved words as field names, perhaps at some point in the future JBoss will recognise reserved words for a given database and automatically handle this problem in the background with out the user having to know.