|Oracle8i SQLJ Developer's Guide and Reference
Release 3 (8.1.7)
Part Number A83723-01
The discussion in this book assumes that you are coding manually in a UNIX environment for English-language deployment. However, you can use SQLJ on other platforms and with IDEs. There is also NLS support for deployment to other languages. This section introduces these topics:
Oracle SQLJ support for native languages and character encodings is based on Java's built-in NLS capabilities.
file.encoding properties of the JVM determine appropriate language and encoding for translator and runtime messages. The SQLJ
-encoding option determines encoding for interpreting and generating source files during translation.
For information, see "NLS Support in the Translator and Runtime".
Oracle SQLJ includes a programmatic API so that it can be embedded in integrated development environments (IDEs) such as Oracle JDeveloper. The IDE takes on a role similar to that of the
sqlj script used as a front end in Solaris, invoking the translator, semantics-checker, compiler, and customizer.
Oracle JDeveloper is a Windows NT-based visual development environment for Java programming. The JDeveloper Suite enables developers to build multi-tier, scalable Internet applications using Java across the Oracle Internet Platform. The core product of the suite--the JDeveloper Integrated Development Environment--excels in creating, debugging, and deploying component-based applications.
The JDeveloper Suite includes Oracle JDeveloper, Oracle Application Server, Oracle8i Enterprise Edition, and Oracle Procedure Builder.
The Oracle JDBC OCI and Thin drivers are included with JDeveloper, as well as drivers to access an Oracle Lite database.
JDeveloper's compilation functionality includes an integrated Oracle SQLJ translator so that your SQLJ application is translated automatically as it is compiled.
JDeveloper is available at the following URL:
Note the following if you are using a Windows platform instead of Solaris:
kshon NT) that permits a different file name syntax.
sqlj, that you use to invoke the SQLJ translator. On Windows, Oracle SQLJ instead provides an executable file,
sqlj.exe. Using a script is not feasible on Windows platforms because
.batfiles on these platforms do not support embedded equals signs (=) in arguments, string operations on arguments, or wildcard characters in file name arguments.
Environmenttab in the
Systemcontrol panel. Additionally, since Windows 95 does not support the "=" character in variable settings, SQLJ supports the use of "#" instead of "=" in setting
SQLJ_OPTIONS, an environment variable that SQLJ can use for option settings. Consult your operating system documentation regarding settings and syntax for environment variables, and be aware of any size limitations.
-passesoption, which is discussed in "SQLJ Two-Pass Execution (-passes)".
Refer to the Windows platform
README file for additional information.