From users-return-1411-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org Wed Nov 22 11:12:01 2006 Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 44037 invoked from network); 22 Nov 2006 11:12:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Nov 2006 11:12:01 -0000 Received: (qmail 27010 invoked by uid 500); 22 Nov 2006 11:12:03 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 26986 invoked by uid 500); 22 Nov 2006 11:12:02 -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 26969 invoked by uid 99); 22 Nov 2006 11:12:02 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Nov 2006 03:12:02 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of jukka.zitting@gmail.com designates 66.249.82.231 as permitted sender) Received: from [66.249.82.231] (HELO wx-out-0506.google.com) (66.249.82.231) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Nov 2006 03:11:50 -0800 Received: by wx-out-0506.google.com with SMTP id i28so179049wxd for ; Wed, 22 Nov 2006 03:11:29 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YRYGyw5hu1ZS/LN22MLxJAFo1+IWAwIa76bWJ4yrfjT1hN+rJ19ozDbndgMMuX4UQcFsfmSqXvmfr8RGnF7Y3/YevpXpkJ3uq0bgXbrUtY5rM4YOCZxXc+8GjIb/I3YjeLyhy/rS/c4QwegdTGGRp/yFHsAMKyDS/SUZrrLTLk4= Received: by 10.90.52.18 with SMTP id z18mr6441610agz.1164193889806; Wed, 22 Nov 2006 03:11:29 -0800 (PST) Received: by 10.90.102.20 with HTTP; Wed, 22 Nov 2006 03:11:29 -0800 (PST) Message-ID: <510143ac0611220311q18039a7j22919c27410e5671@mail.gmail.com> Date: Wed, 22 Nov 2006 13:11:29 +0200 From: "Jukka Zitting" To: users@jackrabbit.apache.org Subject: Re: Registering Node Types over RMI In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <011101c70a8e$3a40af60$74f0500a@mdesad.mdesnet.ms.gov> <009e01c70e05$fbf066d0$7c01a8c0@FLEXO> X-Virus-Checked: Checked by ClamAV on apache.org Hi, On 11/22/06, Christoph Kiehl wrote: > Daniel Murley wrote: > > Is it at all possible to register node definitions using the RMI client? > > > > I currently have a situation where the application uses RMI to talk to a > > separate tomcat instance running jackrabbit. However it doesn't seem to be > > possible to register node types over the wire/ > > No, it's not possible to register nodetypes over RMI. This is because the JCR > spec does not specify how nodetypes are registered and the JCR API does not > include methods to register nodetypes. Since the RMI interface reflects the JCR > API 1:1 there is no method to register nodetypes in the RMI interface as well. > Nodetype registration has to be done locally on your server. Or you have to > write your own RMI interface to register nodetypes. There's an improvement request JCR-585 for extending JCR-RMI with some Jackrabbit-specific features while still maintaining support for other JCR repositories. The initial goal is to have it done by Jackrabbit 1.2. BR, Jukka Zitting