| Author |
Message
|
| nelson |
 Posted: Wed Jun 17, 2015 7:50 am Post subject: Unable to register operation |
 |
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
Hi All,
I updated a WSDL (added new operations) using the message model wizard -> I already has a WSDL for my data... It asked me to replace some files, so these files were replaced.
When I try to deploy a new flow that invokes this WS with one of these new operations, get this error:
| Code: |
BIP3736E: Unable to register the selected operation MyOperation. The operation was not found in the WSDL.
The selected operation MyOperation could not be found in the WSDL.
Determine the cause of the error and correct it. |
I'm pretty sure that the operation is there. Additionally, the Web Service Usage wizard generated the WS subflow with no problems.
If I try to use an operation that previously existed I get no errors...
Any idea? Cleaned the workspace, but no luck...
Thanks a lot. |
|
| Back to top |
|
 |
| ganesh |
| Posted: Wed Jun 17, 2015 11:50 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
Make sure you added the operation in the binding.
You can also check if the wsdl is valid or not using tools or you could try and import the wsdl into soap ui and see if the operations are getting listed.
I would rather create a wsdl with new operations and use it to create a new message model or message set project and use it. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 17, 2015 12:04 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
To get a good deployable wsdl I usually use 2 libraries.
1) library for development of the xsds and wsdl
2) library importing the wsdl (using wizard) and containing the deployable wsdl and xsds...
Of course only the second library is included in any application...
Hope this helps 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| nelson |
| Posted: Wed Jun 17, 2015 12:13 pm Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
I imported the WSDL in another application and deployed with no problem 
| fjb_saper wrote: |
To get a good deployable wsdl I usually use 2 libraries.
1) library for development of the xsds and wsdl
2) library importing the wsdl (using wizard) and containing the deployable wsdl and xsds...
Of course only the second library is included in any application...
Hope this helps |
Yes... I usually work this way... |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 17, 2015 12:21 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Make sure you regenerate (replace) the bindings in your wsdl after changing the wsdl and before importing it into your deployable lib.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| nelson |
| Posted: Wed Jun 17, 2015 12:38 pm Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| fjb_saper wrote: |
| Make sure you regenerate (replace) the bindings in your wsdl after changing the wsdl and before importing it into your deployable lib. |
I'm pretty sure the WSDL (and its XSD's) is updated, since I was able to drag the WSDL and generate the subflow to invoke the new operations... |
|
| Back to top |
|
|
| nelson |
| Posted: Thu Jun 18, 2015 6:30 am Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| After restarting the integration server the issue was solved... weird. |
|
| Back to top |
|
|
|
|
