Chapter 8. J2EE and Web Services
This book has discussed in detail how Java and web services fit together. Web services use standards-based frameworks to extend an application’s reach. However, a web service isn’t the application itself. The web service must still be implemented on a proven application infrastructure—one that supports reliability, availability, serviceability, transactions, security, and other critical enterprise needs. Ultimately, J2EE tries to define just such an infrastructure. Thus, if web services and Java can fit together, and J2EE is the Java form of application infrastructure, the question of how web services fit together with J2EE comes straight to the forefront.
This chapter discusses different approaches of integrating J2EE and web services. How does a web service map into an EJB, a servlet, or J2EE Connector Architecture (CA) adapter? This chapter discusses these topics, looks at some existing standards initiatives, and speculates on what might happen over the next few years.
The SOAP-J2EE Way
Since SOAP is the cornerstone of interoperability and web services, understanding how J2EE and web services work together comes down to analyzing how SOAP and J2EE can work together. SOAP is a wire protocol that can be layered upon other wire protocols such as HTTP, FTP, and SMTP. J2EE supports these Internet protocols through servlets. Therefore, it makes sense that servlets and JSP technology will become the entry point into a J2EE framework for web services. ...
Get Java Web Services now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
