jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jawad Bokhari <jawad.bokh...@gmail.com>
Subject Re: Jackrabbit Deployment [SEC=UNCLASSIFIED]
Date Tue, 20 Jul 2010 19:24:33 GMT
Thanks Ross,

That was exactly what i was thinking for alternative.
It means, that's the only choice I have for now.
And, there isn't other better alternative for this.

Regards,
Jawad

On Mon, Jul 19, 2010 at 6:48 AM, <Ross.Dyson@ipaustralia.gov.au> wrote:

> 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.
>
>
> Ross.
>
> 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
> from
> > web for for viewing documents(ready-only) and from a back-end service
> that
> > populates the repository(read and write) with documents on scheduled
> basis.
> >
> > Both, the web application and the back-end service lies on the same
> machine.
> > I am using File-based repository at the moment.
> > Currently, I can't run both simultaneously. If i start the back-end
> service,
> > it applies lock on the repository and the web-app can't access. So, i
> always
> > have to stop the back-end service to let web-application show the
> documents
> > archived even in just read-only mode.
> >
> > I know, there is a deployment model based on "Repository Server", but
> that
> > would be too complex to setup. Is there any simpler mechanism to achieve
> my
> > desired  model?
> >
> > Many thanks,
> >
> > Jawad
>
>
> --
> This message contains privileged and confidential information only
> for use by the intended recipient.  If you are not the intended
> recipient of this message, you must not disseminate, copy or use
> it in any manner.  If you have received this message in error,
> please advise the sender by reply e-mail.  Please ensure all
> e-mail attachments are scanned for viruses prior to opening or
> using.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message