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

3524RE: [soaplite] Strange SOAP envelope results

Expand Messages
  • Joe Breeden
    Apr 22, 2004
    • 0 Attachment

      I was working with my .Net developer and we have noticed something that
      could be related. I don't know. If you put the URL '
      http://www.w3.org/2001/XMLSchema' in a browser, the result is an HTML
      page describing the XMLSchema namespace and not the actual XML schema.
      If you retrieve ' http://www.w3.org/2001/XMLSchema.xsd' you get the
      schema. I think that may have something to do with the xsi/xsd
      namespaces not being found.

      Again, thanks for all the help.


      -----Original Message-----
      From: Joe Breeden
      Sent: Thursday, April 22, 2004 7:30 AM
      To: soaplite@yahoogroups.com
      Subject: RE: [soaplite] Strange SOAP envelope results


      Thanks for the response. I don't know if I can shed any more light on
      the problem, but I'll try. I don't really know the sequence of calls
      before a failure occurs. I can recreate the error with some regularity
      with a test script I have that makes the same calls listed below, but in
      SOAP 1.1. I put the SOAP call into a while(1) loop and let it hit the
      server and then make the call from the .Net client. Unfortunately, the
      error doesn't happen on a regular basis. I thought for a bit that maybe
      the SOAP::Lite module was using a global variable to store the envelope
      and that it wasn't be rewritten because of the persistent nature of the
      Perl interpreter when used with apache/mod_perl. But, if that were the
      case I would expect the problem would be fairly regular and easily

      Thanks for looking into this for me. I hope this additional info helps.


      -----Original Message-----
      From: Paul Kulchenko [mailto:paulclinger@...]
      Sent: Thursday, April 22, 2004 12:29 AM
      To: Joe Breeden; soaplite@yahoogroups.com
      Subject: Re: [soaplite] Strange SOAP envelope results


      I believe you're right about the reason for this behavior -- mixture
      of SOAP1.1 and 1.2 requests. However, I don't see anything that could
      cause this. Do you know the sequence of SOAP1.1 or 1.2 calls before
      the call that fails? For example, SOAP1.1 -- valid fault response,
      SOAP1.2 invalid response.

      One possible reason for that behavior is the lack of ANY elements in
      the response that reference xsi/xsd namespaces, but even in this case
      the default XML Schema (which is 2001) should be used. I'm puzzled by
      this. Any additional info would be very helpful. Thank you.

      Best wishes, Paul.
    • Show all 6 messages in this topic