On 2012-05-03 14:54, Thomas Mueller wrote:
Hi,

If the OakException wraps a RepositoryException, we extract that one and
rethrow it, it will come with an incorrect stack trace, no?

You mean, if we use "throw ((OakException) e).getOriginalException()" or
something similar when unwrapping?

Yes.

So it seems
we need to re-wrap.

Not sure what you mean with re-wrap actually...

Throw a RepositoryException that wraps whatever was sent from below.


It seems we're converging on

- OakException extends RuntimeException

- OakExpception can carry RepositoryException

Should we start with that, and see how this works? (Open a issue for it?)

Sounds good to me.

Regards,
Thomas



Reply via email to