cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <dk...@apache.org>
Subject Re: xml-version missing in soap message
Date Tue, 28 Oct 2008 16:28:45 GMT
On Tuesday 28 October 2008 12:18:51 pm Glen Mazza wrote:
> Hmmm...aren't XML processing instructions forbidden with SOAP requests and
> responses, per the SOAP spec--or is the XML tag not considered a PI?

According to the xml spec grammar, the xml tag is an "XMLDecl" and not really 
a PI.

In anycase, the WSI-BasicProfile basically states that toolkits should accept 
messages with the xml decl, but not really create one.   If the xml-decl is 
there, it's pretty much ignored as the charset and stuff comes from the HTTP 
content-type header.   Thus, the xml decl really is just wasted bandwidth.

Dan



>
> Glen
>
> dkulp wrote:
> > According to spec, the xml version tag it not required.   It's basically
> > just
> > redundant information that consumes bandwidth and uses more CPU.    
> > Thus, this is technically a bug in whatever implementation you have on
> > your server.
> >
> > That said, I believe you can do:
> >
> > ((BindingProvider)port).getRequestContext()
> >    .put("org.apache.cxf.stax.force-start-document", Boolean.TRUE)
> >
> > to force it.   That may require one of the very recent versions of CXF.
> >
> > Dan



-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog

Mime
View raw message