Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Expecting no namespace, but the schema document has a target namespace

Expecting no namespace, but the schema document has a target namespace

2003-01-13       - By sandygao@(protected)
Reply:     1     2     3  

Xerces defers the loading of schemas. That is, a schema is loaded only when
something from its target namespace is required. In your case, your xsd
file will only be read if the namespace "
http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2
" is referenced. I don't think it's referenced, because there is even no
namespace declaration for that namespace.

I also planned to reply your other mail. Here it goes:

> 1a) I did _NOT_ see any attempt to retrieve the SOAP schema, as
> specified by the root element  attribute:
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"

Schema locations are specified using one of the xsi schema location
attributes, like what you did for the MM7 schema. A namespace declaration
like the above doesn't mean the parser needs to retrieve a schema for that
namespace, not to mention that the parser doesn't know where to retrieve
such schema.

To fix it, add an xsi:schemaLocation attribute for this namespace. So the
result would something like:
xsi:schemaLocation="mm7_namespace mm7.xsd soap_namespace soap.xsd"

This is also the reason why you are seeing the cvc-elt error. You didn't
provide a location for the soap namespace, so Xerces couldn't find a
declaration for your root element.

> Are you also saying that Xerces _can_ do Schema validation _without_ DTD
> validation

If there is no DTD in your instance, then Xerces only does schema
validation. But if you do have a DTD, Xerces validates the instance against
both kinds of grammars. This is not correct as per JAXP. We'll fix it so
that when schemaLanguage==xmlschema, no DTD validation is performed.

Cheers,
Sandy Gao
Software Developer, IBM Canada
(1-905) 413-3255
sandygao@(protected)



                                                                             
                                                       
                     "Jesus M. Salvo                                          
                                                       
                     Jr."                     To:       xerces-j-user@(protected)
.apache.org                                                  
                     <jesus.salvo@(protected)        cc:                            
                                                       
                     sia.com>                 Subject:  Re: Expecting no
namespace, but the schema document has a target namespace    
                                                                             
                                                       
                     01/13/2003 06:05                                        
                                                       
                     PM                                                      
                                                       
                     Please respond to                                        
                                                       
                     xerces-j-user                                            
                                                       
                                                                             
                                                       
                                                                             
                                                       




Sandy,

Thanks for the reply, but ....

I just changed the my SOAP envelope so that the root document is now, as
you have suggested, like this:

<?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"
   xsi:schemaLocation=

"
http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2


http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2.xsd
">


But the problem now is it does not even seem to try or perform a schema
validation.
Running a sniffer, no attempt has been made by the parser to retrieve
the schema document from www.3gpp.org.
But I do still get the following error, also reported on my original post:

Error: URI=null Line=8: cvc-elt.1: Cannot find the declaration of
element 'SOAP-ENV:Envelope'.


The only way I could achieve some level of schema validation is by using
xsi: noNamespaceSchemaLocation, as mentioned in here:

http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JAXPDOM9.html

I would prefer declaring the schemas in the XML document itself ...
rather than assigning them by code.

Any ideas?

Thanks

John


sandygao@(protected) wrote:

>In your instance document:
>
>
>
>>xsi:noNamespaceSchemaLocation="
>>
>>
>http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2.xsd

>">
>
>which means that your xsd file doesn't have a target namespace. But in
your
>schema:
>
>
>
>>targetNamespace
>>
>>
>="
http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2
"
>
>
>A contradiction!  So Xerces is right in reporting an error.  To fix it,
>instead of using xsi:noNamespaceSchemaLocation, use xsi:schemaLocation,
>like this:
>
>xsi:schemaLocation="
>http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2

>http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2.xsd

>"
>
>Cheers,
>Sandy Gao
>Software Developer, IBM Canada
>(1-905) 413-3255
>sandygao@(protected)
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
>For additional commands, e-mail: xerces-j-user-help@(protected)
>
>
>
>


--
Jesus M. Salvo Jr.
Mobile Internet Group Pty Ltd
(formerly Softgame International Pty Ltd)
M: +61 409 126699
T: +61 2 94604777
F: +61 2 94603677

PGP Public key:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0BA5348



---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)





---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)