Michael, thanks for the feedback. The encryption complicates other things so I have removed it. Now the schemas are accessible through plain text http. But now I have discovered another problem: validation takes a long-long time to complete (and it almost never completes). E.g. for 70-80 files it takes it almost ten minutes and somewhere in the middle it throws this kind of errors:
[xmlvalidate] D:\mypath\myfile.xml:8:353: schema_reference.4: Failed to read schema document http://mydomain/schemas/myschema.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>. [xmlvalidate] D:\mypath\myfile.xml:8:353: cvc-elt.1: Cannot find the declaration of element 'myrootelement'. ...and sometimes with: [xmlvalidate] http://mydomain/schemas/myschema.xsd:29:90: schema_reference.4: Failed to read schema document 'someimported.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>. During the whole operation the CPU load is minimal (1% -- like nothing happens). I have looked into the network activity and there are many schema requests (since schemas are not cached by default), but the network is far from being chocked and the server seems to reply promptly. I am using Xerces 2.7.1 through Ant 1.6.5, therefore I am looking for a way to configure Xerces, if possible, without Java coding (e.g. enabling caching by setting some property through Ant -- is that possible?). Please help. Adrian. Michael Glavassevich wrote: > Adrian Herscu <[EMAIL PROTECTED]> wrote on 09/24/2006 11:24:02 AM: > Hi all, >> Using Xerces 2.7.1 through Maven 2.0.4. I need to store XML schemas on our development site. The access to this site is only through password authenticated SSL. I've managed to find an workaround for MSXML4.0 by inserting the username and password in the URL (https://username:[EMAIL PROTECTED]/path/schema) -- of course all our XML files will have usernames and password in them... Anyway, this does not work for Xerces either :-( The following error is reported by Maven: >> [xmlvalidate] D:\mylocalpath\Foo.xml:8:390: schema_reference.4: Failed to read schema document 'https://me:[EMAIL PROTECTED]/Foo.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>. >> Followed by: >> [xmlvalidate] D:\mylocalpath\Foo.xml:8:390: cvc-elt.1: Cannot find the declaration of element 'class'. >> Maven can connect to our artifacts repository through https using the same credentials, therefore I assume that there is no configuration problem on the JRE level. >> Any suggestions? > > Have you tried plugging in an EntityResolver which returns an InputStream > from the URL (i.e. new java.net.URL(" > https://me:[EMAIL PROTECTED]/Foo.xsd").openStream())? If that doesn't > work for you it won't work for Xerces either (since this is what the > parser does when presented with a URI as input). > TIA, Adrian. >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: [EMAIL PROTECTED] > E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
