RE: WSDL Problem

2001-10-08 Thread James Pasley


Keith,

This is an XML namespace issue. The targetNamespace attribute at the
start of the file defines the namespace that all the definitions you define
in your WSDL file will be in. Whenever you reference any of these
definitions
you must use the correct namespace prefix, in your case the tns prefix.

So to be fully correct, you should fix the references to the messages and
portTypes as well as the bindings.

You shouldn't add the prefix before the operation name as the WSDL spec
states that this is a non-qualified name.

I've attached a fixed version of your file with the namespace prefixes
added in all the right placed. 

If you would more details on the kinds of errors to avoid when writing WSDL
check out this link:
http://www.capescience.com/library/articles/common-wsdl-errors.html

Regards,

James



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 05, 2001 5:24 PM
To: [EMAIL PROTECTED]
Subject: WSDL Problem




Hi

I have created a java class which has one method square taking a double and
returning a double.  I have deployed this class to SOAP.
I have genereated WSDL via IBM wstk tool. I am using WSIF to try and
dynamically
read the WSDL and invoke the method,  but I cant seem to call it without
making
some changes to the WSDL that was generated.

If I add tns: to port binding i.e. port binding = tns:MathXBinding, and
also before operation name, I find I can call the service.
Problem is I can't seem to get the IBM tool to generate my WSDL with tns:
in
front of these definitions.

I have included the original WSDL file, perhaps some WSDL heads can have a
look
and suggest something.


(See attached file: MathX.wsdl)

Thanks,

Keith


 
 
 
Diese Nachricht ist vertraulich. Sie ist ausschliesslich fuer
den im Adressfeld ausgewiesenen Adressaten bestimmt.
Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten
wir um eine kurze Nachricht. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Da wir nicht die
Echtheit oder Vollstaendigkeit der in dieser Nachricht
enthaltenen Informationen garantieren koennen, schliessen wir
die rechtliche Verbindlichkeit der vorstehenden Erklaerungen
und Aeusserungen aus. Wir verweisen in diesem Zusammenhang
auch auf die  fuer die Bank geltenden Regelungen ueber die
Verbindlichkeit von Willenserklaerungen mit verpflichtendem
Inhalt, die in den bankueblichen Unterschriftenverzeichnissen
bekannt gemacht werden.

This message is confidential and may be privileged. It is
intended solely for the named  addressee. If you are not the
intended recipient please inform us. Any unauthorised
dissemination, distribution or copying hereof is prohibited.
As we cannot guarantee the  genuineness or completeness of
the information contained in this message, the statements
set forth above are not legally binding. In connection
therewith, we also refer to the governing regulations of
WestLB concerning signatory authority published in the
standard bank signature lists with regard to the legally
binding effect of statements made with the intent to
obligate WestLB.
 




MathX.wsdl
Description: Binary data


RE: WSDL Problem

2001-10-05 Thread Neil Smyth

I've had the same problem when using the wsdl4j toolkit. If you step through
the Definition returned from the wsdl4j toolkit, you'll find that it doesn't
find the referenced binding node - because it is looking in a different
namespace. I've found this problem with a good subset of the wsdl files from
xmethods.

Given that you are generating the wsdl from another tool in the wstk, I'd
classify it as a bug with the generating tool. I'm also not sure about what
the correct syntax as per the wsdl spec is, anyone have any pointers on
that? Should the binding reference always be namespace qualified or not?

If you can find an easy way around this please let me know! I've resorted to
doing basic xml tree searching for the time being which is far from ideal :)

Regards, 

Neil

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 05 October 2001 17:24
To: [EMAIL PROTECTED]
Subject: WSDL Problem




Hi

I have created a java class which has one method square taking a double and
returning a double.  I have deployed this class to SOAP.
I have genereated WSDL via IBM wstk tool. I am using WSIF to try and
dynamically
read the WSDL and invoke the method,  but I cant seem to call it without
making
some changes to the WSDL that was generated.

If I add tns: to port binding i.e. port binding = tns:MathXBinding, and
also before operation name, I find I can call the service.
Problem is I can't seem to get the IBM tool to generate my WSDL with tns:
in
front of these definitions.

I have included the original WSDL file, perhaps some WSDL heads can have a
look
and suggest something.


(See attached file: MathX.wsdl)

Thanks,

Keith


 
 
 
Diese Nachricht ist vertraulich. Sie ist ausschliesslich fuer
den im Adressfeld ausgewiesenen Adressaten bestimmt.
Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten
wir um eine kurze Nachricht. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Da wir nicht die
Echtheit oder Vollstaendigkeit der in dieser Nachricht
enthaltenen Informationen garantieren koennen, schliessen wir
die rechtliche Verbindlichkeit der vorstehenden Erklaerungen
und Aeusserungen aus. Wir verweisen in diesem Zusammenhang
auch auf die  fuer die Bank geltenden Regelungen ueber die
Verbindlichkeit von Willenserklaerungen mit verpflichtendem
Inhalt, die in den bankueblichen Unterschriftenverzeichnissen
bekannt gemacht werden.

This message is confidential and may be privileged. It is
intended solely for the named  addressee. If you are not the
intended recipient please inform us. Any unauthorised
dissemination, distribution or copying hereof is prohibited.
As we cannot guarantee the  genuineness or completeness of
the information contained in this message, the statements
set forth above are not legally binding. In connection
therewith, we also refer to the governing regulations of
WestLB concerning signatory authority published in the
standard bank signature lists with regard to the legally
binding effect of statements made with the intent to
obligate WestLB.