Flex Release Notes

Flex 1.0 Updater 2 Release Notes

The Macromedia Flex 1.0 Updater 2 includes performance and reliability improvements, enhanced documentation for the Flex ActionScript and MXML API Reference, and more. Updater 2 also includes all fixes from Updater 1.

In This Document

This document includes the following sections:

For instructions on installing Flex 1.0 Updater 2, see the Flex 1.0 Updater 2 Installation Instructions.

Compatibility Issues

This section describes changes to Flex 1.0 Updater 2 that can cause applications written using Flex 1.0 and Flex 1.0 Updater 1 to behave differently.

Rebuilding Custom Components

If you have built custom components in the Macromedia Flash MX 2004 IDE and exported them as SWC files to be used in Flex, you must rebuild the SWC files using the updated Flex components in Updater 2. To do this, you install the new file which contains updated component source files for the Flash IDE, and then re-export the component SWC files.

To install the contents of the file:

  1. Close the Flash IDE if it is open.
  2. Delete the following directories:
    c:/Program Files/Macromedia/Flash MX 2004/en/First Run/Flex Classes
    c:/Program Files/Macromedia/Flash MX 2004/en/First Run/Components/Flex Components
    c:/Documents and Settings/{user_name}/Local Settings/Application Data/Macromedia Flash MX 2004/en/Configuration/Flex Classes
    c:/Documents and Settings/{user_name}/Local Settings/Application Data/Macromedia Flash MX 2004/en/Configuration/Components/Flex Components
  3. Find the file. Updater 2 copies it to {flex_install_dir}/flexforflash/
  4. Extract the contents of to the Flash First Run directory. The default location is C:/Program Files/Macromedia/Flash MX 2004/en/First Run. This file creates the Components/Flex Components directory and copies the Flex SWC files to that directory. In addition, it creates the Flex Classes directory, which contains the ActionScript source files for the Flex classes.
For more information about creating components for Flex in Flash, see Developing Flex Applications.

Slider Namespace

The HSlider and VSlider controls were previously part of the samples applications and in the Flex examples. They have now been added to the standard Flex control set. As a result, they must now be used with the "mx" namespace, as the following example shows:

<?xml version="1.0" encoding="iso-8859-1"?>
<mx:Application  xmlns:mx="" >


  <mx:HSlider maximum="100" />



Change to Undocumented border-style Property

Formerly, you could use the undocumented border-style CSS property to add rounded corners to Panel and TitleWindow containers. Now, to round corners on these containers, set the panelBorderStyle property to roundCorners, as the following example shows:

<mx:Panel panelBorderStyle="roundCorners">

The panelBorderStyle property also takes default as an argument.

Authentication Tightening

Previously, you could use a Basic authentication popup dialog box or passthrough authentication to secure any WebService or HTTPService endpoint. Now, if the WebService or HTTPService endpoint is not in the same domain as the Flex proxy, you must use the use-custom-authentication or run-as parameters in the flex-config.xml file to secure the endpoint. An error is sent to the client otherwise.

Change to Namespace Declarations

Due to updates in Flex 1.0 Updater 2, component package namespaces must now end in ".*" or use the special case of "*" to represent the current package. This was not enforced in previous versions of Flex. New and existing applications that do not follow this rule will not compile.

For example, the following component is in a package and the namespace declaration uses valid syntax:

<CustomComponent xmlns="subpackage.*" />

If the component is in the same directory as the application, you can use the following special syntax to declare the namespace:

<CustomComponent xmlns="*" />

Known Issues

The following table describes known issues in Flex 1.0 Updater 2.


When dragging multiple popup windows, the dragged window does not go to the top of the stack. This only occurs if the broadcastOutsideEvents property is set to true in the PopUpManager.createPopUp() method. To work around this issue, set the modalWindow property of the init object to true, as the following example shows:

var window1 = PopUpManager.createPopUp(this, WindowType1, false, {deferred: false, x:20, y:50, modalWindow:true}, true);

Updater 2 Bug Fixes

Flex 1.0 Updater 2 includes bug fixes from Updater 1, plus the fixes listed in the following table:

95837 The undocumented CSS style border-style used by Panel and TitleWindow has been deprecated. For more information, see Compatibility Issues and the entry for bug fix 78750.

95613 The passthrough Authentication header is now only sent to data services in the same domain as the Flex proxy.

95379 If you changed a style's styleName property using the setStyle() method, the style properties for a component instance might have contained the wrong values.

94366 On Linux, custom components specified with the <manifest> tag in the flex-config.xml file were not being found by Flex.

94231 The HTTPService was sending parameters incorrectly when using GET requests.

93435 Untyped component properties were causing typecheck errors in some situations.

93434 Classes were unable to access private variables of their superclass in some situations.

93414 DataBinding was not correctly evaluating expressions that used String concatenations and single quotation marks.

93394 RemoteObject was not serializing inherited properties in complex Java beans. Now, properties in a superclass will be sent to the client.

93213 Binding was not working correctly from a function with a ChangeEvent bound to the property.

92961 Passing bad credentials with custom authentication to a web service caused the Flex proxy to go into a loop making the same request to the endpoint with the same bad credentials 100 times. Eventually, Flex returned a "Maximum redirects (100) exceeded" message to the client. Now, Flex returns a Client.Authentication fault.

92883 If you set a container's enabled property to false, Flex was not disabling the container. Flex now dims the color of the container and of all of its children, and blocks user input to the container and to all of its children.

92819 Arrays were incorrectly encoded by the default XMLEncoder when used with HTTPService.

91964 Binding expressions from a complex model were sometimes raising messages of type WARN when you changed the application source files.

91528 When you added a third parameter to the getURL() method, Flex threw a compilation error. Now, you can specify a GET or POST action as the third parameter in the getURL() method.

89585 Web service requests required more than one parameter when the format was the default, object. Previously, you were required to set the request format to xml; for example, <mx:request format="xml">.

89437 Large XML data model files were generating ActionScript files exceeding the 64KB limit and were not compiling.

89427 Large XML data model files were generating ActionScript functions exceeding the 32KB and were not compiling.

88764 Flex was not including the name and id parameters in the default HTML wrapper.

87302 The <mxml> JSP tag was incorrectly generating name and id parameters in the HTML wrapper.

83178 In Flex 1.0 and Updater 1, Flex used a Java Timer to poll the list of files that each application depended on for changes. With laptops put into hibernation mode, the polling would try to catch up when the laptop was woken up. This caused the CPU to spike. This has been fixed by limiting the polling to once per poll interval.

79502 Sending an ActionScript Date object was sometimes triggering an exception on the server side during deserialization of the RemoteObject.

78750 It is now easier to add rounded corners to Panel and TitleWindow containers. You can now use the panelBorderStyle="roundCorners" style property. The panelBorderStyle property also takes default as an argument. Also, to turn off the drop shadow on Panel and TitleWindow containers, set the dropShadow property to false. To turn it back on, set the value to true.

78086 The TitleWindow container was not sizing itself to fit the entire title String.

60385 The text in Button, Link and AccordionHeader controls now accept the textAlign style property.

Updater 1 Bug Fixes

Flex 1.0 Updater 1 includes the following bug fixes:

89812 UIObject no longer creates a memory leak.

89584 The format="xml" attribute on WebService.operation.request was not working with binding.

89312 The RemoteObject tag with a protocol of AMF now ignores objects of type java.lang.Class rather than throwing exceptions.

89129 When a data-bound Repeater object was used as part of a pop-up window, it was not being destroyed even after the pop-up window was closed.

88810 Accordion containers were handling focus management incorrectly.

88700 The deletePopUp() method is now available on any subclass of UIObject. Previously, it was only available for Window and Panel containers.

88695 The mxmlc command-line compiler now returns a more informative error message if the -configuration option points to an invalid configuration file.

88680 Errors are more descriptive when users incorrectly attempt to set styles using ActionScript.

88470 The showEffect and hideEffect effects were not working for ProgressBar controls.

88134 The XMLDecoder was not handling multiple arrays correctly.

87988 The fdb command-line debugger was displaying "Trial Edition" even when Flex was running under a commercial license.

87853 Setting the selectedIndex property of a ComboBox control was not updating the drop-down list.

87837 When launching a TitleWindow container as a pop-up, using the x and y properties in ActionScript caused a visual separation of the drop-shadow from the TitleWindow.

87755 When selecting Sunday for Day of the Week, the DateFormatter returned undefined if three or more pattern letters were used. With one or two pattern letters, the DateFormatter returned the correct Day of the Week digit.

87581 The Flex Web Service and HTTP Service proxies now allow requests to be routed through an external HTTP proxy server. For authenticating HTTP proxy servers, the Web Service and HTTP Service proxies support Basic and NT domain authentication. You configure the authentication settings in the flex-config.xml file using the <external-proxy> tag, as the following example shows:


The <location> tag defines the server name and port to use as an HTTP proxy. Specify the <username> and <password> tags when the proxy server uses BASIC authentication. Specify a value for <nt-domain> when the proxy server uses NTLM authentication. You must explicitly add the <external-proxy> and its child tags to the <web-service-proxy> and <http-service-proxy> definitions in order to use authentication for the proxies.

87569 ActionScript Profiler data was not being correctly generated when ProfileFunctionEnable was set to 1 in the mm.cfg configuration file.

87534 When a client requested an MXML file and the <User-Agent> HTTP header was missing or was empty, Flex threw a NullPointerException. Now Flex ignores the missing header.

87505 MXML components can now implement interfaces, as the following example shows:

<mx:HBox xmlns:mx="" implements="MyInterface">

87457 You could not export the Slider control (extras/slider/SliderSource.fla) in Flash MX 2004 when the classpath pointed to the Flex classes.

87351 The Explorer Session sample application was failing on Tomcat 5.

87332 The <mx:HTTPService> tag was not sending data on Tomcat or WebLogic servers for POST methods when noProxy was false, and contentType was application/x-www-form-urlencoded. On Tomcat and WebLogic servers, Flex now adds the parameters to the request body by default. If you experience this problem when using another application server, set the flex.addFormParameters JVM property to true; for example, in your jvm.config file, add the following argument:


To turn off this behavior for WebLogic and Tomcat servers, you must explicitly set the value of flex.addFormParameters to false in your JVM configuration file.

87284 Error alert boxes for WebService and HTTPService were not popping up on root, when the faulty service was in a child of a navigator.

87276 Flex was throwing a java.lang.StringIndexOutOfBoundsException exception when the value of an XML node was a single hyphen character ("-").

87217 When dynamically binding data to a TextArea component, null values were not clearing the component; the previous non-null value was still displayed.

87214 There was an error reading variable values when debugging with the Flash Debug Player. Variables referenced by parent object and variable name (for example, myObj.myVar) were not being returned, whereas variables referenced by only the variable name (for example, myVar) were returned.

87206 The browser detection logic was not forwarding Netscape 7.1 users to the correct page when no Flash plug-in was installed.

87123 The speed of tabbing between text fields in the FlexStore sample application has been improved.

87035 The credit card ComboBox in the Flex Store sample application was not working correctly when the user navigated with a keyboard.

86863 The Flex Web Service and HTTP Service proxies now support the pooling of HTTP connections. You configure connection pooling for these services in the appropriate section of the flex-config.xml file by adding a <max-connection> tag. If the tag is not present, then Flex uses the default value of 50 connections. You can change this number by adding a <max-connection> tag to the <web-proxy-service> or <http-proxy-service> settings, as the following example shows:


To disable connection pooling, set the value of <max-connection> to 0.

84069 The width of DataGrid components was increasing slightly after they were loaded.

78995 The ActionScript Profiler was causing a memory leak in Flash Debug Player.

Getting Started


Application Development








Community Resources