Skip to content

Improve Exception/Error handling logic, heirarchy, etc #1106

Open
@MikeNeilson

Description

@MikeNeilson
          There is no parent class that RateException can extend?  Otherwise what keeps ApiServlet from filling up with implementation specific exception types?  I would think that if we really can't think of anything more generic at the very least we should be able to make a class for Controller exceptions and another for DaoExceptions depending on where the issue is.  I don't see ApiServlet knowing how to handle RateException in any helpful or meaningfully different way than other exceptions.

Originally posted by @rma-rripken in #1082 (comment)

Based on the PR discussion, we need to revisit the error handling. I think we have the crux of the right solution and some recent experience may provide us the next improvement.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestjavaPull requests that update Java codepriority:mediumWe care, and will try and get to it soon.user-friendly

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions