Hi Ed, I've never heard of this problem before. All
requests that come from RemoteObject should be of the AMF protocol of course...
and there should be no problem with creating a request of that size, as
I've create ones much larger for testing. Can you try fiddling with the
name of the method, the names of the parameters, and the number of
parameters? There's probably some quirk hidden there.
-Brian
__._,_.___Hello all,
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of edeustace
Sent: Friday, August 18, 2006 9:53 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Flex 1.5 AMF Error:... (not of the binary AMF protocol)
I've been making some modifications to a flex 1.5 application, that was last modified in January of this year and was in good working order. the application is now a subset of a larger web application ( using wicket,spring,hibernate).
On returning to it some remote object requests are causing the following error:
Error: Request received was not Flash-based (not of the binary AMF protocol)
it was hard to tie it down, but i have uncovered on situation where it happens consistently.
i have a function [as]:
addFolder( itemId : Number, name : String, description : String )
which calls the remoteObject function [java]:
addFolder(long itemId, String name, String description )
the error gets triggered if, when calling this function, the combined number of charact! ers in 'name' and 'description' is greater than 25.
i have tried wrapping the arguments into a strict array, but it makes no difference.
i've also tried it with different browsers and flash player 7 and flash player 9.
i've been using a http sniffer to inspect the request and it all seems fine.
the only thing i can think of is that there is some sort of cap on the byte size of requests.
this may be an application wide problem, although there is one successful request whose byte size (876) is larger than the smallest failed request (786), but this request is a bundle of two service calls. Otherwise all successful request have a byte size of less than 780 and all failed requests have a byte size greater than 786.
so i was wondering if anyone has come across this behaviour before?
is it possible that changes to the webapp have affected the functioning of this remote object service, even though all java code relating to flex remains unc! hanged?
is there any other area i should be looking at?!
it wouldn't take much for me to extract these service calls from the flex app and to run them through a popup, but it'd be really good to know why this is occurring.
any help/advice greatly appreciated,
yours,
ed eustace
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
| Software development tool | Software development | Software development services |
| Home design software | Software development company |
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
__,_._,___
