Yea it's not a huge problem for us at the moment. I was just curious.
Thanks for your help.
--
View this message in context:
http://cxf.547215.n5.nabble.com/ParamConverterProvider-use-with-primitive-types-tp5762566p5762759.html
Sent from the cxf-user mailing list archive at Nabble.com.
Yes, unfortunately the fix will only be available in the next 3.1.5
release which is quite far away at the moment given that 3.1.4 was
released last week. Perhaps a default conversion to 'boolean' would work
just fine in meantime ?
Cheers, Sergey
On 09/11/15 16:05, craigrs84 wrote:
Thanks Se
Thanks Sergey!
We're currently running CXF 3.1.2 so no need to migrate.
I tried upgrading to CXF 3.1.4 this morning but the bug still existed there.
Is your fix supposed to be available in CXF 3.1.4? Or is it going to be
packaged in a forthcoming release?
Thanks.
--
View this message in con
I will try making a test case later in the week. For now, I was able
to flip to bval and have things work.
On Mon, Nov 9, 2015 at 5:57 AM, Sergey Beryozkin wrote:
> Hi Benson
>
> Lets try to equalize :-), some of CXF bundles optionally import bean
> validation API, see
>
> http://cxf.apache.org/
Hi Benson
Lets try to equalize :-), some of CXF bundles optionally import bean
validation API, see
http://cxf.apache.org/docs/validationfeature.html
So I guess, because those optional imports can be resolved, there might
be some version mismatch between what CXF expects and what you have
in
