This is a flowchart showing inputs and outputs for the JPublisher publishing process, as described in the accompanying text. In addition to these descriptions, the graphic shows the following:
Input to JPublisher through the command line, properties file, or
INPUT file that includes SQL object types, SQL collection types, PL/SQL packages, server-side Java classes,
DELETE statements, or WSDL files.
The SQLJ translator, which is invoked by JPublisher, is depicted as an entity within the JPublisher product. In contrast, the Java compiler is shown as an external entity. SQLJ source files are shown as the input to the SQLJ translator and Java source files are the output. Java source files, either from the SQLJ translator or generated directly by JPublisher in some circumstances, are shown as input to the Java compiler and Java class files (
.class) as the output.
.class output is shown as optionally going to the database JVM or the client-side or middle-tier JVM. Classes for Web services call-outs are loaded in the database JVM by default.
.sql output, which consists of PL/SQL wrappers and scripts, is shown as optionally going to the database PL/SQL engine. If this happens, it happens by default.
The database is shown to include the PL/SQL engine and database JVM, which includes the SQLJ run time and JDBC driver. The database is also shown to include the metadata that JPublisher checks for defintions of SQL types, PL/SQL packages, and shapes of query results.
User-defined classes, including subclasses of JPublisher-generated classes, are shown as going to the client-side or middle-tier JVM.
The client-side or middle-tier JVM is shown to include the SQLJ run time and JDBC driver.