Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

EclipseLink/Development/DBWS/JDBCUseCases

< EclipseLink‎ | Development‎ | DBWS
Revision as of 15:05, 17 December 2009 by Michael.norman.oracle.com (Talk | contribs) (Supported Use Cases for non-Oracle Platforms)

Supported Use Cases for non-Oracle Platforms

The design-time utility DBWSBuilder uses JDBC meta-data APIs (java.sql.DatabaseMetaData) to extract information about tables (column names and types) and Stored Procedures (argument names and types) which is then translated into information required by DBWS (EclipseLink Project files, XML Schemas, etc) so that at runtime a Web service client can invoke an operation and receive a response.

  • raw SQL
When a DBWS operation is invoked by a Web service, the selection criteria for a Query can be specified as a SQL SELECT statement. This means that DBWS does not know what information will be returned until the statement has been executed and the java.sql.ResultSet returned. In these cases, a simplified XML format is used and the types returned must be simple scalar types (Number, String, Float, etc.)
  • Tables
When a DBWS operation is invoked by a Web service, the returned table row (or rows plural) is transformed into XML that conforms to an XML Schema. Column name and type information retrieved by the DBWSBuilder is used to generate the XML Schema
  • Stored Procedures
blah

Back to the top