Sign in to save your progress (Learn more)
Saving your progress (Learn more)
1. Understand JAX-WS concepts
JAX-WS 2.0 replaces the Java API for XML-based RPC (JAX-RPC), moving Java web service development toward a document-oriented approach and away from one based on remote procedure calls. Get a thorough grasp of JAX-WS concepts by understanding how JAX-WS differs from its predecessor API.
2. Build and deploy JAX-WS web services with Java SE 6
With JAX-WS, you have a choice between top-down and bottom-up approaches to web service configuration. In the top-down approach, you start with a Web Services Description Language (WSDL) document and then generate the necessary Java code. In the bottom-up approach, you code the web services first and then generate the WSDL from the web service. Get hands-on practice with both techniques using Java SE 6.
3. Build JAX-WS services and clients for IBM WebSphere Application Server Community Edition
Learn how to build JAX-WS clients and services with IBM's freely available Java EE application server -- WebSphere Application Server Community Edition, based on Apache Geronimo 2.0 -- and get started on a JAX-WS web service project.
4. Leverage open source frameworks' support for JAX-WS in IBM WebSphere Application Server
Apache Axis2 and Apache CXF are open source web services stacks that support JAX-WS. Instead of using WebSphere’s own JAX-WS engine, you might want to leverage the Axis2 or Apache CXF engine—for example, to use features specific to the Apache runtimes, or reuse code, or achieve application consistency in a multivendor or multiversion environment. Get a handle on JAX-WS configuration in Axis2 and CXF, then see how to use an application EAR with Axis2 or CXF embedded in it with WebSphere Application Server V6.1 or V7.
5. Use the JAX-WS client APIs with WebSphere Application Server
Progress through a series of exercises for creating web service clients using the WebSphere Application Server V6.1 Feature Pack for Web Services and the JAX-WS client APIs. Start by creating a dispatch client using; then create a dynamic proxy client, and finally an asynchronous web client that uses polling and callback models.
Rate this content
Give us feedback
Submission failed. Please try again.
Please complete one of the following questions before submitting.
Sign into give us your feedback
