Oracle8i SQLJ Developer's Guide and Reference Release 3 (8.1.7) Part Number A83723-01 |
Library | Service | Contents | Index

## 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 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".

### 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 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.

Information about `JDeveloper` is available at the following URL:

    http://technet.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 JVM 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.

- How to set environment variables is specific to the operating system. There may also be OS-specific restrictions. In Windows 95, use the `Environment` tab in the `System` control 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.

- As with any operating system and environment you use, be aware of specific limitations. In particular, the complete, expanded SQLJ command line must not exceed the maximum command-line size, which is 250 characters for Windows 95 and 4000 characters for Windows NT. Consult your operating system documentation.

- On Windows, it is possible that the SQLJ translation process will suspend during compilation. If you encounter this problem, use the translator `-passes` option, which is discussed in "SQLJ Two-Pass Execution (-passes)".

Refer to the Windows platform `README` file for additional information.

| Copyright © 1996-2000, Oracle Corporation. All Rights Reserved. |
Library | Service | Contents | Index