I can imagine that when you modify 1'000s of nodes (say in a batch) you win quite some time when you don't save each node "per se" but in the end just tell the session to persist all its pending changes. Just a guess though...
-----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Justin Edelson Gesendet: Dienstag, 16. November 2010 19:32 An: [email protected] Betreff: Re: software engineering question FWIW, this is actually a spec question, not a Jackrabbit question. Justin On Tue, Nov 16, 2010 at 1:11 PM, ChadDavis <[email protected]> wrote: > I'm curious as to the design motivations behind some of the Jackrabbit > code. I'm not questioning these choices. I'm actually trying to > learn from them. In particular, I'm interested in the motivations > that lead to the deprecation of node.save() in favor of > session.save(). Any insight would be appreciated. Thanks! >
