|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Unable to set the port type in SOAP Input node |
« View previous topic :: View next topic » |
Author |
Message
|
kaushik.godugunur |
Posted: Mon Mar 04, 2013 8:43 am Post subject: Unable to set the port type in SOAP Input node |
|
|
Newbie
Joined: 27 Feb 2013 Posts: 9
|
Hi,
Im using a SOAP input node in my flow. Im dragging and dropping the deployable WSDL on the node and the WSDL filename property is populated and the Port type, Imported binding and the service port are populated as a list. When i select the port type in the drop down box, the type is selected but as soon as click on the flow canvas outside the node, the property seems to get unpopulated on its own despite saving it.
Im using 7.0.0 toolkit.
Is it something im doing wrong here or a bug in the version?
Thanks in advance!!
Kaushik |
|
Back to top |
|
 |
nukalas2010 |
Posted: Mon Mar 04, 2013 10:28 pm Post subject: |
|
|
 Master
Joined: 04 Oct 2010 Posts: 220 Location: Somewhere in the World....
|
Are you sure your WSDL contains the POrtType..
Share the WSDL.. |
|
Back to top |
|
 |
kaushik.godugunur |
Posted: Mon Mar 04, 2013 11:01 pm Post subject: |
|
|
Newbie
Joined: 27 Feb 2013 Posts: 9
|
Hi nukalas,
Thank you for the response!!
The WSDL is too long as it contains around 120 operations and im not sure how to attach it here. But then it does contain " <wsdl:portType name="ICustomerValidation">" and the value is also populated in the PortType property of the SOAP Input Node. Im able to select the same and save the flow. But after the project is built, there is an error that the PortType must be specified and when i check the node, the values is still available in the dropdown but is de-selected.
Thanks |
|
Back to top |
|
 |
stevarg |
Posted: Tue Mar 05, 2013 6:55 am Post subject: |
|
|
Novice
Joined: 20 Nov 2012 Posts: 24
|
You can try validating the WSDL before using it..
does your binding have a 'style' attribute which specifies the WSDL being 'document' or 'rpc'.
I had issues with one the WSDLs which didnt have a 'style' attribute and I was not able to configure the SOAPInput node using that WSDL.  |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|