Loading ...
Sorry, an error occurred while loading the content.

Server not parsing .NET Req

Expand Messages
  • mcm1303
    I ve written a small stub Soap::Lite server that needs to accept requests from a .NET client. It seems like the server can t understand the incoming soap
    Message 1 of 2 , Jan 8, 2008
    • 0 Attachment
      I've written a small stub Soap::Lite server that needs to accept
      requests from a .NET client. It seems like the server can't
      understand the incoming soap envelope. Here's the request from .NET:

      Soap request (from .NET)
      01. <soap:Envelope
      xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
      02. xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      03. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      04. <soap:Header>
      05. <HTNGHeader xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      06. xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      07. xmlns="http://htng.org/1.1/Header/">
      08. <From>
      09. <Credential>
      10. <username />
      11. <password />
      12. </Credential>
      13. </From>
      14. <timeStamp>2007-12-26T15:55:33</timeStamp>
      15. <echoToken>xxxx</echoToken>
      16. <transactionId>xxxxx</transactionId>
      17. <action>Request</action>
      18. </HTNGHeader>
      19. </soap:Header>
      20. <soap:Body>
      21. <OTA_HotelResNotifRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-
      instance"
      22. xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      23. EchoToken="xxxx"
      24. PrimaryLangID="en"
      25. TimeStamp="2007-12-26T15:55:33"
      26. Version="4"
      27. ResStatus="Book"
      28. xmlns="http://www.opentravel.org/OTA/2003/05">
      29. <HotelReservations>
      30. <HotelReservation createDateTime="2007-12-26T20:54:58"
      31. RoomStayReservation="true"
      ---truncated---

      And here's what SOAP::Lite responds with:

      SOAP::Lite "500 Internal Server Error" response
      01. <?xml version="1.0" encoding="UTF-8"?>
      02. <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-
      instance"
      03. xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
      04. xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      05. soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding"
      06. xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      07. <soap:Body>
      08. <soap:Fault>
      09. <faultcode>soap:Client</faultcode>
      10. <faultstring>Failed to access class (OTA::2003::05):
      11. Can't locate OTA/2003/05.pm in @INC (@INC contains:) at (eval 97)
      line 3
      12. </faultstring>
      13. </soap:Fault>
      14. </soap:Body>
      15. </soap:Envelope>

      If you notice, line 21 of the request is the method I'm expecting to
      be called, but line 11 of the response complains about something else
      that actually appears on line 28 of the request.

      I'm using Soap::Lite 0.69, Microsoft IIS 6 and ActiveState Perl
      (perlx.exe)

      Any insight here?

      Marlin
    • rahed
      ... On the server side: I use the trailing path in line #28 after a url namespace (OTA/2003/05) as a path to an existing module which has a called method. ...
      Message 2 of 2 , Jan 9, 2008
      • 0 Attachment
        On 1/8/08, mcm1303 <marlin_mixon@...> wrote:

        > 28. xmlns="http://www.opentravel.org/OTA/2003/05">
        > 29. <HotelReservations>
        > 30. <HotelReservation createDateTime="2007-12-26T20:54:58"
        > 31. RoomStayReservation="true"
        > ---truncated---

        On the server side:
        I use the trailing path in line #28 after a url namespace
        (OTA/2003/05) as a path to an existing module which has a called
        method.

        > And here's what SOAP::Lite responds with:

        > 10. <faultstring>Failed to access class (OTA::2003::05):
        > 11. Can't locate OTA/2003/05.pm in @INC (@INC contains:) at (eval 97)

        And client should set a namespace (or uri in perl terms) accordingly:
        uri => "http://www.opentravel.org/OTA/2003/05


        --
        Radek
      Your message has been successfully submitted and would be delivered to recipients shortly.