February 2007 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: Text nodes in SOAP messages

by thomas.diesler＠jboss.com

I assume comments are not white space. Is that right? anonymous wrote : | 2.5 Comments | | [Definition: Comments may appear anywhere in a document outside other markup; in addition, they may appear within the document type declaration at places allowed by the grammar. They are not part of the document's character data; an XML processor may, but need not, make it possible for an application to retrieve the text of comments. For compatibility, the string "--" (double-hyphen) must not occur within comments.] Parameter entity references are not recognized within comments. | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012935#4012935 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012935

17 years, 4 months

1
0
0 / 0

dependecy on snapshot

by Thomas Diesler

Hi Alex, could you please have a look at http://jira.jboss.org/jira/browse/JBWS-800 cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 4 months

2
4
0 / 0

[Design of JBoss Web Services] - Re: Text nodes in SOAP messages

by alex.guizar＠jboss.com

The above extract allows me to complete the checklist: SOAP-1.2 Envelope: whitespace only, insignificant Header: whitespace only, insignificant HeaderElement: any character, significant Body: whitespace only, significant BodyElement: any character, significant Fault: whitespace only, insignificant Detail: whitespace only, significant DetailEntry: any character, significant SOAP 1.1 does not explicitly allow or disallow them. The BP 1.2 explicitly disallows DTDs and PIs, but not text nodes. The only source of information on text nodes is the schema. All SOAP-1.1-defined elements have an element-only content type. Considering the validation rules from the XML Schema Part 1 (see below), SOAP-1.1 elements allow text nodes in the same way as their 1.2 counterparts, except that whitespace is always insignificant. anonymous wrote : 3.4.4 Complex Type Definition Validation Rules | [...] | If the {content type} is element-only, then the element information item has no character information item [children] other than those whose [character code] is defined as a white space in [XML 1.0 (Second Edition)]. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012781#4012781 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012781

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Text nodes in SOAP messages

by alex.guizar＠jboss.com

In the earlier post I missed the following extract from the SOAP 1.2 spec: anonymous wrote : 5. SOAP Message Construct | [...] | Element information items defined by this specification that only have element information items defined as allowable members of their [children] property can also have zero or more character information item children whose character code is amongst the white space characters as defined by XML 1.0 [XML 1.0]. Unless otherwise indicated, such character information items are considered insignificant. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012750#4012750 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012750

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Text nodes in SOAP messages

by alex.guizar＠jboss.com

According to the SOAP 1.2 section you quoted, text nodes are accepted in Body, but only if they are whitespace. The CTS actually adds non-whitespace text to a Body in the 1.2 namespace. SOAP 1.1 does not mention CIIs in Body, but that does not necessarily mean they are disallowed. Comparing the two schemas, neither seems to allow text context, unless it is white space for pretty-printing purposes. The CTS adds non-whitespace text to a Body in the 1.1 namespace as well. SOAP 1.1 Schema <xs:element name="Body" type="tns:Body"/> | <xs:complexType name="Body"> | <xs:sequence> | <xs:any namespace="##any" minOccurs="0" maxOccurs="unbounded" processContents="lax"/> | </xs:sequence> | <xs:anyAttribute namespace="##any" processContents="lax"/> | </xs:complexType> SOAP 1.2 Schema <xs:element name="Body" type="tns:Body"/> | <xs:complexType name="Body"> | <xs:sequence> | <xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> | </xs:sequence> | <xs:anyAttribute namespace="##other" processContents="lax"/> | </xs:complexType> Do we want to validate that only whitespace text is added? Furthermore, that SOAP 1.2 section specifies that unqualified elements and attributes are invalid. We do not currently check for that. How far do we want to go with validation? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012743#4012743 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012743

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JAX-WS documentation

by dwin

Woohoo!!!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012449#4012449 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012449

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - JAX-WS documentation

by thomas.diesler＠jboss.com

Folks, JAX-WS documentation work has started on http://tddell.dyndns.org/mediawiki Please fill in your bits at your earliest convenience. http://jira.jboss.org/jira/browse/JBWS-1307 This needs to get done before we can actually release jbossws-1.2.0 (which is now functionally complete). This work takes priority over CTS, because it is targeted for jboss-4.2 cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012310#4012310 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012310

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Text nodes in SOAP messages

by thomas.diesler＠jboss.com

I only looked at the specs for SOAPBody. Could you please look at the other SOAP elements before we jump to the conclusion that text is generally allowed/disallowed. Once we found out we challege the CTS with our findings. SOAP-1.1 Envelope: ? Header: ? HeaderElement: ? Body: no BodyElement: ? SOAP-1.2 Envelope: ? Header: ? HeaderElement: ? Body: yes BodyElement: ? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012308#4012308 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012308

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Text nodes in SOAP messages

by thomas.diesler＠jboss.com

SOAP-1.1 is also clear and does not allow text http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383503 anonymous wrote : | 4.3 SOAP Body | | The SOAP Body element provides a simple mechanism for exchanging mandatory information intended for the ultimate recipient of the message. Typical uses of the Body element include marshalling RPC calls and error reporting. | | The Body element is encoded as an immediate child element of the SOAP Envelope XML element. If a Header element is present then the Body element MUST immediately follow the Header element, otherwise it MUST be the first immediate child element of the Envelope element. | | All immediate child elements of the Body element are called body entries and each body entry is encoded as an independent element within the SOAP Body element. | | The encoding rules for body entries are as follows: | | 1. A body entry is identified by its fully qualified element name, which consists of the namespace URI and the local name. Immediate child elements of the SOAP Body element MAY be namespace-qualified. | 2. The SOAP encodingStyle attribute MAY be used to indicate the encoding style used for the body entries (see section 4.1.1). | | SOAP defines one body entry, which is the Fault entry used for reporting errors (see section 4.4). | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012304#4012304 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012304

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Text nodes in SOAP messages

by thomas.diesler＠jboss.com

The SOAP-1.2 spec is clear aout text in body and bodyElement http://www.w3.org/TR/soap12-part1/#soapbody anonymous wrote : | 5.3 SOAP Body | | A SOAP body provides a mechanism for transmitting information to an ultimate SOAP receiver (see 2.5 Structure and Interpretation of SOAP Bodies). | | The Body element information item has: | | * A [local name] of Body . | * A [namespace name] of "http://www.w3.org/2003/05/soap-envelope". | * Zero or more namespace qualified attribute information items in its [attributes] property. | * Zero or more namespace qualified element information items in its [children] property. | | The Body element information item MAY have any number of character information item children whose character code is amongst the white space characters as defined by XML 1.0 [XML 1.0]. These are considered significant. | anonymous wrote : | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012303#4012303 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012303

17 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev February 2007