Bill Winspur wrote:
>> I think your approach below is fairly sound. My wish would have >> been to leverage the URL generator, because if you except the >> posting part, of course, the result of a GET or a POST could be >> handled exactly the same way.
> just to confirm I understand, I assume you are suggesting I use URL > generator as the basis for anything I develop to interact with a > gateway ?
I am just saying that "it would be best if"... In the longer term, I see a solution based on the URL generator as being the best.
>> Right now in the URL generator we make a distinction between the >> "oxf:" protocol and all the other ones.
> What do you mean by 'distinct' in the case of oxf:?
There is an "architecture" to handle things slighlty differently if we know we are using the oxf: protocol vs. the other protocols. So my point was that we could pretty easily handle http: separately to use, for example, Apache commons-httpclient as opposed to Java's builtin HTTP client if needed.
>> If we would like to use something like the Apache commons-httpclient, >> we could easily plug this in as well.
> Who are 'we' ? Are you offering to make changes to the URL generator > ? Hope, hope.
"We" is whoever does the job ;-) I would like to but right now I have other things on my plate, so I must limit myself to thinking about this rather than making the changes, unless those are really quick.
> For my current requirement, the show stopper with the URL generator > as documented, is that you can't specify a document to be posted to > the URL during the request part of the transaction. One solution > would be to allow an optional > > <input name="post" ref="payment-req.xml"/> > > element within the URL generator.
We could try to harmonize this with what is currently done with the Email processor. The Email processor builds MIME messages. With the latest changes checked in, it is able to handle attachments as well. When posting documents with HTTP, you may just post an XML file or a text file, but you may post MIME messages as well. The bottom line is that how this is done now with the Email processor is that you can refer to extra processor inputs to access payloads. We could use a similar mechanism here, for example in the URL generator config, we could say something like:
<body src="oxf:my-input-with-payload"/>
-Erik
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ orbeon-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/orbeon-user
