mirror of
https://github.com/hibernate/hibernate-orm
synced 2025-02-21 18:45:09 +00:00
corrected DTD incongruities
git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@14177 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
parent
ae75ae8abf
commit
9900a73769
@ -1821,13 +1821,13 @@
|
||||
<literal>entity-name</literal> (optional): The entity name of the associated class.
|
||||
</para>
|
||||
</callout>
|
||||
</calloutlist>
|
||||
<callout arearefs="manytoone16">
|
||||
<para>
|
||||
<literal>formula</literal> (optional): an SQL expression that defines the value for a
|
||||
<emphasis>computed</emphasis> foreign key.
|
||||
</para>
|
||||
</callout>
|
||||
</calloutlist>
|
||||
</programlistingco>
|
||||
|
||||
<para>
|
||||
|
@ -80,6 +80,14 @@ kittens = cat.getKittens(); // Okay, kittens collection is a Set
|
||||
<sect1 id="collections-mapping" revision="4">
|
||||
<title>Collection mappings</title>
|
||||
|
||||
<tip>
|
||||
<para>
|
||||
There are quite a range of mappings that can be generated for collections, covering
|
||||
many common relational models. We suggest you experiment with the schema generation tool
|
||||
to get a feeling for how various mapping declarations translate to database tables.
|
||||
</para>
|
||||
</tip>
|
||||
|
||||
<para>
|
||||
The Hibernate mapping element used for mapping a collection depends upon
|
||||
the type of the interface. For example, a <literal><set></literal>
|
||||
@ -409,12 +417,6 @@ kittens = cat.getKittens(); // Okay, kittens collection is a Set
|
||||
|
||||
</sect2>
|
||||
|
||||
<para>
|
||||
There are quite a range of mappings that can be generated for collections, covering
|
||||
many common relational models. We suggest you experiment with the schema generation tool
|
||||
to get a feeling for how various mapping declarations translate to database tables.
|
||||
</para>
|
||||
|
||||
<sect2 id="collections-ofvalues" revision="2">
|
||||
<title>Collections of values and many-to-many associations</title>
|
||||
|
||||
|
@ -829,68 +829,78 @@ Cat fritz = (Cat) iter.next();]]></programlisting>
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<para>
|
||||
None of the cache providers support all of the cache concurrency strategies. The following table shows
|
||||
which providers are compatible with which concurrency strategies.
|
||||
</para>
|
||||
|
||||
<table frame="topbot">
|
||||
<title>Cache Concurrency Strategy Support</title>
|
||||
<tgroup cols='5' align='left' colsep='1' rowsep='1'>
|
||||
<colspec colname='c1' colwidth="1*"/>
|
||||
<colspec colname='c2' colwidth="1*"/>
|
||||
<colspec colname='c3' colwidth="1*"/>
|
||||
<colspec colname='c4' colwidth="1*"/>
|
||||
<colspec colname='c5' colwidth="1*"/>
|
||||
<thead>
|
||||
<row>
|
||||
<entry>Cache</entry>
|
||||
<entry>read-only</entry>
|
||||
<entry>nonstrict-read-write</entry>
|
||||
<entry>read-write</entry>
|
||||
<entry>transactional</entry>
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>Hashtable (not intended for production use)</entry>
|
||||
<entry>yes</entry>
|
||||
<entry>yes</entry>
|
||||
<entry>yes</entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>EHCache</entry>
|
||||
<entry>yes</entry>
|
||||
<entry>yes</entry>
|
||||
<entry>yes</entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>OSCache</entry>
|
||||
<entry>yes</entry>
|
||||
<entry>yes</entry>
|
||||
<entry>yes</entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>SwarmCache</entry>
|
||||
<entry>yes</entry>
|
||||
<entry>yes</entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>JBoss TreeCache</entry>
|
||||
<entry>yes</entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry>yes</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
<sect2 id="performance-cache-compat-matrix">
|
||||
<title>Cache-provider/concurrency-strategy compatibility</title>
|
||||
|
||||
<important>
|
||||
<para>
|
||||
None of the cache providers support all of the cache concurrency strategies.
|
||||
</para>
|
||||
</important>
|
||||
|
||||
<para>
|
||||
The following table shows which providers are compatible with which concurrency strategies.
|
||||
</para>
|
||||
|
||||
<table frame="topbot">
|
||||
<title>Cache Concurrency Strategy Support</title>
|
||||
<tgroup cols='5' align='left' colsep='1' rowsep='1'>
|
||||
<colspec colname='c1' colwidth="1*"/>
|
||||
<colspec colname='c2' colwidth="1*"/>
|
||||
<colspec colname='c3' colwidth="1*"/>
|
||||
<colspec colname='c4' colwidth="1*"/>
|
||||
<colspec colname='c5' colwidth="1*"/>
|
||||
<thead>
|
||||
<row>
|
||||
<entry>Cache</entry>
|
||||
<entry>read-only</entry>
|
||||
<entry>nonstrict-read-write</entry>
|
||||
<entry>read-write</entry>
|
||||
<entry>transactional</entry>
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>Hashtable (not intended for production use)</entry>
|
||||
<entry>yes</entry>
|
||||
<entry>yes</entry>
|
||||
<entry>yes</entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>EHCache</entry>
|
||||
<entry>yes</entry>
|
||||
<entry>yes</entry>
|
||||
<entry>yes</entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>OSCache</entry>
|
||||
<entry>yes</entry>
|
||||
<entry>yes</entry>
|
||||
<entry>yes</entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>SwarmCache</entry>
|
||||
<entry>yes</entry>
|
||||
<entry>yes</entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>JBoss TreeCache</entry>
|
||||
<entry>yes</entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry>yes</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
|
@ -526,9 +526,12 @@ public class CustomMapTuplizerImpl
|
||||
|
||||
</sect1>
|
||||
|
||||
<para>
|
||||
TODO: Document user-extension framework in the property and proxy packages
|
||||
</para>
|
||||
<sect1 id="persistent-classes-extensions">
|
||||
<title>Extentsions</title>
|
||||
<para>
|
||||
TODO: Document user-extension framework in the property and proxy packages
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
||||
|
@ -1260,15 +1260,15 @@ public void removeFromEvent(Event event) {
|
||||
|
||||
</sect2>
|
||||
|
||||
<para>
|
||||
Let's turn this into a small web application.
|
||||
</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="tutorial-webapp">
|
||||
<title>Part 3 - The EventManager web application</title>
|
||||
|
||||
<para>
|
||||
Let's turn the following discussion into a small web application...
|
||||
</para>
|
||||
|
||||
<para>
|
||||
A Hibernate web application uses <literal>Session</literal> and <literal>Transaction</literal>
|
||||
almost like a standalone application. However, some common patterns are useful. We now write
|
||||
|
Loading…
x
Reference in New Issue
Block a user