|
|
|
[
Permlink
| « Hide
]
Bill Sahlas - [12/03/07 09:46 AM ]
The LCDS server is required in order to get the full error message back to the client. You'd need to setup a 'destination' and useProxy=true. The server code is able to circumvent the player limitation
Adobe's position on this issue is truly disappointing. To require that we license LCDS server, spending tens of thousands of dollars, to correct for a shortcoming of an Adobe product, whether it be Flex or the Flash Player itself, is shocking. The need for accurate error propagation can hardly be described as a feature request. It is a bug, apparently due to a design flaw, and I urge Adobe to keep this issue open for future consideration.
I agree with Tom (and the others that expressed this sentiment in the previously closed ticket http://bugs.adobe.com/jira/browse/SDK-11841). It's especially frustrating to just have this ticket closed again without stated recognition of the position people are taking and why Adobe feels that this position is invalid. Perhaps if people understood why Adobe felt this is not a bug... Heck, I'd even be more satisfied (if very disappointed) if the answer was "yeah it's a bug, but for now we'd like to get some revenue off of LCDS".
Closing as a duplicate. The other bug is now open.
More than a year later, and still nothing from Adobe. Are the bug owners on this one paying attention?!?!?
Just for a little reference, this bug is the reason no one uses Flash or AIR clients for Amazon Web Services, and any number of other major web services: http://docs.amazonwebservices.com/AlexaSiteThumbnail/2006-05-15/SoapErrorResponseArticle.html Hmm... guess we'd better have Amazon return a non-error response code... oh, wait, they are the ones that are standards compliant, and this YEAR OLD BUG is the problem. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||