Pro JPA 2: Mastering the Java™ persistence API

Pro JPA 2: Mastering the Java™ Persistence API

Volumn , Issue , 2010, Pages 1-503

  Keith, Mike ^a   Schnicariol, Merrick ^b  

^a JPA 20 Expert Group   (Canada)

^b Oracle ^*  (United States)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84892250197     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/978-1-4302-1957-6     Document Type: Book

References (36)

1. Peter P. Chen, "The entity-relationship model-toward a unified view of data", ACM Transactions on Database Systems 1, no. 1(1976):9-36.
2. In most cases, this is a requirement, but in certain configurations the transaction may not be present until later.
3. Annotations on setter methods will just be ignored.
4. In inheritance situations, additional callback methods from parent classes can also be invoked.
5. Although session beans can be invoked asynchronously, they do not offer the same quality of service (QoS) guarantees as message driven beans.
6. Alur, Deepak, John Crupi, and Dan Malks. Core J2EE Patterns: Best Practices and Design Strategies, Second Edition. Upper Saddle River, N. J.: Prentice Hall PTR, 2003.
7. Little, Mark, Jon Maron, and Greg Pavlik. Java Transaction Processing: Design and Implementation. Upper Saddle River, N. J.: Prentice Hall PTR, 2004.
8. Bernstein, Philip A., and Eric Newcomer. Principles of Transaction Processing. Burlington, MA: Morgan Kaufmann, 2009.
9. Alur et al., Core J2EE Patterns.
10. Even though e mbedded ty pes can be shar ed or reused, the instances cannot. An embedded obj ect instance belongs to the entity that references it; and no other entity instance, of that entity type or any other, can reference the same embedded instance.
11. Assuming that the collection was not returned from a second level shared cache.
12. See the javadoc for java.util. Map for more details.
13. The @MapKey annotation is still required, however; otherwise, the @MapKeyColumn defaults would apply.
14. Fowler, Martin. Patterns of Enterprise Application Architecture. Boston: Addison-Wesley, 2002.
15. Alur, Deepak, John Crupi, and Dan Malks. Core J2EE Patterns: Best Practices and Design Strategies, Second Edition. Upper Saddle River, N. J.: Prentice Hall PTR, 2003.
16. Gamma, Erich, Richard Helm, Ralph Johnson, and John Vlissides. Design Patterns: Elements of Reusable Object-Oriented Software. Boston: Addison-Wesley, 1995.
17. * N, where M is the number of entity instances of the first type and N is the number of entity instances of the second type.
18. This is often referred to as an annotation processing tool, or APT, because it used to be a standalone tool shipped with the JDK and used only for processing annotations. Since Java SE 6, it is actually a generalized compile-time hook to perform any kind of pre-processing or code generation.
19. Normalization of data is a database practice that attempts to remove redundantly stored data. For the seminal paper on data normalization, see "A Relational Model of Data for Large Shared Databanks" by E. F. Codd (Communications of the ACM, 13 (6) June 1970). Also, any database design book or paper should have an overview.
20. See http://www.jcp.org/en/jsr/summary?id=303.
21. Some localization mechanisms are built into the validation message interpolator, but custom message interpolation can also be plugged into the validator to perform localization in custom ways.
22. Only the non-standard attributes are listed. The standard/required attributes will be discussed in the section on creating new constraints.
23. validateProperty () and validateValue () methods are also available, but we will discuss only the representative validate () method.
24. Technically, there is a description element in many of the elements, just as there are in most of the standard schemas in Java EE, but they have little functional value and will not be mentioned here. They might be of some use to tools that parse XML schemas and use the descriptions for tooltips and similar actions.
25. It is possible, and even probable, that vendors will process the mapping files in the order that they are listed, but this is neither required nor standardized.
26. Some have argued that these kinds of tuning exercises are precisely why XML should be used to begin with.
27. Most JPA vendors support some kind of schema generation either in the runtime or in a tool.
28. The exception to this rule may be the optional element of the mapping annotations, which may result in a NON NULL constraint, but which may also be used in memory to indicate that the value is or isn't allowed to be set to null.
29. The resulting column must be supported by the provider runtime to enable reading from and writing to the column.
30. Visit http://jakarta.apache.org/cactus/for more information.
31. Alur, Deepak, John Crupi, and Dan Malks. Core J2EE Patterns: Best Practices and Design Strategies, Second Edition. Upper Saddle River, N. J.: Prentice Hall PTR, 2003, p. 315.
32. Visit http://dbunit.sourceforge.net/for more information.
33. At the risk of sounding somewhat biased, might we humbly suggest Oracle XE. It represents the power of the Oracle database conveniently sized to an individual machine at no cost. All the examples in this book (including the advanced SQL query examples) were developed on Oracle XE.
34. Alur, Deepak, John Crupi, and Dan Malks. Core J2EE Patterns: Best Practices and Design Strategies, Second Edition. Upper Saddle River, N. J.: Prentice Hall PTR, 2003.
35. See http://java.sun.com/blueprints/patterns/FastLaneReader.html for more information.
36. Fowler, Martin. Patterns of Enterprise Application Architecture. Boston: Addison-Wesley, 2002.