Thank you for the reply! We are using Hibernate persisted objects between application tiers (detach, serialize to other tier, other tier eventually sends changed objects back, etc). However, we are also trying to develop a solution where we don't have to retransmit the entire graph every time. This is complicated by the fact that the model (graph) mutates on save/update (on saves, the id is assigned, on updates, the version is changed) and so we have to keep these mutations in sync between tiers. Some applications can get away with the "load entire graph, let user make mods, save entire graph back to server - if user wants to continue editing, then reload entire graph from server" cycle, but that is not a workable option for us at the moment. We are now using an enterprise event system (ESB basically) whereby changes are transmitted live to other listening parties, thus keeping the tiers in sync. We just need to know the mechanics of when Hibernate mutates our objects so that we can properly sync those mutations with other tiers via the ESB.
Thanks!
|