On 23/09/2015 5:57am, Andrus Adamchik wrote:
> // optionally can take a changeset serialized to JSON
> @PostCommit
> void processAsJSON(Map<ObjectId, String> map) {..}
Why would you perform this serialisation for the user and not just supply a
piece of sample code to put into the listener. Yes, json is the flavour of the
day, but some people will want separate bits of json for every object, others
will want to try and assemble the whole commit tree into one json string,
others will want to do something else. Why would Cayenne itself have an opinion
on this format?
There are very few other places where Cayenne specifies the data format,
Hessian being the only one I can think of.
My other question is about what objects will be found in the change set. Right
now, if you modify an object, listeners can be fired on objects at the other
end of its relations, even if no FK or other changes will be made in the
database to those other objects. Do you anticipate the change set in the audit
will include these kinds of related records, or only ones where a database
attribute change is made?
This is a very nice feature for Cayenne
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
