Using xb2Net with Alaska and eXPress



I have an HTTPHandler that receives an XML message and then executives this 
command:



oResponseHTTPS := oHttp:Execute( 
"https://lbs.mvpbanking.com/cgi-bin/efs2/gen_notify.pl" , "POST" , oForm )



In Alsaksa 1.9 331 version and earlier this works like a charm. Now this is 
failing in SL1 355. I get a null in my oResponseHTTPS object.



Boris Borzic Suggested that I Compile with Alaska 1.9.331 + Xb2.NET 3.2.13 
(latest version) and if this works, then there is some issue with Xbase++ 
1.9.355 SL1  and to contact Alaska Software. It did not work so I am 
looking for help from Alaska.



Jeanne Harris

Hi Jeanne,

I would send a sample to support@alaska-software.com.

Regards,
Chris.



"Jeanne Harris" <vjharris@starband.net> wrote in message
news:c574730$4966b39b$d1f@news.alaska-software.com...
> Using xb2Net with Alaska and eXPress
>
>
>
> I have an HTTPHandler that receives an XML message and then executives
this
> command:
>
>
>
> oResponseHTTPS := oHttp:Execute(
> "https://lbs.mvpbanking.com/cgi-bin/efs2/gen_notify.pl" , "POST" , oForm )
>
>
>
> In Alsaksa 1.9 331 version and earlier this works like a charm. Now this
is
> failing in SL1 355. I get a null in my oResponseHTTPS object.
>
>
>
> Boris Borzic Suggested that I Compile with Alaska 1.9.331 + Xb2.NET 3.2.13
> (latest version) and if this works, then there is some issue with Xbase++
> 1.9.355 SL1 - and to contact Alaska Software. It did not work so I am
> looking for help from Alaska.
>
>
>
> Jeanne Harris
>
>

I did put together a test app and sent it to Alaska support for help with 
this problem.

Jeanne

Can someone tell me what might have changed from 331 to 355?

The bit of code looks like this

cXmlString := '<efunds_response action="verify">'+ ;
                     '<payment>'+;
                         '<payment_id>'+cPaymentID+'</payment_id>'+;
                         '<student_number>'+cStudent_number+'</student_number>'+;
                         '<family_id>'+cFamilyID+'</family_id>'+;
                         '<amount>'+cAmount+'</amount>'+;
                         '<payment_type>'+cPaymentType+'</payment_type>'+;
                           '<function_ref_id>'+cRefID+'</function_ref_id>'+;
                           '<payment_code>'+cPaymentCode+'</payment_code>'+;
                           '<payer_last_name>'+cLastName+'</payer_last_name>'+;
                           '<payer_first_name>'+cFirstName+'</payer_first_name>'+;
                           '<timestamp>'+cTime+'</timestamp>'+;
                           '<current_balance>'+cCurrentBalance+'</current_balance>'+;
                         '</payment>'+;
        '</efunds_response>'

oHttp := xbHTTPClient():new()
oForm := xbForm():new()
oForm:SetVar("cmd", cXmlString )
oResponseHTTPS := oHttp:Execute( 
"https://lbs.mvpbanking.com/cgi-bin/efs2/gen_notify.pl" , "POST" , oForm )

On Fri, 26 Jun 2009 10:51:15 -0500, Jeanne Harris wrote:

> Can someone tell me what might have changed from 331 to 355?
> 
> The bit of code looks like this
> 
> cXmlString := '<efunds_response action="verify">'+ ;
>                      '<payment>'+;
>                          '<payment_id>'+cPaymentID+'</payment_id>'+;
>                          '<student_number>'+cStudent_number+'</student_number>'+;
>                          '<family_id>'+cFamilyID+'</family_id>'+;
>                          '<amount>'+cAmount+'</amount>'+;
>                          '<payment_type>'+cPaymentType+'</payment_type>'+;
>                            '<function_ref_id>'+cRefID+'</function_ref_id>'+;
>                            '<payment_code>'+cPaymentCode+'</payment_code>'+;
>                            '<payer_last_name>'+cLastName+'</payer_last_name>'+;
>                            '<payer_first_name>'+cFirstName+'</payer_first_name>'+;
>                            '<timestamp>'+cTime+'</timestamp>'+;
>                            '<current_balance>'+cCurrentBalance+'</current_balance>'+;
>                          '</payment>'+;
>         '</efunds_response>'
> 
> oHttp := xbHTTPClient():new()
> oForm := xbForm():new()
> oForm:SetVar("cmd", cXmlString )
> oResponseHTTPS := oHttp:Execute( 
> "https://lbs.mvpbanking.com/cgi-bin/efs2/gen_notify.pl" , "POST" , oForm )

Can we see the xml as a string rather than a collection of strings and
variables of unknown values.. Maybe its a parsing problem. If you then
browse the xml string, you generate, you will see if it's well formed.

Jeanne,

>In Alsaksa 1.9 331 version and earlier this works like a charm. Now this is 
>failing in SL1 355. I get a null in my oResponseHTTPS object.

>Boris Borzic Suggested that I Compile with Alaska 1.9.331 + Xb2.NET 3.2.13 
>(latest version) and if this works, then there is some issue with Xbase++ 
>1.9.355 SL1 – and to contact Alaska Software. It did not work so I am 
>looking for help from Alaska.

You are confusing me here. First you say it worked with Xbase++ 1.9.331 
but that it failed with Xbase++ 1.9.355, and then you are saying it also 
failed with 1.9.331, when using the latest Xb2Net version (3.2.13).

This would indicate that this is an issue that was introduced with Xb2Net 
version 3.2.13, rather than a problem related to Xbase++ 1.9.355!

Or am I missing something here?

-- Andreas

---                                                                      ---
  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
  415 Gute Street                     or: Andreas@DDPSoftware.com
  Owosso, MI 48867-4410               or: Andreas_Gehrs-Pahl@CrimeCog.com
  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
---                                                                      ---

Sorry about the confusion.. it works with Alaska 331 but not 355

Jeanne

Boris' latest version of xb2net is 3.2.13. When I run his 3.2.13 version 
Alaska 331 it works just as it has been but when I run Alaska 355 it now 
fails.. My code is the same.. no change...

This morning I sent a test app to the Alaska Tech Support.

Jeanne

Are you running a 355 compiled version?

Jim

Jeanne Harris wrote:
> Boris' latest version of xb2net is 3.2.13. When I run his 3.2.13 version 
> Alaska 331 it works just as it has been but when I run Alaska 355 it now 
> fails.. My code is the same.. no change...
> 
> This morning I sent a test app to the Alaska Tech Support.
> 
> Jeanne 
> 
>