RE: Regarding importing XML Schema files...

[Wagh, Shrikant]

Hi Tony,   WSI BP does allow import of one WSDL into another WSDL, But schema cannot be imported in <definition>, it has to be in <schema>. WS-I does not care if your imported schema imports other schema in turn. Here are the IMPORT assertions specified in WS-I BP specs.   R2001 A DESCRIPTION MUST only use the WSDL "import" statement to import another WSDL description. R2002 To import XML Schema Definitions, a DESCRIPTION MUST use the XML Schema "import" statement. R2003 A DESCRIPTION MUST use the XML Schema "import" statement only within the xsd:schema element of the types section. R2004 A DESCRIPTION MUST NOT use the XML Schema "import" statement to import a Schema from any document whose root element is not "schema" from the namespace "http://www.w3.org/2001/XMLSchema". R2009 An XML Schema directly or indirectly imported by a DESCRIPTION MAY include the Unicode Byte Order Mark (BOM). R2010 An XML Schema directly or indirectly imported by a DESCRIPTION MUST use either UTF-8 or UTF-16 encoding. R2011 An XML Schema directly or indirectly imported by a DESCRIPTION MUST use version 1.0 of the eXtensible Markup Language W3C Recommendation. Thanks,   Shrikant Wagh QA Lead, HPP/Eprofile, HP   For those who are interested in Web Services testing: ----------------------------------------------------- I found that WebServiceTester from Optimyz software is a very good tool for testing any types of web services, and I'm great fan of this tool. It supports all types of web services, and all simple and complex types and it very usable than any other tool in the market I ever used/evaluated. It automatically generates the SOAP requests and invokes the intended web services. It can perform functional, regression and load testing of web services. Result analysis and status reporting is just wonderful.  I'll highly recommend this tool for testing web services, saves lots of time and efforts in testing web services. For more information visit http://www.optimyz.com.   DISCLAIMER ================================================================ THESE ARE MY PERSONAL VIEWS/OPINIONS AND DOES NOT REPRESENT HP, AND THE INFORMATION PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE I/HP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS INFORMATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. =================================================================       -----Original Message----- From: Tony Opatha [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 3:09 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Regarding importing XML Schema files...   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!