Archive for June, 2010

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 adobe.com.
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.

Macintosh
Run the appropriate uninstaller available from this Tech Note.

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

Delete the libflashplayer.so 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.

http://bugs.adobe.com/jira/browse/SDK-17285 – 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).””

http://bugs.adobe.com/jira/browse/SDK-20140 – item renderer selection gets out of sync when transitions are used
http://bugs.adobe.com/jira/browse/SDK-20270 – 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.
http://bugs.adobe.com/jira/browse/SDK-20880 – Masking a UIComponent is not currently supported
http://bugs.adobe.com/jira/browse/SDK-20944 – spark.components.VideoPlayer – Removing VideoPlayer While Playing Doesn’t Remove Audio
http://bugs.adobe.com/jira/browse/SDK-23050 – backgroundImage is not supported with Spark skins theme
http://bugs.adobe.com/jira/browse/SDK-23154 – 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.
http://bugs.adobe.com/jira/browse/SDK-23416 – 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())}”
http://bugs.adobe.com/jira/browse/SDK-23452 – Tooltips cannot display 4-byte characters on Windows.
http://bugs.adobe.com/jira/browse/SDK-23911 – Sorting or dragging/dropping of pending or failed items isn’t supported.
http://bugs.adobe.com/jira/browse/SDK-24055 – When Alert is used in a module but not defined in the main app, current moduleFactory should be passed to Alert.show() so Alert can pick up styles correctly.
http://bugs.adobe.com/jira/browse/SDK-24060 – 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.
http://bugs.adobe.com/jira/browse/SDK-25270 – AddAction/RemoveAction interferes with DisplayObject sharing
http://bugs.adobe.com/jira/browse/SDK-25302 – VideoPlayer unable to load Amazon Cloudfront videos
http://bugs.adobe.com/jira/browse/SDK-25513 – 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.
http://bugs.adobe.com/jira/browse/SDK-25618 – 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;
}
http://bugs.adobe.com/jira/browse/SDK-25521 – List doesn’t respect its Layout’s typicalLayoutElement
http://bugs.adobe.com/jira/browse/SDK-25412 – 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.
http://bugs.adobe.com/jira/browse/SDK-25419 – List renderer transitions get stuck when allowMultipleSelection is true
http://bugs.adobe.com/jira/browse/SDK-25358 – Elements with a 3D rotation inside a Scroller are affected by the scrollbars of sibling elements
http://bugs.adobe.com/jira/browse/SDK-25480 – Rotate3D can cause elements to not be clickable when they have a non-zero z value
http://bugs.adobe.com/jira/browse/SDK-25231 – Spark MXDataGridItemRenderer leaks content outside of its bounds
http://bugs.adobe.com/jira/browse/SDK-25773 – The ant script to build themes requires a compc.jvm.args parameter. Workaround: Pass in compc.jvm.args:

ant -Dcompc.jvm.args=-Xmx512m
http://bugs.adobe.com/jira/browse/SDK-25781 – 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.*”;
mxair|StatusBar
{
textFieldClass: ClassReference(“mx.core.UIFTETextField”);
}

mxair|TitleBar
{
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
English
French
German
Japanese
Russian

Flash Builder 4.0 Release Notes

Welcome to Adobe® Flash® Builder™ 4. This document contains late-breaking product information, updates, and troubleshooting tips not covered in the Flash Builder 4 documentation.

Minimum system requirements

What’s included

Install your software

Uninstall your software

Trial software

Electronic licensing

Registration information

Known issues

Customer care

Other resources

Minimum system requirements

For the latest system requirements, please visit www.adobe.com/go/flashbuilder4_systemreqs

What’s included

DVD:

The Flash Builder 4 DVD includes the following:

Flash Builder 4 Standalone install folder
Flash Builder 4 Eclipse Plug-in install folder
Extras folder that includes: *
LiveCycle Data Services 3.0 installer
Adobe Application Modeling Plug-in for Eclipse 3.4
Adobe Application Modeling Plug-in for Eclipse 3.5
LiveCycle Service Discovery Plug-in for Flash Builder 4.0
Flex 4 Test Automation Plug-in **
Flash Builder 4 Readme
* The contents of the Extras folder is not included in the Electronic Software Distribution (ESD) download.

** Not included in the Electronic Software Distribution (ESD) download, but available as a separate download at www.adobe.com/go/flex_plugin

Install your software

1. Before you install, quit all browsers and close all applications currently running on your system–including other Adobe applications, chat applications and Microsoft Office applications. It is also recommended to temporarily turn off virus protection during the installation process. Uninstall any previously installed versions of Flash Builder 4.

2. You must have administrative privileges or be able to validate as an administrator.

3. Do one of the following:

Install Flash Builder 4 Standalone on Windows:

a. 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 Flash Builder that you will not be able to run.

b. Prior to installing, uninstall any prerelease versions of Flash Builder 4.

c. Insert the DVD in your drive, and follow the on-screen instructions. If the installer does not launch automatically, navigate to the Adobe Flash Builder 4 Standalone folder found at the root level on the DVD and double-click Set-up.exe to start the installation process.

If you downloaded the software from the web, the installer will self-extract after the folder to copy the installer is selected and launch automatically. If the installer does not launch automatically, open the folder, navigate to the Adobe Flash Builder 4 Installer folder, double-click Set-up.exe, and then follow the on-screen instructions.

d. Accept the user license agreement. When prompted, enter your serial number or choose the trial option. Select a language if not selected.

e. If you are installing as an upgrade, the installer will check your system to find the valid upgrade product. If it cannot find it, it will ask you to input the serial number of the product being upgraded. You can also install the software in trial, then input your new and previous serial numbers in the serialization screen shown during launch.

Install Flash Builder 4 Plug-in on Windows:

NOTE: Flash Builder 4 is only supported on Eclipse 3.4 or higher.

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

a. 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 Flash Builder that you will not be able to run.

b. Prior to installing, uninstall any prerelease versions of Adobe Flash Builder 4 Eclipse Plug-in.

c. Insert the DVD in your drive, and follow the on-screen instructions. If the installer does not launch automatically, navigate to the Adobe Flash Builder 4 Eclipse Plug-in folder found at the root level on the DVD and double-click InstallFlashBuilder4Plugin.bat to start the installation process.

If you downloaded the software from the web, the installer will self-extract after the folder to copy the installer is selected and launch automatically. If the installer does not launch automatically, open the folder, navigate to the Adobe Flash Builder 4 Plugin Installer folder, double-click InstallFlashBuilder4Plugin.bat, and then follow the on-screen instructions.

d. Accept the license agreement and follow the prompts.

e. If you are installing as an upgrade, the installer will check your system to find the valid upgrade product. If it cannot find it, it will ask you to input the serial number of the product being upgraded. You can also install the software in trial, then input your new and previous serial numbers in the serialization screen shown during launch.

Install Flash Builder 4 Standalone on Mac:

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

b. Prior to installing, uninstall any prerelease versions of Flash Builder 4.

c. Insert the DVD in your drive, and follow the on-screen instructions. If the installer does not launch automatically, navigate to the Adobe Flash Builder 4 Standalone folder found at the root level on the DVD and double-click Install.app to start the installation process.
If you downloaded the software from the web, open the folder, navigate to the application folder, double-click Install.app, and then follow the on-screen instructions.

d. Accept the license agreement and follow the prompts.

e. If you are installing as an upgrade, the installer will check your system to find the valid upgrade product. If it cannot find it, it will ask you to input the serial number of the product being upgraded. You can also install the software in trial, then input your new and previous serial numbers in the serialization screen shown during launch.

Install Flash Builder 4 Plug-in on Mac:

NOTE: Flash Builder 4 is only supported on Eclipse 3.4 or higher.

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

a. Log in as the 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 Flash Builder that you will not be able to run.

b. Prior to installing, uninstall any prerelease versions of Adobe Flash Builder 4 Eclipse Plug-in.

c. Insert the DVD in your drive, and follow the on-screen instructions. If the installer does not launch automatically, navigate to the Adobe Flash Builder 4 Eclipse Plug-in folder found at the root level on the DVD and double-click FB4_Plugin_Mac_Installer app to start the installation process.

If you downloaded the software from the web, open the folder, navigate to the Adobe Flash Builder 4 Plugin Installer folder, double-click FB4_Plugin_Mac_Installer app, and then follow the on-screen instructions.

d. Accept the license agreement and follow the prompts.

e. If you are installing as an upgrade, the installer will check your system to find the valid upgrade product. If it cannot find it, it will ask you to input the serial number of the product being upgraded. You can also install the software in trial, then input your new and previous serial numbers in the serialization screen shown during launch.

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.

4. For detailed installation instructions for Flex 4 Automation Plug-in, go to www.adobe.com/go/flex_plugin

Note: In order to install additional components or reinstall your software after your original installation, you will need access to the original installer (CD, DVD or the download from the web). Repair is not an available option.

Uninstall your software

Before you uninstall, quit all browsers and close all applications currently running on your system–including other Adobe applications, chat applications and Microsoft Office applications.

In Windows XP, open the Windows Control Panel and double-click Add or Remove Programs. Select the product that you want to uninstall, click Change/Remove, and then follow the on-screen instructions.
In Windows Vista and Windows 7, open the Windows Control Panel and double-click Programs and Features. Select the product that you want to uninstall, click Uninstall, and then follow the on-screen instructions.
IMPORTANT: Mac OS has new uninstall functionality. DO NOT drag applications to the trash to uninstall them. To safely uninstall on Mac OS X, double-click on the Uninstall alias located in the Application folder. Select Remove Preferences, then Authenticate as an administrator and follow the on-screen instructions.
Note: If you want to install the product on a different computer, you must first deactivate the software on your computer. To deactivate, choose Help > Deactivate Flash Builder.

Trial software
Entering a serial number

Enter the serial number for the software you purchased in the serialization screen. The serialization screen will load the first time you launch the application (if using the Adobe Flash Builder 4 Eclipse Plugin, it may take more than one launch for the serialization screen to appear).

Only applications running as a trial will recognize the new serial number. If any of the applications have already been serialized with a different serial number, it will continue to use that serial number until you remove the older serial number using the Help > Deactivate Flash Builder. Then on the next launch of the application, it will recognize the new serial number.

Volume licensing

Volume licensing customers cannot purchase from a trial directly. Please contact your reseller or authorized Adobe licensing center to place an order for a volume license. To find a reseller in your area, go to http://partners.adobe.com/resellerfinder/na/reseller.jsp.

Electronic licensing
You must accept the license agreement and warranty terms to use this product. See www.adobe.com/go/eulas for details. This product may automatically attempt to activate over the Internet. See www.adobe.com/go/activation for details.

Registration information

Creating an Adobe ID registers your software. Please register to get up-to-date product information, training, newsletters, and invitations to Adobe events and seminars.

Known issues

Please refer to http://www.adobe.com/go/flex4_sdk_releasenotes for Flex 4 SDK known issues

AIR: Project
FB-25251 Can’t install AIR file exported from Builder – “Air file is damaged” error when previous version of AIR application is installed

Workaround: Uninstall previous version of the AIR application

ASDebugger

FB-25724 Installed Adobe Flash Player Is Not a Debugger when Flash Pro CS5 is installed and using the standalone player (no HTML wrapper)

Workaround:Uninstall your current Flash Player and run the debugger player installer found atINSTALL_DIRECTORY/players/. For the standalone Flash Player, launch the Stand Alone Flash Player found in INSTALL_DIRECTORY/players/ and open a swf to re-associate that version of the standalone Player

FB-24607 When debugging in Internet Explorer 8 on Windows 7, Internet Explorer may display a dialog when your Flash application has halted at a breakpoint. This is caused by the fact that Internet Explorer thinks the Flash Player is hung, when in fact the Flash Player is simply waiting for a message from the Flash Builder debugger.

Workaround: You can disable this Internet Explorer warning by making a change to the Windows registry. (Note, this change will affect all Internet Explorer windows, not just ones being used to debug Flash Builder applications.)

– Run regedit.exe

– Navigate to the following registry key: HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main

– Edit > New > DWORD (32-bit) Value

– For the name of the new value, type “HangResistance”

– The value in the right-hand column will show up as zero; leave it with that value.

FB‐16779 Flash Player error may occur when debugging in Google Chrome. If you want to debug your Flash applications in the Chrome browser, Chrome may see the following message when you are halted at a breakpoint in the Flash Builder debugger:
The following plug-in is unresponsive: Shockwave Flash
Would you like to stop it?
It is normal for the Flash Player plug-in to be unresponsive when you are at a breakpoint. To prevent Chrome from displaying this message, modify the shortcut that you use to Chrome. In Windows, right-click on the shortcut and choose Properties. Go to the Shortcut tab, and append “–disable-hang-monitor” to the “Target:” field.

ASDoc – Display

FB-25623 No ASDoc for unsupported locales in plug in build using non bundled eclipse distros

Adobe Community Help

FB-26153 Context-sensitive help for ActionScript Language Reference is not displayed on first invocation. Workaround: Windows: Select Adobe Community Help > Edit > Preferences. Then select Local Content > ActionScript 3.0 Reference and click the update button. OS X: Launch Adobe Help > Preferences. Then select Local Content > ActionScript 3.0 Reference and click the update button.

Compiler

FB-26001 /SDK-25513 Incremental compiler fails to pick up metadata changes. Fix is scheduled for SDK 4.1. Workaround: Perform a full compile.

SDK-25619 Embedding font in a library throws compile time error. Fix is scheduled for SDK 4.1.

FB-25787 Cannot use the -static-rsls option in “Additional compiler arguments” input

Workaround:In the project’s properties dialog, go to “Flex Build Path” and choose “Merged into code”.

FB-24955 Compile error when a package named ‘style’ contains a CSS file that’s referenced by an MXML file in the same package as CSS

Workaround:Rename the the ‘style’ sub-package to something else, and there’s no error.

Installer

FB-21960 FB Plug-in doesn’t launch on certain machines

Workaround: in eclipse.ini file, change the memory allocation to;

-Xms80m

-Xmx256m

FB-26159 Uninstalling ColdFusion Builder deletes the Flash Builder RDS plugin. Workaround: Close ColdFusion Builder perspectives prior to uninstall or reinstall Flash Builder.

FB-26047 unable to install FB Plug-in into external eclipse 3.4.2 when language pack is not installed (Japanese Only)

Workaround: Install the Japanese Eclipse language pack.

FB-15844 FB Plug-in not supported on eclipse3.5 cocoa on mac

FB-25217 Flash Builder installation not supported on Windows OSs where the user name has 4-byte characters.

Project Definition

FB-12261 project that contains modules, and uses -resource-bundle-list compiler option do not list any bundle names derived from [ResourceBundle()] metadata tag

Workaround: if you build large project with many modules, edit the .actionScriptProperties file and comment the modules, build the to generate the bundles.txt. copy the bundles.txt to other location and uncomment the modules to compile the whole project without overwriting the bundles.txt. Everytime you add resourcebundle, you have to repeat this process

Project: Import/Export

FB-26119 FXP import does not update source path when using linked folders

Workaround:Fix .actionScriptProperties file manually or re-add the source path in the project properties UI. For a consumer of a new FXPL, this isn’t obvious.

Refactoring

FB-25769 ASDoc is not updated when using refactor>rename and rename textual matches is checked

Miscellaneous

FB-11184 If you experience crashes while embedding fonts in CSS design view, then try embedding the font using a URL to the ttf file instead of using the system font name.

FB-23727Flash Builder intermittently hangs while opening projects.

Workaround:

Exit Flash Builder
Edit INSTALL_DIRECTORY/plugins/com.adobe.flexide.editorcore_4.0.0.272416/.options
Set the value of com.adobe.flexide.editorcore/registerCodeModelProjectsAsynchronously to true
Re-launch Flash Builder
FB-23023 Line numbers wont scroll along with the rest of the text and breakpoints etc wont show up in the AS editor if on secondary screen

Workaround:Update and patch information here http://blogs.adobe.com/jasonsj/2010/02/patch_for_snow_leopard_line_number_scrolling_bug.html.

Eclipse Update Site Mechanism (P2)

In order to install additional plug ins on OS X and Windows XP, you need to be logged in to a user account with Administrator privileges.
In order to install additional plug ins on Windows Vista and Windows 7, you must launch Flash Builder via the “Run as Administrator” context menu option and authenticate if prompted
If you are installing ColdFusion Builder or the LCDS Modeler plug ins, you will need to run Flash Builder once using a user account that is in the Administrator group on OS X or XP or with “Run As Administrator” on Windows Vista and Windows 7.

Flex Unit

FB-25586 FlexUnit fails to compile if locale is not support by Flex SDKWorkaround:Set the -locale to en_US

Network Monitor

FB-23419Suspend on startup will not suspend the network calls

FB-25589 Network monitor on – not able to make requests

Profiler

FB-23384Loitering Objects Show Zero Object References

FB-23543Safari browser crashes running profiler for the second time

FB-24111 Flash Builder Profiler doesn’t report all methods for Spark components

FB-24109 Flash Builder Profiler doesn’t report all objects for Spark components

FB-25184 Profiler does not show back references in AIR

Third Party IDE Compatibility

FB-19703 Unable to install Flash Builder plug-in properly into Zend Studio 6.1.2 standalone. The recommended workaround is to install the Flash Builder plug-in into the All-In-One Eclipse PDT + Zend Debugger Plug-in (http://www.zend.com/en/community/pdt). An alternate workaround (not recommended) is to rename the “dropins” folder to “links” and restart Zend.

DCD: LCDS

FB-22755 Cannot use update method which has changes – public void updatePerson3Params(Person person, Person prev, ArrayList changes)

DCD: PHP Introspector

FB‐19657 optional arguments not displayed after introspection

FB-19046 PHP Introspector can fail when authentication is enabled on the web server (like IIS)

DCD: Configure Return Type

FB-22805 Auto guess not working when service is created using Generate a Sample link

FB-24640 : [WSDL] Configure Return Type and Test Operation for WebServices is not allowing Date input format

Flex Automation

FLEXENT-792: Very low level of control on the pointing hand movements if you use object spy and move over Flex components in an Air application.

DCD: Service Wizard

FB-24162: [SDK][Dependent][Static XML] RTE occurs as auto CRT incorrectly parses xmls with empty data type

GB18030 support for Windows XP

In order to support the display of all characters of the Chinese standard GB18030 on Windows XP systems, Adobe recommends the installation of the Microsoft GB18030 Support Package. This support package will update an XP system with, among other things, fonts and input-method-editors (IMEs) to correctly support GB18030. The support package is available as a download from the Microsoft website.

Customer care
Customer Service

Adobe Customer Service provides assistance with product information, sales, registration, and other non-technical issues. To find out how to contact Adobe Customer Service, please visit Adobe.com for your region or country and click on Contact.

Support Plan Options and Technical Resources

If you require technical assistance for your product, including information on complimentary and fee-based support plans and troubleshooting resources, more information is available at http://www.adobe.com/go/support/. Outside of North America, go to http://www.adobe.com/go/intlsupport/ click on the drop down menu under the question “Need a different country or region?”, choose a different country or region, then click GO. Alternatively, you can click on Change beside the country name at the top of the screen to select a different country or region.

Free troubleshooting resources include Adobe’s support knowledgebase, Adobe user-to-user forums, Adobe Support Advisor and more. We are continually making additional tools and information available online in order to provide you with flexible options for resolving issues as fast as possible.

Other resources

Online Resources

For complete Help plus community-based instruction, inspiration, and support, go to www.adobe.com/go/learn_Flex_support_en

Adobe Flash Builder Product Information

Flex Developer Center

Flex Developer Center Documentation

Free Flex-in-a-Week training

Tour de Flex – Sample code and Examples for Flex

3rd Party Products and Projects supporting Flex

Adobe TV

Flex User Forums

Adobe User Groups

Adobe Marketplace and Exchange

Training

Adobe Certification Program

Adobe Partner Programs

Find an Adobe Authorized Training Center

© 2010 Adobe Systems Incorporated. All rights reserved.

FB license upgrade related issues

  • Educational Edition of Flex Builder 2, and that edition does not qualify for upgrade to any edition of Flex Builder 3
  • http://kb2.adobe.com/cps/403/kb403219.html

  • Upgrade from Flex Builder 3 to Flash Builder 4
  • http://www.adobe.com/products/flex/buy/

    Notes about caching

    1. caching to the disk is controlled by browser, not by flex/flash. The browser cache can be saved to the disk, flash player cache will only be in the memory.
    2. By default, browsers can cache content over http ( if you didn’t set no-store no-cache in the header ).
    http://stackoverflow.com/questions/174348/will-web-browsers-cache-content-over-https
    3. However, browsers may not cache content to disk over https by default and you need to configure it.
    For IE, you can turn on the feature by change setting at:
    Tools > Internet Options > Advanced tab > Security section > Do not save encrypted pages to disk
    For Firefox, see details in
    http://blogs.atlassian.com/developer/2007/07/when_caching_is_not_caching.html
    4. Only signed RSLs can be stored in the player cache, unsigned will be in browser cache. Only Adobe can create signed RSLs. If you create an RSL that contains a customer library, it will be unsigned, so can’t be in player cache. There is no workaround for this at the moment. Your option is to use unsigned with browser’s cache.
    5. If your app get an connect problem over the first request, but works fine after a refresh, that usually is caused by the content cache over https issue. See above for how to correct it.

    Adobe LiveCycle Data Services ES2 Version 3.1 Release Notes

    Contents
    What’s new
    Known issues and API changes
    Fixed issues

    What’s new
    LiveCycle Data Services 3.1 offers these new features and improvements:

    Alignment with Flex 4 and Flash Builder 4
    The LiveCycle Data Services 3.1 supports the released versions of Flex 4 and Flash Builder 4.

    Extensibility and increased flexibility for model-driven development
    The ability to generate and customize model-driven application code is much improved in LiveCycle Data Services 3.1. In addition to generating and customizing client-side ActionScript code and model-driven forms, you can generate and customize server-side Java code. You can also extract and customize the code generation templates for the generated client-side and server-side code.

    The Modeler provides new user interface features for code generation. You can choose the types of code to generate, which code generation templates to extract, and where to save the generated code and templates.

    For more information, see “Model-driven applications” in Using LiveCycle Data Services.

    Improved offline data management support
    LiveCycle Data Services 3.1 provides major improvements in offline data management support, including:

    Offline queries using SQLite in AIR clients
    Encryption of local data in SQLite
    Model-driven development of offline applications
    For more information, see “Occasionally connected clients” and “Model-driven applications” in Using LiveCycle Data Services.

    Wider platform support
    LiveCycle Data Services 3.1 provides support for additional platforms. For more information, see the LiveCycle Data Services product page on the Adobe website.

    Many fixed issues
    About half of the LiveCycle Data Services 3.1 development resources went into fixing bugs and usability issues. See Fixed issues for details.

    Known issues and API changes
    If you encounter a Hibernate version conflict, you must configure the application server to load the Hibernate classes included with LiveCycle Data Services in the WEB-INF/lib/hibernate*.jar files of the lcds web application.
    BLZ-494 – If client is subscribed to multiple destinations over a single polling endpoint and one subscription is invalidated, polling stops.

    Data Management Service: The fix for LCDS-876 required a public Java API change. The DataMessage.setUpdateBody method has been renamed as DataMessage.modifyUpdateMessageBody.

    FBR-134 – Model-driven development: Using the same entity backed by the same database table in multiple models is not supported.

    FBR-317 – Model deployment: When deploying a model to the Model Assembler, you cannot have a an entity property named “id” that is not an identity property. This is due to a bug in the Hibernate libraries used in the Model Assembler persistence layer.

    FBR-383 – Model-driven development: When working with RDS, certain types of action queries such as UPDATES or DELETES that result in 0 row counts and upon being successful cause RDS to throw this “RDS: java.sql.SQLException: General error resultset closed”. This should be ignored. Also, all DDL statements cause this (for example, ALTER TABLE, etc.). Depending on the database driver used, you may not be allowed to execute queries. Again, the exception may be ignored and the statement will execute.

    LCDS-864 – Model Assembler: After an authorization failure, local data change (delete) doesn’t roll back if there is only one item in the collection.

    LCDS-895 – Modeler: The Modeler does not preserve comments.

    LCDS-907 – Modeler: Invalid entity creation: same table defined in multiple schemas creates duplicate fields in entity model.

    LCDS-1022 – Model-driven development: Deleting an entity from a model does not delete its classes from its package.

    LCDS-1076 – Modeler Expression Builder: Cannot use “up” and “down” keyboard arrow keys to scroll through the list of functions or the function categories.

    LCDS-1103 – Model-driven form: Adding a model-driven form in Flash Builder design mode takes a long time and causes a flicker. This does not occur when using a Flex form, or if either type of form is added in source mode.

    LCDS-1113 – Model-driven development: Import incorrect package for service when entity package and service package are different.

    LCDS-1119 – Model-driven form: Using multiple model-driven forms in same application results in issues with unexpected interactions between the forms.

    LCDS-1187 – Data Management Service: Data Management samples use a deprecated API. New versions of fill methods on the Assembler interface methods take a propertySpecifier as an argument, but the samples and a code sample in the documentation use a deprecated fill method defined on the AbstractAssembler class, which does not take a propertySpecifier as an argument: public Collection fill(List fillParameters).

    LCDS-1445 – Model-driven form: Model-driven form created against an entity with a datatype column of type float causes rounding of that type based on the numericStepper’s stepValue.

    LCDS-1488 – Sample applications: The HTTPService sample in the LiveCycle Data Services samples application is not working on JBoss 5.0.

    LCDS-1522 – The HTTP channels (HTTPChannel and SecureHTTPChannel) are not compatible with the small messages feature. For this reason we attempt to automatically disable small messages when the HTTP channels are being used. Due to this bug, there are some instances where small messages are not automatically disabled when using the HTTP channels and you could get errors unless you explicitly disable them. For this reason, when using an HTTP channel in your application you should explicitly disable small messages on your HTTP endpoint in the services-config.xml file.

    LCDS-1533 – Edge Server: When using the Edge server to communicate with a JMS messaging destination in the application tier, if there is a problem on the JMS end such as the destination can’t be found in JNDI, the error is not making it back to the client and the client could go into an endless reconnect loop. This would likely only occur due to a development or deployment time configuration problem but it is good to be aware of this issue if you are having problems using a JMS messaging destination through the Edge Server as it could make the underlying configuration issue more difficult to identify.

    LCDS-1537 – Modeler: The Generate Code button in the Modeler generates code based on the saved model, not the in memory (possibly modified) model. It needs to prompt for save before running.

    LCDS-1540 – Model-driven development: No error when table creation fails on deploy due to JDBC driver fail to load. RDS view does show an error for same issue.

    LCDS-1564 – Client-side data management: autocommit doesn’t work properly when the entity has a complex key with an association.

    LCDS-1574 – Model-driven development: Using a DB2 database, the CLOB type length is limited to 255 when the column is created through model deployment. This is a bug in Hibernate. The workaround is to create the database table manually. See the following page for more information:

    http://opensource.atlassian.com/projects/hibernate/browse/HHH-2969

    LCDS-1578 – A null pointer exception can be thrown if there is a transient connection failure when using RTMP with LiveCycle Data Services in developer mode.
    Fixed issues
    BLZ-495 – HTTP channel failed to deserialize Externalizable(ArrayCollection) body in AsyncMessage.
    BLZ-488 – ClassCastException when deploying an application in a cluster.
    BLZ-487 – MessagingConfiguration doesn’t set JMX manageable property until after it is constructed.

    BLZ-486 – Streaming HTTP endpoint not working on Safari on Mac.

    BLZ-479 – Only one consumer gets the message from the same client when multiple consumers subscribe to the same messaging destination.

    BLZ-476 -Get different error message in server’s servlet log and console log when a class is not of the expected type.

    BLZ-475 – Changes to MessageService.java class introduced NullPointer exception when using a MultiTopicProducer component .

    BLZ-459 – With create-asobject-for-missing-type set to true on a channel, when you get the type for the created ASObject from the missing type, it returns null.

    BLZ-455 – Document client-load-balancing property in the sample configuration.

    BLZ-452 – AMFConnection does not work against NIO-based endpoints.

    BLZ-447 – AMF3 deserialization: Wrongly counted reference ID of duplicated String when there are Strings with only wildcards in the same message .

    BLZ-428 – Pinging a LiveCycle Data Services endpoint returns HTTP: Status 200 in Internet Explorer 8.

    BLZ-427 – Add configuration option for the BeanProxy.includeReadOnly property.

    BLZ-387 – BlazeDS server hangs during server push.

    BLZ-366 – Get channel fault when there is a transient disconnect on a streaming channel.

    LCDS-1568 – A derived property with a type of boolean or Entity causes a compilation error in the model-driven form.

    LCDS-1547 – Model-driven development: RDS database connection fails to Weblogic 10.3 and 11.

    LCDS-1544 – Model-driven form: Improper activation of Delete button during update.

    LCDS-1530 – Modeler: New entity creation behaves differently using right mouse click context menu versus dragging new entity from palette.

    LCDS-1527 – Modeler Properties view: Edit Annotations dialog from entity, property, and so forth does not let you delete items or values.

    LCDS-1525 – Modeler Properties view: Pressing the Edit Annotations button on the Properties view Inline General tab does nothing.

    LCDS-1524 – Modeler: Modeler does not appear to hit the 2 classes in com.adobe.model.derived.editor.gef.tools.

    LCDS-1517 – Model-driven form: Validation error for multiple rows causes multiple messages in toolbar tip.

    LCDS-1513 – Model-driven development: It is not possible to create a string with indefinite length using modeling.

    LCDS-1512 – Model-driven development: DataManagement model annotation validation gives CRUD duplication error.

    LCDS-1510 – Model-driven development: Null pointer exception error dialog when downloading DDL.

    LCDS-1508 – A call to releaseCollection() does not release the collection from management. Uncommitted changes are not released.

    LCDS-1506 – Model-driven development: Auto-generated checkbox shouldn’t be enabled for id properties of complex types.

    LCDS-1504 – Model-driven development: While specifying the ORDER By clause when creating a filter, if we do not specify ASC or DESC then Flash builder reports it as an issue. This should not be the case as the default behavior is ASC.

    LCDS-1500 – Model-driven development: RDS – cannot connect to Oracle 10 or 11 using ojdbc6.jar in RDS view.

    LCDS-1498 – Modeler Properties view: Change event of General tab property type dropdown does not execute when new or existing property edited as propertyname:type.

    LCDS-1497 – Data Management Service is out of sync and becomes unreliable after DataServiceTransaction.refreshFill() call.

    LCDS-1490 – Client-side data management: Generated DataManager has multiple unnecessary _initRemoteClassAlias() calls.

    LCDS-1489 – Model-driven development: Dragging a table from a different datasource overwrites the existing Hibernate dialect, but not the existing datasource.

    LCDS-1485 – Model-driven development: Dragging a table from a different datasource into a model with existing datasource may confuse users.

    LCDS-1484 – Model-driven development: Dragging a datasource from RDS Dataview into the model pane in design mode doesn’t update the database Information in the Properties view.

    LCDS-1483 – Model-driven development: Dragging database tables from RDS view onto Modeler canvas creates an extra id property “ID”.

    LCDS-1482 – Model-driven development: Value of SQL Dialect combo box paints in an odd location.

    LCDS-1481 – Model-driven development: Download DDL function for Model Explorer not working on Windows 7.

    LCDS-1480 – Model-driven development: Model Explorer doesn’t refresh automatically when a model is deployed.

    LCDS-1478 – Item query by foreign key id not working. The foreign key id value was 1 but changed to 0 when transmitted from client to server.

    LCDS-1475 – Model-driven development: Expression Builder button used for validator expression on inline style/advanced configuration does not open the Expression Builder.

    LCDS-1474 – Model-driven development: In Properties view text inputs for bundle, key, and tokens, vertical spacing gets very big as size of panel is enlarged.

    LCDS-1471 – Model-driven development: Required properties inside a variant should not be annotated with @NotNull.

    LCDS-1470 – Model-driven development: Incorrect error message when a service is not implemented on the server.

    LCDS-1463 – Model-driven development: Properties view for service does not allow you to specify a return type of void.

    LCDS-1454 – Modeler: Usability Improvements for the Modeler plugin.

    LCDS-1453 – Model-driven development: Add an annotation that can suppress the service generation.

    LCDS-1451 – Model-driven development: When a JDBC driver is not found, get the following RDS error: ‘Datasource jdbc/YourNameGoesHere not found’.

    LCDS-1450 -Model-driven development: Expression Builder used for validator expression accepts entity property name during check, but saving the model results in an error in Design view.

    LCDS-1448 – Model-driven form: Item with inline style showing that a validation condition is not met, continues to show a red border after the condition is met.

    LCDS-1446 – Model-driven form: With numericStepper component in form does not activate reset or save buttons when existing value is edited directly in textInput control.

    LCDS-1438 – Model-driven form: Adding a row of data using typical master-detail application with model-driven form should cause newly added row to be selected in DataGrid control.

    LCDS-1423 – Model-driven development: BLOB types sent to FiberAssembler throw unexpected class not found exception.

    LCDS-1422 – Modeler: On Mac, changing the property/column Type (or collection checkbox) does not update the Design view or source.

    LCDS-1420 – Model-driven development: Provide Expression Builder button for default value field in Properties view.

    LCDS-1418 – Model-driven development: Generate Form dialog in Modeler does not provide option to create model-driven form.

    LCDS-1417 – Model-driven development: Using a ColumnName annotation with a complex id causes various JDBC errors when calling createItem(). The generated DDL isn’t correct either.

    LCDS-1416 – Small message feature does not work with RTMP.

    LCDS-1415 – Model-driven form: Form generates compilation error.

    LCDS-1395 – Modeler: In IBM RAD 7.5.5 right mouse click does not bring any context menus up.

    LCDS-1393 – Model-driven form isn’t generated if the template is in a non-default custom location.

    LCDS-1390 – Model-driven form import statement for the Data Management Service shouldn’t use the project name as the package name.

    LCDS-1388 – The Generate button doesn’t generate implicit service wrappers for a Data Management Service destination.

    LCDS-1387 – Modeler: Feature for extracting templates doesn’t work properly.

    LCDS-1385 – Model-driven development: JoinColumn annotation doesn’t work properly with one-to-many relationship when the owning entity has single id field.

    LCDS-1384 – Model-driven development: One-to-many relationship with multiple id fields but no JoinColumns annotation doesn’t work properly.

    LCDS-1383 – Model-driven development: ASImplicitServiceGenerator instance doesn’t find the template from the default location if a template is missing from the customized location.

    LCDS-1380 – Model-driven development: Implicit required field message and others are not localized.

    LCDS-1379 – Model-driven form: Form throws runtime exception with simple validation.

    LCDS-1373 – Model-driven development: Creation of new model in new Flash Builder Flex/LiveCycle Data Services project creates 2 problems in problems view.

    LCDS-1359 -Model-driven development: The Styles view regularly displays “This view is only available … (for design mode)” when you are in Design view.

    LCDS-1357 – Modeler: Draws improper relationship lines when there is a particular combination of entity relationships.

    LCDS-1355 – Model-driven development: An expression in a validation overrides ASValidator setting. Therefore, they should be mutually exclusive in the user interface.

    LCDS-1348 – Model-driven development: For a bidirectional association, update returns incorrect result.

    LCDS-1347 – Remote objects with AS keyword method names should causes error from client-side validator.

    LCDS-1343 – Model-driven development: ComboBox control created by model-driven generation does not show error with red color when value is missing for required field.

    LCDS-1341 – Model-driven development: Inline style created using only the Advanced Style Configuration dialog is not visible in the Properties view once it is created.

    LCDS-1340 – Model-driven development: Message caption, error, and description text are populated with caption, error, and text when creating a global style. This causes these name and values to go into the model even when not wanted.

    LCDS-1339 – RTMPProtocolHandler$DirectRTMPConnection Queue Grows in size until OOM exception occurs.

    LCDS-1338 – Model-driven development: Opening a model results in the following message: “org.eclipse.core.runtime.CoreException: Plug-in com.adobe.model.editor was unable to load class com.adobe.model.derived.editor.xml.configuration.folding.FiberFoldingStructureProviderProxy.”

    LCDS-1325 – A paged fill causes a null pointer exception.

    LCDS-1323 – Modeler: For the Assembler Generator, get a null pointer exception when the template path is set to null.

    LCDS-1318 – Model-driven form: Template uses xxxInput.value for a text input and causes compilation error.

    LCDS-1317 – Model-driven development: The initial setting of project-level code generation should use the current workspace setting instead of the default setting.

    LCDS-1309 – Model-driven form: borderColor setting causes compiler error with Flex SDK 4.

    LCDS-1306 – Modeler: Closing a Flex project with a model file still open causes a Data Model Validation Error alert.

    LCDS-1305 – Modeler: Relationship lines draw incorrectly or do not redraw as adding bidirectional relationship with the Properties view.

    LCDS-1300 – Model-driven form: Reset button should clear data if clicked after adding a new row in a master-detail DataGrid control.

    LCDS-1299 – Modeler: The name of an id, property, or entity is reset to the original name after a mouse click to another control in the Properties view.

    LCDS-1288 – Model-driven form: Form radio button should be disabled if a service method is selected in the Generate Form dialog.

    LCDS-1284 – Modeler: Creating a new FML file as a link to an FML file already on disk does not work properly.

    LCDS-1280 – Modeler: Entities do no show in Design view after importing a service with a services wizard.

    LCDS-1279 – GatewayFlexSession invalidations are not logged.

    LCDS-1278 – Modeler: Unchecking ‘Paged Queries From Database’ and/or ‘Auto-refresh’ in Properties view for filter has no effect.

    LCDS-1277 – Modeler: Properties view dialog lets you to add both a criteria filter and a pass through query. However, these are mutually exclusive options.

    LCDS-1276 – Model-driven development: ActionScript service generation doesn’t generate proper code if findItem uses the same function as getItem in the DataManagement annotation.

    LCDS-1275 – Model-driven development: Incorrect exception is thrown when a query is used along with a criteria in a filter.

    LCDS-1274 – Modeler: An error in a model causes the alert with message, “The editor could not switch between pages …” to appear. But clicking OK closes the dialog and the Modeler does switch to Design view.

    LCDS-1273 – Modeler: The property element’s default attribute cannot be set in the Properties view.

    LCDS-1272 – Model-driven development: The modeling runtime should allow non-numeric ID field to be auto-generated.

    LCDS-1270 – Modeler: There is no way to create a version property in Design view.

    LCDS-1267 -Client-side data management: An autocommit value of true doesn’t work properly.

    LCDS-1265 – AmfTrace causes out of memory errors when debug logging is enabled even when no endpoint filter is enabled.

    LCDS-1264 – Modeler: The Properties view cannot handle a property type defined as char[32].

    LCDS-1262 – Model-driven development: A null pointer exception is thrown in logs when there is a particular combination of entity relationships.

    LCDS-1260 – Modeler: An invalid length for a property is silently removed without any feedback to the user.

    LCDS-1259 – Modeler: Cannot set length of properties of type Blob in the Modeler Design view.

    LCDS-1255 – Orphan records are left on the server.

    LCDS-1254 – Model-driven development: Malformed code is generated when there is an entity without a package name.

    LCDS-1253 – Model-driven development: Code generated for a paged operation ignores parameters of the operation.

    LCDS-1249 – Model-driven development: A generated ActionScript value object causes an error when the entity has a uid as the id field.

    LCDS-1245 – WebService wrapper regression error: “Cannot assign operations into an RPC Service (convertResultHandler).”

    LCDS-1241 – Commit(array, cascadeCommit) fails to commit new created children intermittently.

    LCDS-1240 – Modeler: Setting and unsetting the required attribute in the relationship Properties view for an assocation has no impact.
    LCDS-1239 -An ItemReference instance’s responder isn’t called when commit(array, true) is used.

    LCDS-1231 – New Flex project with WTP option has many errors similar to “Nested exception: cvc-elt.1: Cannot find the declaration of element ‘hibernate-configuration’.”

    LCDS-1227 – Model-driven development: Modeling language XSD schema could support a default or initial attribute for property.

    LCDS-1224 – Model-driven development: The revert() method should be exposed on service proxy the same way the commit() method is.

    LCDS-1215 – Model-driven development: The com.adobe.model.core plug-in eventually causes a ClassCastException on parsing an FML file.

    LCDS-1210 – Looping Connection Write on Ack State 2 in Reactor.java

    LCDS-1209 – Support for URL binding notation for REST-style APIs in service wrapper classes.

    LCDS-1205 – Strong sub-objects resulting in runtime error.

    LCDS-1202 – Model-driven development: ColumnName annotation isn’t honored when using IdClass.

    LCDS-1194 – refreshFill() method throws LazyInitializationException when updating.

    LCDS-1190 – Modeler: When deleting an association in Design view, the cardinality attribute is not removed from the property in the model.

    LCDS-1185 – Model-driven development: FullyQualifiedReferences flag not working.

    LCDS-1181 – Model-driven development: Setting the selectedIndex property of a DataGrid control in a master/detail application with a model-driven form causes the form to immediately activate the Reset and Save buttons.

    LCDS-1174 – When an item is removed from the managed fill, it triggers a DataConflictEvent instead of removing the item from the list silently.

    LCDS-1172 – ASGeneration of _super*services does not place semicolon at end of import statements.

    LCDS-1167 – Filter using JPQL passthrough query doesn’t work if the destination uses paging.

    LCDS-1159 – Modeler: Adding new annotations, items, and values should leave the cursor on the field in enter mode.

    LCDS-1057 – Model-driven development: DataGrid should display columns for derived properties.

    LCDS-1150 – Model-driven development:Saving problems with multiple collections of same type.

    LCDS-1148 – Modeler: Design view painting issue when dragging properties into cases of variant.

    LCDS-1134 – Updating a Company form updates Company DataGrid and Employee form but not Employee DataGrid.

    LCDS-1119 – Model-driven form: Using multiple model-driven forms on same application has issues with unexpected interactions between forms.

    LCDS-1111 – Null pointer exception during startup on Mac OS when deploying within EAR with multiple modules on JBoss.

    LCDS-1105 – Model-driven development: Model entity string ID length attribute doesn’t get enforced in the created table in the database.

    LCDS-1104 – Model-driven development: Modeling fails to deploy a composite entity.

    LCDS-1093 – Model-driven development: Integer entity of database imported is by default auto-generated and causes a run time error.

    LCDS-1088 – Client-side data management can detect duplicate rows coming from the server and warn the user when user has chosen a wrong primary key.

    LCDS-1066 – Expose the client IP address when an RTMP request is handled on the server.

    LCDS-1055 – Modeler: Expression Builder has a syntax error when escaping GT, LT, etc.

    LCDS-1048 – Network Monitor feature requires support to deserialize DataMessage and other LiveCycle Data Services messages present in flex.data.messages in Java to show server data.

    LCDS-1040 – Assign convertresulthandler property of AbstractWebService to TypeUtility’s convertResultHandler.

    LCDS-1039 – Dynamic channel configuration not working with DataService instance.

    LCDS-1028 – GatewayService should fail gracefully if it has been blacklisted by GatewayEndpoint.

    LCDS-1018 – When using Data Management Service paging, get an error when holding down the down arrow on a DataGrid scrollbar for paged association.

    LCDS-1004 – Model-driven form: Generating model-driven form does not create working form.

    LCDS-993 – Model-driven form: Compiler error is thrown when model-driven form is generated for remote destination.

    LCDS-985 – Model-driven development: Variable argument support in FML files.

    LCDS-974 – Get runtime exception: WLEventContextImpl must implement flash.util.IExternalizable.

    LCDS-970 – Model-driven development: refreshFill() method doesn’t update the item if the item is first removed from the subscription and then added back into the subscription.

    LCDS-959 – Modeler: Should provide the minimum diagramming features necessary to use it for simple class modeling.

    LCDS-940 – ClassCastException when cascading the create of a unidirectional association from a class with no RemoteObject alias.

    LCDS-931 – With shared-backend set to false, the update message triggers EntityUtility LazyInitializationException in a cluster.

    LCDS-930 – There is no getRemoteAddr() interface when using NIOAMF endpoint.

    LCDS-928 – SequenceManager.getSequence ArrayIndexOutOfBound Exception.

    LCDS-917 – Deserialization error when returning properties of type Array which are typed entities.

    LCDS-890 – Model-driven form: Form uses a getAll() function even though the destination isn’t backed by the FiberAssembler.

    LCDS-884 – TypeError cannot convert ArrayCollection to Array when using DataService to update value.

    LCDS-879 – Client-side data management: The getItem() method does not return a single item when an array is sent.

    LCDS-815 – Model-driven form: Null pointer exception when having two model-driven forms are on the same MXML page.

    LCDS-730 – ReleaseReference applied on no single-value property.

    LCDS-713 – When deleting an item that has an child association, the Data Management Service sends back two delete result event.

    LCDS-577 – MPI headers not getting added to server pushed messages.

    LCDS-478 – When a paged fill returns only one item, client-side data management throws an argument error.

    LCDS-429 – For client-side data management, a delete function with parameters= “id” doesn’t work when the entity has multiple id fields.

    FB-19843 – Data Management destination introspection in Flash Builder does not generate proper fill function for Data Management Service destinations that use the AbstractAssembler approach.