1. Rahul Kumar Shaw
  2. PowerBuilder
  3. Wednesday, 27 December 2017

Hi,

 

I was getting "The SoapClient doesn't support .NET proxy" error in the migrated application(migrated from PB12.5 to PB2017). I removed the pbsoapclient.pbd and then the error is gone. My question is do we really need pbsoapclient.pbd?

 

Regards,

Rahul

Bruce Armstrong Accepted Answer Pending Moderation
0
Votes
Undo

You need either pbsoapclientXXX.pbd or pbwsclientXXX.pbl, but not both.  It depends how you generated your proxy.  If you used the EasySoap engine, then use pbsoapclient.  If you used the .Net engine, then use pbwsclient.  The error you are getting is from generating the proxy using the .Net engine and then trying to use the pbsoapclient.

The PBD have the same classes in them, so only one gets use (the first found in the library list) if you add both. 

Comment
There are no comments made yet.
  1. Thursday, 28 December 2017
  2. PowerBuilder
  3. # 1
Roland Smith Accepted Answer Pending Moderation
0
Votes
Undo

PBD files are version specific so use pbsoapclient170.pbd. For your particular issue, it does appear that it might only work with a .Net based call.

Comment
There are no comments made yet.
  1. Thursday, 28 December 2017
  2. PowerBuilder
  3. # 2
Marco Meoni Accepted Answer Pending Moderation
0
Votes
Undo

Hello Rahul,

pbsoapclient is required by web services that use EasySoap to build proxies.

For web services that use .Net, you instead include pbwsclient to build proxies based on the .Net implementation of the SoapConnection object. This supports both the EasySoap proxies and .Net proxies.

There is no particular reason for keeping a proxy using the EasySoap engine, it is an old implementation.

Cheers,

Marco

Comment
There are no comments made yet.
  1. Thursday, 28 December 2017
  2. PowerBuilder
  3. # 3
  • Page :
  • 1


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