Checking contextual integrity

Cantor, Scott cantor.2 at osu.edu
Wed May 29 09:35:13 EDT 2013


On 5/29/13 5:16 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:

>1) Keep the current code but arrange for the Predicates to throw an
>unchecked Exception.  Then in the upper layers we can either convert this
>to
>a FilteringException or "do the right thing" - which is to say log the
>error, deny *all* attribute release (we have to do this since we cannot
>know
>the scope of the operation). This worries me somewhat (but then so do all
>the options)

It would bother me more if it weren't for the fact that Java doesn't
really take the notion of unchecked exceptions seriously. Applications
seem to have to catch them all regardless if they want to avoid crashing,
and libraries throw them gratuitously. So I guess one more doesn't make
much difference.

-- Scott




More information about the dev mailing list