The eclipselink-dbws-schema.xsd file is used only with EclipseLink database Web services (see Section 2.18, "Considering EclipseLink Database Web Service Architecture"). A EclipseLink database Web service automatically generates this file from your database table metadata and uses it to derive element tag names and types.

+

The eclipselink-dbws-schema.xsd file is used only with EclipseLink database Web services (see [[Introduction to EclipseLink#Considering EclipseLink Database Web Service Architecture|Considering EclipseLink Database Web Service Architecture]]). A EclipseLink database Web service automatically generates this file from your database table metadata and uses it to derive element tag names and types.

XSD File Format

The eclipselink-dbws.xml file XSD is eclipselink-dbws_11_1_1.xsd and it is located in the <ECLIPSELINK_HOME>\xsds directory.

eclipselink-dbws-schema.xsd

The eclipselink-dbws-schema.xsd file is used only with EclipseLink database Web services (see Considering EclipseLink Database Web Service Architecture). A EclipseLink database Web service automatically generates this file from your database table metadata and uses it to derive element tag names and types.

An XML schema .xsd file is generated using the following two rules:

table name: translate any characters not supported by XML, then convert to lower case (to_lowercase), and then add suffix Type. This will result in a top-level complex element type in the .xsd file.

column name: translate characters, and then convert to lower case (to_lowercase). This will result in an element tag name.
Note: This includes all columns, with BLOB columns being automatically mapped to xsd:base64Binary and, optionally, included in-line to the XML document, or handled as binary attachments (swaRef-style).

This table shows metadata from a typical database, and Corresponding eclipselink-dbws-schema.xsd shows the corresponding eclipselink-dbws-schema.xsd file that the EclipseLink database Web service generates from it.

EclipseLink logging level to be inserted in the EclipseLink database Web service sessions.xml file.
Controls the amount and detail of log output by configuring the log level (in ascending order of information) to one of the following java.util.logging.
Level values:

off-Disable logging.

severe-Logs exceptions indicating EclipseLink cannot continue, as well as any exceptions generated during login. This includes a stack trace.

warning-Logs exceptions that do not force EclipseLink to stop, including all exceptions not logged with severe level. This does not include a stack trace.

info-Logs the login/logout per sever session, including the user name. After acquiring the session, detailed information is logged.

config-Logs only login, JDBC connection, and database information.

fine-Logs SQL.

finer-Similar to warning. Includes stack trace.

finest-Includes additional low level information.

No

INFO

targetNameSpace

The URI of the target namespace that the EclipseLink database Web service inserts into the eclipselink-dbws-schema.xsd file.

No

urn: + projectName

eclipselink-dbws-build.xml File

<?xmlversion="1.0"encoding="UTF-8"?><dbws-builderxmlns:xsd="http://www.w3.org/2001/XMLSchema"<properties><propertyname="projectName">test</property><propertyname="driver">oracle.jdbc.OracleDriver</property><propertyname="password">tiger</property><propertyname="url">jdbc:oracle:thin:@localhost:1521:ORCL</property><propertyname="username">scott</property></properties><tablecatalogPattern="%"schemaPattern="SCOTT"tableNamePattern="XR_EMP"><procedurereturnType="xr_empType"catalogPattern="SOME_PKG"schemaPattern="SCOTT"procedurePattern="GetEmployeeByEMPNO_DEPTNO"/><sqlname="findXREmpByName"isCollection="true"returnType="xr_empType"><text><![CDATA[select * from XR_EMP where ENAME like ?]]></text><bindingname="ENAME"type="xsd:string"/></sql></table><sqlname="employeeInfo"simpleXMLFormatTag="employee-info"xmlTag="aggregate-counts"><text><![CDATA[select count(*) as "COUNT", max(SAL) as "MAX-Salary" from EMP]]></text></sql></dbws-builder>

For more information, see the following:

[[#Creating Deployment Files for EclipseLink Database Web Services]

[#What You May Need to Know About Builder Operations]

What You May Need to Know About Builder Operations

The following are the builder operations:

procedure-You use this operation to specify a stored procedure.

table-You use this operation to specify a database table.

sql-You use to this operation to specify an SQL statement.

The following tables describe attributes of builder operations that eclipselink-dbws-build.xml File uses.
This table lists attributes common to all three builder operations.

Common Attributes of Builder Operations

Attribute

Description

Default

name

Name of the operation.

None

isCollection

Specifies whether or not the procedure returns multiple results. The following are valid values:

true - the operation returns more than a single row.

false - the operation returns a single row.

false

isSimpleXMLFormat

Specifies whether or not the procedure returns information in the Simple XML Format (SXF). The following are valid values:

The name of the root-level Simple XML Format element-tag.
For more information, see Unstructured Data.

<simple-xml-format>

xmlTag

The name of the grouping XML element-tag for rows.
For more information, see Unstructured Data.

<simple-xml>

binaryAttachment

Specifies whether or not the operation returns binary data as a SOAP attachment. The following are valid values:

true - the operation returns binary data as a SOAP attachment.

false - the operation does not return binary data as a SOAP attachment.

false

returnType

Specifies a return type when the operation's return type cannot be deduced from database metadata. Valid values are any type that the eclipselink-dbws-schema.xsd file defines. For more information, see #eclipselink-dbws-schema.xsd.

Note: This attribute is optional.

None

This table lists attributes of the procedure operation.

Attributes of the procedure Operation

Attribute

Description

catalogPattern

A pattern that matches one or more catalog names in the database identified by the parent operation (supports SQL-92 % wild-card).

schemaPattern

A pattern that matches one or more schema names in the database identified by the parent operation (supports SQL-92 % wild-card).

procedurePattern

A pattern that matches one or more stored procedure, stored function, or stored trigger names in the database identified by the parent operation (supports SQL-92 % wild-card).

This table lists attributes of the table operation.

Attributes of the table Operation

Attribute

Description

catalogPattern

A pattern that matches one or more catalog names in the database identified by the parent operation (supports SQL-92 % wild-card).

schemaPattern

A pattern that matches one or more schema names in the database identified by the parent operation (supports SQL-92 % wild-card).

tableNamePattern

A pattern that matches one or more table names in the database identified by the parent operation (supports SQL-92 % wild-card).