Alternative Development Scenarios

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:

• NLS support

• SQLJ in IDEs

• Windows considerations

SQLJ NLS Support

Oracle SQLJ support for native languages and character encodings is based on Java's built-in NLS capabilities.

The standard user.language and file.encoding properties of the Java VM 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".

SQLJ in JDeveloper and Other IDEs

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 that is similar to that of the sqlj script that is used as a front-end in Solaris, invoking the translator, semantics-checker, compiler, and customizer.

Oracle JDeveloper is a Windows-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.

Information about JDeveloper is available at the following URL:

http://technet.us.oracle.com

Windows Considerations

Note the following if you are using a Windows platform instead of Solaris:

• This manual uses Solaris/UNIX syntax. Use platform-specific file names and directory separators (such as "\" on Windows) that are appropriate for your platform, because your Java VM expects file names and paths in the platform-specific format. This is true even if you are using a shell (such as ksh on NT) that permits a different file name syntax.

• For Solaris, Oracle SQLJ provides a front-end script, 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 .bat files on these platforms do not support embedded equals signs (=) in arguments, string operations on arguments, or wildcard characters in file name arguments.

• Be aware of any limitations for the maximum size of your command line and environment variables.

• On Windows, the SQLJ translation process may sometimes suspend during compilation. If you encounter this problem, use the translator -passes option, which is discussed in "Run SQLJ in Two Passes (-passes)".

Refer to the Windows platform README file for additional information.

---