Re: Static resource STATIC_RESOURCES_MAP_RESOURCE

Hi CXFServlet is not expected to be initialized per every request, it is only initialized once and then used, so I'm not sure why it is the problem - but I guess you can def block it in a servlet subclass Cheers, Sergey On 01/10/15 08:49, tigga.aks...@gmail.com wrote: Hi Sergey, I am using

Re: Not able to disable schema validation

Are you trying to disable the validation of SOAP payloads ? The below code uses CXF JAX-RS specific classes... Cheers, Sergey I've tried programmatically @Inject public CxfConfig jaxWsConfig(OneAXmlManager headerManager, Bus

Re: Consuming mutiple xml representations on resource

Hi The method parameters do not affect the selection algorithm. You can try a custom CXF ResourceComparator - then you can tell the runtime which of the two equal candidates wins. Re Patch/etc - yes wadl-to-java can not generate the custom annotation classes - it is time to do it though, will

Re: @...Param and client proxy

On 04/10/15 18:44, Veit Guna wrote: Alright. Thanks for the quick feedback! May I create a ticket for that? Sure, please do open JIRA tickets whenever you spot CXF client issues Cheers, Sergey Thanks Veit Am 04.10.2015 um 19:33 schrieb Sergey Beryozkin: Hi Veit The client proxy code appa

Re: @...Param and client proxy

Alright. Thanks for the quick feedback! May I create a ticket for that? Thanks Veit Am 04.10.2015 um 19:33 schrieb Sergey Beryozkin: > Hi Veit > > The client proxy code apparently does not support nested BeanParams, > so more work will need to be done > > Cheers, Sergey > On 04/10/15 19:21, Veit

Re: @...Param and client proxy

Maybe https://code.google.com/p/reflections/ could help? 2015-10-04 19:18 GMT+02:00 Sergey Beryozkin : > Hi Veit > > The CXF server will also work the same way, the restriction is only on the > client proxy side, I've just checked a code, it should be sufficient to > have a setter - which is used

Re: @...Param and client proxy

Hi Veit The client proxy code apparently does not support nested BeanParams, so more work will need to be done Cheers, Sergey On 04/10/15 19:21, Veit Guna wrote: Hi Sergey. I see. Any news about the nested @BeanParam :)? Cheers Veit Am 04.10.2015 um 19:18 schrieb Sergey Beryozkin: Hi Veit

Re: can logging and StaxTransformFeature use at the same time?

Some info is here http://cxf.apache.org/docs/transformationfeature.html#TransformationFeature-Transforminterceptorsandphases but it is not enough... Sergey On 04/10/15 19:20, Sergey Beryozkin wrote: As far as I recall you can register TransformIn/OutInterceptor directly and set a phase on it to

Re: @...Param and client proxy

Hi Sergey. I see. Any news about the nested @BeanParam :)? Cheers Veit Am 04.10.2015 um 19:18 schrieb Sergey Beryozkin: > Hi Veit > > The CXF server will also work the same way, the restriction is only on > the client proxy side, I've just checked a code, it should be > sufficient to have a sett

Re: can logging and StaxTransformFeature use at the same time?

As far as I recall you can register TransformIn/OutInterceptor directly and set a phase on it to make sure it is run before Logging interceptors. Aki, can you please remind what the approach is, I recall you were fixing this issue :-) Thanks, Sergey On 04/10/15 12:07, Christopher Cheng wrote:

Re: @...Param and client proxy

Hi Veit The CXF server will also work the same way, the restriction is only on the client proxy side, I've just checked a code, it should be sufficient to have a setter - which is used to determine a possible field candidate without having to check all the fields - this is done on the proxy si

RE: Consuming mutiple xml representations on resource

Hi, The warning message is correct, because accordingly JAX-RS spec, the method must be selected based on URI, HTTP Verb, Request MediaType and Response Accepted Type: " 3.7.2 Request Matching A request is matched to the corresponding resource method or sub-resource method by comparing the nor

RE: ReflectionServiceFactoryBean performance

Hi, 2.5 to 3 minutes is quite long even for 15 clients initialization. Did you specify wsdlLocation attribute in jaxws:client? Can performance be related to remote WSDL downloading? Could you bind any profiling tool and discover which operation caused performance problem? Regards, Andrei. > --

can logging and StaxTransformFeature use at the same time?

I found out that if I use both logging and StaxTransformFeature at the same time, logging will not be performed. If I comment out "transformFeature" in "features", logging works again How can they work together? I am using cxf-2.4.2

Re: @...Param and client proxy

While working around the nested @BeanParam for now, I encountered the fact, that @...Param annotations work on fields now, but somehow getter/setter for that field are still required. Leaving them out, will leave the value unset on request. On the opposite, the Jersey server is fine with fields wi

Re: @...Param and client proxy

Ok, 3.0.5 seems to fix the field annotation issue - nice :). One to go... Am 04.10.2015 um 10:13 schrieb Veit Guna: > Hi. > > I'm using Apache CXF 3.0.4 on client side against a Jersey based REST > service. > On client side I'm using the CXF client proxy using the server side > interface classes.

@...Param and client proxy

Hi. I'm using Apache CXF 3.0.4 on client side against a Jersey based REST service. On client side I'm using the CXF client proxy using the server side interface classes. Now I encountered, that annotated fields (e.g. with @QueryParam) on @BeanParam classes are ignored when invoking a method passi