That is the way I made it work also.. And I ran WS-I testing tool - it was ok - my WSDL passed test assertions ...
-----Original Message----- From: Wagh, Shrikant [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 6:08 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Regarding importing XML Schema files... Jim, I had that issue of WSI compliance and importing schemas. The way I did is as follows: <types> <schema targetNamespace="http://wstesting.com/eProfileService"; xmlns="http://www.w3.org/2001/XMLSchema";> <import namespace="http://wstesting.com/CreateProfile"; schemaLocation="http://localhost:8070/CreateProfile.xsd"/> <import namespace="http://wstesting.com/UpdateProfile"; schemaLocation="http://localhost:8070/UpdateProfile.xsd"/> This does work and works well with axis too. I tried this with axis 1.1 final release. Best regards, 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: 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] > > >
