Re: SOAP errors and suggestion

Hi Brett,

Thank you for your answer! :)
Thanks a lot for the helping way you've described.
That seems really nice, usefull and fun !

See you!

Karim
--
http://akoncept.com
Innovate Humanum Est.

On 10/2/07, Brett Bieber <brett.bieber@gmail.com> wrote:
> Hi Karim,
>
> On 10/1/07, Gmail Directeur <directeur@gmail.com> wrote:
> >
> > Hello,
> >
> > I've intentionnally submitted http://yahoo.co (without the "m" for com)
> > to the markup validator and here's what it returned as a soap12 output:
> >
> > <?xml version='1.0' encoding="utf-8"?>
> > <env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"
> >             xmlns:m='http://www.w3.org/2005/10/markup-validator'>
> >   <env:Body>
> >    <env:Fault>
> >      <env:Code>
> >        <env:Value>env:Sender</env:Value>
> >        <env:Subcode>
> >         <env:Value>m:Exception</env:Value>
> >        </env:Subcode>
> >      </env:Code>
> >
> >      <env:Reason>
> >         <env:Text xml:lang="en-US">HTTP Error</env:Text>
> >      </env:Reason>
> >      <env:Detail>
> >         <m:errordetail xml:lang="en-US">
> >     Unexpected HTTP response
> >     500 Can&#39;t connect to yahoo.co:80 (Bad hostname &#39;yahoo.co&#39;)
> >     while trying to retrieve http://yahoo.co/.
> >
> >     If you made recent changes to your domain name (DNS) configuration, you may
> >     also want to <a href="http://www.squish.net/dnscheck/">check that your
> >     domain records are correct</a>, or ask your hosting company to do so.
> >
> >        </m:errordetail>
> >      </env:Detail>
> >
> >    </env:Fault>
> >  </env:Body>
> > </env:Envelope>
> >
> > This seems fine, except for the "m:errordetail" tag's content which IMHO
> > should be wrapped inside a CDATA for it contains an html link <a>
> >
>
> Ah yes. It should be encoded or wrapped in CDATA.
>
> > Can you please publish more details about this api, especially for
> > the FAULT part of it?
> >
> > I've also submitted in a precedent email some other suggestions,
> > but i didn't recieved an answer :(
> >
> > How can i help? :)
> >
>
> I've found the best way to help is to get the validator running
> locally from the CVS version at http://dev.w3.org/cvsweb/validator/
> and start understanding how it works internally. Then monitor the
> mailing list (as it seems you're already doing) and the bug tracker
> --- then start submitted patches for bug fixes.
>
> This mail to the list is a good start. I would file a bug report for
> items you know are bugs, and dig into the source to see if you can
> provide a patch with your bug report.
>
> Take a look at the file
> validator/share/templates/en_US/soap_fault.tmpl  and I'm sure you can
> easily see what needs to be modified.
>
>
> > Thanks for all !
> >
> > Karim
> > --
> > http://akoncept.com
> > Innovate Humanum Est.
> >
> >
>
>
> --
> -Brett Bieber
>
> http:saltybeagle.com aim:ianswerq
>

Received on Tuesday, 2 October 2007 20:05:37 UTC