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

Resolved Web Service Proxy Wizard (Obsolete)

  1. How-to
0
Votes
Undo
  1. Samuel Sanchez Avila
    Samuel Sanchez Avila
  2. PowerBuilder
  3. Friday, 19 March 2021 22:49 PM UTC

Hello.

 

We have a Web Service Proxy project running out in 2017, but now in 2019 r3 that object is obsolete. I just have a few question...

 

Why is Obsolete?

Is there other object for the replacement of this object?

Our project is going to stop working if we migrate it to 2019r3?

We need to re-work it with snap develop c#?

Why, if its obsolete, i can stil creating that object, until when it will stop working?

 

thanks u for reading this...

Spin Editmask Issue
dot net wrapper
Accepted Answer
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Saturday, 20 March 2021 00:48 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi Samuel,

Obsolete means the feature is still in the product but it is not being enhanced anymore and is not eligible for technical support.  We keep it in the product for backwards compatibility reasons until customers have time to migrate off the obsolete feature.  So no, your project will not stop working simply by upgrading to PowerBuilder 2019 R3.

It is obsolete because we have new Web service clients to replace it that are more secure, easier to deploy, more flexible, and arguably just overall much better.

HTTPClient - this is an all-purpose HTTP client that can be used to basically do anything.  You can use it to call SOAP Web services, but it will require some extra coding compared to the obsolete Web service proxy wizard.  Please refer to this tech article.

RESTClient - this is a specialized HTTP client for calling REST Web APIs that return JSON result set.  It requires very little coding, and can even automatically import/export JSON data from the REST Web API to a DataWindow.

Regardless the Web service proxy wizard is obsolete or not, I would immediately migrate off of that as it is not secure since it doesn't support TLS 1.2.  The HTTPClient and RESTClient support TLS 1.2, and TLS 1.3 coming soon.  Plus, it supports token technology such as OAuth 2.0 and JWT.

Best regards,
Armeen

Comment
There are no comments made yet.
Responses (2)
Nabeel Aslam
Nabeel Aslam Accepted Answer Pending Moderation
  1. Monday, 11 April 2022 09:44 AM UTC
  2. PowerBuilder
  3. # 1

Hi Everyone,

We are migrating from PB 12.5.2 build 5629 to Appeon 2021. After code migration, we are trying to consume WCF Service using HTTPClient because the existing SOAP Connection approach is obsolete now but we are getting response error of 400 bad request. Can anyone help us to resolve this issue. Source code has been place below for you reference.

 

Suggest the change that need to be incorporate 

httpClient lo_client
integer li_ret , i , li_StatusCode
String lo_xml_request
string ls_url,ls_return,ls_soap_action
string ls_data
string ls_body
string ls_ret

lo_client = Create httpClient
ls_url="http://cms7017:49161/WKFLoginManager.svc?wsdl"
ls_soap_action ="http://tempuri.org/ILoginManager/LoginUser"
lo_client.SetRequestHeader("soapAction", ls_soap_action)
lo_client.SetRequestHeader("Content-Type", "application/soap+xml; charset=utf-8")
ls_body="username=ib2&password=a1!&moduleid=cms&clientmachine=cms&request_dte=2022-11-04 10:13:00.193"
lo_client.sendrequest("POST",ls_url,ls_body)
li_StatusCode = lo_client.GetResponseStatusCode()
ls_ret = lo_client.GetResponseStatusText( )
li_ret = lo_client.getresponsebody(ls_data)
destroy lo_client

 

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 11 April 2022 14:44 PM UTC
Please post this as separate question.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


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