ant elder wrote:
So we can have the Java runtime support the same, could you describe how
this automatic loading works for things like duplicate namespaces and
relative imports?
Thanks,
...ant
On 9/13/06, Andrew Borley (JIRA) <[email protected]> wrote:
[
http://issues.apache.org/jira/browse/TUSCANY-91?page=comments#action_12434446]
Andrew Borley commented on TUSCANY-91:
--------------------------------------
We now automatically load all .wsdl and .xsd files we can find in a
package tree - so no requirement for <import.wsdl>. Can this be closed?
> Replace Tuscany-model.config with <import.wsdl>
> -----------------------------------------------
>
> Key: TUSCANY-91
> URL: http://issues.apache.org/jira/browse/TUSCANY-91
> Project: Tuscany
> Issue Type: New Feature
> Components: C++ SCA
> Affects Versions: Cpp-current
> Reporter: Pete Robbins
> Priority: Minor
> Fix For: Cpp-current
>
>
> Sync with Java SCA method of defining wsdls
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Ant,
It's pretty simple:
- We scan the directory containing your composite and its
sub-directories and register the WSDLs and XSDs we find.
- Tuscany.config is still supported for now if you have special
requirements to load WSDL/XSD files from outside your composite
directory, or not load some of them for example. If nobody finds a good
use for it in the next few months then I hope to be able to remove
that support altogether.
- If you want to load WSDLs and XSDs from outside (e.g. a URL on the
Web) you just need to <import> or <include> it in a local WSDL or XSD.
- Schemas and WSDL definitions sharing a namespace get merged. We may
need to improve the merge logic later to avoid including the same WSDL
or XSD definition multiple times, but I've not yet seen any good use
case requiring this.
- Imports and includes are handled as per the WSDL and XSD specifcations.
- A relative import location is resolved relative to the importing file.
There are probably corner cases and some bugs in the code, but this
summarizes the current design. Hopes this helps...
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
