<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Luis F. Majano &#187; Flash Remoting</title>
	<atom:link href="http://luismajano.com/category/Flash-Remoting/feed/" rel="self" type="application/rss+xml" />
	<link>http://luismajano.com</link>
	<description>Computer Engineer</description>
	<lastBuildDate>Mon, 05 Mar 2012 17:41:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Flash Player 8 Mac OS Gateway bug using Flash Remoting and CFMX 7</title>
		<link>http://luismajano.com/2006/02/16/Flash-Player-8-Mac-OS-Gateway-bug-using-Flash-Remoting-and-CFMX-7/</link>
		<comments>http://luismajano.com/2006/02/16/Flash-Player-8-Mac-OS-Gateway-bug-using-Flash-Remoting-and-CFMX-7/#comments</comments>
		<pubDate>Thu, 16 Feb 2006 00:00:00 +0000</pubDate>
		<dc:creator>Luis Majano</dc:creator>
				<category><![CDATA[ColdFusion]]></category>
		<category><![CDATA[Flash Remoting]]></category>

		<guid isPermaLink="false">http://www.luismajano.com/</guid>
		<description><![CDATA[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 [...]]]></description>
			<content:encoded><![CDATA[<p>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.</p>
<p>Thanks to Dave Stanten at Adobe, for sending me the technote and resolving this issue: <a href="http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=e514dd93">Tech Note</a></p>
<blockquote><p>
<strong>ColdFusion MX 7 Gateway Connection URL</strong></p>
<p>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.
</p></blockquote>
<p>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.</p>
<p>Also, the tricky part is that the Coldfusion logs report the following, which is due to the malformed URL&#8217;s:</p>
<blockquote><p>
[Flash Remoting MX]->Request received was not Flash-based (not of the binary AMF protocol)
</p></blockquote>
<p>So lookout for this tricky bug if you come upon it. A single character can make a difference. <img src='http://luismajano.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Happy Remoting!!!</p>
]]></content:encoded>
			<wfw:commentRss>http://luismajano.com/2006/02/16/Flash-Player-8-Mac-OS-Gateway-bug-using-Flash-Remoting-and-CFMX-7/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>NetDebugger and CF Flash Forms</title>
		<link>http://luismajano.com/2005/09/02/netdebuggercfflashforms/</link>
		<comments>http://luismajano.com/2005/09/02/netdebuggercfflashforms/#comments</comments>
		<pubDate>Fri, 02 Sep 2005 00:00:00 +0000</pubDate>
		<dc:creator>Luis Majano</dc:creator>
				<category><![CDATA[ColdFusion]]></category>
		<category><![CDATA[Flash Forms]]></category>
		<category><![CDATA[Flash Remoting]]></category>

		<guid isPermaLink="false">http://www.luismajano.com/</guid>
		<description><![CDATA[Restart CFMX and you are ready to debug.  This is tedious if you need to disable it again. So after a few hours of trial and error and digging through the Actionscript whitepapers, I finally came up with a "ONE LINER" to activate debugging.  Let's say for example you have a simple form calling a remote service and the button code is the following:

<div class="code"><FONT COLOR=MAROON>&#60;cfinput type=<FONT COLOR=BLUE>"button"</FONT> &#160;&#160;&#160;&#160;&#160;&#160;<br />
&#160;&#160;&#160;&#160;&#160;&#160; name=<FONT COLOR=BLUE>"button_hello"</FONT><br />
&#160;&#160;&#160;&#160;&#160;&#160; value=<FONT COLOR=BLUE>"Say Hello"</FONT> <br />
&#160;&#160;&#160;&#160;&#160;&#160; onclick=<FONT COLOR=BLUE>"#sayhello#"</FONT>&#62;</FONT></div>

The "sayhello" variable holds the remoting call:

<div class="code"><FONT COLOR=MAROON>&#60;cfsavecontent variable=<FONT COLOR=BLUE>"sayhello"</FONT>&#62;</FONT><br /><FONT COLOR=GRAY><I>
//NetDebuggin ON, That was simple</I></FONT>
var debug:Boolean = mx.remoting.debug.NetDebug.initialize();<br />
<br /><FONT COLOR=GRAY><I>
//create gateway connection    </I></FONT>
var connection:mx.remoting.Connection = mx.remoting.NetServices.createGatewayConnection(<FONT COLOR=BLUE>"<A TARGET="_blank" HREF="http://www.luismajano.com/flashservices/gateway/">http://www.luismajano.com/flashservices/gateway/</A>"</FONT>);<br /><FONT COLOR=GRAY><I>
//declare service    </I></FONT>
var myService:mx.remoting.NetServiceProxy;<br /><FONT COLOR=GRAY><I>
//Create response handler</I></FONT>
var responseHandler = {};<br />
<br />
responseHandler.onResult = function( results: Object ):Void {<br />
  alert(results);<br />
}<br />
<br /><FONT COLOR=GRAY><I>
//function that receives any error that may have occurred during the call</I></FONT>
responseHandler.onStatus = function( stat: Object ):Void {<br />
 <FONT COLOR=GRAY><I> //if there is any error, show an alert</I></FONT>
  alert(<FONT COLOR=BLUE>"Error while calling cfc:"</FONT> + stat.description);<br />
}<br />
      <br /><FONT COLOR=GRAY><I>
//get service</I></FONT>
myService = connection.getService(<FONT COLOR=BLUE>"utilities.hello"</FONT>, responseHandler );<br />
   <br /><FONT COLOR=GRAY><I>
//make call</I></FONT>
myService.sayHello();<br />
<FONT COLOR=MAROON>&#60;/cfsavecontent&#62;</FONT></div>

And there you go, the NetDebugger will now work.  That was a lot of research for one line. Please let me know if you have any other ways of enabling debugging.  

Thanks.]]></description>
			<content:encoded><![CDATA[<p>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.</p>
<p>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: <b>flex-config.xml</b> which can be found under the following directory:</p>
<p>{CF_ROOT}/WEB-INF/cfform/flex-config.xml</p>
<p>Open the xml file and locate the following section:
<div class="code">
<p>&lt;!&#8211; When production-mode=true, the debugging options are always<br />
    false and may not be set. &#8211;&gt;<br />
    <FONT COLOR=NAVY>&lt;debugging&gt;</FONT></p>
<p>&lt;!&#8211; allow override of values in debugging section via<br />
query parameter on a per-request basis, if applicable &#8211;&gt;<br />
        <FONT COLOR=NAVY>&lt;process-debug-query-params&gt;</FONT>true<FONT COLOR=NAVY>&lt;/process-debug-query-params&gt;</FONT><br />&#8230;&#8230;    <br />
  <FONT COLOR=NAVY>&lt;/debugging&gt;</FONT></p>
</p></div>
<p>This is the flex debuggin configuration.  So in order to activate the debugger change the following entries to true.</p>
<div class="code"><FONT COLOR=GRAY><I><FONT COLOR=GRAY><I>&lt;!&#8211; turn on debug to see the request and response on the server side as well<br />
             as debug information in client side tracing &#8211;&gt;</I></FONT></I></FONT><br />
        <FONT COLOR=NAVY>&lt;remote-objects-debug&gt;</FONT>false<FONT COLOR=NAVY>&lt;/remote-objects-debug&gt;</FONT></p>
<p>&lt;!&#8211; turn on debug to see the request and response on the server side as well<br />
             as debug information in client side tracing &#8211;&gt;<br />
        <FONT COLOR=NAVY>&lt;web-service-proxy-debug&gt;</FONT>false<FONT COLOR=NAVY>&lt;/web-service-proxy-debug&gt;</FONT></p>
<p>        <FONT COLOR=GRAY><I>&lt;!&#8211; turn on debug to see the request and response on the server side &#8211;&gt;</I></FONT><br />
        <FONT COLOR=NAVY>&lt;http-service-proxy-debug&gt;</FONT>false<FONT COLOR=NAVY>&lt;/http-service-proxy-debug&gt;</FONT></div>
]]></content:encoded>
			<wfw:commentRss>http://luismajano.com/2005/09/02/netdebuggercfflashforms/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

