I should have missed something because even if I used the CatalogResolver, it's like it's not using it. I have set (via setProperty) the debug level + the catalog list, and it's still using the schemaLocation declaration from my XML file to find the associated schema (not DTD).
Same if I use the XMLCatalogResolver (using the setCatalogList to set the catalog lists). I am just wondering which key is used for the resolution when you use a schema and not a DTD. Lydie. -----Original Message----- From: Michael Glavassevich [mailto:[EMAIL PROTECTED] Sent: Monday, September 25, 2006 15:56 To: [email protected] Subject: RE: Trying to validate XML files using several XSD No. You have to use the xml-commons resolver directly if you want to set that. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] "Decoker, Lydie \(Lydie\)" <[EMAIL PROTECTED]> wrote on 09/25/2006 08:01:12 AM: > Is there a way to setup the "verbose" mode too? > > -----Original Message----- > From: Michael Glavassevich [mailto:[EMAIL PROTECTED] > Sent: Monday, September 25, 2006 13:52 > To: [email protected] > Subject: RE: Trying to validate XML files using several XSD > > Settings in that properties file have no effect on it. Use > XMLCatalogResolver.setCatalogList() [1]. > > [1] > http://xerces.apache.org/xerces2-j/javadocs/xerces2/org/apache/xerces/ > ut > il/XMLCatalogResolver.html#setCatalogList(java.lang.String[]) > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: [EMAIL PROTECTED] > E-mail: [EMAIL PROTECTED] > > "Decoker, Lydie \(Lydie\)" <[EMAIL PROTECTED]> wrote on 09/25/2006 > 07:16:19 AM: > > > Thx! > > Does it mean that XMLCatalogResolver does not use CatalogManager. > > properties at all? > > > > Lydie > > > > > > Take a look at this thread : > > > > http://www.mail-archive.com/[email protected]/msg00826.html > > > > I have not tested this, but from the symptoms you report this may > > work > > > for you. > > > > Excerpt from the above emial: > > >Hi Mark, > > > > > The settings of system properties for the xml-commons resolver > > > have no > > > > effect on an XMLCatalogResolver. This is by design [1]. You need > > > to > set > > > the catalog list [2] on each instance of XMLCatalogResolver you > create. > > > > > Thanks. > > > > > [1] http://mail-archives.apache.org/mod_mbox/xerces-j- > > users/200401.mbox/[EMAIL PROTECTED] > > > [2] http://xerces.apache.org/xerces2- > > j/javadocs/xerces2/org/apache/xerces/util/XMLCatalogResolver. > > html#setCatalogList(java.lang.String[]) > > > > > Michael Glavassevich > > > > -Prashant > > > > Decoker, Lydie (Lydie) wrote: > > I have corrected my CatalogManager.properties to: > > > > #CatalogManager.properties > > > > verbosity=10 > > > > # Always use semicolons in this list > > > > catalogs=C:\data\Teliasonera\Development\NeBiLight_Dvlpt\NeBi_JMSInt > > er > > fa > > ce\config\Catalog.xml > > > > prefer=public > > > > The Catalog.xml: > > > > <?xml version="1.0" encoding="UTF-8"?> <catalog > > xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"> > > <uri name="http:/my.uri.com/GRIPP/jmsProperties" > > uri="file:///C:/data/JMS_properties.xsd" > > > > </catalog> > > > > I have set the verbose mode to 3 for the catalog but I do not get > > any output on my console :o( I still have the same error: > > > > Failed to read schema document 'JMS_properties.xsd', because 1) > > could not find the document; 2) the document could not be read; 3) > > the root element of the document is not <xsd:schema>. > > > > Not sure the catalog is really used. > > > > 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] > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
