One significant improvement in 2.9 is that instead of just having
`JsonMappingException` base type (and couple of more specialized subtypes),
there will be division into 2 classes, subtypes of mapping exception:

* `InputDefinitionException` for problems discovered during introspection,
not related anything within input content (such as invalid combination of
annotations, or missing creator)
* Another exception type that is due to mismatching content (not parsing
problem, for which there is already `JsonParseException`), like missing
`type id`, or getting a JSON Object when number is expected

For latter, I thought of using `InputMismatchException` as relatively
descriptive name. Alas, there is also `java.util.InputMismatchException`,
which makes its use cumbersome in IDEs.
This may or may not be significant problem for users. Possibly not (most
users do not distinguish between types, and just catch
`JsonMappingException` or `IOException`), but if you do need processing, it
can be awkward.

Now: one way to make name unique would be to use a prefix:

* `JsonInputMismatchException` would be consistent with existing naming --
however, I dislike inclusion of `json` these days, since there are many
non-JSON backends, and these problems are not necessarily or even commonly
related to JSON encoding itself (for which `JsonParseException` would be
relevant)
* `JacksonInputMismatchException` would be unique, not json-specific, and
prefix is used for certain things (like some of annotations). But sort of
differs from naming of exceptions.

Any opinions on best choice? As things are, 2.9.0-SNAPSHOT has
`InputMismatchException`, and there is no strict need to change that.
But if it was to be changed, I'd like to get it changed before 2.9.0.rc1
(which is still month or more out).

-+ Tatu +-

-- 
You received this message because you are subscribed to the Google Groups 
"jackson-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to