Packaging – source code versus .jar file
The creation of a Java class via the preceding method (creating the Java source and compiling it using CREATE AND COMPILE JAVA SOURCE NAMED …) is fine for simple, one-off, implementation, but such an approach has a number of limitations:
Many utility methods would be better off being moved to other classes, for example,
getConnection,getPrecisionScale,getSRIDResolving errors and dependent class/JAR references is difficult the more complex a class becomes
It is a very difficult method to scale when one wants to add more methods to an existing Java source, or if you want to build other classes that rely on earlier loaded sources
A GUI development tool such as JDeveloper is a solid tool for developing small, simple Java classes, to larger scale and more complex packages of Java classes, and compiling and testing, before packaging into suitable JAR files (ours will be called J6365EN.jar), before trying to load into the Oracle database.
In our first example...
