Generated Java Source Structure

The generated Java code is inspired by Java EE core patterns.

Generated Java Code Class Groups

  • Implementation classes :
    • Generated JDBC Java code.
    • For each PL/SQL function, PL/SQL procedure and PL/SQL package a Java class is generated.
    • Java classes for PL/SQL functions and PL/SQL procedures have one method call(..) to call the PL/SQL stored procedure.
    • Java classes for PL/SQL packages have one method for each PL/SQL function or PL/SQL procedure.
    • In-parameter of the PL/SQL stored procedure defines the argument list of the Java method.
    • If the PL/SQL stored procedure has no out-parameter the Java methods return type is void.
    • If the PL/SQL stored procedure has one out-parameter the Java methods return type is equivalent Java type.
    • If the PL/SQL stored procedure has more out-parameters the Java methods return type is a Java transfer object.
    • The service interface is implemented here.
    • The postfix ServiceImpl is appended.
  • Transfer object classes :
    • A Java transfer object is created than the calling PL/SQL stored procedure returns more than one out-parameter. All return values of the PL/SQL stored procedure are attributes of Java transfer object. The Java transfer object class name is the camel case name of the PL/SQL stored procedure appended with TO.
    • For any PL/SQL object type a Java transfer object is generated in camel case naming notation.
  • Service interface :
    • For each generated implementation class a service interface is generated.
    • The service interface declares all methods to PL/SQL stored procedures.
    • The postfix Service is appended.
  • Remote call factory class :
    • One factory class is generated per Connector Builder.
    • For each generated implementation class and service interface and a static service getter method getServiceXXX() is generated.
    • The static getServiceXXX() method instantiates a service with the configured data source class.
    • The default name is the Connector Builder name in camel case appended by RPCFactory.
  • Data source class :
    • One data source class is generated per remote call factory class.
    • This class configures the date source connection and will not be overwritten if the class exists. So individual configurations can be made without being overwritten.
    • Each data source class has a static method getDataSource() which is called by the factory.
    • The default name is the database user name in camel case appended by DataSource.
  • Resource files :
    • One resource file is generated per data source class.
    • In the resource file the JDBC connection parameter are defined.
    • The resource file will not be overwritten if the file exists. So individual configurations can be made without being overwritten.
    • The default name is the database user name in lower case appended by .properties.