| Author |
Message
|
| mr_jaber |
 Posted: Wed Nov 23, 2011 9:16 pm Post subject: Error loading WSDL file |
 |
|
Apprentice
Joined: 21 May 2009
Posts: 28
|
Hi,
i got the following error when i tried to create "start from WSDL and/or XSD file". the error shows when i select the .wsdl file which is working fine on other env.
"Error loading WSDL file "XXXXXXX.wsdl". Check the file for validity. The supplied WSDL must declare at least one WSDL binding to be used."
Its MB 7 with patchset 3
Thanks, |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Nov 23, 2011 10:10 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
did you try:-
- Create a message set project
- Import the WSDL plus any XSD's into the project
- New -> Create message definitions from WSDL
I did that on 7.0.0.3 yesterday and it was fine.
I always do it that way. Then I have a copy of the original wsdl/xsd's in the project for reference.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mr_jaber |
| Posted: Wed Nov 23, 2011 10:27 pm Post subject: |
|
|
Apprentice
Joined: 21 May 2009
Posts: 28
|
Yes. i tried that as well but the same error message keeps coming.
But one more input. i have tried another WSDL file that seems to be working.
as far as i know MB 7 supports WSDL 1.1 and 2 !? does the version makes any difference !? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Nov 24, 2011 12:41 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Have you validated the WSDL?
There are number of online WSDL Validators.
If it is valid, AND this issue can be replicated on at least one more machine, then it is time for a PMR.
Does it happen if you try the same operation with 7.0.0.2?
If the Deployable WSDL & Message Set builds on another toolkit then at least you can go forward using that while an PMR is being investigated.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Nov 28, 2011 5:55 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Once you do all the common sense stuff, check with IBM through a PMR. The WSDL parser has several APARs open on it.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Amazer |
| Posted: Wed Apr 04, 2012 3:34 am Post subject: |
|
|
Novice
Joined: 10 Feb 2009
Posts: 24
|
Hi,
What has been the result of raising a PMR for this issue?
I have the same problem as was stated.
Error loading WSDL file "xxxxFile.wsdl". Check the file for validity. The supplied WSDL must declare at least one WSDL binding to be used.
Please, can anyone highlight what is the solution?
I am using version 6.1.0.3.
Thanks.
Amazer
 |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Apr 04, 2012 4:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Amazer wrote: |
| What has been the result of raising a PMR for this issue? |
Nothing that will help you.
| Amazer wrote: |
| I am using version 6.1.0.3. |
This (rather old) thread is talking about WMBv7 and fixes for that. You don't even have all the fixes for WMBv6.1 (you're 7 levels of maintenance behind).
Apply those & see if it helps.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Amazer |
| Posted: Wed Apr 04, 2012 9:49 pm Post subject: |
|
|
Novice
Joined: 10 Feb 2009
Posts: 24
|
Thanks for your advice, Vitor.
However, what is puzzling is the sample WSDL file works, but the other WSDL file does not. Any clues that can help?
-Amazer |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 05, 2012 4:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Amazer wrote: |
| However, what is puzzling is the sample WSDL file works, but the other WSDL file does not. Any clues that can help? |
The sample file is a sample. It doesn't contain all the possibly complexitiies, subtle codings and other issues live WSDLs do. Obviously.
I'm not saying it's not a problem with the product. I'm saying it's a problem that might well have been fixed in maintenance you don't have.
And will be fixed by a fix that won't come from any PMR raised on this thread because that will be for the v7 tooling.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gilberthg |
| Posted: Mon Apr 16, 2012 7:48 am Post subject: I had the same problem in WMB8 |
|
|
Novice
Joined: 01 Feb 2012
Posts: 14
Location: Costa Rica
|
Hi all,
Maybe I can save time to people with the same problem.
Recently I had the same problem in WMB8 , and the message
"WSDL must declare at least one WSD"
has nothing to do with it.
The WSDL I was working with, have a malformation in the definitions tag.
It is :
xmlns:tns="http://http://ws.sdde.bccr.fi.cr/"
The problem is that the WSDL file comes from a goverment institution,
and is used in many applications, and they for some reason they did not have problem with it . I know most of this applications are .NET .
Well, when we receive the WSDL, we need to do some changes to it, so we thought it was something we changed, but not, the problem is from the original file they proviede. You don't expect the problem to be there...
So, I think this error may appear for any malformations in the definitions section of the wsdl, so first you can review it , I did that comparing with another WSDL that was working good in the Wizard.
Hope this helps,
Kind regards |
|
| Back to top |
|
|
| trbryant |
| Posted: Fri May 02, 2014 8:14 pm Post subject: Is the file extension upper case? |
|
|
Newbie
Joined: 24 Jun 2001
Posts: 6
Location: Timm R Bryant
|
| There's a known defect where this error is reported if the file extension is not all lower case. An APAR has been opened, but since this is a defect in the RAD portion of the Message Broker Toolkit don't expect it to be patched quickly. |
|
| Back to top |
|
|
| ganesh |
| Posted: Sun May 04, 2014 1:37 pm Post subject: Re: Is the file extension upper case? |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
| trbryant wrote: |
| There's a known defect where this error is reported if the file extension is not all lower case. An APAR has been opened, but since this is a defect in the RAD portion of the Message Broker Toolkit don't expect it to be patched quickly. |
That's correct, MB toolkit expects the file extension to be in lowercase and also we have noticed toolkit having issues when the wsdl file name is too long. |
|
| Back to top |
|
|
|
|
