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.
Difference between revisions of "EclipseLink/UserGuide/DBWS/Overview"
| Line 1: | Line 1: | ||
<div style="float:right;border:1px solid #000000;padding:5px;max-width:500px;">__TOC__</div> | <div style="float:right;border:1px solid #000000;padding:5px;max-width:500px;">__TOC__</div> | ||
| − | ==DBWS Overview== | + | ==EclipseLink DBWS Overview== |
| + | The goal of EclipseLink DBWS is to enable simple and efficient access to relational database artifacts via a Web Service, extending EclipseLink's core capabilities while leveraging existing components (ORM, OXM). | ||
| − | + | EclipseLink DBWS has two parts: a design-time tooling component and a runtime provider component that takes a service descriptor (along with related deployment artifacts) and realizes it as a JAX-WS 2.0 Web service. The runtime provider uses EclipseLink to bridge between the database and the XML SOAP Messages used by Web service clients. | |
| − | EclipseLink | + | An EclipseLink DBWS service may be comprised of any number of '''operations''' of which there are 4 types: |
| − | + | ||
| − | + | ||
# Insert - inserts into the database persistent entities described by an XML document. | # Insert - inserts into the database persistent entities described by an XML document. | ||
# Update - updates database persistent entities described by an XML document. | # Update - updates database persistent entities described by an XML document. | ||
| Line 15: | Line 14: | ||
#* EclipseLink Expressions | #* EclipseLink Expressions | ||
| − | The XML documents used by | + | The XML documents used by an '''operation''' conform to an XML Schema Definition <tt>.xsd</tt> document auto-generated by the design-time tooling. Alternatively, if no <tt>.xsd</tt> is available, a pre-defined simple XML format (SXF) can be used. |
===Configuration=== | ===Configuration=== | ||
| − | The metadata for an DBWS service is contained in an easy-to-read service descriptor | + | The metadata for an EclipseLink DBWS service is contained in an easy-to-read service descriptor file. The internal configuration requirements are minimal and omitted fields have simple defaults, allowing for both auto-generation by tools or manual editing. Existing EclipseLink metadata - ORM and OXM Projects - is handled by existing EclipseLink <tt>sessions.xml</tt> capabilities. |
===XML Schema Definition (.xsd)=== | ===XML Schema Definition (.xsd)=== | ||
| − | + | An EclipseLink DBWS service requires an XML Schema Definition <tt>.xsd</tt> file to specify how returned information from the database is shaped. The EclipseLink OXM map handles converting information from the database to XML, giving the user access to the complete range of EclipseLink Object-to-XML mapping capabilities. If no schema is provided by the user, a pre-defined Simple XML Format (SXF) can be used. | |
<blockquote style="padding:4px;border:1px solid black;"> | <blockquote style="padding:4px;border:1px solid black;"> | ||
SXF uses information only available at the time of query execution to build the XML element-tag names; thus, these XML documents cannot be validated against any schema. | SXF uses information only available at the time of query execution to build the XML element-tag names; thus, these XML documents cannot be validated against any schema. | ||
</blockquote> | </blockquote> | ||
| − | ===Auto-generation of | + | ===Auto-generation of An EclipseLink DBWS service=== |
The design-time tooling will auto-generate a DBWS service, creating the service descriptor and all required deployment artifacts. | The design-time tooling will auto-generate a DBWS service, creating the service descriptor and all required deployment artifacts. | ||
Revision as of 14:53, 12 March 2009
EclipseLink DBWS Overview
The goal of EclipseLink DBWS is to enable simple and efficient access to relational database artifacts via a Web Service, extending EclipseLink's core capabilities while leveraging existing components (ORM, OXM).
EclipseLink DBWS has two parts: a design-time tooling component and a runtime provider component that takes a service descriptor (along with related deployment artifacts) and realizes it as a JAX-WS 2.0 Web service. The runtime provider uses EclipseLink to bridge between the database and the XML SOAP Messages used by Web service clients.
An EclipseLink DBWS service may be comprised of any number of operations of which there are 4 types:
- Insert - inserts into the database persistent entities described by an XML document.
- Update - updates database persistent entities described by an XML document.
- Delete - removes from the database persistent entities described by an XML document.
- Query - retrieves from the database persistent entities described by an XML document.
Selection criteria for Query operations can be specified by:- custom SQL
- Stored Procedures
- EclipseLink Expressions
The XML documents used by an operation conform to an XML Schema Definition .xsd document auto-generated by the design-time tooling. Alternatively, if no .xsd is available, a pre-defined simple XML format (SXF) can be used.
Configuration
The metadata for an EclipseLink DBWS service is contained in an easy-to-read service descriptor file. The internal configuration requirements are minimal and omitted fields have simple defaults, allowing for both auto-generation by tools or manual editing. Existing EclipseLink metadata - ORM and OXM Projects - is handled by existing EclipseLink sessions.xml capabilities.
XML Schema Definition (.xsd)
An EclipseLink DBWS service requires an XML Schema Definition .xsd file to specify how returned information from the database is shaped. The EclipseLink OXM map handles converting information from the database to XML, giving the user access to the complete range of EclipseLink Object-to-XML mapping capabilities. If no schema is provided by the user, a pre-defined Simple XML Format (SXF) can be used.
SXF uses information only available at the time of query execution to build the XML element-tag names; thus, these XML documents cannot be validated against any schema.
Auto-generation of An EclipseLink DBWS service
The design-time tooling will auto-generate a DBWS service, creating the service descriptor and all required deployment artifacts.