Amritendu De - Spring, Hibernate, Data Modeling, REST and TDD:Agile Java Design and Development

Dedicated to my father, the late Tapan Kumar De Copyright 2014 by Amritendu De All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the written prior permission of the author. Editor - Cathy Reed (www.cathyreedediting.com) Cover design Iryna Spica (www.spicabookdesign.com) About the author After completing his computer science, engineering degree, Amritendu De has spent the last 12 years working in the IT industry. He has worked for organizations such as HP, IBM and Oracle in various capacities and is currently working with a leading multinational company as a Senior Software Architect. He has worked extensively on Java and related technologies; has been involved in end-to-end product development for CRM, Utilities and Data Center Infrastructure Management business domains; and holds Sun Certified Enterprise Architect (SCEA) certification. He is the author of the Oracle Certified Master Java EE Enterprise Architect Practice Guide and the Oracle Certified Associate Java SE 7 and SE 6 Practice Exams.

In his free time, Amritendu likes to watch movies and read detective stories. About the technical editor Michael Rocha is an Enterprise Architect and Consultant with more than 25 years of experience. He started his career in IT in the era of Unix based systems and MS-DOS PCs and has been at the forefront of disruptive technologies, including the client-server era, web-based computing, the dot com boom, and most recently in the Cloud, Analytics, Mobile and Social computing. He has extensive experience in Java and JEE and has architected solutions for clients worldwide. About the code contributors Lalit Narayan Mishra is an Electronics engineer who has spent the last eight years working on Java and related technologies. Hazekul Alam graduated from West Bengal University of Technology in 2006 with a degree in Computer Engineering. Hazekul Alam graduated from West Bengal University of Technology in 2006 with a degree in Computer Engineering.

He has worked for organizations like Sears Holding and IBM, has extensive experience with Java and related technologies, and is currently working with Synechron Technologies as Sr. Associate. In his spare time, he likes to watch cricket. Preface I have been working on Java based, data driven applications for more than a decade now. I have seen the rise of popular object relational model frameworks solving the object relational impedance mismatch which is a set of technical and conceptual problems encountered in an object oriented program when using a relational database management system. This book takes into consideration all the relationships of data modeling and solves the problem by designing, developing and unit testing using Spring and Hibernate technology.

Developers who are working with relational database driven Spring and Hibernate applications will find it very useful. The book will also be helpful for developers who are using Spring for designing business service and data access tiers or service based development which supports front ends like Android, iPhone or mobile browser. Chapter 1 starts with a discussion of the most popular data driven Java based architecture Spring and Hibernate. The architecture along with each architected and important tier is discussed in detail. The chapter also covers REST architectural style in detail. Chapter 2 starts with a simple example of managing a standalone entity.

The chapter contains detailed explanations with code examples. Chapters 3, 4 and 5 focus on one-to-one relationships with a detailed explanation of how to manage a one-to-one unidirectional, bidirectional and self-referencing relationship. Chapters 6, 7 and 8 focus on one-to-many relationships. If you wish to manage a one-to-many relationship, whether it is a unidirectional, bidirectional or self-referencing relationship, this chapter shows you how. Chapters 9, 10, 11, 12 and 13 are about managing many-to-many relationships. Chapters 14, 15 and 16 are about managing inheritance relationships. Chapters 14, 15 and 16 are about managing inheritance relationships.

The different forms, like Single table, Concrete table and Class table inheritance relationships, are covered in detail. All the chapters begin with a mock test service tier which can be used for developing the user interface. The user interface team and the service development team can work in parallel, saving crucial dependency time in an agile manner. You will find a detailed explanation of how to achieve this by reading the second chapter. The chapters contain fragments of the entire source code and therefore I thought it would be useful to provide the entire source code to the readers. I strongly urge that the reader gets hands-on and implements all the code described in this book.

Experienced architects and developers may skip as per their judgment. The Github location for the entire application covered in the book is: https://github.com/Spring-Hibernate-Book/spring-hibernate-datamodeling-tdd-rest.The download does not require a password. The Appendix contains the software installations used to develop the application. At the time of publishing the book, the versions may have been upgraded, so only the names are provided. The latest versions available can be downloaded and a small amount of tweaking may be required. I wish you good luck and happy reading! Part I. An Introduction to Data-Driven Development Chapter 1.

Architecture In this chapter, we cover the essentials of forming software architecture, specifically REST based. We will first look at what is software architecture. We will then look at how to select a framework for RESTful Web Services, a web framework, a business-tier technology, and a persistence mechanism. Finally, we will review some popular patterns and best practices and take a look ahead to the application architecture covered in the book. The aim is to set the context for the discussions after this chapter on data driven development using REST architectural style. What is Software Architecture? Software architecture denotes the higher-level building blocks of a software system.

Like architecture in the real world, software architecture defines the high-level system structure of the software components, the discipline of creating the component hierarchy, and documenting this structure. It also forms a set of architectural design decisions that lead to the structure and the rationale behind it. During the start of the product development, an architect creates a software architecture, which forms the basis of design and development for the technical requirements converted from business requirements. When we look at how software development started, we mainly see focus on the required functionality and a data-driven flow. However, modern application development has extended the focus on quality attributes such as extensibility, reliability, performance, scalability, mantainability, availability, security, backward compatibility and usability. These quality attributes drive the software architecture to a certain extent and are popularly known as non-functional requirements.