Tuesday, December 23, 2008
Building Spring 2 Enterprise Applications
Product Description
Spring has made a remarkable rise in popularity since its conception in 2002. Many users have found the lightweight, open source Spring Framework 2.x ideal for building their applications in Java EE environments. Written by Interface21, Building Spring 2 Enterprise Applications will take developers through the following:
* Covers the first steps of using Spring while discussing the relevant technologies that Spring can be integrated with, what to be aware of, and how working with Spring makes them easier to use
* Focuses on the most useful features of Spring, including persistence and transaction management as well as the complete Spring web tools portfolio
* Introduces three-tier application design and how to test these designs
What you’ll learn
* Get a gentle introduction to the Spring Framework 2.x and the application context.
* Access and persist your data with Spring and its modules for JDBC, Hibernate, iBATIS, JDO, OpenJPA, and others.
* Use Spring for business logic and transaction management and support.
* Work with Spring’s web-tier solutions including Spring MVC web framework, web forms, web flow, as well as integration with other web solutions.
* See how Aspect-Oriented Programming (AOP) is important and what role it plays in Spring and your three-tier enterprise application.
* Test and deploy Spring.
Who is this book for?
Ideal for those new to J2EE/Java EE, this book provides a broad insight into Spring’s enterprise Java-based technologies, while showing how to use Spring correctly in applications lowers the enterprise Java learning curve without going into too much detail.
Product Details
* Amazon Sales Rank: #459548 in Books
* Published on: 2007-08-27
* Original language: English
* Number of items: 1
* Binding: Paperback
* 335 pages
Editorial Reviews
About the Author
Interface21 is a privately held international company made up of consultants who build, use, and train for the most popular application framework in the world. Springframework.com is operated by Interface21 Limited, a privately owned company. The developers who brought you the Spring framework also provide training, consulting, and support. Interface21 also has partnerships in Europe and North America, partnering with companies that value a high quality of service and have experience with Spring, as well as partnerships with developers who deliver .NET services. Interface21 wants to be your first partner for enterprise development.
Seth Ladd is a software engineer and professional Spring Framework
trainer and mentor specializing in object-oriented and testable web applications.
He started his own company building websites at age 17, but now
enjoys having a real job. Currently working for Camber Corporation, Seth
has built and deployed systems for NEC, Rochester Institute of Technology,
Brivo Systems, and National Information Consortium. He has
architected and developed enterprise applications in Java and C for both
the server and remotely connected embedded devices. He enjoys speaking and teaching, and
is a frequent presenter at local Java user groups and at corporate developer conferences. Seth
is very thankful for living and working in Kailua, Hawaii, with his wife.
Bram Smeets is a Java architect with over 8 years’ experience in developing enterprise Java applications. Currently, Bram is technical director at JTeam (www.jteam.nl), a Java software development company based in the Netherlands and senior consultant at SpringSource (www.springsource.com). He is a regular speaker at technology–focused conferences like The Ajax Experience and SpringOne. Using GWT, Bram has delivered several successful RIA projects at JTeam. He also delivered Ajax and GWT trainings at several companies.
Customer Reviews
Where's the Beef?2
I expected much more from Interface21 (now SpringSource), the developers of Spring. There is a good discussion on architecture and separation of concerns via dependency injection. There is also a good introduction to Aspect Oriented Programming (AOP). Too much space is dedicated to Spring MVC which is probably the weakest and least popular part of the Spring framework.
Integration with ORMs like Hibernate and iBatis is mentioned in passing, but there are no concrete examples. There is very little in the way of explaining integration with other web tier frameworks such as Struts, WebWork, Tapestry, etc. Given that Spring is supposedly lightweight and not intrusive,integration with other frameworks should be covered in depth. No mention of common issues like trying to inject a Spring bean into a Servlet.
a4
The authors of Building Spring 2 Enterprise Applications presented from Java developer's perspective how would web software required to persist
data be realized in model-view-controller pattern using framework. For those who were amazed by the popularity of Spring but no chance in
exploring till now, this book might just be the practical guide with coherent topics leaving advance counterparts by further references.
Rather than essential, framework helped solve problem in proved way so purposes of using Spring were illustrated by means of comparison. After
all, software was about integration. With inversion of control pattern, dependent deployment used to be static or via looking up mechanisms like
naming service was demonstrated to be injected at run time by configuration. Aspect oriented programming was then described to overcome the
limitations of either composition or inheritance in flexibly adding functionality to existing classes anywhere. Such cross-cutting concerns were
widely applied to areas like logging, debugging, and resource pooling. Besides, JDBC was commented to be so low level that its use introduced
management issues like exception, resource, and transaction avoidable by abstractions. While keeping batch executions for performance, we were
allowed to be more object-oriented and declaring transaction in interfacing with relational database. By mastering these concepts, one would
proceed to architect web in MVC. Not only the view could be chosen amongst Velocity, Free Marker, XSLT, PDF, Excel, and Jasper Reports other
than conventional JSP, but also the logic could be tested independent of the container.
The latest version of Spring was 2.5 while the book covered 2.0 which was 2 years ago. Its source code could neither be compiled nor executed
due to separately downloadable missing libraries, classes left as exercises, and configuration files. A sample application throughout chapters of the
book that could be run out of the box was important especially for beginners
Excellently Written5
This book was exactly what I was looking for - short (300+ pages), covers several areas in both a concise and easily understandable manner. What I was looking for was a more in-depth explanation of configuring the applicationContext.xml, which I felt the authors covered well. The bonus was an excellent introduction to Spring AOP. I didn't really buy the book for that purpose, but the AOP introduction gave me enough footing to feel like I can begin introducing its concepts into my projects.
Labels:
Applications,
Interface21

