Property pages

Strategy

Specify the strategy to use when mapping a class or class hierarchy:

• Single table – All classes in the hierarchy are mapped to a single table.

• Joined – The root of the hierarchy is mapped to a single table; each child maps to its own table.

• Table per class – Each class is mapped to a separate table.

This field corresponds to the @Inheritance annotation.

Single table

Entity

Discriminator Value

Specify the discriminator value used to differentiate an entity in this inheritance hierarchy. The value must conform to the specified Discriminator Type.

Entity

Discriminator Column

These fields are available when using a Single or Joined inheritance strategy.

This field corresponds to the @DiscriminatorColumn annotation.

Use the Details area to define the Length and Column definition of this Discriminator Column.

Name

Name of the discriminator column

Entity

Type

Set this field to set the discriminator type to Char or Integer (instead of its default: String). The Discriminator Value must conform to this type.

String

Entity

Length

The column length for String-based discriminator types.

0

Entity

Column definition

The SQL fragment that is used when generating the DDL for the discriminator column.

Entity

Primary Key Join Columns

Use to override the default primary key join columns. Select Override Default, then click Add to select new Join Column with the Add Primary Key Join Column dialog.

This field corresponds with @PrimaryKeyJoinColumn annotation.

Entity

Column

The database column that contains the value for the attribute. This field corresponds to the @Column annotation.

By default, the Column is assumed to be named identically to the attribute and always included in the INSERT and UPDATE statements.

Name

The database column that contains the value for the attribute.

Table

Name of the database table that contains the selected column.

Details

Insertable

Specifies if the column is always included in SQL INSERT statements.

True

Updatable

Specifies if this column is always included in SQL UPDATE statements.

True

Unique

Sets the UNIQUE constraint for the column.

False

Nullable

Specifies if the column allows null values.

True

Length

Sets the column length.

255

Precision

Sets the precision for the column values.

0

Scale

Sets the number of digits that appear to the right of the decimal point.

0

Column definition

The SQL fragment that is used when generating the DDL for the column.

Fetch

Defines how data is loaded from the database:

• Eager – Data is loaded in before it is actually needed.

• Lazy – Data is loaded only when required by the transaction.

Eager

Optional

Specifies if this field is can be null.

True

Mutable

Specify if the value of a complex field type can be changed (or not changed) instead of being replaced.

True

Target class

The class (basic or embeddable) that is the element type of the collection.

Fetch

Defines how data is loaded from the database:

• Eager – Data is loaded in before it is actually needed.

• Lazy – Data is loaded only when required by the transaction.

Lazy

Join fetch

The type of fetch to use:

• Inner – Provides the inner join fetching of the related object.

  Note: Inner joining does not allow for null or empty values

• Outer – Provides the outer join fetching of the related object

  Note: Outer joining allows for null or empty values.

None

Collection Table

Name

Name of the database table used for the mapping.

Schema

Database schema of the Collection Table.

Catalog

Database Catalog of the Collection Table.

Join Columns

Override default

Click Add to create a new join column, by using the Add Join Column dialog.

0

Column

The database column that contains the value for the attribute. This field corresponds to the @Column annotation.

By default, the Column is assumed to be named identically to the attribute.

Name

The database column that contains the value for the attribute.

Table

Name of the database table that contains the selected column.

Details

Insertable

Specifies if the column is always included in SQL INSERT statements.

True

Updatable

Specifies if this column is always included in SQL UPDATE statements.

True

Unique

Sets the UNIQUE constraint for the column.

False

Nullable

Specifies if the column allows null values.

True

Length

Sets the column length.

255

Precision

Sets the precision for the column values.

0

Scale

Sets the number of digits that appear to the right of the decimal point.

0

Column definition

The SQL fragment that is used when generating the DDL for the column.

Mutable

Specify if the value of a complex field type can be changed (or not changed) instead of being replaced.

True

Target entity

The persistent entity to which the attribute is mapped.

Fetch

Defines how data is loaded from the database:

• Eager – Data is loaded in before it is actually needed.

• Lazy – Data is loaded only when required by the transaction.

Lazy

Join fetch

The type of fetch to use:

• Inner – Provides the inner join fetching of the related object.

  Note: Inner joining does not allow for null or empty values

• Outer – Provides the outer join fetching of the related object

  Note: Outer joining allows for null or empty values.

None

Cascade

Specify which operations are propagated throughout the entity.

• All – All operations

• Persist

• Merge

• Move

• Remove

• Refresh

True

Target entity

The persistent entity to which the attribute is mapped.

You do not need to explicitly specify the target entity, since it can be inferred from the type of object being referenced.

null

Fetch

Defines how data is loaded from the database:

• Eager – Data is loaded in before it is actually needed.

• Lazy – Data is loaded only when required by the transaction.

Lazy

Join fetch

The type of fetch to use:

• Inner – Provides the inner join fetching of the related object.

  Note: Inner joining does not allow for null or empty values

• Outer – Provides the outer join fetching of the related object

  Note: Outer joining allows for null or empty values.

Optional

Specifies if this field is can be null.

True

Cascade

Specify which operations are propagated throughout the entity.

• All – All operations

• Persist

• Merge

• Move

• Remove

• Refresh

True

Target entity

The persistent entity to which the attribute is mapped.

Fetch

Defines how data is loaded from the database:

• Eager – Data is loaded in before it is actually needed.

• Lazy – Data is loaded only when required by the transaction.

Lazy

Join fetch

The type of fetch to use:

• Inner – Provides the inner join fetching of the related object.

  Note: Inner joining does not allow for null or empty values

• Outer – Provides the outer join fetching of the related object

  Note: Outer joining allows for null or empty values.

Private owned

Specify that a relationship is privately owned; target object is a dependent part of the source object and is not referenced by any other object and cannot exist on its own.

Orphan removal

False

Cascade

Specify which operations are propagated throughout the entity.

• All – All operations

• Persist

• Merge

• Move

• Remove

• Refresh

True

Target entity

The persistent entity to which the attribute is mapped.

Fetch

Defines how data is loaded from the database:

• Eager – Data is loaded in before it is actually needed.

• Lazy – Data is loaded only when required by the transaction.

Eager

Join fetch

The type of fetch to use:

• Inner – Provides the inner join fetching of the related object.

  Note: Inner joining does not allow for null or empty values

• Outer – Provides the outer join fetching of the related object

  Note: Outer joining allows for null or empty values.

Optional

Specifies if this field is can be null.

True

Private owned

Specify that a relationship is privately owned; target object is a dependent part of the source object and is not referenced by any other object and cannot exist on its own.

False

Orphan removal

False

Cascade

Specify which operations are propagated throughout the entity.

• All – All operations

• Persist

• Merge

• Move

• Remove

• Refresh

True

Column

The database column that contains the value for the attribute. This field corresponds to the @Column annotation.

By default, the Column is assumed to be named identically to the attribute.

Name

The database column mapped to the entity attribute.

By default, the Column is assumed to be named identically to the attribute and always included in the INSERT and UPDATE statements.

Table

Name of the database table that contains the selected column.

Details

Insertable

Specifies if the column is always included in SQL INSERT statements.

True

Updatable

Specifies if this column is always included in SQL UPDATE statements.

True

Unique

Sets the UNIQUE constraint for the column.

False

Nullable

Specifies if the column allows null values.

True

Length

Sets the column length.

255

Precision

Sets the precision for the column values.

0

Scale

Sets the number of digits that appear to the right of the decimal point.

0

Column definition

The SQL fragment that is used when generating the DDL for the column.

Mutable

Specify if the value of a complex field type can be changed (or not changed) instead of being replaced.

True

Default

Basic mapping, ID mapping, and Version mapping

LOB

Specify if the field is mapped to java.sql.Clob or java.sql.Blob.

This field corresponds to the @Lob annotation.

Basic mapping

Temporal

Specifies if this field is one of the following:

• Date – java.sql.Date

• Time – java.sql.Time

• Timestamp – java.sql.Timestamp

This field corresponds to the @Temporal annotation.

Basic mapping, ID mapping, and Version mapping

Enumerated

Specify how to persist enumerated constraints if the String value suits your application requirements or to match an existing database schema.

• ordinal

• String

This field corresponds to the @Enumerated annotation.

Basic mapping

Converted

Converter name:

• None (default) –

• class-instance –

• serialized –

Basic mapping, ID mapping, and Version mapping

Mapped by

The field in the database table that "owns" the relationship. This field is required only on the non-owning side of the relationship.

Many-to-many mapping, One-to-many mapping, and One-to-one mapping

Attribute

Primary key join columns

One-to-one mapping

Join columns

By default, the name is assumed to be the primary tables associated with the entities concatenated with an underscore.

Select Override Default, then Add, Edit, or Remove the join columns.

Many-to-one mapping, One-to-many mapping, and One-to-one mapping

Join table

Many-to-many mapping, Many-to-one mapping, One-to-many mapping, and One-to-one mapping

Name

Name of the join table that contains the foreign key column.You must specify the join table on the owning side.

By default, the name is assumed to be the primary tables associated with the entities concatenated with an underscore.

Schema

Schema of the table

Catalog

Catalog of the table

Join columns

The foreign key columns of the join table which reference the primary table of the entity owning the association. (that is, the owning side of the association).

Inverse join columns

The foreign key columns of the join table which reference the primary table of the entity that does not own the association. (that is, the inverse side of the association).

None

Many-to-one mapping and One-to-one mapping

ID

Many-to-one mapping and One-to-one mapping

Maps ID

Many-to-one mapping and One-to-one mapping

Primary Key Generation

These fields define how the primary key is generated. These fields correspond to the @GeneratedValue annotation.

Generated Value

Strategy

• Auto

• Identity – Values are assigned by the database's Identity column.

• Sequence – Values are assigned by a sequence table (see Sequence Generator).

• Table – Values are assigned by a database table (see Table Generator).

Auto

Generator Name

Unique name of the generated value.

Table Generator

These fields define the database table used for generating the primary key and correspond to the @TableGenerator annotation.

These fields apply only when Strategy = Table.

Name

Unique name of the generator.

Table

Database table that stores the generated ID values.

Schema

Schema of the table

Catalog

Catalog of the table

Primary Key Column

The column in the table generator's Table that contains the primary key.

Value Column

The column that stores the generated ID values.

Primary Key Column Value

The value for the Primary Key Column in the generator table.

Allocation size

Initial value

Sequence Generator

These fields define the specific sequence used for generating the primary key and correspond to the @SequenceGenerator annotation.

These fields apply only when Strategy = Sequence.

Name

Name of the sequence table to use for defining primary key values.

Sequence

Unique name of the sequence.

Schema

Catalog

Allocation size

Initial value

Package

The Java package that contains the persistent entities. Click Browse and select the package

Schema

The database schema that contains the Table.

This field corresponds to the <schema> element in the orm.xml file.

Catalog

The database catalog that contains the Table.

This field corresponds to the <catalog> element in the orm.xml file.

Access

Specify the default access method for the variables in the project:

• Property

• Field

This field corresponds to the <access> element in the orm.xml file.

XML Mapping Data Complete

Specifies that the Java classes in this persistence unit are fully specified by their metadata. Any annotations will be ignored.

This field corresponds to the <xml-mapping-metadata-complete> element in the orm.xml file.

Cascade Persist

Adds cascade-persist to the set of cascade options in entity relationships of the persistence unit.

This field corresponds to the <cascade-persist> element in the orm.xml file.

Schema

The database schema that contains the Table.

This field corresponds to the <schema> element in the orm.xml file.

Catalog

The database catalog that contains the Table.

This field corresponds to the <catalog> element in the orm.xml file.

Access

Specify how the entity its access instance variables.

• Property – Persistent state accessed through the property accessor methods. The property accessor methods must be public or private.

• Field – Instance variables are accessed directly. All non-transient instance variables are persistent.

Deliminated identifiers

Generators

Click Add to create a new table or sequence generator, or select an existing generator and click Remove, to add or remove a generator.

Sequence Generators

Name

Sequence

Schema

Catalog

Allocation size

50

Initial value

1

Table Generators

Name

Table

Schema

Catalog

Primary key column value

Allocation size

50

Initial value

1

Queries

Displays the existing Named and Native queries.

Click Add to add a named query, or Add Native for a native query.

For named queries, enter the query in the Query field.

For native queries, select a result class, then enter the query in the Query field.

Named Queries

Name

Query

Lock mode

None

Native Queries

Name

Result class

Query

Query Hints

Displays the existing query hints (Name and Value).

Click Add to add a new query hint.

General

Name

Enter the name of the persistence unit.

Defines the <persistence-unit name> element.

The project name

Persistence provider

Enter the name of the persistence provider.

Defines the <provider> element.

Determined by the server

Description

Enter a description for this persistence unit. This is an optional property.

Defines the <description> element.

Managed Classes

Classes

Click Add to add a new class, or select an existing class and click Remove, to add or remove the classes managed through the persistence unit.

Defines the <class> element.

Select a class and click Open to modify the class in the editor.

Exclude Unlisted Classes

Select to include all annotated entity classes in the root of the persistence unit.

Defines the <exclude-unlisted-classes> element.

False

XML Mapping Files

Files

Click Add to select an XML mapping file, or select an existing file and click Remove, to add or remove an object/relational mapping XML files that define the classes to be managed by the persistence unit.

Defines the <mapping-file> element.

Meta-INF\orm.xml

Exclude default EclipseLink XML mapping file

Select to include all annotated EclipseLink mapping files. Defines the eclipselink.exclude-eclipselink-orm property element.Note: This field applies only when using EclipseLink JPA implementation

False

JAR Files

Files

Click Add to select a JAR file, or select an existing file and click Remove, to add or remove JAR files and libraries in the persistence unit.

Transaction type

Specify if the connection for this persistence unit uses one of the following transaction types:

• Default -- Select to use the container used by the container.

• JTA (Java Transaction API) -- Transactions of the Java EE server.

• Resource Local -- Native actions of a JDBC driver that are referenced by a persistence unit.

JTA

Batch writing

Specify the use of batch writing to optimize transactions with multiple write operations.

Set the value of this property into the session at deployment time.

Note: This property applies when used both in a Java SE and Java EE environment.

The following are the valid values for oracle.toplink.config.BatchWriting:

• JDBC–Use JDBC batch writing.

• Buffered–Do not use either JDBC batch writing nor native platform batch writing.

• OracleJDBC–Use both JDBC batch writing and Oracle native platform batch writing.

• None–Do not use batch writing (turn it off).

None

Statement caching

Specify if the query caches its JDBC statement. If enabled, you can also set the number of statements to cache.

50

Native SQL

Specify if Dali includes platform-specific (that is, "native") SQL statements. If false, Dali uses generic SLQ.

False

Database

JTA Data Source Name

If you selected JTA as the transaction type, then enter the name of the default JTA data source for the persistence unit.

Non-JTA Data Source Name

If you selected Resource Local as the transaction type, then enter the name of the non-JTA data source.

This property is not available for projects using the Generic platform.

EclipseLink connection pool

Define the connection pool driver, URL, user name and password.

These properties are note available for projects using the Generic platform.

Bind parameters

Control whether or not the query uses parameter binding.

Note: This property applies when used in a Java SE environment.

This property is not available for projects using the Generic platform.

True

Read Connection

The maximum and minimum number of connections allowed in the JDBC read connection pool.

Note: These property apply when used in a Java SE environment.

These properties are not available for projects using the Generic platform

Minimum: 2

Maximum 2

Write Connection

The maximum and minimum number of connections allowed in the JDBC read connection pool.

Note: These property apply when used in a Java SE environment.

These properties are not available for projects using the Generic platform

Minimum: 5

Maximum 10

Exclusive connections

These fields are available only when Transaction Type is Local Resource.

Exclusive connection mode

Specify when Dali performs reads through the write connection.

• Always – Create an exclusive isolated client session if reading an isolated entity, otherwise create an exclusive client session.

• Isolated – Create an exclusive isolated client session if reading an isolated entity, otherwise raise an error.

• Transactional – Create an isolated client session if some or all entities require isolated cache, otherwise create a client session.

Transactional

Lazy connection acquisition

Specify if Dali acquires write connections lazily.

True

Weaving

Specifies if weaving of the entity classes is performed. The EclipseLink JPA persistence provider uses weaving to enhance JPA entities for such properties as lazy loading, change tracking, fetch groups, and internal optimizations. Select from the following options:

• No Weaving

• Weave Dynamically

• Weave Statically -- Use this option if you plan to execute your application outside of a Java EE 5 container in an environment that does not permit the use of -javaagent:eclipselink.jar on the JVM command line. This assumes that classes have already been statically woven. Run the static weaver on the classes before deploying them.

Weave Dynamically

Lazy

Select this option to enable lazy weaving.

True

Fetch Groups

Select this option to enable fetch groups through weaving. Set this option to false if:

• There is no weaving.

• Classes should not be changed during weaving (for example, when debugging).

Set this property to false for platforms where it is not supported.

True

Internal

Specify if Dali uses internal optimizations through weaving.

If enabled, enables lazy one-to-one and many-to-one mappings through weaving.

True

Eager

Specify if Dali uses indirection on eager relationships.

False

Change Tracking

Select this option to use weaving to detect which fields or properties of the object change.

True

Validation only

Specify if Dali should validate deployments by initializing descriptors but not connecting to the data source.

True

Mapping files schema validation

False

Throw exceptions

Select this option to set EclipseLink to throw an exception or log a warning when it encounters a problem with any of the files listed in a persistence.xml file <mapping-file> element.

True

Exception handler

Select (or create) a Java class (that implements the org.eclipse.persistence.exceptions.ExceptionHandler interface) to handle exceptions.

Session Customizer

Select a session customizer class: a Java class that implements the eclipselink.tools.sessionconfiguration.SessionCustomizer interface and provides a default (zero-argument) constructor. Use this class' customize method, which takes an eclipselink.sessions.Session, to programmatically access advanced EclipseLink session API.

Profiler

Specify which performance profiler to use in order to capture runtime statistics.

• No Profiler – Do not use a performance profiler.

• Performance Profiler – Use EclipseLink performance profiler (org.eclipse.persistence.tools.profiler.PerformanceProfiler class).

• Query Monitor – Monitor query executions and cache hits (org.eclipse.persistence.tools.profiler.QueryMonitor class).

NoProfiler

Shared cache mode

Select one of the following as the shared cache mode:

• All – .

• None –

• Enable Selective –

• Disable Selective –

• Unspecified –

Disable selective

Default Cache Type

Select one of the following as the Default Cache Type:

• Weak with Soft Subcache–This option is similar to Weak with Hard Subcache except that it maintains a most frequently used subcache that uses soft references. The size of the subcache is proportional to the size of the identity map. The subcache uses soft references to ensure that these objects are garbage-collected only if the system is low on memory.

  Use this identity map in most circumstances as a means to control memory used by the cache.

• Weak with Hard Subcache–This option is similar to Soft with Weak subcache except that it maintains a most frequently used subcache that uses hard references. Use this identity map if soft references are not suitable for your platform.

• Weak–This option is similar to Full, except that objects are referenced using weak references. This option uses less memory than Full, allows complete garbage collection and provides full caching and guaranteed identity.

  Use this identity map for transactions that, once started, stay on the server side.

• Soft–This option is similar to Weak except that the map holds the objects using soft references. This identity map enables full garbage collection when memory is low. It provides full caching and guaranteed identity.

• Full–This option provides full caching and guaranteed identity: all objects are cached and not removed.

  Note: This process may be memory-intensive when many objects are read.

• None–This option does not preserve object identity and does not cache objects.This option is not recommended.

Weak with soft subcache

Default Cache Size

Set the size (maximum number of objects) of the cache.

100

Flush clear cache

Select one of the following as the Default Cache Type:

• Drop – This mode is the fastest and uses the least memory. However, after commit the shared cache might potentially contain stale data.

• Drop Invalidate – Classes that have at least one object updated or deleted are invalidated in the shared cache at commit time. This mode is slower than Drop, but as efficient memory usage-wise, and prevents stale data.

• Merge – Drop classes from the EntityManager's cache of objects that have not been flushed. This mode leaves the shared cache in a perfect state after commit. However, it is the least memory-efficient mode; the memory might even run out in a very large transaction.

Drop Invalidate

Logging Level

Specifies the amount and detail of log output by selecting the log level (in ascending order of information):

The following are the valid values for the java.util.logging.Level:

• OFF–disables logging

• SEVERE–logs exceptions indicating TopLink cannot continue, as well as any exceptions generated during login. This includes a stack trace.

• WARNING–logs exceptions that do not force TopLink to stop, including all exceptions not logged with severe level. This does not include a stack trace.

• INFO–logs the login/logout per sever session, including the user name. After acquiring the session, detailed information is logged.

• CONFIG–logs only login, JDBC connection, and database information.

• FINE–logs SQL.

• FINER–similar to warning. Includes stack trace.

• FINEST–includes additional low level information.

Example: persistence.xml file

<property name="eclipselink.logging.level" value="INFO"/>

Info

Timestamp

Control whether the timestamp is logged in each log entry.

The following are the valid values:

• True–log a timestamp.

• False–do not log a timestamp.

Example: persistence.xml file

<property name="eclipselink.logging.timestamp" value="false"/>

True

Thread

Control whether a thread identifier is logged in each log entry.

The following are the valid values:

• true–log a thread identifier.

• false–do not log a thread identifier.

True

Session

Control whether an EclipseLink session identifier is logged in each log entry.

The following are the valid values:

• true–log a EclipseLink session identifier.

• false–do not log a EclipseLink session identifier.

Example: persistence.xml file

<property name="eclipselink.logging.session" value="false"/>

true

Exceptions

Control whether the exceptions thrown from within the EclipseLink code are logged prior to returning the exception to the calling application. Ensures that all exceptions are logged and not masked by the application code.

The following are the valid values:

• true–log all exceptions.

• false–do not log exceptions.

Example: persistence.xml file

<property name="eclipselink.logging.exceptions" value="true"/>

false

Log file

Specify a file location for the log output (instead of the standard out).

Example: persistence.xml file

<property name="eclipselink.logging.file" value="C:\myout\" />

stdout

Logger

Select the type of logger to use:

The following are the valid values:

• DefaultLogger–the EclipseLink native logger eclipselink.logging.DefaultSessionLog.

• JavaLogger–the java.util.logging logger eclipselink.logging.JavaLog.

• ServerLogger–the java.util.logging logger eclipselink.platform.server.ServerLog. Integrates with the application server's logging as define in the eclipselink.platform.server.ServerPlatform.

• Fully qualified class name of a custom logger. The custom logger must implement the eclipselink.logging.SessionLog interface.

Example: persistence.xml file

<property name="eclipselink.logging.logger" value="acme.loggers.MyCustomLogger" />

DefaultLogger

Logging Categories

You can also specify the logging level for the following specific categories:

• SQL

• Connection

• Event

• Query

• Cache

• Propagation

• EJB

• DMS

• EJB or metatdata

• JPA metadata

• Weaving

• Properties

• Server

Info

Session Options

Session Name

Specify the name by which the EclipseLink session is stored in the static session manager. Use this option if you need to access the EclipseLink shared session outside of the context of the JPA or to use a pre-existing EclipseLink session configured through a EclipseLink sessions.xml file

Valid values: a valid EclipseLink session name that is unique in a server deployment.

Example: persistence.xml file

<property name="eclipselink.session-name" value="MySession"/>

Sessions XML

Specify persistence information loaded from the EclipseLink session configuration file (sessions.xml).

You can use this option as an alternative to annotations and deployment XML. If you specify this property, EclipseLink will override all class annotation and the object relational mapping from the persistence.xml, as well as ORM.xml and other mapping files, if present.

Indicate the session by setting the eclipselink.session-name property.

Note: If you do not specify the value for this property, sessions.xml file will not be used.

Valid values: the resource name of the sessions XML file.

Example: persistence.xml file

<property name="toplink.session-xml" value="mysession.xml"/>

Target Database

Select the target database. You can also set the value to the fully qualified class name of a subclass of the org.eclipse.persistence.platform.DatabasePlatform class.

Example: persistence.xml file

<property name="eclipselink.target-database" value="Oracle"/>

Auto

Target Server

Select the target server for your JPA application.

Example: persistence.xml file

<property name="eclipselink.target-server" value="OC4J_10_1_3"/>

None

Event Listener

Specify a descriptor event listener to be added during bootstrapping.

Valid values: qualified class name for a class that implements the eclipselink.sessions.SessionEventListener interface.

Example: persistence.xml file

<property name="eclipselink.session-event-listener" value="mypackage.MyClass.class"/>

Include Descriptor Queries

Enable or disable the default copying of all named queries from the descriptors to the session. These queries include the ones defined using EclipseLink API, descriptor amendment methods, and so on.

True

Miscellaneous Options

Temporal mutable

Specify if all Date and Calendar persistent fields should be handled as mutable objects.

Example: persistence.xml file

<property name="eclipselink.temporal.mutable" value="true"/>

False

Lock timeout

5

Query timeout

5

Validation mode

Auto

Validate pre-persist group

Validate pre-update group

Validate pre-remove group

DDL Generation Type

Select the type of DDL generation:

• None -- Do not generate DDL; no schema is generated.

• Create Tables -- Create DDL for non-existent tables; leave existing tables unchanged.

• Drop and Create Tables -- Create DDL for all tables; drop all existing tables.

None

Output Mode

Select the DDL generation target:

• Both -- Generate SQL files and execute them on the database.

• Database -- Execute SQL on the database only (do not generate SQL files).

• SQL Script -- Generate SQL files only (do not execute them on the database).

DDL Generation Location

Specify where EclipseLink writes DDL output. Specify a file specification to a directory in which you have write access. The file specification may be relative to your current working directory or absolute. If it does not end in a file separator, then EclipseLink appends one that is valid for your operating system.

Create DDL File Name

Specify the file name of the DDL file that EclipseLink generates that contains SQL statements for creating tables for JPA entities. Specify a file name valid for your operating system.

createDDL.jdbc

Drop DDL File Name

Specify the file name of the DDL file that EclipseLink generates that contains SQL statements for dropping tables for JPA entities.

dropDDL.jdbc