Jean-Sebastien Delfino wrote:
Huang Kai wrote:
Hi, Raymond,
We encountered the same problem when implementing SDO's XSDHelper.
Where we used EMF's xsd tool package for resolve xsd. Wherein we just
implemented our own XSDSchemaLocator and added it to the resource's
adapters, then we can do
Huang Kai wrote:
Hi, Raymond,
We encountered the same problem when implementing SDO's XSDHelper. Where we
used EMF's xsd tool package for resolve xsd. Wherein we just implemented our
own XSDSchemaLocator and added it to the resource's adapters, then we can do
everything in locating the imp
ort/include xsd. It works fine.
I don't know if XmlSchema have any thing alike.
- Original Message -
From: "Mike Edwards" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, July 25, 2007 9:33 PM
Subject: Re: [XmlSchema] Pluggability for XSD import/include resolvers?
> Ra
/ns1) as the key to find the
matching schema (which contains the type/element definitions referenced by
a.xsd) from another artifact(s).
Thanks,
Raymond
- Original Message -
From: "Mike Edwards" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, July 25, 2007 6:33 AM
Subject:
Raymond,
How does this relate to the contribution resolution mechanism described
by the SCA specifications?
Yours, Mike.
Raymond Feng wrote:
Hi,
We currently use XmlSchema to load XSDs. To resolve the import/include
directives using our schemes, we provide an implementation of
org.apache
Hi,
We currently use XmlSchema to load XSDs. To resolve the import/include
directives using our schemes, we provide an implementation of
org.apache.ws.commons.schema.resolver.URIResolver and set it to
org.apache.ws.commons.schema.XmlSchemaCollection. It works well if the
schemaLocation attrib
