From: Alexey L. <lou...@us...> - 2002-12-26 07:53:17
|
User: loubyansky Date: 02/12/25 23:53:16 Modified: src/resources/org/jboss/metadata Tag: Branch_3_2 jbosscmp-jdbc_3_0.dtd Log: added optimistic locking configuration elements Revision Changes Path No revision No revision 1.19.2.4 +63 -1 jboss/src/resources/org/jboss/metadata/jbosscmp-jdbc_3_0.dtd Index: jbosscmp-jdbc_3_0.dtd =================================================================== RCS file: /cvsroot/jboss/jboss/src/resources/org/jboss/metadata/jbosscmp-jdbc_3_0.dtd,v retrieving revision 1.19.2.3 retrieving revision 1.19.2.4 diff -u -r1.19.2.3 -r1.19.2.4 --- jbosscmp-jdbc_3_0.dtd 10 Oct 2002 14:26:00 -0000 1.19.2.3 +++ jbosscmp-jdbc_3_0.dtd 26 Dec 2002 07:53:15 -0000 1.19.2.4 @@ -171,7 +171,7 @@ remove-table?, read-only?, read-time-out?, row-locking?, pk-constraint?, read-ahead?, list-cache-max?, fetch-size?, table-name?, cmp-field*, load-groups?, eager-load-group?, lazy-load-groups?, - query*, unknown-pk?, entity-command?)> + query*, unknown-pk?, entity-command?, optimistic-locking?)> <!-- Name of the entity being configured. This must match an entity declared @@ -652,3 +652,65 @@ The name of the attribute --> <!ATTLIST attribute name CDATA #REQUIRED> + +<!-- +Optimistic locking configuration +--> +<!ELEMENT optimistic-locking ( + group-name | + modified-strategy | + read-strategy | + ((version-column | timestamp-column | (key-generator-factory, field-type)), + field-name?, column-name?, (jdbc-type, sql-type)?) +)> + +<!-- +Optimistic locking field group name. +This name must match one of the entity's load-group-name. +The fields in this group will be used for optimistic locking. +--> +<!ELEMENT group-name (#PCDATA)> + +<!-- +Optimistic locking modified strategy. +This means the fields that were modified during transaction +will be used for optimistic locking +--> +<!ELEMENT modified-strategy EMPTY> + +<!-- +Optimistic locking read strategy. +This strategy implies that the fields that were read/changed +in the transaction will be used for optimistic locking +--> +<!ELEMENT read-strategy EMPTY> + +<!-- +Optimistic locking version column strategy. +Setting this element will add to entity bean additional version field +of type java.lang.Long that will be used for optimistic locking. +Each update of the entity will increase the value of this field. +--> +<!ELEMENT version-column EMPTY> + +<!-- +Optimistic locking timestamp column strategy. +Setting this element will add to entity bean additional field of type +java.util.Date that will be used for optimistic locking. +Each update of the entity will set the value of this field to the current +time. +--> +<!ELEMENT timestamp-column EMPTY> + +<!-- +Optimistic locking field type. +The type for locking field in optimistic locking. +--> +<!ELEMENT field-type (#PCDATA)> + +<!-- +Key generator factory JNDI name. +This element specifies the JNDI name of key generator factory that is +used to obtain key generator for locking column used in optimistic locking. +--> +<!ELEMENT key-generator-factory (#PCDATA)> |