. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 5.2.2. Exception Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . specific to each technology. 2.1. Consistent Exception Hierarchy Spring provides a convenient translation from technology-specific exceptions, such as SQLException to its own exception class hierarchy best way to guarantee that your Data Access Objects (DAOs) or repositories provide exception translation is to use the @Repository annotation. This annotation also lets the component scanning support

on plain JPA ........................................................... 303 12.6.4. Exception Translation ...................................................................................... 305 12.7 .................................................................................. 524 A.2.9. The tool schema .......................................................................................... possibilities for leveraging such a marker is the automatic translation of exceptions as described in Section 12.6.4, “Exception Translation”. The IoC container Spring Framework (2.5) 98 Spring 2.5

possibilities for leveraging such a marker is the automatic translation of exceptions as described in Section 12.6.4, “Exception Translation”. Spring 2.5 introduces further stereotype annotations: @Component Similarly, as stated above, @Repository is already supported as a marker for automatic exception translation in your persistence layer. The IoC container Spring Framework (2.5.1) 99 3.12.2. Auto-detecting expressions does still require Java 5+ though) and is backed by genuine POJOs. When using AOP as a tool to configure enterprise services then XML can be a good choice (a good test is whether you consider

The Spring Framework - Reference Documentation Spring Framework (2.0.2) vi 12.6.4. Exception Translation ...................................................................................... 237 12.7 .................................................................................. 441 A.2.7. The tool schema .......................................................................................... expressions does still require Java 5 though) and is backed by genuine POJOs. When using AOP as a tool to configure enterprise services (a good test is whether you consider the pointcut expression to be

The Spring Framework - Reference Documentation Spring Framework (2.0.1) vi 12.6.4. Exception Translation ...................................................................................... 236 12.7 .................................................................................. 439 A.2.7. The tool schema .......................................................................................... expressions does still require Java 5 though) and is backed by genuine POJOs. When using AOP as a tool to configure enterprise services (a good test is whether you consider the pointcut expression to be

on plain JPA ........................................................... 237 12.6.4. Exception Translation ...................................................................................... 239 12.7 .................................................................................. 440 A.2.7. The tool schema .......................................................................................... expressions does still require Java 5 though) and is backed by genuine POJOs. When using AOP as a tool to configure enterprise services (a good test is whether you consider the pointcut expression to be

possibilities for leveraging such a marker is the automatic translation of exceptions as described in Section 12.6.4, “Exception Translation”. Spring 2.5 introduces further stereotype annotations: @Component Similarly, as stated above, @Repository is already supported as a marker for automatic exception translation in your persistence layer. 3.12.2. Auto-detecting components Spring provides the capability of expressions does still require Java 5+ though) and is backed by genuine POJOs. When using AOP as a tool to configure enterprise services then XML can be a good choice (a good test is whether you consider

possibilities for leveraging such a marker is the automatic translation of exceptions as described in Section 12.6.4, “Exception Translation”. The IoC container Spring Framework (2.5.2) 100 Spring 2 Similarly, as stated above, @Repository is already supported as a marker for automatic exception translation in your persistence layer. 3.12.2. Auto-detecting components Spring provides the capability of expressions does still require Java 5+ though) and is backed by genuine POJOs. When using AOP as a tool to configure enterprise services then XML can be a good choice (a good test is whether you consider

on plain JPA ........................................................... 249 12.6.4. Exception Translation ...................................................................................... 250 12.7 .................................................................................. 458 A.2.7. The tool schema .......................................................................................... expressions does still require Java 5 though) and is backed by genuine POJOs. When using AOP as a tool to configure enterprise services (a good test is whether you consider the pointcut expression to be

on plain JPA ........................................................... 249 12.6.4. Exception Translation ...................................................................................... 251 12.7 .................................................................................. 458 A.2.7. The tool schema .......................................................................................... expressions does still require Java 5 though) and is backed by genuine POJOs. When using AOP as a tool to configure enterprise services (a good test is whether you consider the pointcut expression to be