[
https://issues.jboss.org/browse/WFLY-1186?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on WFLY-1186:
------------------------------------
[~anilarora], the JPA 2.1 specifications outline the new capabilities that will be in
every JPA 2.1 persistence provider implementation (e.g. Hibernate 4.3.0).
There is a JPA 2.1 way to generate scripts but also to specify the name of a DDL/DML SQL
script to be executed.
Exactly, how your/others needs are addressed by the JPA 2.1 specification, is open at this
point. If you want to get involved with *scratching* your "database migration"
itch, using the new JPA 2.1 specification features, that would be great.
Create JPA service callback for invoking database migration
-----------------------------------------------------------
Key: WFLY-1186
URL:
https://issues.jboss.org/browse/WFLY-1186
Project: WildFly
Issue Type: Feature Request
Components: JPA / Hibernate
Reporter: Anil Arora
Assignee: Scott Marlow
Looking for a simple callback/listener mechanism so that we can invoke a database
migration script before JPA persistent unit starts up and runs the Hibernate schema
validation mechanism.
Ideally, there would be a property within the persistence.xml that indicates which class
to call. It would also pass in/inject the datasource that is being used for the
persistence unit.
Essentially, this would solve the lack of migration support in Hibernate itself.
--
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