My blog has moved and can now be found at

No action is needed on your part if you are already subscribed to this blog via e-mail or its syndication feed.

Tuesday, February 13, 2007
« SOA Practitioners' Guide | Main | Comparison of Web Services Stacks »

Both Paul Fremantle in the comments on my previous entry and Sanjiva Weerawarana in his blog entry confirm that the option of moving away from serialization to handling the raw XML messaging is something that was designed into the Axis2 core but was not something that the majority of developers seem to be comfortable with. Very much appreciate the information. Would love to see some tutorials around this (if it is not there already) on either the WSO2 or Axis2 sites.

Sanjiva also noted the need to define a benchmark for testing that takes into account a lot more of the factors that I noted in my previous entry and offered to host it as an open source project.

So to start, what is needed would be some sort of a "real" application against which the tests could be run. Hmm... I'll throw one out for consideration. Have you thought about running your tests against the WS-I sample application?

According to the WS-I web site:

"The Sample Application presents a high-level, interoperable example of a supply chain management application in the form of a set of Use Cases that demonstrate use of Web services that conform to the Basic Profile 1.0."

Currently the Sample Application has been implemented by BEA Systems, Bowstreet, Corillian, IBM, Microsoft, Nokia, Novell, Oracle, Quovadx, SAP and Sun Microsystems (On a variety of web services stacks to be sure). Source code is available for download on the WS-I site.

Please keep in mind that I am throwing this out after about 5 minutes of thinking and have not really explored any of the details such as possible licensing restrictions by WS-I etc. Something to consider....

2/13/2007 12:27 AM Eastern Standard Time  |  Comments [3]  |  Disclaimer  |  Permalink   
Wednesday, February 14, 2007 5:04:34 AM (Eastern Standard Time, UTC-05:00)
The WSO2 developer portal had lots of articles and tutorials on Axis2. check out
Saturday, February 17, 2007 1:10:28 PM (Eastern Standard Time, UTC-05:00)

Have you had a look at Frank Cohen's work on FastSOA? Frank goes into some detail on moving away from the XML <-> Java Object approach and explores XQuery in some detail. He has also published a book on the subject.

Here is one of Frank's articles:

FastSOA: Accelerate SOA with XML, XQuery, and native XML database technology -- The role of a mid-tier SOA cache architecture
Pat Podenski
Saturday, February 17, 2007 9:00:38 PM (Eastern Standard Time, UTC-05:00)

Appreciated the pointer to the article. I had not heard of FastSOA before but in reading the article, I found it to be a sensible use of a caching architecture. The core aspects seem to be (1) get away from any perf overhead associated with databinding technologies to directly process the messages using XML technologies (2) implement a caching mechanism using a native XML database.

The interesting thing seems to be that this is positioned as a capability that can front an existing service. I guess my question is why? If I wanted to provide this type of capability, would it simply not make sense to implement it as part of the service design itself? As has been noted before, modern web service stacks such as Axis2 and WCF natively provide the ability to process XML directly and combining it with a caching mechanism should give me the same benefits without the need for another moving piece that I have to worry about.
Anil John
Comments are closed.