|Oracle8i SQLJ Developer's Guide and Reference
In addition to the
AuditorInstaller discussed in "AuditorInstaller Customizer for Debugging", there are other considerations to be aware of regarding debugging:
-linemap) that can aid in debugging your SQLJ code.
-linemap flag instructs SQLJ to map line numbers from a SQLJ source code file to locations in the corresponding
.class file. (This will be the
.class file created during compilation of the
.java file generated by the SQLJ translator.) As a result of this, when Java runtime errors occur, the line number reported by the Java VM is the line number in the SQLJ source code, making it much easier to debug.
See "Line-Mapping to SQLJ Source File (-linemap)" for more information about this flag.
If you are loading SQLJ source into the server, using the server-side embedded translator to translate it, the debug option instructs the server-side compiler to output debugging information when a
.java source file is compiled in the server. This is equivalent to using the
-g option when running the standard
javac compiler on a client. This does not aid in debugging your SQLJ code in particular, but aids in debugging your Java code in general.
See "Option Support in the Server Embedded Translator" for more information about this option and information about how to set options in the server.
Oracle SQLJ is fully integrated into the Oracle JDeveloper visual programming tool.
JDeveloper also includes an integrated debugger that supports SQLJ. SQLJ statements, like standard Java statements, can be debugged in-line as your application executes. Reported line numbers map back to the line numbers in your SQLJ source code (as opposed to in the generated Java code).
See "SQLJ in JDeveloper and Other IDEs" for an introduction to JDeveloper.