Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 97952 invoked from network); 13 Oct 2010 15:27:59 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 Oct 2010 15:27:59 -0000 Received: (qmail 79958 invoked by uid 500); 13 Oct 2010 15:27:59 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 79765 invoked by uid 500); 13 Oct 2010 15:27:58 -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 79757 invoked by uid 99); 13 Oct 2010 15:27:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Oct 2010 15:27:58 +0000 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=FREEMAIL_FROM,FREEMAIL_REPLY,RCVD_IN_DNSWL_NONE,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.214.170 as permitted sender) Received: from [209.85.214.170] (HELO mail-iw0-f170.google.com) (209.85.214.170) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Oct 2010 15:27:52 +0000 Received: by iwn37 with SMTP id 37so10487568iwn.1 for ; Wed, 13 Oct 2010 08:27:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=GT4o6FFA8WebsQeO/5tEFW1Q1kZdKxhgbEpd4kXfmj0=; b=U6oYqtpGi1VXZAENedRWmkEfy2o7QKUhbh63LMklhdWmzKZoVOUDBiwIDoIwNC1168 ZqB7nAJ/MKwfm86z53SeHVimgGHfU8zNuS3b7gFEukN1CYAocPaqLiTTC+WNKFwKroc9 AqFz+3q5YwRyuAJzS83xSERSD7yTPOjWPyXX4= 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=tTrsAReldV8qPYmbZcU8KxMA1M7gj2KABJlyooQu+a67siC8OlkDWO6rHZscr8gHk3 LFYGi7n3ZjHNVhi3/vSvJQL5lPs1hEimv0Rhlzey8kKykIWsjMcpxPtqEyYFKCVP4eDt 5+euT02hZkF+5vK/2UO+AFodxN777mzY3hy3w= Received: by 10.231.161.16 with SMTP id p16mr7235676ibx.61.1286983652032; Wed, 13 Oct 2010 08:27:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.207.74 with HTTP; Wed, 13 Oct 2010 08:27:11 -0700 (PDT) In-Reply-To: <1286982477717-2993831.post@n4.nabble.com> References: <1286982477717-2993831.post@n4.nabble.com> From: Jukka Zitting Date: Wed, 13 Oct 2010 17:27:11 +0200 Message-ID: Subject: Re: Local vs Remote access while creating Namespace and Node Types To: dev@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 Hi, On Wed, Oct 13, 2010 at 5:07 PM, kazim_ssuet@yahoo.com wrote: > Question 1: This namespace (created as local access) is not visible in > remote access when I run standalone server and use RMI API, why? It seems likely that your standalone server is not accessing the same repository as the one you created locally. Please double-check your configuration. The RMI layer simply proxies the remote JCR API calls to the server, so there's no reason why it would behave differently than a local client as long as you're actually accessing the same repository. This most likely explains all the other oddities you mentioned. BR, Jukka Zitting