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 51 Next »

Module Overview

If you need to quickly consume and/or publish WS-I compliant web services, GroovyWS can help you.


If you are online and using the latest groovy version, here is the no-brainer way to use GroovyWS:

If you need more control, see the GroovyWS installation notes.

Getting Started

GroovyWS comes with two sets of APIS that are briefly described below using a simple example.

When your service is using groovy beans on the server side, you may want to control the fields that are serialized. This is done using a small xml file located next to your script. A small example is demonstrating this:

When consuming a web service, you may also be using some complex types. Those types are automatically generated from the WSDL, compiled and made available via your classloader. The client API is providing you a method to easily instantiate such a complex object from its name. Obviously, knowing the class name can be difficult when using a complex web service and may require to study the contract (WSDL). In order to help the user, GroovyWS is logging the names of the classes generated on the fly.

The client side integrates seamlessly with Grails applications.

There exists a lot of public web services. We provide two examples that show how easy it is to use GroovyWS to tap on these resources.

More WSClient configuration is available if you need to use proxies, basic authentication and security related features.

The javadoc is probably the ultimate place to the missing bits. If you are missing a feature email us


  1. A nice article from Geertjan's blog with several examples:
  2. An article explaining the difference between the different WSDL styles


  • The build process is using gradle.  In order to build the sources from svn, just run:
    in the directory containing the source tree.
  • Feel free to contribute by testing, giving your feedback, reporting bugs and sending patches.
  • No labels