On Wed, Mar 18, 2009 at 7:34 PM, Luciano Resende <[email protected]> wrote:

> I think the issue is, when wsdlLocation and schemaLocation is
> provided, but it fails to properly resolve... should we fall back to
> the SCA resolution mechanism or should we fail.

We do have to deal with this issue.

However, I think we first have to deal with what it means to say that,
for example:  "@schemaLocation was provided but fails to properly
resolve".

So in addition to being an SCA runtime we're also a runtime that
supports XSD imports, and it seems we must define what the behavior of
our non-SCA mechanism for resolving XSD imports is.

In TUSCANY-2906, I'm suggesting that for our non-SCA XSD import, we at
least look within the current contribution in the case that
@schemaLocation is specified but incorrect/invalid.   And I'd argue
the same for WSDL import with @location.  (Hadn't considered
@wsdlLocation).

On Wed, Mar 18, 2009 at 7:55 PM, Raymond Feng <[email protected]> wrote:
> IMO, if the wsdlLocation/schemaLocation fails to resolve the artifacts, we
> should not try to use the SCA way.

I agree the OSOA and OASIS specs clearly state we should not use the
SCA way (contribution import) if we cannot find the XSD or WSDL with
our non-SCA mechanisms.

The thing which bothers me is this:  how is one actually supposed to
use the SCA way (contribution import)?  We do make it difficult.   For
example, I guess you have to make sure never to use xsd:import
@schemaLocation(s).   If you'd like to refactor a set of schemas into
their own contribution, you might have to go remove existing
@schemaLocation(s).    I imagine that the spec is written the way it
is to cut down the complexity of chained imports and competing,
co-existing artifact resolution methods, but if there are no schema
definitions within my contribution how else would I want to resolve
the import than via the SCA way?  What's to get confused about?

And how do we handle WSDL import?  It says in the Basic Profile that
wsdl import is supposed to have a non-empty @location.   So you can
never use SCA contribution import to resolve a WSDL import?

Scott

Reply via email to