Friday, May 2, 2008
In JAX-WS, a web service process invocation is representing by an XML-based protocol such as SOAP. The SOAP specification defines the structure, encoding rules, and conventions for representing web service invocations and responses. These calls and responses are transmitting over the HTTP as SOAP messages.
JAX-WS API hides the complexity of forming SOAP messages from the application developer. On the server side, the developers specify the web service operation by an interface written in the Java programming language. The developer codes one or more classes to implement this web service operation. A client forms a proxy and then simply invokes methods on the proxy. With JAX-WS, the developer does not produce or parse SOAP messages. JAX-WS converts the API calls and responses to and from SOAP messages.
JAX-WS make clients and web services have more advantage because Java is platform independent language. JAX-WS is not restrictive one (i.e.,) a JAX-WS client can access the web service that is running on any platform. JAX-WS gives more flexibility because it uses W3C technologies like HTTP, SOAP, and the WSDL.
Earthlink
Netscape
Netvouz
RawSugar
Shadows
Sphinn
StumbleUpon
Yahoo MyWeb




1 Comments:
At May 5, 2008 1:49 AM,
Live like you're going to die tomorrow..-JILL said…
Hey.. Short and sweet info about JAX-WS. Really interesting. Expecting more information about upcoming technology in this blog.
Post a Comment
<< Home