[ https://issues.jboss.org/browse/WFLY-1186?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-1186: ------------------------------------ I agree, that for the Hibernate (or any persistence provider) JPA 2.1 database migration support, the database user account used, would need permissions to execute DDL. I think there are probably multiple ways we could handle deployment time callbacks for database migration. One strategy might be to let an application level class be invoked (at deployment time, before the persistence unit is created). This would be pretty much following your original suggestion (either via extension annotation or a persistence unit property). The callback could probably use the JPA 2.1 database migration api or something custom like FlyWayDB (perhaps even using http://schemacrawler.sourceforge.net) that verify the schema. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira