Skip to content
Scan a barcode
Scan
Paperback Core Java Data Objects Book

ISBN: 0131407317

ISBN13: 9780131407312

Core Java Data Objects

A guide to Java Data Objects (JDO) - the standard for persistent storage of Java objects. The text includes pratical examples and best practices as well as a full case study. This description may be from another edition of this product.

Recommended

Format: Paperback

Temporarily Unavailable

We receive 1 copy every 6 months.

Customer Reviews

4 ratings

Good JDO Overview

Java Data Objects (JDO) is a persistence framework to save Java objects to a datastore. The example code shows you how to create, read, update, and delete a persistent object using the JDO API. The book goes through the JDP API, especially the five main interfaces needed. The metadata, an xml file, that is needed for JDO is make clear in one chapter and the various options in the JDO xml file are explained to show you how to store your type of objects. The explanation of first-class and second-class object could have been longer. It seems like a more important topic and the brief mention in the book. Part of the book shows you how to develop applications with JDO and the architecture scenarios where you should or should not use JDO. The third part of the book covers using JDO and J2EE application. The authors argue that JDO in most situations offers a better solution over EJB entity beans to store your objects or to use JDO and some direct JDBC. Practical examples showing how JDO can be applied to existing applications The authors also have a real world case study that provides best practices and tips for your projects. The only part missing from the book, are using JDO implementations, which makes the examples impossible to test without using an implementation from one on the JDO implementers. I would recommend this book for anyone trying to learn JDO, but more information would be needed to use an actual JDO implementation.

A great book on JDO.

Name of the book: Core Java Data ObjectsAuthors: Sameer Tyagi, Keiron McCammon, Michael Vorburger, and Heiko Bobzin.Published: Sun Microsystems Inc.,Publishing Date: Winter 2004.City: Upper Saddle River, NJ5=Well done! This book will be a valuable teaching and reference tool.4=I would recommend this book to someone interested in its topic. 5=A complete reference. I would not need any additional reference on this topic.Write a minimum of three paragraphs describing the different aspects of this book. This is an excellent book on Java data objects for people who have worked with databases for a long time. the authors have taken the time to explain the concepts of JDO and how it can be implemented with fairly simple examples that are more real world.the authors also explain about the security aspects in JDO that need to be considered while implementing a real world situation. they also explain the differences between JDO and JDBC for people who have worked with JDBC and ways to implement JDO.the authors towards the end of the book explains how to explain the implementation of JDO for J2EE and enterprise solutions. they also provide tricks and tips for effective jdo implementation. a real world case study is presented for people who want to implement this solution.I would recommend this book to anyone interested in learning java data object.

Don?t drop your JDBC yet!

A good presentation for both architects and programmers, about JDO. The author explains the issues with Object oriented programs and relational databases then goes to show how JDO attempts to solve this mismatch (otherwise know as object relational impedance mismatch) Note from this book you will find that JDO is a standard to be implemented by vendors so that developers need not know varying interfaces object relational mapping frame works. JDO also has its own query language, which is not as powerful as SQL especially if you have complex joins or aggregation (OLAP) so, don't drop your JDBC yet! Well written with little fluff. It's not a O'rilly style code code book, it has the write amount of theory and code mix

JDO has matured in one year

In the march towards higher levels of abstraction and more powerful coding approaches, Sun came up with Enterprise Java Beans several years ago. But despite one's best efforts, instead of focusing on writing business logic in a modular, fully encapsulated way, you often also have to deal with reading and writing to a persistent format; usually a relational database. The gritty details of the impedance mismathc between your [hopefully] object oriented approach and the latter might eat up too much of your time.Realising this, Sun devised Java Data Objects. The book describes their main promise, which is to hide away the details of persistence. The big gain is in increasing the potential developer audience, as compared with EJBs. And you have less need of expert knowledge of RDBs. Previously, that was often a de facto requirement. You can now focus on the business logic. The second gain is shown in the JDO code examples, which are often cleaner without the persistence details. Of course, any realistic business logic will have more complicated details than the simple examples in the book, but at least persistence can be pushed offline.Last year, Robin Roos wrote "Java Data Objects" [also by the same publisher]. At that time, JDO was just getting started. Now, Sun has moved it deeper into J2EE. There is a lot more support for transactions and JDBC. JDO is no longer a speculative fling.
Copyright © 2024 Thriftbooks.com Terms of Use | Privacy Policy | Do Not Sell/Share My Personal Information | Cookie Policy | Cookie Preferences | Accessibility Statement
ThriftBooks® and the ThriftBooks® logo are registered trademarks of Thrift Books Global, LLC
GoDaddy Verified and Secured