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

4292Re: XML Fragment in String Data causes Soap Error ...

Expand Messages
  • etaekema
    Jan 6, 2005
    • 0 Attachment
      I just ran a quick test and if I connect directly to the soap service
      it encodes the < characters and decodes it on the other side ... if I
      do it through the WSDL ... it doesn't encode it ... Is there
      something I can do in the wsdl file to force it do encode/decode
      correctly?

      Ed

      --- In soaplite@yahoogroups.com, Joseph Hourcle <oneiros@g...> wrote:

      >
      > I haven't played with the WSDL support in SOAP::Lite, or used
      SOAP::WSDL,
      > so I don't know what might've caused the problem -- I've just seen
      the
      > same error message before, so I knew what the likely culprit was.
      >
      > [Although, in my case, I was the one that caused it, because of
      replacing
      > the serializer, and things weren't calling the default encoding
      functions]
      >
      > -----
      > Joe Hourcle
    • Show all 6 messages in this topic