Payloadvalidatinginterceptor schemas property error updating ad aware
The plugin contains all of the Spring WS libraries it requires.
In addition, the Spring WS plugin also has a dependency on the 'functional-test' plugin when conducting web service functional tests, and the Spring Security Grails plugin if you want to use that option for securing your endpoints.
A functional endpoint test provides an instance of the Web Service Template that you can use to invoke a web service endpoint.
The complete functional test, including using Markup Builder to create the outgoing 'Holiday Request' document and XMLSlurper to the examine the response document, is shown below: New Feature for 0.2!
This is especially useful when you are working with a schema that has been in existence prior to your endpoint implementation, or perhaps is a public shared schema that you simply cannot change.
We've introduced the neater with Endpoint Request feature in 0.2 of the plugin that means even less code in your endpoint functional tests (so now there really is no reason not to implement them).
New in version 0.2, To expose the Holiday Endpoint's wsdl we can now take advantage of the new configuration support for this.
As per the comments in the Callback Handler below, it's probably a good idea to have a cache manager, something like Hazelcast or Ehcache to cache authenticated users, depending on security / performance considerations.
The Digest Validator below can just be used directly from the Sun library, I was just wanted to see how it worked.
To override the default endpoint payload mapping strategy, all you have to do is provide the request Element static property that contains the name of the element you expect in the root of the documents that you want to route to your endpoint: WS-Security is the standard mechanism for providing secure web services.