Attempt to manually deserialize from the message object.
Attempt to manually deserialize from the message object.
Create a the bindings to bind this object to a request.
Extract the value from the target object.
Add a parameter to the list of parameters that make up this composite.
Add a parameter to the list of parameters that make up this composite.
Attempt to manually deserialize from the message object.
Attempt to manually deserialize from the message object. User-friendly synonym for <--?(), which is why the method is final.
Extract the value from the target object.
Extract the value from the target object. Throws on failure, but that shouldn't be a problem as the pre-validation stage for declared parameters and bodies handles the failure before user code is entered. User-friendly synonym for <--(), which is why the method is final.
Bind the value to this parameter User-friendly synonym for -->(), which is why the method is final.
Bind the value to this parameter User-friendly synonym for -->(), which is why the method is final.
the binding
User-friendly synonym for <->(), which is why the method is final.
User-friendly synonym for <->(), which is why the method is final.
(Changed in version 2.9.0) The behavior of scanRight
has changed. The previous behavior can be reproduced with scanRight.reverse.
(Changed in version 2.9.0) transpose
throws an IllegalArgumentException
if collections are not uniformly sized.
(Since version ) see corresponding Javadoc for more information.
A composite allows for a single object to be extracted from many request parameters. Validation is applied to all of the parts before being passed to a user implemented service. Extend this to provide custom extraction for composite objects.