View source for EclipseLink/Development/DBWS/JDBCUseCases

== Supported Use Cases for non-Oracle Platforms ==
The design-time utility <code>DBWSBuilder</code> uses JDBC meta-data APIs (<code>java.sql.DatabaseMetaData</code>) 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 <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
: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
: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.)