Re: Lock/Block write access in order to maintenance of the repository

[Michael Wechner]

Thomas Müller schrieb:
Hi,
ok, but I guess Jackrabbit then throws  some "cannot write" exception (in
  
the case of writing), whereas  it's not going to be clear
to the application why this is happening, right?
    


Yes. You could catch the exception and re-throw one with a better message.
  

right, but how does the application know that the exception thrown by 
Jackrabbit is because the backend was set to read-only
and not for instance by some permission or some other problem?

Thanks

Michael
Regards,
Thomas