Re: How to programmatically send a form (Dev WO)

[James M. Terry]

Xavier, I wrote a similar app a couple years ago for PayFlowLink using WORedirect: public WOComponent sendToVerisign() { WORedirect nextPage; nextPage = new WORedirect(context()); nextPage.setUrl (yourTargetUrlAsString());  <-- use your banks method here return nextPage; } I created a component that extended WOComponent, which contained a WOActiveImage linked to the above method.  I placed mine on a 'verify order' page, and it worked great. The return side of the transaction poses a bigger problem if you are running multiple instances of your app.  If your bank makes a return-post to a directAction, WO will probably create a new session for your user.  To deal with this, I passed the session and instance number to verisign, which in turn is part of their return post.  The return-post directAction I provided was to a separate app, that parsed the return-post and redirected the user to the original instance & session much in the same way as the above method. If you are running a single instance, then it is a simple DA. Hope that helps, Jim :) In fact I "just" need to generate a "signed" form then the submit   button should do a couple thing on my side, and send my user to the   bank server. Then, depending on the transaction, the bank will call a direct   action on my side to activate a sort of recipe. So basically I don't really need to "wait" for something, I send the   form to the bank then if something happens (a call to my direct   action), then I'll update the order to either true or false. So actually I'm pretty "stop" about how to write a method that would   provide "send my form using http and display the bank site", but   maybe just having a url in the action field of the form would lead to   this behavior and linking an action to the submit button to do the   stuff I need on my side (like saving the order). Would it work to have both something for the action of the form and   an action bind to the submit button? In this case, I'm not sure I could handle the following case: bug on my side, but the user get send to the bank account anyway. In fact after thinking about it, I'm pretty sure I shouldn't provide   the form inside the page, but only generate the post action when the   submit button is clicked...I'm not sure I'm clear;) Usually your provider will give you instructions specific to   sending a user to their credit card page where the user fills in   the details and processes the payment. They do (more below) For example if you go to this page on this site and right-click on   the actual form and open in a new window, you will see that the   form is really a page on the credit card provider's site shown   inside a html frame on the originating site. http://www.loacademy.com/OrderProduct.asp (not my site ... I don't   do asp dev!) I cannot use frame, we've got important concerned about   accessibility, and frame are just... horrible;) But I don't need to handle the bank part, only send my user there   using a "post" form, and eventually answer to a call to a direct action. Did your bank provider provide you with a development kit/manual? Yes they do provide me with a Java kit containing the method that   would generate the form as a string....but I don't know what to do   with this string:(

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to archive@mail-archive.com