Classpath Issues

The OracleAS TopLink Mapping Workbench does not display the class(es) to import.: Cause: Your classes are not available for import on the Select Classes dialog box.; Action: Ensure that the class is in your project's classpath (on the project's General properties tab).
Ensure that the class is in the .zip or .jar file. You cannot import compressed classes.

The OracleAS TopLink Mapping Workbench generates an exception error when importing classes.: Cause: OracleAS TopLink's class import utility did not start correctly. One of the classes includes a static initialization method, which may cause the import utility to fail.; Action: Ensure that your project's classpath points to the root folder of your package hierarchy. For example, to import the com.company.class package in the C:\classes\com\company directory, your project classpath should be C:\classes\.

The OracleAS TopLink Mapping Workbench fails to import the class, but does not generate an exception error.: Cause: Ensure that you have properly indicated the directories that contain the domain class(es) to map on the project's General tab.; Action: The classpath containing your JDBC drivers should still be on your system CLASSPATH. The OracleAS TopLink Mapping Workbench classpath is for domain classes only.