Re: RequestDispatcherProvider not saving QueryParameters in HttpServletRequest

On 05/04/13 17:17, harrisgilliam wrote: It is not a form... the query parameters are available in the resource class.. ie: they are injected into the parameters of the methods annotated with @GET Is there a way to configure LoggingFeature without using Spring? I have a requirement that I cannot

Re: Question on org.apache.cxf.rs.provider

On 05/04/13 18:23, geecxf wrote: I can confirm that String[] works. I thought it didn't at first, but then I realized that toArray() produces an Object[] even when the type is ArrayList (stupid Java). While using String[] works, it's still not ideal for us because we also need the ability to pa

Re: DefaultSecurityTokenServiceProvider does not use CXF UsernameTokenValidator

Thanks for pointing that out Colm. Once I started debugging from that entry point I realized there was a subtle bug in my validator. Everything works now. Once again many thanks for the help. I truly appreciate it. -- View this message in context: http://cxf.547215.n5.nabble.com/DefaultSecurity

Re: Problem while reading soap response

Thanks you, it works fine using the JAX-WS frontend. Julien On 05/04/2013 16:20, Daniel Kulp wrote: On Apr 5, 2013, at 7:18 AM, Julien Taillard wrote: Hello, I'm facing a problem using CXF 2.7.4 to build a client for a Metro Secured WebService. Client library is generated using the wsdl2ja

Re: Question on org.apache.cxf.rs.provider

I can confirm that String[] works. I thought it didn't at first, but then I realized that toArray() produces an Object[] even when the type is ArrayList (stupid Java). While using String[] works, it's still not ideal for us because we also need the ability to pass an object as well. Is there a JIR

RE: Problem while reading soap response

Hi, Could you provide part of WSDL with definition of sayHelloResponse element and appropriate message? Regards, Andrei. > -Original Message- > From: Julien Taillard [mailto:julien.taill...@alicante.fr] > Sent: Freitag, 5. April 2013 13:19 > To: users@cxf.apache.org > Subject: Problem w

Re: Problem while reading soap response

On Apr 5, 2013, at 7:18 AM, Julien Taillard wrote: > Hello, > > I'm facing a problem using CXF 2.7.4 to build a client for a Metro Secured > WebService. > Client library is generated using the wsdl2java tool. If you are using the wsdl2java tool, you most likely need to use the JAX-WS fronten

Re: RequestDispatcherProvider not saving QueryParameters in HttpServletRequest

It is not a form... the query parameters are available in the resource class.. ie: they are injected into the parameters of the methods annotated with @GET Is there a way to configure LoggingFeature without using Spring? I have a requirement that I cannot use Spring. I am configuring the provide

Re: cxf-2.7.4: configuring woodstox limits.

Daniel thanks for the quick reply. Still I cannot solve it server side. On 04/05/2013 02:17 PM, Daniel Kulp wrote: On Apr 5, 2013, at 5:29 AM, Vassilis Virvilis wrote: 1) Server side: How I can configure the limits from the spring configuration. Is it possible to do it per endpoint? per se

Re: DefaultSecurityTokenServiceProvider does not use CXF UsernameTokenValidator

Your endpoint configuration looks fine to me. For example, here is a (non-STS) endpoint with a custom UsernameToken Validator: http://svn.apache.org/viewvc/cxf/trunk/services/sts/systests/advanced/src/test/resources/org/apache/cxf/systest/sts/usernametoken/cxf-service.xml?view=markup Could you ch

Problem while reading soap response

Hello, I'm facing a problem using CXF 2.7.4 to build a client for a Metro Secured WebService. Client library is generated using the wsdl2java tool. Calling a simple helloworld service, I get null result while SOAP response message seems correct. System.out.println(fuzzimpl.sayHello());

Re: cxf-2.7.4: configuring woodstox limits.

On Apr 5, 2013, at 5:29 AM, Vassilis Virvilis wrote: > Hello, > > We have updated to cxf-2.7.4 and our internal test suite had hit the 5 > limit of cxf configuration for the woodstox xml parser. Furthermore woodstox > in this release is a hard requirement so we can't get rid of it. > > S

Re: Question on org.apache.cxf.rs.provider

Hi, On 05/04/13 00:29, geecxf wrote: Thank for pointing out that class. That was very helpful in debugging. Unfortunately, the behavior is still the same only more baffling than before! Here's what I'm doing: List providers = new ArrayList(); providers.add(new org.apache.cxf.rs.security.saml.Sa

cxf-2.7.4: configuring woodstox limits.

Hello, We have updated to cxf-2.7.4 and our internal test suite had hit the 5 limit of cxf configuration for the woodstox xml parser. Furthermore woodstox in this release is a hard requirement so we can't get rid of it. So far we have found (after digging in the source) the following sys

RE: org.apache.cxf.phase.PhaseInterceptorChain doIntercept INFO: Interceptor has thrown exception, unwinding now org.apache.cxf.interceptor.Fault: Connection reset

Hi, It could be either connection issue or kind of SSL problem. Is problem persist or occurs sporadically? I would recommend to activate SSL debugging (-Djavax.net.debug=all), perhaps it shines more light on the problem. Regards, Andrei. > -Original Message- > From: james-singh [mail