Dear Rick:

Our Payment Portal Provider has changed some things and it has completely stopped working.

The line of code in the program that is that is crashing that is part of the soap program that you provided is
**************************************************
THIS.oWSDLMethod = loSD.GetMethod(lcMethod) - ERROR 1924 LOSD is NOT and Object
**************************************************

After 2 days we got the message from them...

a security update has been implemented for our Web Services users that eliminates the ability to access EPS Web Service endpoints in a browser.

You will need to point the system that you use to create transactions to the WSDLs that are attached.

I have reviewed the code samples that they sent me and the only real difference is the header.

They send

<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="https://ssl.selectpayment.com/PV" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetNamespace="https://ssl.selectpayment.com/PV" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>

I am currently using

<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" >

If I change the code in 'FUNCTION CreateSoapRequestXML'

Will this solve the problem ???

Edward K. Marois
Realty Information Systems

I don't think so. I don't think wwSoap cares about a bigger header with additional namespace defines in it. It's how the namespaces are applied to the XML document that matters. It looks to me that they're adding a bunch of SOAP feature namespaces and if those are used the service is going to break for sure.

IAC, you're kind of on your own with this. wwSoap has been deprecated about 6 years ago and replaced with the more resilient technology in the West Wind Web Service Proxy Generator. Part of the reason for this change was that the SOAP parsing features were offloaded to a system component rather than a Fox component that manually has to configure each little document feature and keep up with various SOAP spec changes and all the insane differences in SOAP behavior for different SOAP server implementations.

The newer tooling automates generation of the proxy and can much more easily keep up with changes simply by regenerating the proxies in a few steps. Anyway something to think about if you need to maintain this service for a long while.

That's not to say wwSoap won't work, but it requires a lot more manual tweaking to get any non-standard features to work with wwSoap. I haven't looked at wwSoap code in years...

+++ Rick ---

Dear Rick:

This is Edward from Realty Information Systems writing again.

I appreciate that you will consult us but will take that under advisement.

I did a lot of work and have the following problem....

FUNCTION AuthorizeTransactionWithCustomer(...... as created by the '.NET Web Service Proxy Generator'

Is displaying the following Error

Method 'TransactionProcessing.TransactionProcessing.AuthorizeTransactionWithCustomer' not found

Thinking I could change

cComClass = "TransactionProcessing.TransactionProcessing"

to

cComClass = "TransactionProcessing"

Did NOT effect the system well

Please Advice