Accessibility
Adobe
Sign in Privacy My Adobe

Flex Release Notes

Flex Builder 3.0.2 Release Notes

Welcome to Adobe® Flex® Builder™ 3, the Eclipse™-based IDE for Flex developers.

Note: Adobe Flex Builder 3 automatically installs both the Flex 3.2 SDK and the Flex 2.0.1 SDK (Flex 2.0.1 Hotfix 3).

The Flex Builder 3 download page lets you download a trial version.

For instructions on installing just Flex 3 SDK, see Flex 3 SDK Installation Instructions.

What's new

This section lists some of the major new features and changes for Flex Builder 3 . See the Flex Developer Center for more information on new features.

Native support for Adobe® AIR™ – Flex Builder 3  adds support for Adobe AIR which lets developers use their existing web development skills in HTML, AJAX, Flash, and Flex to build and deploy RIAs to the desktop. Adobe AIR features include AIR project creation and Export Release Build in AIR format.
Note: Flexbuilder 3.0.2 updates this support to AIR 1.5.

Support for Flash Player 10 – Flexbuilder 3.0.2 add support for Adobe Flash Player 10.

Productivity enhancements – Flex Builder 3 introduces refactoring support, new profilers for performance and memory tuning, and code generation tools for data access.

Integration with Creative Suite 3 – New skinning templates for Adobe Photoshop, Illustrator, Fireworks, and Flash are available and Flex Builder 3 adds new wizards for importing assets from those CS3 applications as skins.

New wizards for accessing data on remote servers – The wizards guide you in connecting to your database and provides the choice of generating server-side PHP, Java, ColdFusion, or ASP.NET code to expose their data. The wizard also generates all of the MXML and ActionScript code necessary to power a basic Flex application that demonstrates standard CRUD operations against the data on your server using simple REST calls. You can then enhance the generated code to incorporate into your applications.

SOAP web services enhancements – Flex Builder 3 adds support for Web Services Introspection to simplify data access from web services. Using Flex Builder 3, you can introspect a WSDL and automatically generate code to allow easy invocation and handling of web service operations. In addition to providing code hinting on which methods can be called on a service, the generated code will deserialize responses into strongly typed objects for incorporation into the rest of the Flex application.

Enhanced Flex Builder Design View – The Flex Builder Design View has been enhanced to accurately preview item renderers. There are new pan and zoom tools to provide more fine-grained manipulations..

CSS Design View – The new CSS Design View allows Flex Builder users to graphically manipulate the skins and styles of Flex components. CSS Design View includes tools for specifying styles for component properties.

Flex Ajax Bridge Wizard – Flex Builder 3 provides a wizard that uses the Flex Ajax library to generate JavaScript calls into a Flex application. This allows a JavaScript developer to call in to the Flex application without needing to know the internals of the application.

Installation instructions

This release contains the following versions of Flex Builder:

  • Standalone Flex Builder IDE (built on Eclipse)
  • Flex Builder Eclipse Plug-in
  • Additionally, both the standalone and Plug-in versions of Flex Builder now contain two Flex SDKs; Flex 3.1 and Flex 2.0.1 Hotfix 3.

NOTE: You can run Flex Builder 2.0.1 and Flex Builder 3 on the same system. You do not have to uninstall Flex Builder 2.0.1.

Debug versions of Flash Player 10 installers are included in Flex Builder 3.0.2 in install/Player/10. They are not installed by default as part of the 3.0.2 update.

CAUTION: Do not install Flex Builder 3 into the same location of an existing installation of Flex Builder 2 or a previous Beta version of the Flex Builder 3. In particular, do not install the plug-in version of Flex Builder 3 into an Eclipse installation that is already running the plug-in version of Flex Builder 2.

Install Flex Builder Standalone on Windows

The default location of the installation directory for Flex Builder standalone is C:\Program Files\Adobe\Flex Builder 3.

  1. Log in as the Windows Administrator or as a computer administrator (a user account with administrator privileges).

    Note: If you attempt to install without administrator privileges, the installation will complete with flagged issues. However, you will have installed an incomplete version of Flex Builder that you will not be able to run.

  2. Prior to installing, uninstall any prerelease versions of Flex Builder 3.
  3. Open or double-click the installer executable file.
  4. Accept the license agreement and follow the prompts.
  5. By default, the debugging version of the Flash Player 9 browser plug-in is selected for installation.
    • The debugging version of Flash Player is Flash Player 9 (9.0.124.0)
    • This version is required for viewing and debugging applications developed with Adobe Flex Builder.
    • You must select separate installs of the Flash Player plug-in for Internet Explorer and for Firefox and Netscape browsers.
  6. (Optional) You can select the following to install:
    • ColdFusion Extensions for Flex Builder
    • JSEclipse - JavaScript plug-in (not available in Japanese)
  7. Follow the prompts to complete the installation.
  8. If you had previously installed Flex Builder 3 Beta, refer to the instructions in the section Clean and Reinitialize Cached Bundle Data.
  9. Review the Release Notes.
  10. Start Flex Builder using its shortcut in the Start menu under Adobe.
  11. When prompted, enter your serial number or choose the Trial option.
  12. Run the Help menu command "Search for Flex Builder Updates." If you do not receive a message in return, then the Adobe Update Manager was not installed automatically on your system. Here’s how to remedy that:
    • In your installed Flex Builder 3 folder, run this file: \AMT\AdobeAUM5.1All.win.installer\Setup.exe

Install Flex Builder Standalone on Mac OS X

  1. Prior to installing, uninstall any prerelease versions of Flex Builder 3.
  2. Open or double-click the installer DMG file. The installer image will be mounted.
  3. Open or double-click the installer application to begin the Flex Builder installation process.
  4. Accept the license agreement and follow the prompts.
  5. By default, the debugging version of the Flash Player 9 browser plug-in is selected for installation.
    • The debugging version of Flash Player is Flash Player 9 (9.0.115.0)
    • This version is required for viewing and debugging applications developed with Adobe Flex Builder.
  6. (Optional) You can select the following to install:
    • ColdFusion Extensions for Flex Builder
    • JSEclipse - JavaScript plug-in (not available in Japanese)
  7. Follow the prompts to complete the installation.
  8. If you had previously installed Flex Builder 3 Beta, refer to the instructions in the section Clean and Reinitialize Cached Bundle Data.
  9. Review the Release Notes.
  10. To start Flex Builder, locate and double-click the executable file in /Applications/Adobe Flex Builder 3.
  11. When prompted, enter your serial number or choose the Trial option.
  12. Run the Help menu command "Search for Flex Builder Updates." If you do not receive a message in return, then the Adobe Update Manager was not installed automatically on your system. Here’s how to remedy that:
    • In your installed Flex Builder 3 folder, run this file: /AMT/AdobeAUM5.1All.win.installer/Setup.app

Install Flex Builder Plug-in on Windows

NOTE: Flex Builder is only supported on Eclipse 3.2.2 or Eclipse 3.3.

CAUTION: Do not install the plug-in version of Flex Builder 3 into a copy of Eclipse that is already hosting Flex Builder 2 plug-in. If you want to continue running Flex Builder 2 plug-in, download a new copy of Eclipse, and use that when installing Flex Builder 3 plug-in. In addition, be sure to use separate Eclipse workspaces for each installation of Flex Builder plug-in.

  1. Log in as the Windows Administrator or as a computer administrator (a user account with administrator privileges).

    Note: If you attempt to install without administrator privileges, the installation will complete with flagged issues. However, you will have installed an incomplete version of Flex Builder that you will not be able to run.

  2. Prior to installing, uninstall any prerelease versions of Flex Builder 3.
  3. Open or double-click the installer executable file. Accept the license agreement and follow the prompts.
  4. By default, the debugging version of the Flash Player 9 browser plug-in is selected for installation.
    • The debugging version of Flash Player is Flash Player 9 (9.0.115.0)
    • This version is required for viewing and debugging applications developed with Adobe Flex Builder.
    • You must select separate installs of the Flash Player plug-in for Internet Explorer and for Firefox and Netscape browsers.
  5. (Optional) You can select the following to install:
    • ColdFusion Extensions for Flex Builder
    • JSEclipse - JavaScript plug-in (not available in Japanese)
  6. Follow the prompts to complete the installation.
  7. If you had previously installed Flex Builder 3 Beta, refer to the instructions in the section Clean and Reinitialize Cached Bundle Data.
  8. Review the Release Notes.
  9. Start Flex Builder using its shortcut in the Start Menu under Adobe.

    (Windows Vista Only) The first time you run Flex Builder 3, you must "Run as Admin", after which you can run it normally.

    To run as Admin, right click the Adobe Flex Builder 3 Eclipse Launcher launch icon in the Start Menu, select "Run As," and then specify a user with administrator privileges.

  10. Select Window > Open Perspective > Other > Flex Development.
  11. When prompted, enter your serial number or choose the Trial option.
  12. Run the Help menu command "Search for Flex Builder Updates." If you do not receive a message in return, then the Adobe Update Manager was not installed automatically on your system. Here’s how to remedy that:
    • In your installed Flex Builder 3 folder, run this file: \AMT\AdobeAUM5.1All.win.installer\Setup.exe

NOTE: You must create a new workspace before beginning. Select File > Switch Workspace from the menu bar and enter a new directory name. If the directory does not exist, Eclipse creates it.

Install Flex Builder Plug-in on Mac OS X

NOTE: Builder is only supported on Eclipse 3.2.2, Eclipse 3.3 and Eclipse 3.4.

CAUTION:Do not install the plug-in version of Flex Builder 3 into a copy of Eclipse that is already hosting Flex Builder 2 plug-in. If you want to continue running Flex Builder 2 plug-in, download a new copy of Eclipse, and use that when installing Flex Builder 3 plug-in. In addition, be sure to use separate Eclipse workspaces for each installation of Flex Builder plug-in..

  1. Prior to installing, uninstall any prerelease versions of Flex Builder 3.
  2. Open or double-click the installer DMG file. The installer image will be mounted.
  3. Open or double-click the installer app to begin the Flex Builder installation process.
  4. When prompted select the existing Eclipse installation directory.
  5. Accept the license agreement and follow the prompts.
  6. By default, the debugging version of the Flash Player 9 browser plug-in is selected for installation.
    • The debugging version of Flash Player is Flash Player 9 (9.0.115.0)
    • This version is required for viewing and debugging applications developed with Adobe Flex Builder.
  7. (Optional) You can select the following to install:
    • ColdFusion Extensions for Flex Builder
    • JSEclipse - JavaScript plug-in (not available in Japanese)
  8. Follow the prompts to complete the installation.
  9. If you had previously installed Flex Builder 3 Beta, refer to the instructions in the section Clean and Reinitialize Cached Bundle Data.
  10. Review the Release Notes.
  11. To start Flex Builder, in the Finder window opened to your eclipse folder, run Eclipse. Then select Window > Open Perspective > Other > Flex Development.
  12. When prompted, enter your serial number or choose the Trial option.
  13. Run the Help menu command "Search for Flex Builder Updates." If you do not receive a message in return, then the Adobe Update Manager was not installed automatically on your system. Here’s how to remedy that:
    • In your installed Flex Builder 3 folder, run this file: /AMT/AdobeAUM5.1All.win.installer/Setup.app

NOTE: You must create a new workspace before beginning. Select File > Switch Workspace from the menu bar and enter a new folder name. If the folder doesn't exist, Eclipse creates it.

Clean and reinitialize cached bundle data (Beta customers)

When using Flex Builder 3 with a workspace from a Beta release, after installing the release version of Flex Builder 3, clean and reinitialize the workspace using the following platform-specific procedures (this operation does not remove or alter Eclipse projects residing the workspace in any way). In addition to cleaning the workspace, this operation also reinitializes any cached bundle data.

Windows:

  1. Go to install_drive\Program Files\Adobe\Flex Builder 3, or the root of the Eclipse install directory if using the Flex Builder Plug in
  2. Open FlexBuilder.ini or Eclipse.ini in a text editor
  3. Add the following to the top of the file (not the bottom) and save it.
    	-clean 
  4. Launch Flex Builder or Eclipse
  5. Remove -clean after exiting Flex Builder or Eclipse

OS X:

  1. Go to install_drive/Applications/Adobe Flex Builder 3, or the root of the Eclipse install directory if using the Flex Builder Plug in
  2. Right click on the Flex Builder application or Eclipse application and choose Show Package Contents
  3. Open Contents > MacOS
  4. Open FlexBuilder.ini or Eclipse.ini in a text editor
  5. Add the following to the top of the file (not the bottom) and save it.
    	-clean 
  6. Launch Flex Builder or Eclipse
  7. Remove -clean after exiting Flex Builder or Eclipse

Install and Configure Flex Automated Testing

To use Flex Automated Testing, you must install Flex Builder 3 Professional. You cannot use Flex Automated Testing with only the Flex 3 SDK. If you do not have a Flex Builder Professional license, your test scripts are limited to 30 actions. If you exceed 30 actions in a test without the Professional license, you will receive a warning that your license is not present.

Flex Automated Testing SWC files are installed by default with Flex Builder 3. They are located in the /frameworks/libs directory with the other SWC files. You can begin using Flex Automated Testing and build your own custom agents without any further installation.

To use run-time automated testing (recommended):

  1. Open a command prompt.
  2. Navigate to the flex_builder_root/sdks/3.0.0/templates/automation-runtimeloading-files directory.
  3. Execute the build.bat file. This compiles the runtimeloading.mxml file into a SWF file.
  4. Copy the runtimeloading.swf and RunTimeLoading.html file to your web server. Copy the Flex application that you want to test to this server as well (the application need not be compiled with automation libraries).
  5. Request the RunTimeLoading.html file and pass your Flex application as the automationswfurl query string parameter; for example:
    http://localhost/RunTimeLoading.html?automationswfurl=MyApp.swf

To compile your applications with static automation support:

  1. Start Flex Builder.
  2. Create a new Flex Project.
  3. Select your new Flex project in the Navigator.
  4. Select Project > Properties > Flex Compiler.
  5. In the "Additional compiler arguments" field, enter the following:
    -include-libraries "flex_builder_dir\sdks\3.0.0\frameworks\libs\automation.swc"
     "flex_builder_dir\sdks\3.0.0\frameworks\libs\automation_agent.swc"
     "flex_builder_dir\sdks\3.0.0\frameworks\libs\qtp.swc"
     "flex_builder_dir\sdks\3.0.0\frameworks\libs\automation_dmv.swc"

    The -include-libraries compiler option is relative to the Flex Builder installation directory; the default on Windows is "C:\Program Files\Adobe\Flex Builder 3\".

  6. Click the OK button to save your changes and OK to close the project Properties dialog box.
  7. Compile your Flex application.

    Examples and documentation for using custom agents can be found at Custom Agents

Flex 3 Plug-in for HP QuickTest Professional
To use Flex Automated Testing with the Flex 3 Plug-in for HP QuickTest Professional (formerly Mercury QuickTest Pro), you must perform additional steps. The rest of this section describes how to install and use the Flex 3 Plug-in for HP QuickTest Professional

Requirements for Using the QTP Plug-in
To test applications with Flex Automated Testing and the QTP agent, you must install the following:

  • Mercury QuickTest Professional 9.2 with Internet Explorer 6
  • HP (formerly Mercury) QuickTest Professional 9.5 with Internet Explorer 6 & Internet Explorer 7
  • Patch 1701 needs to be installed for Smart Identification support with Mercury QuickTest Professional 9.2
  • Mercury QuickTest Professional 9.2 is not supported with Internet Explorer 7
  • Adobe Flex 3 Plug-in for Mercury QuickTest Pro
  • Microsoft Internet Explorer, version 6 or later
  • Flash Player ActiveX control, version 9.0.28.0 or higher

Installing the Plug-in
This section describes the steps necessary for a QC testing professional to configure QTP to work with Flex applications. You must install QTP and the plug-in.

To install QTP:

  1. Install Flash Player 9 ActiveX control (9.0.28.0 or higher) for Microsoft Internet Explorer. This is currently the only supported browser/player.
  2. Install QTP 9.1 if you do not require support for Smart Identification. If you want to use Smart Identification, install QTP 9.2 and patch 1701. You must get QTP 9.1 from Mercury.
  3. If you are using Mercury QTP on Microsoft Windows Vista you need to turn off the User Account Control (UAC) feature. Instructions to turn off UAC are available here
  4. Restart your computer.

To install the Flex 3 Plug-in for Mercury QuickTest Pro:

  1. Run the flex_builder_root/Installers/QTP_Plugin_Installer.exe.
  2. Start QTP.
  3. Close QTP.

In addition to the plug-in's DLLs and XML files, the plug-in installer includes the following in the installation directory:

  • /demo — Contains a Flash movie that describes the basics of using the plug-in. Be sure to enable audio on your computer.
  • /Uninstall Adobe Flex 3 Plug-in for Mercury QuickTest Pro — Contains the uninstaller.

Using the Plug-in

  1. Start QTP again after installing the plug-in. The Add-in Manager lists the Flex plug-in.
  2. Select the Flex plug-in in the Add-in Manager.
  3. Select New > Test and click the Record button.

NOTE: Flex application testing with QTP currently supports only Microsoft Internet Explorer with the ActiveX Flash Player.

For more information on these tasks and using QTP to test Flex applications, see Testing with QTP.

For information on the operations and properties of Flex objects in QTP, see QTP Object Type Information.

Samples for Automated Testing
Sample custom agents are available at Custom Automation Agents.

An application ready for testing with QTP can be found at Flexstore AT. This sample can be used to test if the QTP plugin installation was successful.

An example for automating custom components can be found at Automating Custom Component.

Using automation with the Adobe Flex Component Kit for Flash CS3
You can create Flex controls, containers, skins, and other assets in Flash CS3 Professional, and then import those assets into your Flex application. When you want to automate an application that uses such assets, you must include the automation_flashflexkit.swc library.

If you are using run-time loading, re-compile the runtimeloading.swf file by using the build.bat file in flex_builder_root\sdks\3.0.0\templates\automation-runtimeloading-files\. The batch file includes the necessary libraries.

If you are compiling automation support into your application, add the automation_flashflexkit.swc to your include-libraries compiler option. This is in addition to the other automation SWC files. The SWC files are located in the flex_builder_root\sdks\3.0.0\frameworks\libs directory.

Uninstalling

The procedure for uninstalling Flex Builder standalone and Flex Builder plugin are the same.

Uninstall Flex Builder 3 on Windows:

  1. Select Start > Settings > Control Panel.
  2. Select Add or Remove Programs.
  3. Click the Adobe Flex Builder version to uninstall (Flex Builder, Flex Builder Plug-in only).
  4. Click the Uninstall button in the uninstaller dialog box.
  5. Click Done.

Uninstall Flex Builder 3on Mac OS X:

  1. Go to the flex_builder_root/Uninstall Adobe Flex Builder 3 folder.
  2. Double-click "Uninstall Adobe Flex Builder 3".
  3. Click the Uninstall button in the uninstaller dialog box.
  4. Click Done.

Uninstalling Flash Player
If you intend to debug your applications, use the debugger version of Flash Player that is included with either Flex Builder 3 or the Flex 3 SDK. If you are currently using a previously released Flash Player, you will need to uninstall that Player before installing the new debugger version of Flash Player.

Flash Player Uninstallation Instructions

  • If you are using Flex Builder 3, the installer tries to uninstall your old Player before installing the appropriate debug Player.

  • If you are using the Flex 3 SDK or did not install the new debug Flash Player when installing Flex Builder, use the following instructions:

Windows–Plugin-based browsers
Run the appropriate uninstaller available from this TechNote.

Macintosh
Run the appropriate uninstaller available from this TechNote.

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

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

RPM removal:

  • As root, enter in terminal:
    # rpm -e flash-plugin
  • Click Enter and follow the prompts.

Compatibility issues

Using Flex Builder with Adobe AIR – If you are using Flex Builder 3 with Adobe AIR, you may encounter issues not covered in these release notes. Please take time to review the AIR release notes.

Query Builder included in the ColdFusion Extensions for Flex Builder is not supported on the Mac OS X platform.

Flex Design Extensions for CS3 - Although the Flex Component Kit for Flash is localized in Japanese, the Flex Design Extensions for CS3 are not translated.

Flex Builder database wizards – With Flex Builder database wizards you can now generate sample code that will connect to your database tables through a server technology. Java 1.5 is required to use this feature. The currently-supported platforms are

  • Java using the LiveCycle Data Services 2.5 server
  • Java using REST (XML over HTTP) transport
  • PHP using REST (XML over HTTP) transport (only for MySQL)
  • ASP.NET (C# and VBScript) using Web Services (only for SQL Server)

To run the database wizard on a project, you must have previously set the server-side language when the project was initially created (on the first page of the project wizard).

To run the database wizard on Java projects, the Eclipse Web Tools Platform project (WTP) must have been installed prior to creating the project. (See FB-9324.)

Flash Player on Mac OS X – On Mac OS X, Flash Player now looks for the mm.cfg file in your home directory(~), generally, /Users/<username>. If one is not found, it looks for mm.cfg in /Library/Application Support/Macromedia. For previous versions of Flash Player, Flash Player ignored an mm.cfg file in your home directory /Users/<username>. For some users with an mm.cfg in their home directory, tracing to the flashlog.txt file will not work.

Flex 2 Charting – You must get a separate Flex 2 Charting serial number to use Flex 2 Charting components. If you have a licensed version of Flex 2 Charting and want to use those components in Flex Builder 3, then you must do the following:

  • Copy the following line (which contains your serial number) from your Flex 2 Charting license.properties file and paste it into the Flex Builder 3 license.properties file for the SDK 2.0.1, which is located at flex_builder_root/sdks/2.0.1/frameworks/license.properties.

    charting=serial_number
  • Select the SDK 2.0.1 in Flex Builder 3 by selecting Project > Properties > Flex Compiler. Select the Use a Specific SDK option, and select Flex 2.0.1 Hotfix 3 from the drop-down list.

Known issues

This section contains selected known issues. For a complete list of Flex Builder 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.

AIR

  • FB-11294  When signing AIR applications with a digital certificate, do not save the digital signature file (ends with .p12) inside the project's source folder or it will be embedded into the AIR app itself, which is a security risk.

ActionScript Editor

  • FB-10804 Organize Imports does not verify whether or not the file is writable.
  • FB-6060 if you auto-complete trace() it will add an import for trace which doesn't compile.
  • FB-12275 Toggle Block comment, Add CDATA Block menu items always inactive.

Installer / Licensing

  • FB-10052 Flex Builder does not run in 64-bit eclipse.
  • FB-9038 UNC homedrive and homepath leads to win install failure. Workaround: Use a local user account.

Design View and CSS Design View

  • FB-11252 A custom component with nothing but a constructor freezes Flex Builder in Design View. A workaround is to add a dummy updateDisplayList method that just calls the super method.
  • FB-11677 Hangs when dragging custom component from library into design view (Mac PowerPC only).
  • FB-7373 Type selector styles for custom MXML component in MXML do not render in DV.
  • FB-12041 OS X 104.x Only: When both Components Panel and Flex Properties view are undocked, FB hangs when dragging a component from Components panel to DV.

Profiler

  • SDK-9421, SDK-12655, and SDK-12638 In some cases the profiler may not show any back references for loitering objects. This happens mostly for non-heap objects, like String created during ABC decoding. To investigate loitering objects without back references, refer to the allocation trace, which must be enabled via the Launch Dialog.
  • SDK-13688 Performance Profiling is not supported on Mac PPC hardware.
  • SDK-11873 Zero time functions are very slow on OS X.

Project

  • FB-10212 No way to add an air project nature.
  • FB-11116 The Flex SDK version is set to "Use server's SDK" if you use a linked resource as the root folder.
    Workaround: Go to Flex Compiler property page and change the SDK used.
  • FB-11064 Pre-2.5 server project defaults to incompatible client SDK.
    Workaround: Go to Flex Compiler property page and change the SDK used.
  • FB-10826 Unable to specify a Content Folder that is more than one directory level deep.
  • FB-8947 Output folder URLs with file:////C: are not recognized as valid.
  • FB-5692 Flex Builder wraps Eclipse linked resource names in dollar curly brace, e.g. ${FOO}
    Workaround: Update the .setting files and flex build configuration for libraries, src, etc.
  • FB-11954 Imported Flex Project using LCDS incorrectly sets fds.swc location in build path
    Workaround: Go to project properties > Flex Build Path > Library Path and update the path to LCDSSERVERROOT\WEB-INF\flex\libs.
  • FB-12035 Run Project opens an invalid URL when used for imported projects. 
    Workaround: Edit the run configuration and enter the correct run/debug URL.

Refactoring

  • FB-12016 'null argument' error when refactoring class name that resides in a source path of a referenced library project
    Workaround: Refactor from the Library project.
  • FB-12007 when renaming a class by selecting constructor part at instantiation, tag version of the class instance doesn't get renamed.
  • FB-12004 Error dialog and log entry on rename of a type that is in a swc that has no src attachment.

Database Wizards

  • FB-12060 Db Wizard AIR generated descriptor is old (from M5) - There will be a Tech note on this
  • FB-11873 Deleting a data grid record that was selected for updating doesn't work when using a project with an ASP.NET server side.
  • FB-11935 For Flex Builder standalone, or for Flex Builder plugin on Eclipse 3.3, the database wizard requires JRE 1.5. This requirement does not exist for Flex Builder plugin on Eclipse 3.2.

Web Service Introspection

ColdFusion Extensions for Eclipse

  • FB-10914 Using the ColdFusion/Flex wizard with and existing Flex Project that uses Cold Fusion server overwrites the additional compiler arguments.
    Workaround: Change the additional compiler argument back to the one used before using the ColdFusion/Flex wizard.
  • FB-10913 Using the ColdFusion/Flex wizard with and existing Flex Project that uses Cold Fusion server changes the output folder.
    Workaround: Go to Project -> Properties -> Flex Build Path and set the output folder and the output folder URL.
  • FB-10907 Projects created with the ColdFusion/Flex wizard don't have server properties.
    Workaround: Use the Flex project wizard to create a CF project using as a default location a folder on your Web Root and then use the ColdFusion/Flex wizard, selecting on the last step to use the existing flex project.
  • FB-9616 Exception when closing Flex Builder after using CF RDS.
  • FB-9888 Cannot install ColdFusion Flex Builder Extension into BEA 10.2.
  • FB-14176 "Unable to un-install extensions(CF /JSEclipse), which are installed through FlexBuilder3.0.2 plug-in on Eclipse3.4." These extensions can be un-installed if they installed directly on Eclipse3.4.
  • CF 71293 Data intermittently fails to display in forms generated by the ColdFusion/Flex wizard.
    Work around: Close the detail form and open it again.
  • CF 73118 - Services Browser: When User tries to browse methods and parameters in CFCs/wsdls in Services Browser, it indefinitely shows "Contacting Server." Workaround: User has to browse those cfcs or wsdls through browser to view the
  • CF 73013 - RDS File View/RDS Data View: Expanding RDS Data View/RDS File view shows "Contacting server."
  • Workaround : Right click on RDS Server and hit "Refresh RDS Server."

Flex Skin Design Extensions for CS

  • FB-11003 Photoshop Skinning Extension: Only individual layers are exported, causing problems for nested layers

Japanese Flex Builder

  • FB-6026 Double-byte workspace name gets corrupted on Macintosh, causing Run/Debug to fail. Components icons are not displayed correctly.
  • FB-11057 Flex Builder cannot be uninstalled in English locale if it was originally installed in Japanese locale on double-byte path.
  • FB-10411 Cannot create Output folder with double-byte name on Macintosh.
  • FB-10021 Duplicate folder with a corrupted name is created if Workspace folder name contains double-byte characters with diacritics on Macintosh.
  • FB-10124 Flex Builder crashes when installed on a path containing certain double-byte character on Windows.
  • FB-10088 Flex Skin Design Extensions for Illustrator and Photoshop do not function with CS3 Japanese Edition
  • FB-11891 JA install automatically installs JSEclipse Help entry even if you didn't specify to install JSEclipse extension.
  • FB-10031 JSEclipse not supported on the Japanese version.
  • FB-11947 JA - Help: Rollover text over image are mojibake.
  • FB-11914 JA - dynamic and related help docs are in English.
  • FB-12078 JA: the text in the license dialog after entering standard serial is still in English.
  • FB-13556 JA All the components except for “custom” do not show up in the components panel when Flex Builder is installed on a 2byte path on Macintosh.

Data Management and Visualization issues

Advanced DataGrid

  • FLEXDMV-1449 Setting a custom sort renderer at runtime does not work.
  • FLEXDMV-1438 Vertically scrolling while doing multiple cell selection does not work properly.
  • FLEXDMV-1117 ADG Summary Rows may move to the top when a column is sorted.
  • FLEXDMV-1417 Setting sortExpertMode of PADG does not render the sort display properly.
  • FLEXDMV-1382 Sort indication shown in sort icon area is incorrect when user wants to change the sort. order (ascending/decending) on already sorted column.
  • FLEXDMV-1347 MXML completion does not take DefaultProperty into account.
  • FLEXDMV-1171 Cell highlight incorrect on keyboard navigation using ENTER key.
  • FLEXDMV-784 Drag and drop non functional when selectionMode="multipleCells".
  • FLEXDMV-1300 Flex Builder Design View goes blank after refresh when an AdvancedDataGrid with "groupedColumns" is used.

Flex Builder Professional, Automated Testing

  • FLEXENT-841 : automation_flashflexkit.swc missing

Getting Started

 

Application Development

 

Security

 

Downloads

 

Documentation

 

Community Resources