DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13420>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13420

Dynamic Validation not ignoring complex type without schema

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |
            Summary|Complex Validation not      |Dynamic Validation not
                   |catching error              |ignoring complex type
                   |                            |without schema



------- Additional Comments From [EMAIL PROTECTED]  2002-10-10 21:28 -------
I tried running my example with the newest version of xerces from 
http://gump.covalent.net/jars/latest/xml-xerces2/ and indeed, with dynamic 
validation switched on, the error in the instance document which had a 
respective schema was correctly reported.  However, I tried adding a complex 
type to my instance document that did not have a schema, and the validator 
still reported an error.  Below I have added the new instance document and 
error message.  The java code and schema remain as in the initial bug report.

Ben

INSTANCE DOCUMENT REVISED (D) envelope.xml
-----------------------------

<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
                                   xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance"
                                   xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
        <SOAP-ENV:Body>
                <ns1:addEntry xmlns:ns1="urn:AddressFetcher" SOAP-
ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
                        <nameToRegister 
xsi:type="xsd:string">Ben</nameToRegister>
                        <xaddress xmlns:ns2="urn:xml-soap-address-demo" 
xsi:type="ns2:address">
                                <city xsi:type="xsd:string">Cambridge</city>
                                <phoneNumber xsi:type="ns2:phone">
                                        <areaCode 
xsi:type="xsd:int">607</areaCode>
                                        <exchange 
xsi:type="xsd:string">339</exchange>
                                        <number 
xsi:type="xsd:string">1540</number>
                                </phoneNumber>
                                <state xsi:type="xsd:string">MA</state>
                                <streetName 
xsi:type="xsd:string">JFK</streetName>
                                <streetNum xsi:type="xsd:int">50</streetNum>
                                <zip xsi:type="xsd:int">2138</zip>
                        </xaddress>
                        <foo 
xmlns:ns3="http://www.lws.ibm.com/namespace/wstypes"; xsi:type="ns3:object">
                                <b xsi:type="xsd:string">bonjour</b>
                                <a xsi:type="xsd:string">hello</a>
                                <num xsi:type="xsd:short">5</num>
                        </foo>
                </ns1:addEntry>
        </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

ERROR MESSAGE (E)
-----------------
ERROR: cvc-complex-type.2.4.a: Invalid content starting with element 'zip'. The
content must match 'all(("":city),("":phoneNumber),("":state),("":streetName),("
":streetNum),("":zips))'.
ERROR: cvc-elt.4.2: Cannot resolve 'ns3:object' to a type definition for element
 'foo'.
ROOT: SOAP-ENV:Envelope

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to