The leading "f6" and trailing "0" that raised your suscipions are the single chunk length and the last chunk marker respectively.
To turn off HTTP chunking, use a configuration something like: <beans xmlns="http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:http-conf="http://cxf.apache.org/transports/http/configuration"; xsi:schemaLocation="http://cxf.apache.org/transports/http/configuration http://cxf.apache.org/schemas/configuration/http-conf.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd";> <http-conf:conduit name="{http://apache.org/hello_world_soap_http}SoapPort.http-conduit";> <http-conf:client AllowChunking="false" /> </http-conf:conduit> </beans> ... where "{http://apache.org/hello_world_soap_http}SoapPort"; is the QName of the target port. Cheers, Eoghan > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Michael Matczynski > Sent: 27 June 2007 18:56 > To: [email protected] > Subject: WS-I Compliance / SOAP Messages > > I have a test environment where a CXF client communicates > with a CXF server, both generated from a wsdl using the > wsdl2java utility. With a direct connection the client is > able to function properly, but when I insert a WS-I monitor > between the client and server, messages sent from the client > appear to be stopped by the WS-I monitor on their way to the server. > > Using tcpmon, I've discovered suspicious text (a few extra > characters, perhaps a checksum?) that appears before and > after every request sent by the client. I've loaded up the > wsdl in SOAP UI and am able to successfully communicate with > the server. Here is a comparison of the two outgoing > requests: > > === Request message produced from a client using CXF's wsdl2java === > > POST /FileCrawlerService HTTP/1.1 > Content-Type: text/xml; charset=UTF-8 > SOAPAction: "" > Cache-Control: no-cache > Pragma: no-cache > User-Agent: Java/1.5.0_11 > Host: localhost:12000 > Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 > Connection: keep-alive > Transfer-Encoding: chunked > > f6 > <soap:Envelope > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:B > ody><ns2:startCrawl > xmlns:ns2=" http://endeca.com/itl/file > "><crawlId><id>test</id></crawlId><crawlMode>FULL_CRAWL</crawl > Mode></ns2:startCrawl></soap:Body></soap:Envelope> > 0 > > === Same request sent from SOAP UI ==== > > POST /FileCrawlerService HTTP/1.1 > Content-Type: text/xml;charset=UTF-8 > SOAPAction: "" > User-Agent: Jakarta Commons-HttpClient/3.0.1 > Host: localhost:12000 > Content-Length: 381 > > <soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:file=" http://endeca.com/itl/file";> > <soapenv:Header/> > <soapenv:Body> > <file:startCrawl> > <crawlId> > <id>foobar</id> > </crawlId> > <!--Optional:--> > <crawlMode>?</crawlMode> > </file:startCrawl> > </soapenv:Body> > </soapenv:Envelope> > > === === > > Any idea what could be going on? Has CXF been tested for > WS-I compliance? > > Thanks! > Mike > > -- > Michael Matczynski > e: [EMAIL PROTECTED] > c: 617-388-4606 > w: www.zingtech.com > w: www.catchwine.com > ---------------------------- IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
