[Hibernate-JIRA] Created: (HHH-6938) Clarify the use of getHibernateConfiguration and Configuration handling with JPA bootstrap
3:49 a.m.
Clarify the use of getHibernateConfiguration and Configuration handling with JPA
bootstrap
------------------------------------------------------------------------------------------
Key: HHH-6938
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6938
Project: Hibernate Core
Issue Type: Task
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Hi,
I am willing to register custom types automatically when our application starts. We are
using JPA2 and the EntityManager.
To do so I can use a method on the Configuration object (registerTypeOverride). When
configuring the JPA container, the PersistenceProvider can be extended. That's what I
am doing but I came to this code (Ejb3Configuration on 3.6.5)
{code:java}
/**
* This API is intended to give a read-only configuration.
* It is sueful when working with SchemaExport or any Configuration based
* tool.
* DO NOT update configuration through it.
*/
public AnnotationConfiguration getHibernateConfiguration() {
//TODO make it really read only (maybe through proxying)
return cfg;
}
{code}
I believe there is a TODO here that may lead to a change that would disallow me to use the
configuration object to register new types on startup. If this TODO gets ever resolved
(why?), what could I do to register new types?
Thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:22 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6938) Clarify the use of getHibernateConfiguration and Configuration handling with JPA bootstrap
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6938?page=c...
]
Steve Ebersole commented on HHH-6938:
-------------------------------------
Not really following the purpose of this ticket. Is there some coding actually to be
done?
If you are just looking for an explanation, see below. However, JIRA is not the place to
ask user questions. Do that on the forums or on irc. I answered this time because it is
your first offense :)
The reason we say read-only is a matter of timing. Once the underlying {{SessionFactory}}
is built, changes made to that {{Configuration}} have no effect. Also, in general we do
not suggest applications using this {{org.hibernate.ejb.Ejb3Configuration}} class at all.
JPA defines a bootstrapping mechanism for both JSE and JEE uses. We are planning a better
approach to allow configuration stuff like you mentioned to happen in conjunction with
those standard bootstrapping methods. But thats still being planned. A likely approach
is through {{org.hibernate.integrator.spi.Integrator}}. Again, you have a vested interest
here, so maybe join the planning discussions for that.
Clarify the use of getHibernateConfiguration and Configuration
handling with JPA bootstrap
------------------------------------------------------------------------------------------
Key: HHH-6938
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6938
Project: Hibernate Core
Issue Type: Task
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Hi,
I am willing to register custom types automatically when our application starts. We are
using JPA2 and the EntityManager.
To do so I can use a method on the Configuration object (registerTypeOverride). When
configuring the JPA container, the PersistenceProvider can be extended. That's what I
am doing but I came to this code (Ejb3Configuration on 3.6.5)
{code:java}
/**
* This API is intended to give a read-only configuration.
* It is sueful when working with SchemaExport or any Configuration based
* tool.
* DO NOT update configuration through it.
*/
public AnnotationConfiguration getHibernateConfiguration() {
//TODO make it really read only (maybe through proxying)
return cfg;
}
{code}
I believe there is a TODO here that may lead to a change that would disallow me to use
the configuration object to register new types on startup. If this TODO gets ever resolved
(why?), what could I do to register new types?
Thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:27 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6938) Clarify the use of getHibernateConfiguration and Configuration handling with JPA bootstrap
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6938?page=c...
]
Stephane Nicoll commented on HHH-6938:
--------------------------------------
Hey Steve, thanks again for the response. I actually went through the redhat support and
since 3.6 is not supported, I could not get any response from them. I perfectly understand
the limitation of configuration and I agree with that. How about a constructor in
Ejb3Configuration taking a Configuration instance ?
If you look how Spring is starting the JPA container, it goes through that
PersistenceContext and currently that's the only way as far as I can see to touch the
Hibernate config before it starts.
And thanks for the pointers, I'll have a look.
As far as this issue, my apologies. I realized indeed it was more a question than an issue
itself. If there is an alternative to what I am currently doing with Spring bootstrap, I
am more than happy to change my code.
Clarify the use of getHibernateConfiguration and Configuration
handling with JPA bootstrap
------------------------------------------------------------------------------------------
Key: HHH-6938
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6938
Project: Hibernate Core
Issue Type: Task
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Hi,
I am willing to register custom types automatically when our application starts. We are
using JPA2 and the EntityManager.
To do so I can use a method on the Configuration object (registerTypeOverride). When
configuring the JPA container, the PersistenceProvider can be extended. That's what I
am doing but I came to this code (Ejb3Configuration on 3.6.5)
{code:java}
/**
* This API is intended to give a read-only configuration.
* It is sueful when working with SchemaExport or any Configuration based
* tool.
* DO NOT update configuration through it.
*/
public AnnotationConfiguration getHibernateConfiguration() {
//TODO make it really read only (maybe through proxying)
return cfg;
}
{code}
I believe there is a TODO here that may lead to a change that would disallow me to use
the configuration object to register new types on startup. If this TODO gets ever resolved
(why?), what could I do to register new types?
Thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:29 a.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HHH-6938) Clarify the use of getHibernateConfiguration and Configuration handling with JPA bootstrap
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6938?page=c...
]
Stephane Nicoll edited comment on HHH-6938 at 1/5/12 8:28 AM:
--------------------------------------------------------------
Hey Steve, thanks again for the response. I actually went through the redhat support and
since 3.6 is not supported, I could not get any response from them. I perfectly understand
the limitation of configuration and I agree with that. How about a constructor in
Ejb3Configuration taking a Configuration instance ?
If you look how Spring is starting the JPA container, it goes through that
PersistenceProvider and currently that's the only way as far as I can see to touch the
Hibernate config before it starts.
And thanks for the pointers, I'll have a look.
As far as this issue, my apologies. I realized indeed it was more a question than an issue
itself. If there is an alternative to what I am currently doing with Spring bootstrap, I
am more than happy to change my code (that is extending HibernatePersistence to change the
config before the entity manager factory gets created).
was (Author: snicoll):
Hey Steve, thanks again for the response. I actually went through the redhat support
and since 3.6 is not supported, I could not get any response from them. I perfectly
understand the limitation of configuration and I agree with that. How about a constructor
in Ejb3Configuration taking a Configuration instance ?
If you look how Spring is starting the JPA container, it goes through that
PersistenceContext and currently that's the only way as far as I can see to touch the
Hibernate config before it starts.
And thanks for the pointers, I'll have a look.
As far as this issue, my apologies. I realized indeed it was more a question than an issue
itself. If there is an alternative to what I am currently doing with Spring bootstrap, I
am more than happy to change my code.
Clarify the use of getHibernateConfiguration and Configuration
handling with JPA bootstrap
------------------------------------------------------------------------------------------
Key: HHH-6938
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6938
Project: Hibernate Core
Issue Type: Task
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Hi,
I am willing to register custom types automatically when our application starts. We are
using JPA2 and the EntityManager.
To do so I can use a method on the Configuration object (registerTypeOverride). When
configuring the JPA container, the PersistenceProvider can be extended. That's what I
am doing but I came to this code (Ejb3Configuration on 3.6.5)
{code:java}
/**
* This API is intended to give a read-only configuration.
* It is sueful when working with SchemaExport or any Configuration based
* tool.
* DO NOT update configuration through it.
*/
public AnnotationConfiguration getHibernateConfiguration() {
//TODO make it really read only (maybe through proxying)
return cfg;
}
{code}
I believe there is a TODO here that may lead to a change that would disallow me to use
the configuration object to register new types on startup. If this TODO gets ever resolved
(why?), what could I do to register new types?
Thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:37 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6938) Clarify the use of getHibernateConfiguration and Configuration handling with JPA bootstrap
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6938?page=c...
]
Steve Ebersole commented on HHH-6938:
-------------------------------------
No idea what spring does or does not do so I unfortunately cannot help there.
As for the Hibernate side of things, I think that in 3.6 what you are doing is exactly
what you would need to do. The bright side of us not developing 3.6 anymore is that you
in fact do not have to worry about that code changing :D
Clarify the use of getHibernateConfiguration and Configuration
handling with JPA bootstrap
------------------------------------------------------------------------------------------
Key: HHH-6938
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6938
Project: Hibernate Core
Issue Type: Task
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Hi,
I am willing to register custom types automatically when our application starts. We are
using JPA2 and the EntityManager.
To do so I can use a method on the Configuration object (registerTypeOverride). When
configuring the JPA container, the PersistenceProvider can be extended. That's what I
am doing but I came to this code (Ejb3Configuration on 3.6.5)
{code:java}
/**
* This API is intended to give a read-only configuration.
* It is sueful when working with SchemaExport or any Configuration based
* tool.
* DO NOT update configuration through it.
*/
public AnnotationConfiguration getHibernateConfiguration() {
//TODO make it really read only (maybe through proxying)
return cfg;
}
{code}
I believe there is a TODO here that may lead to a change that would disallow me to use
the configuration object to register new types on startup. If this TODO gets ever resolved
(why?), what could I do to register new types?
Thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:37 a.m.
New subject: [Hibernate-JIRA] Closed: (HHH-6938) Clarify the use of getHibernateConfiguration and Configuration handling with JPA bootstrap
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6938?page=c...
]
Steve Ebersole closed HHH-6938.
-------------------------------
Resolution: Rejected
Clarify the use of getHibernateConfiguration and Configuration
handling with JPA bootstrap
------------------------------------------------------------------------------------------
Key: HHH-6938
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6938
Project: Hibernate Core
Issue Type: Task
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Hi,
I am willing to register custom types automatically when our application starts. We are
using JPA2 and the EntityManager.
To do so I can use a method on the Configuration object (registerTypeOverride). When
configuring the JPA container, the PersistenceProvider can be extended. That's what I
am doing but I came to this code (Ejb3Configuration on 3.6.5)
{code:java}
/**
* This API is intended to give a read-only configuration.
* It is sueful when working with SchemaExport or any Configuration based
* tool.
* DO NOT update configuration through it.
*/
public AnnotationConfiguration getHibernateConfiguration() {
//TODO make it really read only (maybe through proxying)
return cfg;
}
{code}
I believe there is a TODO here that may lead to a change that would disallow me to use
the configuration object to register new types on startup. If this TODO gets ever resolved
(why?), what could I do to register new types?
Thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:41 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6938) Clarify the use of getHibernateConfiguration and Configuration handling with JPA bootstrap
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6938?page=c...
]
Stephane Nicoll commented on HHH-6938:
--------------------------------------
okay, thanks ! :)
Clarify the use of getHibernateConfiguration and Configuration
handling with JPA bootstrap
------------------------------------------------------------------------------------------
Key: HHH-6938
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6938
Project: Hibernate Core
Issue Type: Task
Affects Versions: 3.6.5
Reporter: Stephane Nicoll
Hi,
I am willing to register custom types automatically when our application starts. We are
using JPA2 and the EntityManager.
To do so I can use a method on the Configuration object (registerTypeOverride). When
configuring the JPA container, the PersistenceProvider can be extended. That's what I
am doing but I came to this code (Ejb3Configuration on 3.6.5)
{code:java}
/**
* This API is intended to give a read-only configuration.
* It is sueful when working with SchemaExport or any Configuration based
* tool.
* DO NOT update configuration through it.
*/
public AnnotationConfiguration getHibernateConfiguration() {
//TODO make it really read only (maybe through proxying)
return cfg;
}
{code}
I believe there is a TODO here that may lead to a change that would disallow me to use
the configuration object to register new types on startup. If this TODO gets ever resolved
(why?), what could I do to register new types?
Thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4523
days inactive
4523
days old
hibernate-issues@lists.jboss.org
6 comments
2 participants
participants (2)
-
Stephane Nicoll (JIRA) -
Steve Ebersole (JIRA)