Dear Sergey,
To be more specific, at ClientProxyImpl.java the Object[] params are
available, but they are not passed onto the interceptor chain:
return doChainedInvocation(uri, headers, ori, body, bodyIndex, null, null);
Is there a another way I can access the Object[] params in an interceptor?
Or do I have to subclass ClientProxyImpl.java?
Best regards,
Johannes
Am 13.11.2016 um 20:45 schrieb J. Fiala:
Dear Sergey,
I tried to implement the BeanValidation for the client for outgoing
operations in an OutInterceptor.
I need to be able to validate the parameters for the method:
Set<ConstraintViolation<Object>> violations =
executableValidator.validateParameters(this, method,
parameterValues);
Getting access to the method is no problem using
OperationResourceInfo.class.
How can I access the parameter values (Object[] parameterValues) of
the method that has been invoked so I can validate them?
I can get easily access to the json objects if passed to the method,
but I need access to the original method invocation, before the
message has been assembled to query/path/body params etc.
Best regards,
Johannes
Am 24.10.2016 um 17:04 schrieb Sergey Beryozkin:
Hi
I guess it can be interesting to support an optional client side bean
validation for the proxy clients as they have all the bean validation
annotations available...
Cheers, Sergey
On 24/10/16 14:47, J. Fiala wrote:
Hi there,
Is automatic client-side beanvalidation supported somehow (currently
this is not mentioned in the docs)?
Maybe it would make sense to add this to the configuration, so this has
not to be done manually before calling the server?
Best regards,
Johannes
