Request: Custom Serialization for Specific Types about salat HOT 2 OPEN

Hi Andy,

I believe what you actually want to do here is break apart an object graph for persistence into separate collections?

I would suggest doing this instead using a parent id that references the top level object in the children, and then use SalatDAO with ChildCollection to break apart the object when you persist it and re-assemble it when you deserialize it. See the salat specs on the dao and child collections in salat-core.

I don't plan to support passing in a custom serializer as you propose at present (leaving aside the problem that custom serialization and deserialization must be paired or deserialization will fail), although future versions might allow you to define custom transformations for global types (like, say, java.net.URI).

from salat.

Hi Rose,

Thanks you, I've just adapt my model to use what you told me. Which works pretty well indead.

But still that it would be interesting to have such back and forth marshalling to handle objects graph splitted into several collections.

'Cause now, I've introduced some ObjectId as parameter of my case class, with lazy val that retrieves the orignial object. That fits the need but polute a little bit the model? Don't you think?

However, couldn't we have special behavior for ObjectId, Collection of ObjectId and Map valued by ObjectId fields ? By using an annotation for instance (I'm writing while thinking, sorry if it's dumb) like the following

case class Person(name:String, @listref[AddressDAO, "_id"] addresses:List[Address]) {}

This will store the _id of addresses as a mondgo db list.

Just my 0.02c

from salat.