Author Archive: lin

Adobe Product – system requirement

If you have an older version of the product, please check the following links so that you can consider upgrade to a supported version.

Adobe Product – Supported Versions:






Flash Player:

CQ/CRX — How to download hotfixes/package from package share

To find out what hotfix/component/featurepack you need, please check hotfixes list for CRX or CQ.

To download and install the hotfix/component/featurepack:

1. Start your CQ/CRX service, and login to your CQ/CRX main page, click on package, then package share; you can also find package share by go to /crx, then click on package share.
You will be prompted for login. You need to use your Adobe ID to login. If you don’t have one yet, just click on register and create one. It only needs your email address as user name, and a password.

2. Once logged in, you can see a list of packages that is available. Note it will only display the first 5 Adobe package on the page, so you may not see the hotfix you needed. You can search the name/number of the package/hotfix you need from the top right searching box. For example, type in 36281 will find cq-5.4.0-hotfix-36281.
Note, you may find multiple versions of cq-5.4.0-hotfix-36281, use any one of them for download.

3. Before you download the package/hotfix, you should check the dependency first. Click on cq-5.4.0-hotfix-36281, it will display the detail about the hotfix. Pay attention to the Dependencies. For hotfix-36281, it has feature:cq-5.4.0-featurepack-35156:1.1 as dependencies. This means you should download feature:cq-5.4.0-featurepack-35156:1.1 first, then apply cq-5.4.0-hotfix-36281.
Note, if this feels complicated, you may want to open a support ticket to have support engineer guide you. Sometimes, there is a replacement hotfix that will allow you to use one later version of hotfix instead of download several packages. In our example, you can use cq-5.4.0-hotfix-34304 instead of using cq-5.4.0-hotfix-36281 and cq-5.4.0-featurepack-35156:1.1.

4. Once you know which hotfix is needed, click on download to download, and then click install to install the hotfix.

CQ/CRX general info and troubleshooting tips

General Info:

  • Q: What version of OS or app server are supported by CQ/CRX?
    A: For CQ5.4, See Technical requirement
    Only the version of OS/App server indicated with “A:supported” are officially supported.
    Note, ADEP doesn’t support any app server at this point, customers who want that support need to contact support team and make a request.

  • Q:what is the current version of CQ/CRX?
    A:The corrent version of CQ is 5.4, and it includes CRX 2.2.0. There are hotfixes for both CQ and CRX.
    CRX2.2 Hotfixes

    Troubleshooting tip

  • Problem: Downloading PowerPoint in Internet Explorer displays login screen before download.
    Solution: See our KB at
  • Continue reading…

    Behind the scenes– what happens when you install CQ/CRX

    When you install CQ or CRX either by double click on crx-quickstart.jar/cq-quickstart.jar or using command line(doesn’t matter what run mode you are installing, a default mode, or author/publish mode), the following steps are performed during first installation:
    1. the quickstart is unpacked to the crx-quickstart directory, and you can see crx-explorer_crx.war & crx-launchpad.war under: crx-quickstart\server\webapps
    2. then cqse is started
    3. cqse starts the crx webapp
    4. the crx webapp starts the repository
    5. during repository start-up, it checks the repository/install folder for content packages and installs them (if repository/Tar/index is out of sync, will not start correctly)
    6. then the launchpad webapp is started
    7. Felix starts the core bundles
    8. one of the core bundles is the JCR installer, which searches all ‘install’ nodes in the repository and registers those bundles
    9. Felix starts the newly registered bundles

    There are three parts in CQ/CRX that will work together, they are descripted below:

    Where the data gets stored:

    • CRX uses the Tar Persistence Manager (TarPM), tar files are stored under:
    • CRX configuration files

    How to create class/jar files for data service project without using maven

    In the sample for “Create a Data Services application for the Experience Server that returns data“, it showed how to bundle your class for data service project into the template application and build/deploy the bundle using Maven. There are several ways to build the bundle without using Maven. I will add all the options here.

    For our sample, the class we need to build is this:

    package com.adobe.myexample;
    public class EchoService {
        public String sayHello(String val){        
            return "Adobe Digital Enterprise Platform says: " +val ;

    • Using CRXDE

    This is the easiest option for this task. It will compile your java class, build bundle and automatically install and start in the OSGI container. New user should use this option. For details, see “Creating a Bundle” section of the doc here. The following steps should be clear.

    Note, whenever work with CRXDE Lite, you have to click on “Save ALL” at the left top after you made any change (create/modify/delete) in CRXDE, and click on refresh to make sure the change has been saved/updated.

    1. Start your experience service and go to CRXDE Lite via http://localhost:4502/crxde

    2. Create a project by right click on apps, select create-create project, put in the following info:
    Project name: myapp
    Java package: com.adobe.myexample
    This will create folder /src, /install, and /components under myapp for you.

    3. Create a bundle by Right click the folder apps/myapp/src, select create-create bundle , put in the following info:
    Symbolic Bundle Name: com.adobe.myexample.TestEcho (this can be any name)
    Bundle Name: TestEcho Bundle (this is the name will be displayed in Felix console Bundle )
    Bundle Description: This is my Test Bundle
    Package: com.adobe.myexample (This must be your java package name)
    This will create com.adobe.myexample.TestEcho folder and com.adobe.myexample.TestEcho.bnd under it.

    4. create your java code by Right click on folder /apps/myapp/src/com.adobe.myexample.TestEcho/src/main/java/com/adobe/myexample, create–>create file, enter as name. Make sure it is at the same folder as Then click on , and then put your java code into the right side edit area. Save it.

    package com.adobe.myexample;
                       public class EchoService {
                       public String sayHello(String val){  
                           return "Adobe Digital Enterprise Platform says: " +val ;

    Note, If you already have your classes in a jar, then instead of creating class here, create a folder libs under /apps//src//libs/, then go to http://localhost:4502/crx and use “content loader” to import the jar into libs folder.

    5. build your bundle by Right click on com.adobe.myexample.TestEcho .bnd, select Tools–>build Bundle
    This will compile your java class, build bundle and automatically install and start in the OSGI container.

    To verify the bundle has been install into OSGI, you can check from Felix, http://localhost:8900/system/console/bundles/
    you can search by the Bundle name “ TestEcho Bundle” to find it. Click on the arrow to see the info about the Bundle. Make sure you have all the class in there and the proper packages are exported.

    • Convert a jar File into an OSGi Bundle
    When you have your classes in a jar, you can convert it into an OSGI Bundle, see details here

    1. Creating manifest file.
    This is the key to the process. In order for Bundle to be created correctly, there are several elements you need to pay attention to. You should have the following in the manifest file:
    Bundle-Name: (this will be the name displayed in the Felix console Bundle tag, you can search this name to check if the bundle is installed or active.)
    Bundle-Version: (should always use a higher number than the provirus version if a version has been installed, otherwise the new bundle will not be installed. But if you include SNAPSHOT like 1.0- SNAPSHOT, it will always install.
    Bundle-ClassPath: .,myapp.jar (make sure you have the correct name of the jar you want to convert.)
    Bundle-SymbolicName: (can be any name)
    Import-Package: (if you have dependency class/jar for your class, you need to import them)
    Export-Package: (this is the name of your java package name, must have this so that the class can be accessed by others)

    2. Create the bundle jar (myapp-bundle.jar) by using zip or java command:
    jar cvfm myapp-bundle.jar manifest.txt myapp.jar

    3. Install the bundle.
    Use content loader to load the jar under your app’s /install or /libs folder, like /apps/myapp/install/ and jar under /install or libs folder will be picked up.

    Note, the /install or /libs should not be at more than 3 layer under apps, for example, /apps/myapp/component/bundle/install, the bundle jar will not be picked up in this case.

    This can also be done by using curl command line described here.

    Another option is to install OSGi bundles via CRX packages as described in this techNote.

    How to Create a Data Services application for the Experience Server that returns data

    In Our development guide for Experience Service, there is an good example about “Create a Data Services application for the Experience Server that returns data”, see link here. It described all the details necessary for the project. However, there are a few places that could be confusing for users that are not familiar with CRX/CQ and Maven. In this blog I have re-organized and simplified the steps to make it easier to follow, and added Note in the places where it could be easy to make mistake or get confused. I have also put Troubleshooting Tips at the end. I hope this will make deploying to Experience Services easier for you.

    I have divided the task into three sections:

    • Prepare the development environment:
    • Create and configure server-side project
    • Create and configure client side project

    If this is the first time you work with data service 4.5 version(running on CQ servlet), please make sure you go through the first section to get your environment set up correctly for your future development.

    [Note] Step 6 to 8 is for using Maven to build and deploy the app. If you want to load you class/Jar and app directly into OSGI without using the template application and maven, you can skip these steps and follow the link here, then go to step 9.

  • Prepare the development environment:

  • 1. Download the Flash Builder 4.5 installer from here and install the software as described in Flash Builder 4.5 Release (Note, for MAC, you need to do more configuration. See here

    2. Install plug-ins for Flash Builder, see here.

    3. Setting up Maven in your development environment (If you don’t want to build the project via maven for developing test, you don’t have to configure this at this time)

      a. Download maven from
      b. After extract Maven to your machine, for example, c:/apache-maven-3.0.3, create an environment variable named M3_HOME, and point to c:/ apache-maven-3.0.3.

    4. Install and config ADEP Experience Services

      a. Download the Experience Services Quickstart JAR file from here . The file name should be something like adep-ria-quickstart-10-0-all-all.jar
      b. Make sure you have jdk1.6.0_26 or higher installed on your machine (but 1.7 is not supported). And set JAVA_HOME to point to the jdk1.6.0_26, and Path= %JAVA_HOME%\bin;
      c. Create a directory to run your ADEP Experience Services. For example, create c:/dataService_sample, and copy adep-ria-quickstart-10-0-all-all.jar into directory and rename it to adep-ria-quickstart-10-0-all-all-p4502.jar. (This will make the Experience Services to use port 4502).
      d. Start Experience Services by double click on adep-ria-quickstart-10-0-all-all-p4502.jar. This will take several minutes to install. Once it is done installing, a license page will come up, or you can access it by http://localhost:4502 . Log in using your Adobe ID and password to Retrieve License Key. (Note: the Adobe ID is the account you use to download any adobe software to access adobe lab or shared package. If you don’t have an account yet, you can go to to create one.)
      Once you get the license key and put in the license page, you will see ADEP Experience Services login page. Use admin/admin to login.
      e. From the welcome page, click on “packages”, scroll down and find Clicks on, then click download to save it on your machine. Then do the same to download

    Make sure you have all above installed and configured before you start to create or deploy your data service project.

  • Create your data service application server-side--using remote to return data
  • 5. Create your Java server-side class. For this example, we create a simple class named like this:

    package com.adobe.myexample;
    public class EchoService {
    public String sayHello(String val){
    return "Adobe Digital Enterprise Platform says: " +val ;

    Note: To compile your class, you need to have dataservices-bundle.jar in your classpath. (EchoService doesn’t need this because it is not using any of the data service classes). The dataservices-bundle.jar can be obtained from the you downloaded on step 4.e. It is under:[ZIP location]\dataservices-sdk-pkg\jcr_root\etc\aep\sdks\riaservices\dataservices\4.5.0\java

    6. To place the application files in the template application
    Extract you got from 4.e to a folder on your machine, say c:/template:

      a. copy dataservices-bundle.jar and put into the template application’s lib folder.
      b. Under the sourceCode\src\main\java folder, create a folder structure that reflects the Java package structure. For this example, it is: sourceCode\src\main\java\com\adobe\myexample.
      c. Place file in the myexample folder.
      d. Open pom.xml file under sourceCode folder, scroll down and find the following section:


    And change it to:


    Note: there are multiple mop.xml file in the template app, make sure you modify the one under sourceCode folder, otherwise your app will not be built correctly.

    7. Using Maven to build the package:
    Open command prompt under c:/ template, enter the following command:
    %M3_HOME%\bin\mvn clean install

    Make sure the build was successful by looking at the log. After the build was successful, it will create a zip file dataservices-example-app-bundle-1.0-SNAPSHOT.jar under c:/ template/package/target

    8. Deploy your app to Experience Services:

      a. Go back to http://locahost:4502, click on Packages, then click “Upload package” from the menu, then select dataservices-example-app-bundle-1.0-SNAPSHOT.jar under c:/ template/package/target.
      Click on dataservices-example-app-bundle-1.0-SNAPSHOT.jar that’s displayed there, then click Install.

    Note, make sure you click install, otherwise the jar is not loaded into the experience services.

      b. To confirm your package was deployed, to go OSGI console by http://localhost:4502/system/console/bundles (or you can go to welcome page, click on OSGI console, then select bundle tag), login using admin/admin
      Then search your bundle to make sure it is here, and click on the arrow beside the [package name to see the details and make sure your class is in there.
      c. To confirm your RDS is enabled: go to http://localhost:4502/system/console/configMgr
      click on “Adobe data Services”, then check enable RDS

    9. Defining the server destination for the echo service

      a. Go to http://localhost:4502/crxde , from left panel, find: /etc/aep/config/dataservices/destinations/remoting Right click on remoting folder, and select create-create file, put the file name as com.adobe.myexample.xml, click OK.
      b. Double click the com.adobe.myexample.xml file, then add the following in the to file (at right)

    <?xml version="1.0" encoding="UTF-8"?>
      <destination channels="my-amf" id="echo">

    From the top menu, click the Save All button. (Don’t forget about this step).

  • Creating a Flash Builder client project for the Echo service
  • Start flash builder 4.5 (make sure the Modeler plug-in is installed by step #2)

    10. Before you create a flash builder project for your app, verify you can see the destination you created in step #9 :

      a. Change perspective to Data Model from flash builder by clicking Window, Open Perspective, Data Model,
      b. Search echo in the Remoting destinations folder.

    11. the a Flex Project for ADEP Experience Services application

      a. create a project “Flex Project for ADEP Experience Services”
      b. From the RDS server, select Experience Server (localhost)
      The host name for RDS is localhost, port is 4502, user account admin/admin.
      c. Click Test Connection button to verify connection. If it can’t connect, check and make sure the service is started (see step#4.d), and RDS is enabled (see step #8.c)
      d. Put the client code from the doc sample
      e. Run the client code from flash builder

    Troubleshooting Tips:

      1. Get Fault: “cannot create class of type ‘com.adobe.myexample.EchoService’”

    This indicates your class is not loaded into the OSGI. Double check Step 5, 6, 7, 8, and reinstall your package.

      2. Get “connection failed” error

    This ould be caused your RDS not enabled or configured correctly, see step 11.c. It also could be channel/destination configure issue, you may want to double check your channel/destination configure to make sure all the sytax and spell are correct.

      3. Get error indicating my-streaming-amf:

    go to
    http://localhost:4502/crxde , open /etc/aep/config/dataservices/services-config.xml from the left panel, you can see the section:

               <channel ref="my-streaming-amf"/>        
               <channel ref="my-polling-amf"/>      
               <channel ref="my-amf"/>

    <channel ref="my-amf"/>

    to be the first item in there, and restart the server and re-run the client code, this should get rid of the error.

    Duplication session error

    We have heard a number of customers who run into duplicate sessions error in LCDS/BlazeDS. To understand why and how it could happen, please see explanation here.

    Basically, here are the causes and solution:
    1. Cookies are disabled on the client.
    solution: turn the cookies on the client.

    2. Citrix had a policy to block session cookies.
    solution: if you are using Citrix, need to turned it off.

    3. The flex app makes two subsequent requests to the server before a session is established on the server for the first request.
    solution: there are two options (See details here.):
    a). the flex app should make the initial request and waits for its response (so a session is established) before making new requests.
    b). trap the duplicate session error on the client and reissue the request. (See details here.)

    4. Load balance tool cause subsequent requests to send to different server.
    LCDS is a stateful server. This means that when a client makes an initial request to a server, the environment needs to make sure that all the requests from that client ends up on the same server from then on. In this case, you have to make sure your Load balance is configured so that all the subsequent requests from the same client is going to the same server. fail to do so will end up with this duplicate session error.
    solution:: Make sure all the subsequent requests from a client end up at the same server.

    Note, Some users may want to disable the duplicate session detection to get round the problem. Disabling the duplicate session detection is not an option because it’s a security risk. A single FlexClient is supposed to be associated with a single HTTP based session. If this is not enforced, your app could have some security risk. So, LCDS is checking the duplicate session for you and it should not be ignored. You should always find out and fix the underline problem instead of try to disable the duplicate session detection.

    Tips about AIR 2.5.1 installation

    1. Mac OS X 10.4.9 is the minimum version required by AIR 2.5+. It is advisable to run 10.4.11.
    2. To install AIR, you have to login as an user that has admin rights.
    3. If you do have admin rights but the installer display an error indicating you don’t, then you may have run into a file system permissions issue. On Mac, Check /Library/Application Support/Adobe to see who owns the directory. If it is owned by root, then you need to reset it to the user account, and remove the AIR subdirectory.
    4. Older version of AIR can be found at

    Flex 4 SDK Release Notes

    This document contains release notes and installation instructions for Adobe® Flex® 4 SDK.

    About Flex 4 SDK
    What’s new
    Installation instructions
    Compatibility issues
    Using Datavisualization with the Flex SDK 4
    Using Automated Testing with the Flex SDK 4
    Known issues
    Flex 4 Documentation
    About Flex 4 SDK
    Flex 4 SDK includes the Flex framework (also known as the Flex class library), Flex command-line compilers, the Flex debugger, the ASDoc utility, and the debugger version of Flash Player and AIR runtimes. Use the Flex 4 SDK to develop, compile, and deploy Flex applications that connect to XML and SOAP web services or connect to various server technologies such as PHP, ColdFusion, Java, and .NET using a server technology such as BlazeDS. Flex applications can be built and configured to target browsers via the Flash Player runtime or desktops via the AIR runtime.

    What’s New in Flex 4
    This section lists some of the major new features and changes for Flex 4 SDK. See the What’s New in Flex 4 article for more information on new features.

    A new and powerful component skinning architecture, known as “Spark”. To learn more about the Spark skinning architecture, see the Introducing Skinning in Flex 4 article.
    A set of components that use the Spark architecture that can be mixed and matched with the MX components that are available in Flex 3. To learn more about the Spark architecture and components, see the Brief Overview of the Spark Architecture & Component Set article.
    Support for declarative, dynamic MXML graphics, as well as for static, optimized FXG graphics.
    A new default look (the “Spark” theme) for MX and Spark components which support a new set of styles.
    More powerful layout capabilities, including support for MXML graphic elements, improved support for rotation and other transforms, support for assignable custom layouts, and enhanced z-order management capability. To learn more about layouts in Flex 4, see the Spark Layouts with Flex 4 article.
    Numerous new and/or improved effects, including support for animating MXML graphic elements, support for animating arbitrary types via custom interpolators, a more flexible easing API, and more automatic behaviors. To learn more about effects in Flex 4, see the Effects in Adobe Flex pair of articles.
    3D effect support.
    Animation of Flash filters, including Pixel Bender shaders.
    More advanced text support, based on the Flash Text Engine and the Text Layout Framework, as well as support for CFF (Compact Font Format) fonts.
    Improved compiler performance.
    New MXML language features, including the MXML 2009 namespace, much improved support for States, and the Declarations, Library, and Definition tags.
    CSS enhancements, including support for namespaces, descendant selectors, ID selectors, multiple class selectors, and pseudo-selectors for component states.
    Convenient syntax for two-way databinding.
    ASDoc improvements including support for Linux platforms, comments defined in mxml files, and creation of DITA XML files that allow for documentation to be displayed as tooltips within FlashBuilder.
    Improved HTML templates, based on SWFObject.
    Hosting of SDK runtime shared libraries (RSLs) at
    Additional locale support for developing localized applications.
    Support for JAWS 11 – As of version 4, Flex supports the JAWS 11 screen reader.
    Installation instructions
    The Flex SDK installation is delivered as a ZIP file and contains the Flex framework, Adobe AIR framework, and command-line tools, such as the mxmlc command-line utility, Adobe AIR command-line utility, the ASDoc utility, the Flex command-line debugger, and the debugger version of Flash Player.

    Uninstall Current Flash Player

    You should use Flex SDK with the latest version of the debug Flash Player 10. Prior to installing the Flex SDK, you should uninstall your current Flash Player.

    Windows-Plugin-based browsers
    Run the appropriate uninstaller available from this Tech Note.

    Run the appropriate uninstaller available from this Tech Note.

    Manual removal (for users who installed the plug-in via Install script):

    Delete the binary and the flashplayer.xpt file in directory /home//.mozilla/plugins/

    RPM removal:

    As root, enter the following command:

    # rpm -e flash-plugin
    Click Enter and follow the prompts.
    Install the Flex SDK

    1. Download Flex SDK ZIP file from the Adobe website or the Adobe Open Source site.

    Create a directory to contain Flex SDK

    Extract the Flex SDK ZIP file to this directory. The Flex SDK contains the following directories:

    /ant — Contains Flex Ant Tasks.
    /asdoc — Contains helper files for the ASDoc tool that creates HTML documentation from your MXML and ActionScript source code.
    /bin — Contains the mxmlc, compc, asdoc, and fdb utilities. The bin directory also contains the jvm.config file, which specifies Java settings that you can modify, if necessary.
    /frameworks — Contains compiled framework classes, configuration files, and framework source code.
    /lib — Contains JAR files used by the utilities.
    /runtimes — Contains installers for the Adobe AIR runtime inside the air directory and installers for debug versions of Flash Player 9 inside the player directory.
    /samples — Contains sample applications.
    /templates — Contains HTML templates for Flash Player detection and browser integration and inside the air folder, a sample Adobe AIR application.xml file.
    Ensure that the Java Runtime Environment (JRE) is installed on the computer and that the java_home/bin directory is defined in the system path. JRE 1.5,or 1.6 is required.

    Install the appropriate debug Flash Player from the install_root/runtimes/player/platform directory.

    (Optional) When the Flash Player installation finishes, restart your computer to ensure that the updated Flash Player browser plug-in is enabled.

    Compatibility issues
    Backwards compatibility compiler argument – There are a number of Flex SDK backwards compatibility changes in Flex 4. You can return the behavior to Flex 3 by using the compiler argument: -compatibility-version.

    To get the full list of issues, please refer to the Flex 4 Backwards Compatibility document. You may also learn more about the differences between Flex 3 and Flex 4 in this article.

    Using the Data Visualization components with Flex SDK 4
    As of Flex 4, automated testing support is part of the SDK distribution.

    Using Automated Testing with Flex SDK 4
    As of Flex 4, automated testing support is part of the SDK distribution.

    Known issues
    This section contains selected known issues. For a complete list of Flex issues and their status, see the public bugbase. The public bugbase lets you search for known issues, comment on them, and add new bugs.

    Tip: Use Filters to customize your search. – Focus does not work correctly for components that draw off-screen in Internet Explorer. Button, RadioButton, CheckBox, and Sliders draw shadows into the “negative territory.” If these components are placed at (0,0), they won’t correctly be picked up when tabbing to switch the focus.

    The workaround is to either move the component so it’s not at (0,0) anymore and doesn’t draw anything off-screen, or to change the component skins and create a custom skins that doesn’t draw shadows starting at (-1, -1).”” – item renderer selection gets out of sync when transitions are used – If some visual elements appear in some states and not in others, you may need to add a transparent Rect to cover the entire hit area to prevent an infinite loop of state changes. – Masking a UIComponent is not currently supported – spark.components.VideoPlayer – Removing VideoPlayer While Playing Doesn’t Remove Audio – backgroundImage is not supported with Spark skins theme – Avoid setting backgroundColor on a global style selector. This style gets picked up by several components that may cause unintended behavior to avoid this, set the backgroundColor style on specific components instead of on the global style selector. – RTE if TextArea is used in List ItemRenderer. Workaround is to import import flashx.textLayout.elements.TextFlow; and add this to the List typicalItem=”{(TextFlow(data[0]).deepCopy())}” – Tooltips cannot display 4-byte characters on Windows. – Sorting or dragging/dropping of pending or failed items isn’t supported. – When Alert is used in a module but not defined in the main app, current moduleFactory should be passed to so Alert can pick up styles correctly. – When module uses Alert but the loading Application does not. A variable of type PopUpManager should be added to the loading Application to avoid Runtime Exception. – AddAction/RemoveAction interferes with DisplayObject sharing – VideoPlayer unable to load Amazon Cloudfront videos – Incremental compiler fails to pick up metadata changes. Work around to do full compile. You can also download a patched .jar from the bug which fixes the problem. – In Firefox 3.6, Scroll bars show in browser after first click.

    Workaround is to add the following to the style section of the HTML template:

    a:focus, object:focus {
    outline: none;
    -moz-outline-style: none;
    } – List doesn’t respect its Layout’s typicalLayoutElement – Spark List isnt updating renderers correctly when specifying custom itemRendererFunction and using virtual layout. Workaround: Reset the itemRendererFunction to the same function after setting the data provider. – List renderer transitions get stuck when allowMultipleSelection is true – Elements with a 3D rotation inside a Scroller are affected by the scrollbars of sibling elements – Rotate3D can cause elements to not be clickable when they have a non-zero z value – Spark MXDataGridItemRenderer leaks content outside of its bounds – The ant script to build themes requires a compc.jvm.args parameter. Workaround: Pass in compc.jvm.args:

    ant -Dcompc.jvm.args=-Xmx512m – Using FTETextfield for an AIR application causes a runtime error when you open a Window with MX components. To get around this issue, you will need to use embedded fonts for this application and add the following to a Style block in your application:

    @namespace mxair “mx.core.windowClasses.*”;
    textFieldClass: ClassReference(“mx.core.UIFTETextField”);

    textFieldClass: ClassReference(“mx.core.UIFTETextField”);

    Flash Builder 4 System requirements

    Flash Builder 4 for Windows (Standard and Premium editions)
    2GHz or faster processor
    Microsoft® Windows® XP with Service Pack 3, Windows Vista® Ultimate or Enterprise (32 or 64 bit running in 32-bit mode), Windows Server® 2008 (32 bit), or Windows 7 (32 or 64 bit running in 32-bit mode)
    1GB of RAM (2GB recommended)
    1GB of available hard-disk space
    Java™ Virtual Machine (32 bit): IBM® JRE 1.5, Sun™ JRE 1.5, IBM JRE 1.6, or Sun JRE 1.6
    1024×768 display (1280×800 recommended) with 16-bit video card
    DVD-ROM drive
    Eclipse 3.4.2 or 3.5 (for plug-in installation)

    Flash Builder 4 for Mac OS (Standard and Premium editions)
    Intel® processor
    Mac OS X v10.5.6-10.6
    1GB of RAM (2GB recommended)
    1GB of available hard-disk space
    Java Virtual Machine (32 bit): JRE 1.5 or 1.6
    1024×768 display (1280×800 recommended) with 16-bit video card
    DVD-ROM drive
    Eclipse 3.4.2 or 3.5 Carbon version (for plug-in installation)

    Flash Builder 4 data-centric development features
    Adobe® ColdFusion® server: ColdFusion 8.0.1 or 9
    J2EE server: BlazeDS 4 or Adobe LiveCycle® Data Services 3
    PHP server: PHP 5.2 or Zend Framework 1.9.4 (included with Flash® Builder™ 4)
    Web services: WSDL 1.1
    Flex 4 SDK
    Windows XP Professional with Service Pack 2 or 3, Windows 7 (32 bit), or Windows Vista (32 bit)
    Mac OS X v10.5.6-10.6 (Intel only)
    Ubuntu 9.10
    Fedora Core 12
    Language versions
    Adobe Flash Builder 4 software is available in the following languages:

    Chinese Simplified