Hi,
I have the following situation.
My company app is using a JBOSS web service for a while; proxy was generated in a previous old PB version and it is currently working under PB 12.5 classic without any glitch.
This service is receiving two parameters from PB without any problem but we need to modify the webservice to receive 3 more parameters from PB and here is where my problem begins.
Trying to generate the new proxy (Web Service proxy wizard) using SOAP engine and I am getting 'There is no service in the WSDL file' however if I try .NET engine PB shows the webservice and it allows me to generate the proxy; I can make a connection but then when I try to invoke the web service I am getting
Cannot invoke Web service... Unmarshalling Error: unexpected element (uri:"", local:"NameNumber"). Expected elements are <{http://www.gisis.sgicanada.ca/}NameNumber>,<{http://www.gisis.sgicanada.ca/}ConsentIndicator>
Has somebody faced the same situation?
Please, any help will be appreciated.
Thanks
Enrique
The key is that PB only handles Standard (aka "simple") data types in web service interactions. The same for return values from a web service.
Regards ... Chris
Thanks for your bad news :-). Will the coming introduction of C# in PB change this situation or we have to settle in manipulating SOAP XMLs?
Regards
András
The new RESTful feature added in PB 2017R3 is based on JSON and not XML. So that would not help you either.
You should be able use the new HTTP Client for this that was introduced in PB2017R2 but, you would still be on your own to parse out the XML - say via PB's PBDOM feature.