Not sure. Need to think about that one some more.
The problem there is that Components have their mapping information
resolved differently from all other types. Its a long standing problem
in Hibernate that causes all kinds of issues.
On Mon 04 Jun 2012 11:17:44 AM CDT, Chris Pheby wrote:
Would it be possible to apply the pull request
From: Chris Pheby
Sent: 10 May 2012 10:29
To: 'Steve Ebersole'
Subject: RE: [hibernate-dev] Problem with Properties of Embeddable Classes and Type
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
From: Steve Ebersole [mailto:firstname.lastname@example.org] On Behalf Of Steve Ebersole
Sent: 01 May 2012 15:25
To: Chris Pheby
Subject: Re: [hibernate-dev] Problem with Properties of Embeddable Classes and Type
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 @
If you want to give solving the problem a go, have a look @
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
> Thanks Chris
> hibernate-dev mailing list
hibernate-dev mailing list