[ https://issues.jboss.org/browse/JBRULES-3318?page=com.atlassian.jira.plug... ] Geoffrey De Smet edited comment on JBRULES-3318 at 7/18/12 3:18 AM: -------------------------------------------------------------------- You might not want to use "xml-mapping-metadata-complete", as you don't want to disable all annotations in code. For example, disabling @Temporal(TemporalType.TIMESTAMP) and requiring them to rewrite it, is unnecessary duplication (and prone to bugs, especially when it changes in a new version). If all they want to do is change the table names (not the column names), it could be just a list of @Table(tableName) overrides in the orm.xml file. was (Author: ge0ffrey): From my experience, the META-INF/orm.xml is indeed the way to do it: it can override any annotation in the code. Problem is they have to put it in the drools/jbpm-persistence-jpa.jar file AFAIK, so that's a PITA when upgrading to a new drools/jbpm version. You might not want to use "xml-mapping-metadata-complete", as you don't want to disable all annotations in code. For example, disabling @Temporal(TemporalType.TIMESTAMP) and requiring them to rewrite it, is unnecessary duplication. If all they want to do is change the table names (not the column names), it could be just a list of @Table(tableName) overrides in the orm.xml file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira