Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 71048 invoked from network); 17 May 2010 09:09:43 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 17 May 2010 09:09:43 -0000 Received: (qmail 68100 invoked by uid 500); 17 May 2010 09:09:40 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 67501 invoked by uid 500); 17 May 2010 09:09:38 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 67494 invoked by uid 99); 17 May 2010 09:09:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 May 2010 09:09:38 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of stefan.guggisberg@gmail.com designates 209.85.161.42 as permitted sender) Received: from [209.85.161.42] (HELO mail-fx0-f42.google.com) (209.85.161.42) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 May 2010 09:09:31 +0000 Received: by fxm2 with SMTP id 2so1165736fxm.1 for ; Mon, 17 May 2010 02:09:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; bh=W3tV3AOaecGmRx1xhtBCli2YHAMWiXKbCCS9CWLhVSc=; b=e8vTIQKGpnCVcHO26De+gORpP2O/MSk02rQobPZM5kxB0rJhWj9hpe0Sjofs2F5LBv wBQzBc2v4LB7DHdPHFjOlEEXZGin/Dq75wXgm4dYZWeEC9WNmEfgSrWr+ZTVAVAVXnis JqyiJ3qc9UhFswD0f4/4E9HsSqqhoOhNKRmxk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=EzLXuKTLTsujMwx0af8EBcfmbPbJnrjvS8p7SwR+DwmnsL38sTsFghcZP+7pPnUnq4 l4paThTzgD0dQw2NnN1cGBrSetTBwWv+htVU350U0S8XMudWA5Hr/JXDPCvx7U1uh6Z6 rVhlHT2qTZDxQvVFHS0sEmFMGCjPXzITtj35M= MIME-Version: 1.0 Received: by 10.223.5.13 with SMTP id 13mr5897047fat.68.1274087351049; Mon, 17 May 2010 02:09:11 -0700 (PDT) Sender: stefan.guggisberg@gmail.com Received: by 10.223.121.207 with HTTP; Mon, 17 May 2010 02:09:10 -0700 (PDT) In-Reply-To: References: Date: Mon, 17 May 2010 11:09:10 +0200 X-Google-Sender-Auth: N3bx0e5F2vdV4G4WVHhQPucQ2I0 Message-ID: Subject: Re: FYI: Moving session-related classes to o.a.j.core.session From: Stefan Guggisberg To: dev@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Mon, May 17, 2010 at 11:00 AM, Thomas M=FCller = wrote: > Hi, > > I'm not sure if this will help more than it will complicate things. > Disadvantages: > > - Isn't almost every class at in o.a.j.core at least somewhat session rel= ated? > > - If you move classes to other packages, you will have to make many > method public. i share tomas's concerns. > > Instead of moving session related classes to a separate package, what > about moving unrelated classes to different packages? For example > TestContentLoader (>test), RepositoryCopier (>utilities), > SearchManager (>search), NodeTypeInstanceHandler (>nodetype), > RepositoryChecker (>persistence), UserPerWorkspaceSecurityManager > (>security), DefaultSecurityManager (>security), ItemValidator > (>nodetype). +1 cheers stefan > > Regards, > Thomas > > > On Mon, May 17, 2010 at 10:43 AM, Jukka Zitting = wrote: >> Hi, >> >> As a part of my work on JCR-890, I'm planning to move most of the >> session-related classes from o.a.j.core to a new o.a.j.core.session >> package. This will make it easier to review and control related >> dependencies and code paths, and to ultimately guard them against >> access from concurrent threads. >> >> As the first step I'm simply moving the relevant classes and making >> the minor dependency changes where needed, so the functional risk >> should be low. However, the moves will likely invalidate many other >> pending jackrabbit-core changes, so please let me know if you have >> pending changes that I should wait for before I move these classes. >> Unless there's a need to wait, I'm planning to commit the changes in >> the afternoon today. >> >> BR, >> >> Jukka Zitting >> >