There are some valid arguments against using Optional as a method parameter type, but they are not good enough to say that you should avoid it at all costs
I had a similar problem and struggling, googling for 1 day. But it was a simple mistake that instead of:
{http://ws.somecompany.com/services}ValidateUser
It should be
{http://ws.somecompany.com/services/}ValidateUser
Hello, I am currently searchin for a way to convert several Word documents into a single PDF file. The original Word documents are attachments to a One Order object in CRM 5.0, and I want to create an
Custom parsing / setting of handler arguments.
A custom HandlerMethodArgumentResolver might be written extending the RequestParamMethodArgumentResolver laveraging already existent parameter parsing functionlaity.