PL/SQL Connector Builder
The core idea of the code generator is to produce the access code exactly to the point the data call is needed, without any further data manipulations or transfer of data.
Code Generation On Development
The PL/SQL Connector Builder generates Java Oracle JDBC code during development.
Mindset For Success
Database driven development.Only Oracle JDBC driver required
No framework is required to call the PL/SQL stored procedures.
Types Of Connector Builder
- Raw : Direct call API to the database with self managed transaction handling.
- JavaRPC : Client call API to the database including automatic transaction handling.
- Batch/Stream Processor : Client call API with cursor processing for batches.
- JavaEE :
- Server Only : JavaEE session beans. Application server managed transactions.
- Client/Server : Client call API, remote call to JavaEE session bean. Application server managed transactions.
- RMI : Client call API, remote call to RMI server bean. RMI server bean manages automatically transactions.
- Spring-HTTP-Remoting : Client call API, remote call via Spring server bean. . Spring server bean manages automatically transactions.
- Rest : planed in future versions
- Soap : planed in future versions
Local Calls
Direct calls to the database.
- Raw
- JavaRPC
- Batch/Stream Processor
- JavaEE : Using local JavaEE session bean.
Remote Calls
Calls to the database are tunneled thru an application server.
- JavaEE : Remote call to JavaEE session bean.
- RMI
- Spring HTTP-Remoting
Calling API
- Client Call API : All PL/SQL Connector of type JavaRPC, Batch/Stream Processor, JavaEE, RMI, Spring-HTTP-Remoting using the same calling API. Switching between these PL/SQL Connectors differs only in different configuration without any change of code.
- Raw : For transaction handling, the connection is added to the call.
- JavaEE : Using JavaEE application server session beans.