| Author |
Message
|
| meena05 |
 Posted: Mon Mar 21, 2016 6:32 am Post subject: WESB WSDL to IIB |
 |
|
Apprentice
Joined: 26 Feb 2016
Posts: 39
|
Hi ,
I am trying to convert WESB services to IIB.
Consumer had a requirement that the WSDL should not change.
How can I use WESB's service WSDL in IIB?
When I tried creating Message Model from existing WSDL. It created Inline schemas. My IIB WSDL did not match the WESB/Consumer WSDL file.
Please guide me. Thank you! |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Mar 21, 2016 6:36 am Post subject: Re: WESB WSDL to IIB |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| meena05 wrote: |
| When I tried creating Message Model from existing WSDL. It created Inline schemas. My IIB WSDL did not match the WESB/Consumer WSDL file. |
What's bad about that? What about the end result doesn't match the consumer's expectations?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| meena05 |
| Posted: Mon Mar 21, 2016 6:43 am Post subject: |
|
|
Apprentice
Joined: 26 Feb 2016
Posts: 39
|
It failed at consumer end.
with error " invalid soap call exception"
Consumer WSDL has two xsd's.
When I took consumer WSDL and created Message Model. My message Model created three xsd's with different inline schema names. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 21, 2016 6:55 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| meena05 wrote: |
It failed at consumer end.
with error " invalid soap call exception" |
And how did you determine that this was the result of a badly constructed WSDL and not (for example) a code or configuration error?
| meena05 wrote: |
Consumer WSDL has two xsd's.
When I took consumer WSDL and created Message Model. My message Model created three xsd's with different inline schema names. |
Again, I ask why that is a problem?
Did you correctly import the XSDs prior to importing the WSDL?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| meena05 |
| Posted: Mon Mar 21, 2016 7:19 am Post subject: |
|
|
Apprentice
Joined: 26 Feb 2016
Posts: 39
|
The new IIB service URL is working for me in SOAP UI
But it is failing for Consumer.
Any Request/response inside the WSDL, IIB Message Model is converting them into Schemas by default. For consumer, WSDL has these objects within the WSDL file.
Except this I do not see any other differences.
Please advise. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Mar 21, 2016 7:23 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Did you request the ESB file and use the wizard to import it?
This should have created your WSDL and a bunch or other artifacts... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 21, 2016 7:39 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| meena05 wrote: |
The new IIB service URL is working for me in SOAP UI
But it is failing for Consumer. |
| meena05 wrote: |
| Please advise. |
Tell the customer whatever code bug they've got at their end might have been tolerated by WESB but it isn't by IIB.
Alternatively you could abandon the use of IIB's SOAP tooling and roll your own through an HTTPInput node. I wouldn't, but it's an option.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| meena05 |
| Posted: Mon Mar 21, 2016 8:44 am Post subject: |
|
|
Apprentice
Joined: 26 Feb 2016
Posts: 39
|
| Thank you for your quick responses. I will work with consumer on this. Will get back if any questions. Thanks again! |
|
| Back to top |
|
|
| timber |
| Posted: Mon Mar 21, 2016 9:34 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Quote: |
| Any Request/response inside the WSDL, IIB Message Model is converting them into Schemas by default. For consumer, WSDL has these objects within the WSDL file. |
Yes, IIB always does that. This does not change the meaning of the WSDL. IIB just prefers to keep the WSDL separate from the XSD.
| Quote: |
The new IIB service URL is working for me in SOAP UI
But it is failing for Consumer. |
How *exactly* is it failing? Can you quote any error messages reported by the customer?
In my opinion, it's too early to talk about how to fix this - we don't even know what the problem is yet. |
|
| Back to top |
|
|
| Gralgrathor |
| Posted: Mon Mar 21, 2016 10:16 pm Post subject: |
|
|
Master
Joined: 23 Jul 2009
Posts: 297
|
| timber wrote: |
| Yes, IIB always does that. |
It does so in an incredibly stupid way, by the way. Especially if you look at IIB9's limitations regarding schema definitions. There are lots of scenario's in which two linked WSDLs partly overlap, and the way IIB splits up WSDLs makes resolving conflicts a *load of work.
_________________
A measure of wheat for a penny, and three measures of barley for a penny; and see thou hurt not the oil and the wine. |
|
| Back to top |
|
|
| timber |
| Posted: Tue Mar 22, 2016 12:34 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Quote: |
| It does so in an incredibly stupid way, by the way. |
To be clear, I'm not here to defend IIB's treatment of WSDLs. But it can be made to work, and I stand by the advice given above.
| Quote: |
| Especially if you look at IIB9's limitations regarding schema definitions. |
You are referring to the fact that
a) One Application cannot contain two definitions of the same XML Schema qualified name, but
b) If you import two WSDLs, and they both define the same QName in their inline xsds then you will always violate rule a)
IIBv10 provides a good workaround; you can put each imported WSDL into its own shared library, and get around the limitation. |
|
| Back to top |
|
|
|
|
