jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross.Dy...@ipaustralia.gov.au
Subject Re: Jackrabbit Deployment [SEC=UNCLASSIFIED]
Date Mon, 19 Jul 2010 01:48:43 GMT
Split the update components from the back end service and offer them as 
web services from the web app part.

The back end service becomes a client.  Use a shared directory, pass paths 
to files to save encoding them into soap messages.


Jawad Bokhari <jawad.bokhari@gmail.com> wrote on 17/07/2010 07:10:54 PM:

> From: Jawad Bokhari <jawad.bokhari@gmail.com>
> To: users@jackrabbit.apache.org
> Date: 17/07/2010 07:11 PM
> Subject: Jackrabbit Deployment
> Hi,
> I want to setup single Jackrabbit repository that should be accessible 
> web for for viewing documents(ready-only) and from a back-end service 
> populates the repository(read and write) with documents on scheduled 
> Both, the web application and the back-end service lies on the same 
> I am using File-based repository at the moment.
> Currently, I can't run both simultaneously. If i start the back-end 
> it applies lock on the repository and the web-app can't access. So, i 
> have to stop the back-end service to let web-application show the 
> archived even in just read-only mode.
> I know, there is a deployment model based on "Repository Server", but 
> would be too complex to setup. Is there any simpler mechanism to achieve 
> desired  model?
> Many thanks,
> Jawad

View raw message