Changing the catalog entry from
<public publicId="http://www.ivoa.net/xml/STC/STCcoords/v1.10";
uri="STCcoords-v1.10.xsd"/>
to:
<system systemId="http://www.ivoa.net/xml/STC/STCcoords/v1.10";
uri="STCcoords-v1.10.xsd"/>
still requires adding the `schemeLocation` attribute in the `<import>`
element otherwise the types of the imported schema are not found.
That is, I still need to modify the XSD schema (which only has an
`<import>` element without a `schemaLocation` attribute).
Can you elaborate a bit more on public versus system entries? I am not sure
I get all the nuances.
On Thu, Sep 26, 2013 at 5:42 PM, Aki Yoshida <[email protected]> wrote:
> that's not a public id.
> can you use the system entry instead?
>
>
> 2013/9/26 Menelaos Perdikeas <[email protected]>:
> > I am using Apache CXF 2.7.6 `wsdl2java` and it seems that the tool
> ignores
> > or fails to find public catalog entries. In particular I have the
> following
> > `<xs:import>` in one of my XSD files:
> >
> > <xs:import namespace="http://www.ivoa.net/xml/STC/STCcoords/v1.10"/>
> >
> > The above cannot be properly resolved with the catalog file entry:
> >
> > <public publicId="http://www.ivoa.net/xml/STC/STCcoords/v1.10";
> > uri="STCcoords-v1.10.xsd"/>
> >
> > If I change the `<xs:import>` by adding a `schemaLocation` attribute,
> i.e.
> > change it to:
> >
> > <xs:import namespace="http://www.ivoa.net/xml/STC/STCcoords/v1.10";
> > schemaLocation="http://www.ivoa.net/xml/STC/STCcoords/v1.10/>
> >
> > It resolves files, but my understanding is that this shouldn't have been
> > necessary as I don't want to have to edit the XSD I am provided with.
> >
> > The behavior is the same whether OASIS XML format or TR9401 format is
> used.
> > Kind Regards,
> > Menelaus.
>
