OK, I'm not as familiar with POST, but it looks like the filter controls
the urlToUse and the message body.
Of course, I could be wrong...
-Alex
On 7/12/17, 6:36 AM, "Jeffry Houser" wrote:
> Not doing a get, doing a post, FWIW.
>
>
>On 7/11/2017 5:05 PM, Alex Harui wrote:
>> I don't know this
Not doing a get, doing a post, FWIW.
On 7/11/2017 5:05 PM, Alex Harui wrote:
I don't know this code at all, so I could be missing something, but I saw
this in AbstractOperation's sendBody:
if (filter != null)
{
// TODO: does this need to run on the array version of the
p
I gave up on HTTPService long ago. It’s nice how simple it is to use, but it’s
sooo limiting.
I use URLLoader for just about everything. I wrapped it in my own classes that
do everything I need including tracking status, parsing responses and error
responses, progress, dispatching custom events
I don't know this code at all, so I could be missing something, but I saw
this in AbstractOperation's sendBody:
if (filter != null)
{
// TODO: does this need to run on the array version of the
parameters
ctype = filter.getRequestContentType(this, parameters, ctype);
I looked into a Serialization Filter too. Explicitly, the
serializeParameters() function. Unfortunately, it returns a generic
object and is called before the parameters are processed in the
sendBody() function; meaning it had no affect.
On 7/11/2017 2:13 PM, Alex Harui wrote:
Ah yes. I
Ah yes. It looks like the parameters might become the body. It appears
there is a class called a SerializationFilter that might help you
translate the parameters to the right parts of the request.
From AbstractOperation:
if (filter != null)
{
// TODO: does this need to run o
On 7/11/2017 12:32 PM, Alex Harui wrote:
But interestingly, the code also looks like you can give
HTTPService.send() the request string instead of an object of name/value
pairs and it will use the string.
The code does look like that, and it was the first thing I tried. The
string does not get
Hi Alex,
Interesting, that has potential.
The potential problem is that the mx.rpc.httpAbstractOperation would
need an extension or rework, because it seems to copy my given
parameters into a paramsToSend object. I never could find the code
where paremsToSend is added to the outgoing reque
I think I see paramsToSend get added in sendBody in
frameworks/projects/rpc/src/mx/rpc/http/AbstractOperation.as
I think I see it "serialize" the object into a string. If OrderedObject
doesn't work, you can write your own Proxy subclass and control the order.
But interestingly, the code also lo
Hi Jeffry,
Good you got something to work. I just had a thought that maybe you could
pass in an mx.utils.OrderedObject as the parameters and still use
HTTPService.
-Alex
On 7/11/17, 6:44 AM, "Jeffry Houser" wrote:
>Thanks Kyle and Javier for their thoughts.
>
>I was eventually able to do this
e, but functional and resolves this as
> possible error cause when dealing with the vendor who built this API.
>
> Updated Stack Overflow Post: https://stackoverflow.com/ques
> tions/44924870/can-i-control-the-parameter-order-in-an-httpservice-post
>
> My blog post on the issue: http
easy as using HTTPService, but functional and resolves this as
possible error cause when dealing with the vendor who built this API.
Updated Stack Overflow Post:
https://stackoverflow.com/questions/44924870/can-i-control-the-parameter-order-in-an-httpservice-post
My blog post on the issue:
Sorry, one very important typo in my example. This line should include the
string in quotes so it's not interpreted as an object that will then be
processed like you are seeing and you lose the order:
> httpService.send({ \"otherParameters\": \"Other Random Misc Data\",
> \"lastParameter\": \"L
Hey Jeffry:
I may be missing something in my understanding of your problem, but are you
trying to send a body of parameters in the request payload? If so, I suggest
you adopt a JSON or plain text approach, and build your params into the
body/payload in the order you want by just building the st
Hi Jeffrey!
My 4 cents :)
1. Maybe defining the inside the declaration
(and just binding the contents) helps somewhat. Maybe not, but at least
it's prettier :)
http://help.adobe.com/en_US/Flex/4.0/AccessingData/WS2db454920e96a9e51e63e3d11c0bf69084-7fdc.html
2. Stupid one: try method="POST" (up
When iterating over properties in ActionScript there is no guarantee of the
order unfortunately. I can't think of a front-end solution that would solve
this problem. I believe the only solution would be on the server's side.
Kyle
Kyle McKnight
Senior UI Engineer - Accesso
602.515.1444 (M)
On Tu
Hi Everyone,
I'm updating a Point of Sale system that was built with Flex and AIR
using the Cairngorm framework.
The code integrates with a custom server provided by my client's
payment processor vendor. Part of their requirement is that parameters
be form posted to their server in a spe
17 matches
Mail list logo
