[jboss-cvs] JBossAS SVN: r97714 - in projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide: en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Dec 10 22:13:08 EST 2009
Author: benlc
Date: 2009-12-10 22:13:08 -0500 (Thu, 10 Dec 2009)
New Revision: 97714
Modified:
projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/en-US/entity.xml
projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/en-US/xml-overriding.xml
projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/publican.cfg
Log:
'committing changes to callout lists for correct rendering'
Modified: projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/en-US/entity.xml
===================================================================
--- projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/en-US/entity.xml 2009-12-11 02:14:36 UTC (rev 97713)
+++ projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/en-US/entity.xml 2009-12-11 03:13:08 UTC (rev 97714)
@@ -27,14 +27,14 @@
<chapter id="entity">
<title>Entity Beans</title>
- <sect1 id="entity-overview" revision="2">
+ <section id="entity-overview" revision="2">
<title>Intro</title>
<para>This section covers EJB 3.0 (aka Java Persistence) entity
annotations and Hibernate-specific extensions.</para>
- </sect1>
+ </section>
- <sect1 id="entity-mapping" revision="2">
+ <section id="entity-mapping" revision="2">
<title>Mapping with EJB3/JPA Annotations</title>
<para>EJB3 entities are plain POJOs. Actually they represent the exact
@@ -58,7 +58,7 @@
tests have been designed to represent a concrete example and be a
inspiration source.</para>
- <sect2 id="entity-mapping-entity">
+ <section id="entity-mapping-entity">
<title>Declaring an entity bean</title>
<para>Every bound persistent POJO class is an entity bean and is
@@ -95,7 +95,7 @@
type from the position of <literal>@Id</literal> or
<literal>@EmbeddedId</literal>.</para>
- <sect3>
+ <section>
<title>Defining the table</title>
<para><literal>@Table</literal> is set at the class level; it allows
@@ -131,9 +131,9 @@
may be different than the property name (if the column name is
explicit). Unless you override the NamingStrategy, you shouldn't worry
about that.</remark>
- </sect3>
+ </section>
- <sect3 id="entity-mapping-entity-version" revision="1">
+ <section id="entity-mapping-entity-version" revision="1">
<title>Versioning for optimistic locking</title>
<para>You can add optimistic locking capability to an entity bean
@@ -162,13 +162,13 @@
Hibernate in any way. To artificially increase the version number,
check in Hibernate Entity Manager's reference documentation
<literal>LockMode.WRITE</literal></para>
- </sect3>
- </sect2>
+ </section>
+ </section>
- <sect2 id="entity-mapping-property" revision="1">
+ <section id="entity-mapping-property" revision="1">
<title>Mapping simple properties</title>
- <sect3>
+ <section>
<title>Declaring basic property mappings</title>
<para>Every non static non transient property (field or method) of an
@@ -263,9 +263,9 @@
and if the property is not annotated with <literal>@Lob</literal>,
then the Hibernate <literal>serializable</literal> type is
used.</para>
- </sect3>
+ </section>
- <sect3 id="entity-mapping-property-column" revision="1">
+ <section id="entity-mapping-property-column" revision="1">
<title>Declaring column attributes</title>
<para>The column(s) used for a property mapping can be defined using
@@ -321,25 +321,35 @@
<programlistingco>
<areaspec>
- <area coords="2 55" id="hm1" />
+ <area coords="2" id="hm1" />
- <area coords="3 55" id="hm2" />
+ <area coords="3" id="hm2" />
- <area coords="4 55" id="hm3" />
+ <area coords="4" id="hm3" />
- <area coords="5 55" id="hm4" />
+ <area coords="5" id="hm4" />
- <area coords="6 55" id="hm5" />
+ <area coords="6" id="hm5" />
- <area coords="7 55" id="hm6" />
+ <area coords="7" id="hm6" />
- <area coords="8 55" id="hm7" />
+ <area coords="8" id="hm7" />
- <area coords="9 55" id="hm8" />
+ <area coords="9" id="hm8" />
- <area coords="10 55" id="hm9" />
+ <area coords="10" id="hm9" />
- <area coords="11 55" id="hm10" />
+ <area coords="11" id="hm10" />
+ <!-- <area id="hm1" coords="2" />
+ <area id="hm2" coords="3" />
+ <area id="hm3" coords="4" />
+ <area id="hm4" coords="5" />
+ <area id="hm5" coords="6" />
+ <area id="hm6" coords="7" />
+ <area id="hm7" coords="8" />
+ <area id="hm8" coords="9" />
+ <area id="hm9" coords="10" />
+ <area id="hm10" coords="11" /> -->
</areaspec>
<programlisting>@Column(
@@ -409,9 +419,9 @@
</callout>
</calloutlist>
</programlistingco>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Embedded objects (aka components)</title>
<para>It is possible to declare an embedded component inside an entity
@@ -512,9 +522,9 @@
<classname>DefaultComponentSafeNamingStrategy</classname> is a small
improvement over the default EJB3NamingStrategy that allows embedded
objects to be defaulted even if used twice in the same entity.</para>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Non-annotated property defaults</title>
<para>If a property is not annotated, the following rules
@@ -545,10 +555,10 @@
</para>
</listitem>
</itemizedlist>
- </sect3>
- </sect2>
+ </section>
+ </section>
- <sect2 id="entity-mapping-identifier">
+ <section id="entity-mapping-identifier">
<title>Mapping identifier properties</title>
<para>The <literal>@Id</literal> annotation lets you define which
@@ -802,9 +812,9 @@
public Presenter presenter;
}
</programlisting>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Mapping inheritance</title>
<para>EJB3 supports the three types of inheritance:</para>
@@ -836,7 +846,7 @@
<para>Annotating interfaces is currently not supported.</para>
</note>
- <sect3>
+ <section>
<title>Table per class</title>
<para>This strategy has many drawbacks (esp. with polymorphic queries
@@ -858,9 +868,9 @@
shared across several tables. Consequently, when using this strategy,
you should not use <literal>AUTO </literal>nor
<literal>IDENTITY</literal>.</para>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Single table per class hierarchy</title>
<para>All properties of all super- and subclasses are mapped into the
@@ -900,9 +910,9 @@
<para><literal>@Inheritance</literal> and
<literal>@DiscriminatorColumn</literal> should only be defined at the
top of the entity hierarchy.</para>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Joined subclasses</title>
<para>The<literal> @PrimaryKeyJoinColumn</literal> and
@@ -928,9 +938,9 @@
<literal>AmericaCupClass</literal> table is joined with
<literal>Boat</literal> using the join condition <code>Boat.id =
AmericaCupClass.BOAT_ID</code>.</para>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Inherit properties from superclasses</title>
<para>This is sometimes useful to share common properties through a
@@ -1031,13 +1041,13 @@
<literal>@Entity</literal> classes,
<literal>@MappedSuperclass</literal> classes and properties pointing
to an <literal>@Embeddable</literal> object.</para>
- </sect3>
- </sect2>
+ </section>
+ </section>
- <sect2 id="entity-mapping-association">
+ <section id="entity-mapping-association">
<title>Mapping entity bean associations/relationships</title>
- <sect3>
+ <section>
<title>One-to-one</title>
<para>You can associate entity beans through a one-to-one relationship
@@ -1169,9 +1179,9 @@
<para>You must declare the join table name and the join columns
explicitly in such a mapping.</para>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Many-to-one</title>
<para>Many-to-one associations are declared at the property level with
@@ -1242,12 +1252,12 @@
...
}
</programlisting>
- </sect3>
+ </section>
- <sect3 id="entity-mapping-association-collections" revision="1">
+ <section id="entity-mapping-association-collections" revision="1">
<title>Collections</title>
- <sect4 id="entity-mapping-association-collections-overview"
+ <section id="entity-mapping-association-collections-overview"
revision="1">
<title>Overview</title>
@@ -1415,9 +1425,9 @@
<para>Unless the collection is a generic, you will have to define
<literal>targetEntity</literal>. This is a annotation attribute that
take the target entity class as a value.</para>
- </sect4>
+ </section>
- <sect4 id="entity-mapping-association-collection-onetomany"
+ <section id="entity-mapping-association-collection-onetomany"
revision="2">
<title>One-to-many</title>
@@ -1425,7 +1435,7 @@
with the annotation <literal>@OneToMany</literal>. One to many
associations may be bidirectional.</para>
- <sect5>
+ <section>
<title>Bidirectional</title>
<para>Since many to one are (almost) always the owner side of a
@@ -1476,9 +1486,9 @@
public Troop getTroop() {
...
}</programlisting>
- </sect5>
+ </section>
- <sect5>
+ <section>
<title>Unidirectional</title>
<para>A unidirectional one to many using a foreign key column in
@@ -1506,9 +1516,9 @@
<para><literal>Customer</literal> describes a unidirectional
relationship with <literal>Ticket</literal> using the join column
<literal>CUST_ID</literal>.</para>
- </sect5>
+ </section>
- <sect5>
+ <section>
<title>Unidirectional with join table</title>
<para>A unidirectional one to many with join table is much
@@ -1541,9 +1551,9 @@
(<literal>joinColumns</literal>) and a foreign key
<literal>monkey_id</literal> to <literal>Monkey</literal>
(<literal>inversejoinColumns</literal>).</para>
- </sect5>
+ </section>
- <sect5 id="entity-mapping-association-collection-manytomany-default"
+ <section id="entity-mapping-association-collection-manytomany-default"
revision="1">
<title>Defaults</title>
@@ -1580,14 +1590,14 @@
name, <keycap>_</keycap>, trainer id) and a foreign key
<literal>trainedTigers_id</literal> to <literal>Monkey</literal>
(property name, <keycap>_</keycap>, Tiger primary column).</para>
- </sect5>
- </sect4>
+ </section>
+ </section>
- <sect4 id="eentity-mapping-association-collection-manytomany"
+ <section id="eentity-mapping-association-collection-manytomany"
revision="">
<title>Many-to-many</title>
- <sect5>
+ <section>
<title>Definition</title>
<para>A many-to-many association is defined logically using the
@@ -1644,9 +1654,9 @@
describe the physical mapping: a simple
<literal>mappedBy</literal> argument containing the owner side
property name bind the two.</para>
- </sect5>
+ </section>
- <sect5>
+ <section>
<title>Default values</title>
<para>As any other annotations, most values are guessed in a many
@@ -1716,11 +1726,11 @@
the <literal>Store</literal> table. The
<literal>customers_id</literal> column is a foreign key to the
<literal>Customer</literal> table.</para>
- </sect5>
- </sect4>
- </sect3>
+ </section>
+ </section>
+ </section>
- <sect3 id="entity-mapping-association-cascade">
+ <section id="entity-mapping-association-cascade">
<title>Transitive persistence with cascading</title>
<para>You probably have noticed the <literal>cascade</literal>
@@ -1764,9 +1774,9 @@
<para>Please refer to the chapter 6.3 of the EJB3 specification for
more information on cascading and create/merge semantics.</para>
- </sect3>
+ </section>
- <sect3 id="entity-mapping-association-fetching" revision="1">
+ <section id="entity-mapping-association-fetching" revision="1">
<title>Association fetching</title>
<para>You have the ability to either eagerly or lazily fetch
@@ -1788,10 +1798,10 @@
allows you to override laziness when doing a particular query. This is
very useful to improve performance and is decided on a use case to use
case basis.</para>
- </sect3>
- </sect2>
+ </section>
+ </section>
- <sect2>
+ <section>
<title>Mapping composite primary and foreign keys</title>
<para>Composite primary keys use a embedded class as the primary key
@@ -1883,9 +1893,9 @@
<para>Note the explicit usage of the
<literal>referencedColumnName</literal>.</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Mapping secondary tables</title>
<para>You can map a single entity bean to several tables using the
@@ -1943,13 +1953,13 @@
<para>Check out the JBoss EJB 3 tutorial or the Hibernate Annotations
unit test suite for more examples.</para>
- </sect2>
- </sect1>
+ </section>
+ </section>
- <sect1 id="entity-mapping-query">
+ <section id="entity-mapping-query">
<title>Mapping Queries</title>
- <sect2 id="entity-mapping-query-hql" label="Mapping JPAQL/HQL queries"
+ <section id="entity-mapping-query-hql" label="Mapping JPAQL/HQL queries"
revision="1">
<title>Mapping JPAQL/HQL queries</title>
@@ -2062,9 +2072,9 @@
</tbody>
</tgroup>
</table>
- </sect2>
+ </section>
- <sect2 id="entity-mapping-query-native" revision="2">
+ <section id="entity-mapping-query-native" revision="2">
<title>Mapping native queries</title>
<para>You can also map a native query (ie a plain SQL query). To achieve
@@ -2285,10 +2295,10 @@
introduced: <literal>org.hibernate.callable</literal> which can be true
or false depending on whether the query is a stored procedure or
not.</para>
- </sect2>
- </sect1>
+ </section>
+ </section>
- <sect1 id="entity-hibspec">
+ <section id="entity-hibspec">
<title>Hibernate Annotation Extensions</title>
<para>Hibernate 3.1 offers a variety of additional annotations that you
@@ -2300,7 +2310,7 @@
<classname>org.hibernate.annotations</classname> package contains all
these annotations extensions.</para>
- <sect2 id="entity-hibspec-entity" revision="4">
+ <section id="entity-hibspec-entity" revision="4">
<title>Entity</title>
<para>You can fine tune some of the actions done by Hibernate on
@@ -2459,15 +2469,15 @@
@Entity
@OnDelete(action=OnDeleteAction.CASCADE)
public class Carrot extends Vegetable { ... }</programlisting></para>
- </sect2>
+ </section>
- <sect2 id="entity-hibspec-identifier" label="Identifier" revision="2">
+ <section id="entity-hibspec-identifier" label="Identifier" revision="2">
<title>Identifier</title>
<para>Hibernate Annotations goes beyond the Java Persistence
specification when defining identifiers.</para>
- <sect3>
+ <section>
<title>Generators</title>
<para><literal><literal>@org.hibernate.annotations.GenericGenerator</literal>
@@ -2514,9 +2524,9 @@
}
)
package org.hibernate.test.model</programlisting>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>@NaturalId</title>
<para>While not used as identifier property, some (group of)
@@ -2555,13 +2565,13 @@
<para>Note that the group of properties representing the natural
identifier have to be unique (Hibernate will generate a unique
constraint if the database schema is generated).</para>
- </sect3>
- </sect2>
+ </section>
+ </section>
- <sect2 id="entity-hibspec-property" revision="2">
+ <section id="entity-hibspec-property" revision="2">
<title>Property</title>
- <sect3>
+ <section>
<title>Access type</title>
<para>The access type is guessed from the position of
@@ -2663,9 +2673,9 @@
}
}
</programlisting>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Formula</title>
<para>Sometimes, you want the Database to do some computation for you
@@ -2679,9 +2689,9 @@
<para>The SQL fragment can be as complex as you want and even include
subselects.</para>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Type</title>
<para><literal>@org.hibernate.annotations.Type</literal> overrides the
@@ -2742,9 +2752,9 @@
private Currency currency;
...
}</programlisting>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Index</title>
<para>You can define an index on a particular column using the
@@ -2756,9 +2766,9 @@
public String getStoryPart1() {
return storyPart1;
}</programlisting>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>@Parent</title>
<para>When inside an embeddable object, you can define one of the
@@ -2778,9 +2788,9 @@
person == person.address.owner</programlisting>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Generated properties</title>
<para>Some properties are generated at insert or update time by your
@@ -2807,9 +2817,9 @@
<para><literal>@Version</literal> properties cannot be
<literal>@Generated(INSERT)</literal> by design, it has to be either
<literal>NEVER</literal> or <literal>ALWAYS</literal>.</para>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>@Target</title>
<para>Sometimes, the type guessed by reflection is not the one you
@@ -2826,9 +2836,9 @@
}</programlisting>
<para></para>
- </sect3>
+ </section>
- <sect3>
+ <section>
<title>Optimistic lock</title>
<para>It is sometimes useful to avoid increasing the version number
@@ -2838,10 +2848,10 @@
<para>More formally, specifies that updates to this property do not
require acquisition of the optimistic lock.</para>
- </sect3>
- </sect2>
+ </section>
+ </section>
- <sect2 id="entity-hibspec-inheritance" revision="3">
+ <section id="entity-hibspec-inheritance" revision="3">
<title>Inheritance</title>
<para>SINGLE_TABLE is a very powerful strategy but sometimes, and
@@ -2879,9 +2889,9 @@
<para>The foreign key from the <literal>Document</literal> table to the
<literal>File</literal> table will be named
<literal>FK_DOCU_FILE</literal>.</para>
- </sect2>
+ </section>
- <sect2 id="entity-hibspec-singleassoc">
+ <section id="entity-hibspec-singleassoc">
<title>Single Association related annotations</title>
<para>By default, when Hibernate cannot resolve the association because
@@ -2933,7 +2943,7 @@
alter table Child add constraint FK_PARENT foreign key (parent_id) references Parent</programlisting>
- <sect3 id="entity-hibspec-singleassoc-fetching">
+ <section id="entity-hibspec-singleassoc-fetching">
<title>Lazy options and fetching modes</title>
<para>EJB3 comes with the <literal>fetch</literal> option to define
@@ -3031,9 +3041,9 @@
</tbody>
</tgroup>
</table>
- </sect3>
+ </section>
- <sect3 id="entity-hibspec-singleassoc-any">
+ <section id="entity-hibspec-singleassoc-any">
<title>@Any</title>
<para>The <classname>@Any</classname> annotation defines a polymorphic
@@ -3088,13 +3098,13 @@
public Property getMainProperty() {
return mainProperty;
}</programlisting>
- </sect3>
- </sect2>
+ </section>
+ </section>
- <sect2 id="entity-hibspec-collection" revision="2">
+ <section id="entity-hibspec-collection" revision="2">
<title>Collection related annotations</title>
- <sect3 id="entity-hibspec-collection-enhance" revision="3">
+ <section id="entity-hibspec-collection-enhance" revision="3">
<title>Enhance collection settings</title>
<para>It is possible to set <itemizedlist>
@@ -3176,12 +3186,12 @@
alter table Man_Woman add constraint TO_WOMAN_FK foreign key (woman_id) references Woman
alter table Man_Woman add constraint TO_MAN_FK foreign key (man_id) references Man</programlisting>
- </sect3>
+ </section>
- <sect3 id="entity-hibspec-collection-extratype" revision="1">
+ <section id="entity-hibspec-collection-extratype" revision="1">
<title>Extra collection types</title>
- <sect4>
+ <section>
<title>List</title>
<para>Beyond EJB3, Hibernate Annotations supports true
@@ -3205,9 +3215,9 @@
limitations of it, consider using
<literal>@CollectionId</literal>.</para>
</note>
- </sect4>
+ </section>
- <sect4 id="entity-hibspec-collection-extratype-map" revision="1">
+ <section id="entity-hibspec-collection-extratype-map" revision="1">
<title>Map</title>
<para>Hibernate Annotations also supports true Map mappings, if
@@ -3231,9 +3241,9 @@
private Map<Luggage, Size> sizePerLuggage = new HashMap<Luggage, Size>();</programlisting>
<para></para>
- </sect4>
+ </section>
- <sect4 id="entity-hibspec-collection-extratype-indexbidir"
+ <section id="entity-hibspec-collection-extratype-indexbidir"
revision="2">
<title>Bidirectional association with indexed collections</title>
@@ -3293,9 +3303,9 @@
<para>Note that in this mapping, the collection-valued end of the
association is responsible for updating the foreign key.</para>
- </sect4>
+ </section>
- <sect4>
+ <section>
<title>Bag with primary key</title>
<para>Another interesting feature is the ability to define a
@@ -3324,9 +3334,9 @@
private Collection<Stamp> visaStamp = new ArrayList();
...
}</programlisting>
- </sect4>
+ </section>
- <sect4>
+ <section>
<title>Collection of element or composite elements</title>
<para>Hibernate Annotations also supports collections of core types
@@ -3465,9 +3475,9 @@
elements the old way still work but is considered deprecated and
is going to be unsupported in future releases</para>
</note>
- </sect4>
+ </section>
- <sect4>
+ <section>
<title>@ManyToAny</title>
<para><classname>@ManyToAny</classname> allows polymorphic
@@ -3497,11 +3507,11 @@
<classname>@ManyToAny</classname> can use named
<classname>@AnyDef</classname>s, see <xref
linkend="entity-hibspec-singleassoc-any" /> for more info.</para>
- </sect4>
- </sect3>
- </sect2>
+ </section>
+ </section>
+ </section>
- <sect2 id="entity-hibspec-cascade">
+ <section id="entity-hibspec-cascade">
<title>Cascade</title>
<para>Hibernate offers more operations than the Java Persistence
@@ -3570,9 +3580,9 @@
<para>It is recommended to use @Cascade to compliment @*To*(cascade=...)
as shown in the previous example.</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Cache</title>
<para>In order to optimize your database accesses, you can activate the
@@ -3599,11 +3609,11 @@
<programlistingco>
<areaspec>
- <area coords="2 55" id="hm11" />
+ <area coords="2" id="hm11" />
- <area coords="3 55" id="hm12" />
+ <area coords="3" id="hm12" />
- <area coords="4 55" id="hm13" />
+ <area coords="4" id="hm13" />
</areaspec>
<programlisting>@Cache(
@@ -3630,9 +3640,9 @@
</callout>
</calloutlist>
</programlistingco>
- </sect2>
+ </section>
- <sect2 id="entity-hibspec-filters">
+ <section id="entity-hibspec-filters">
<title>Filters</title>
<para>Hibernate has the ability to apply arbitrary filters on top of
@@ -3678,9 +3688,9 @@
//filter on the association table
@FilterJoinTable(name="security", condition=":userlevel >= requiredLevel")
public Set<Forest> getForests() { ... }</programlisting>
- </sect2>
+ </section>
- <sect2 id="entity-hibspec-query">
+ <section id="entity-hibspec-query">
<title>Queries</title>
<para>Since Hibernate has more features on named queries than the one
@@ -3739,9 +3749,9 @@
<literal>@javax.persistence.NamedQuery</literal> annotations through the
detyped <literal>@QueryHint</literal>. Another key advantage is the
ability to set those annotations at a package level.</para>
- </sect2>
+ </section>
- <sect2 id="entity-hibspec-customsql" revision="1">
+ <section id="entity-hibspec-customsql" revision="1">
<title>Custom SQL for CRUD operations</title>
<para>Hibernate gives you the ability to override every single SQL
@@ -3838,9 +3848,9 @@
<para>The previous example also show that you can give a comment to a
given table (promary or secondary): This comment will be used for DDL
generation.</para>
- </sect2>
+ </section>
- <sect2>
+ <section>
<title>Tuplizer</title>
<para><classname>org.hibernate.tuple.Tuplizer</classname>, and its
@@ -3881,6 +3891,6 @@
}</programlisting>
- </sect2>
- </sect1>
-</chapter>
\ No newline at end of file
+ </section>
+ </section>
+</chapter>
Modified: projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/en-US/xml-overriding.xml
===================================================================
--- projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/en-US/xml-overriding.xml 2009-12-11 02:14:36 UTC (rev 97713)
+++ projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/en-US/xml-overriding.xml 2009-12-11 03:13:08 UTC (rev 97714)
@@ -24,7 +24,7 @@
-->
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<chapter id="xml-overriding" label="Overriding metadata through XML">
+<chapter id="xml-overriding">
<title>Overriding metadata through XML</title>
<para>The primary target for metadata in EJB3 is annotations, but the EJB3
@@ -91,25 +91,25 @@
<programlistingco>
<areaspec>
- <area coords="3 85" id="aa1" />
+ <area coords="3" id="aa1" />
- <area coords="9 85" id="aa2" />
+ <area coords="9" id="aa2" />
- <area coords="10 85" id="aa3" />
+ <area coords="10" id="aa3" />
- <area coords="11 85" id="aa4" />
+ <area coords="11" id="aa4" />
- <area coords="17 85" id="aa5" />
+ <area coords="17" id="aa5" />
- <area coords="23 85" id="aa6" />
+ <area coords="23" id="aa6" />
- <area coords="24 85" id="aa7" />
+ <area coords="24" id="aa7" />
- <area coords="25 85" id="aa8" />
+ <area coords="25" id="aa8" />
- <area coords="26 85" id="aa9" />
+ <area coords="26" id="aa9" />
- <area coords="31 85" id="aa10" />
+ <area coords="31" id="aa10" />
</areaspec>
<programlisting><?xml version="1.0" encoding="UTF-8"?>
@@ -424,4 +424,4 @@
informations in the chapter describing annotations.</para>
</section>
</section>
-</chapter>
\ No newline at end of file
+</chapter>
Modified: projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/publican.cfg
===================================================================
--- projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/publican.cfg 2009-12-11 02:14:36 UTC (rev 97713)
+++ projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/publican.cfg 2009-12-11 03:13:08 UTC (rev 97714)
@@ -1,5 +1,5 @@
# Config::Simple 4.59
-# Wed Nov 25 14:58:40 2009
+# Wed Dec 9 17:29:44 2009
debug: 1
xml_lang: en-US
More information about the jboss-cvs-commits
mailing list