cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Matczynski" <>
Subject WS-I Compliance / SOAP Messages
Date Wed, 27 Jun 2007 17:56:05 GMT
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

=== 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

<soap:Envelope xmlns:soap=""><soap:Body><ns2:startCrawl

=== 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=""

=== ===

Any idea what could be going on?  Has CXF been tested for WS-I compliance?


Michael Matczynski
c: 617-388-4606

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message