Yep, that'd work. Per-type converters might be simpler/fewer depending on the domain model, but registering a bunch of per-field local converters would certainly be the ultimate in flexibility.
It'd be interesting to know the exact use case. One of the nice things about working with whole aggregates rather than table-by-table is that it reduces the number of ordering dependencies you need to worry about when deserializing. But that may not matter in Sebastian's case. Jaime On Wed, Oct 17, 2012 at 3:40 PM, Jörg Schaible <joerg.schai...@scalaris.com>wrote: > > Jamie is the Hibernate expert, I am not using it. So my answer might be a > bit naive in the light of his experience. > > I would simply declare local converters for the fields with > the foreign key. These converters should write the id at serialization and > restore from it the object at deserialization. > > - Jörg > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
