Gopalan Suresh Raj
Web Cornucopia
Gopalan's Profile
Archives
« November 2009
SunMonTueWedThuFriSat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
     
       
Today
Click me to subscribe Download Open ESB
Syndication
Search

Table of Contents
Tags
bpel choreography ejb esb http integration javacaps javaee javaone jax-ws jbi management openesb orchestration process-oriented rest sca service-oriented soa soap wsdl xml xsd
Links
 
Referrers

Today's Page Hits: 110

Map of Visitors
Locations of visitors to this page
Caveat Emptor
This is my personal weblog. The contents of this Weblog represent my personal opinion which may differ from the official views of my employer, Sun Microsystems, Inc. or any past employers. I do not speak for my employer or any past employers.
View Gopalan Suresh Raj's profile on LinkedIn
« JBI/SOA Tips: Do not... | Main | JBI/SOA Tips: Securi... »
Tuesday May 01, 2007
May
1
JBI/SOA Tips: Stateless vs Stateful

WSDL-based Web Services define a stateless model and an unordered set of operations. WSDL and therefore WSDL-based web services do not have the concept of state. Do not use transport layer features to accomplish state management into your WSDL based web service. Dependency on HTTP and its session support to implement state management into your WSDL-based web services is a bad practice. To avoid issues with scalability, and provide deployment flexibility, web services should be stateless. If you want state management, you have to have the web service consumer implement this functionality.

A better alternative if you want state management, is to consider using BPEL for orchestration. Among other features, BPEL provides:

 

Like this write-up? Subscribe to receive  more  like it.



 

Posted at 12:27AM May 01, 2007 by Suresh Gopalan in A Tip a Day  |  Listen to this article Listen to this entry  |  Comments added Comments[0]

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed

Disclaimer: The contents of this Weblog represent my personal opinion which may differ from the official views of my employer, Sun Microsystems, Inc. or any past employers.



View blog top tags

Enter your email address:

Delivered by FeedBurner

[Valid RSS]