. . . . . . . . . . . . . . . . . . . 157 5.3.2. Implementing DAOs Based on the Plain Hibernate API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 5.3.3. Declarative Transaction Demarcation transaction APIs, such as Java Transaction API (JTA), JDBC, Hibernate, and the Java Persistence API (JPA). • Support for declarative transaction management. • A simpler API for programmatic transaction management Container-Managed Transactions (CMT) or choosing to drive local transactions through a proprietary API, such as Hibernate. • Understanding the Spring Framework transaction abstraction outlines the core

......................................... 126 12.2.5. Implementing DAOs based on plain Hibernate3 API .................................................. 126 12.2.6. Programmatic transaction demarcation ................................................ 134 12.3.3. Implementing DAOs based on plain JDO API ........................................................... 135 12.3.4. Transaction management ... ............................................ 139 12.4.3. Implementing DAOs based on plain TopLink API ..................................................... 140 12.4.4. Transaction management .........

......................................... 137 12.2.5. Implementing DAOs based on plain Hibernate3 API .................................................. 137 12.2.6. Programmatic transaction demarcation ................................................ 145 12.3.3. Implementing DAOs based on plain JDO API ........................................................... 146 12.3.4. Transaction management ... ............................................ 150 12.4.3. Implementing DAOs based on plain TopLink API ..................................................... 151 12.4.4. Transaction management .........

......................................... 126 12.2.5. Implementing DAOs based on plain Hibernate3 API .................................................. 126 12.2.6. Programmatic transaction demarcation ................................................ 134 12.3.3. Implementing DAOs based on plain JDO API ........................................................... 135 12.3.4. Transaction management ... ............................................ 139 12.4.3. Implementing DAOs based on plain TopLink API ..................................................... 140 12.4.4. Transaction management .........

......................................... 126 12.2.5. Implementing DAOs based on plain Hibernate3 API .................................................. 126 12.2.6. Programmatic transaction demarcation ................................................ 134 12.3.3. Implementing DAOs based on plain JDO API ........................................................... 135 12.3.4. Transaction management ... ............................................ 139 12.4.3. Implementing DAOs based on plain TopLink API ..................................................... 140 12.4.4. Transaction management .........

......................................... 126 12.2.5. Implementing DAOs based on plain Hibernate3 API .................................................. 126 12.2.6. Programmatic transaction demarcation ................................................ 134 12.3.3. Implementing DAOs based on plain JDO API ........................................................... 135 12.3.4. Transaction management ... ............................................ 139 12.4.3. Implementing DAOs based on plain TopLink API ..................................................... 140 12.4.4. Transaction management .........

......................................... 126 12.2.5. Implementing DAOs based on plain Hibernate3 API .................................................. 126 12.2.6. Programmatic transaction demarcation ................................................ 134 12.3.3. Implementing DAOs based on plain JDO API ........................................................... 135 12.3.4. Transaction management ... ............................................ 139 12.4.3. Implementing DAOs based on plain TopLink API ..................................................... 140 12.4.4. Transaction management .........

overall performance. This new release also introduces a first (beta) version of the Unomi GraphQL API. 1.1.1. INTRODUCING PROFILES ALIASES Profiles may now have alias IDs, which is a new way to reference with external systems, as well as provide more flexible and reliable merging mechanisms. A new REST API makes it easy to define, update and remove aliases for profiles. You can read more about profile aliases Scopes can be easily created via the corresponding REST API ( cxs/scopes ) For example, an "apache" scope can be created using the following API call. 1.1.3. JSON SCHEMAS Apache Unomi 2 introduces support

......................................... 118 11.2.5. Implementing DAOs based on plain Hibernate3 API .................................................. 118 11.2.6. Programmatic transaction demarcation ................................................ 126 11.3.3. Implementing DAOs based on plain JDO API ........................................................... 127 11.3.4. Transaction management ... ............................................ 131 11.4.3. Implementing DAOs based on plain TopLink API ..................................................... 132 11.4.4. Transaction management .........

................................................................. 117 11.2.4. Using the Hibernate API directly in DAO implementations ........................................ 118 11.2.5. Programmatic transaction (alternately called Dependency Injection) features. The BeanFactory [http://www.springframework.org/docs/api/org/springframework/beans/factory/BeanFactory.html] provides an advanced configuration mechanism capable potentially any kind of storage facility. The ApplicationContext [http://www.springframework.org/docs/api/org/springframework/context/ApplicationContext.html] builds on top of the BeanFactory (it's a subclass)