Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (herse.apache.org: domain of enjoyjava@gmail.com designates
 209.85.146.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:from:to:cc:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole;
        b=hRY/LFszW9UaovM5GRUGdWV7J0WGwtLgI3VNsWAIQyKOV4OII6wPK0FZqhV6KfHaG1amEUAlq55BgWueiQFmLO17LG5TI/bvtx2nIcEnmWO1B5vxSDNv2hOT3g1m8xoUuOr0OE4gSuXbHClIH1P1G1kgiip/Z11bkEMsw/hYulQ=
Message-ID: <01c601c7ce44$73a15780$6601a8c0@rfengt60p>
From: "Raymond Feng" <enjoyjava@gmail.com>
To: <axis-dev@ws.apache.org>
Cc: <tuscany-dev@ws.apache.org>
Subject: [XmlSchema] Pluggability for XSD import/include resolvers?
Date: Tue, 24 Jul 2007 15:46:18 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit

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 attribute for the <xsd:import> or <xsd:include> is set.

Now we would like to handle the cases where the schemaLocation attribute is 
not present. For example, <xsd:import namespace="http://ns1"/>. Without the 
schemaLocation, we resolve the import/include by namespace. In this case, we 
already have a map keyed by namespace for a list of XmlSchema objects loaded 
from a catalog or other files and we want to reuse them. Would it be 
possible to open the XmlSchemaCollection.getSchema(SchemaKey) method so that 
we can override/customize the behavior to associate existing XmlSchema 
instances to a SchemaKey? BTW, using a singleton of XmlSchemaCollection to 
keep the schema map is not always feasible.

Another observation is that a NPE will be thrown if the 
URIResolver.resolveEntity() returns null. Is there any way to disable the 
aggressive resolving/loading of import/include?

rfeng@apache.org
Raymond Feng
Apache Tuscany 


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org