book

Beginning Spring Framework 2

Name: Beginning Spring Framework 2
ISBN: 9780470101612

by Bruce Snyder, Sing Li, Anne Horton, Thomas Van de Velde, Naveen Balani, Christian Dupuis

December 2007

Beginner

499 pages

13h 6m

English

Wrox

Read now

Unlock full access

Copyright
About the Authors
Credits
Acknowledgments
Introduction
How to Use This BookConventionsDownloads for the BookErratap2p.wrox.com
1. Jump Start Spring 2
1.1. All About Spring1.2. Focus on Simplicity1.3. Applying Spring1.3.1. Creating a Modularized Application1.3.1.1. Decoupling at the Interface1.3.1.2. Creating the Result Writer Components1.3.1.3. Putting the Application Together1.3.1.4. Mixing and Matching Components1.3.2. Using Spring to Configure a Modularized Application1.3.2.1. ApplicationContext is a BeanFactory1.3.2.2. Providing the Spring Container with Wiring Instructions1.3.2.3. Creating and Wiring Java Beans1.3.2.4. Adding a Logging Configuration File1.3.3. Wiring Beans Automatically by Type1.3.4. Understanding Spring's Inversion of Control (IoC) Container1.3.4.1. Dependency Injection1.4. Adding Aspect-Oriented Programming to the Mix1.4.1. Adding a Logging Aspect1.4.1.1. Wiring in AOP Proxies1.4.1.2. Matching Join Points via AspectJ Pointcut Expressions1.5. Beyond Plumbing — Spring API Libraries1.5.1. Using Spring APIs To Facilitate Application Creation1.6. Summary
2. Designing Spring Applications
2.1. Overview of the PIX Album-Management System2.1.1. The PIX System Requirements2.1.1.1. PixUser Requirements2.1.1.2. Album Viewer Requirements2.1.1.3. Affiliate Requirements2.1.1.4. External Interfacing Requirements2.2. Discovering the Domain Model2.2.1. The PixUser POJO2.2.2. The Affiliate POJO2.2.3. The Picture Object2.2.4. The Album POJO2.2.5. The Comment POJO2.2.6. The POJO Relationships2.2.6.1. Adding POJO Operations to Support Relationships2.2.6.2. Establishing POJO Identity2.2.6.2.1. Why the Java Platform Default Implementation Is Not Adequate2.2.6.3. The Appeal of a Nonintrusive Framework2.3. The Importance of Unit Testing2.3.1. POJO-Based Design and Containerless Unit Testing2.3.2. Regression Testing2.3.3. Working with a Unit-Testing Framework2.3.3.1. Running Test Cases2.4. Summary
3. Spring Persistence Using JPA
3.1. Java Persistence3.1.1. JDBC Architecture3.1.2. Traditional JDBC Approach3.2. DAO — Unifying Data Access3.2.1. Spring DAO Support3.2.1.1. Spring Template Classes3.2.1.1.1. Using the JDBC Template3.2.1.1.2. About DataSource Injection3.2.2. Spring Exception Translation3.3. Spring and JPA3.3.1. Entities3.3.1.1. Entity Metadata3.3.1.2. Entity Manager3.3.1.3. Container-Managed Entity Managers3.3.1.4. Application-Managed Entity Managers3.3.1.5. Entity States3.3.1.6. Entity Relationships3.3.1.7. One-to-One Entity Relationship3.3.1.8. One-to-Many Entity Relationship3.3.1.9. Many-to-One Entity Relationship3.3.1.10. Many-to-Many Relationship3.3.1.11. Entity Relationship Direction3.3.1.12. Entity Inheritance Mapping3.3.1.13. Persisting Entities3.3.1.14. Removing Entity Instances3.3.1.15. Creating Database Queries3.3.1.16. Persistence Unit3.3.1.17. Persistence Context3.3.2. Spring as a JPA Container3.3.3. About JPA APIs3.3.4. JPA the Easy Way — Using Annotations3.3.4.1. JPA Entity Annotation3.3.5. SPRING JPA Exception Translation3.3.6. SPRING JPA DAOs3.3.6.1. JpaDaoSupport and JpaTemplate Classes3.3.7. Spring JPA Configuration3.3.7.1. Wiring a DataSource to EntityManagerFactory3.3.7.2. Configuring JPA Provider3.3.7.3. Changing JPA Providers3.4. Persistence and the PIX Domain Model3.4.1. Persisting The PixUser POJO3.4.2. Implementing PixUser Repository DAO3.4.3. Implementing the Album Repository DAO3.5. Testing the Persistence Layer3.5.1. Spring Test Support3.5.2. Executing the Persistence Test Suite3.5.3. Testing the PIX Repositories3.6. Summary
4. Using Spring MVC to Build Web Pages
4.1. The MVC Architectural Pattern4.1.1. The Sample Application's Architecture4.2. Spring MVC Development4.2.1. Processing Web Requests with Controllers4.2.1.1. Dispatching Requests to Controller Classes4.2.1.2. Mapping URLs to Controllers4.2.1.3. Creating a Basic Controller to Retrieve Albums4.2.1.4. Ensuring Controllers Behave as Expected with Unit Tests4.2.1.5. Using the Spring Mock Package for Unit Testing4.2.2. Presenting the Model with a View4.2.2.1. Resolving View Names4.3. Getting Data from the User with Forms4.3.1. A Basic Form-Submission Workflow4.3.1.1. Understanding Form Submissions in Spring MVC4.3.2. Using the Form View4.3.2.1. Passing Reference Data to the Form View4.3.2.2. Populating the Model4.3.2.3. Implementing Form Validation4.4. When Things Go Wrong4.5. Summary
5. Advanced Spring MVC
5.1. Submitting a Form Across Multiple Pages5.1.1. Adding Pictures to an Album5.1.2. Developing Wizard Form Pages5.1.3. Implementing Wizard Form Actions5.1.4. Validating Data Submitted Through a Wizard5.2. Uploading Files5.3. Getting More Stuff Done with the Same Controller5.4. Creating a Different View5.4.1. Your First View5.4.2. Saving an Album to PDF5.4.3. Generating an RSS Feed5.5. Personalization5.5.1. Retrieving Text Labels from a Message Source5.5.2. Displaying Application Labels in a Different Language5.5.3. Changing the Application's Language Settings5.5.4. Allowing the User to Personalize the Application5.6. Summary

6. Spring Web Flow
6.1. Examining a Sample Work Flow for Loan Applications6.2. Introducing Spring Web Flow6.2.1. How SWF Works with Spring MVC6.2.1.1. Spring Web Flow Configuration6.2.2. Launching Flows6.3. Implementing SWF in the PixWeb Application6.3.1. The Login Flow6.3.1.1. The Login Flow Beans XML6.3.1.1.1. The Registration Flow File6.3.1.1.2. The Registration Flow Beans XML6.3.1.1.3. The register.jsp File6.3.1.1.4. The labels_en.properties File6.3.1.1.5. The RegistrationAction.java File6.3.1.1.6. Deploying the Changes6.3.2. The Album Creation Flow6.4. Implementing Actions6.5. Implementing Views6.6. Testing Flows6.7. Architectural Overview6.8. Advanced Topics6.8.1. REST-Style URLs6.8.2. Flow Execution Repositories6.8.3. Flow Execution Repository Implementations6.8.4. Subflows and Attribute Mappers6.8.5. Flow Execution Listeners6.8.6. Exception Handlers6.9. Summary
7. Ajax and Spring: Direct Web Remoting Integration
7.1. Web 2.0: The World of Ajax7.2. Ajax Basics7.2.1. Client-Side Ajax Development with JavaScript7.2.2. The XMLHttpRequest Object7.2.2.1.7.2.2.1.1. Working with XMLHttpRequest Methods and Properties7.2.2.2. Monitoring XMLHttpRequest readyState7.2.2.3. Cross-Browser Differences and the XMLHttpRequest Object7.3. Introducing Direct Web Remoting 27.3.1. Downloading DWR 27.3.2. Working with DWR 27.3.2.1.7.3.2.1.1. Writing Client-Side JavaScript Code with DWR 27.3.2.2. Working with the util.js Library7.3.2.3. The addOptions() Utility Function7.3.2.4. Ajax Versus Spring MVC and Webflow7.3.3. Integrating Spring and DWR 27.3.3.1. The PIX Ajax Album Viewer7.4. Setting up the PIX System for the Ajax Album Viewer7.5. Remoting Requires EAGER Fetching of Contained Objects7.5.1.7.5.1.1. Confirming DWR is Working7.6. Summary
8. Spring and JMS — Message-Driven POJOs
8.1. JMS Concepts8.2. JMS Messaging Domains8.2.1. Point-To-Point Messaging8.2.2. Publish/Subscribe Messaging8.2.3. Persistence versus Durability8.3. The JMS Message8.3.1. Message Header8.3.2. Message Properties8.3.3. Message Selectors8.3.4. Message Body8.4. Producing JMS Messages8.5. Consuming JMS Messages8.5.1. Synchronous Message Consumption8.5.2. Asynchronous Message Consumption8.5.2.1. Message-Driven Beans8.5.2.2. Message-Driven POJOs8.6. The Spring JMS Framework8.6.1. The Spring JMS Packages8.6.2. The JmsTemplate Class8.6.3. Message Listener Containers8.6.4. Destinations8.6.5. Transactions8.7. Configuring Message-Driven POJOS8.8. Realizing the JMS Use Case8.8.1. Modeling Message-Driven POJOs8.8.2. The PIX Web POJOS8.8.3. Changing the PIX Web POJOs Into Message-Driven POJOs8.9. A JMS Provider — Apache ActiveMQ8.10. The JMS Template in the PIX Web Application8.11. Summary
9. Spring Web Services and Remoting
9.1. Web Service Benefits9.2. Introducing Web Services9.3. Web Services Architecture9.3.1. The Network Layer9.3.2. XML9.3.3. SOAP9.3.4. WSDL9.3.4.1. WSDL Document9.3.4.2. WSDL Bindings9.3.5. UDDI9.4. Web Services Interactions9.5. Web Services Interoperability9.5.1. Java Web Service Technologies9.5.2. Java Web Application Web Services9.5.2.1. JSR 181–Compliant Java9.5.2.2. JSR 181 Annotations9.6. Spring Remoting9.7. SOAP Frameworks9.7.1. Java-to-XML Bindings9.7.2. XFire9.7.2.1. Aegis Binding9.8. Spring Web Services with XFire9.9. Realizing the PIX AffiliateManagement Use Case9.10. Invoking Web Services9.11. SOAP Handlers9.11.1. Testing SOAP Handlers with XFire9.12. Summary
10. Web Service Consumer and Interoperation with .NET
10.1. Creating Web Service Consumers — Overview10.2. Describing Web Services with WSDL10.3. Creating a Web Service Consumer with XFire10.3.1. The XFire Maven Plugin10.3.2. Invoking Web Service Methods via XFire-Generated Stubs10.4. Understanding the E-Mail-Validation Web Service Consumer in PIX10.4.1. Examining a WSDL Document10.4.2. WSDL Description of a Web Service Endpoint10.5. Generating Web Service Stubs from WSDL Using XFire10.5.1. The XFire WsGen Tool10.5.2. Generated Interface for Invocation of Web Service10.6. Creating a Web Service Consumer with XFire-Generated Stubs10.7. Add a Web Service Consumer to PIX10.8. Web Service Interoperability10.8.1. WS-I and Web Service Interoperability10.8.2. Expose PIX Service for .NET Web Service Consumers10.9. Summary
11. Rapid Spring Development with Spring IDE
11.1. Brief Feature Overview11.2. Installing and Setting Up Your Eclipse Environment11.2.1. Installing Spring IDE11.2.2. Preparing an Eclipse Project11.2.2.1. Converting a Project to a Spring Project11.2.2.2. Adding Bean Definition Files11.3. Support for Spring Beans Configuration Files11.3.1. Viewing Spring Bean Definitions11.3.1.1. Using the Tree View of Spring Bean definitions11.3.1.2. Using the Dependency Graph for Bean Definitions11.3.2. Validating Spring Bean Definition Files11.3.2.1. Understanding Config Sets in the Context of Validation11.3.2.2. Starting Validation11.3.3. XML Editing11.3.3.1. Content Assist11.3.3.2. Hyperlink11.3.3.3. Contextual Hover Information11.3.4. Searching for and Navigating to Bean Definitions11.4. Visual Support for Spring AOP Configurations11.4.1. Enabling AOP Support for Spring Projects11.4.2. Working with Spring IDE's AOP Support11.4.3. Integration with the AspectJ Development Tools11.5. Web Flow Development with Spring IDE11.5.1. Setting Up Your Spring Web Flow Project11.5.2. Validating Spring Web Flow Definition Files11.5.3. Editing Spring Web Flow Definition Files11.5.4. Graphical Editor for Web Flow Definitions11.5.4.1. Opening and Working the Graphical Web Flow Editor11.5.4.2. Exporting and Printing Web Flow Definitions11.6. Summary
12. Spring AOP and AspectJ
12.1. Comparing Aspect-Oriented Programming to Object-Oriented Programming12.1.1. What Is AOP?12.1.2. Crosscutting Concerns12.1.2.1. AOP Concepts and Terminology12.1.2.2. What Does This All Mean?12.1.2.3. Refactoring fetchdata()12.2. AOP in Spring12.3. XML Schema-Based Support12.3.1. The AOP Namespace Explored12.3.1.1. Defining Aspects12.3.1.2. Defining Pointcuts12.3.1.3. Defining Advice12.3.1.3.1. Before Advice12.3.1.3.2. After Returning Advice12.3.1.3.3. After Throwing Advice12.3.1.3.4. After Advice12.3.1.3.5. Around Advice12.3.2. Advice Parameters12.4. AspectJ Support12.4.1. @AspectJ Explored12.4.1.1. @AspectJ Pointcuts12.4.1.2. Enabling @AspectJ Style of Configuration12.4.2. @AspectJ-Style Advice12.4.2.1. Before Advice12.4.2.2. After Returning Advice12.4.2.3. After Throwing Advice12.4.2.4. After (Finally) Advice12.4.2.5. Around Advice12.4.2.6. Advice Parameters12.5. Performance Monitoring with AOP and JETM12.5.1.12.5.1.1. Programmatic Monitoring With JETM12.5.1.2. Declarative Monitoring With JETM12.6. Summary12.7. References
13. More AOP: Transactions
13.1. Understanding Transactions13.1.1. Understanding Spring Transaction Management13.1.1.1. Local Transactions Versus Global Transactions13.1.1.2. Programmatic Transaction versus Declarative Transaction13.1.2. Spring Transaction Abstraction13.1.2.1. The PlatformTransactionManager Interface13.1.2.2. Available Transactional Platforms Support13.1.3. Applying AOP to Transactions13.2. Adding Spring Transaction Support to PIX13.2.1. Selecting the Transaction Manager13.2.1.1. Coding Directly to the JPA Transaction Manager13.2.1.2. Adding Transaction Support13.2.1.3. Using Transaction Annotations13.2.1.3.1. Propagation Property13.2.1.3.2. Transaction Isolation Property13.2.1.4. Read-Only Property13.2.1.5. Rollback Properties13.2.2. Coding Spring Transactions13.2.2.1.13.2.2.1.1. Using the rollbackFor Property13.2.3. Global Transactions13.3. Summary
A. Maven 2 Basics
A.1. Downloading and Installing MavenA.1.1. Downloading and Installing MavenA.2. Directory StructureA.2.1. Maven and the Project Build Life CycleA.2.2. Maven Plug-InsA.2.3. Plug-In MojosA.2.4. The Project Object ModelA.2.5. Maven ArtifactsA.2.6. Dependency ManagementA.2.6.1. Running Only One Unit TestA.2.6.2. Using Wild Cards in Running Unit TestsA.2.6.2.1. Skipping Unit TestsA.2.6.2.2. Obtaining Information on a Specific Mojo of a Plug-InA.3. Summary
B. Spring and Java EE
B.1. A Heavyweight Application Server versus a Lightweight FrameworkB.1.1. The Server-Centric Architecture of Java EEB.1.2. The Lightweight Approach of SpringB.2. Complexity versus SimplicityB.2.1. Complexity Caused by Boilerplate Source Code ExplosionB.2.2. Complexity in Code InterdependencyB.2.3. Simplicity in POJOsB.2.4. A Convergence of IdealsB.3. Java SE Versus the Open-Source CommunityB.3.1. The Spring Open-Source CommunityB.3.2. Toward an Open-Source Java EE Application ServerB.4. Java EE 5 and the Spring FrameworkB.4.1. Java EE Support Modules in Spring Framework 2B.4.2. EJB 3 Persistence Implementation — JPAB.4.3. Declarative Transaction SupportB.4.4. POJOs for EJBsB.4.5. Dependency Injection and EJB 3B.4.6. Parallel Coexistence and CollaborationB.5. Summary
C. Getting Ready for the Code Examples

Content preview from Beginning Spring Framework 2

Chapter 9. Spring Web Services and Remoting

A web service is software that is identified by a URI and whose interfaces and bindings are specified through XML. The web service can then be discovered by other distributed software systems and communicated with via XML-based messages. In its simplest form, a web service can be viewed as a client/server architecture that allows varying systems to interact with one another through the use of industry standards protocols. Web services is an interface or wrapper around disparate system implementations.

Because web services can operate over the Internet, they are accessible from anywhere Internet service is available. This enables applications as well as people to consume these web services in order to achieve business goals. Because web services can run over existing transport infrastructures and web standards, you don't need to install any new infrastructure to use them.

This chapter will cover the server aspect of web services. The next chapter will cover the client aspect. Specifically, this chapter covers the following:

The concepts behind web services
Why you want to use web services
An analysis of the PIX services that need to be exposed
XFire, an open-source web service container
Integrating Spring with XFire
Exposing POJOs as web services
Intercepting web service messages
Creating web service clients and invoking web services

In this chapter, you add new Spring configurations and code to the PIX application to expose PIX functionality as web ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9780470101612Purchase book

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Beginning Spring Framework 2

by Bruce Snyder, Sing Li, Anne Horton, Thomas Van de Velde, Naveen Balani, Christian Dupuis

Chapter 9. Spring Web Services and Remoting

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.