December 13th, 2007 by Kyle
Tags: , , , , , , , , , , , ,
Posted in: Air, Flex, LCDS


Adobe Flex sdk beta 3 and Adobe AIR beta 3 just release to Adobe Labs yesterday, so I have updated my version checker AIR application to detect the new SDK and also compiled the app against the new AIR classes targeting the new AIR runtime.

All other blog references will be pointing to this new version

>>>> here <<<<<.




5 Comments »

November 26th, 2007 by Kyle
Tags: , , , , , , , , , , , , ,
Posted in: Air, Flex, LCDS


I just recently was made aware that there are actually 3 different “builds” of Flex SDK “hotfix 3″ out there.
1. Originally hotfix 3 was applied to hotfix 2 (updating a few swcs) – version 1
2. Late summer 2007 it was realized this confused some folks so the hotfix kb article was replaced with a full version of the SDK with the fixes applied – version 2
3. Flex Builder 3 beta 2 shipped with the latest/greatest SDK from the 2.0.1 branch which is an equivalent to hotfix 3 SDK – version 3.

These versions should be functionally identical afaik.

I updated my version checker to detect and differentiate these versions. I have updated the original blog entry here and also have links to the update AIR app here.




No Comments »

November 12th, 2007 by Kyle
Tags: , , , , , , , , , , , ,
Posted in: Air, Flex, LCDS


Finding out what version of the SDK you are using for Flex Builder, command line compilation, Ant compilation or in your Flex war file for FDS or LCDS can be comfusing. Especially if you have added one of the SDK hotfixes for 2.0.1. When faced with issues from customers, I often ask them what version of the Flex SDK or FDS/LCDS they are using. Sometimes they don’t know or don’t remember if they have installed a hot fix or if they are running FDS or LCDS. To be fair though, finding out what version of the SDK is not clear nor is finding out the version of a FDS/LCDS war. Cracking open some swc files or jar files to find a build number or starting your server to look for a build number in the output or logs and translating the build number to an actual version equivalent really could be made easier. I thought this would make a good AIR application, so I started coding and here is what I came up with. Mind you, it is not feature complete, pretty looking or by any means architecturally elegant. It does the job though…those other things can come later. This is build with Adobe Air Beta2, which can be downloaded here.

Here is a link to the installer.




1 Comment »

This post is to carry on from my previous post regarding moving data from ColdFusion CFCs to Flex 2 Applications Using Webservices.

Here is the first sample showing basic retrieval of a string via Remote Object:

< ?xml version="1.0" encoding="utf-8"?>
<mx:application xmlns:mx="http://www.adobe.com/2006/mxml" layout="vertical" >
    <mx:script>
        < ![CDATA[
            import mx.rpc.events.ResultEvent;
            import mx.controls.Alert;
           
            [Bindable]
            public var sResult:String;
           
            public function handleStringResult(event:ResultEvent):void{
                sResult=event.result as String
            }
         
        ]]>
    </mx:script>
       
    <mx:remoteobject id="myService"
        destination="ColdFusion"
        source="services.HelloWorld">  
        <mx:method name="sayHelloString" result="handleStringResult(event)"  fault="Alert.show(event.fault.message)" />
    </mx:remoteobject>

    <mx:label id="lblStringResult" text="{sResult}"/>   
    <mx:button label="get String Remote Object" click="myService.sayHelloString()"/>

</mx:application>
 

This movie requires Flash Player 9

Browse the source of this example.
Download a zipfile containing the source to this sample.

Read the rest of this post»




1 Comment »

One of my first blog posts pointed to a dev center article that I wrote on this topic for the Flex 2 release. I often send customers to look at this article when appropriate as it is a good starting point for webservice and remoteobject communication between Flex and Coldfusion. I also find myself referring to this sample once in a while and so I have finally decided to host the sample and cfc from my website/blog and potentially enhance the cfc to support more use cases for subsequent blog posts.

< ?xml version="1.0" encoding="utf-8"?>
<mx:application xmlns:mx="http://www.adobe.com/2006/mxml" layout="vertical" >
    <mx:script>
        < ![CDATA[
            import mx.rpc.events.ResultEvent;
            import mx.controls.Alert;
           
            [Bindable]
            public var sResult:String;
               
            public function handleStringResult(event:ResultEvent):void{
                sResult=event.result as String
            }
           
        ]]>
    </mx:script>
       
    <mx:webservice id="myService"
        useProxy="false"
        wsdl="http://739saintlouis.com/services/HelloWorld.cfc?wsdl"
        showBusyCursor="true">     
        <mx:operation name="sayHelloString" result="handleStringResult(event)" fault="Alert.show(event.fault.message)"/>
    </mx:webservice>
    <mx:label id="lblStringResult" text="{sResult}"/>   
    <mx:button label="get String via Webservice" click="myService.sayHelloString.send()"/>

</mx:application>
 

This movie requires Flash Player 9

Browse the source of this example.
Download a zipfile containing the source to this sample.

Read the rest of this post»




2 Comments »

August 2nd, 2007 by Kyle
Tags: , , , , , , , , ,
Posted in: Flex, LCDS


Here is a post by the Flex Doc team on their blog that is very useful:

Real Time Messaging channels in LCDS ES

It should help customer’s with configuration questions regarding dataservices and rtmp/t channels when using firewalls and load balancing software.

HTH

-Kyle




No Comments »

June 29th, 2007 by Kyle
Tags: , , , , , , , ,
Posted in: Flex, LCDS


I have had a few customers come across the following error when trying to restart the LCDS 2.5 or FDS 2.0 applications without restarting the app server.

[6/28/07 10:54:22:468 EDT] 0000001f ServletWrappe E   Deregister the
mbean because of uncaught init() exception thrown by servlet
MessageBrokerServlet: javax.servlet.UnavailableException: The MBean, ‘flex.runtime.LiveCycle Data Services:type=MessageBroker,id=MessageBroker1′, cannot be registered because the previous MBean with the same name could not be unregistered possibly due to some security setting on the application server. This can be avoided by setting manageable property to false in the configuration file.
at
flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:154)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:
190)
at
com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.jav
a:317)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper
.java:1142)
at
com.ibm.ws.wswebcontainer.servlet.ServletWrapper.initialize(ServletWrapp
er.java:150)
at

……

 

Read the rest of this post»




No Comments »

I just published two Tech note articles for Flex regarding changes to Daylight Savings time in effect for 2007 and Sun’s JVM changes regarding this:

“How to upgrade the JVM shipped with Flex”

and

“Flex and Sun’s JVM: U.S. Daylight Saving Time changes in 2007″




1 Comment »

I wrote this article for the Flex 2.0 release.
It is a good intro on how you can move data between Coldfusion 7.02 CFCs and Flex 2.0 using Web Services or Remote Object calls.

My co-worker, Lin Lin, blogged a good follow up to this article that expands up on the configuration and steps necessary to access cfcs on your Coldfusion server from a flex app on a separate server.




No Comments »