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.
Here I am
Monday, April 11, 2011
Sunday, April 10, 2011
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
• Cookies
• URL Rewriting
• SSL Sessions
Friday, April 8, 2011
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.
Tuesday, April 5, 2011
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.
Monday, April 4, 2011
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.
Thursday, March 31, 2011
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.
Thursday, March 24, 2011
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.
Subscribe to:
Posts (Atom)