Merge pull request #90 from javaee/revert-82-jon_branch

Revert "Removed JAX-WS chapters."

Author: jepatt

src/main/jbake/content/ejb-basicexamples004.adoc

@@ -15,7 +15,9 @@ A Web Service Example: helloservice
 
 This example demonstrates a simple web service that generates a response
 based on information received from the client. `HelloServiceBean` is a
-stateless session bean that implements a single method: `sayHello`.
+stateless session bean that implements a single method: `sayHello`. This
+method matches the `sayHello` method invoked by the client described in
+link:jaxws002.html#BNAYX[A Simple JAX-WS Application Client].
 
 The following topics are addressed here:
 
@@ -45,7 +47,9 @@ not be declared `static` or `final`.
 * Business methods that are exposed to web service clients must be
 annotated with `javax.jws.WebMethod`.
 * Business methods that are exposed to web service clients must have
-JAXB-compatible parameters and return types.
+JAXB-compatible parameters and return types. See the list of JAXB
+default data type bindings at link:jaxws003.html#BNAZC[Types Supported by
+JAX-WS].
 * The implementing class must not be declared `final` and must not be
 `abstract`.
 * The implementing class must have a default public constructor.
@@ -201,3 +205,5 @@ Methods, enter a name as the parameter to the `sayHello` method.
 +
 The sayHello Method invocation page opens. Under Method returned, you'll
 see the response from the endpoint.
+
+

src/main/jbake/content/ejb-intro004.adoc

@@ -383,7 +383,9 @@ Web Service Clients
 ~~~~~~~~~~~~~~~~~~~
 
 A web service client can access a Java EE application in two ways.
-First, the client can access a web service created with JAX-WS. Second, a web service client can
+First, the client can access a web service created with JAX-WS. (For
+more information on JAX-WS, see link:jaxws.html#BNAYL[Chapter 29,
+"Building Web Services with JAX-WS"].) Second, a web service client can
 invoke the business methods of a stateless session bean. Message beans
 cannot be accessed by web service clients.
 
@@ -448,3 +450,5 @@ parameters in remote methods should be relatively coarse-grained. A
 coarse-grained object contains more data than a fine-grained one, so
 fewer access calls are required. For the same reason, the parameters of
 the methods called by web service clients should also be coarse-grained.
+
+

src/main/jbake/content/jaxrs.adoc

@@ -2,7 +2,7 @@ type=page
 status=published
 title=Building RESTful Web Services with JAX-RS
 next=jaxrs001.html
-prev=webservices-intro003.html
+prev=jaxws005.html
 ~~~~~~
 Building RESTful Web Services with JAX-RS
 =========================================

src/main/jbake/content/jaxws.adoc

@@ -0,0 +1,31 @@
+type=page
+status=published
+title=Building Web Services with JAX-WS
+next=jaxws001.html
+prev=webservices-intro003.html
+~~~~~~
+Building Web Services with JAX-WS
+=================================
+
+[[BNAYL]]
+
+[[building-web-services-with-jax-ws]]
+29 Building Web Services with JAX-WS
+------------------------------------
+
+
+This chapter describes Java API for XML Web Services (JAX-WS), a
+technology for building web services and clients that communicate using
+XML. JAX-WS allows developers to write message-oriented as well as
+Remote Procedure Call–oriented (RPC-oriented) web services.
+
+The following topics are addressed here:
+
+* link:jaxws001.html#A1250966[Overview of Java API for XML Web Services]
+* link:jaxws002.html#BNAYN[Creating a Simple Web Service and Clients with
+JAX-WS]
+* link:jaxws003.html#BNAZC[Types Supported by JAX-WS]
+* link:jaxws004.html#BNAZD[Web Services Interoperability and JAX-WS]
+* link:jaxws005.html#BNAZE[Further Information about JAX-WS]
+
+

src/main/jbake/content/jaxws001.adoc

@@ -0,0 +1,55 @@
+type=page
+status=published
+title=Overview of Java API for XML Web Services
+next=jaxws002.html
+prev=jaxws.html
+~~~~~~
+Overview of Java API for XML Web Services
+=========================================
+
+[[A1250966]]
+
+[[overview-of-java-api-for-xml-web-services]]
+Overview of Java API for XML Web Services
+-----------------------------------------
+
+In JAX-WS, a web service operation invocation is represented by an
+XML-based protocol, such as SOAP. The SOAP specification defines the
+envelope structure, encoding rules, and conventions for representing web
+service invocations and responses. These calls and responses are
+transmitted as SOAP messages (XML files) over HTTP.
+
+Although SOAP messages are complex, the JAX-WS API hides this complexity
+from the application developer. On the server side, the developer
+specifies the web service operations by defining methods in an interface
+written in the Java programming language. The developer also codes one
+or more classes that implement those methods. Client programs are also
+easy to code. A client creates a proxy (a local object representing the
+service) and then simply invokes methods on the proxy. With JAX-WS, the
+developer does not generate or parse SOAP messages. It is the JAX-WS
+runtime system 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
+independence of the Java programming language. In addition, JAX-WS is
+not restrictive: A JAX-WS client can access a web service that is not
+running on the Java platform and vice versa. This flexibility is
+possible because JAX-WS uses technologies defined by the W3C: HTTP,
+SOAP, and WSDL. WSDL specifies an XML format for describing a service as
+a set of endpoints operating on messages.
+
+
+[width="100%",cols="100%",]
+|=======================================================================
+a|
+Note:
+
+Several files in the JAX-WS examples depend on the port that you
+specified when you installed GlassFish Server. These tutorial examples
+assume that the server runs on the default port, 8080. They do not run
+with a nondefault port setting.
+
+|=======================================================================
+
+
+