I don't see any requirement in WS-I BP 1.0a that specifies that imported XSDs
can not import additional XSDs. However, it is reasonable to allow WSDL
to import other .wsdl's.
BTW, I believe .NET 1.1 Framework/VS.NET 2003 WSDL processor
does not resolve multiple imported XSDs, hence you have to have
a WSDL importing another WSDL which contains type definition
pertaining to your original XSD schemas. Major limitation on .NET
which may hinder how you publish your public interfaces and
schema components using AXIS....
-----Original Message-----
From: Jim Murphy [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 22, 2004 12:17 PM
To: [EMAIL PROTECTED]
Subject: Re: Regarding importing XML Schema files...
Unfortunately the WS-I doesn't like that very much. :) The WS-I BP 1.0
says WSDL imports can only import other WSDL documents. You can put a
dummy wsdl:type/xsd:schema section that imports these directly.
Though I'm not sure what axis will do in either case.
Jim
Heitzeg, Bill wrote:
> This is how I've done it. It works fine with Axis:
>
> <?xml version="1.0" encoding="UTF-8" ?>
> *-*
> <http://localhost:8080/BillWebService_axis/services/BillWebService?wsdl#>
> <definitions targetNamespace="*https://webservices.sabre.com/websvc*"
> xmlns="*http://schemas.xmlsoap.org/wsdl/*"
> xmlns:bill="*http://webservices.sabre.com/BillWebService*"
> xmlns:eb="*http://www.ebxml.org/namespaces/messageHeader*"
> xmlns:soap="*http://schemas.xmlsoap.org/wsdl/soap/*"
> xmlns:tns="*https://webservices.sabre.com/websvc*"
> xmlns:wsse="*http://schemas.xmlsoap.org/ws/2002/12/secext*"
> xmlns:xs="*http://www.w3.org/2001/XMLSchema*">
> * * <import
> location="*http://localhost:8080/BillWebService_axis/Bill.xsd*"
> namespace="*http://webservices.sabre.com/BillWebService*" />
> * * <import
> location="*http://localhost:8080/BillWebService_axis/msg-header-2_0.xsd*"
> namespace="*http://www.ebxml.org/namespaces/messageHeader*" />
> * * <import
> location="*http://localhost:8080/BillWebService_axis/xmldsig-core-schema.xsd*"
> namespace="*http://www.w3.org/2000/09/xmldsig#*" />
> * * <import
> location="*http://localhost:8080/BillWebService_axis/xlink.xsd*"
> namespace="*http://www.w3.org/1999/xlink*" />
> * * <import
> location="*http://localhost:8080/BillWebService_axis/envelope.xsd*"
> namespace="*http://schemas.xmlsoap.org/soap/envelope/*" />
> * * <import
> location="*http://localhost:8080/BillWebService_axis/xml.xsd*"
> namespace="*http://www.w3.org/XML/1998/namespace*" />
> * * <import
> location="*http://localhost:8080/BillWebService_axis/wsse.xsd*"
> namespace="*http://schemas.xmlsoap.org/ws/2002/12/secext*" />
>
> -----Original Message-----
> *From:* Marepalli, Somesh [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, January 22, 2004 1:59 PM
> *To:* [EMAIL PROTECTED]
> *Subject:* Regarding importing XML Schema files...
>
> Hi:
>
> In my WSDL - I need to import a .xsd file which needs to import
> another .xsd file
>
> What is the correct way (per WS-I) checks to make Axis import
> these files?
>
> Any e.g.s. would be most appreciated
>
>
>
> regards
>
> **Somesh Marepalli**
>
> Software Engineer, CleverPath Analytics Dev
>
> tel: +1 216 643-9214
>
> [EMAIL PROTECTED]
>
>
>
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
