Thanks Norman,
Yes, I agree that the StockQuote service code needs to be refactored and
made more generic.
I wrote all the soap client code from scratch to illustrate how easy it is
to write soap clients without the need of any framework.
In fact, the only other jar file needed in the example is xerces.jar (that
reminds me, the code needs to be decoupled from xerces)
We should consider using soap beans or other frameworks in the refactoring.
See
http://xml.apache.org/soap/docs/apiDocs/org/apache/soap/package-summary.html
The code in the jetspeed cvs is actually a webservice client, whereas the
webservice is running in another container on my server.
The StockQuote portlet is not complete, hope to finish this week...:
- customization, to select your own quotes, and store the quote list by user
- wml support
As for a UDDI browser portlet, yes, great!
With this portlet, my goal was to bring some focus to web services in
jetspeed, which we haven't really explored up until now.
David
> -----Original Message-----
> From: Norman Sch�neich [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 24, 2001 8:25 AM
> To: [EMAIL PROTECTED]
> Subject: Jetspeed goes Webservices !
>
>
> I checked out the latest cvs and see a stock quote portlet
> (as a webservice
> call).
>
> Good job !
>
> P.S.
> What's about a common webservice portlet, where i can choose
> a webservice
> from UDDI and call methods of the webservice and get response.
> Are there plans to do something like that ?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
