| Author |
Message
|
| Vgowda |
 Posted: Fri Jan 13, 2012 5:11 am Post subject: Error while importing WSDL's or XSD's |
 |
|
Acolyte
Joined: 11 Dec 2007
Posts: 61
Location: Bengaluru
|
Hi,
I am using WMB Toolkit V 6.1.0.3, trying to create MF using Start from WSDL and/or XSD's. In that after importing WSDL's, the required XSD's are converted to MXSD files, but i got few errors in mxsd's as mentioned below.
| Quote: |
| Type restriction error 'http://www.abc.com/abc/1#CustKeys_Type' (content type incompatible with the content type of the baseType): element declaration 'CustId (Identifier_Type)' does not exist in the base type. |
Any  will be appreciated.
_________________
Regards
Vinay |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Jan 13, 2012 5:18 am Post subject: Re: Error while importing WSDL's or XSD's |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Vgowda wrote: |
| Any will be appreciated. |
Apply some maintenance to your Toolkit.
Make sure that the declaration in question is accessable.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jan 13, 2012 5:23 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| sounds like you're missing an import or include. or the path is not correct. |
|
| Back to top |
|
|
| Vgowda |
| Posted: Fri Jan 13, 2012 5:28 am Post subject: |
|
|
Acolyte
Joined: 11 Dec 2007
Posts: 61
Location: Bengaluru
|
right now i am downloading FP 8 for the same. The declaration is accessable, it has created the include for the same.
_________________
Regards
Vinay |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 13, 2012 5:31 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Vgowda wrote: |
| it has created the include for the same. |
What it has created the include?
Never mind if there's an import or an include in the XSD / WSDL, is it accessable as my most worthy associate has intimated?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Jan 13, 2012 6:12 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Check that the paths of any include or import xsd's do actually exist.
If find that it is sometimes easier to put everything in the one directory then I don't have to worry about relative path names being wrong.
They will get mangled when broker imports them anyway (the mangled paths depend upon the namespace) so it really does not matter that much to edit them befire importing them.
_________________
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 |
|
|
| vennela |
| Posted: Fri Jan 13, 2012 6:24 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| the required XSD's are converted to MXSD files |
Maybe the WSDL is still referring to XSDs while toolkit converted them to MXSDs. |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Jan 13, 2012 8:17 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Type restriction error 'http://www.abc.com/abc/1#CustKeys_Type' (content type incompatible with the content type of the baseType): element declaration 'CustId (Identifier_Type)' does not exist in the base type. |
Previous comments see to be assuming that this is a problem with an xs:include or xs:import. I don't think it is.
To properly understand this error, you need to understand what an XML Schema type restriction is, and what the relevant rules are. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jan 13, 2012 8:22 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| kimbert wrote: |
| Quote: |
| Type restriction error 'http://www.abc.com/abc/1#CustKeys_Type' (content type incompatible with the content type of the baseType): element declaration 'CustId (Identifier_Type)' does not exist in the base type. |
Previous comments see to be assuming that this is a problem with an xs:include or xs:import. I don't think it is. |
I was assuming that the WSDL and XSDs being imported were already valid according to the XML Standard, and that any type restriction errors were a result of the import process rather than an inherent flaw. |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Jan 13, 2012 8:27 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
mqjeff: Not an unreasonable assumption, but there seem to be quite a lot of xsds out there that break the rules.
Vgowda: I would need to see the actual type definitions to understand the error properly. |
|
| Back to top |
|
|
| Vgowda |
| Posted: Sun Jan 15, 2012 9:49 pm Post subject: |
|
|
Acolyte
Joined: 11 Dec 2007
Posts: 61
Location: Bengaluru
|
Vitor :Applying FP 8 din't work, its the same error.
kimbert: The XSD's and WSDL's are successfully validated in ALTOVA XML Spy before it is imported into WMB. After Importing the Files into toolkit, all the XSD's are converted into mxsd's and files are placed in the same folder.
All the paths are appropriate and WSDL's are updated to refer MXSD's only.
_________________
Regards
Vinay |
|
| Back to top |
|
|
| Vgowda |
| Posted: Sun Jan 15, 2012 10:45 pm Post subject: |
|
|
Acolyte
Joined: 11 Dec 2007
Posts: 61
Location: Bengaluru
|
I deleted and re-created the complex type using Message Set editor, now i dont have any errors.
Weird but it solved the issue. 
_________________
Regards
Vinay |
|
| Back to top |
|
|
|
|
