In addition, JPublisher simplifies access to PL/SQL types from Java. Use this approach if you need to generically process any SQL object, collection, reference, or OPAQUE type. If these classes meet your requirements, then you do not need JPublisher. Use generic, weakly typed classes of the oracle.sql package to represent object, object reference, and collection types.
This approach is flexible, but time-consuming and error-prone. JPublisher generates initial versions of the subclasses, to which you can add any desired functionality. Instead of directly using JPublisher-generated classes, you can:Įxtend the generated classes. These classes have wrapper methods to call the stored procedures in a PL/SQL package. JPublisher can also generate classes for PL/SQL packages. In this scenario, a wr apper method is a Java method that invokes a stored procedure, which runs in Oracle Database. If the object type has stored procedures, then JPublisher can generate wrapper methods to invoke the stored procedures. The utility generates the accessor methods, get XXX () and set XXX (), for each attribute of an object type. In addition, there is a corresponding Java type for each attribute of the SQL object type. For example, a Person class is associated with a corresponding PERSON SQL type. The term, strongly typed, indicates that a particular Java type is associated with a particular user-defined SQL type, such as an object type.
