Java and EJB visual editing - release notes


1.0 Known problems
   1.1 EJB display name issues
   1.2 Error messages might display when you work with the CSS editor and model files or visualization diagrams
   1.3 Interfaces might contain unwanted method stubs
   1.4 Java source code might be lost without warning

1.0 Known problems

1.1 EJB display name issues

Currently, in the same EJB project, you can create two Enterprise JavaBeans (EJB) with the same display name, and one or more EJB with no display name.

1.2 Error messages might display when you work with the CSS editor and model files or visualization diagrams

When you work with the cascading style sheet (CSS) editor, you should not work with model files or visualization diagrams at the same time. If you do, and you close the CSS editor, several error exceptions are reported to the .log file and many of the following messages are displayed:

An error has occurred. See the error log for details.

If you click anywhere in the product, the same sequence of error messages display.

To avoid this issue, close all of your model files or visualization diagrams before you close the CSS editor.

To work around this issue, complete the following steps:

  1. Close all of the error message windows.
  2. (Optional) Type Ctrl+Shift+S to save your work.
  3. (Optional) Close all of the new error message windows.
  4. Restart the product.

1.3 Interfaces might contain unwanted method stubs

When you create an extends relationship between Java interfaces, if the target interface is a binary Java type, unwanted method stubs are created in the subinterface. The method stubs are created for the methods that are declared in the super interface or interfaces.

To work around this issue, delete the unwanted method stubs from the subinterface by using the Delete from Project pop-up menu, or by editing the source code with the Java source editor or Package Explorer view.

NOTE: This issue does not occur if the super interface is defined in one of the projects in your workspace.

1.4 Java source code might be lost without warning

When you work with a UML visual editing diagram, if you drag a Java method from one class to another, the method is not removed from the first class and an empty method body is created in the second class. The diagram does not display any errors.

You should never drag a method from one class to another. To recover from this error, delete the empty method body from the source code of the second class and close your diagram and project. The next time that you open your diagram, the error is removed and you can create a diagram view of your classes.

Return to the main readme file