<div>
Great! If the exception is in the DAO Layer should I catch it in the Business layer also? or only in the service layer?
</div>


<div>
You should always catch Exceptions at the level of the system that knows how to correctly handle that exception.<br />
<br />
In other words, &quot;it depends&quot;. &nbsp;If you know what to do at the business layer to handle the exception (e.g. database offline, let's check the cache) then handle it there.<br />
<br />
But if you need to return to the user &quot;it didn't work&quot; you should let it bubble up to the service layer and send the error out to the user.<br />
<br />
Doug
</div>


<div>
<div class="content wysiwyg-content">
I´m designing a service layer in a multilayerd architecture (Service, Business, Dao). Suposse I need a method like getUserAccounts<br />
<br />
This method just return a list of Accounts, but what if my dao layer can´t connect to database, or if I have some error when reading the recorset, a parse problem for example. Or maybe another error in the business layer.<br />
<br />
Do I have to catch the exception in the service layer, and map to a error code? <br />
Do I have to catch the exception in the business layer, and the buisness layer return a bean with the error code? Avoiding to have any kind of logic in the service layer, more than exposing the Rest API
</div>
</div>


I´m designing a service layer in a multilayerd architecture (Service, Business, Dao). Suposse I need a method like getUserAccounts

This method just return a list of Accounts, but what if my dao layer can´t connect to database, or if I have some error when reading the recorset, a parse problem for example. Or maybe another error in the business layer.

Do I have to catch the exception in the service layer, and map to a error code? 
Do I have to catch the exception in the business layer, and the buisness layer return a bean with the error code? Avoiding to have any kind of logic in the service layer, more than exposing the Rest API

Java Message handling in Service Layer

Java is a platform-independent, object-oriented programming language and run-time environment, designed to have as few implementation dependencies as possible such that developers can write one set of code across all platforms using libraries. Most devices will not run Java natively, and require a run-time component to be installed in order to execute a Java program.

Java

Computer-aided design (CAD) is the use of computer systems to aid in the creation, modification, analysis, or optimization of a design. CAD output is often in the form of electronic files for print, machining, or other manufacturing operations. CAD software for mechanical design uses either vector-based graphics to depict the objects of traditional drafting, or may also produce raster graphics showing the overall appearance of designed objects. As in the manual drafting of technical and engineering drawings, the output of CAD must convey information, such as materials, processes, dimensions, and tolerances, according to application-specific conventions.