Persistence Models.pptVIP

Persistence Models Margaret Smith Overview Java Data Objects (JDO) Enterprise Java Beans (EJB) 3.0 Demos and code What is JDO? The Java Data Objects (JDO) API is a standard interface-based Java model abstraction of persistence developed as Java Specification Request 12 (JSR 12) under the Java Community Process. What is EJB 3.0? Enterprise Java Beans (EJB) 3.0 is a deep overhaul and simplification of the EJB specification. EJB 3.0s goals are to simplify development and focus more on writing plain old java objects (POJOs) rather than on complex EJB APIs. JSR-220 of the Java Community Process. How are EJB and JDO related? Earlier EJB Versions vs EJB 3.0 Focus on plain Java classes Strong emphasis on Java metadata annotations eliminates need for deployment descriptor Annotations take the form of @[Something] and are used to express meta-data Specification of programmatic defaults Provides default database Less transactional code Creating an application Step 1: Design your domain/model classes as you would do normally Step 2: Define their persistence definition using Meta-Data Step 3: Compile your classes, and instrument them (using a JDO enhancer) Step 4: Generate the database tables where your classes are to be persisted Step 5: Write your code to persist your objects within the DAO layer Step 6: Run your application Step 1: Design your domain/model classes as you would do normally Step 2: Define their persistence definition using annotations as Meta-Data Step 3: Compile your classes Step 4: Run your application Optional step: specify a database other than the default Hsqldb database Usage Models Demos and code Store application where objects are Product and Book Plain java objects PersistenceManager object More error checking Investment calculator application where objects are Fund and EntityCalculator Plain annotated java objects EntityManager object JDO: Schema file ?xml version=1.0? !DOCTYPE jdo PUBLIC -//Sun Microsystems, Inc.//DTD Java Data Objec