Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/FAQ/DBWS"
(→How are Oracle PL/SQL Records and Collections Handled?) |
(→How are Oracle PL/SQL Records and Collections Handled?) |
||
Line 25: | Line 25: | ||
== How are Oracle PL/SQL Records and Collections Handled? == | == How are Oracle PL/SQL Records and Collections Handled? == | ||
− | Oracle PL/SQL Record and Collection types cannot be transported over JDBC. To compensate for this, an anonymous block of PL/SQL code will be generated that contains functions responsible for converting to/from equivalent JDBC and PL/SQL types, based on the information passed to the DBWS Builder. In order for this to work, each PL/SQL record or collection type that will be an IN, IN OUT, OUT or RETURN argument (or any PL/SQL record/collection type nested within these) will need to have an equivalent JDBC type - the name of the type is expected to be in the form <package name>_<type name>. | + | Oracle PL/SQL Record and Collection types cannot be transported over JDBC. To compensate for this, an anonymous block of PL/SQL code will be generated that contains functions responsible for converting to/from equivalent JDBC and PL/SQL types, based on the information passed to the DBWS Builder. In order for this to work, each PL/SQL record or collection type that will be an <tt>IN</tt>, <tt>IN OUT</tt>, <tt>OUT</tt> or <tt>RETURN</tt> argument (or any PL/SQL record/collection type nested within these) will need to have an equivalent JDBC type - the name of the type is expected to be in the form <tt><package name>_<type name></tt>. |
Given the following PL/SQL Package: | Given the following PL/SQL Package: | ||
− | <source lang=" | + | <source lang="plsql" enclose="div"> |
CREATE OR REPLACE PACKAGE MYPKG AS | CREATE OR REPLACE PACKAGE MYPKG AS | ||
TYPE TBL1 IS TABLE OF VARCHAR2(111) INDEX BY BINARY_INTEGER; | TYPE TBL1 IS TABLE OF VARCHAR2(111) INDEX BY BINARY_INTEGER; |
Revision as of 14:34, 25 July 2012
Contents
What is EclipseLink DBWS?
Overview
For the current version, see: Developing Persistence Architectures Using EclipseLink Database Web Services, Release 2.4
For EclispeLink DBWS Overview, see http://www.eclipse.org/eclipselink/documentation/2.4/dbws/overview.htm
Who uses this feature?
Anyone who wishes to expose a database artifact as a Web Service.
Why do they use it?
EclipseLink DBWS provides a simple light-weight metadata model that requires no Java programming, yet is highly extensible.
What technologies apply?
EclipseLink JPA/ORM, MOXy, JAX-WS
What version of JavaSE does DBWS support?
Using the EclipseLink DBWS design-time tools requires JDK 1.6 (or higher) while the DBWS runtime requires JDK 1.5 or higher.
How are Oracle PL/SQL Records and Collections Handled?
Oracle PL/SQL Record and Collection types cannot be transported over JDBC. To compensate for this, an anonymous block of PL/SQL code will be generated that contains functions responsible for converting to/from equivalent JDBC and PL/SQL types, based on the information passed to the DBWS Builder. In order for this to work, each PL/SQL record or collection type that will be an IN, IN OUT, OUT or RETURN argument (or any PL/SQL record/collection type nested within these) will need to have an equivalent JDBC type - the name of the type is expected to be in the form <package name>_<type name>.
Given the following PL/SQL Package:
TYPE TBL1 IS TABLE OF VARCHAR2(111) INDEX BY BINARY_INTEGER;
TYPE ARECORD IS RECORD (
T1 TBL1,
T2 BOOLEAN
);
FUNCTION F1(FOO IN VARCHAR2) RETURN ARECORD;
END MYPKG;
The following equivalent JDBC types are required:
CREATE OR REPLACE TYPE MYPKG_ARECORD AS OBJECT (
T1 MYPKG_TBL1,
T2 BOOLEAN
)