java.lang.String
objects are mapped to varchar2
,
which has a size limitation of 32KB.
A report must not reference an invalid Java object through the generated PL/SQL package.
Java imported with the Java Importer and referenced in reports must exist in the middle-tier of the application.
When PL/SQL calls imported Java on the Reports 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.
Once a Java class has been loaded into a Reports 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 Reports Builder.
If you have imported a Java class during a Reports Builder session and then make changes to the class, you must restart Reports Builder and then import the changed Java class. The Java Importer does not pick up changes made to a Java class during the same Reports Builder session in which that class was previously imported.
If you edit the CLASSPATH during a Reports Builder session, you must restart Reports 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 field.
Importing a Java Class into PL/SQL
Copyright © 1984, 2005, Oracle. All rights reserved.