migrating xml schema definitions from v2 to v3 ?

[Cantor, Scott]

On 2/28/13 5:29 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:

>I remember that incident.  I wondered at the time whether that was due
>to our misuse of spring.schemas and corresponding overriding of the
>entity resolver (?) that makes what we did actually work.  IIUC with a
>default Spring beans setup and their standard stuff, it should not fetch
>remotely since the schemas are stored in their jars and (properly)
>referenced using a spring.schemas file.  I speculate that since we
>mucked with the resolution process, their schemas were no longer locally
>resolvable, so it fell back to trying to fetch remotely.

Certainly plausible. Just means we have to do more work I guess.

>I think it's fine to try in general, but Spring specifically might be
>problematic.  Maybe there's a way to introduce a different XML catalog
>type of thing, rather than their own catalog-ish type of approach (i.e.
>the spring.schemas stuff).  But I've never seen any docs on this,
>everything always seems to assume use of schemaLocation.  So I think
>we'll probably be on our own in trying to figure out how to do this for
>Spring's stuff.

I'm used to that. I think at this point we should be able to rely on real
catalogs for this stuff, Xerces-J should have decent support for that.

-- Scott