2. Using the Tutorial Examples 3. Getting Started with Web Applications 5. JavaServer Pages Technology 7. JavaServer Pages Standard Tag Library 10. JavaServer Faces Technology 11. Using JavaServer Faces Technology in JSP Pages 12. Developing with JavaServer Faces Technology 13. Creating Custom UI Components 14. Configuring JavaServer Faces Applications 15. Internationalizing and Localizing Web Applications Creating a Simple Web Service and Client with JAX-WS Requirements of a JAX-WS Endpoint Coding the Service Endpoint Implementation Class Building, Packaging, and Deploying the Service Building, Packaging, and Deploying the Service Using NetBeans IDE Building, Packaging, and Deploying the Service Using Ant Testing the Service without a Client Building and Running the Client Web Services Interoperability and JAX-WS Further Information about JAX-WS 17. Binding between XML Schema and Java Classes 19. SOAP with Attachments API for Java 21. Getting Started with Enterprise Beans 23. A Message-Driven Bean Example 24. Introduction to the Java Persistence API 25. Persistence in the Web Tier 26. Persistence in the EJB Tier 27. The Java Persistence Query Language 28. Introduction to Security in the Java EE Platform 29. Securing Java EE Applications 31. The Java Message Service API 32. Java EE Examples Using the JMS API 36. The Coffee Break Application | Chapter 16Building Web Services with JAX-WSJAX-WS stands for Java API for XML Web Services. JAX-WS is a technologyfor building web services and clients that communicate using XML. JAX-WS allows developersto write message-oriented as well as RPC-oriented web services. In JAX-WS, a web service operation invocation is represented by an XML-based protocolsuch as SOAP. The SOAP specification defines the envelope structure, encoding rules, andconventions for representing web service invocations and responses. These calls and responses aretransmitted as SOAP messages (XML files) over HTTP. Although SOAP messages are complex, the JAX-WS API hides this complexity from theapplication developer. On the server side, the developer specifies the web service operationsby defining methods in an interface written in the Java programming language. The developeralso codes one or more classes that implement those methods. Client programs arealso easy to code. A client creates a proxy (a local object representingthe service) and then simply invokes methods on the proxy. With JAX-WS, thedeveloper does not generate or parse SOAP messages. It is the JAX-WS runtimesystem that converts the API calls and responses to and from SOAP messages. With JAX-WS, clients and web services have a big advantage: the platform independenceof the Java programming language. In addition, JAX-WS is not restrictive: a JAX-WSclient can access a web service that is not running on the Javaplatform, and vice versa. This flexibility is possible because JAX-WS uses technologies definedby the World Wide Web Consortium (W3C): HTTP, SOAP, and the Web ServiceDescription Language (WSDL). WSDL specifies an XML format for describing a service asa set of endpoints operating on messages. Copyright © 2010, Oracle and/or its affiliates. All rights reserved.Legal Notices |