Adjusted the XStream security permissions to allow references.
Hibernate.enable_lazy_load_no_trans true in in hibernate.cfg file. We are not using Annotation in our projects, only hbm file mappings
Question: What could be causing the ConversionException during the deserialization process, and how can I resolve this issue? Are there specific configuration changes required in XStream or Hibernate for managing collections and references?
Additional Information: If there are any known bugs or incompatibilities between Hibernate and XStream that could trigger this error, any insight would be appreciated.
You should better ask the maintainers of XStream about this since you’re experiencing an exception thrown by that library. Hibernate ORM doesn’t “support” integration with that library, so this community most likely won’t be able to help you.
I am encountering an issue with ORM while loading a subset in Hibernate 6.5.2 migration. Lazy loading is not functioning as expected, despite configuring everything properly. The problem arises after the DAO object loads with values for the set and subset, where XStream comes into play after loading objects from DAO select query.
We would like assistance with the necessary configuration to resolve this issue.
@beikov please check if you can support here -
Here I am getting some extra field like org.hibernate.collection.spi.PersistentSet
isTempSession
initialized
cachedSize
role
key
dirty
elementRemoved
storedSnapshot
Please try to create a reproducer with our test case template and if you are able to reproduce the issue, create a bug ticket in our issue tracker and attach that reproducer.