Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Creating a Relational Project (ELUG)"
m |
m |
||
| Line 1: | Line 1: | ||
<div style="margin:5px;float:right;border:1px solid #000000;padding:5px">__TOC__ | <div style="margin:5px;float:right;border:1px solid #000000;padding:5px">__TOC__ | ||
| − | [[Special:Whatlinkshere/Creating a Relational Project (ELUG)|Related Topics]]</div> | + | [[Special:Whatlinkshere/Creating a Relational Project (ELUG)|Related Topics]]</div>This section describes the various components that you must configure in order to create a relational project. |
| − | + | ||
| − | This section describes the various components that you must configure in order to create a relational project. | + | |
For information on how to create more than one type of EclipseLink projects, see [[Creating%20a%20Project%20(ELUG)|Creating a Project]]. | For information on how to create more than one type of EclipseLink projects, see [[Creating%20a%20Project%20(ELUG)|Creating a Project]]. | ||
| − | + | You can create a project using the Workbench or Java code. We recommend using the Workbench to create projects and generate deployment XML or Java source versions of the project for use at run time. For more information, see: | |
| − | + | *[[Creating%20a%20Project%20(ELUG)#How to Create a Project Using the Workbench|How to Create a Project Using the Workbench]] | |
| − | + | *[[Creating%20a%20Project%20(ELUG)#How to Create a Project Using Java|How to Create a Project Using Java]]. | |
| − | + | ||
| − | You can create a project using the Workbench or Java code. | + | |
| − | + | ||
| − | We recommend using the Workbench to create projects and generate deployment XML or Java source versions of the project for use at run time. For more information | + | |
You can use EclipseLink to create a relational project, if any of the following conditions are met: | You can use EclipseLink to create a relational project, if any of the following conditions are met: | ||
| − | |||
* You have both an object and data model: see [[#Creating a Project from an Existing Object and Data Model|Creating a Project from an Existing Object and Data Model]]. | * You have both an object and data model: see [[#Creating a Project from an Existing Object and Data Model|Creating a Project from an Existing Object and Data Model]]. | ||
* You have an object model, but no data model yet: see [[#Creating a Project from an Existing Object Model|Creating a Project from an Existing Object Model]]. | * You have an object model, but no data model yet: see [[#Creating a Project from an Existing Object Model|Creating a Project from an Existing Object Model]]. | ||
| Line 26: | Line 19: | ||
==Creating a Project from an Existing Object and Data Model== | ==Creating a Project from an Existing Object and Data Model== | ||
| − | |||
If you have both an existing object model (Java classes for your domain objects) and data model (such as an existing database schema), use this procedure to create your EclipseLink project. | If you have both an existing object model (Java classes for your domain objects) and data model (such as an existing database schema), use this procedure to create your EclipseLink project. | ||
| Line 32: | Line 24: | ||
===How to Create a Project from an Existing Object and Data Model Using Workbench=== | ===How to Create a Project from an Existing Object and Data Model Using Workbench=== | ||
| − | + | # [[Creating%20a%20Project%20(ELUG)#How to Create a Project Using the Workbench|Create the project]]. | |
| − | # | + | # [[Configuring%20a%20Project%20(ELUG)#Configuring Project Classpath|Configure the project classpath]]. |
| − | # | + | # [[Using%20Workbench%20(ELUG)#How to Import and Update Classes|Import classes]]. |
| − | # | + | # [[Using%20Workbench%20(ELUG)#Importing Tables from a Database|Import database tables]]. |
| − | # | + | # [[Creating%20a%20Mapping%20(ELUG)#How to Create Mappings Automatically During Development Using Workbench|Automatically create mappings]]. |
| − | # | + | # [[Configuring%20a%20Project%20(ELUG)|Configure project options]]. |
| − | # | + | |
==Creating a Project from an Existing Object Model== | ==Creating a Project from an Existing Object Model== | ||
| − | |||
If you have an existing object model (Java classes for your domain objects), but you do not have a corresponding data model, use this procedure to create your EclipseLink project and automatically generate the corresponding data model. | If you have an existing object model (Java classes for your domain objects), but you do not have a corresponding data model, use this procedure to create your EclipseLink project and automatically generate the corresponding data model. | ||
| Line 49: | Line 39: | ||
===How to Create a Project from an Existing Object Model Using Workbench=== | ===How to Create a Project from an Existing Object Model Using Workbench=== | ||
| − | + | # [[Creating%20a%20Project%20(ELUG)#How to Create a Project Using the Workbench|Create the project]]. | |
| − | # | + | # [[Configuring%20a%20Project%20(ELUG)#Configuring Project Classpath|Configure the project classpath]]. |
| − | # | + | # [[Using%20Workbench%20(ELUG)#How to Import and Update Classes|Import classes]]. |
| − | # | + | |
# Generate database tables. For more information, see the following: | # Generate database tables. For more information, see the following: | ||
#* [[Using%20Workbench%20(ELUG)#Creating New Tables|Creating New Tables]] | #* [[Using%20Workbench%20(ELUG)#Creating New Tables|Creating New Tables]] | ||
| Line 58: | Line 47: | ||
#* [[Configuring%20a%20Relational%20Project%20(ELUG)|How to Configure Table Creator Java Source Options Using Workbench]] | #* [[Configuring%20a%20Relational%20Project%20(ELUG)|How to Configure Table Creator Java Source Options Using Workbench]] | ||
#* [[#How to Export Table Creator Files Using Workbench|How to Export Table Creator Files Using Workbench]] | #* [[#How to Export Table Creator Files Using Workbench|How to Export Table Creator Files Using Workbench]] | ||
| − | # | + | # [[Configuring%20a%20Project%20(ELUG)|Configure project options]]. |
==Creating a Project from an Existing Data Model== | ==Creating a Project from an Existing Data Model== | ||
| − | |||
If you have an existing data model (such as a database schema), but you do not have a corresponding data model (Java classes for domain objects), use this procedure to create your EclipseLink project and automatically generate the corresponding object model. | If you have an existing data model (such as a database schema), but you do not have a corresponding data model (Java classes for domain objects), use this procedure to create your EclipseLink project and automatically generate the corresponding object model. | ||
| Line 69: | Line 57: | ||
===How to Create a Project from an Existing Data Model Using Workbench=== | ===How to Create a Project from an Existing Data Model Using Workbench=== | ||
| − | + | # [[Creating%20a%20Project%20(ELUG)#How to Create a Project Using the Workbench|Create the project]]. | |
| − | # | + | # [[Using%20Workbench%20(ELUG)#Importing Tables from a Database|Import database tables]]. |
| − | # | + | # [[Using%20Workbench%20(ELUG)#Generating Classes and Descriptors from Database Tables|Generate classes]]. |
| − | # | + | # [[Configuring%20a%20Project%20(ELUG)#Configuring a Project|Configure project options]]. |
| − | + | ||
| − | # | + | |
==Exporting Project Information== | ==Exporting Project Information== | ||
| − | |||
Workbench generates and exports the following project information: | Workbench generates and exports the following project information: | ||
| − | + | * [[#How to Export Project Java Source Using Workbench|Project Java source]] | |
| − | * [[#How to Export Project Java Source Using Workbench|Project Java source]] | + | * [[#How to Export Table Creator Files Using Workbench|Table creator files]] |
| − | * [[#How to Export Table Creator Files Using Workbench|Table creator files]] | + | |
===How to Export Project Java Source Using Workbench=== | ===How to Export Project Java Source Using Workbench=== | ||
| − | |||
For relational projects only, you can convert the project to Java source code. Generally, the generated code executes faster and deploys easier than XML files. See [[Creating%20a%20Descriptor%20(ELUG)#Generating Java Code for Descriptors|Generating Java Code for Descriptors]] to export the model source for a ''specific descriptor'' in a project. To convert your relational project to Java source, use this procedure: | For relational projects only, you can convert the project to Java source code. Generally, the generated code executes faster and deploys easier than XML files. See [[Creating%20a%20Descriptor%20(ELUG)#Generating Java Code for Descriptors|Generating Java Code for Descriptors]] to export the model source for a ''specific descriptor'' in a project. To convert your relational project to Java source, use this procedure: | ||
# Right-click the project in the '''Navigator''' and choose '''Export''' > '''Project Java Source''' from the context menu.[[Image:expjava.gif|Export to Java Source button]]<br /> You can also choose '''Workbench''' > '''Export''' > '''Export Java Source''' or '''Selected''' > '''Export''' > '''Project Java Source''' from the menu. If you have not defined deployment and source code generation defaults (see [[Configuring%20a%20Project%20(ELUG)|Configuring a Project]]) Workbench prompts for a project class name and directory. | # Right-click the project in the '''Navigator''' and choose '''Export''' > '''Project Java Source''' from the context menu.[[Image:expjava.gif|Export to Java Source button]]<br /> You can also choose '''Workbench''' > '''Export''' > '''Export Java Source''' or '''Selected''' > '''Export''' > '''Project Java Source''' from the menu. If you have not defined deployment and source code generation defaults (see [[Configuring%20a%20Project%20(ELUG)|Configuring a Project]]) Workbench prompts for a project class name and directory. | ||
| − | |||
{| class="Note oac_no_warn" width="80%" border="1" frame="hsides" rules="groups" cellpadding="3" frame="hsides" rules="groups" | {| class="Note oac_no_warn" width="80%" border="1" frame="hsides" rules="groups" cellpadding="3" frame="hsides" rules="groups" | ||
| align="left" | | | align="left" | | ||
| − | '''''Note''''' If your Workbench project uses the UTF-8 character set, you must use a compatible JDK when compiling the exported Java source. If your project contains errors, the <tt>project.xml</tt> file may not be valid. See for information on each reported error. | + | '''''Note''''' If your Workbench project uses the UTF-8 character set, you must use a compatible JDK when compiling the exported Java source. If your project contains errors, the <tt>project.xml</tt> file may not be valid. See [[Troubleshooting an EclipseLink Application (ELUG)|Troubleshooting an EclipseLink Application]] for information on each reported error. |
|} | |} | ||
| Line 105: | Line 87: | ||
===How to Export Table Creator Files Using Workbench=== | ===How to Export Table Creator Files Using Workbench=== | ||
| − | |||
For relational projects only, you can create Java source code to generate database tables defined in the project using this procedure: | For relational projects only, you can create Java source code to generate database tables defined in the project using this procedure: | ||
| Line 123: | Line 104: | ||
[[Category: Draft]] | [[Category: Draft]] | ||
[[Category: Task]] | [[Category: Task]] | ||
| + | [[Category: ORM]] | ||
Revision as of 11:21, 14 December 2007
Contents
For information on how to create more than one type of EclipseLink projects, see Creating a Project.
You can create a project using the Workbench or Java code. We recommend using the Workbench to create projects and generate deployment XML or Java source versions of the project for use at run time. For more information, see:
You can use EclipseLink to create a relational project, if any of the following conditions are met:
- You have both an object and data model: see Creating a Project from an Existing Object and Data Model.
- You have an object model, but no data model yet: see Creating a Project from an Existing Object Model.
- You have a data model, but no object model yet: Creating a Project from an Existing Data Model.
For more information, see Introduction to Relational Projects.
Creating a Project from an Existing Object and Data Model
If you have both an existing object model (Java classes for your domain objects) and data model (such as an existing database schema), use this procedure to create your EclipseLink project.
How to Create a Project from an Existing Object and Data Model Using Workbench
- Create the project.
- Configure the project classpath.
- Import classes.
- Import database tables.
- Automatically create mappings.
- Configure project options.
Creating a Project from an Existing Object Model
If you have an existing object model (Java classes for your domain objects), but you do not have a corresponding data model, use this procedure to create your EclipseLink project and automatically generate the corresponding data model.
How to Create a Project from an Existing Object Model Using Workbench
- Create the project.
- Configure the project classpath.
- Import classes.
- Generate database tables. For more information, see the following:
- Configure project options.
Creating a Project from an Existing Data Model
If you have an existing data model (such as a database schema), but you do not have a corresponding data model (Java classes for domain objects), use this procedure to create your EclipseLink project and automatically generate the corresponding object model.
How to Create a Project from an Existing Data Model Using Workbench
Exporting Project Information
Workbench generates and exports the following project information:
How to Export Project Java Source Using Workbench
For relational projects only, you can convert the project to Java source code. Generally, the generated code executes faster and deploys easier than XML files. See Generating Java Code for Descriptors to export the model source for a specific descriptor in a project. To convert your relational project to Java source, use this procedure:
- Right-click the project in the Navigator and choose Export > Project Java Source from the context menu.
You can also choose Workbench > Export > Export Java Source or Selected > Export > Project Java Source from the menu. If you have not defined deployment and source code generation defaults (see Configuring a Project) Workbench prompts for a project class name and directory.
|
Note If your Workbench project uses the UTF-8 character set, you must use a compatible JDK when compiling the exported Java source. If your project contains errors, the project.xml file may not be valid. See Troubleshooting an EclipseLink Application for information on each reported error. |
How to Export Table Creator Files Using Workbench
For relational projects only, you can create Java source code to generate database tables defined in the project using this procedure:
- Right-click the project in the Navigator and choose Export > Table Creator Java Source from the context menu.You can also choose Workbench > Export > Table Creator Java Source or Selected > Export > Table Creator Java Source from the menu.
If you have not defined deployment and source code generation defaults (see Configuring a Project) Workbench prompts for a class name and root directory.