Unashamedly geek post this. I my role as a data architect, I’ve been playing with Altova Schema Agent to manage XML schemas & WSDLs. Here’s the best way I’ve found to set things up for local development purposes:The first problem you’ll notice is that you can’t just throw a bunch of files at it. It’ll load your schemas & WSDLs OK, but will also try & resolve and any imports etc, so you’re left with a bunch of un-resolvable imports, if your namespaces don’t resolve to a real world interwebs address, which most don’t.So, you’ll have to serve the schemas up locally using something good like Apache 2.2. Installing it is trivial, so I won’t go into that, but you’ll need to make some changes to the configuration file httpd.conf.
Turn on WebDAVSo schema agent can traverse all your schemas, you’ll need to turn on WebDAV in Apache.
LoadModule dav_module modules/mod_dav.soand add
LoadModule dav_lock_module modules/mod_dav_lock.so
Point Apache At Your Schemas
Assuming your schemas are just served up off the root of your local apache, you’ll need to set the document root, say
Then you’ll need a Directory tag to specify that WebDAV should be turned on
Options Indexes FollowSymLinks
Allow from all
<LimitExcept GET PROPFIND OPTIONS REPORT>
Dav On turns on WebDAV for that folder and the LimitExcept tag will disallow all HTTP operations except those listed, so you can turn on write access if you need it too. This can be useful as Schema Agent integrates with XMLSpy so you can browse & edit schemas directly from Schema Agent.