Java Importer Limitations
Import Dialog and JAWS
When trying to select Java classes from the Import Java Classes dialog, pressing Tab does not move focus to the trees in the Select Java Classes window. However, you can still use this dialog by
typing in the name of the class, or you can find the classes by looking in the Java directory structure.
Java/PL/SQL Issues and Requirements
java.lang.String
objects are mapped to varchar2
,
which has a size limitation of 32KB.
- A Forms application must not
reference an invalid Java object through the generated PL/SQL package.
Java in the Forms Server
- Java imported with the Java Importer and referenced
in Forms applications must exist in the middle-tier of the application.
- When PL/SQL calls imported Java on the Forms Server,
a separate Java virtual machine (JVM) starts for each runtime process started.
The amount of memory used by each JVM includes the overhead of the JVM process
plus the memory used for Java application execution and Java object storage.
Builder CLASSPATH Updates
- Once a Java class has been
loaded into a Form Builder session, changes to the class are not reflected
in the running of the class. To run the class with the changes reflected,
you must restart the builder.
- If you have imported a Java class during a Form
Builder session and then make changes to the class, you must restart the builder
and then import the changed Java class. The Java Importer does not pick up
changes made to a Java class during the same Form Builder session in which
that class was previously imported.
- If you edit the
CLASSPATH
during a Form builder session, you
must restart the Builder so the Java Importer can see the CLASSPATH
changes.
Note:
You can still import classes added to the CLASSPATH
during a Builder session, even though they are not listed in the Import
Java Classes dialog box. To import a class that is now in the CLASSPATH
but not listed in the Import Java Classes dialog box, enter the fully qualified
class name in the Import Classes text field.