Re: [ecf-dev] rest and soap additions to remoteservice

[Ted Kubaska <ted.kubaska@xxxxxxxxx>]

Here is one that seems alive
http://www.nws.noaa.gov/xml/


On Tue, Jan 12, 2010 at 7:19 PM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
> Hi Ted,
>
> Ted Kubaska wrote:
>
> Are any of those in http://soapclient.com/XmethodsServices.html useful? -ted
>
>
> Yeah, these look pretty good.  Any opinions/views about which one to use?
> i.e. EBayWatcherService, Delayed Stock Quote, CA Traffic Conditions, or etc?
>
> I don't particularly care...but it would be good to use one that people
> would find compelling as an example.
>
> Scott
>
>
> On Tue, Jan 12, 2010 at 5:58 PM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
>
>
> Hi Folks,
>
> Over the break and since I've been doing some refactoring of the ECF REST
> API...as well as adding on some classes to allow easy support of SOAP-based
> providers.  I've produced a blog posting about this here:
>
> http://eclipseecf.blogspot.com/2010/01/soap-rest-and-ecf-remote-services.html
>
> One thing that remains to do...create an example SOAP client
> provider...using an existing example SOAP service.  That is, I would like to
> create a client provider for some existing SOAP service...hopefully a fairly
> simple service...that has some wsdl to describe the protocol/method calls.
>  My intention is to take the wsdl, run it through WTP's web client creation
> wizard (that uses wsdl2java from Apache Axis) to create the java code, and
> then add a few (~3) ECF classes to finish the provider and expose the
> service as an OSGi service.
>
> So if someone has/knows about a SOAP-based web service that is public,
> simple, and is running fairly consistently (so that people can test the
> client against a real running server) please let me know...as I would prefer
> to use an existing service rather than create a new one.  If others wish to
> work on this with me, please let me know and we can do so.
>
> Another option is to use one of the Axis example services...which I will do
> if a better one cannot be easily found.
>
> Thanks,
>
> Scott
>
>
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev
>
>
>
>
>
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev
>
>



-- 
 -Ted