BTW, node.save() still works in Jackrabbit 2.x.
Regards,
Alex
--
Alexander Klimetschek
Developer // Adobe (Day) // Berlin - Basel
On 16.11.10 19:11, "ChadDavis" 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 favo
Hi,
From: ChadDavis [mailto:chadmichaelda...@gmail.com]
> 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 o
tinedel...@gmail.com [mailto:justinedel...@gmail.com] Im Auftrag von
Justin Edelson
Gesendet: Dienstag, 16. November 2010 19:32
An: users@jackrabbit.apache.org
Betreff: Re: software engineering question
FWIW, this is actually a spec question, not a Jackrabbit question.
Justin
On Tue, Nov 16, 2010 a
FWIW, this is actually a spec question, not a Jackrabbit question.
Justin
On Tue, Nov 16, 2010 at 1:11 PM, ChadDavis 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 particul
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 a
