Chris Simmons wrote on 10/17/2011 12:22:09 PM:
> I'd be interested in hearing from anyone involved in the original
> spec for catalogs as to whether rewriteURI was intended for
> namespace URI's or not. I suspect it wasn't considered at the time
> and hence there's no consensus.
Norm Walsh wa
Mapping namespace URIs to schemas via resolveURI is perfectly acceptable,
especially if there is no schemaLocation value (or "respect schema
locations" has been turned off).
The schema design has always left it flexible how a processor maps documents
to schemas and mapping namespaces to schema doc
On 14/10/11 20:20, Mark R Maxey wrote:
Xerces Java Users,
Xerces is failing to correctly resolve XSDs to their locations using
XML catalogs that prefer public IDs during the loading of the XSDs for
schema validation. After extensive debugging, we've found that the
following method out of _XM
One final comment on our use case:
When doing XSD validation, you have to be able to tell the validator which
XSD to use. We have 130+ namespaces and 300-400 XSDs. For every type of
XML instance document, we had to have a piece of configuration that told us
which XSD that document maps to. Tha
t; Modifying the XSDs is less painful if it is only done at build
>>> time and then deployed. I'm going to need to think about whether we
>>> want to continue this practice and/or use the XML catalogs with system IDs
>>> ...
>>> >
>>> >
>>
. I'm going to need to think about whether we
>> want to continue this practice and/or use the XML catalogs with system IDs
>> ...
>> >
>> >
>> >
>> > Mark
>> >
>> >
>> > Chad La Joie ---10/17/2011 07:30:51 AM---We'
10/17/2011 07:30:51 AM---We've run in to this
> before as well. Is there any reason you can't just change the
schemalocations
> >
> >
> > From:
> > Chad La Joie
> > To:
> > j-users@xerces.apache.org
> > Date:
> > 10/17/2011 07:30 AM
> >
> Chad La Joie ---10/17/2011 07:30:51 AM---We've run in to this before as well.
> Is there any reason you can't just change the schema locations
>
>
> From:
> Chad La Joie
> To:
> j-users@xerces.apache.org
> Date:
> 10/17/2011 07:30 AM
> Subject:
> Re:
1 07:30 AM
Subject: Re: JAXP XML Catalog Resolver for
We've run in to this before as well. Is there any reason you can't
just change the schema locations to point to local files? That was
the only truly reliable method we could find that worked across all
our XML processing stacks.
On Mon, Oct 17, 2011 at 08:16, Mark R Maxey wrote:
>
> Thank you a
52 PM
Subject: Re: JAXP XML Catalog Resolver for Publi
Mark,
Mark R Maxey wrote on 10/14/2011 06:03:08 PM:
> Thank you for your quick response.
>
> I'll confess we've struggled mightily with XSD resolution. We turned
> to XML catalogs hoping the namespace to URI mapping would allow us
> to work around invalid schemaLocations. Our (bad?) idea was to
Date: 10/14/2011 02:51 PM
Subject:Re: JAXP XML Catalog Resolver for Public IDs
Mark,
This is not a bug. A public
Mark,
This is not a bug. A public ID is not a target namespace or vice versa.
Xerces passes the parameters in their correct positions [1] to the
LSResourceResolver.
If you want to process a namespace URI as if it were a public ID you can
extend the XMLCatalogResolver and override resolveResource(
14 matches
Mail list logo
