5:30 a.m.
Support SpringJPAConfiguration
------------------------------
Key: HBX-1086
URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1086
Project: Hibernate Tools
Issue Type: New Feature
Components: ant
Affects Versions: 3.2.0.GA
Reporter: John Turner
I'm working on a module based approach to developing a persistence layer for a web
application.
One of the things I want to be able to do is deploy each module in its own jar file with a
corresponding persistence.xml file. Having done this spring's PersistenceUnitManager
detects the persistence.xml files at runtime and merges the persistence configuration
files into a single persistence configuration.
Problem is, at build time, I use hibernate tools and jpa configuration to build drop and
create schema ddl. This just picks up the first persistence.xml on the classpath and uses
it to provide the jpa configuration. I would like to see a SpringJPAConfiguration that
operates in the same way as the PersistenceUnitManager.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:45 a.m.
New subject: [Hibernate-JIRA] Commented: (HBX-1086) Support SpringJPAConfiguration
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-1086?page=c...
]
Max Rydahl Andersen commented on HBX-1086:
------------------------------------------
interesting - which of the persistence.xml files should we listen to when it comes to
connection info ?
Support SpringJPAConfiguration
------------------------------
Key: HBX-1086
URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1086
Project: Hibernate Tools
Issue Type: New Feature
Components: ant
Affects Versions: 3.2.0.GA
Reporter: John Turner
I'm working on a module based approach to developing a persistence layer for a web
application.
One of the things I want to be able to do is deploy each module in its own jar file with
a corresponding persistence.xml file. Having done this spring's
PersistenceUnitManager detects the persistence.xml files at runtime and merges the
persistence configuration files into a single persistence configuration.
Problem is, at build time, I use hibernate tools and jpa configuration to build drop and
create schema ddl. This just picks up the first persistence.xml on the classpath and uses
it to provide the jpa configuration. I would like to see a SpringJPAConfiguration that
operates in the same way as the PersistenceUnitManager.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:57 a.m.
New subject: [Hibernate-JIRA] Commented: (HBX-1086) Support SpringJPAConfiguration
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-1086?page=c...
]
John Turner commented on HBX-1086:
----------------------------------
I've looked into this a bit more and the PersistenceUnitManager does not do exactly
what I thought it did. I might follow this up with Spring though.
For the project I am working on, the ideal scenario would be this.
HibernateTools loads all persistence.xml from the classpath and executes hbm2ddl on the
specified persistent unit. If multiple persistent units of the same name exist, the class
list, mapping file list etc. could be merged. I know what you are saying re the
connection info but the hibernate tools would be used at build time with no need to
connect to database (open to correction here).
At suntime, spring can inject the datasource into the entitymanagerfactory or
PersistenceUnitManager in this case and so no connection information exists in the
persistence.xml. Spring can also inject the dialect etc.
I'm sure some of the specifics would need a bit of work, but the idea is sound. End
result would be that by dropping a jar with a persistence.xml, entity classes etc. into an
ear, spring will automatically load the configuration and merge into the persistent unit.
I might not be explaining myself very well but I hope this makes a bit of sense?
Support SpringJPAConfiguration
------------------------------
Key: HBX-1086
URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1086
Project: Hibernate Tools
Issue Type: New Feature
Components: ant
Affects Versions: 3.2.0.GA
Reporter: John Turner
I'm working on a module based approach to developing a persistence layer for a web
application.
One of the things I want to be able to do is deploy each module in its own jar file with
a corresponding persistence.xml file. Having done this spring's
PersistenceUnitManager detects the persistence.xml files at runtime and merges the
persistence configuration files into a single persistence configuration.
Problem is, at build time, I use hibernate tools and jpa configuration to build drop and
create schema ddl. This just picks up the first persistence.xml on the classpath and uses
it to provide the jpa configuration. I would like to see a SpringJPAConfiguration that
operates in the same way as the PersistenceUnitManager.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:45 a.m.
New subject: [Hibernate-JIRA] Commented: (HBX-1086) Support SpringJPAConfiguration
[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-1086?page=c...
]
Max Rydahl Andersen commented on HBX-1086:
------------------------------------------
Well, hibernatetools *does* need to connect to the database when you either are reverse
engineering from it or executing queries.
I'm very much open for making it easier to use so any ideas in form of patches would
be welcome.
One thing I definitly need to do is to improve the jpaconfiguration option to not have to
require persistence.xml to be located in a specific location.
But "merging" persistence units just feels "wrong" ...they are no
longer a unit then...
Support SpringJPAConfiguration
------------------------------
Key: HBX-1086
URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1086
Project: Hibernate Tools
Issue Type: New Feature
Components: ant
Affects Versions: 3.2.0.GA
Reporter: John Turner
I'm working on a module based approach to developing a persistence layer for a web
application.
One of the things I want to be able to do is deploy each module in its own jar file with
a corresponding persistence.xml file. Having done this spring's
PersistenceUnitManager detects the persistence.xml files at runtime and merges the
persistence configuration files into a single persistence configuration.
Problem is, at build time, I use hibernate tools and jpa configuration to build drop and
create schema ddl. This just picks up the first persistence.xml on the classpath and uses
it to provide the jpa configuration. I would like to see a SpringJPAConfiguration that
operates in the same way as the PersistenceUnitManager.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5950
days inactive
5959
days old
hibernate-issues@lists.jboss.org
3 comments
2 participants
participants (2)
-
John Turner (JIRA) -
Max Rydahl Andersen (JIRA)