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

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: As... | Main | JBI/SOA Tips: Do not... »
Sunday Apr 29, 2007
Apr
29
JBI/SOA Tips: Be aware of SOAP Verbosity (Message size overhead)

Depending on the nesting levels of the parameter types, XML and SOAP message overhead can grow significantly. As I mentioned in previous blog entries, document/literal always performs much better than other style/use models. Keep in mind that XML data cannot be optimized too much. When using SOAP, the SOAP envelope has to be extracted, the XML information that it contains has to be parsed. SOAP requires type information in every SOAP message. Due to the XML character-set restrictions, binary data when included in XML bloats the payload, and when converted to to a base64 encoded message also requires encoding at the senders end before packaging the document and decoding at the receivers end before parsing the XML payload. You just have to be aware of these issues.

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


Posted at 12:04AM Apr 29, 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]