You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Wagh, Shrikant" <sh...@hp.com> on 2004/01/23 18:49:18 UTC
FW: Unable to invoke the web services using SOAPscope tool.

Hi Jim,

 

Here is the issues I logged on Nov 11, 2003, with Mindreef Support team
(Please take a look at the forwarded e-mail). The only reply I got so
far from MindReef Support Team is, they will look into the issue. You
can check the issues log yourself, if Mindreef maintains the customer
issues. I never heard anything from them afterwards (more than three
months now). This again shows how good their customer support is?

 

Please check the Mindreef customer issues log. You will find all the
information I sent to them, including WSDL file. Test with that WSDL and
let me know if it works. If it works with our WSDL then only I'll be
interested in trying the new 3.0 version, else I won't be interested in
spending my cycles.

 

Hope this makes very clear that my comments are VERY true.  Please do
let me know if you hear anything about the issue I logged from your
customer support.

 

Best regards,

 

HPP/eProfile QA Lead. HP

 

For those who are interested in Web Services testing:

-----------------------------------------------------

I found that WebServiceTester from Optimyz software is a very good tool
for testing any types of web services, and I'm great fan of this tool.
It supports all types of web services, and all simple and complex types
and it very usable than any other tool in the market I ever
used/evaluated. It automatically generates the SOAP requests and invokes
the intended web services. It can perform functional, regression and
load testing of web services. Result analysis and status reporting is
just wonderful.  I'll highly recommend this tool for testing web
services, saves lots of time and efforts in testing web services. For
more information visit http://www.optimyz.com <http://www.optimyz.com/>
. 

 

DISCLAIMER 

================================================================

THESE ARE MY PERSONAL VIEWS/OPINIONS AND DOES NOT REPRESENT HP, AND THE
INFORMATION PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL
THE I/HP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
INFORMATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 

=================================================================

 

 

-----Original Message-----
From: Wagh, Shrikant 
Sent: Monday, December 01, 2003 12:09 PM
To: 'support@mindreef.com'
Cc: Wagh, Shrikant
Subject: Unable to invoke the web services using SOAPscope tool.

 

Hi SOAPscope Support team,
 
I have been evaluating the SOAPscope tool to test our web services and
WSDL file. I'm unable to invoke our web services using SOAPscope tool.
Please find the attached WSDL file for your reference. When I analyzed
this WSDL file, it reported no errors and the WSDL is found to be
correct. In "Service View" screen it does display the correct operation
signatures. I also attached the request generated by SOAPscope and the
received error message when I tried to invoke the web service, at the
end of this email.
 
The same WSDL when tested with other testing tools like
WebServiceTester, it works fine.
 
The web services described in WSDL file are document-literal and take
the XML document as input argument and returns the XML document. I found
that the SOAP request <body> has the wrapper element
<eprofile:eCreateProfile>. 
May I know the reason WHY the XML document passed as input argument is
wrapped in <eprofile:eCreateProfile> element.
 
If the input is "null" then the <body part of the request should be
   <soap:Body>
   </soap:Body>
 
and NOT
 
   <soap:Body>
      <eprofile:createProfile/>
   </soap:Body>
 
If the input is <doc><val>val1</val></doc> then the <body part of the
request should be
   <soap:Body>
        <doc><val>val1</val></doc>
   </soap:Body>
 
and NOT
 
   <soap:Body>
        <eprofile:createProfile>
                <doc><val>val1</val></doc>
        </eprofile:createProfile>
   </soap:Body>
 
I also noticed that the request generated by Axis Client does not have
the wrapper element as it is in the request generated by SOAPscope.
 
I'll highly appreciate your response to this email.
 
Best regards,
Shrikant Wagh
HPP/eProfile QA Lead
Hewlett Packard Company.
 
Request generated by SOAPscope
------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope
   xmlns:eprofile="http://eprofile.globalops.hp.com/eProfileService"
   xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
   <soap:Header>
      <eprofile:eProfileHeader>
         <ApplicationID>111</ApplicationID>
         <LanguageCode>111</LanguageCode>
         <HPPID>111</HPPID>
         <SiteMinderSID>111</SiteMinderSID>
         <TemplateID>111</TemplateID>
      </eprofile:eProfileHeader>
   </soap:Header>
   <soap:Body>
      <eprofile:createProfile/>
   </soap:Body>
</soap:Envelope>

 

 

Response

---------------


Malformed XML: 


Line: 4, Column: 1 in the original XML stream.

XML document structures must start and end within the same entity.
<http://localhost:7103/main/message?msgType=response&mid=69&type=XML&set
Type=1#theXmlError#theXmlError> 



The following has been reformatted for readability and may not match the
original content.

<HTML>
   <HEAD>
      <TITLE>Redirection</TITLE>
   </HEAD>
   <BODY>
      <H1>Redirect</H1>
   </BODY>