On 15/10/14 07:19, shisholik wrote:
Thank you so much for your answer! I will switch to CXF 3.0.1 and try
ParamConverterProvider with Boolean, Integer and Enums.
I think no need to create a specific exception for integers.
I was not suggesting to an exception for the integer specific format
issues, but rather to have an exception which one would be able to check
in JAX-RS ExceptionMapper and extract the name of the parameter which
caused the exception. However it would make the mapper code
non-portable, so I guess I'd just drop this idea.
Yes, using ParamConverterProvider would be the right way to go. FYI it
is supported in CXF 2.7.13 too, but if you can then migrating to 3.0.2
(just released) would be a better move
Maybe better
way will be is make exception for deserialization errors.
These are captured as WebApplicationException cause and can be analyzed
in the exception mappers
Sergey
--
View this message in context:
http://cxf.547215.n5.nabble.com/Getting-parameter-name-from-exception-tp5749870p5749901.html
Sent from the cxf-user mailing list archive at Nabble.com.
