1. Enrique Perez
  2. PowerBuilder
  3. Monday, 20 August 2018

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

Attachments (1)
Enrique Perez Accepted Answer Pending Moderation
0
Votes
Undo

Hi Chris,

Thanks very much for your response.

I do not understand why trying SOAP proxy I am getting 'There is no service in the WSDL file' , for the .NET proxy I found somebody saying the problem is web service is expecting namespace = http://www.gisis.sgicanada.ca/for input parameters but I am sending "". Is that possible?

from the command line I run 

wsdl "http://egi-jbuat.egi.ca:8080/GISInternalInsuranceScore/services/GISInsuranceScoreServiceSOAP?wsdl" and I got .cs file . I am assuming that file is used to create the the assembly dll. Is there any way I can send you that .cs file so you can have a look at it?

Regards

Enrique

 

 

Comment
There are no comments made yet.
  1. Tuesday, 21 August 2018
  2. PowerBuilder
  3. # 1
Chris Pollach Accepted Answer Pending Moderation
0
Votes
Undo

Hi Enrique;

  As long as the Web Service is expecting input parameters as standard datatypes, this should still work well. Also, the web service needs to be returning standard data types in a simple 2D result set (ie: rows, columns). Non-Standard data types, embedded arrays of data, etc will cause the EasySoap and .Net based SOAP processing to fail.

  FYI: standard (primative) data types

  We can ascertain more if you post your old & new WSDL here.

Regards .. Chris

Comment
Hi András;

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

  1. Chris Pollach
  2. Thursday, 30 August 2018
Hi 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
  1. András Balázs
  2. Friday, 31 August 2018
PB 2018 will only be using C# in the middle tier as a Web Service itself or as a .Net Assembly. The C# code will be based on the .Net Core technology. The Web Service feature will be JSON only.

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.
  1. Chris Pollach
  2. Saturday, 1 September 2018
There are no comments made yet.
  1. Monday, 20 August 2018
  2. PowerBuilder
  3. # 2
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.