Glad to see you're lurking ...
I think Spring approach is here is nice. They have their own unchecked
exception hierarchy and adapters for different data stores convert
specific exceptions to one of the exceptions in Spring's hierarchy.
can define a simple LDAP related data store exception hierarchy and
expect all partition implementations to obey it.
On Jan 16, 2008 12:45 AM, Alex Karasulu <email@example.com> wrote:
> Hi all,
> Different underlying stores have different kinds of checked exceptions they
> throw at the lowest level. For example JDBM is humble and just uses IO
> exceptions. The JE authors use an exception hierarchy based on
> DatabaseException. I was wondering if there was a preference out the base
> class for what exceptions are thrown from partitions? Right now there are a
> few options:
> (1) Throw exceptions that extend IOException (works well with JDBM)
> (2) Throw NamingExceptions works well with Java Naming but we have a bad
> taste in our mouths from this.
> (3) Create our own base class for exceptions thrown at these lower layers
> like say PartitionException
> Right now I went with IOException but I'm thinking it might be biased
> towards a particular partition implementation. Does anyone have some
> opinion one way or the other?