Cxf Client - Support for Soap Service Endpoints

  • Authors : Christian Oestreich, Brett Borchardt, Laura Helde, Kyle Dickerson, Jordan Howe
  • License : Apache License 2.0
2 votes
Dependency :
compile ":cxf-client:1.6.0"

Documentation Source


Used for easily calling soap web services. Provides wsdl2java grails target to easily generate code into src/java from configured cxf clients. Ability to dynamically update endpoint at runtime.


grails install-plugin cxf-client


The Cxf Client plugin will allow you to use existing (or new) apache cxf wsdl2java generated content to invoke soap services. The plugin will also cache the port reference to speed up your soap service end point invocations. The client(s) are easily configured via the standard grails config Config.groovy file.

Also bundled with this plugin is a wsdl2java grails script run target for you to quickly and easily generate the cxf client components from a wsdl directly into your src/java directory.

v1.4.0 - Updating the wsdl2java script to not require the installPath any longer. Updating cxf to version 2.6.1 to match the cxf plugin.

v1.3.0 - Adding ability to update endpoint during runtime if needed - Thanks to Laura Helde for finalizing this work. Adding reponse mime attachement support - Thanks to Kyle Dickerson for helping with this issue.

v1.2.7 - Ability to set allowChunking. Ability to specify custom HTTPClientPolicy bean to use for the client instead of separate timeouts (connection/receive) and chunking (see for more details)

v1.2.6 - Added the ability to specify a connectionTimeout and a receiveTimeout for each client that will be used when creating the client proxy. Defaults to cxf default values of 30000 and 60000 ms respectively. Can be set to 0 to disable timeout and wait indefinitely for a response.

v1.2.5 - Changed the keyword binding to bindingFile as that is a reserved keyword.

v1.2.4 - User can now provide a wsdlArgs to specify a custom list of commands to pass to the wsdl2java command for each client such as

wsdlArgs = ["-autoNameResolution","-validate"]

v1.2.3 - The ability to define a list of in, out or fault out interceptors for each client. You can still use the same single security interceptor as before, or you can use a more generic approach and define any number of interceptors you see fit. You can also now disable the default logging interceptors to turn off logging. You can also disable the default logging interceptors and define your own if you wish to manipulate the logged data to remove sensitive data for example.

v1.2.2 - By default you can invoke secure services using wss4j by setting secure = true, but there is also the ability to define and use a custom security out interceptor.

Documentation can be found at

Sample implementation can be found at