[hibernate-dev] Problem with Properties of Embeddable Classes and Type Registry
chris at jadira.co.uk
Wed May 9 22:28:32 EDT 2012
Thanks for your reply. I decided to dig deeper and find the fix.
The problem is that the type is being cached inside the Component class.
I created the Jira issue at https://hibernate.onjira.com/browse/HHH-7310
I also created a pull request for a test and the fix at https://github.com/hibernate/hibernate-orm/pull/335
From: Steve Ebersole [mailto:steven.ebersole at gmail.com] On Behalf Of Steve Ebersole
Sent: 01 May 2012 15:25
To: Chris Pheby
Cc: hibernate-dev at lists.jboss.org
Subject: Re: [hibernate-dev] Problem with Properties of Embeddable Classes and Type Registry
That is not the expected behavior. Myabe just an oversight in how components (embeddables) are handled? If that is the behavior you see, I would consider that a bug. Please create a JIRA and attach a test case as outlined @ http://hibernate.org/issuetracker
If you want to give solving the problem a go, have a look @ https://github.com/hibernate/hibernate-orm/wiki/Contributing-Code
On Tue 01 May 2012 05:02:07 AM CDT, Chris Pheby wrote:
> The new type registry capability in Hibernate 4 and above is really useful. I have implemented an integrator that autoregisters some types, however what I have found is that whilst this works perfectly, the registered types are not being resolved correctly when they are used within @Embeddable classes.
> Is this the expected behaviour?
> I have tried debugging through the sources and it looks like the SessionFactory's TypeResolver is not used in the case of properties of such classes. See the comments at http://blog.jadira.co.uk/blog/2012/1/19/release-jadira-usertype-300cr1-with-support-for-joda-money-0.html#comments.
> Thanks Chris
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
steve at hibernate.org
More information about the hibernate-dev