Hi James, Could you provide more description about your problem? Most importantly, which version of Xerces are you using? And which version of XML4J does the personal-schema.xml come with?
If you are using Xerces 1.3.1, make sure it's "http://www.w3.org/2000/10/..."; in your .xml and .xsd files; and if you are using Xerces 1.4.0 (the latest version), make sure it's "http://www.w3.org/2001/..."; Cheers, Sandy Gao Software Developer, IBM Canada (1-416) 448-3255 [EMAIL PROTECTED] James Liu <[EMAIL PROTECTED] To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> dServ.com> cc: Subject: RE: Namespaces and schema locations 05/23/2001 03:55 PM Please respond to xerces-j-user Hi, I couldn't even parse the example personal-schema.xml comes with XmL4J, if I turn on the feature http://xml.org/sax/features/validation, the parser always report elements not defined. BTW, do I still need the DTD when I turn to schema? thanks a lot, James -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 23, 2001 2:36 PM To: [EMAIL PROTECTED] Subject: Re: Namespaces and schema locations Hi Ivan, This might cause the problem: xsi:schemaLocation="http://com.csfb.equity.isis/report http://com.csfb.equity.isis/schema/Report.xsd"; It says that for namespace "http://com.csfb.equity.isis/report";, its corresponding xsd can be found at " http://com.csfb.equity.isis/schema/Report.xsd";. But the parser can't find the specified file (my browser couldn't either). If your .xml and .xsd file are in the same folder, try change it to: xsi:schemaLocation="http://com.csfb.equity.isis/report Report.xsd" Hope this helps, Sandy Gao Software Developer, IBM Canada (1-416) 448-3255 [EMAIL PROTECTED] "O'Connor, Ivan" To: [EMAIL PROTECTED] <ivan.o'connor cc: @csfb.com> Subject: Namespaces and schema locations 05/23/2001 01:18 PM Please respond to xerces-j-user I'm having a problem specifying (or understanding) namespaces - any help would be appreciated. My schema document looks roughly like this: <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns="http://com.csfb.equity.isis/report"; targetNamespace="http://com.csfb.equity.isis/report";> ... lots of definitions here... <xsd:element name="report" type="reportType"/> </xsd:schema> As far as I understand it, this says that the default namespace is http://com.csfb.equity.isis/report, and the target namespace is the same. Any elements without a prefix belong to the default namespace. In my instance document I have the following: <report xmlns ="http://com.csfb.equity.isis/report"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://com.csfb.equity.isis/report http://com.csfb.equity.isis/schema/Report.xsd";> ... the report specification goes here... </report> This should, I believe, associate the namespace http://com.csfb.equity.isis/report with my schema definition, Report.xsd. When I run this through the parser (developed with Xerces-J 1.3.0) I get the following error: Error: org.xml.sax.SAXParseException: General Schema Error: Grammar with uri 2: http://com.csfb.equity.isis/report , can not found. Can anyone shed any light on this? Thanks, Ivan This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. CREDIT SUISSE GROUP and each of its subsidiaries each reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Unless otherwise stated, any pricing information given in this message is indicative only, is subject to change and does not constitute an offer to deal at any price quoted. Any reference to the terms of executed transactions should be treated as preliminary only and subject to our formal written confirmation. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
