Oracle® Application Server TopLink Mapping Workbench User's Guide
10g Release 2 (10.1.2) Part No. B15900-01 |
|
Previous |
Next |
The OracleAS TopLink Mapping Workbench has a number of known issues in this release, namely:
Changing the icon size of the OracleAS TopLink Mapping Workbench toolbar may cause the application to fail at the next start-up. You must edit the workbench.xml
file and change small-icon="false"
to "true"
.
OracleAS TopLink Mapping Workbench does not generate proper set method for array type attributes.
In the OracleAS TopLink Mapping Workbench, changes to the interface descriptor do not update properly. When the inheritance structure of a class, for example, class A
changes so that the class A
is no longer a subclass of a class B
which implements the interface I
, the interface's descriptor is not properly updated by the OracleAS TopLink Mapping Workbench and still displays class A
as the implementor. If you attempt to remove class A
from the interface I
implementors, the OracleAS TopLink Mapping Workbench throws the following exception: java.lang.ArrayIndexOutOfBoundsException
.
As a work around, remove the implementor from the interface descriptor before changing its inheritance.
JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.
Due to limitations in JAWS 4.5.1, input field labels in the OracleAS TopLink Mapping Workbench are not read properly. Oracle recommends using JAWS 3.7 and version 103 Access Bridge for maximum accessibility.