Does any one know a good package with checked exceptions?

Question

Hey,
Today in a place that i work there is a lot of use in checked exception and there is no good reuse in exception. For each case a new check exception is created.
i want to eliminate the checked exception types in the system, so i want to recognize the common cases of checked exceptions like :
Required
Validation and etc
The best will be to find a package (like jackarta) that has those common cases or any other good reference in order to get ideas.
Thank you

Answer 1

AvihaiMar wrote:
they are not sufficient
i excpect from exception like validation exception to have the following fields (some of them optional):
class name
field name
given data
expected value
additional information
i am looking for any framework that already did this job.
That really looks like a system that doesn't understand the difference between exceptional states and normal error conditions to me.
If a user enters 13 for the month in a date field that is NOT an exception. Users are expected to enter invalid data. Thus it is not exceptional.
Conversely if your GUI client is sending data to the server then the server should not, normally, expect to see a 13 for the month. It might happen but it should be so rare that it should not require anything different than if a order request came in which didn't actually have any items in it (substantially different type of exceptional situation but still something the server would not expect.)
Now there are situations where you might, as a matter of convenience choose to use exceptions (as a class) to handle normal conditions. However such exceptions should be specific to a layer if common and very uncommon if they cross layer boundaries. And those specific to a layer are unlikely to have the same properties of those in another layer.
This of course is applicable to an application of which most software is in the world and thus most programmers would be working on that.
If you should find yourself in the unique position of being a library developer then a modified position would be required. A library developer is NOT someone who creates a 'library' for an application. Instead it is someone who delivers as a final product code that is ONLY intended to be used in other applications and only when there is more than one application.