IMO, if the wsdlLocation/schemaLocation fails to resolve the artifacts, we
should not try to use the SCA way.
Thanks,
Raymond
--------------------------------------------------
From: "Luciano Resende" <[email protected]>
Sent: Wednesday, March 18, 2009 4:34 PM
To: <[email protected]>
Subject: Re: [DISCUSS] Use of Existing (non-SCA) Mechanisms for Resolving
Artifacts
On Wed, Mar 18, 2009 at 4:05 PM, Raymond Feng <[email protected]> wrote:
Hi,
I don't think there is a conflict in the spec. Even though the SCA
resolution mechanism is preferred, we have to honor the non-SCA way first
if
the users choose to use to use wsdlLocation or schemaLocation.
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. And I'm just wondering
what the side effects of using SCA resolution might be when they are
not expected (e.g out of a sudden, wsdl and schemas from imported
contributions start to be used).
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
