Comments on: Finding cover art with Flex and Amazon WebServices

By: Sintara

Sintara — Fri, 06 Feb 2009 13:05:26 +0000

Thanks for making this available!

By: 2pha

2pha — Sat, 19 Jan 2008 03:23:20 +0000

ahhh. I changed the aws:Namespace to awsNS:Namespace

because there is also a aws:HTTPservice

Everythings working now :)

Thanks alot for sharing you code

By: Theo

Theo — Fri, 18 Jan 2008 15:52:52 +0000

Hmm, when I look at the namespace it strikes me that Amazon regularly updates the namespace URI with a new date. Check the return data from ECS and see what the current namespace is, that might be the problem you’re having.

By: Theo

Theo — Fri, 18 Jan 2008 15:51:56 +0000

Could it be some kind of namespace problem? I haven't used the code since I wrote this article, so I'm not sure, but try to replace

default xml namespace = aws;

with

use namespace aws;

That might work better. Or do this:

result.aws::Items.aws::Item.aws::SmallImage.aws::URL

"aws" is the namespace which Amazon ECS uses, declared as

namespace aws = "http://webservices.amazon.com/AWSECommerceService/2005-10-05";

By: 2pha

2pha — Fri, 18 Jan 2008 15:42:11 +0000

I am having the same problem as above I think.

the problem is with:

var imageUrlNodes : XMLList = (result.Items.Item.SmallImage.URL);

tracing the xml before it is fine, it outputs the xml returned from amazon. But the items are not populating the XMLList for some reason.

By: Mike

Mike — Fri, 20 Jul 2007 06:35:15 +0000

Hey, Thanks for your reply.

I worked out my problem with Webservices. My problem was that in Flex builder 3 (beta, I might add) you can't just go AWS.ItemSearch.send(mySearchObject). (*Note - you can in FB2)

You have to go AWS.ItemSearch.arguments = mySearchObject; AWS.ItemSearch.send();

FB3 does actually deserialize the result quite well when the resultFormat is "object".

I am now experimenting with the resultFormat "e4x" but I am having problems getting data out of the returned XMLList.

All the examples I have looked at say to use: var myXML:XMLList = event.result..Item;

BUT this doesn't work. The data is there but the variable myXML becomes a null object, and no matter whether you are using HTTPService or WebService the e4x result is the same.

I tried piecing together your code above. I couldn't get everything to compile because the Dictionary component is missing... but I tried your line ( var args : XMLList = event.result.OperationRequest.Arguments;) on the HTTPService result and that didn't work either.

Is there something I'm missing?

I've got the webservice part to work fine. I just can't seem to successfully parse the "e4x" results in flex.

By: Theo

Theo — Mon, 16 Jul 2007 07:17:21 +0000

Can’t remember now, but it might have been the same error that made me give it up an use the REST interface instead. There is one part of the request that is supposed to be a “complex type”, probably one of those keys must be present in that for it to work, but since Flex doesn’t serialize the complex type right the key isn’t there.

By: Mike

Mike — Mon, 16 Jul 2007 02:50:44 +0000

I also have had an issue trying to communicate with AWS using soap.

It does seem to connect ok.. but I keep getting an error back saying that my ItemSearch request needs to define at least one of these parameters: AWSAccessKeyId, SubscriptionId... but I have!

By: Theo

Theo — Tue, 03 Jul 2007 09:35:04 +0000

Sorry, I never pursued the matter further. Amazon’s REST interface was much easier to work with.

By: Maz

Maz — Mon, 02 Jul 2007 11:35:43 +0000

Seems that Flex2 (even Moxie) do not handle too complex ComplexTypes... (particularly WSDL types with attributes in addition to elements)

If you work out anything, tell me :)

maz.spam_AT_gmail_DOT_com (replace words between underscores)