How do you use FastInfoset with JAXWS?

Question

I have code that looks like it should be correct based on what I can find, but the erupted output does not indicate that it uses FastInfoset. My understanding is that Accept should indicate that it can accept Fastinfoset, and the response really uses it, i.e. it is not text / xml as the type of response. Any idea what I'm doing wrong? I looked through Google and it’s hard for me to find detailed information on how to use FastInfoset in general.

JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean(); factory.getInInterceptors().add(new LoggingInInterceptor()); factory.getOutInterceptors().add(new LoggingOutInterceptor()); factory.setServiceClass( C360Server.class); factory.setAddress("http://localhost:8501/cxfcontroller/cl_v5"); C360Server client = (C360Server)factory.create(); ((BindingProvider)client).getRequestContext().put( "com.sun.xml.ws.client.ContentNegotiation", "optimistic"); C360Request requestTrans = new C360Request(); ... code to fill in the request ... C360Response response = client.findContacts( requestTrans ); 

Logging does not seem to indicate that FastInfoset is even trying:

 INFO: Outbound Message --------------------------- ID: 1 Address: http://localhost:8501/cxfcontroller/cl_v5 Encoding: UTF-8 Content-Type: text/xml Headers: {SOAPAction=[""], Authorization=[Basic cWFfc3VwZXI6cWFfc3VwZXI=], Accept=[*/*]} Payload: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns1:findContacts>...bunch of xml deleted for brevity...</ns1:findContacts></soap:Body></soap:Envelope> -------------------------------------- May 17, 2010 3:23:45 PM org.apache.cxf.interceptor.LoggingInInterceptor logging INFO: Inbound Message ---------------------------- ID: 1 Response-Code: 200 Encoding: UTF-8 Content-Type: text/xml; charset=utf-8 Headers: {content-type=[text/xml; charset=utf-8], Content-Length=[611], Server=[Jetty(6.1.x)]} Payload: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns1:findContactsResponse>...bunch of xml spew deleted for brevity...</ns1:findContactsResponse></soap:Body></soap:Envelope> -------------------------------------- 

Any ideas what I'm doing wrong? Even if the server did not support FastInfoset, I should still see an attempt to reconcile in the request, right?

Answer 1

The answer is that the information I had on how to include it is out of date. The following works on the client side (and, presumably, on the server, but there I have included the Spring configuration that processes it).

  JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean(); // This enables FastInfoset as the communication protocol factory.getInInterceptors().add( new FIStaxInInterceptor() ); factory.getOutInterceptors().add( new FIStaxOutInterceptor() ); ... other code to set username, location, etc. goes here. client = (C360Server) factory.create(); 

Answer 2

 //Enabling FastInfoset by configuring proxy // Enabling FI in pessimistic mode Map<String, Object> ctxt = ((BindingProvider)proxy).getRequestContext(); ctxt.put(JAXWSProperties.CONTENT_NEGOTIATION_PROPERTY, "pessimistic"); 

OR

Enabling FastInfoset Using the System Property

 -Dcom.sun.xml.ws.client.ContentNegotiation=pessimistic