Hibernate
/
hibernate-orm
mirror of https://github.com/hibernate/hibernate-orm
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

some minor changes 

git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@7024 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
Gavin King 2005-06-05 07:28:53 +00:00
parent 6d7fef311b
commit 5ae9192e1c
2 changed files with 29 additions and 31 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
reference/en/modules/collection_mapping.xml
View File

@ -347,8 +347,7 @@ kittens = cat.getKittens(); // Okay, kittens collection is a Set
</callout> </callout>
<callout arearefs="mapkey3"> <callout arearefs="mapkey3">
<para> <para>
<literal>type</literal> (optional, defaults to <literal>integer</literal>): <literal>type</literal> (reguired): The type of the map keys.
The type of the collection index.
</para> </para>
</callout> </callout>
</calloutlist> </calloutlist>
@ -380,8 +379,7 @@ kittens = cat.getKittens(); // Okay, kittens collection is a Set
</callout> </callout>
<callout arearefs="indexmanytomany3"> <callout arearefs="indexmanytomany3">
<para> <para>
<literal>class</literal> (required): The entity class used as the <literal>class</literal> (required): The entity class used as the map key.
collection index.
</para> </para>
</callout> </callout>
</calloutlist> </calloutlist>

54
reference/en/modules/persistent_classes.xml
View File

@ -10,7 +10,7 @@
<para> <para>
Hibernate works best if these classes follow some simple rules, also known Hibernate works best if these classes follow some simple rules, also known
as the Plain Old Java Object (POJO) programming model. However none of these as the Plain Old Java Object (POJO) programming model. However, none of these
rules are hard requirements. Indeed, Hibernate3 assumes very little about rules are hard requirements. Indeed, Hibernate3 assumes very little about
the nature of your persistent objects. You may express a domain model in other the nature of your persistent objects. You may express a domain model in other
ways: using trees of <literal>Map</literal> instances, for example. ways: using trees of <literal>Map</literal> instances, for example.
@ -107,36 +107,15 @@ public class Cat {
</para> </para>
<sect2 id="persistent-classes-pojo-accessors" revision="1">
<title>Declare accessors and mutators for persistent fields</title>
<para>
<literal>Cat</literal> declares accessor methods for all its persistent fields.
Many other ORM tools directly persist instance variables. We believe
it is far better to decouple this implementation detail from the persistence
mechanism. Hibernate persists JavaBeans style properties, and recognizes method
names of the form <literal>getFoo</literal>, <literal>isFoo</literal> and
<literal>setFoo</literal>. You may however switch to direct field access for
particular properties, if needed.
</para>
<para>
Properties need <emphasis>not</emphasis> be declared public - Hibernate can
persist a property with a default, <literal>protected</literal> or <literal>
private</literal> get / set pair.
</para>
</sect2>
<sect2 id="persistent-classes-pojo-constructor" revision="1"> <sect2 id="persistent-classes-pojo-constructor" revision="1">
<title>Implement a no-argument constructor</title> <title>Implement a no-argument constructor</title>
<para> <para>
<literal>Cat</literal> has a no-argument constructor. All <literal>Cat</literal> has a no-argument constructor. All persistent classes must
persistent classes must have a default constructor (which may be non-public) so have a default constructor (which may be non-public) so that Hibernate can instantiate
Hibernate can instantiate them using <literal>Constructor.newInstance()</literal>. them using <literal>Constructor.newInstance()</literal>. We strongly recommend having a
We recommend having a constructor with at least <emphasis>package</emphasis> default constructor with at least <emphasis>package</emphasis> visibility for runtime proxy
visibility for runtime proxy generation in Hibernate. generation in Hibernate.
</para> </para>
</sect2> </sect2>
@ -206,6 +185,27 @@ public class Cat {
</para> </para>
</sect2> </sect2>
<sect2 id="persistent-classes-pojo-accessors" revision="2">
<title>Declare accessors and mutators for persistent fields (optional)</title>
<para>
<literal>Cat</literal> declares accessor methods for all its persistent fields.
Many other ORM tools directly persist instance variables. We believe it is
better to provide an indirection between the relational schema and internal
data structures of the class. By default, Hibernate persists JavaBeans style
properties, and recognizes method names of the form <literal>getFoo</literal>,
<literal>isFoo</literal> and <literal>setFoo</literal>. You may switch to direct
field access for particular properties, if needed.
</para>
<para>
Properties need <emphasis>not</emphasis> be declared public - Hibernate can
persist a property with a default, <literal>protected</literal> or
<literal>private</literal> get / set pair.
</para>
</sect2>
</sect1> </sect1>
<sect1 id="persistent-classes-inheritance"> <sect1 id="persistent-classes-inheritance">