Summary

This tutorial has given you an in-depth look into enterprise Web services demonstrated on the Apache Geronimo application server. You should now be familiar with JAX-RPC-related concepts and their integration into the J2EE 1.4 platform. You've learned about several options for accessing external Web services and the exposure of your own Web services from both the Web tier and the EJB tier of your J2EE applications. With the help of the BookShop example application, this tutorial has shed some light on the configuration jungle you must navigate when developing Web services-enabled applications for the J2EE 1.4 platform.

A brief look ahead

Part 2 of this tutorial series will concentrate on registry access, SOAP attachments, message handlers, and Web services security. It will discuss and demonstrate the following aspects of enterprise Java Web services in detail:

• The Java API for XML Registries (JAXR): JAXR defines a standard Java API for accessing and programmatically interacting with various types of metadata registries, such as Universal Description, Discovery, and Integration (UDDI) and Electronic Business XML (ebXML).
• The SOAP with Attachments API for Java (SAAJ): SAAJ provides convenient ways to access the various parts of SOAP messages. This includes message headers and the option to include binary message attachments.
• Message handlers: Learn several ways to implement message IDs for conversational Web services, the implementation of appropriate message-encryption mechanisms following the WS-Security standard, and suitable logging strategies for Web service-related activities.
• SOAP faults: Gain insight into exception handling for Web services, including standard SOAP faults, Web services-related exception types, and checked user exceptions.
• The future of J2EE Web services: Get a preview of Web service-related plans for the upcoming J2EE 5 platform. You'll see that many of the pitfalls developers have encountered in the J2EE 1.4 platform have been addressed.

Acknowledgement

The author would like to express his sincere thanks to the Geronimo community, which kindly helped during the development of this tutorial through mailing lists and IRC chats. Special thanks to David Jencks, who spent considerable time explaining Geronimo-specific Web services handling and fixing several bugs encountered during the development of the BookShop example code.

7 of 10 | Previous | Next

Comments

Back to top

Table of contents

• Before you start
• Extending BookShop with JAX-RPC
• Exposing Web services from BookShop
• Web service clients in BookShop
• Required deployment artifacts
• BookShop in action
• Summary
• Download
• Resources
• About the author

---

7 of 10 | Previous | Next

Next steps from IBM

With the WebSphere Application Server you can benefit from the simplified EJB 3.0 development experience, new persistence model, and interceptors.

---

• Try: Download a free trial version of WebSphere Application Server Community Edition, the lightweight Java 5 application server with robust EJB 3.0 funtionality.
• Article: Learn how call patterns and components involved in making calls to EJB components deployed in the EJB container operate in WebSphere Application Server.
• Tutorial: This tutorials shows you how to create an enterprise J2EE application that implements both Plain Old Java Object (POJO) and EJB Web services endpoints.
• Demo: Watch this demo and learn how to configure and use the WebSphere Application Server and the Eclipse IDE with the Web Tool Project Platform.
• Buy: WebSphere Application Server

Dig deeper into Open source on developerWorks

Try IBM PureSystems. No charge.

Experience today!

---

Get started with the cloud-based trial and pattern development kit.