Web Services Tutorial, JokeOfTheDay no longer works

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Web Services Tutorial, JokeOfTheDay no longer works

Thomas Gagné-2
Executing from the WebServices book:

    | wsdlClient soapRequest soapResponse |
    wsdlClient := WsdlClient new loadFrom:
    'http://services.xmltoday.com/vx_engine/wsdl.vep?joke.wsdl' asURI.
    soapRequest := SoapRequest new.
    soapRequest port: wsdlClient config anyPort.
    soapRequest smalltalkEntity:
    (Message selector: #JokeOfTheDay ).
    soapResponse := soapRequest value .

Gives me a "referent inaccessible"  It looks like the webservice no
longer runs there.  Is there another example coming in the next version
of the book?

--
Visit <http://tggagne.blogspot.com/>,<http://gagne.homedns.org/> or
      <http://gagne.homedns.org/~tgagne/> for more great reading.

Reply | Threaded
Open this post in threaded view
|

Re: Web Services Tutorial, JokeOfTheDay no longer works

Thomas Gagné-2
I'm looking around just for something simple to try.  What's really
needed is a publicly accessible "Hello, world!" service.

Anyway, even this doesn't work:

WsdlClient new loadFrom:
'http://interpressfact.net/webservices/getjoke.asmx' asURI.

I need a simpler test service.  Instead of returning something
inspectable I get, "Unhandled exception: The close tag for br was not
found."

I appreciate that it's a good thing to get well-formed XML in a
response, but what's obnoxious is the intolerance of clients.  Perhaps
that's a problem with XML.  Humans can read sentences with misspelled
words and web browsers are tolerant of malformed HTML.  In this case the
text coming back has a <br> when a <br/> is what was intended -- and if
not intended at least correct.

Perhaps the exactitude of XML well-formedness makes things too brittle?

--
Visit <http://tggagne.blogspot.com/>,<http://gagne.homedns.org/> or
      <http://gagne.homedns.org/~tgagne/> for more great reading.

Reply | Threaded
Open this post in threaded view
|

Re: Web Services Tutorial, JokeOfTheDay no longer works

Thomas Gagné-2
I was able to get this to work.  Perhaps the tutorial could be updated
with it:

    | wsdlClient soapRequest soapResponse |
    wsdlClient := WsdlClient new loadFrom:
    'http://lepago.homeip.net/HelloLangJB4EJB/HelloLangEndpointPort?wsdl'
    asURI.
    soapRequest := SoapRequest new.
    soapRequest port: wsdlClient config anyPort.
    soapRequest smalltalkEntity: (Message selector: #sayHello arguments:
    #('Hello, world.')).
    soapResponse := soapRequest value .

The response was "Hello, world! not in database (yet)"  I don't know if
it was the correct response but it wasn't an exception.

--
Visit <http://tggagne.blogspot.com/>,<http://gagne.homedns.org/> or
      <http://gagne.homedns.org/~tgagne/> for more great reading.

Reply | Threaded
Open this post in threaded view
|

RE: Web Services Tutorial, JokeOfTheDay no longer works

Kogan, Tamara
In reply to this post by Thomas Gagné-2
I created AR#50680 to improve the WS client error messages.

Thanks,
Tamara Kogan
Smalltalk Development
Cincom Systems

> -----Original Message-----
> From: Thomas Gagné [mailto:[hidden email]]
> Sent: Tuesday, April 18, 2006 4:12 PM
> To: vwnc
> Subject: Re: Web Services Tutorial, JokeOfTheDay no longer works
>
> I'm looking around just for something simple to try.  What's really
> needed is a publicly accessible "Hello, world!" service.
>
> Anyway, even this doesn't work:
>
> WsdlClient new loadFrom:
> 'http://interpressfact.net/webservices/getjoke.asmx' asURI.
>
> I need a simpler test service.  Instead of returning something
> inspectable I get, "Unhandled exception: The close tag for br was not
> found."
>
> I appreciate that it's a good thing to get well-formed XML in a
> response, but what's obnoxious is the intolerance of clients.  Perhaps
> that's a problem with XML.  Humans can read sentences with misspelled
> words and web browsers are tolerant of malformed HTML.  In this case the
> text coming back has a <br> when a <br/> is what was intended -- and if
> not intended at least correct.
>
> Perhaps the exactitude of XML well-formedness makes things too brittle?
>
> --
> Visit <http://tggagne.blogspot.com/>,<http://gagne.homedns.org/> or
>       <http://gagne.homedns.org/~tgagne/> for more great reading.