Blog

Category Filtering: 'Flash-Remoting'

Remove Filter


Flash Player 8 Mac OS Gateway bug using Flash Remoting and CFMX 7

Posted by Luis Majano
16 Feb 2006 12:00 AM
This is a recorded bug that is solved by the CFMX7 cumulative hot fix 2. However, the bug is still active only on MAC OS X standalone flash player or projector.

Thanks to Dave Stanten at Adobe, for sending me the technote and resolving this issue: Tech Note

ColdFusion MX 7 Gateway Connection URL

If you are using Flash Remoting to access ColdFusion code, you may run into an issue where ColdFusion constructs an invalid URL when appending a jsessionid. If this occurs, the web server that is accessing your code could throw errors. The solution is to simply add a question mark (?) to the end of the gateway URL. Change /flashservices/gateway to /flashservices/gateway?. This ensures that the URL is created correctly.

I only had this problem with flash player 8 and 7 for the MAC, but standalone only. If I used the flash player plugin within a browser I was ok or if I used any form of the flash player on Windows.

Also, the tricky part is that the Coldfusion logs report the following, which is due to the malformed URL's:

[Flash Remoting MX]->Request received was not Flash-based (not of the binary AMF protocol)

So lookout for this tricky bug if you come upon it. A single character can make a difference. :)

Happy Remoting!!!

NetDebugger and CF Flash Forms

Posted by Luis Majano
02 Sep 2005 12:00 AM
This entry is to enlighten those who need to enable the Flash Remoting NetDebugger using CF Flash Forms. By default, coldfusion has the flex debuggin off, so you either have to tweak the flex settings or programmatically activate the debugging.

I would not recommend the first solution on a production environment, due to the nature of somebody peaking in to your requests and responses. However, for development is fine. So to start, find the following file: flex-config.xml which can be found under the following directory:

{CF_ROOT}/WEB-INF/cfform/flex-config.xml

Open the xml file and locate the following section:

<!-- When production-mode=true, the debugging options are always

false and may not be set. -->

<debugging>


<!-- allow override of values in debugging section via

query parameter on a per-request basis, if applicable -->

<process-debug-query-params>true</process-debug-query-params>
......

</debugging>

This is the flex debuggin configuration. So in order to activate the debugger change the following entries to true.

<!-- turn on debug to see the request and response on the server side as well

as debug information in client side tracing -->

<remote-objects-debug>false</remote-objects-debug>


<!-- turn on debug to see the request and response on the server side as well

as debug information in client side tracing -->

<web-service-proxy-debug>false</web-service-proxy-debug>


<!-- turn on debug to see the request and response on the server side -->

<http-service-proxy-debug>false</http-service-proxy-debug>

Site Updates

Entries Search