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: 30

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 Blueprints:... | Main | JBI/SOA Tips: Expose... »
Monday Apr 23, 2007
Apr
23
JBI/SOA Tips: Expose Request/Response Message Exchange Patterns to external Clients

When exposing a service interface to external clients, always expose Request/Response Message Exchange Patterns (MEPs) as much as possible since they work best with HTTP transports and provide interoperability.

You should keep in mind that One-Way Message Exchange Patterns are for non-HTTP transports. When constructing your WSDL, always stay away from exposing  solicit-response and notification MEPs to external clients.

Moreover, if there is one and only one binding that you want to expose to an external client, expose HTTP as the default transport protocol binding to external clients. This will ensure interoperability support. You can consider also exposing other transport protocol bindings externally as long as you also expose a HTTP transport binding.

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


 

Posted at 01:23AM Apr 23, 2007 by Suresh Gopalan in A Tip a Day  |  Listen to this article Listen to this entry  |  Comments added Comments[0]
Tags:
Share This Post: del.icio.us | furl | simpy | slashdot | technorati | digg

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]