Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 5172 invoked from network); 19 May 2005 23:49:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 May 2005 23:49:51 -0000 Received: (qmail 19837 invoked by uid 500); 19 May 2005 23:49:51 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 19782 invoked by uid 500); 19 May 2005 23:49:50 -0000 Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C User List" Reply-To: "Apache AXIS C User List" Delivered-To: mailing list axis-c-user@ws.apache.org Received: (qmail 19768 invoked by uid 99); 19 May 2005 23:49:50 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_60_70,HTML_MESSAGE,SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from smtp2.enomia.com (HELO smtp2.enomia.com) (66.194.55.12) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 19 May 2005 16:49:43 -0700 Received: from MAIL22.eNomia.com ([10.160.16.31]) by smtp2.enomia.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 19 May 2005 19:49:34 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C55CCD.67A0FD6E" Subject: FW: Problem with WSDL??? Date: Thu, 19 May 2005 19:49:32 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Problem with WSDL??? Thread-Index: AcVchs1JYMoK7v76RkKGy7cbMN3RrgARqXZw From: "Ken Noland" To: "axis-c-user@ws.apache.org" <'axis-c-user@ws.apache.org'> X-OriginalArrivalTime: 19 May 2005 23:49:34.0618 (UTC) FILETIME=[68CC07A0:01C55CCD] X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------_=_NextPart_001_01C55CCD.67A0FD6E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hey, =20 I'm not sure if the last email I sent out worked, so here is another copy =20 -----Original Message----- From: Ken Noland=20 Sent: Thursday, May 19, 2005 11:22 AM To: 'axis-c-user@ws.apache.org' Subject: Problem with WSDL??? =20 Hey, =20 I've got an error, and I'm not sure where it is coming from. It could be something server side, but I need to make sure, so I thought I would email you guys and see if any of you could help me out a bit. I got a WSDL document describing to me how to interface with the service and all I have to do is send a basic XML doc back to the server. It is a simple request-response, but instead of the WSDL document being available, it is hidden as a security precaution. =20 Here is the WSDL doc(with a few changes for security reasons) =20 =20 xmlns:apachesoap=3D"http://xml.apache.org/xml-soap" xmlns:impl=3D"urn:doc" xmlns:intf=3D"urn:doc" xmlns:soapenc=3D"http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl=3D"http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap=3D"http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" >=20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 />=20 =20 =20 =20 namespace=3D"urn:doc" use=3D"encoded"/>=20 =20 =20 namespace=3D"urn:doc" use=3D"encoded"/>=20 =20 =20 =20 =20 = =20 =20 =20 =20 and here is my response =20 POST /services/doc User-Agent:Client Host: server:port Content-Type: text/xml; charset=3D"utf-8" Content-Length:537 SOAPAction: "servername:port/service/doc" username password =20 and the response from the server is nothing. I don't get anything back from the server, not even an error, and my receive command times out. Is it something I'm doing on my side, or is there something going on that I don't know about? =20 Unfortunately I do not have access to the server and I would consider myself to be a rookie when it comes to XML. I know that I should be using the WSDL doc namespace in the request, but since that document is unavailable to me, I have to make do with what I have. Perhaps it is a namespace related issue? =20 Or perhaps their services are incorrectly configured, if so, is there a way for me to remotely tell? =20 Thanks, -Ken Noland =20 =20 ------_=_NextPart_001_01C55CCD.67A0FD6E Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hey,

 

I’m not sure if the last = email I sent out worked, so here is another copy

 

-----Original Message-----
From: Ken Noland
Sent: Thursday, May 19, 2005 11:22 = AM
To: = 'axis-c-user@ws.apache.org'
Subject: Problem with = WSDL???

 

Hey,

 

I’ve got an error, and I’m not sure where = it is coming from. It could be something server side, but I need to make sure, = so I thought I would email you guys and see if any of you could help me out a = bit. I got a WSDL document describing to me how to interface with the service = and all I have to do is send a basic XML doc back to the server. It is a simple request-response, but instead of the WSDL document being available, it = is hidden as a security precaution.

 

Here is the WSDL doc(with a few changes for security reasons)

 

<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<wsdl:definitions targetNamespace=3D"urn:doc" xmlns=3D"http://schemas.xmlsoap.or= g/wsdl/" xmlns:apachesoap=3D"http://xml.apache.org/xml-s= oap" xmlns:impl=3D"urn:doc" xmlns:intf=3D"urn:doc" = xmlns:soapenc=3D"http://schemas.x= mlsoap.org/soap/encoding/" xmlns:wsdl=3D"http://schemas.xmlsoap.or= g/wsdl/" xmlns:wsdlsoap=3D"http://schemas.xmlso= ap.org/wsdl/soap/" xmlns:xsd=3D"http://www.w3.org/2001/XM= LSchema">

   <wsdl:message = name=3D"loginGetDecalRequest">
      <wsdl:part name=3D"username" type=3D"xsd:string"/>
      <wsdl:part name=3D"password" type=3D"xsd:string"/>
   </wsdl:message>
   <wsdl:message = name=3D"loginGetDecalResponse">
      <wsdl:part name=3D"loginGetDecalReturn" type=3D"xsd:int"/> =
   </wsdl:message>
   <wsdl:portType name=3D"DOCLogin">
      <wsdl:operation name=3D"loginGetDecal" parameterOrder=3D"username = password">
         <wsdl:input message=3D"impl:loginGetDecalRequest" name=3D"loginGetDecalRequest"/>
         <wsdl:output message=3D"impl:loginGetDecalResponse" name=3D"loginGetDecalResponse"/>
      </wsdl:operation>
   </wsdl:portType>
   <wsdl:binding name=3D"nteloginSoapBinding" type=3D"impl:DOCLogin">
      <wsdlsoap:binding = style=3D"rpc" transport=3D"http://schemas.xmlsoa= p.org/soap/http"/>
      <wsdl:operation name=3D"loginGetDecal">
         <wsdlsoap:operation soapAction=3D""/>
         <wsdl:input name=3D"loginGetDecalRequest">
            <wsdlsoap:body encodingStyle=3D"http://schemas.x= mlsoap.org/soap/encoding/" namespace=3D"urn:doc" use=3D"encoded"/>
         </wsdl:input> =
         <wsdl:output name=3D"loginGetDecalResponse">
            <wsdlsoap:body encodingStyle=3D"http://schemas.x= mlsoap.org/soap/encoding/" namespace=3D"urn:doc" use=3D"encoded"/>
         </wsdl:output> =
      </wsdl:operation>
   </wsdl:binding>
   <wsdl:service name=3D"DOCLoginService"> =
      <wsdl:port binding=3D"impl:docloginSoapBinding" = name=3D"doclogin">
         <wsdlsoap:address location=3D”server address"/>
      </wsdl:port>
   </wsdl:service>
</wsdl:definitions>

 

and here is my response

 

POST /services/doc

User-Agent:Client

Host: server:port

Content-Type: text/xml; = charset=3D”utf-8”

Content-Length:537

SOAPAction: = “servername:port/service/doc”

<soapenv:Envelope = xmlns:impl=3D”urn:doc” xmlns:soapenv=3D”http://schemas.xmlsoap= .org/soap/envelope/” soapenv:encodingStyle=3D”http://schemas.xmlsoap= .org/soap/encoding/”>

<soapenv:Body>

<impl:username>username</impl:username>

<impl:password>password</impl:password>

</soapenv:Body>

</soapenv:Envelope>

 

and the response from the server is nothing. I = don’t get anything back from the server, not even an error, and my receive = command times out. Is it something I’m doing on my side, or is there = something going on that I don’t know about?

 

Unfortunately I do not have access to the server and = I would consider myself to be a rookie when it comes to XML. I know that I = should be using the WSDL doc namespace in the request, but since that document is unavailable to me, I have to make do with what I have. Perhaps it is a namespace related issue?

 

Or perhaps their services are incorrectly configured, = if so, is there a way for me to remotely tell?

 

Thanks,

-Ken Noland

 

 

------_=_NextPart_001_01C55CCD.67A0FD6E--