-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hibernate4Module causes Type Erasure #81
Comments
I would need a reproduction of this (ideally unit test); above is not enough to trigger the issue. |
Let me know if this is enough:
Without Hibernate4Module the serialized value looks like this:
but with the Hibernate4Module it is:
Excerpt from pom.xml: (note I have tried with using the same version 2.6.1 for all of them and the issues is still here)
|
@agorina Thank you -- I'll have a look; should be enough. I will use consistent version for all components for testing. |
Ok, yes, I can reproduce the issue. |
Looks like type handler was not being passed properly; needed rather sizable changes so can only be done for 2.7. Will be included in 2.7.0 when it is released soon. |
Thank you! Could you please let me know the estimated timeline for 2.7.0 release? |
Within 2 weeks, mid-january or earlier. |
Thank you for a prompt response. |
I have an object that contains the following object that in turn has a collection of polymorphic objects.
Without registering Hibernate4Module, I am able to serialize/deserialize the parent object with all its children.
Calling registerModule with Hibernate4Module causes the failure.
When I examine the difference, I can see that with Hibernate4Module being registered, the serialized object is missing @type for objects within RecordFilter.
The text was updated successfully, but these errors were encountered: