RE: Problem for .wsdl that imports .xsd

"Leng, Jialing" <[email protected]>
Newsgroups gmane.comp.apache.webservices.wsif.user
Message-ID <CF27D8AAF8C6D41187D400306E00604F0A39CB35@ukhil712nts.hld.uk.fid-intl.com>
Paolo,
 
The web services we are using haven't been published in WSDL and it is end
to end connection and communication via SOPA over HTTP at the moment. We are
only a client and have no control over server side at all. The WSDL I am
using is someone's volunteered work. The thing which I can't understand is
that AXIS' WSDL2Java tool can recognise both my WSDL and XSD and generate
the Java class files correctly (I suppose WSDL2Java would validate both) but
WSIF doesn't. 
 
BTW, those simple types are defined in my XSD file but after the definition
of the complex types and I suppose the order is not significant ?
 
Thanks
Jialing

-----Original Message-----
From: Fiore Paolo [mailto:[email protected]] 
Sent: 14 July 2005 09:26
To: [email protected]
Subject: R: Problem for .wsdl that imports .xsd


Jialing,
 
when you try to deploy a web-service, the WSDL will be validate. That means
that all xsd data types must be imported.
The attached file test.xsd is a correct schema file built starting from your
schema file. I re-writed semplyfing it. This file is OK. As you can see I
added information missing. These info missing are writed as "simple type".
In your schema file, for example you refere to type "OperIdType" that
doesn't exist. So or you define in schema file this type of data, or you
refere it importing these type form another schema file.
 
Paolo
 
 
 

-----Messaggio originale-----
Da: Leng, Jialing [mailto:[email protected]]
Inviato: mercoledì 13 luglio 2005 18.19
A: '[email protected]'
Oggetto: RE: Problem for .wsdl that imports .xsd


Paolo,
 
Yes, I didn't include the whole schema file but only included the piece
which is relevant in my early mail.
 
As for the point 2 below, do you mean I must add an import section in the
XSD file to include the location of WSDL so the WSDL can be validated? I
have tried the following in the XSD file :
 
<xsd:import namespace="urn:schemas-xtrac-fmr-com:b2b"
schemaLocation="../schemas/XtracB2BServiceSchema.xsd" /> 

or

<import namespace="urn:schemas-xtrac-fmr-com:b2b"
schemaLocation="../wsdls/XtracB2B.wsdl" />

but none of them works, could you please give more ideas? I am new to
WSDL/XSD/WebService so your help is very much appreciated.

Thanks

Jialing

 

-----Original Message-----
From: Fiore Paolo [mailto:[email protected]] 
Sent: 13 July 2005 15:39
To: [email protected]
Subject: R: Problem for .wsdl that imports .xsd


Jialing,
 
there are two error.
1)
At end of schema file there isn't  tag </xsd:schema>. But I suppose that you
have forgotten to write it in this e-mail.
 
2)
You must add in the your schema file a section with <import
namesapce="urn:schemas-xtrac-fmr-com:b2b" schemaLocation="....."> to
validate your WSDL. The error message say you that into WSDL isn't possible
resolve the namespace referenced in schema file and defined by the following
piece of code:
xmlns:xt="urn:schemas-xtrac-fmr-com:b2b" 

Regards

Paolo


 -----Messaggio originale-----
Da: Leng, Jialing [mailto:[email protected]]
Inviato: mercoledì 13 luglio 2005 16.20
A: '[email protected]'
Oggetto: RE: Problem for .wsdl that imports .xsd



Thanks Fiore.
 
I used the following:
 
<types xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"

xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<xsd:schema>

<xsd:import namespace="urn:schemas-xtrac-fmr-com:b2b"

schemaLocation="../schemas/XtracB2BServiceSchema.xsd" />

</xsd:schema>

</types>

But it complains

Error   INVALID_WSDL: XSD element {urn:schemas-xtrac-fmr-com:b2b}Login
cannot be resolved XtracLogin.wsdl IPManager/src/wsifclients/wsdls line 1.

and in XSD file, "Login" is as follows:

<?xml version="1.0" encoding="UTF-8"?>

<xsd:schema xmlns:xt="urn:schemas-xtrac-fmr-com:b2b"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:schemas-xtrac-fmr-com:b2b"
elementFormDefault="qualified" attributeFormDefault="unqualified">

<!-- Xtrac Session Cookie data type -->

<xsd:element name="Cookie" type="xsd:string"/>

 

<!-- ***************************************************** -->

<!-- Login -->

<!-- ***************************************************** -->

<!-- Request -->

<xsd:element name="Login" type="xt:LoginType"/>

<xsd:complexType name="LoginType">

<xsd:sequence>

<xsd:element name="OperId" type="xt:OperIdType"/>

<xsd:element name="Password" type="xt:PasswordType"/>

<xsd:element name="GetSecurityFunctions" type="xt:YesNoType" minOccurs="0"/>

<xsd:element name="GetBitmaskSecurityFunctions" type="xt:YesNoType"
minOccurs="0"/>

<xsd:element name="GetOperatorProfileInfo" type="xt:YesNoType"
minOccurs="0"/>

<xsd:element name="GetSourceSystemInfo" type="xt:YesNoType" minOccurs="0"/>

</xsd:sequence>

</xsd:complexType>

 

Any idea why ?


Thanks

Jialing


 

-----Original Message-----
From: Fiore Paolo [mailto:[email protected]] 
Sent: 13 July 2005 14:47
To: [email protected]
Subject: R: Problem for .wsdl that imports .xsd


Leng,
 
try with:
 
<import namespace="urn:schemas-xtrac-fmr-com:b2b"
schemaLocation="../schemas/XtracB2BServiceSchema.xsd" /> 

-----Messaggio originale-----
Da: Leng, Jialing [mailto:[email protected]]
Inviato: mercoledì 13 luglio 2005 15.41
A: '[email protected]'
Oggetto: Problem for .wsdl that imports .xsd




Hi, I am new to this forum/WSIF and hopefully someone can point me into the
direction ... 

I am trying to use WSIF to access the web services and the WSDL file
describing the web services includes an "import" tag section which should
import the specified XSD file which defines the data types used for the web
services. WSDL2Java does generates the classes fine. But somehow my WSIF
application cannot seem to pick up the data types there. I am using wsif 2.0
downloaded from Apache web site. The import line is like :

<import namespace="urn:schemas-xtrac-fmr-com:b2b"
location="../schemas/XtracB2BServiceSchema.xsd" /> 

Can anyone help me on this ? 

Thanks 
Jialing
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.