Depending on the type of application you are deploying, you may need to create any of the following deployment files:

Depending on the type of application you are deploying, you may need to create any of the following deployment files:

* [[#project.xml File|project.xml File]]

* [[#project.xml File|project.xml File]]

* [[#sessions.xml File|sessions.xml File]]

* [[#sessions.xml File|sessions.xml File]]

−

* [[#eclispelink-dbws-schema.xsd|eclispelink-dbws-schema.xsd]]

Workbench provides the ability to [[Creating%20a%20Project%20(ELUG)#Exporting Project Information)|create deployment files from a Workbench project]]. After you build a project, you have two options to create the deployment files:

Workbench provides the ability to [[Creating%20a%20Project%20(ELUG)#Exporting Project Information)|create deployment files from a Workbench project]]. After you build a project, you have two options to create the deployment files:

Line 28:

Line 32:

'''Note:''' If you are using JPA, you can use annotations to specify most of what you formerly specified in deployment descriptors. Use deployment descriptors to override annotations or specify options not supported by annotations.

'''Note:''' If you are using JPA, you can use annotations to specify most of what you formerly specified in deployment descriptors. Use deployment descriptors to override annotations or specify options not supported by annotations.

|}

|}

+

Line 36:

Line 41:

====XSD File Format====

====XSD File Format====

−

The <tt>project.xml</tt> file XSD is <tt>eclispelink-object-persistence_11_1_1.xsd</tt> and it is located in the ''<tt><ECLIPSELINK_HOME></tt>''<tt>\config\xsds</tt> directory.

+

The <tt>project.xml</tt> file XSD is <tt>persistence_1_0.xsd</tt> and it is located in the ''<tt><ECLIPSELINK_HOME></tt>''<tt>\xsds</tt> directory.

−

+

+

See [[EclipseLink/XSDs]] for more information.

====POJO Applications and Project Metadata====

====POJO Applications and Project Metadata====

Line 44:

Line 49:

The <tt>project.xml</tt> file provides a simple and flexible way to configure, modify, and troubleshoot the project metadata. Because of these attributes, the <tt>project.xml</tt> file is the preferred way to configure an EclipseLink project.Workbench provides a graphical tool to build and edit the <tt>project.xml</tt> file. For information on creating projects with Workbench, see [[#Creating the project.xml File with Workbench|Creating the project.xml File with Workbench]].

The <tt>project.xml</tt> file provides a simple and flexible way to configure, modify, and troubleshoot the project metadata. Because of these attributes, the <tt>project.xml</tt> file is the preferred way to configure an EclipseLink project.Workbench provides a graphical tool to build and edit the <tt>project.xml</tt> file. For information on creating projects with Workbench, see [[#Creating the project.xml File with Workbench|Creating the project.xml File with Workbench]].

−

Line 50:

Line 54:

For a JPA application, you can express project metadata using JPA annotations, <tt>persistence.xml</tt>, <tt>orm.xml</tt>, and EclipseLink JPA annotation and <tt>persistence.xml</tt> property extensions. The EclipseLink JPA persistence provider interprets all these sources of metadata to create an in-memory EclipseLink session and project at run time.

For a JPA application, you can express project metadata using JPA annotations, <tt>persistence.xml</tt>, <tt>orm.xml</tt>, and EclipseLink JPA annotation and <tt>persistence.xml</tt> property extensions. The EclipseLink JPA persistence provider interprets all these sources of metadata to create an in-memory EclipseLink session and project at run time.

−

Using EclipseLink JPA, you also have the option of specifying your metadata using EclipseLink <tt>sessions.xml</tt> and <tt>project.xml</tt> while accessing your persistent classes using JPA and an <tt>EntityManger</tt>. For more information, see [[Using%20EclipseLink%20JPA%20Extensions%20(ELUG)#What You May Need to Know About EclipseLink JPA Overriding Mechanisms|What You May Need to Know About EclipseLink JPA Overriding Mechanisms]].

+

Using EclipseLink JPA, you also have the option of specifying your metadata using EclipseLink <tt>sessions.xml</tt> and <tt>project.xml</tt> while accessing your persistent classes using JPA and an <tt>EntityManager</tt>. For more information, see [[Using%20EclipseLink%20JPA%20Extensions%20(ELUG)#What You May Need to Know About EclipseLink JPA Overriding Mechanisms|What You May Need to Know About EclipseLink JPA Overriding Mechanisms]].

−

+

Line 64:

Line 67:

'''Note'''<nowiki>:</nowiki> You can name this file with a name other than <tt>project.xml</tt><nowiki>; however, for clarity, this discussion assumes that the file has not been renamed.</nowiki>

'''Note'''<nowiki>:</nowiki> You can name this file with a name other than <tt>project.xml</tt><nowiki>; however, for clarity, this discussion assumes that the file has not been renamed.</nowiki>

|}

|}

−

Line 71:

Line 73:

* From an application, instantiate the <tt>DeploymentXMLGenerator</tt> and your java source. Call the following method:<tt>generate (</tt>''<tt><MW_Project.mwp></tt>''<tt>,</tt> ''<tt><output file.xml></tt>''<tt>)</tt>

* From an application, instantiate the <tt>DeploymentXMLGenerator</tt> and your java source. Call the following method:<tt>generate (</tt>''<tt><MW_Project.mwp></tt>''<tt>,</tt> ''<tt><output file.xml></tt>''<tt>)</tt>

Before you use either method, ensure that your classpath includes the ''<tt><ECLIPSELINK_HOME></tt>''<tt>\config</tt> directory.

+

Before you use either method, ensure that your classpath includes the ''<tt><ECLIPSELINK_HOME></tt>''<tt>\jlib\eclipselink.jar</tt> and ''<tt><ECLIPSELINK_HOME></tt>''<tt>\utils\workbench\jlib\eclipselinkmw.jar</tt> files.

'''Note:''' If you are using EJB 3.0, you can use annotations to specify most of what you formerly specified in the <tt>project.xml</tt> file. To override annotations or specify options not supported by annotations, you can still provide a <tt>project.xml</tt> file in your EJB 3.0 application. For more information on what annotations are currently supported, see ''[http://www.oracle.com/technology/documentation/index.html Oracle Fusion Middleware Enterprise JavaBeans Developer's Guide for Oracle Containers for Java EE]''

+

'''Note:''' If you are using EJB 3.0, you can use annotations to specify most of what you formerly specified in the <tt>project.xml</tt> file. To override annotations or specify options not supported by annotations, you can still provide a <tt>project.xml</tt> file in your EJB 3.0 application.

|}

|}

Line 85:

Line 87:

===sessions.xml File===

===sessions.xml File===

Each EclipseLink project belongs to an EclipseLink ''session''. A session is the facade through which an application accesses EclipseLink functionality (for more information on sessions, see [[EclipseLink/UserGuide/Using EclipseLink Sessions (ELUG)|EclipseLink Sessions]]).

Each EclipseLink project belongs to an EclipseLink ''session''. A session is the facade through which an application accesses EclipseLink functionality (for more information on sessions, see [[EclipseLink/UserGuide/Using EclipseLink Sessions (ELUG)|EclipseLink Sessions]]).

−

====XSD File Format====

====XSD File Format====

−

The <tt>sessions.xml</tt> file XSD is <tt>eclipse_persistence_sessions_1_0.xsd</tt> and it is located in the ''<tt><ECLISPELINK_HOME></tt>''<tt>\config\xsds</tt> directory as well as on the web at http://www.eclipse.org/eclipselink/xsds/eclipse_persistence_sessions_1_0.xsd.

+

The <tt>sessions.xml</tt> file XSD is <tt>eclipse_persistence_sessions_1_0.xsd</tt> and it is located in the ''<tt><ECLIPSELINK_HOME></tt>''<tt>\xsds</tt> directory as well as on the web at http://www.eclipse.org/eclipselink/xsds/eclipse_persistence_sessions_1_0.xsd.

When you use the XSD formatted <tt>sessions.xml</tt> file, the EclipseLink run time separates <tt>sessions.xml</tt> file validation from session instantiation. Separating XML file formatting problems from Session Manager session instantiation problems simplifies troubleshooting. Exceptions thrown during validation clearly indicate that the failure is due to an invalid <tt>sessions.xml</tt> file, as the following illustrates.

When you use the XSD formatted <tt>sessions.xml</tt> file, the EclipseLink run time separates <tt>sessions.xml</tt> file validation from session instantiation. Separating XML file formatting problems from Session Manager session instantiation problems simplifies troubleshooting. Exceptions thrown during validation clearly indicate that the failure is due to an invalid <tt>sessions.xml</tt> file, as the following illustrates.

Line 99:

Line 100:

Exception Description: A End tag does not match start tag 'session'. was thrown while parsing the XML file against the XML schema.

Exception Description: A End tag does not match start tag 'session'. was thrown while parsing the XML file against the XML schema.

For a JPA application, you can express session metadata using JPA annotations, <tt>persistence.xml</tt>, <tt>orm.xml</tt>, and EclipseLink JPA annotation and <tt>persistence.xml</tt> property extensions. The EclipseLink JPA persistence provider interprets all these sources of metadata to create an in-memory EclipseLink session and project at run time.

For a JPA application, you can express session metadata using JPA annotations, <tt>persistence.xml</tt>, <tt>orm.xml</tt>, and EclipseLink JPA annotation and <tt>persistence.xml</tt> property extensions. The EclipseLink JPA persistence provider interprets all these sources of metadata to create an in-memory EclipseLink session and project at run time.

−

Using EclipseLink JPA, you also have the option of specifying your metadata using EclipseLink <tt>sessions.xml</tt> and <tt>project.xml</tt> while accessing your persistent classes using JPA and an <tt>EntityManger</tt>. For more information, see [[Using%20EclipseLink%20JPA%20Extensions%20(ELUG)#What You May Need to Know About EclipseLink JPA Overriding Mechanisms|What You May Need to Know About EclipseLink JPA Overriding Mechanisms]].

+

Using EclipseLink JPA, you also have the option of specifying your metadata using EclipseLink <tt>sessions.xml</tt> and <tt>project.xml</tt> while accessing your persistent classes using JPA and an <tt>EntityManager</tt>. For more information, see [[Using%20EclipseLink%20JPA%20Extensions%20(ELUG)#What You May Need to Know About EclipseLink JPA Overriding Mechanisms|What You May Need to Know About EclipseLink JPA Overriding Mechanisms]].

−

===eclispelink-dbws.xml File===

−

The <tt>eclispelink-dbws.xml</tt> file is used only with EclipseLink database Web services. The EclipseLink runtime uses the properties (see the following table set in this file to determine such things as service name, generated <tt>sessions.xml</tt> file name, and query definitions for an EclipseLink database Web service, as the following example shows.

The <tt>eclipselink-dbws-service.xml</tt> file XSD is <tt>eclipselink-dbws_1.xsd</tt> and it is located in the ''<tt><ECLIPSELINK_HOME></tt>''<tt>\config\xsds</tt> directory.

−

−

===eclispelink-dbws-schema.xsd===

−

The <tt>eclipselink-dbws-schema.xsd</tt> file is used only with EclipseLink database Web services. The EclipseLink database Web service automatically generates this file from your database table metadata and uses it to derive element-tag names and types.

−

−

The [[#Table 8-2|Typical Database Metadata]] table shows metadata from a typical database and the [[#Example 8-3| Corresponding eclispelink-dbws-schema.xsd]] example shows the corresponding <tt>eclipselink-dbws-schema.xsd</tt> file that the EclipseLink database Web service generates from it.

You may also choose to use the [[#project.xml File|project.xml File]] and [[#sessions.xml File|sessions.xml File]].

You may also choose to use the [[#project.xml File|project.xml File]] and [[#sessions.xml File|sessions.xml File]].

Line 417:

Line 157:

* [[Developing Applications Using EclipseLink JPA (ELUG)#Application Development with EclipseLink JPA|Application Development with EclipseLink JPA)]]

* [[Developing Applications Using EclipseLink JPA (ELUG)#Application Development with EclipseLink JPA|Application Development with EclipseLink JPA)]]

−

==Creating Deployment Files for JPA Applications==

−

See [[Packaging and Deploying EclipseLink JPA Applications (ELUG)|Packaging and Deploying EclipseLink JPA Applications]] for information on how to create deployment files for your JPA application.

−

==Creating Deployment Files for EclipseLink Database Web Services==

+

==Creating Deployment Files for JPA Applications==

−

This section describes how to automatically generate a WAR file containing the WSDL and all deployment files an EclipseLink database Web service requires, including the following:

+

See [[Packaging and Deploying EclipseLink JPA Applications (ELUG)|Packaging and Deploying EclipseLink JPA Applications]] for information on how to create deployment files for your JPA application.

−

* [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Database Table|How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from an Database Table]]

+

−

* [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from SQL|How to Create Deployment Files for an EclipseLink Database Web Service Using Ant: from SQL]]

+

−

* [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Stored Procedure|How to Create Deployment Files for an EclipseLink Database Web Service Using Ant: from a Stored Procedure]]

+

−

* [[#How to Customize a EclipseLink Database Web Service Using Java: Session Customization|How to Customize an EclipseLink Database Web Service Using Java: Session Customization]]

+

−

* [[#How to Customize a EclipseLink Database Web Service Using project.xml and sessions.xml|How to Customize an EclipseLink Database Web Service Using project.xml and sessions.xml]]

* [[#What You May Need to Know About Creating Deployment Files for a EclipseLink Database Web Service|What You May Need to Know About Creating Deployment Files for an EclipseLink Database Web Service]]

+

+

<!--

+

==Configuring the orion-ejb-jar.xml File for OC4J==

−

===How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Database Table===

+

To deploy a EclipseLink application to OC4J, modify the <tt>orion-ejb-jar.xml</tt> file. For more information, see [[#How to Configure persistence-manager Entries|How to Configure persistence-manager Entries]].

−

You can generate an EclipseLink database Web service from an existing relational database table using Ant.

+

−

====To Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Database Table====

+

===How to Configure persistence-manager Entries===

−

<ol>

+

−

<li> Create the table in your relational database and ensure that the relational database management system is online.</li>

+

−

<li> Execute the <tt>GenerateFromTables</tt> Ant task, as the following example shows.<br><span id="Example 8-4"></span>'''''Generating an EclipseLink Database Web Service from a Table''''' <div class="pre">

===How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from SQL===

+

If you are using EclipseLink as your OC4J persistence manager, you can configure the <tt>persistence-manager</tt> subentry (see the [[#Table 8-14|orion-ejb-jar.xml File persistence-manager Entries]] table) in the <tt>orion-ejb-jar.xml</tt> file.

−

You can generate an EclipseLink database Web service from one or more SQL statements written with respect to an existing relational database schema using Ant.

+

−

+

−

+

−

+

−

====To Create Deployment Files for a EclipseLink Database Web Service Using Ant: from SQL====

+

−

<ol>

+

−

<li> Create your relational database schema and ensure that the relational database management system is online.</li>

+

−

<li> Execute the <tt>GenerateFromSQL</tt> Ant task, as the following example shows:

+

−

<ol>

+

−

<li> Create an <tt>SQLOperation</tt> for each SQL statement you want to expose.</li>

+

−

<li> If the SQL statement takes arguments, add a <tt>Binding</tt> task for each argument. The order in which you define <tt>Binding</tt> tasks must match the order of the arguments in your SQL statement.<br><span id="Example 8-5"></span>''''' Generating an EclipseLink Databases Service from SQL'''''

===How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Stored Procedure===

+

−

You can generate an EclipseLink database Web service from one or more stored procedures, stored functions, and triggers defined in an existing relational database schema using Ant.

+

−

+

−

+

−

+

−

====To Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Stored Procedure====

+

−

<ol>

+

−

<li> Create your relational database schema and ensure that the relational database management system is online.</li>

+

−

<li> Execute the <tt>GenerateFromStoredProcedure</tt> Ant task, as the following example shows. Create an <tt>Operation</tt> for each stored procedure, stored function, or trigger you want to expose.<br><span id="Example 8-6"></span>''''' Generating an EclipseLink Databases Service from a Stored Procedure'''''

<li>Implement a <tt>org.eclipse.persistence.tools.sessionconfiguration.SessionCustomizer</tt>, as the following example shows.<br><span id="Example 8-7"></span>''''' Implementing a SessionCustomizer''''' <div class="pre">

<li> Execute the <tt>BuildDBWSWar</tt> Ant task, as this example shows.When you execute the <tt>BuildDBWSWar</tt> Ant task, specify the <tt>SessionCustomizer</tt> class name using the <tt>BuildDBWSWar</tt> attribute <tt>sessionCustomizerClassName</tt>.<br><span id="Example 8-8"></span>''''' Building the EclipseLink Database Web Service WAR File With a Session Customizer''''' <div class="tt">

* [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Database Table|How to Create Deployment Files for an EclipseLink Database Web Service Using Ant: from a Database Table]]

+

−

* [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from SQL|How to Create Deployment Files for an EclipseLink Database Web Service Using Ant: from SQL]]

+

−

* [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Stored Procedure|How to Create Deployment Files for an EclipseLink Database Web Service Using Ant: from a Stored Procedure]]

</div><br>Executing the <tt>BuildDBWSWar</tt> Ant task with a generator creates the necessary EclipseLink database Web service files and subdirectories.

+

−

For more information, see:

+

−

* [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Database Table|How to Create Deployment Files for an EclipseLink Database Web Service Using Ant: from a Database Table]]

+

−

* [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from SQL|How to Create Deployment Files for an EclipseLink Database Web Service Using Ant: from SQL]]

+

−

* [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Stored Procedure|How to Create Deployment Files for an EclipseLink Database Web Service Using Ant: from a Stored Procedure]]

'''Note:''' Your custom <tt>project.xml</tt> files must use the same names as specified by <tt>BuildDBWSWar</tt> attributes <tt>ormProjectFilename</tt> and <tt>oxmProjectFilename</tt>. Your custom <tt>sessions.xml</tt> file must use the same name as specified by <tt>BuildDBWSWar</tt> attribute <tt>sessionsFileName</tt>.

* [[#What You May Need to Know About Creating Deployment Files for a EclipseLink Database Web Service|What You May Need to Know About Creating Deployment Files for an EclipseLink Database Web Service]]</li>

<li> Execute the <tt>BuildDBWSWar</tt> Ant task without a generator, as the following example shows.<br><span id="Example 8-10"></span><br>''''' Building the EclipseLink Database Web Service WAR File''''' <br>

Executing the <tt>BuildDBWSWar</tt> Ant task without a generator assembles the EclipseLink database Web service files in the subdirectory of the current working directory named according to the <tt>EclipseLinkProjectName</tt> attribute.<br>For more information, see:

<li> Include the <tt>eclipselink-ant-lib.xml</tt> file in your Ant <tt>build.xml</tt> file, as the following example shows.<br><span id="Example 8-12"></span>''''' Specifying the eclipselink-ant-lib.xml File in a build.xml File'''''

You can invoke these Ant tasks directly on the command line or within your application's build system. For more information, see [[#How to Configure Ant to Use EclipseLink Database Web Services Tasks|How to Configure Ant to Use EclipseLink Database Web Services Tasks]].

+

−

+

−

+

−

+

−

====EclipseLink Database Web Services WAR File====

+

−

When you generate a EclipseLink database Web service, all generated files are packaged into a WAR file, as the following example shows. The [[#table_8_5|EclipseLink Database Web Service WAR File Contents]] table lists the files in these WAR files.

Default EclipseLink database Web service landing page.The name and content of this file is determined by its role in Web deployment and cannot be changed.Applicable to all WAR files.

+

−

|- align="left" valign="top"

+

−

| id="r3c1-t10" headers="r1c1-t10" align="left" |

+

−

<tt>swaref.xsd</tt>

+

−

| headers="r3c1-t10 r1c2-t10" align="left" |

+

−

Contains XML type definitions for attachments.The name and content of this file is determined by its role in Web deployment and cannot be changed.

+

−

|- align="left" valign="top"

+

−

| id="r4c1-t10" headers="r1c1-t10" align="left" |

+

−

<tt>topink-dbws-schema.xsd</tt>

+

−

| headers="r4c1-t10 r1c2-t10" align="left" |

+

−

Contains XML type definitions for operation arguments and return types. The EclipseLink database Web service automatically generates this file from your database table metadata and uses it to derive element-tag names and types. For more information, see [[#eclispelink-dbws-schema.xsd|eclispelink-dbws-schema.xsd]].

+

−

|- align="left" valign="top"

+

−

| id="r5c1-t10" headers="r1c1-t10" align="left" |

+

−

<tt>MANIFEST.MF</tt>

+

−

| headers="r5c1-t10 r1c2-t10" align="left" |

+

−

The manifest file for the WAR file.

+

−

|- align="left" valign="top"

+

−

| id="r6c1-t10" headers="r1c1-t10" align="left" |

+

−

<tt>oracle-webservices.xml</tt>

+

−

| headers="r6c1-t10 r1c2-t10" align="left" |

+

−

The deployment descriptor that the OC4J Web services stack requires.The name and content of this file is determined by its role in Web deployment and cannot be changed.

+

−

|- align="left" valign="top"

+

−

| id="r7c1-t10" headers="r1c1-t10" align="left" |

+

−

<tt>web.xml</tt>

+

−

| headers="r7c1-t10 r1c2-t10" align="left" |

+

−

The Web application deployment file that binds the EclipseLink database Web service to an OC4J Web services stack servlet.

The EclipseLink <tt>sessions.xml</tt> file for this EclipseLink database Web service. It contains references to the EclipseLink relational and object-XML <tt>project.xml</tt> files.<br>For more information, see [[Introduction%20to%20EclipseLink%20Sessions%20(ELUG)|Introduction to EclipseLink Sessions]].

+

−

|- align="left" valign="top"

+

−

| id="r10c1-t10" headers="r1c1-t10" align="left" |

+

−

<tt>eclispelink-dbws-or.xml</tt>

+

−

| headers="r10c1-t10 r1c2-t10" align="left" |

+

−

The EclipseLink relational <tt>project.xml</tt> file.<br>For more information, see [[Introduction%20to%20Relational%20Projects%20(ELUG)|Introduction to Relational Projects]].

+

−

|- align="left" valign="top"

+

−

| id="r11c1-t10" headers="r1c1-t10" align="left" |

+

−

<tt>eclispelink-dbws-ox.xml</tt>

+

−

| headers="r11c1-t10 r1c2-t10" align="left" |

+

−

The EclipseLink object-XML <tt>project.xml</tt> file.<br>For more information, see [[Introduction%20to%20XML%20Projects%20(ELUG)#BABEGHHD|Introduction to XML Projects]].

+

−

|- align="left" valign="top"

+

−

| id="r12c1-t10" headers="r1c1-t10" align="left" |

+

−

<tt>eclispelink-dbws.wsdl</tt>

+

−

| headers="r12c1-t10 r1c2-t10" align="left" |

+

−

Contains equivalent entries for each operation for the specified EclipseLink database Web service. Required for deployment as a Web service.

+

−

|}

+

−

+

−

<br>

+

−

+

−

Before you can deploy the EclipseLink database Web service, you must package the WAR in the appropriate Java EE archive for your application, such as an EAR.

* The default root-element tag name is simple-xml-format and each row uses the tag name simple-xml. You can customize these element tag names using attributes <tt>simpleXMLFormatTag</tt> and <tt>xmlTag</tt> in Ant tasks and.

+

−

* Columnar data uses tag names taken either from the database schema (the actual database column name) or from the stored procedure, stored function, or trigger.

+

−

* If a column is a primary key, the EclipseLink database Web service adds a <tt>isPrimaryKey</tt> attribute to the column tag and sets it to <tt>true</tt>, as shown for <tt>EMPNO</tt> in this example.

+

−

+

−

+

−

<span id="Example 8-15"></span>

+

−

'''''Example Unstructured Data Document'''''

+

−

<?xml version = '1.0' encoding = 'UTF-8'?>

+

−

<simple-xml-format>

+

−

<simple-xml>

+

−

<EMPNO isPrimaryKey="true">7788</EMPNO>

+

−

+

−

<ENAME>SCOTT</ENAME>

+

−

<JOB>ANALYST</JOB>

+

−

<MGR>7566</MGR>

+

−

<HIREDATE>1987-04-19T00:00:00.000-0400</HIREDATE>

+

−

+

−

<SAL>3000</SAL>

+

−

<DEPTNO>20</DEPTNO>

+

−

</simple-xml>

+

−

<simple-xml>

+

−

<EMPNO isPrimaryKey="true">7369</EMPNO>

+

−

+

−

<ENAME>SMITH</ENAME>

+

−

<JOB>CLERK</JOB>

+

−

<MGR>7902</MGR>

+

−

<HIREDATE>1980-12-17T00:00:00.000-0400</HIREDATE>

+

−

+

−

<SAL>800</SAL>

+

−

<DEPTNO>20</DEPTNO>

+

−

</simple-xml>

+

−

</simple-xml-format>

+

−

+

−

+

−

+

−

For more information, see the following:

+

−

* [[#GenerateFromSQL|GenerateFromSQL]]

+

−

* [[#GenerateFromStoredProcedures|GenerateFromStoredProcedures]]

+

−

* [[#Operations|Operations]]

+

−

+

−

====Customizing EclipseLink Database Web Services====

+

−

To customize an EclipseLink database Web service, you can do the following:

+

−

+

−

* Implement an EclipseLink <tt>SessionCustomizer</tt> class.A <tt>SessionCustomizer</tt> is a Java class that implements the <tt>org.eclipse.persistence.sessionconfiguration.SessionCustomizer</tt> interface and provides a default (zero-argument) constructor.Use this class's <tt>customize</tt> method, which takes an <tt>oracle.toplink.essentials.sessions.Session</tt>, to programmatically access advanced EclipseLink session API. Using this API you can get object relational and XML descriptors and from descriptors, you can get object relational and XML mappings.<br>In this way, you can access all session, descriptor, and mapping API to customize any part of the EclipseLink runtime that the EclipseLink database Web service generates. For example, to turn off the session cache. This approach is best when you just want to customize a few details.You specify the <tt>SessionCustomizer</tt> when you execute the [[#BuildDBWSWar|BuildDBWSWar]] Ant task.By default, the session names are defined based on the <tt>eclipselink-dbws.xml</tt> file <tt>name</tt> attribute as follows:

* Manually generate <tt>project.xml</tt> files and <tt>sessions.xml</tt> file.Using your preferred tool, Oracle JDeveloper or Workbench, you can map your objects to your relational database in an EclipseLink relational project, map your objects to your XML schema in an EclipseLink XMl project, and create an EclipseLink <tt>sessions.xml</tt> file that references both projects.In this way, you can control all aspects of the relational and XML mapping. This approach is best when you want to customize most or all details.

+

−

+

−

For more information, see the following:

+

−

* [[#How to Customize a EclipseLink Database Web Service Using Java: Session Customization|How to Customize a EclipseLink Database Web Service Using Java: Session Customization]]

+

−

* [[#How to Customize a EclipseLink Database Web Service Using project.xml and sessions.xml|How to Customize a EclipseLink Database Web Service Using project.xml and sessions.xml]]

+

−

* [[#BuildDBWSWar|BuildDBWSWar]]

+

−

* ''EclipseLink API Reference''

+

−

+

−

===Binding===

+

−

The <tt>Binding</tt> Ant task is a EclipseLink database Web services task you use to bind an argument in an SQL statement to an XSD data type.

+

−

+

−

The order in which you define <tt>Binding</tt> tasks must match the order of the arguments in your SQL statement, as the [[#Example 8-16|SQLOperation Task: With Binding Elements for Arguments]] example shows.

The name of the stored procedure, stored function, or trigger to execute. The parent task that owns the <tt>Operation</tt> specifies the database that provides the stored procedure, stored function, or trigger.<br>For more information, see [[#GenerateFromSQL|GenerateFromSQL]].

+

−

| headers="r2c1-t11 r1c3-t11" align="left" |

+

−

Yes

+

−

|- align="left" valign="top"

+

−

| id="r3c1-t11" headers="r1c1-t11" align="left" |

+

−

<tt>type</tt>

+

−

| headers="r3c1-t11 r1c2-t11" align="left" |

+

−

The XSD data type to bind to the argument <tt>name</tt>.

+

−

| headers="r3c1-t11 r1c3-t11" align="left" |

+

−

Yes

+

−

|}

+

−

+

−

+

−

+

−

====Examples====

+

−

The following example shows a typical <tt>SQLOperation</tt> task that specifies arguments using nested <tt>Binding</tt> tasks. The order in which you define <tt>Binding</tt> tasks must match the order of the arguments in your SQL statement.

+

−

+

−

For example, the <tt>SQLOperation</tt> named <tt>FindAnEmployee</tt> takes one <tt>int</tt> argument (<tt>EMPNO</tt>), one <tt>string</tt> argument (<tt>LAST_NAME</tt>), and returns all fields in a <tt>RowSet</tt> using a <tt>rowsetTag</tt> of <tt>employee-rowset</tt> and a <tt>rowTag</tt> of <tt>employee</tt>

The <tt>BuildDBWSWar</tt> Ant task (see the [[#Example 8-17|BuildDBWSWar Task]] example) is a EclipseLink database Web services task you use either with a EclipseLink database Web services generator task or without.

+

−

+

−

When you execute the <tt>BuildDBWSWar</tt> task with a generator, the <tt>BuildDBWSWar</tt> task generates EclipseLink database Web services files and assemble them into a Web Archive (WAR) file. The <tt>BuildDBWSWar</tt> task supports the following generators:

+

−

* [[#GenerateFromSQL|GenerateFromSQL]]

+

−

* [[#GenerateFromStoredProcedures|GenerateFromStoredProcedures]]

+

−

* [[#GenerateFromTables|GenerateFromTables]]

+

−

+

−

When you execute the <tt>BuildDBWSWar</tt> task without a generator, the <tt>BuildDBWSWar</tt> task assembles EclipseLink database Web services files in a subdirectory of the current working directory named according to the <tt>EclipseLinkProjectName</tt> attribute into a Web Archive (WAR) file.

+

−

+

−

This allows you to customize the generated EclipseLink database Web services files and then execute the <tt>BuildDBWSWar</tt> task again to re-package the WAR file to include your changes.

+

−

+

−

This task extends the Ant <tt>Jar</tt> task and inherits its attributes and nested elements.

Alternatively, you can use a nested Ant [http://ant.apache.org/manual/usingl#path <tt>classpath</tt>] element.

+

−

| headers="r2c1-t12 r1c3-t12" align="left" |

+

−

Yes

+

−

| headers="r2c1-t12 r1c4-t12" align="left" |

+

−

None

+

−

|- align="left" valign="top"

+

−

| id="r3c1-t12" headers="r1c1-t12" align="left" |

+

−

<tt>contextRoot</tt>

+

−

| headers="r3c1-t12 r1c2-t12" align="left" |

+

−

The value of the <tt>web.xml</tt> file <tt>servlet-mapping</tt> element's <tt>url-pattern</tt> sub-element.<br>'''Example:'''

+

−

<servlet-mapping>

+

−

...

+

−

<url-pattern>

+

−

/servlet/MyWebService

+

−

</url-pattern>

+

−

</servlet-mapping>

+

−

| headers="r3c1-t12 r1c3-t12" align="left" |

+

−

Yes

+

−

| headers="r3c1-t12 r1c4-t12" align="left" |

+

−

None

+

−

|- align="left" valign="top"

+

−

| id="r4c1-t12" headers="r1c1-t12" align="left" |

+

−

<tt>destfile</tt>

+

−

| headers="r4c1-t12 r1c2-t12" align="left" |

+

−

The fully qualified path to the WAR file.

+

−

| headers="r4c1-t12 r1c3-t12" align="left" |

+

−

Yes

+

−

| headers="r4c1-t12 r1c4-t12" align="left" |

+

−

None

+

−

|- align="left" valign="top"

+

−

| id="r5c1-t12" headers="r1c1-t12" align="left" |

+

−

<tt>dataSource</tt>

+

−

| headers="r5c1-t12 r1c2-t12" align="left" |

+

−

JNDI datasource location to be inserted into the EclipseLink database Web service <tt>sessions.xml</tt> file (see <tt>sessionsFileName</tt>).

+

−

+

−

The JNDI name you use here is as defined in ''<tt>ORACLE_INSTANCE</tt>''<tt>/config/oc4j/</tt>''<tt>OC4J_INSTANCE</tt>''<tt>/data-sources.xml</tt> file element <tt>managed-data-source</tt> attribute <tt>jndi-name</tt> or element <tt>native-data-source</tt> attribute <tt>jndi-name</tt>.

+

−

+

−

You must configure this datasource in OC4J before deploying your EclipseLink database Web service.

+

−

+

−

Use this attribute as an alternative to generator attributes:

+

−

* <tt>driver</tt>

+

−

* <tt>password</tt>

+

−

* <tt>rdbms</tt>

+

−

* <tt>url</tt>

+

−

* <tt>userid</tt>

+

−

+

−

'''Example:'''

+

−

+

−

Given the following OC4J <tt>data-sources.xml</tt> configuration, you would set <tt>BuildDBWSWar</tt> attribute <tt>dataSource</tt> to <tt>jdbc/OracleDS</tt>.

+

−

<data-sources ... >

+

−

<connection-pool name="MyPool">

+

−

...

+

−

</connection-pool>

+

−

<managed-data-source

+

−

name="OracleManagedDS"

+

−

jndi-name="jdbc/OracleDS"

+

−

connection-pool-name="MyPool"

+

−

...

+

−

/>

+

−

</data-sources ... >

+

−

| headers="r5c1-t12 r1c3-t12" align="left" |

+

−

No

+

−

| headers="r5c1-t12 r1c4-t12" align="left" |

+

−

None

+

−

|- align="left" valign="top"

+

−

| id="r6c1-t12" headers="r1c1-t12" align="left" |

+

−

<tt>logLevel</tt>

+

−

| headers="r6c1-t12 r1c2-t12" align="left" |

+

−

Control the amount and detail of log output by configuring the log level (in ascending order of information) to one of the following <tt>java.util.logging.Level</tt> values:

+

−

* <tt>OFF</tt> – Disable logging.

+

−

* <tt>SEVERE</tt> – Logs exceptions indicating EclipseLink cannot continue, as well as any exceptions generated during login. This includes a stack trace.

+

−

* <tt>WARNING</tt> – Logs exceptions that do not force EclipseLink to stop, including all exceptions not logged with severe level. This does not include a stack trace.

+

−

* <tt>INFO</tt> – Logs the login/logout per sever session, including the user name. After acquiring the session, detailed information is logged.

The fully qualified name of the EclipseLink database platform class to use to connect to the relational database. This class must be in the task classpath.<br><br>'''Example:''' <tt>org.eclipse.persistence.platform.database.oracle.Oracle11Platform</tt>

+

−

| headers="r7c1-t12 r1c3-t12" align="left" |

+

−

Yes – when you execute this task with a generator to generate a new service.

+

−

+

−

No – when you execute this task without a generator to assemble pre-existing metadata files.

+

−

| headers="r7c1-t12 r1c4-t12" align="left" |

+

−

None

+

−

|- align="left" valign="top"

+

−

| id="r8c1-t12" headers="r1c1-t12" align="left" |

+

−

<tt>projectName</tt>

+

−

| headers="r8c1-t12 r1c2-t12" align="left" |

+

−

The name of this EclipseLink database Web service.

+

−

+

−

By default, the EclipseLink project names are defined based on this attribute:

The name of the <tt>org.eclipse.persistence.sessions.SessionCustomizer</tt> class you use to customize the EclipseLink database Web service.

+

−

+

−

For more information, see [[#How to Customize a EclipseLink Database Web Service Using Java: Session Customization|How to Customize a EclipseLink Database Web Service Using Java: Session Customization]].

+

−

| headers="r9c1-t12 r1c3-t12" align="left" |

+

−

Yes – when you execute this task with a generator to generate a new service.

+

−

+

−

No – when you execute this task without a generator to assemble pre-existing metadata files.

+

−

| headers="r9c1-t12 r1c4-t12" align="left" |

+

−

None

+

−

|- align="left" valign="top"

+

−

| id="r10c1-t12" headers="r1c1-t12" align="left" |

+

−

<tt>sessionsFileName</tt>

+

−

| headers="r10c1-t12 r1c2-t12" align="left" |

+

−

The name of the EclipseLink <tt>sessions.xml</tt> file that references the relational and XML projects.

+

−

+

−

By default, the EclipseLink session names are defined based on the <tt>projectName</tt> attribute:

Yes – when you execute this task with a generator to generate a new service.

+

−

+

−

No – when you execute this task without a generator to assemble pre-existing metadata files.

+

−

| headers="r10c1-t12 r1c4-t12" align="left" |

+

−

<tt>eclipselink-dbws-sessions.xml</tt>

+

−

|- align="left" valign="top"

+

−

| id="r11c1-t12" headers="r1c1-t12" align="left" |

+

−

<tt>targetNameSpace</tt>

+

−

| headers="r11c1-t12 r1c2-t12" align="left" |

+

−

The URI of the target namespace that the EclipseLink database Web service inserts into the <tt>eclipselink-dbws-schema.xsd</tt> file. For more information, see [[#eclipselink-dbws-schema.xsd|eclipselink-dbws-schema.xsd]].

+

−

| headers="r11c1-t12 r1c3-t12" align="left" |

+

−

No

+

−

| headers="r11c1-t12 r1c4-t12" align="left" |

+

−

<tt>"urn:" + projectName</tt>

+

−

|- align="left" valign="top"

+

−

| id="r12c1-t12" headers="r1c1-t12" align="left" |

+

−

<tt>wsdlLocationURI</tt>

+

−

| headers="r12c1-t12 r1c2-t12" align="left" |

+

−

URI of this EclipseLink DBWS service's WSDL (used by Web Service tools to generate client code).

* [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Database Table|How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Database Table]]

+

−

* [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from SQL|How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from SQL]]

+

−

* [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Stored Procedure|How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Stored Procedure]]

+

−

+

−

===GenerateFromSQL===

+

−

The <tt>GenerateFromSQL</tt> task is a EclipseLink database Web services task you use to generate a Web service based on one or more SQL statements you specify with <tt>SQLOperation</tt> nested elements. You specify SQL statements with respect to the existing relational database schema that the <tt>SQLOperation</tt> element's parent identifies.

+

−

+

−

This task generates an operation for each <tt>SQLOperation</tt> nested element you specify.

+

−

+

−

This task generates EclipseLink database Web service files in a subdirectory of the current working directory named according to the <tt>EclipseLinkProjectName</tt> attribute.

The fully qualified name of the JDBC driver class to use to connect to the relational database. This class must be in the task classpath.

+

−

+

−

This attribute is inherited from the Ant [http://ant.apache.org/manual/CoreTasks/sqll <tt>Sql</tt>] task.<br><br>'''Example:''' <tt>oracle.jdbc.OracleDriver</tt>

+

−

| headers="r2c1-t13 r1c3-t13" align="left" |

+

−

No – Can be overridden by <tt>BuildDBWSWar</tt> attribute <tt>dataSource</tt>.

+

−

| headers="r2c1-t13 r1c4-t13" align="left" |

+

−

None

+

−

|- align="left" valign="top"

+

−

| id="r3c1-t13" headers="r1c1-t13" align="left" |

+

−

<tt>password</tt>

+

−

| headers="r3c1-t13 r1c2-t13" align="left" |

+

−

The password to use when connecting to the relational database.

+

−

+

−

This attribute is inherited from the Ant [http://ant.apache.org/manual/CoreTasks/sqll <tt>Sql</tt>] task.

+

−

| headers="r3c1-t13 r1c3-t13" align="left" |

+

−

No – Can be overridden by <tt>BuildDBWSWar</tt> attribute <tt>dataSource</tt>.

+

−

| headers="r3c1-t13 r1c4-t13" align="left" |

+

−

None

+

−

|- align="left" valign="top"

+

−

| id="r4c1-t13" headers="r1c1-t13" align="left" |

+

−

<tt>url</tt>

+

−

| headers="r4c1-t13 r1c2-t13" align="left" |

+

−

The connection URL to use when connecting the relational database.

+

−

+

−

This attribute is inherited from the Ant [http://ant.apache.org/manual/CoreTasks/sqll <tt>Sql</tt>] task.<br><br>'''Example:''' <tt>jdbc:oracle:thin:@</tt>''<tt>HOST_NAME</tt>''<tt><nowiki>:</nowiki></tt>''<tt>PORT</tt>''<tt><nowiki>:</nowiki></tt>''<tt>SID</tt>''

+

−

| headers="r4c1-t13 r1c3-t13" align="left" |

+

−

No – Can be overridden by <tt>BuildDBWSWar</tt> attribute <tt>dataSource</tt>.

+

−

| headers="r4c1-t13 r1c4-t13" align="left" |

+

−

None

+

−

|- align="left" valign="top"

+

−

| id="r5c1-t13" headers="r1c1-t13" align="left" |

+

−

<tt>userid</tt>

+

−

| headers="r5c1-t13 r1c2-t13" align="left" |

+

−

The user name to use when connecting to the relational database.

+

−

+

−

This attribute is inherited from the Ant [http://ant.apache.org/manual/CoreTasks/sqll <tt>Sql</tt>] task.

+

−

| headers="r5c1-t13 r1c3-t13" align="left" |

+

−

No – Can be overridden by <tt>BuildDBWSWar</tt> attribute <tt>dataSource</tt>.

+

−

| headers="r5c1-t13 r1c4-t13" align="left" |

+

−

None

+

−

|}

+

−

+

−

====Specifying Parameters as Nested Elements====

+

−

You can specify the following parameters as nested elements of this task:

The EclipseLink database Web service named <tt>emp</tt> will contain an operation <tt>findXREmpByName</tt> that takes one <tt>string</tt> argument (<tt>ENAME</tt>) and returns all records from the <tt>XR_EMP</tt> table whose <tt>ENAME</tt> column is like the argument. Results are returned as a <tt>Collection</tt> of <tt>xr_emptType</tt> instances.

For more information, see [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from SQL|How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from SQL]].

+

−

+

−

+

−

+

−

===GenerateFromStoredProcedures===

+

−

The <tt>GenerateFromStoredProcedures</tt> task is a EclipseLink database Web services task you use to generate a Web service based on one or more stored procedures, stored functions, or triggers you specify with <tt>Procedure</tt> nested elements. You specify stored procedures, stored functions, or triggers with respect to the existing relational database schema that the <tt>Procedure</tt> element's parent identifies.

+

−

+

−

This task generates an operation for each <tt>Procedure</tt> nested element you specify.

+

−

+

−

This task generates EclipseLink database Web service files in a subdirectory of the current working directory named according to the <tt>EclipseLinkProjectName</tt> attribute.

The fully qualified name of the JDBC driver class to use to connect to the relational database. This class must be in the task classpath.This attribute is inherited from the Ant [http://ant.apache.org/manual/CoreTasks/sqll <tt>Sql</tt>] task.<br><br>'''Example:''' <tt>oracle.jdbc.OracleDriver</tt>

+

−

| headers="r2c1-t14 r1c3-t14" align="left" |

+

−

No – Can be overridden by <tt>BuildDBWSWar</tt> attribute <tt>dataSource</tt>.

+

−

| headers="r2c1-t14 r1c4-t14" align="left" |

+

−

None

+

−

|- align="left" valign="top"

+

−

| id="r3c1-t14" headers="r1c1-t14" align="left" |

+

−

<tt>password</tt>

+

−

| headers="r3c1-t14 r1c2-t14" align="left" |

+

−

The password to use when connecting to the relational database.This attribute is inherited from the Ant [http://ant.apache.org/manual/CoreTasks/sqll <tt>Sql</tt>] task.

+

−

| headers="r3c1-t14 r1c3-t14" align="left" |

+

−

No – Can be overridden by <tt>BuildDBWSWar</tt> attribute <tt>dataSource</tt>.

+

−

| headers="r3c1-t14 r1c4-t14" align="left" |

+

−

None

+

−

|- align="left" valign="top"

+

−

| id="r4c1-t14" headers="r1c1-t14" align="left" |

+

−

<tt>url</tt>

+

−

| headers="r4c1-t14 r1c2-t14" align="left" |

+

−

The connection URL to use when connecting the relational database.This attribute is inherited from the Ant [http://ant.apache.org/manual/CoreTasks/sqll <tt>Sql</tt>] task.<br><br>'''Example:''' <tt>jdbc:oracle:thin:@</tt>''<tt>HOST_NAME</tt>''<tt><nowiki>:</nowiki></tt>''<tt>PORT</tt>''<tt><nowiki>:</nowiki></tt>''<tt>SID</tt>''

+

−

| headers="r4c1-t14 r1c3-t14" align="left" |

+

−

No – Can be overridden by <tt>BuildDBWSWar</tt> attribute <tt>dataSource</tt>.

+

−

| headers="r4c1-t14 r1c4-t14" align="left" |

+

−

None

+

−

|- align="left" valign="top"

+

−

| id="r5c1-t14" headers="r1c1-t14" align="left" |

+

−

<tt>userid</tt>

+

−

| headers="r5c1-t14 r1c2-t14" align="left" |

+

−

The user name to use when connecting to the relational database.This attribute is inherited from the Ant [http://ant.apache.org/manual/CoreTasks/sqll <tt>Sql</tt>] task.

+

−

| headers="r5c1-t14 r1c3-t14" align="left" |

+

−

No – Can be overridden by <tt>BuildDBWSWar</tt> attribute <tt>dataSource</tt>.

+

−

| headers="r5c1-t14 r1c4-t14" align="left" |

+

−

None

+

−

|}

+

−

+

−

+

−

+

−

+

−

+

−

====Specifying Parameters as Nested Elements====

+

−

You can specify the following parameters as nested elements of this task:

+

−

* [[#SQLOperation|SQLOperation]]

+

−

* [[#Binding|Binding]]

+

−

+

−

+

−

+

−

====Examples====

+

−

The [[#Example 8-19|GenerateFromStoredProcedures Task]] example shows a typical <tt>GenerateFromStoredProcedures</tt> task that specifies a <tt>Procedure</tt> for each of two stored procedures.

+

−

+

−

The EclipseLink database Web service named <tt>emp</tt> will contain one operation <tt>GetEmployeeByEMPNO_DEPTNO</tt> that invokes a stored procedure such as this:

+

−

GetEmployeeByEMPNO_DEPTNO(I_EMPNO IN NUMBER,I_DEPTNO IN NUMBER, Y OUT SYS_REFCURSOR);

+

−

OPEN y FOR SELECT * FROM XR_EMP where EMPNO = I_EMPNO and DEPTNO = I_DEPTNO;

+

−

+

−

Note that if <tt>procedurePattern</tt> matches more than one stored procedure, stored function, or trigger, then the EclipseLink database Web service will contain a procedure for each match. For more information, see [[#Procedure|Procedure]].

For more information, see [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Stored Procedure|How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Stored Procedure]].

+

−

+

−

+

−

+

−

===GenerateFromTables===

+

−

The <tt>GenerateFromTables</tt> task is a EclipseLink database Web services task you use to generate a Web service based on one or more relational database tables.

+

−

+

−

This task generates the following operations for each table you specify using one or more <tt>Table</tt> nested elements:

+

−

* <tt>create</tt>

+

−

* <tt>findAll</tt>

+

−

* <tt>findByPrimaryKey</tt>

+

−

* <tt>update</tt>

+

−

* <tt>delete</tt>

+

−

+

−

These operations apply to a single table only: they do not traverse relationships to other tables. For example, the read operation returns the key value of a foreign key column, not the row it references in a related table.

+

−

+

−

This task generates EclipseLink database Web service files in a subdirectory of the current working directory named according to the <tt>EclipseLinkProjectName</tt> attribute.

The fully qualified name of the JDBC driver class to use to connect to the relational database. This class must be in the task classpath.This attribute is inherited from the Ant [http://ant.apache.org/manual/CoreTasks/sqll <tt>Sql</tt>] task.

+

−

+

−

'''Example:''' <tt>oracle.jdbc.OracleDriver</tt>

+

−

| headers="r2c1-t15 r1c3-t15" align="left" |

+

−

No – Can be overridden by <tt>BuildDBWSWar</tt> attribute <tt>dataSource</tt>.

+

−

| headers="r2c1-t15 r1c4-t15" align="left" |

+

−

None

+

−

|- align="left" valign="top"

+

−

| id="r3c1-t15" headers="r1c1-t15" align="left" |

+

−

<tt>password</tt>

+

−

| headers="r3c1-t15 r1c2-t15" align="left" |

+

−

The password to use when connecting to the relational database.This attribute is inherited from the Ant [http://ant.apache.org/manual/CoreTasks/sqll <tt>Sql</tt>] task.

+

−

| headers="r3c1-t15 r1c3-t15" align="left" |

+

−

No – Can be overridden by <tt>BuildDBWSWar</tt> attribute <tt>dataSource</tt>.

+

−

| headers="r3c1-t15 r1c4-t15" align="left" |

+

−

None

+

−

|- align="left" valign="top"

+

−

| id="r4c1-t15" headers="r1c1-t15" align="left" |

+

−

<tt>url</tt>

+

−

| headers="r4c1-t15 r1c2-t15" align="left" |

+

−

The connection URL to use when connecting the relational database.This attribute is inherited from the Ant [http://ant.apache.org/manual/CoreTasks/sqll <tt>Sql</tt>] task.

The EclipseLink database Web service named <tt>emp</tt> will contain create, read, read-all, update, and delete operations for table <tt>XR_EMP</tt>.

+

−

+

−

Note that if <tt>tableNamePattern</tt> matches more than one table name, then the EclipseLink database Web service will contain create, read, read-all, update, and delete operations for each match. For more information, see [[#Table|Table]].

For more information, see [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Database Table|How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Database Table]].

+

−

+

−

+

−

+

−

===Operations===

+

−

The <tt>Operations</tt> task is a EclipseLink database Web services task you use to specify one or more stored procedure or SQL operations.

+

−

+

−

This task is applicable only in <tt>Table</tt> tasks. For more information, see [[#Table|Table]].

+

−

+

−

+

−

+

−

====Using Parameters====

+

−

This task has no parameters (only nested elements).

+

−

+

−

+

−

+

−

====Specifying Parameters as Nested Elements====

+

−

You can specify the following parameters as nested elements of this task:

For more information, see [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Database Table|How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Database Table]].

+

−

+

−

+

−

+

−

===Procedure===

+

−

The <tt>Procedure</tt> task is a EclipseLink database Web services task you use to specify a stored procedure.

* <tt>false</tt> - the operation does not return binary data as a SOAP attachment.

+

−

| headers="r9c1-t16 r1c3-t16" align="left" |

+

−

No

+

−

| headers="r9c1-t16 r1c4-t16" align="left" |

+

−

<tt>false</tt>

+

−

|- align="left" valign="top"

+

−

| id="r10c1-t16" headers="r1c1-t16" align="left" |

+

−

<tt>returnType</tt>

+

−

| headers="r10c1-t16 r1c2-t16" align="left" |

+

−

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

The EclipseLink database Web service named <tt>emp</tt> will contain one operation <tt>GetEmployeeByEMPNO_DEPTNO</tt> that invokes a stored procedure of the same name (defined in the database table that the parent task specifies) like this:

+

−

GetEmployeeByEMPNO_DEPTNO(I_EMPNO IN NUMBER,I_DEPTNO IN NUMBER, Y OUT SYS_REFCURSOR);

+

−

OPEN y FOR SELECT * FROM XR_EMP where EMPNO = I_EMPNO and DEPTNO = I_DEPTNO;

+

−

+

−

Note that if <tt>procedurePattern</tt> matches more than one stored procedure, stored function, or trigger, then the EclipseLink database Web service will contain a procedure for each match.

For more information, see [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from SQL|How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from SQL]].

+

−

+

−

+

−

+

−

===SQLOperation===

+

−

The <tt>SQLOperation</tt> task is a EclipseLink database Web services task you use to specify an SQL statement.

* <tt>false</tt> - the operation does not return binary data as a SOAP attachment.

+

−

| headers="r7c1-t17 r1c3-t17" align="left" |

+

−

No

+

−

| headers="r7c1-t17 r1c4-t17" align="left" |

+

−

<tt>false</tt>

+

−

|- align="left" valign="top"

+

−

| id="r8c1-t17" headers="r1c1-t17" align="left" |

+

−

<tt>returnType</tt>

+

−

| headers="r8c1-t17 r1c2-t17" align="left" |

+

−

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

+

−

| headers="r8c1-t17 r1c3-t17" align="left" |

+

−

No

+

−

| headers="r8c1-t17 r1c4-t17" align="left" |

+

−

Deduced from database metadata

+

−

|}

+

−

+

−

+

−

+

−

+

−

====Specifying Parameters as Nested Elements====

+

−

You can specify the following parameter as nested element of this task:

The EclipseLink database Web service named <tt>emp</tt> will contain two operations:

+

−

* <tt>findXREmpByName</tt> that takes one <tt>string</tt> argument (<tt>ENAME</tt>) and returns all records from the <tt>XR_EMP</tt> table whose <tt>ENAME</tt> column is like the argument. Results are returned as a <tt>Collection</tt> of <tt>xr_emptType</tt> instances.

+

−

* <tt>xr-employeeInfo</tt> that returns unstructured data in the Simple XML Format as the [[#Example 8-25|Unstructured Data Result]] example shows. In this output, <tt>COUNT</tt> is the number of records in table <tt>XR_EMP</tt> and <tt>MAX-Salary</tt> is the largest number in the <tt>SAL</tt> column. The tag names <tt>COUNT</tt> and <tt>MAX-Salary</tt> are as specified in the SQL statement.

+

−

+

−

+

−

<span id="Example 8-25"></span>

+

−

''''' Unstructured Data Result'''''

+

−

<?xml version = '1.0' encoding = 'UTF-8'?>

+

−

<xr-employee-info>

+

−

<aggregate-counts>

+

−

<COUNT>60000</COUNT>

+

−

+

−

<MAX-Salary>125000</MAX-Salary>

+

−

</aggregate-counts>

+

−

</xr-employee-info>

+

−

+

−

+

−

+

−

For more information, see [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from SQL|How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from SQL]].

+

−

+

−

+

−

+

−

===Table===

+

−

The <tt>Table</tt> task is a EclipseLink database Web services task you use to specify a database table.

+

−

+

−

This task is applicable only in <tt>GenerateFromTables</tt> tasks. For more information, see [[#GenerateFromTables|GenerateFromTables]].

For more information, see [[#How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Database Table|How to Create Deployment Files for a EclipseLink Database Web Service Using Ant: from a Database Table]].

+

−

+

−

==Configuring the orion-ejb-jar.xml File for OC4J==

+

−

To deploy a EclipseLink application to OC4J Release R1 or later, modify the <tt>orion-ejb-jar.xml</tt> file. For more information, see [[#How to Configure persistence-manager Entries|How to Configure persistence-manager Entries]].

+

−

+

−

+

−

+

−

===How to Configure persistence-manager Entries===

+

−

If you are using EclipseLink as your OC4J persistence manager, the default persistence manager in Release R1, you can configure the <tt>persistence-manager</tt> subentry (see the [[#Table 8-14|orion-ejb-jar.xml File persistence-manager Entries]] table) in the <tt>orion-ejb-jar.xml</tt> file.

+

If you are not using EclipseLink as your OC4J persistence manager, do not modify the <tt>persistence-manager</tt> subentries.

If you are not using EclipseLink as your OC4J persistence manager, do not modify the <tt>persistence-manager</tt> subentries.

Use of <tt>pm-name</tt> is unsupported and will be removed in a future release.

−

| align="left" |

+

Specify pm usage using <tt><persistence-manager></tt> 'name' instead.

−

'''WARNING:''' Use of <tt>pm-name</tt> is unsupported and will be removed in a future release. Specify pm usage using <tt><persistence-manager></tt> 'name' instead.

+

−

|}

+

Line 2,259:

Line 196:

<tt>name</tt>

<tt>name</tt>

| headers="r2c1-t20 r1c2-t20" align="left" |

| headers="r2c1-t20 r1c2-t20" align="left" |

−

The name of the persistence manager to use. Set this value to <tt>eclipselink</tt>.If you set the <tt>name</tt> property to <tt>eclipselink</tt>, you may also configure <tt>pm-properties</tt> (see [[#Configuring pm-properties|Configuring pm-properties]]).

+

The name of the persistence manager to use. Set this value to <tt>eclipselink</tt>.

+

+

If you set the <tt>name</tt> property to <tt>eclipselink</tt>, you may also configure <tt>pm-properties</tt> (see [[#Configuring pm-properties|Configuring pm-properties]]).

|- align="left" valign="top"

|- align="left" valign="top"

| id="r3c1-t20" headers="r1c1-t20" align="left" |

| id="r3c1-t20" headers="r1c1-t20" align="left" |

Line 2,269:

Line 208:

<tt>descriptor</tt>

<tt>descriptor</tt>

| headers="r4c1-t20 r1c2-t20" align="left" |

| headers="r4c1-t20 r1c2-t20" align="left" |

−

This property applies only when <tt>name</tt> is set to <tt>eclipselink</tt>.If you export your EclipseLink mapping metadata to a deployment XML file, set this property to the name of the deployment XML file (default: <tt>toplink-ejb-jar.xml</tt>).

+

This property applies only when <tt>name</tt> is set to <tt>eclipselink</tt>.

+

+

If you export your EclipseLink mapping metadata to a deployment XML file, set this property to the name of the deployment XML file (default: <tt>toplink-ejb-jar.xml</tt>).

Do not set this property if you are using a EclipseLink project class instead of a mapping metadata file (see <tt>project-class</tt> in the [[#Table 8-15|orion-ejb-jar.xml File persistence-manager Subentries for pm-properties]] table).

Do not set this property if you are using a EclipseLink project class instead of a mapping metadata file (see <tt>project-class</tt> in the [[#Table 8-15|orion-ejb-jar.xml File persistence-manager Subentries for pm-properties]] table).

|}

|}

−

Line 2,279:

Line 219:

====Configuring pm-properties====

====Configuring pm-properties====

+

When you select EclipseLink as the persistence manager (see <tt>name</tt> in the [[#Table 8-14|orion-ejb-jar.xml File persistence-manager Entries]] table), use the <tt>persistence-manager</tt> subentries for <tt>pm-properties</tt> (see the [[#Table 8-15|orion-ejb-jar.xml File persistence-manager Subentries for pm-properties]] table) to configure the EclipseLink session that the EclipseLink run time creates and uses internally.

When you select EclipseLink as the persistence manager (see <tt>name</tt> in the [[#Table 8-14|orion-ejb-jar.xml File persistence-manager Entries]] table), use the <tt>persistence-manager</tt> subentries for <tt>pm-properties</tt> (see the [[#Table 8-15|orion-ejb-jar.xml File persistence-manager Subentries for pm-properties]] table) to configure the EclipseLink session that the EclipseLink run time creates and uses internally.

Line 2,325:

Line 266:

<tt>db-platform-class</tt>

<tt>db-platform-class</tt>

| headers="r5c1-t22 r1c2-t22" align="left" |

| headers="r5c1-t22 r1c2-t22" align="left" |

−

Optional EclipseLink database platform class (instance of <tt>org.eclipse.persistence.platform.database</tt> or <tt>org.eclipse.persistence.platform.database.oracle</tt>) containing EclipseLink support specific to a particular database.Set this value to the database platform class that corresponds to the database that your application uses. The class must be fully qualified by its package name.

Set this value to the database platform class that corresponds to the database that your application uses. The class must be fully qualified by its package name.

|- align="left" valign="top"

|- align="left" valign="top"

| id="r6c1-t22" headers="r1c1-t22" align="left" |

| id="r6c1-t22" headers="r1c1-t22" align="left" |

Line 2,348:

Line 291:

====Configuring cache-synchronization Properties====

====Configuring cache-synchronization Properties====

+

When you select EclipseLink as the persistence manager (see <tt>name</tt> in the [[#Table 8-14|orion-ejb-jar.xml File persistence-manager Entries]] table), use the <tt>pm-properties</tt> subentry for <tt>cache-synchronization</tt> (see the [[#Table 8-16|orion-ejb-jar.xml File pm-properties Subentries for cache-synchronization table]] table) to configure EclipseLink cache coordination features of the session that the EclipseLink run time uses internally for CMP projects. For more information about EclipseLink cache coordination, see [[Introduction%20to%20Cache%20(ELUG)#Cache Coordination|Cache Coordination]].

When you select EclipseLink as the persistence manager (see <tt>name</tt> in the [[#Table 8-14|orion-ejb-jar.xml File persistence-manager Entries]] table), use the <tt>pm-properties</tt> subentry for <tt>cache-synchronization</tt> (see the [[#Table 8-16|orion-ejb-jar.xml File pm-properties Subentries for cache-synchronization table]] table) to configure EclipseLink cache coordination features of the session that the EclipseLink run time uses internally for CMP projects. For more information about EclipseLink cache coordination, see [[Introduction%20to%20Cache%20(ELUG)#Cache Coordination|Cache Coordination]].

Line 2,381:

Line 325:

Optional username required to log in to the JNDI naming service.

Optional username required to log in to the JNDI naming service.

|}

|}

−

−

Line 2,407:

Line 349:

* <tt>Create</tt> (default): This value tells EclipseLink to create the mapped tables during the deployment. If the tables already exist, EclipseLink will log an appropriate warning messages (such as "''Table already existed...''") and keeps processing the deployment.

* <tt>Create</tt> (default): This value tells EclipseLink to create the mapped tables during the deployment. If the tables already exist, EclipseLink will log an appropriate warning messages (such as "''Table already existed...''") and keeps processing the deployment.

* <tt>DropAndCreate</tt><nowiki>: This value tells EclipseLink to drop tables before creating them during deployment. If a table does not initially exist, the drop operation will cause anSQLException to be thrown through the driver. However, EclipseLink handles the exception (logs and ignores it) and moves on to process the table creation operation. The deployment fails only if both drop and create operations fail.</nowiki>

* <tt>DropAndCreate</tt><nowiki>: This value tells EclipseLink to drop tables before creating them during deployment. If a table does not initially exist, the drop operation will cause anSQLException to be thrown through the driver. However, EclipseLink handles the exception (logs and ignores it) and moves on to process the table creation operation. The deployment fails only if both drop and create operations fail.</nowiki>

−

* <tt>UseExisting</tt><nowiki>: This value tells EclipseLink to perform no table manipulation. If the tables do not exist, deployment still goes through without error.</nowiki>If no <tt>orion-ejb-jar.xml</tt> file is defined in your EAR file, the OC4J container generates one during deployment. In this case, to specify a value for <tt>db-table-gen</tt>, use the EclipseLink system property <tt>eclipselink.defaultmapping.dbTableGenSetting</tt>. For example: <tt>-Declipselink.defaultmapping.dbTableGenSetting="DropAndCreate"</tt>.<br>The <tt>orion-ejb-jar.xml</tt> property overrides the system property. If both the <tt>orion-ejb-jar.xml</tt> property and the system property are present, EclipseLink retrieves the setting from the <tt>orion-ejb-jar.xml</tt> file.This setting overrides <tt>autocreate-tables</tt> and <tt>autodelete-tables</tt> configuration at the application (EAR) or system level. For more information, see [[Using%20the%20Schema%20Manager%20(ELUG)#Creating Database Tables Automatically|Creating Database Tables Automatically]].

+

* <tt>UseExisting</tt><nowiki>: This value tells EclipseLink to perform no table manipulation. If the tables do not exist, deployment still goes through without error.</nowiki>

+

+

If no <tt>orion-ejb-jar.xml</tt> file is defined in your EAR file, the OC4J container generates one during deployment. In this case, to specify a value for <tt>db-table-gen</tt>, use the EclipseLink system property <tt>eclipselink.defaultmapping.dbTableGenSetting</tt>. For example: <tt>-Declipselink.defaultmapping.dbTableGenSetting="DropAndCreate"</tt>.

+

+

The <tt>orion-ejb-jar.xml</tt> property overrides the system property. If both the <tt>orion-ejb-jar.xml</tt> property and the system property are present, EclipseLink retrieves the setting from the <tt>orion-ejb-jar.xml</tt> file.

+

+

This setting overrides <tt>autocreate-tables</tt> and <tt>autodelete-tables</tt> configuration at the application (EAR) or system level. For more information, see [[Using%20the%20Schema%20Manager%20(ELUG)#Creating Database Tables Automatically|Creating Database Tables Automatically]].

|- align="left" valign="top"

|- align="left" valign="top"

| id="r3c1-t24" headers="r1c1-t24" align="left" |

| id="r3c1-t24" headers="r1c1-t24" align="left" |

<tt>extended-table-names</tt>

<tt>extended-table-names</tt>

| headers="r3c1-t24 r1c2-t24" align="left" |

| headers="r3c1-t24 r1c2-t24" align="left" |

−

An element used if the generated table names are not long enough to be unique. Values are restricted to <tt>true</tt> or <tt>false</tt> (default). When set to <tt>true</tt>, the EclipseLink run time will ensure that generated tables names are unique.In default mapping, each entity is mapped to one table. The only exception is in many-to-many mappings where there is one extra relation table involved in the source and target entities.When <tt>extended-table-names</tt> is set to <tt>false</tt> (the default), a simple table naming algorithm is used as follows: table names are defined as <tt>TL_<bean_name></tt>. For example, if the bean name is <tt>Employee</tt>, the associated table name would be <tt>TL_EaMPLOYEE</tt>.

+

An element used if the generated table names are not long enough to be unique. Values are restricted to <tt>true</tt> or <tt>false</tt> (default). When set to <tt>true</tt>, the EclipseLink run time will ensure that generated tables names are unique.

−

However, if the same entity is defined in multiple JAR files in an application, or across multiple applications, table-naming collision is inevitable.<br>To address this problem, set <tt>extended-table-names</tt> to <tt>true</tt>. When set to <tt>true</tt>, EclipseLink uses an alternative table-naming algorithm as follows: table names are defined as ''<tt><bean_name>_<jar_name>_<app_name></tt>''. This algorithm uses the combination of bean, JAR, and EAR names to form a table name unique across the application. For example, given a bean named <tt>Employee</tt>, which is in <tt>Test.jar</tt>, which is in <tt>Demo.ear</tt> (and the application name is "<tt>Demo</tt>"), then the corresponding table name will be <tt>EMPLOYEE_TEST_DEMO</tt>.If there is no <tt>orion-ejb-jar.xml</tt> file defined in the EAR file, the OC4J container generates one during deployment. In this case, to specify a value for <tt>extended-table-names</tt>, use the EclipseLink system property <tt>eclipselink.defaultmapping.useExtendedTableNames</tt>. For example: <tt>-Declipselink.defaultmapping.useExtendedTableNames="true"</tt>.The <tt>orion-ejb-jar.xml</tt> property overrides the system property. If both the <tt>orion-ejb-jar.xml</tt> property and the system property are present, EclipseLink retrieves the setting from the <tt>orion-ejb-jar.xml</tt> file.

+

In default mapping, each entity is mapped to one table. The only exception is in many-to-many mappings where there is one extra relation table involved in the source and target entities.

+

+

When <tt>extended-table-names</tt> is set to <tt>false</tt> (the default), a simple table naming algorithm is used as follows: table names are defined as <tt>TL_<bean_name></tt>. For example, if the bean name is <tt>Employee</tt>, the associated table name would be <tt>TL_EaMPLOYEE</tt>.

+

+

However, if the same entity is defined in multiple JAR files in an application, or across multiple applications, table-naming collision is inevitable.

+

+

To address this problem, set <tt>extended-table-names</tt> to <tt>true</tt>. When set to <tt>true</tt>, EclipseLink uses an alternative table-naming algorithm as follows: table names are defined as ''<tt><bean_name>_<jar_name>_<app_name></tt>''. This algorithm uses the combination of bean, JAR, and EAR names to form a table name unique across the application. For example, given a bean named <tt>Employee</tt>, which is in <tt>Test.jar</tt>, which is in <tt>Demo.ear</tt> (and the application name is "<tt>Demo</tt>"), then the corresponding table name will be <tt>EMPLOYEE_TEST_DEMO</tt>.

+

+

If there is no <tt>orion-ejb-jar.xml</tt> file defined in the EAR file, the OC4J container generates one during deployment. In this case, to specify a value for <tt>extended-table-names</tt>, use the EclipseLink system property <tt>eclipselink.defaultmapping.useExtendedTableNames</tt>. For example: <tt>-Declipselink.defaultmapping.useExtendedTableNames="true"</tt>.

+

+

The <tt>orion-ejb-jar.xml</tt> property overrides the system property. If both the <tt>orion-ejb-jar.xml</tt> property and the system property are present, EclipseLink retrieves the setting from the <tt>orion-ejb-jar.xml</tt> file.

|}

|}

−

==Configuring the weblogic-ejb-jar.xml File for BEA WebLogic Server==

+

-->

−

Before you deploy a EclipseLink application to a BEA WebLogic Server, you must modify the <tt>weblogic-ejb-jar.xml</tt> file.

+

+

+

+

==Configuring the weblogic-ejb-jar.xml File for WebLogic Server==

+

Before you deploy a EclipseLink application to Oracle WebLogic Server, you must modify the <tt>weblogic-ejb-jar.xml</tt> file.

Avoid the <tt>weblogic-ejb-jar.xml</tt> tags that EclipseLink either does not support or does not require (see [[#What You May Need to Know About Unsupported weblogic-ejb-jar.xml File Tags|What You May Need to Know About Unsupported weblogic-ejb-jar.xml File Tags]]).

Avoid the <tt>weblogic-ejb-jar.xml</tt> tags that EclipseLink either does not support or does not require (see [[#What You May Need to Know About Unsupported weblogic-ejb-jar.xml File Tags|What You May Need to Know About Unsupported weblogic-ejb-jar.xml File Tags]]).

Line 2,426:

Line 388:

===What You May Need to Know About Unsupported weblogic-ejb-jar.xml File Tags===

===What You May Need to Know About Unsupported weblogic-ejb-jar.xml File Tags===

The <tt>weblogic-ejb-jar.xml</tt> file includes the following tags that EclipseLink either does not support or does not require:

The <tt>weblogic-ejb-jar.xml</tt> file includes the following tags that EclipseLink either does not support or does not require:

−

* <tt>concurrency-strategy</tt><nowiki>: This tag specifies how WebLogic manages concurrent users for a given bean. Because EclipseLink manages concurrent access internally, it does not require this tag.</nowiki><br>For more information about the EclipseLink concurrency strategy, see [[Configuring%20a%20Descriptor%20(ELUG)#Configuring Locking Policy|Configuring Locking Policy]].

+

* <tt>concurrency-strategy</tt><nowiki>: This tag specifies how Oracle WebLogic Server manages concurrent users for a given bean. Because EclipseLink manages concurrent access internally, it does not require this tag.</nowiki><br>For more information about the EclipseLink concurrency strategy, see [[Configuring%20a%20Descriptor%20(ELUG)#Configuring Locking Policy|Configuring Locking Policy]].

* <tt>db-is-shared</tt><nowiki>: Because EclipseLink does not make any assumptions about the exclusivity of database access, EclipseLink does not require this tag. EclipseLink addresses multiuser access issues through various locking and refreshing policies.</nowiki>

* <tt>db-is-shared</tt><nowiki>: Because EclipseLink does not make any assumptions about the exclusivity of database access, EclipseLink does not require this tag. EclipseLink addresses multiuser access issues through various locking and refreshing policies.</nowiki>

* <tt>delay-updates-until-end-of-tx</tt><nowiki>: EclipseLink always delays updates until the end of a transaction, and does not require this tag.</nowiki>

* <tt>delay-updates-until-end-of-tx</tt><nowiki>: EclipseLink always delays updates until the end of a transaction, and does not require this tag.</nowiki>

Create Java source files, which you compile and deploy outside of Workbench.

We recommend XML deployment because XML files are easier to deploy and troubleshoot than compiled Java files. This approach gives you a very flexible configuration that enables you to make changes safely and easily. XML deployment files do not require third-party applications or compilers to deploy successfully.

Note: If you are using JPA, you can use annotations to specify most of what you formerly specified in deployment descriptors. Use deployment descriptors to override annotations or specify options not supported by annotations.

project.xml File

The project.xml file is the core of your application. It contains the descriptors and mappings you define and also includes any named queries or finders associated with your project.

XSD File Format

The project.xml file XSD is persistence_1_0.xsd and it is located in the <ECLIPSELINK_HOME>\xsds directory.

POJO Applications and Project Metadata

For a POJO application, you define your project metadata in a project.xml file.

The project.xml file provides a simple and flexible way to configure, modify, and troubleshoot the project metadata. Because of these attributes, the project.xml file is the preferred way to configure an EclipseLink project.Workbench provides a graphical tool to build and edit the project.xml file. For information on creating projects with Workbench, see Creating the project.xml File with Workbench.

JPA Applications and Project Metadata

For a JPA application, you can express project metadata using JPA annotations, persistence.xml, orm.xml, and EclipseLink JPA annotation and persistence.xml property extensions. The EclipseLink JPA persistence provider interprets all these sources of metadata to create an in-memory EclipseLink session and project at run time.

Creating the project.xml File with Workbench

Because you must synchronize the project.xml file with the classes and data source associated with your application, we recommend that you not modify this file manually. Workbench ensures proper synchronization, and is the best way to make changes to the project. Simply modify the project in Workbench and redeploy the project.xml file. Using this option reduces development time by eliminating the need to regenerate and recompile Java code each time the project changes.

Before you use either method, ensure that your classpath includes the <ECLIPSELINK_HOME>\jlib\eclipselink.jar and <ECLIPSELINK_HOME>\utils\workbench\jlib\eclipselinkmw.jar files.

Note: If you are using EJB 3.0, you can use annotations to specify most of what you formerly specified in the project.xml file. To override annotations or specify options not supported by annotations, you can still provide a project.xml file in your EJB 3.0 application.

sessions.xml File

Each EclipseLink project belongs to an EclipseLink session. A session is the facade through which an application accesses EclipseLink functionality (for more information on sessions, see EclipseLink Sessions).

When you use the XSD formatted sessions.xml file, the EclipseLink run time separates sessions.xml file validation from session instantiation. Separating XML file formatting problems from Session Manager session instantiation problems simplifies troubleshooting. Exceptions thrown during validation clearly indicate that the failure is due to an invalid sessions.xml file, as the following illustrates.

Enhanced Validation Exceptions

Exception [ECLIPSELINK-9010] (EclipseLink): org.eclipselink.exceptions.SessionLoaderException
Exception Description: A End tag does not match start tag 'session'. was thrown while parsing the XML file against the XML schema.
Internal Exception: oracle.xml.parser.v2.XMLParseException: End tag does not match start tag 'session'.

POJO Applications and Session Metadata

For a POJO application, you define your sessions in a sessions.xml file.

The sessions.xml file provides a simple and flexible way to configure, modify, and troubleshoot the application sessions. Because of these attributes, the sessions.xml file is the preferred way to configure an EclipseLink session.EclipseLink provides graphical toosl to build and edit the sessions.xml file. For information see Creating a Session.

JPA Applications and Session Metadata

For a JPA application, you can express session metadata using JPA annotations, persistence.xml, orm.xml, and EclipseLink JPA annotation and persistence.xml property extensions. The EclipseLink JPA persistence provider interprets all these sources of metadata to create an in-memory EclipseLink session and project at run time.

Creating Deployment Files for Java Applications

In a Java application, EclipseLink does not use a Java EE container for deployment. Instead, it relies on EclipseLink mechanisms to provide functionality and persistence. The key elements of this type of application are the lack of a Java EE container and the fact that you deploy the application by placing the application JAR file on the classpath.

Creating Deployment Files for Session Bean Applications

Session beans generally model a process, operation, or service and as such, are not persistent. You can build EclipseLink applications that wrap interaction with EclipseLink in session beans. Session beans execute all EclipseLink-related operations on behalf of the client.

This type of design uses JTS and externally managed transactions, but does not incur the overhead associated with persistence applications. Session bean applications also scale and deploy easily.

What You May Need to Know About Unsupported weblogic-ejb-jar.xml File Tags

The weblogic-ejb-jar.xml file includes the following tags that EclipseLink either does not support or does not require:

concurrency-strategy: This tag specifies how Oracle WebLogic Server manages concurrent users for a given bean. Because EclipseLink manages concurrent access internally, it does not require this tag.For more information about the EclipseLink concurrency strategy, see Configuring Locking Policy.

db-is-shared: Because EclipseLink does not make any assumptions about the exclusivity of database access, EclipseLink does not require this tag. EclipseLink addresses multiuser access issues through various locking and refreshing policies.

delay-updates-until-end-of-tx: EclipseLink always delays updates until the end of a transaction, and does not require this tag.

finders-load-bean: EclipseLink always loads the bean upon execution of the finder, and does not require this tag.

pool: EclipseLink does not use a pooling strategy for entity beans. This avoids object-identity problems that can occur due to pooling.

lifecycle: This element manages beans that follow a pooling strategy. Because EclipseLink does not use a pooling strategy, EclipseLink ignores this tag.

is-modified-method-name: EclipseLink does not require a bean developer-defined method to detect changes in the object state.

isolation-level: Because isolation level settings for the cache or database transactions are specified in the EclipseLink project, EclipseLink ignores this tag.

cache: Because you define EclipseLink cache properties in Workbench, this tag is unnecessary.