Thanks for the suggestions! Turning off chunking in the client fixed this WS-I conformance issue, but exposed another one...
It looks like the Content-Type HTTP header is not being set properly on messages sent from the server. Apparently the "charset" value must be set when the "Content-Type" property is specified. Example server header: HTTP/1.1 200 OK Content-Type: text/xml (should also have charset=UTF-8) SOAPAction: "" Content-Length: 174 Server: Jetty(6.1.3) Is there a way to make "Content-Type" equal to "text/xml; charset=UTF-8" programmatically using the API (JaxWsServerFactoryBean)? Thanks! Mike On 6/27/07, Sergey Beryozkin <[EMAIL PROTECTED]> wrote:
Thanks, seems like the HTTP layer can be tuned a lot :-) Cheers, Sergey > -----Original Message----- > From: Sergey Beryozkin [mailto:[EMAIL PROTECTED] > Sent: 27 June 2007 19:05 > To: [email protected] > Subject: Re: WS-I Compliance / SOAP Messages > > Looks like the WS-I monitor can not deal with > > > Transfer-Encoding: chunked Yep, I think you're right Sergey. > I'm wondering, is it possible to configure CXF not to use > chunked mode ? Yep again, see my last mail on this thread. > Cheers, Sergey ---------------------------- IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland ---------------------------- IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
-- Michael Matczynski e: [EMAIL PROTECTED] c: 617-388-4606 w: www.zingtech.com w: www.catchwine.com
