Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (herse.apache.org: local policy)
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:X-MimeOLE:Thread-Index;
  b=wok9soOP367vKdFvqP8nS3wCGNH0UXItw1iPgrEwab8Q1svwI5qtojrwcnzdYBvh2qMj3X0E9sAw2EQbo27pwhorUIvEWEiTa0vmDToUB6vXV7cypiGX9JO50KSTlgdCOb+dzOcCHFgmu+egmkH9xdfjJqfoC9T1qX8YE4KgHfk=
  ;
From: "Shaun Barriball" <sbarriba@yahoo.co.uk>
To: <users@jackrabbit.apache.org>
Subject: RE: Providing RMI access for a model 2 - shared deployment
Date: Thu, 15 Feb 2007 11:58:35 -0000
Message-ID: <000601c750f8$a1397fc0$7201a8c0@mobileiq.local>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <510143ac0702150016o42a533eax4e8c61fde44f1ed@mail.gmail.com>
Thread-Index: AcdQ2bgXDaG0ej0oQwqdVl6X//mcpwAHgHHg

Hi Zukka et al,
Thanks for the info. I tried your suggestion.

* I modified the JackRabbit web.xml to only include the config for the
"Repository" servlet.
* Changing "repository-name" worked fine
* However I expected/hoped that specifying an rmi-url with host and port
would result in the repository being exposed via RMI. This didn't happen.

Looking at the code for RepositoryAccessServlet it does not appear to be
capable of exposing a repository via RMI, unlike RepositoryStartup which
can. I'm guessing RepositoryAccessServlet  is only intended for access, not
for publishing?

If this is the case, is it possible to get the RepositoryStartup to either:

 * read from a JNDI name and publish via RMI, or

 * initialise the repository and publish into the global JNDI spec for other
webapps AND via RMI. Perhaps I'm just looking for the right combination of
"java.naming.provider.url" and "java.naming.factory.initial" values to
emulate the settings on the Tomcat server.xml.

Using model 2 with RMI enabled access will be very, very useful for remote
adminstration.

Regards,
Shaun.
  

-----Original Message-----
From: Jukka Zitting [mailto:jukka.zitting@gmail.com] 
Sent: 15 February 2007 08:17
To: users@jackrabbit.apache.org
Subject: Re: Providing RMI access for a model 2 - shared deployment

Hi,

On 2/14/07, Shaun Barriball <sbarriba@yahoo.co.uk> wrote:
> So I don't actually have a deployed webapp based on the 
> JackRabbit-webapp.war

OK, understood.

>  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?,
>
>  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?

Option 2 is the best for you. You need to remove the "RepositoryStartup"
servlet configuration in the jackrabbit-webapp web.xml descriptor and modify
the "Repository" servlet configuration to load the repository from JNDI and
to expose it via RMI.

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