From users-return-11999-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org Tue Jul 21 16:13:04 2009 Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 2309 invoked from network); 21 Jul 2009 16:13:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 Jul 2009 16:13:04 -0000 Received: (qmail 74643 invoked by uid 500); 21 Jul 2009 16:14:09 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 74622 invoked by uid 500); 21 Jul 2009 16:14:09 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 74584 invoked by uid 99); 21 Jul 2009 16:14:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jul 2009 16:14:09 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of aklimets@day.com designates 207.126.148.181 as permitted sender) Received: from [207.126.148.181] (HELO eu3sys201aog001.obsmtp.com) (207.126.148.181) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 21 Jul 2009 16:13:59 +0000 Received: from source ([74.125.78.147]) by eu3sys201aob001.postini.com ([207.126.154.11]) with SMTP ID DSNKSmXpMJ5+6Hebo9MD9/DLNsqRmc45Hsfr@postini.com; Tue, 21 Jul 2009 16:13:39 UTC Received: by ey-out-1920.google.com with SMTP id 5so666171eyb.24 for ; Tue, 21 Jul 2009 09:13:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.44.211 with SMTP id n61mr1550459web.133.1248192815922; Tue, 21 Jul 2009 09:13:35 -0700 (PDT) In-Reply-To: <672136130907210854y5e26a3bdk69c41492054c4a74@mail.gmail.com> References: <672136130907210405p5ec1b02bwd6c3d25901113ae5@mail.gmail.com> <672136130907210854y5e26a3bdk69c41492054c4a74@mail.gmail.com> Date: Tue, 21 Jul 2009 18:13:35 +0200 Message-ID: Subject: Re: rmi client RemoteRepositoryException - AbstractMethod From: Alexander Klimetschek To: users@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Jul 21, 2009 at 5:54 PM, bruno coelho wrote: > ok, thanks. > > I was almost sure that it will be the answer... > > do you have a roadmap for version 2.0 of jackrabbit and rmi client? > I didn't find any thing specific in the site. Jackrabbit 2.0 should be out in the next 3 months (rough guessing). You can track the jsr-283 related work in JIRA: https://issues.apache.org/jira/browse/JCR-1104 The JCR-RMI library has its own release cycle (because it does not depend on Jackrabbit and should work with any JCR repository), hence it has its own Jira project: https://issues.apache.org/jira/browse/JCRRMI?report=com.atlassian.jira.plugin.system.project:roadmap-panel Feel free to add your issue there so it doesn't get lost for the 2.0 update. I don't know of any plans to release a JCR-2.0 compatible JCR-RMI, but if there is demand, it could get out along with Jackrabbit's 2.0 release. Regards, Alex -- Alexander Klimetschek alexander.klimetschek@day.com