You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by Jeremy Stell-Smith <je...@gmail.com> on 2005/08/08 18:21:55 UTC

having to catch RepositoryException everywhere

So I'm playing around w/ jackrabbit, and getting really annoyed that
EVERYTHING throws a RepositoryException, and that RepositoryException
is checked.  Has any thought been given to changing that?  Wasn't that
one of the big problems w/ java's RMI?

Jeremy Stell-Smith

Re: having to catch RepositoryException everywhere

Posted by Brian Moseley <bc...@osafoundation.org>.

Jeremy Stell-Smith wrote:
> So I'm playing around w/ jackrabbit, and getting really annoyed that
> EVERYTHING throws a RepositoryException, and that RepositoryException
> is checked.

agree.

Re: having to catch RepositoryException everywhere

Posted by Stefan Guggisberg <st...@gmail.com>.

On 8/8/05, Jeremy Stell-Smith <je...@gmail.com> wrote:
> So I'm playing around w/ jackrabbit, and getting really annoyed that
> EVERYTHING throws a RepositoryException, and that RepositoryException
> is checked.  Has any thought been given to changing that?  Wasn't that
> one of the big problems w/ java's RMI?

most JCR implementations will probably be remote clients communicating 
with a server, i.e. method calls can fail for a number of reasons
(network failure etc).
that's why most methods throw RepositoryException.  

btw: the concept of the JCR api is very similar to the concept of JDBC
and AFAIK every JDBC method throws SQLException...

cheers
stefan

> 
> Jeremy Stell-Smith
>