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/Development/DBWS/ParseDDLDS"
< EclipseLink | Development | DBWS
(New page: == Parsing DDL for Metadata ==) |
(→Parsing DDL for Metadata) |
||
| Line 1: | Line 1: | ||
| − | + | = Parsing DDL for Metadata = | |
| + | The primary job of <tt>DBWSBuilder</tt> is to extract metadata from the database about some artifact such as a Table or a StoredProcedure that will be used as the basis of (JAX-WS compliant) Web Service. The <tt>DBWSBuilder</tt> translates the information (fields, arguments, scalar or complex datatypes, etc.) into EclipseLink ORM and OXM files. Thus it is crucial that <tt>DBWSBuilder</tt> get complete and accurate metadata from the database. | ||
| + | |||
| + | For Oracle databases, <tt>DBWSBuilder</tt> uses a modified cut-down version of the JPublisher classes to send SQL queries to Data Dictionary views (<tt>ALL_OBJECTS</tt>, <tt>ALL_ARGUMENTS</tt>, etc.) | ||
Revision as of 16:01, 31 May 2011
Parsing DDL for Metadata
The primary job of DBWSBuilder is to extract metadata from the database about some artifact such as a Table or a StoredProcedure that will be used as the basis of (JAX-WS compliant) Web Service. The DBWSBuilder translates the information (fields, arguments, scalar or complex datatypes, etc.) into EclipseLink ORM and OXM files. Thus it is crucial that DBWSBuilder get complete and accurate metadata from the database.
For Oracle databases, DBWSBuilder uses a modified cut-down version of the JPublisher classes to send SQL queries to Data Dictionary views (ALL_OBJECTS, ALL_ARGUMENTS, etc.)