Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

Groovy SOAP

Error rendering macro 'link' : Link needs a name and a URL as arguments.
 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. Groovy has a SOAP implementation based on
Error rendering macro 'link' : Link needs a name and a URL as arguments.
which allows you to create a SOAP server and to make calls on remote SOAP servers.

Installing GroovySOAP

 You just need to download this jar file in your ${user.home}/.groovy/lib directory.

The Server

You can develop your web service using a groovy script and/or a groovy class. The following two groovy files are valid for building a web-service.

  1. MathService.groovy
  2. You can also using something more Groovy
  3. Then the easy part ... no need for comments
    That's all !

The Client

  1. Oh ... you want to test it ... two more lines.
  2. You're done!

Current limitations (and workaround)

  1. No proxy support
  2. No authentication
  3. It looks like the XFire dynamic client does not support complex datatypes. This may be a concern if you need for example to transfer an Image as a byte array. The workaround I use is to transform this in a String an transfer that String - As this is a bit painful I am investigating moving to the regular XFire client. Here is a little program demo-ing this (look at this "disco age" image - Is Groovy that old ?

The (ugly) server part (embedding the image which is Base64 encoded):

and the missing and secred part is here.

Demos with public web services

There exist a lot of web-services available for testing. One which is pretty easy to evaluate is the currency rate calculator from
Here is a small swing sample that demonstrate the use of the service. Enjoy !

And here is the result:

  • No labels