Notice that the <xsd:import> element is required to specify a
namespace and optionally may specify a schema location.  When there is
a schema location, it is only a hint to the processor, which may
preferably use other information (such as the externalSchemaLocations
property in xerces or an attached EntityResolver) to find the schema
grammar associated with the namespace.  In particular, the particular
implementation of the EntityResolver interface may store a table of
namespace -> schema file mappings and resollve the namespace URI to
the schema document.

Jeff

On 4/7/06, Martin Gainty <[EMAIL PROTECTED]> wrote:
> Good Evening Jeff-
> would you be prohibited from storing the local url (which resolves the
> remote url) on a local file?
> Many Thanks for your thoughtful response,
> Martin--
>
> "As far as the laws of mathematics refer to reality, they are not certain,
> as far as they are certain, they do not refer to reality."  - Albert
> Einstein
> ----- Original Message -----
> From: "Jeff Greif" <[EMAIL PROTECTED]>
> To: <[email protected]>; "Martin Gainty" <[EMAIL PROTECTED]>
> Sent: Friday, April 07, 2006 8:22 PM
> Subject: Re: Monitor progress of an AXIS SOAP request and response over http
> transport
>
>
> You keep a local copy of the schema and define an
> org.xml.sax.EntityResolver to return an InputSource constructed on the
> local url when resolving the remote url.  You do *not* change the
> namespaces.
>
> Alternatively, you add external schema locations to the parser for the
> namespaces in question, associating each namespace with a local file
> containing the schema definition.  This works with Xerces parsers and
> possibly others.
>
> If you have local copies, you can modify the <import> elements to
> point to the local copies, and modify the wsdl (for which you
> presumably also have a local copy) to point to the local copy of the
> schemas it references.
>
> Jeff
>
> On 4/7/06, Martin Gainty <[EMAIL PROTECTED]> wrote:
> >
> > how is the schema resolved when there is no access to outside environment?
> > M-
> >

Reply via email to