Re: 404 with numeric IPv6 address in URL

Hi Brian http://\[fd4f:6e92:48ef:1:20c:29ff:fe9a:4b0\]/rws/mobile/devices is likely confusing CXF ServletController or JAX-RS code delaing with finding a match , will need to be investigated, can you please try CXF 2.3.4, there were some related changes before I can get to looking into it ?

Secured java web application calls secured web services with identity delegation

Hi there Let's assume a tomcat based web application is secured either with SAML-P or WS-Federation (passive requestor profile). The web application is calling web services on behalf of the original authenticated user. The web services have an IssuedToken assertion and expect a SAML 2.0 token

Re: Secured java web application calls secured web services with identity delegation

Hi Oli, Does the fix I commited for CXF-3565 meet your needs? https://issues.apache.org/jira/browse/CXF-3565 See for example this CallbackHandler implementation I added for setting an OnBehalfOf element from the SecurityConstants.USERNAME value:

Spring autowiring

All: I have been using the CXF non-Spring servlet and am now moving to the CXF Spring servlet. I'm not completely familiar with Spring's autowiring capabilities, but is there a way of adding a new web service to my server without explicitly modifying the Spring configuration? In other words, I'd

AW: Spring autowiring

You can drop a war file in a Servlet Container or a bundle jar into Karaf. This will make it execute without restarting the server. Spring or CXF do are no containers so they do not offer direct support for hot deploy. Christian -Ursprüngliche Nachricht- Von: David Sills

Re: Heavy REST requests block Light ones

Hello, I use CXF JAX-RS actually. I've updated to 2.3.4 but it didn't help unfortunately :( I've created simple test in JMeter with two thread groups for heavy and light http requests, which work simultaneously. As experiment I've replaced logic in heavy method by Thread.sleep(40*1000), and

Re: Heavy REST requests block Light ones

Hi, That is interesting, thanks for the info. I reckon that what you are seeing is the server thread pool exhaustion, so I guess one initial option is to experiment with the container-specific configuration and increase the pool somehow, check how it can be done with embedded Jetty:

Handling response - Invoking web services asynchronously

Hi all, What is the best practice for handling async call response? Below is what I do normally, new AsyncHandlerMyResponse() { @Override public void handleResponse(ResponseMyResponse res) { try { MyResponse v = res.get(); // process v ... }catch

AW: Secured java web application calls secured web services with identity delegation

Hi Colm After authentication happened within the web application I've got access to the bootstrap token. There is no cxf message object created at this stage because no processing occured at the web application yet. I see one option which involves two steps. A servlet filter writes the

Re: Getting payload in the client side.

On Thursday, June 02, 2011 5:05:30 PM Humagain, Himal wrote: Thanks a lot for your reply. I am trying the logging option but will not fulfill my need. I need to get hold of the payload (content) in the client side then I want to include it in my MD5 hashing of the content, then the generated

Re: AW: Secured java web application calls secured web services with identity delegation

Oli, Normally in this kind of case, in your application code, you would do something like: ... get security token somehow proxy.getRequestContext().put(TOKEN_KEY, token) or similar to pass the token into the client proxy that is then used.Thus, no callback needed. The trick

Re: 404 with numeric IPv6 address in URL

Hi Sergey, Thanks for your quick response. I tried 2.3.4 this morning, and I have the same failure, 404 returned to the client and the same log messages on the server. By the way, I tried with just a single host this morning, using localhost addresses: http://127.0.0.1/rws/mobile/devices for

RE: Getting payload in the client side.

Thanks a lot Dan. I am very close to getting it done. I have one question. This is what I am doing now: // in spring config bean id=loggingOutInterceptor class=org.apache.cxf.interceptor.LoggingOutInterceptor constructor-arg value=write/ /bean cxf:bus

RE: Spring autowiring

Christian: Thanks, I wasn't looking for hot deploy, however. I was simply looking to be able to auto-discover web services when the server starts up, so that I could 1. Drop a JAR file into WEB-INF/lib 2. Restart the server without having to modify the Spring configuration file. Can this be

Re: Getting payload in the client side.

In this case you need to use a WebClient.create() variant which accepts a classpath location of Spring config, ex, WebClient.create(address, classpath:/config/beans.xml). WebClient.getConfig(client).getOutInterceptors().add(new LoggingOutInterceptor()); Sergey On Fri, Jun 3, 2011 at 4:17 PM,

Re: Heavy REST requests block Light ones

Hi, I found out that bottleneck is connected to the Spring transactions support in our application. After I had commented out @Transactional annotation on heavy and light services (out of curiosity), light reuqests became fast as they had to be. So, seems actual reason not related to the CXF

Re: 404 with numeric IPv6 address in URL

Hi Brian On Fri, Jun 3, 2011 at 4:14 PM, bks bksmit...@yahoo.com wrote: Hi Sergey, Thanks for your quick response.  I tried 2.3.4 this morning, and I have the same failure, 404 returned to the client and the same log messages on the server. By the way, I tried with just a single host this

Re: Tag ? Xml version = 1.0 encoding = utf-8? in the response

Hi Dan, thank you very much for responding. I added PhaseInterceptorChain.getCurrentMessage (). GetExchange (). Put (org.apache.c xf.stax.force-start-document , Boolean.TRUE); and went, but what this I also did was added in response within each tag ns1: if only I had the principal of the

RE: Getting payload in the client side.

I am using JAX-RS. -Original Message- From: Sergey Beryozkin [mailto:sberyoz...@gmail.com] Sent: Friday, June 03, 2011 6:45 AM To: Humagain, Himal Cc: Fabio souza; users@cxf.apache.org Subject: Re: Getting payload in the client side. Do you use JAX-WS or JAX-RS ? Cheers, Sergey On

CXF with basic authentication with wsdl2java

I am using CXF and the wsdl2java tool to generate the classes. The process works nicely. However the services are protected by basic authentication and unfortunately its a customer requirement. The wsdls are not protected by basic authentication. What I would like to do is pass in credentials in

CXF Bad XML

client.invoke throws error: Type 'xs:string' is not validly derived from the type definition, 'echo', of element 'ns3:echo'. This is due to badly formed XML generated by CXF. The test code is a simple echo and the XML is derived by CXF using the WSDL. It works for a simple Java web

OW2 FraSCAti 1.4 released

Hi, OW2 FraSCAti 1.4, an open source SCA implementation built on top of Apache CXF 2.4.0, is now released. Have a look at http://frascati.ow2.org Best regards, OW2 FraSCAti team http://frascati.ow2.org -- You receive this message as a subscriber of the frasc...@ow2.org mailing list. To

jaxb validation

Upgrading from CXF 2.2.2 to 2.3.4. We have some client software that's sending the wrong namespace in a request and so we're getting the Unexpected wrapper element fault. I find plenty of discussion in previous posts suggesting to: set-jaxb-validation-event-handler to false Though I've

feature list incomplete?

I had look at http://cxf.apache.org/docs/featureslist.html and do not see e.g. the validation feature, and the list is only partially documented. Where can I find all available features delivered with CXF?

Re: CXF with basic authentication with wsdl2java

Hi, To enable basic auth on client side for all endpoints, you needn't manually change each generated code, you can just add a configuration file for the http:conduit of the CXF bus, something like http:authorization sec:UserNameBetty/sec:UserName