I've reviewed the code.  I do not find that a method with a validation error is called.  The validation error is thrown.  It is captured[1] and returned to the caller in the Response object as an HTTP 400 error.[2]

[1]https://github.com/resteasy/Resteasy/blob/master/resteasy-jaxrs/src/main/java/org/jboss/resteasy/core/ResourceMethodInvoker.java#344
[2]https://github.com/resteasy/Resteasy/blob/master/resteasy-jaxrs/src/main/java/org/jboss/resteasy/core/ResourceMethodInvoker.java#191




On Wed, Oct 25, 2017 at 5:26 AM, Alessio Soldano <asoldano@redhat.com> wrote:
Hi John,
sorry, I'm a bit busy atm, anyway I'm forwarding your email to the resteasy-dev list. We'll get back to you.

Cheers
Alessio

On Tue, Oct 24, 2017 at 11:59 AM, John O'Hara <johara@redhat.com> wrote:
Alessio,

I am not sure if you are the correct person to ask, if not please let me if there is someone more appropriate to ask.

I have been investigating some unexpected behaviour in how entity validations exceptions are propagated through WF/EAP when http post requests are made via rest endpoints. 

One thing I have noticed in the resteasy-jaxrs module is that in org.jboss.resteasy.core.MethodInjectorImpl.invoke() the method parameters are validated [1], but the method is still invoked, irrespective of the outcome of the call to the validator [2]

Is there is a possibility of failing a method invocation after the validation call [1], so that we do not invoke the method, which ends up failing anyway due to validation exceptions? 

Thanks

John



_______________________________________________
resteasy-dev mailing list
resteasy-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/resteasy-dev