Um .. not sure why I saw this note now and replied ... its an old thread!!!! Sorry guys; need more coffee.
Sanjiva. On Tue, 2005-08-16 at 13:16 +0600, Sanjiva Weerawarana wrote: > On Wed, 2005-07-27 at 14:42 +0530, Venkat Reddy wrote: > > Why should we limit the infoset support at SOAP Model? Is it for > > performance or for compliance with the spec? I don't think we should > > limit it, unless it is proved to be costly for perf. > > We should limit it because its totally illegal in SOAP for the XML > content of headers and payload to contain certain things (like PIs). > > > On 7/28/05, Eran Chinthaka <[EMAIL PROTECTED]> wrote: > > > Hi all, > > > > > > We all know that in StAXSOAPModelBuilder, we do not support the full > > > infoset > > > of XML. But think about the following scenario. > > > Body can contain any XML junk inside it. So that XML part may contain PIs, > > > DTDs, etc., > > > SO if you wanna give access to the parts within the body through > > > StAXSOAPModelBuilder, we will have problem. > > > So what can we do for this ?? > > I think if you build with StAXSOAPModelBuilder then you've already been > asked to create a valid *SOAP Infoset*, not an arbitrary XML Infoset. In > this case the Body *MUST NOT* contain any old junk .. it must be XML > which follows the SOAP rules. > > As such I don't see a problem with the behavior as it stands now. > > +1 for adding comment support however because those are indeed allowed > in SOAP! > > Sanjiva. > > >
