Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (1)

Resolved Problem with Werservice

  1. Issue
0
Votes
Undo
  1. Oscar Rios
    Oscar Rios
  2. PowerBuilder
  3. Wednesday, 29 November 2017 19:35 PM UTC
Hi
 
I'm try to call to webservice using .Net Engine but in the metod it does not resolve in the same way what i do not using .Net Engine.
 
Return the same method but with differents variables
 
With .Net Engine 
 
• migra.migragetcarnetext( /*string numdocumento*/, /*string tipodocumento*/, /*ref string nombres*/, /*ref string primerapellido*/, /*ref string segundoapellido*/, /*ref string numrespuesta */)
 
Without  .Net Engine 
 
• migra.migragetcarnetext( /*string numdocumento*/, /*string tipodocumento*/, /*ref string calidadmigratoria*/, /*ref string nombres*/, /*ref string primerapellido*/, /*ref string segundoapellido */)
 
in the first option that responds well, in the second option it  responds "can not connect"
 
My powerBuilder version is 12
  1. Service
How to deploy at PowerServer 2017 using Powerbuild...
.NET
Accepted Answer
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 29 November 2017 20:56 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Oscar;

   FYI: The .NET Web Service engine contains the more recent web service support & WSDL parsing code. The So I am not surprised that you are not seeing the correct proxy & methods being generated with the old SOAP feature (without the .NET engine). Looks like you are OK though with the .NET engine and I would recommend that you always use this feature for your web service access in PB 12.x.

Regards ... Chris

Comment
Oscar Rios
  1. Oscar Rios
  2. Thursday, 30 November 2017 20:50 PM UTC
Hi Chris



You're right, the strange thing is that with the .NET engine I return the same function but different parameters than in the SOAP. Thanks for your support.

  1. Helpful
There are no comments made yet.
Responses (1)


There are replies in this question but you are not allowed to view the replies from this question.