Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add DatabindException as intermediate subtype of JsonMappingException #2828

Closed
cowtowncoder opened this issue Jan 16, 2019 · 1 comment
Closed
Milestone

Comments

@cowtowncoder
Copy link
Member

cowtowncoder commented Jan 16, 2019

There is too much historical naming convention using "json" in names; and this is particularly unfortunate at databinding level where multiple other formats are supported.
With 3.x we can start improving on at least some of these cases.

One initial thing to do for 2.13 would be to add new DatabindException as base type of JsonMappingException (similar to StreamReadException (under JsonParseException) and StreamWriteException (under JsonGenerationException)) -- for 2.x it can be used as receiver (but not thrown), and for 3.0 we can start actually using it and possibly remove JsonMappingException.

@cowtowncoder cowtowncoder transferred this issue from FasterXML/jackson-core Aug 23, 2020
@cowtowncoder cowtowncoder added 2.13 and removed 3.x labels Jan 21, 2021
@cowtowncoder cowtowncoder changed the title Rename JsonMappingException as DatabindException (for 3.0) Add DatabindException as intermediate subtype of JsonMappingException Jan 21, 2021
@cowtowncoder cowtowncoder added this to the 2.13.0 milestone Jan 22, 2021
@cowtowncoder
Copy link
Member Author

Bit trickier than I thought as the location information (including helper class) cannot move... but will make it work to some degree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant