JAX-WS with JBoss 6 Day 11 : RESTful

Web services have become a standard way to achieve interoperability between systems. There are two main approaches for developing web services; one is by using the Simple Object Access Protocol (SOAP) and the other is by using the Representational State Transfer (REST) architecture style.

JAX-WS with JBoss 6 Day 10 : Stateful

A service using a SOAP/HTTP binding can use the following three mechanisms for maintaining a session:
• Cookies
• URL Rewriting
• SSL Sessions

JAX-WS with JBoss 6 Day 9 : handler framework

The handler framework is implemented by a JAX-WS protocol binding in both client and server side runtimes.

JAX-WS with JBoss 6 Day 8 : SOAP Fault

In the SOAP Web services world, a fault flows from the server to the client in the form of SOAP fault.

JAX-WS with JBoss 6 Day 7 : Provider API

java.xml.ws.Provider interface offers an alternative to SEIs and may be implemented by services wishing to work at the XML message level.

JAX-WS with JBoss 6 Day 6 : SOAP header

SOAP Header is a mechanism for exchanging contextual data like data related WS-Security, WS-Addressing, WS-AtomicTransaction etc.

JAX-WS with JBoss 6 Day 5 : Asynchronous

An asynchronous invocation of a Web service sends a request to the service endpoint and then immediately returns control to the client program without waiting for the response to return from the service.

JAX-WS with JBoss 6 Day 4 : Dispatch API

The Java API for XML-Based Web Services (JAX-WS) Web service client programming model supports both the Dispatch client API and the Dynamic Proxy client API.

JAX-WS with JBoss 6 Day 1 : Hello World

JBoss 6 ships with JAXWS 2.2 , while Java SE 6 has JAXWS 2.0 itself, so you need to copy all jar files under %JBOSS_HOME%/lib/endorsed to %JAVA_HOME%/jre/lib/endorsed.