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.
EclipseLink/Development/DBWS/JDBCUseCases
< EclipseLink | Development | DBWS
Revision as of 13:12, 17 December 2009 by Unnamed Poltroon (Talk) (→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
QueryOperationis invoked by a Web service, the selection criteria for the 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 thejava.sql.ResultSetreturned. In these cases, a simplified XML format is used and the types returned must be simple scalar types (Number, String, Float, etc.)
- Tables
- blah
- Stored Procedures
- blah