• From: "Anthony B. Coates (XML-Dev)" <abcoatesecure-xmldev@y...>
• To: xml-dev@l...
• Date: Tue, 08 Sep 2009 20:45:05 +0100

I forgot to mention previously that the Londata XML Catalogs  
implementation for .NET supports log4net logging so that you can debug  
your XML Catalogs.  Myself, I find that it can be easy to get stuck - your  
catalog looks correct, but doesn't work as you expected.  So, if you need  
it, the Londata tool lets you see in detail, via logging, how your URIs  
are (or aren't) being resolved using your XML Catalogs.

I've written a new page describing it, and showing the kind of detail that  
is available:

http://londata.svnrepository.com/xmlcatalog.net/trac.cgi/wiki/XmlCatalogLoggingDebugging

Questions and comments are welcome.

Cheers, Tony.

On Sun, 06 Sep 2009 15:39:54 +0100, Anthony B. Coates (XML-Dev)  
<abcoatesecure-xmldev@y...> wrote:

> The OASIS XML Catalog specification allows you specify how Schema/etc.
> locations in XML files are translated to actual file locations on your
> machine. For example, a Schema location that is a URL to a remote Web
> server can be converted into a file location on your machine, speeding up
> the validation and increasing security. I have posted a .NET
> implementation of OASIS XML Catalogs to
>
> http://xmlcatalog.net/
>
> Questions and comments are welcome.
>
> Thanks, Cheers, Tony.

-- 
Anthony B. Coates
Director and CTO
Londata Ltd
UK: +44 (20) 8816 7700, US: +1 (239) 344 7700
Mobile/Cell: +44 (79) 0543 9026
Data standards participant: genericode, ISO 20022 (ISO 15022 XML),  
UN/CEFACT, MDDL, FpML, UBL.
http://www.londata.com/

• References:
  • OASIS XML Catalogs implementation for .NET
    • From: "Anthony B. Coates (XML-Dev)" <abcoatesecure-xmldev@y...>