| Oracle® Application Server Release Notes 10g Release 3 (10.1.3) for Microsoft Windows (64-Bit) on Intel Itanium B28115-01 |
|
 Previous |
 Next |
| Oracle® Application Server Release Notes 10g Release 3 (10.1.3) for Microsoft Windows (64-Bit) on Intel Itanium B28115-01 |
|
Previous |
Next |
This chapter describes issues associated with Oracle TopLink (TopLink). It includes the following topic:
This section describes general issue and workaround. It includes the following topic:
Section 7.1.1, "Links to Hosted Documentation and Web-Based Resources from TopLink Workbench"
Section 7.1.2, "Using Non-ASCII Characters with a JAXB 1.0 TopLink Project"
Section 7.1.3, "TopLink Workbench Look and Feel With Linux GTK"
When using the online help and the hosted documentation, TopLink Workbench requires an internet connection to OTN (Oracle Technology Network). Your PC must have a network connection (including any required proxy information) and an internet browser for use with the TopLink Workbench. If the TopLink Workbench is unable to connect to OTN, some links in the online help or the Welcome page may not work properly.
To configure preferences for an external browser for use with the TopLink Workbench, select Tools > Preferences > Help. Click Browse and select the location of your default Web browser. For more information on Help preferences, go to the Help menu and select Working With TopLink Workbench Preferences.
When you generate class and method names that include non-ASCII characters, TopLink will throw an exception. This problem occurs when creating a JAXB 1.0 TopLink project from an XML schema that contains non-ASCII characters. Ensure that your XML schema does not contain any non-ASCII characters.
When using TopLink Workbench on a PC using the Linux GTK look and feel, do not set the TopLink Workbench Look and Feel Preference to GTK+. Doing so may cause unexpected complications. Oracle recommends using the Metal, Oracle, or CD/Motif look and feel instead. Refer to "Working with TopLink Workbench Preferences" in Oracle TopLink Developer's Guide for complete information.
If a unit of work is synchronized with a Java Transaction API (JTA), an exception will be thrown if it is released. If the current transaction requires that changes not be persisted, the JTA transaction must be rolled back. If you wish to have the transaction rolled back, do so with its API.
