Exceptions are objects and should be treated as such. Organizing exceptions in an
is problematic. Consequently you would also have to create packages for classes, interfaces, beans etc.
Usually you are not searching for classes, interfaces or exceptions during the development cycle, rather than for functionality first. It is a better idea to organize the code after domain responsibilities and not obvious nature. Also it easily possible to find exceptions with any modern IDE regardless of their location: all exceptions have to inherit from
NEW workshop: Building HTML 5 Applications With Angular 2
Full week in December 2016: from Java EE 7 Bootstrap, Effective, Architectures over Testing to Microservices
On demand workshops: Java EE 7: Bootstrap, Effective, Testing and Microservices available for streaming.