Posted on Fri. January 26, 2007 by Ryan Guill #
Entries for January 2007
After all the agony Mark has put us through lately, he has finally released CFEclipse 1.3! Get it while its hot!
A quick question I want to pose to the community. How do you handle releases and new versions of your coldfusion or flex application? Does your method support multiple versions being available at the same time? Does your method support being able to fall back on a previous version if something goes wrong in the current release? I'm interested in methods for your public facing "internet" sites as well as internal only "intranet" type applications.
Just curious how different people handle these things or if it is a concern at all.
You will have to forgive me too, my mail server is still not working correctly, so I may have to respond to you directly, but I'll try to post back here as well with any responses.
Thanks!
Posted on Thu. January 25, 2007 by Ryan Guill #
Someone helped me a while back figure this out (sorry, I can't remember who, if it was you, let me know!) but I thought it was quite useful, because it gives you a lot more flexibility.
This allows you to create your remote objects for flex to talk to CF in actionscript instead of using the mx:RemoteObject tags.
Here is the example code:
import mx.rpc.remoting.RemoteObject;
import mx.rpc.events.ResultEvent;
import mx.rpc.events.FaultEvent;
import mx.rpc.events.InvokeEvent;
import mx.messaging.Channel;
import mx.messaging.channels.AMFChannel;
import mx.messaging.ChannelSet;
import flash.events.Event;
import mx.controls.Alert;
public function onCreationComplete () : void
{
//create the remote objects first
createRemoteObjects();
//set the AMF Channel on the remote objects
setUpAmfChannel();
}
public function createRemoteObjects () : void
{
ro = new RemoteObject();
ro.destination = "ColdFusion";
ro.source = "path.to.cfc";
ro.addEventListener("fault",ro_fault_handler);
//You probably want and need a result handler...
ro.methodName.addEventListener("result",methodName_result_handler);
//You may need this if you need to do something when a method is called
ro.methodName.addEventListener("invoke",methodName_invoke_handler);
//You may need this if you need to catch and handle errors differently
ro.methodName.addEventListener("fault",methodName_fault_handler);
//This is just sugar, you really dont need it unless you want it.
ro.methodName.showBusyCursor = true;
}
/* You can call the following method anytime to set the amf channel for a remote object on the fly */
public function setUpAmfChannel () : void
{
var amfChannel:Channel = new AMFChannel("my-cfamf","http://server/flex2gateway/");
amfChannelSet = new ChannelSet();
amfChannelSet.addChannel(amfChannel);
//repeat the following line for all remoteObjects
this.ro.channelSet = amfChannelSet;
}
public function ro_fault_handler ( event:FaultEvent ) : void
{
Alert.show( event.fault.faultString, 'Error');
}
public function call_methodName () : void
{
//use this to call the method
ro.methodName(/*pass arguments here*/);
}
public function methodName_invoke_handler ( event:InvokeEvent ) : void
{
//this will fire when the method is invoked
}
public function methodName_fault_handler ( event:FaultEvent ) : void
{
//this will fire when the method throws an error
}
public function methodName_result_handler ( event:ResultEvent ) : void
{
//this will fire when a result comes back from the method
}
You can see how the remote object is created, the methods are defined along with the actionscript methods that handle faults, invokes and results, and you can also specify the amf-channel on the fly, which is quite nice. This gives you far more flexibility when calling your remote object methods than the mxml does in my opinion.
Posted on Thu. January 18, 2007 by Ryan Guill #
It really is amazing how many people are really interested in Open Source software. I wrote CFSSP a long time ago to fill a need for a manager for Todd Dominey's slideshowpro. I thought interest in it had died down and so I stopped developing on it, especially once Todd released his own manager for the program (although admittedly it is php) that was so much nicer than what I had written. So I let the project sit. But then I moved hosting servers which broke all my links to the cfssp files and man, you wouldn't believe the emails and questions I get of people trying to find it.
So, just so you all know, I have pushed the project to RIA forge. You can find it here: http://cfssp.riaforge.org/. There are forums and the whole nine yards there, so enjoy!
Posted on Mon. January 15, 2007 by Ryan Guill #
Well, yeah, it sorta is I guess. I thought I would wait to today to let the flex 2.0.1 dust settle, but from the looks of MXNA its still going strong.
Just a quick note to those of you out there that are about to get it: If you already have flex 2 products installed, you need the Updaters. If you do not have any flex 2 products installed, go get the free trials, it wont matter.
Thanks to Renaun Erickson for clearing that up.
Go get Flex 2.0.1 here, and get ready for apollo!
Posted on Mon. January 08, 2007 by Ryan Guill #
I am now the new manager of the Memphis Adobe User Group, previously the Memphis Macromedia User Group. For those of you that have been involved in the past, Tom Kristien will still be helping. We have a lot of things planned, and our first meeting is tomorrow night, Wednesday the 3rd at 6pm. Please come and bring a friend! It should be a short meeting, we are mostly going to talk about what sort of topics that people are interested in, and in different ways we can improve attendance.
Also, if you are interested in joining or coming at all, please join the new google groups email list at
http://groups.google.com/group/MAUG/
So if you are in the Memphis area and are interested in any Adobe products, please join the list and come by!
If you have any other questions or comments, feel free to contact me directly at ryanguill [at] gmail [dot] com.
Posted on Tue. January 02, 2007 by Ryan Guill #