Hi,
Yes exactly, this would be a "cheap" feature and would prevent the
server from unnecessary requests (as long client SDKs are in synch...).
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
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
Hi all,
The Web Application Description Language specification [1] defines:
>> Boolean matrix parameters are represented as: ';name' when 'value' is 'true'
>> and are omitted from identifier when 'value' is 'false'
Is there a way to achieve this behavior with cxf out of the box?
Brgrds,
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
Hi,
Thank you, moving the validationFeature to the endpoint did the job
perfectly!
Best regards,
Johannes
Am 24.10.2016 um 14:11 schrieb Sergey Beryozkin:
Or register the validation feature directly on the server endpoint
Sergey
On 24/10/16 13:10, Sergey Beryozkin wrote:
Hi
This is
Or register the validation feature directly on the server endpoint
Sergey
On 24/10/16 13:10, Sergey Beryozkin wrote:
Hi
This is caused by the fact that a server-scoped feature is visible to a
client because this feature is set on a bus visible to the client.
I've just updated the code for
Hi
This is caused by the fact that a server-scoped feature is visible to a
client because this feature is set on a bus visible to the client.
I've just updated the code for this feature be explicitly marked as a
Server scoped feature - but it will only help for now if the features
are
Can you share the implementation of HelloApi?
On Oct 24, 2016 07:36, "Johannes Fiala" wrote:
> Hi there,
>
> cxf-spring-boot-starter-jaxrs: 3.1.7
>
> I tried using Spring Boot CXF in combination with Spring Boot integration
> tests (running as a Spring Boot application
Hi there,
cxf-spring-boot-starter-jaxrs: 3.1.7
I tried using Spring Boot CXF in combination with Spring Boot
integration tests (running as a Spring Boot application everything runs
fine without exceptions):
As soon as the BeanValidation Feature is enabled:
Yes it's possible to add headers and sign and encrypt them. There is a test
which demonstrates how to do this for encryption, although Signature works
as well:
Hi John,
thanks for your answer. Your proposal was my initial thought, but the
problem is that ParamConverter in Apache CXF works considering every single
element in a List, not the List as a whole, meaning that rawType in
ApacheCXF will never be a List but, in the case of List, a String.
In
No one?
Is it not possible with CXF or is it an unusual demand?
I need to consume this webservice. If its not possible with CXF I need
to find another way but I'd like to stick with CXF.
Thanks
Martin
Am 20.10.2016 um 10:00 schrieb Martin Fernau:
Hi,
is it possible to call a webservice
Hi Diego
Hope you've had enough time to recover before a new working day :-)
Here are the reasons I won't agree with it before either JAX-RS 2.1 or
future TCK will force CXF to do it:
1. Minor:
IMHO it is wrong to expect a custom param converter to guarantee it
parses all of the query
13 matches
Mail list logo