Adobe LiveCycle Mosaic

Version 9.5.0.1

Release Notes 

October 2010

Edition 1.0

Copyright 2010 Adobe Systems Incorporated. All rights reserved.

This file contains important information that was not available when the product documentation was written. Review this information before you run this version of Adobe® LiveCycle® Mosaic 9.5.

Note: For more information on the status of an issue listed in the release notes, contact Adobe Technical Support and specify the unique reference identifier provided in the title of the issue (ex. [Ref: #1234567]).


Contents

Installation Issues

Localization Issues

Development Issues

End User Issues

The Documentation Set

Additional Licenses and Copyrights


Installation Issues

Cannot install Mosaic on JBoss 4.2.0 application server [Ref: #2713862]

Mosaic 9.5 cannot be deployed on a Red Hat JBoss 4.2.0 application server (standalone and cluster).

Ant server tasks support rootPath attribute [Ref: #2659373]

You can specify a "rootPath" attribute for the mosaic-application, mosaic-catalog, and mosaic-policy server tasks. "rootPath" specifies the path to the root of the Mosaic 9.5 application on the server. However, the default value of "/mosaic" is currently the only valid value.

Configuration for Mosaic 9.5 WebDAV repository in WebSphere cluster environement [Ref: #2699855]

For each node of the cluster, make the following changes to mosaic-context.xml. The mosaic-context.xml file is located in the mosaic.war file in the directory META-INF/spring/mosaic-context.xml:

1. Remove the comment markers from the following section:

<!--
   <bean id="mosaicWebDAVAuthenticationParams" class="com.adobe.livecycle.mosaic.webdav.config.BasicAuthenticationParams">
      <property name="username" value="administrator" />
      <property name="password" value="password" />
   </bean>

   <bean id="mosaicWebDAVConfigParams" class="com.adobe.livecycle.mosaic.webdav.config.ConfigParams">
      <property name="protocol" value="http" />
      <property name="hostname" value="localhost" />
      <property name="port" value="9080" />
      <property name="authenticationParams"><ref bean="mosaicWebDAVAuthenticationParams"/></property>
   </bean>
-->

2. Change the value of the hostname and port properties to the values that are appropriate for the node.

3. Add comment tags to the following section, which is the default WebDAV repository configuration:

   <bean id="mosaicWebDAVAuthenticationParams" class="com.adobe.livecycle.mosaic.webdav.config.BasicAuthenticationParams">
      <property name="username" value="administrator" />
      <property name="password" value="password" />
   </bean>

   <bean id="mosaicWebDAVConfigParams" class="com.adobe.livecycle.mosaic.webdav.config.ConfigParams">
      <property name="requestInfoService"><ref bean="mosaicRequestInfoService"/></property>
      <property name="authenticationParams"><ref bean="mosaicWebDAVAuthenticationParams"/></property>
   </bean>


Localization Issues

Mosaic internationalization/localization [Ref: #2638768]

Mosaic 9.5.0.1 is available in English only, but supports internationalization. Full localization will be available in Mosaic 9.5.0.2.


Development Issues

ILayout interface (ActionScript) and Layout class (JavaScript) getter methods return the values set by the corresponding setter methods [Ref: #2643443]

The getter methods for the com.adobe.mosaic.core.om.interfaces.ILayout class (ActionScript) and Layout class (JavaScript) do not return the default values of class properties. Instead, the getter methods return the values set by the associated property setter methods. This issue will be corrected in a future release.

Pop-up dialogs in Mosaic 9.5 tiles are displayed in the wrong location [Ref: #2627087 & 2730509]

Pop-up dialogs, such as ActionScript alert boxes and custom pop-up panels, are not automatically centered horizontally and vertically relative to viewable area of the tile. Rather, these pop-ups are centered relative to the entire width and height of the tile. This can result in pop-up dialogs that are displayed partially or completely outside the visible boundaries of the tile that are viewable in the application.

Similarly, when the browser client window is maximized, the height and width values of "FlexGlobals.topLevelApplication.stage" are incorrect. If the location of pop-up windows is determined using these values, those windows are displayed in the wrong location.

A workaround is to set the x and y coordinate values of the dialog using the width and height values of the entire Mosaic application. For example, for a panel:

      panel.x = (this.screen.width  - panel.width)  / 2;
      panel.y = (this.screen.height - panel.height) / 2;

The following code illustrates the values using a popup:

      popup.x = (this.screen.width  - popup.width)  / 2;
popup.y = (this.screen.height - popup.height) / 2;

The tileChrome attribute applies only to immediate tile children [Ref: #2559253]

The tileChrome attributes applies only to its immediate tile children, and not to nested (child) panels. If there are nested panels, the tileChrome attribute should be specified for each panel.

Deploying sample applications to an HTTPS server [Ref: #2478725]

When you deploy the sample Mosaic 9.5 applications provided in the Mosaic 9.5 installation, the default server protocol is HTTP. To deploy the sample applications to an HTTPS server, edit the Ant build.xml files that deploy the samples:

  1. Edit the build.xml file to include the variable ${protocol}.
  2. When you run Ant, set the protocol variable to "https".

Removing a view with the removeView() API by clicking a button on a tile in the view to be removed gives 1009 error [Ref: #2648159]

Using the Mosaic 9.5 API to close a view by placing a button on the view you wish to close will result in a 1009 error. It is recommended that you place a button, connected to the removeView API, somewhere other than on the view being closed or use the built-in close button.

Performance issues using LiveCycle as the repository [Ref: #2635991]

It is recommended that users implement the iRepository interface to use their own content management system. Using LiveCycle as the repository produces poor performance results.

Errors are displayed when debugging the desktop client [Ref:#2703087]

When debugging Flex tiles in the desktop client, the application may display errors related to thrown exceptions. Close the message to continue running the application. For example, when closing a panel, the error message is: Error#1034: Type Coercion failed when converting mx:managers::WindowSystemManager to mx:managers:SystemManager when closing a panel.

ActionScript error is displayed when you are debugging using Internet Explorer and close a view [Ref: ##2703080]

When debugging Mosaic 9.5 Flex tiles running in Internet Explorer, an ActionScript error may be displayed when you close a view. Close the error to continue running the application. Complete error message is: ReferenceError: Error #1069: Property loaderInfo not found on String and there is no default value.

Errors when closing a view that was opened from a catalog [Ref: #2703080]

When an application allows a user to open a view from a catalog, the user may experience problems after closing the view. For example, if the application is running in the desktop client, the views disappear, and, when working in the browser client, Error 1009 is displayed. To avoid this problem, change views by opening a new view instead of closing the current one.

Application crashes when a tile removes its parent view [Ref: #2703076]

If a Mosaic application uses the removeView () method provided by the IApplication interface, the application will crash when a tile removes its parent view from the application. To avoid this problem, configure the method to remove the view using a tile that is not a child of the view. For example:

var viewToRemove:IView = ... // Get a view

// Verify the view to remove is not this tile’s view
if (this.parentView.nodeId != viewToRemove.nodeId)
{
   this.mosaicApp.removeView(viewToRemove);
}

Complete error message is: TypeError: Error #1009: Cannot access a property or method of a null object reference.

View tabs overlap the view controls when many views are added [Ref: #2655275]

If the number of views becomes too large to fit in the view tab area, the tabs overlap the view controls. To avoid this problem, you can change the user interface for views to a combo box. For more information on alternative styles, in Developing Applications for LiveCycle Mosaic 9.5, under Creating Applications, see "Creating application styles and skins".

Desktop client only: Tiles cannot load their own style sheet [Ref: #2722963]

Mosaic treats style sheets that are compiled as SWF files as "module" SWF files, which have some security domain constraints. Adobe AIR applications run in their own domain, which makes their behavior similar to "localhost". Because the style sheet SWF is located on the Mosaic server, AIR considers this to be a foreign domain and rejects the style sheet SWF. But if you run your application in the browser client, the style sheet SWF is accepted because it comes from the same domain as the Mosaic runtime environment. To configure a tile to use its own style sheet while running in the desktop client, embed the style sheet in the tile. (For example, in Flex 4, <fx:Style source="mystyles.css" />.)

Browser client only: Cannot load more than one tile with a specific LCDS connection [Ref: #2727583]

In the browser client, when an application has loaded a tile with a LiveCycle Data Services (LCDS) connection, you cannot load additional tiles with the same connection. The tiles that cannot be loaded include both additional instances of the same tile or a different tile with a LCDS connection to the same server.

Browser client only: HTML tile content is not displayed if the panel is configured to use a fixed width or height [Ref: #2734192]

If you specify the width or height of a panel using HorizontalLayout or VerticalLayout, when an HTML tile is added to the panel, its content is not displayed. For more information about layouts, see "Using application layouts" in Developing Applications for Mosaic 9.5.


End User Issues

Changing browser cache settings can cause unexpected results when viewing Mosaic 9.5 applications [Ref: #2636161]

End users are advised not to alter their web browser caching settings when using Mosaic 9.5. Altering the settings can produce undesirable Mosaic 9.5 application behaviors, such as SWF files not refreshing from the Mosaic 9.5 server appropriately.

Tiles may overlap in views and panels added programmatically [Ref: #2473831]

If your Mosaic 9.5 application adds views or panels using the addTile() or addView() methods, the added elements use DynamicColumnLayout by default. Depending on how many tiles are already in the view or panel, the newly added tiles may be reduced in size or overlap existing tiles.

Style sheet background color covers HTML tiles [Ref: #2475669]

If you set the background color attribute of a Mosaic 9.5 application’s style sheet and a user accesses the application using the browser client, the HTML tiles display incorrectly. Avoid this problem by setting the backgroundAlpha property (a Flex property that controls transparency) to a value less than .5.

User interface is nonresponsive after actions that display a dialog box [Ref: #2403746]

When a user accesses a Mosaic 9.5 application using Firefox, if the application contains an HTML tile with content created using Adobe Flash® technology, the application may stop working after actions that display a dialog box (for example, dialog box confirming a tile will be deleted). Avoid this problem by modifying the HTML source. For more information, contact Adobe Technical Support.

Memory limitation for displaying tiles [Ref: #2458513]

Each instance of a tile in a Mosaic 9.5 application needs the same amount of memory. There is no built-in limit to the number of tiles you can add to a Mosaic 9.5 application. However, if the memory requirements of the tile instances you attempt to display in a single session exceed the memory capacity of Mosaic 9.5, the desktop or browser client session fails.

Editing an application or catalog item without the correct permission appears successful on the client, but results in an error on the server [Ref: #2607316]

If a user edits an application or catalog item without the correct permission, the changes appear to be saved on client, even though they are not saved.

Note: For Mosaic 9.5, the Catalog Manager and the visual design tool are unsupported. This is one known issue. However, there may be other issues not yet identified.

Scrolling issue with HTML tiles [Ref: #2635995]

There are scrolling and redrawing issues with HTML tiles. For example, when scrolling down a page, the HTML tile erases from the top, but redraws when scrolling up.

Cannot scroll all the way down in an HTML tile [Ref: #2636163]

When scrolling down the tile, only the top half of the HTML tile is displayed and an unnecessary horizontal scroll bar appears. To see the tile in its entirety, use the mouse wheel to scroll down more, or resize the application window until the scroll bars fix themselves.

Using the tab key to change focus to an HTML tile causes the HTML tile to resize [Ref: #2636164]

Using the tab key to change focus to an HTML tile causes the HTML tile to resize outside its correct borders. To view the tile properly, resize the window so that scrolling is not required to see the HTML tile in its entirety.

Moving a second tile out of a panel causes double scroll bars to appear [Ref: #2636165]

When moving a second tile out of a panel, two sets of vertical scroll bars appear at the right of the panel when only one vertical scroll bar should appear for the tile.

Desktop client only: Expanded drop-down list in an HTML tile remains expanded when scrolling or switching to another view [Ref: #2637678]

If a drop-down list in an HTML tile is expanded, it remains expanded and visible when scrolling the tile or switching to another view. To collapse the drop-down list, users must click on the tile.

The Internet Explorer Zoom feature moves content outside the borders of an HTML tile [Ref: #2655279]

When accessing Mosaic 9.5 applications in Internet Explorer, if the zoom level is increased using the View menu or the magnifying glass button, the content of an HTML tile expands beyond its borders.

View tabs are too narrow [Ref: #2655278]

When adding view tabs, if the total width of the tabs fills the available space and the application window is resized, a tab may be resized to a very small width (1 pixel).

Application loads a tile that is already loaded [Ref: #2715837 & 2715839]

If an application loads a tile as part of a view or panel, the same tile is loaded again when the user opens another panel or view that uses the tile.

Desktop client only: The PDF content in a tile extends outside of the desktop client [Ref: #2715841]

If a tile contains PDF content, it may overlap or extend outside the user interface of the desktop client when the tile is loaded.

Desktop client only: In a cluster environment, the client does not switch nodes when the current node is unavailable [Ref: #2656563]

If the desktop client is connected to the server using load balancing and the current node fails, restart the desktop client to continue using the application.

Content moves outside of HTML tile frame when resizing the application window [Ref: #2727572]

When you resize an application, the frame of the HTML tile is resized, but the content of the tile is displayed outside of the frame.

Browser client only: When a drop-down is displayed, click an HTML tile twice to access it [Ref: #2730845]

If the hasPlugin attribute for an HTML tile is set to "none", the tile is displayed on top of user interface elements. However, if a Mosaic 9.5 drop-down menu is displayed, the menu has display priority. When a drop-down menu is displayed, click the HTML tile to give it priority, and then click it again to access its content. For more information about the hasPlugin attribute, see "Configuring applications to work with HTML plug-in content" in Developing Applications for LiveCycle Mosaic 9.5.

For Mosaic 9.5 on JBoss, opening a Process Management ES2 form generates errors [Ref: #2727484]

This problem occurs when Mosaic 9.5 is deployed on LiveCycle ES2 for JBoss and is customized with a library associated with a specific Process Management ES2 form. Javascript errors are reported when the user tries to open a form from a Mosaic 9.5 tile. You cannot set Flash vars and access them from a tile. To avoid this problem, manually set the swfId in workspace-frames.js.


The Documentation Set

For LiveCycle ES2, all the product documentation is now available from the Adobe LiveCycle Developer Center. The documentation is provided in PDF, HTML help, and downloadable ZIP files. You can add any comments or questions that you have directly to the HTML help files.


Additional Licenses and Copyrights

By installing this product, in addition to the Adobe license terms, you also agree to be bound by the third-party terms specified in the product documentation and at www.adobe.com/go/thirdparty. Adobe recommends that you review these third-party terms.


Release Notes -- Adobe LiveCycle Mosaic 9.5.0.1 -- 10/07/2010 12:36 PM