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.
Difference between revisions of "EclipseLink/Development/DBWS/JDBCUseCases"
< EclipseLink | Development | DBWS
(→Supported Use Cases for non-Oracle Platforms) |
(→Supported Use Cases for non-Oracle Platforms) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
* raw SQL | * raw SQL | ||
| − | : | + | :The selection criteria for a Query can be specified as a SQL <tt>SELECT</tt> statement. This means that DBWS does not know what information will be returned until the statement has been executed and the <code>java.sql.ResultSet</code> returned. In these cases, a [[EclipseLink/Development/DBWS/FunctionalSpecification#SXF_.28Simple_XML_Format.29|simplified XML format]] is used and the types returned must be simple scalar types (Number, String, Float, etc.) |
* Tables | * Tables | ||
| − | : | + | :A returned table row (or row<b>s</b> plural) is transformed into XML that conforms to an XML Schema. For each table, a <tt>complexType</tt> is generated with each column as an <tt>element</tt> of the <tt>complexType</tt>. The XML datatypes used are simple scalar types (<code><xsd:string></code>, <code><xsd:decimal></code>, <code><xsd:datetime></code>, etc.) |
* Stored Procedures | * Stored Procedures | ||
| − | : | + | :A Stored Procedure can invoke complex business logic encapsulated within the database. The arguments to the procedure are simple scalar types (Number, String, Float, etc.) |
Latest revision as of 15:34, 17 December 2009
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
- 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.ResultSetreturned. In these cases, a simplified XML format is used and the types returned must be simple scalar types (Number, String, Float, etc.)
- Tables
- A returned table row (or rows plural) is transformed into XML that conforms to an XML Schema. For each table, a complexType is generated with each column as an element of the complexType. The XML datatypes used are simple scalar types (
<xsd:string>,<xsd:decimal>,<xsd:datetime>, etc.)
- Stored Procedures
- A Stored Procedure can invoke complex business logic encapsulated within the database. The arguments to the procedure are simple scalar types (Number, String, Float, etc.)