8.7. Conclusion

In this chapter we examined the adventure builder enterprise application, in particular its Web service implementations. We discussed the rationale for our different Web service application design choices and illustrated how we went about implementing these various endpoints and communication patterns. Drawing on examples from the application, we tried to bring to life many of the Web service architectural and design issues.

The chapter covered the details of Web service design and implementation, including establishing a service's interaction and processing layers, selecting the appropriate endpoint type, determining the proper granularity, passing parameters between client and service, delegating to business logic, publishing and deploying the service, and client considerations. It also discussed how to extend a Web service's quality of service. It considered strategies such as using context information with messages, relying on a canonical data model, including a correlation identifier, and using registries, among other strategies for adding robustness to a service.

In this book, we have tried to cover the Web service standards as they currently exist and how you can develop Web services on the J2EE platform that conform to these standards. We have also tried to show how you can use the J2EE platform technologies to achieve additional robustness and quality of service beyond the current standards for your Web services.