UML diagrams - release notes


1.0 Known problems
   1.1 SVG images might not save with correct colors in communication diagrams
   1.2 Shortcut keys might not work in text fields
   1.3 Cannot display constraints on association endpoints
   1.4 Decorators might not update to reflect visibility changes
   1.5 Lifelines cannot display decorators
   1.6 Invalid exceptions occur when you generate Javadoc documentation
   1.7 Cannot create new operations on C++ sequence diagrams
   1.8 Constraint violations do not load in the diagram editor
   1.9 Architectural discovery pattern count might be misleading
   1.10 Implements notations might appear as generalizations
   1.11 Default browser on SuSE Linux does not properly display class diagrams as SVG
   1.12 Rational Software Architect might not respond properly if the LANG environment variable is incorrect
   1.13 Operations might make UML diagrams unusable
   1.14 SVG images might not generate properly
   1.15 Text editors might not display files properly
   1.16 Relationship connectors might not appear properly
   1.17 Show related elements operations might cause errors

1.0 Known problems

1.1 SVG images might not save with correct colors in communication diagrams

When you save a communication diagram as an SVG image, the fill colors for lifelines might not save correctly. To work around this issue, save the communication diagram as a GIF or JPEG image.

1.2 Shortcut keys might not work in text fields

When you work with an editable diagram, the copy shortcut key (Ctrl+C) and paste shortcut key (Ctrl+V) might not work in text fields. To work around this issue, copy and paste text by using the Edit menu:

  1. Select the text to copy.
  2. Right-click the selection; then click Copy.
  3. Create a new text diagram element.
  4. Right-click the text diagram element; then click Paste.

1.3 Cannot display constraints on association endpoints

When you work with a UML diagram, you cannot display constraints on association endpoints.

1.4 Decorators might not update to reflect visibility changes

When you work with state machine diagrams, you can change the visibility of a state element. However, in the State view, the decorator of the state element might not update to reflect the visibility change.

1.5 Lifelines cannot display decorators

If you display a lifeline that represents a property of a specific kind of classifier or a stereotyped element, the decorator icon is not displayed. Changing the stereotype and visibility settings has no effect. To work around this issue, you can differentiate the lifeline by changing its color.

1.6 Invalid exceptions occur when you generate Javadoc documentation

When you generate Javadoc documentation for a UML diagram from a generated Ant script, the script runs to completion, but throws an exception. You can ignore the exception.

1.7 Cannot create new operations on C++ sequence diagrams

You cannot create a new operation on a C++ sequence diagram. To work around this issue, update the C++ source code to include the new operation.

1.8 Constraint violations do not load in the diagram editor

When you double-click a constraint violation in the Problems view, the element opens in the UML Model Editor. However, the element should open in the diagram editor.

1.9 Architectural discovery pattern count might be misleading

In the Diagram Navigator, the architectural discovery pattern count indicates the number of matches found at the time of analysis. If you update the workspace by importing new projects, or by closing existing projects, the count does not update. To update the count, run the analysis again.

1.10 Implements notations might appear as generalizations

On Linux operating systems, the implements notation appears as a generalization.

1.11 Default browser on SuSE Linux does not properly display class diagrams as SVG

You cannot view class diagrams as Scalable Vector Graphics (SVG) on SuSE Linux using the Konqueror browser. To download and install a viewer that correctly displays class diagrams as SVG, see www.adobe.com/svg/viewer/install/main.html

1.12 Rational Software Architect might not respond properly if the LANG environment variable is incorrect

If the LANG environment variable on your computer is not set, or is set to a value not supported by the GIMP Toolkit (GTK), the product might not respond properly when you work with UML diagrams. In either case, the following Gdk warnings appear in the Eclipse log file:

 (process:9793): Gdk-WARNING **: locale not supported by Xlib
(process:9793): Gdk-WARNING **: can not set locale modifiers

To work around this issue, set the LANG environment variable to a value supported by the Gdk (for example, en_US) and ensure that your setting matches the locale for your X Window System environment.

1.13 Operations might make UML diagrams unusable

On Red Hat Enterprise Linux 3.0, certain operations might make a UML diagram unusable. In each case, the following error message is displayed:

An internal error occurred while showing an internal error. You are recommended to exit the workbench. Subsequent errors may happen and may terminate the workbench without warning. See the .log file for more details. Do you want to exit the workbench?

The .log file will contain exceptions that are similar to the following ones:

 !MESSAGE Failed to execute runnable (java.lang.InternalError: Can't connect to X11 
window server using ':0.0' as the value of the DISPLAY variable.)
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.InternalError:
Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.)
at org.eclipse.swt.SWT.error(Unknown Source)
at org.eclipse.swt.SWT.error(Unknown Source)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1377)
...

 !MESSAGE Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
!STACK 0
java.lang.InternalError: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:175)
at java.lang.Class.initializeImpl(Native Method)
at java.lang.Class.initialize(Class.java:350)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:116)
at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:91)
at java.awt.image.BufferedImage.createGraphics(BufferedImage.java:1073)
at org.apache.batik.ext.awt.image.GraphicsUtil.createGraphics(Unknown Source)
at org.apache.batik.gvt.filter.GraphicsNodeRed8Bit.genRect(Unknown Source)
at org.apache.batik.gvt.filter.GraphicsNodeRed8Bit.copyData(Unknown Source)
at org.apache.batik.ext.awt.image.rendered.TileCacheRed.genRect(Unknown Source)
...

To work around this issue, you must exit and restart the product.

1.14 SVG images might not generate properly

On SuSE Linux Enterprise Server (SLES) Version 9, when you save a UML diagram as an SVG image, the SVG transcoder maps to an incorrect color. As a result, you see color differences between diagrams displayed in the product and diagrams generated as SVG images.

1.15 Text editors might not display files properly

When you invoke a command that displays a UML diagram, such as a file with an .emx, .epx, .dnx, or .tpx file extension, in text mode, the text editor might not display the file properly. To work around this issue, complete the following steps:

  1. In the Model Explorer view, select the diagram files
  2. Right-click the selection, then click Properties.
  3. Click the Info tab.
  4. Under Text file encode, click Other.
  5. Select UTF-8 from the drop-down list.
  6. Click Apply.
  7. Click OK.

1.16 Relationship connectors might not appear properly

When importing an Enterprise JavaBeans (EJB) diagram from WebSphere Application Developer, Version 5.1.1, relationship connectors may not appear properly. To work around this issue, select the connector(s) and in the Properties view, under Appearance, clear the Avoid obstructions check box.

1.17 Show related elements operations might cause errors

When working with a UML diagram, the Show Related Elements operation can return a large number of elements, which may cause your computer to run out of memory. This issue is most common when you specify a search level greater than one, and when you search for all relationships. To work around this issue, specify a lower search level value, and rerun the query. This informationa also applies to Browse diagram queries.

Return to the main readme file