Good Morning Jeff--
The analogy i think of is that
when one travels from point A to point B one must stop at a number of way
points to acquire additional directions on how best to route to take to
their target goal
Most folks including myself would rather go from Point A to Point B to avoid
incurring overhead and time lag from processing activities of intervening
nodes
i.e. a shortcut
a real world example is an static ip route entry where one can say all
transmissions from point A to Point B must pass thru intervening node (e.g.
Princeton)
If implementor has apriori knowledge of which schema file mapping to use for
intended xsd:import
where could the implementor acquire information on how to configure
processor to use the intended schema file mapping?
Many Thanks for your thoughtful response,
Martin--
"One aspect of this is that rationality of thought imposes a limit on a
person's concept of his relation to the cosmos."
-- John Nash --
----- Original Message -----
From: "Jeff Greif" <[EMAIL PROTECTED]>
To: <[email protected]>; "Martin Gainty" <[EMAIL PROTECTED]>
Sent: Saturday, April 08, 2006 10:13 AM
Subject: Re: Monitor progress of an AXIS SOAP request and response over http
transport
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-
>
