Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (asf.osuosl.org: domain of pittet@gmail.com designates
 64.233.184.238 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=qxH18UNjtDFj4Q9yHh22nNJFK5a7SNd55aFpDLu5cH6LcuRlC1K5UDRGR5It2NrZwCacVmWYExsAB3FhJvaGBup6fQdtKd5wpqSsWL34wOKJwP9r7JrVK1vDue5TkbwJGkSvj597HjSp3mAwIu4/h+WHnHF0gtHnMsZqXEJ7q5g=
Message-ID: <309be0990610170746x1445b22v7836aa0a644c9675@mail.gmail.com>
Date: Tue, 17 Oct 2006 16:46:28 +0200
From: "Jean-Michel Pittet" <jmp@day.com>
Sender: pittet@gmail.com
To: dev@jackrabbit.apache.org, tobias.bocanegra@day.com
Subject: Re: refactoring the persistence managers
Cc: "Hans Juerg Lips" <hansjuerg.lips@day.com>
In-Reply-To: <8be731880610170636tee6eeb6t9db767b8e9851df@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <8be731880610170636tee6eeb6t9db767b8e9851df@mail.gmail.com>

what is the impact of for the existing connectors? WIll it impact
configuration i.e. moving from current to your proposed model in an
upgrade?

Cheers
JM

On 10/17/06, Tobias Bocanegra <tobias.bocanegra@day.com> wrote:
> hi,
> currently the persistence managers reside in:
>  org.apache.jackrabbit.core.state
>  org.apache.jackrabbit.core.state.db
>  org.apache.jackrabbit.core.state.mem
>  org.apache.jackrabbit.core.state.obj
>  org.apache.jackrabbit.core.state.xml
>  (org.apache.jackrabbit.core.state.util)
>
> there are also a lot of other classes that deal with states (eg:
> SharedItemStateManager) in the state package that do not relate to
> pms.
>
> i would like to move all persistencemanagers and pm related stuff to:
>
>  org.apache.jackrabbit.core.persistence
>
> and drop the 'db', 'mem', 'obj', 'xml' sub-packages.
>
> because the configurations in the workspaces use fully qualified class
> names, i would put legacy classes in the old places that extend the
> new ones and put them into some sort of compat.jar. or we could
> introduce a more general class-mapping in the configuration that mapps
> FQN to classes (which i prefer).
>
> opinions?
>
> btw: as soon there is more response/consensus on this issue, i will
> create a proper jira issue and suggest a patch.
>
> regards, toby
> --
> -----------------------------------------< tobias.bocanegra@day.com >---
> Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
> T +41 61 226 98 98, F +41 61 226 98 97
> -----------------------------------------------< http://www.day.com >---
>


-- 
Cheers
Jean-Michel

----------------------------------------------------------------------
standardize your content-repository !          http://jcr.day.com
-------------------------------------< jean-michel.pittet@day.com >---

This message is a private communication. If you are not the intended
recipient, please do not read, copy, or use it, and do not disclose it
to others. Please notify the sender of the delivery error by replying
to this message, and then delete it from your system. Thank you.

The sender does not assume any liability for timely, trouble free,
complete, virus free, secure, error free or uninterrupted arrival of
this e-mail. For verification please request a hard copy version.

----------------------------------------------------------------------
Jean-Michel Pittet - Senior Vice President of Engineering
Day, +41 61 226 98 98,  PF, CH-4001 Basel