Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 76726 invoked from network); 14 Feb 2007 07:52:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Feb 2007 07:52:24 -0000 Received: (qmail 25607 invoked by uid 500); 14 Feb 2007 07:52:31 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 25581 invoked by uid 500); 14 Feb 2007 07:52:31 -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 25565 invoked by uid 99); 14 Feb 2007 07:52:31 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Feb 2007 23:52:31 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [217.12.11.33] (HELO smtp002.mail.ukl.yahoo.com) (217.12.11.33) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 13 Feb 2007 23:52:20 -0800 Received: (qmail 42321 invoked from network); 14 Feb 2007 07:51:59 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=Received:X-YMail-OSG:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:In-Reply-To:Thread-Index:X-MimeOLE; b=XocrPDbKMMH+/Wxb+9BESa0fXwOeUt8vHnWvoxbC5ZrtAwbDAQ1JtGUe5gX9IL/D3ISRh476G44q2LiGBBimoE9hxNCQ5GJcq3K66hRgr/Yrs0PN3XfNNgRj92jd5TsQ6QaI551m1QilAg7jjpbOVriUosmzu5H8L1p5AnS2his= ; Received: from unknown (HELO MIQSBARRIBA) (sbarriba@81.149.172.165 with login) by smtp002.mail.ukl.yahoo.com with SMTP; 14 Feb 2007 07:51:58 -0000 X-YMail-OSG: cDa25owVM1nddenUB89uf2m6rQpzap9xKtV9nDxWtEMe5pOHGPCXL80LfqE1LfuiJ7c26b.xQspX5X8pdTAzLN9UaZN5P77RE5_W7nGXgXMPn3N4fai0GnFv.OBZNb7e5a_LeWJie3DD From: "Shaun Barriball" To: Subject: RE: Providing RMI access for a model 2 - shared deployment Date: Wed, 14 Feb 2007 07:51:58 -0000 Message-ID: <001c01c7500d$01261b60$7201a8c0@mobileiq.local> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <510143ac0702131508n2d15e92dr14b31a5fc3f8e630@mail.gmail.com> Thread-Index: AcdPw+AUBD6/TgdrTqyuLZQLP4+EWAAR6ikA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Virus-Checked: Checked by ClamAV on apache.org Hi Zukka, Thanks for your response (as always). "....you can simply configure your existing repository webapp to expose the RMI endpoint. Check the rmi-port, rmi-host, and rmi-uri init parameters in the RepositoryStartup servlet configuration within WEB-INF/web.xml in the Jackrabbit webapp." My setup: /Tomcat /conf server.xml - Configured as per http://jackrabbit.apache.org/doc/deploy/howto-model2.html to provide JackRabbit via JNDI - Snippet from server.xml below. /webapps app1 - using JNDI to access JackRabbit app2 - using JNDI to access JackRabbit So I don't actually have a deployed webapp based on the JackRabbit-webapp.war (http://mirrors.dedipower.com/ftp.apache.org/jackrabbit/binaries/jackrabbit- webapp-1.2.1.war). I have deployed that in the past to enable RMI access but only where "app1" and "app2" were then changed to use RMI over JNDI. So my clarifications are (as I'm rusty on RMI and JNDI): 1) do I need to deploy the JackRabbit-webapp and configure its JNDI and RMI settings such that it "replaces" the configuration in the server.xml?, or 2) do I need to deploy the JackRabbit-webapp such that uses JNDI to lookup the repository configured in the server.xml and then just exposes via RMI?, or 3) can I improve my server.xml and add the RMI library to common/lib to get JackRabbit registered in both JNDI and RMI WITHOUT the need to deploy JackRabbit-webapp? Regards, Shaun. -- Snippet from server.xml -- factory org.apache.jackrabbit.core.jndi.BindableRepositoryFactory configFilePath C:/software/tomcat-5.0.30/jackrabbit-server/WEB-INF/repository/reposi tory.xml repHomeDir c:/transientrepository -----Original Message----- From: Jukka Zitting [mailto:jukka.zitting@gmail.com] Sent: 13 February 2007 23:08 To: users@jackrabbit.apache.org Subject: Re: Providing RMI access for a model 2 - shared deployment Hi, On 2/14/07, Shaun Barriball wrote: > Is it possible to deploy an additional JackRabbit.war configured for > RMI within the same container to expose the repository via RMI, but > allow fast local access for the other apps? Yes, in fact you shouldn't even need a separate Jackrabbit webapp, as you can simply configure your existing repository webapp to expose the RMI endpoint. Check the rmi-port, rmi-host, and rmi-uri init parameters in the RepositoryStartup servlet configuration within WEB-INF/web.xml in the Jackrabbit webapp. BR, Jukka Zitting ___________________________________________________________ All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine http://uk.docs.yahoo.com/nowyoucan.html