File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Web Services and the fly likes SOAP Protocol Query Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "SOAP Protocol Query" Watch "SOAP Protocol Query" New topic

SOAP Protocol Query

Sachin Dere
Ranch Hand

Joined: Jan 14, 2003
Posts: 80
Hi guys,
I need ur help in understanding the SOAP Protocol/Flow.Well currently we are using Axis SOAP Client to consume a WebService. the problem is we are posting about 6000 records to the WebService and it has to be done pretty quick. But it takes about 2 hours to complete the whole transaction which is ineffeicient for us. We are told that the WebService can process about 14 transactions per second ie thats about 840 transactions per minute.And we are posting only 410 transactions per minute. thats about 6.83 transactions which is relatively slow.
ok Now we looked hard at the SOAP Response generated and it as follows :

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV=
<m:SendMessageResponse xmlns:m="wsdl file path">
<Return xsi:type="xsd:boolean">OK0</Return>

If u notice, there are 5 URLs,Now my bosses want to know if these URLS are actually being referenced? meaning do the WebService actually go to these URLs perform the necessary processing in building up the SOAP body and then sending it to us?
Guys, i know this may sound very stupid but please help me in coming to a conclusion as i have to prove their theory so that we can influence the WebService to respond to us via different mechanism.
Any diagram or Link will be enough and higly appreciated. Also please post ur thoughts on this even though it may not be correct.
I appreciate ur efforts
Sonia Gun

Joined: Oct 15, 2004
Posts: 10

I am a beginner with SOAP but have done a deal in it. Here are my two cents. From the namespaces you use, envelop refers only two. Soap-ENV and xsi, xsd. In anycase they are used to uniquely identify each node. Even if you define a few more namespapces, only the ones refered in the body or header will be processed.
A SOAP application SHOULD include the proper SOAP namespace on all elements and attributes defined by SOAP in messages that it generates. A SOAP application MUST be able to process SOAP namespaces in messages that it receives. It MUST discard messages that have incorrect namespaces and it MAY process SOAP messages without SOAP namespaces as though they had the correct SOAP namespaces. It is not recommended as it may cause scalability issues.
I agree. Here's the link:
subject: SOAP Protocol Query
jQuery in Action, 3rd edition