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

Difference between revisions of "EclipseLink/Examples/DBWS/DBWSBasicAutoGenSchema"

Line 8: Line 8:
 
__NOTOC__  
 
__NOTOC__  
  
== sdfsdf ==
+
== EclipseLink DBWS Service based on schema-formatted Results from custom SQL SELECT statements ==
 +
This example shows an extension to an existing use case where the Web service exposes the results of executing some custom SQL SELECT statements; however, the 'shape' of the returned result is determined at design-time, not runtime.
  
The use-case is the creation of a Web service that exposes the results of executing some custom SQL <tt>SELECT</tt> statement, without exposing the actual SQL. Currently, DBWS determines the 'shape' of the returned result at the time the <tt>SELECT</tt> statement is executed (i.e. at runtime, not design-time). For example, the  following <tt>DBWSBuilder</tt> file produces a SXF (Simplified XML Format) document where the element tag names are direct copies of column names:
+
Under normal circumstances, executing some custom SQL <tt>SELECT</tt> statement returns <code>java.sql.ResultSet</code>'s from which one can determine the name and datatype of the columns of information. Since this information is not available until the SQL is executed at runtime, DBWS has a
 +
 
 +
 
 +
Currently, DBWS determines the 'shape' of the returned result at the time the <tt>SELECT</tt> statement is executed (i.e. at runtime, not design-time). For example, the  following <tt>DBWSBuilder</tt> file produces a SXF (Simplified XML Format) document where the element tag names are direct copies of column names:
 
<source lang="xml">
 
<source lang="xml">

Revision as of 14:07, 13 June 2011


EclipseLink DBWS Service based on schema-formatted Results from custom SQL SELECT statements

This example shows an extension to an existing use case where the Web service exposes the results of executing some custom SQL SELECT statements; however, the 'shape' of the returned result is determined at design-time, not runtime.

Under normal circumstances, executing some custom SQL SELECT statement returns java.sql.ResultSet's from which one can determine the name and datatype of the columns of information. Since this information is not available until the SQL is executed at runtime, DBWS has a


Currently, DBWS determines the 'shape' of the returned result at the time the SELECT statement is executed (i.e. at runtime, not design-time). For example, the following DBWSBuilder file produces a SXF (Simplified XML Format) document where the element tag names are direct copies of column names:

 

Back to the top