| Summary: | DBWSBuilder should generate CREATE and DROP DDL for 'shadow' JDBC types compatible with PL/SQL record + collection types | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Mike Norman <michael.norman> |
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | eclipselink.dbws-inbox |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Mike Norman
Assume that we are using a schema U1 and have defined a new Object type EMPLOYEE_CONTACT :
CREATE OR REPLACE TYPE EMPLOYEE_CONTACT IS OBJECT (
EMP_NUMBER NUMERIC,
EMP_NAME VARCHAR2(50),
HOME_CONTACT U2.CONTACT,
WORK_CONTACT U2.CONTACT
);
You can see that this Object type is using a type defined in the U2 schema:
CREATE OR REPLACE TYPE CONTACT IS OBJECT (
HOME VARCHAR2(40),
BUSINESS VARCHAR2(40)
);
The new DBWSBuilder uses the DBMS_METADATA package to extract the DDL for any
table/procedure/package or type - the U1schema must have the
SELECT_CATALOG_ROLE role assigned to it in order for the DBMS_METADATA package
to work:
SQL> grant select_catalog_role to U1;
Grant succeeded.
So, in addition to generating DDL for 'shadow' JDBC types compatible with PL/SQL record + collection types, we must also generate some 'SYSDBA' commands as well
separate out issue of data dictionary access from DDL generation: - https://bugs.eclipse.org/bugs/show_bug.cgi?id=362585 Oracle DDL Parser should resolve types from other schemas fix in SVN revisions: 10702, 10710, 10715, 10721, 10723 New class o.e.p.tools.dbws.oracle.ShadowDDLGenerator generates same 'shadow' DDL that the JPublisher code did The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |