Return-Path: X-Original-To: apmail-jackrabbit-users-archive@minotaur.apache.org Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B94F34999 for ; Mon, 6 Jun 2011 09:45:01 +0000 (UTC) Received: (qmail 81655 invoked by uid 500); 6 Jun 2011 09:45:01 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 81630 invoked by uid 500); 6 Jun 2011 09:45:01 -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 81622 invoked by uid 99); 6 Jun 2011 09:45:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Jun 2011 09:45:01 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jukka.zitting@gmail.com designates 209.85.212.42 as permitted sender) Received: from [209.85.212.42] (HELO mail-vw0-f42.google.com) (209.85.212.42) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Jun 2011 09:44:54 +0000 Received: by vwl1 with SMTP id 1so6313805vwl.1 for ; Mon, 06 Jun 2011 02:44:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=u5g6IgOuHw7ddN9EQ58WTVzRlAD+dJ9nhT1T9jEYeuM=; b=LTQRzDBLz45dKhmrOhMO79gIXLqX6rKNHYKbsqUaFZs//K64j5kA1UZeK+oQljYrlS ArVTKvGKiahB5PwcG/BmDq/Li/fhkyRXZMINdFU6mhBoBcphgMOdbLJNS9br0HSVUz/m BrH0v15oketWiJG8mPHYn8AA5UC9XzPzgfl3M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=O91cegYtMUFXwQtlf9hfqHyfSi1EdL09sVQjNdm0R6TGUheQiEEO9f08vQ62B22WKR tlqE/7qxy+EN8ckj3P9LAIeH2pSb5mg0hqSyJcBTpQuCatjjJQ7qZsx5tO/zZm8SDVpO 0RXZBPH+cSzJHLGVwABvwFZMl1e7IBN0OhtJM= Received: by 10.52.179.161 with SMTP id dh1mr4306126vdc.177.1307353474078; Mon, 06 Jun 2011 02:44:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.163.69 with HTTP; Mon, 6 Jun 2011 02:44:14 -0700 (PDT) In-Reply-To: References: From: Jukka Zitting Date: Mon, 6 Jun 2011 11:44:14 +0200 Message-ID: Subject: Re: Strange behavior with JCA adapter To: users@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 Hi, On Wed, Jun 1, 2011 at 2:35 PM, Edouard Hue wrote: > The two pathes \var\opt\data\flat\rbus\jcr > and \opt\application\rbus\current\etc\repository.xml are defined in the RAR > deployment descriptor. I expected the repository to be created and accessed > remotely on the server, but it appears that it is created locally on the > client machine ! Is this really the way it should work ? Sounds like something to do with the JNDI implementation (org.ow2.carol.jndi.spi.IRMIContextWrapperFactory) you're using, as it's impossible for Jackrabbit's JndiRepositoryFactory class to instantiate a local repository by itself. Are you sure the RMI implementation isn't trying to do something like serialize the entire remote repository instance? See the jackrabbit-jcr-rmi component for a JCR-RMI bridge that you can use to access a repository remotely. The repository instance that jackrabbit-jca binds to JNDI on the server is not enabled for remote access over RMI. BR, Jukka Zitting