You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by Stefan Henke <st...@gmx.de> on 2001/10/22 17:57:53 UTC
Import WSDL in WSDE
Hi,
I´m using IBM WSTK and WSDE to test developoing webservices. I tried to invoke some services found on www.xmethods.com.
I downloaded the appropriate WSDL file and tried to create a proxy class in WSDE. But for every file I tried, I got error messages.
Most often I got the message: "Cannot convert java.lang.Object to null".
For the WSDL files I created with WSDE for local testing work fine.
Do you have any experience with WSDE and WSDL files created for e.g. .NET?
Maybe WSDE uses an older version of Apache SOAP or WSDL4J?
Thanks
Stefan
Re: Import WSDL in WSDE
Posted by Stefan Henke <st...@gmx.de>.
Hi,
thanks for the response. This seems to be the problem.
Does anybody know if it is possible to "update" the plugins of WSDE with
newer versions of the libs?
Because the "buggy" version of the WSDE is useless if you need real
interoperability, isn´t it?
Stefan
----- Original Message -----
From: "Tony Hong" <th...@xmethods.net>
To: <so...@xml.apache.org>; "Pavlovic Petar" <pp...@ptt.yu>
Sent: Monday, October 22, 2001 10:03 PM
Subject: RE: Import WSDL in WSDE
> Hi all,
>
> Before WSTK 2.4, IBM's toolkits generated and consumed WSDL that did not
> namespace qualify the references to WSDL elements.
>
> For example:
> (incorrect)
> <binding name="eBayWatcherBinding" type="eBayWatcherPortType">
>
> vs
>
> (correct)
> <binding name="eBayWatcherBinding" type="tns:eBayWatcherPortType">
>
> where tns is the namespace for the wsdl doc. If the toolkit encountered
> qualification, it errored.
>
> This is actually a bug, and it led to WSDL interop problems between IBM
> toolkits and most non-IBM toolkits.
>
> For the services actually *owned* by XMethods, I did indeed publish an
"IBM"
> version of the WSDL in addition to the "regular" version, to get around
this
> problem.
>
> This is fixed in WSTK 2.4, though, so hopefully I will be able to take
those
> "alternative" links down soon.
>
> cheers,
> Tony
>
> > -----Original Message-----
> > From: Pavlovic Petar [mailto:ppavlovic@ptt.yu]
> > Sent: Monday, October 22, 2001 12:43 PM
> > To: Stefan Henke
> > Subject: Re: Import WSDL in WSDE
> >
> >
> > Sender: Stefan <st...@gmx.de>,
> > Time: Monday, October 22, 2001, 5:57:53 PM
> >
> > I had similar problems with IBM WSTK. I've never tried any in
> > WSDE.
> > The only example that passed with no problem was
> > EBayWatcherService from XMethods.net.
> > The problem is in WSDL version that differ in case of IBM
> > WSTK. EBayWatcherService has two different WSDL definitions. Try it.
> >
> > Has anybody tried WSIF (Web Services Invocation Framework)
> > from IBM?
> >
> > SH> I´m using IBM WSTK and WSDE to test developoing webservices. I
> > SH> tried to invoke some services found on www.xmethods.com.
> >
> > SH> I downloaded the appropriate WSDL file and tried to create a proxy
> > SH> class in WSDE. But for every file I tried, I got error messages.
> > SH> Most often I got the message: "Cannot convert
> > java.lang.Object to null".
> >
> > SH> For the WSDL files I created with WSDE for local testing work fine.
> >
> > SH> Do you have any experience with WSDE and WSDL files created
> > for e.g. .NET?
> > SH> Maybe WSDE uses an older version of Apache SOAP or WSDL4J?
> >
> >
> > --
> > pozdrav...
> > coyote
> > When you're making hammers, everything looks like a nail
>
Re: Import WSDL in WSDE
Posted by Stefan Henke <st...@gmx.de>.
Hi,
thanks for the response. This seems to be the problem.
Does anybody know if it is possible to "update" the plugins of WSDE with
newer versions of the libs?
Because the "buggy" version of the WSDE is useless if you need real
interoperability, isn´t it?
Stefan
----- Original Message -----
From: "Tony Hong" <th...@xmethods.net>
To: <so...@xml.apache.org>; "Pavlovic Petar" <pp...@ptt.yu>
Sent: Monday, October 22, 2001 10:03 PM
Subject: RE: Import WSDL in WSDE
> Hi all,
>
> Before WSTK 2.4, IBM's toolkits generated and consumed WSDL that did not
> namespace qualify the references to WSDL elements.
>
> For example:
> (incorrect)
> <binding name="eBayWatcherBinding" type="eBayWatcherPortType">
>
> vs
>
> (correct)
> <binding name="eBayWatcherBinding" type="tns:eBayWatcherPortType">
>
> where tns is the namespace for the wsdl doc. If the toolkit encountered
> qualification, it errored.
>
> This is actually a bug, and it led to WSDL interop problems between IBM
> toolkits and most non-IBM toolkits.
>
> For the services actually *owned* by XMethods, I did indeed publish an
"IBM"
> version of the WSDL in addition to the "regular" version, to get around
this
> problem.
>
> This is fixed in WSTK 2.4, though, so hopefully I will be able to take
those
> "alternative" links down soon.
>
> cheers,
> Tony
>
> > -----Original Message-----
> > From: Pavlovic Petar [mailto:ppavlovic@ptt.yu]
> > Sent: Monday, October 22, 2001 12:43 PM
> > To: Stefan Henke
> > Subject: Re: Import WSDL in WSDE
> >
> >
> > Sender: Stefan <st...@gmx.de>,
> > Time: Monday, October 22, 2001, 5:57:53 PM
> >
> > I had similar problems with IBM WSTK. I've never tried any in
> > WSDE.
> > The only example that passed with no problem was
> > EBayWatcherService from XMethods.net.
> > The problem is in WSDL version that differ in case of IBM
> > WSTK. EBayWatcherService has two different WSDL definitions. Try it.
> >
> > Has anybody tried WSIF (Web Services Invocation Framework)
> > from IBM?
> >
> > SH> I´m using IBM WSTK and WSDE to test developoing webservices. I
> > SH> tried to invoke some services found on www.xmethods.com.
> >
> > SH> I downloaded the appropriate WSDL file and tried to create a proxy
> > SH> class in WSDE. But for every file I tried, I got error messages.
> > SH> Most often I got the message: "Cannot convert
> > java.lang.Object to null".
> >
> > SH> For the WSDL files I created with WSDE for local testing work fine.
> >
> > SH> Do you have any experience with WSDE and WSDL files created
> > for e.g. .NET?
> > SH> Maybe WSDE uses an older version of Apache SOAP or WSDL4J?
> >
> >
> > --
> > pozdrav...
> > coyote
> > When you're making hammers, everything looks like a nail
>
RE: Import WSDL in WSDE
Posted by Tony Hong <th...@xmethods.net>.
Hi all,
Before WSTK 2.4, IBM's toolkits generated and consumed WSDL that did not
namespace qualify the references to WSDL elements.
For example:
(incorrect)
<binding name="eBayWatcherBinding" type="eBayWatcherPortType">
vs
(correct)
<binding name="eBayWatcherBinding" type="tns:eBayWatcherPortType">
where tns is the namespace for the wsdl doc. If the toolkit encountered
qualification, it errored.
This is actually a bug, and it led to WSDL interop problems between IBM
toolkits and most non-IBM toolkits.
For the services actually *owned* by XMethods, I did indeed publish an "IBM"
version of the WSDL in addition to the "regular" version, to get around this
problem.
This is fixed in WSTK 2.4, though, so hopefully I will be able to take those
"alternative" links down soon.
cheers,
Tony
> -----Original Message-----
> From: Pavlovic Petar [mailto:ppavlovic@ptt.yu]
> Sent: Monday, October 22, 2001 12:43 PM
> To: Stefan Henke
> Subject: Re: Import WSDL in WSDE
>
>
> Sender: Stefan <st...@gmx.de>,
> Time: Monday, October 22, 2001, 5:57:53 PM
>
> I had similar problems with IBM WSTK. I've never tried any in
> WSDE.
> The only example that passed with no problem was
> EBayWatcherService from XMethods.net.
> The problem is in WSDL version that differ in case of IBM
> WSTK. EBayWatcherService has two different WSDL definitions. Try it.
>
> Has anybody tried WSIF (Web Services Invocation Framework)
> from IBM?
>
> SH> I´m using IBM WSTK and WSDE to test developoing webservices. I
> SH> tried to invoke some services found on www.xmethods.com.
>
> SH> I downloaded the appropriate WSDL file and tried to create a proxy
> SH> class in WSDE. But for every file I tried, I got error messages.
> SH> Most often I got the message: "Cannot convert
> java.lang.Object to null".
>
> SH> For the WSDL files I created with WSDE for local testing work fine.
>
> SH> Do you have any experience with WSDE and WSDL files created
> for e.g. .NET?
> SH> Maybe WSDE uses an older version of Apache SOAP or WSDL4J?
>
>
> --
> pozdrav...
> coyote
> When you're making hammers, everything looks like a nail
RE: Import WSDL in WSDE
Posted by Tony Hong <th...@xmethods.net>.
Hi all,
Before WSTK 2.4, IBM's toolkits generated and consumed WSDL that did not
namespace qualify the references to WSDL elements.
For example:
(incorrect)
<binding name="eBayWatcherBinding" type="eBayWatcherPortType">
vs
(correct)
<binding name="eBayWatcherBinding" type="tns:eBayWatcherPortType">
where tns is the namespace for the wsdl doc. If the toolkit encountered
qualification, it errored.
This is actually a bug, and it led to WSDL interop problems between IBM
toolkits and most non-IBM toolkits.
For the services actually *owned* by XMethods, I did indeed publish an "IBM"
version of the WSDL in addition to the "regular" version, to get around this
problem.
This is fixed in WSTK 2.4, though, so hopefully I will be able to take those
"alternative" links down soon.
cheers,
Tony
> -----Original Message-----
> From: Pavlovic Petar [mailto:ppavlovic@ptt.yu]
> Sent: Monday, October 22, 2001 12:43 PM
> To: Stefan Henke
> Subject: Re: Import WSDL in WSDE
>
>
> Sender: Stefan <st...@gmx.de>,
> Time: Monday, October 22, 2001, 5:57:53 PM
>
> I had similar problems with IBM WSTK. I've never tried any in
> WSDE.
> The only example that passed with no problem was
> EBayWatcherService from XMethods.net.
> The problem is in WSDL version that differ in case of IBM
> WSTK. EBayWatcherService has two different WSDL definitions. Try it.
>
> Has anybody tried WSIF (Web Services Invocation Framework)
> from IBM?
>
> SH> I´m using IBM WSTK and WSDE to test developoing webservices. I
> SH> tried to invoke some services found on www.xmethods.com.
>
> SH> I downloaded the appropriate WSDL file and tried to create a proxy
> SH> class in WSDE. But for every file I tried, I got error messages.
> SH> Most often I got the message: "Cannot convert
> java.lang.Object to null".
>
> SH> For the WSDL files I created with WSDE for local testing work fine.
>
> SH> Do you have any experience with WSDE and WSDL files created
> for e.g. .NET?
> SH> Maybe WSDE uses an older version of Apache SOAP or WSDL4J?
>
>
> --
> pozdrav...
> coyote
> When you're making hammers, everything looks like a nail
Re: Import WSDL in WSDE
Posted by Pavlovic Petar <pp...@ptt.yu>.
Sender: Stefan <st...@gmx.de>,
Time: Monday, October 22, 2001, 5:57:53 PM
I had similar problems with IBM WSTK. I've never tried any in
WSDE.
The only example that passed with no problem was
EBayWatcherService from XMethods.net.
The problem is in WSDL version that differ in case of IBM
WSTK. EBayWatcherService has two different WSDL definitions. Try it.
Has anybody tried WSIF (Web Services Invocation Framework)
from IBM?
SH> I´m using IBM WSTK and WSDE to test developoing webservices. I
SH> tried to invoke some services found on www.xmethods.com.
SH> I downloaded the appropriate WSDL file and tried to create a proxy
SH> class in WSDE. But for every file I tried, I got error messages.
SH> Most often I got the message: "Cannot convert java.lang.Object to null".
SH> For the WSDL files I created with WSDE for local testing work fine.
SH> Do you have any experience with WSDE and WSDL files created for e.g. .NET?
SH> Maybe WSDE uses an older version of Apache SOAP or WSDL4J?
--
pozdrav...
coyote
When you're making hammers, everything looks like a nail
Re: Import WSDL in WSDE
Posted by Pavlovic Petar <pp...@ptt.yu>.
Sender: Stefan <st...@gmx.de>,
Time: Monday, October 22, 2001, 5:57:53 PM
I had similar problems with IBM WSTK. I've never tried any in
WSDE.
The only example that passed with no problem was
EBayWatcherService from XMethods.net.
The problem is in WSDL version that differ in case of IBM
WSTK. EBayWatcherService has two different WSDL definitions. Try it.
Has anybody tried WSIF (Web Services Invocation Framework)
from IBM?
SH> I´m using IBM WSTK and WSDE to test developoing webservices. I
SH> tried to invoke some services found on www.xmethods.com.
SH> I downloaded the appropriate WSDL file and tried to create a proxy
SH> class in WSDE. But for every file I tried, I got error messages.
SH> Most often I got the message: "Cannot convert java.lang.Object to null".
SH> For the WSDL files I created with WSDE for local testing work fine.
SH> Do you have any experience with WSDE and WSDL files created for e.g. .NET?
SH> Maybe WSDE uses an older version of Apache SOAP or WSDL4J?
--
pozdrav...
coyote
When you're making hammers, everything looks like a nail