|
|
Hibernate example source code file (persistent_classes.po)
This example Hibernate source code file (persistent_classes.po) is included in the DevDaily.com
"Java Source Code
Warehouse" project. The intent of this project is to help you "Learn Java by Example" TM.
The Hibernate persistent_classes.po source code
# translation of Collection_Mapping.po to
# Xi HUANG <xhuang@redhat.com>, 2007, 2010.
msgid ""
msgstr ""
"Project-Id-Version: Collection_Mapping\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2010-07-20 21:02+0000\n"
"PO-Revision-Date: 2010-01-04 13:58+1000\n"
"Last-Translator: Xi HUANG <xhuang@redhat.com>\n"
"Language-Team: <en@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
#. Tag: title
#: persistent_classes.xml:32
#, no-c-format
msgid "Persistent Classes"
msgstr "永続クラス"
#. Tag: para
#: persistent_classes.xml:34
#, fuzzy, no-c-format
msgid ""
"Persistent classes are classes in an application that implement the entities "
"of the business problem (e.g. Customer and Order in an E-commerce "
"application). The term \"persistent\" here means that the classes are able "
"to be persisted, not that they are in the persistent state (see <xref "
"linkend=\"objectstate-overview\"/> for discussion)."
msgstr ""
"永続クラスはビジネス上の問題のエンティティ（例えば、 E コマースアプリケーショ"
"ンの顧客や注文） を実装するアプリケーションのクラスです。永続クラスのすべての"
"インスタンスが永続状態であると見なされるわけではありません。インスタンスは逆"
"に一時的（transient）であったり、分離状態（detached）であったりするかもしれま"
"せん。"
#. Tag: para
#: persistent_classes.xml:41
#, fuzzy, no-c-format
msgid ""
"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 rules are hard requirements. Indeed, Hibernate assumes very little "
"about the nature of your persistent objects. You can express a domain model "
"in other ways (using trees of <interfacename>java.util.Map "
"instances, for example)."
msgstr ""
"Plain Old Java Object (POJO)プログラミングモデルとしても知られるいくつかの単"
"純なルールに従うなら、 Hibernate は最もよく働きます。しかしこれらのルールは難"
"しいものではありません。実際 Hibernate3 は永続オブジェクトの性質にほとんど何"
"の前提も置いていません。ドメインモデルは他の方法で表現することもできます。例"
"えば <literal>Map インスタンスのツリーを使う方法があります。"
#. Tag: title
#: persistent_classes.xml:49
#, no-c-format
msgid "A simple POJO example"
msgstr "単純な POJO の例"
#. Tag: title
#: persistent_classes.xml:52
#, no-c-format
msgid "Simple POJO representing a cat"
msgstr ""
#. Tag: programlisting
#: persistent_classes.xml:53
#, fuzzy, no-c-format
msgid ""
"package eg;\n"
"import java.util.Set;\n"
"import java.util.Date;\n"
"\n"
"public class Cat {\n"
"private Long id; // identifier\n"
"\n"
"private Date birthdate;\n"
"private Color color;\n"
"private char sex;\n"
"private float weight;\n"
" private int litterId;\n"
"\n"
" private Cat mother;\n"
" private Set kittens = new HashSet();\n"
"\n"
" private void setId(Long id) {\n"
" this.id=id;\n"
" }\n"
" public Long getId() {\n"
" return id;\n"
" }\n"
"\n"
" void setBirthdate(Date date) {\n"
" birthdate = date;\n"
" }\n"
" public Date getBirthdate() {\n"
" return birthdate;\n"
" }\n"
"\n"
" void setWeight(float weight) {\n"
" this.weight = weight;\n"
" }\n"
" public float getWeight() {\n"
" return weight;\n"
" }\n"
"\n"
" public Color getColor() {\n"
" return color;\n"
" }\n"
" void setColor(Color color) {\n"
" this.color = color;\n"
" }\n"
"\n"
" void setSex(char sex) {\n"
" this.sex=sex;\n"
" }\n"
" public char getSex() {\n"
" return sex;\n"
" }\n"
"\n"
" void setLitterId(int id) {\n"
" this.litterId = id;\n"
" }\n"
" public int getLitterId() {\n"
" return litterId;\n"
" }\n"
"\n"
" void setMother(Cat mother) {\n"
" this.mother = mother;\n"
" }\n"
" public Cat getMother() {\n"
" return mother;\n"
" }\n"
" void setKittens(Set kittens) {\n"
" this.kittens = kittens;\n"
" }\n"
" public Set getKittens() {\n"
" return kittens;\n"
" }\n"
"\n"
" // addKitten not needed by Hibernate\n"
" public void addKitten(Cat kitten) {\n"
" kitten.setMother(this);\n"
" kitten.setLitterId( kittens.size() );\n"
" kittens.add(kitten);\n"
" }\n"
"}"
msgstr ""
"package eg;\n"
"import java.util.Set;\n"
"import java.util.Date;\n"
"\n"
"public class Cat {\n"
" private Long id; // identifier\n"
"\n"
" private Date birthdate;\n"
" private Color color;\n"
" private char sex;\n"
" private float weight;\n"
" private int litterId;\n"
"\n"
" private Cat mother;\n"
" private Set kittens = new HashSet();\n"
"\n"
" private void setId(Long id) {\n"
" this.id=id;\n"
" }\n"
" public Long getId() {\n"
" return id;\n"
" }\n"
"\n"
" void setBirthdate(Date date) {\n"
" birthdate = date;\n"
" }\n"
" public Date getBirthdate() {\n"
" return birthdate;\n"
" }\n"
"\n"
" void setWeight(float weight) {\n"
" this.weight = weight;\n"
" }\n"
" public float getWeight() {\n"
" return weight;\n"
" }\n"
"\n"
" public Color getColor() {\n"
" return color;\n"
" }\n"
" void setColor(Color color) {\n"
" this.color = color;\n"
" }\n"
"\n"
" void setSex(char sex) {\n"
" this.sex=sex;\n"
" }\n"
" public char getSex() {\n"
" return sex;\n"
" }\n"
"\n"
" void setLitterId(int id) {\n"
" this.litterId = id;\n"
" }\n"
" public int getLitterId() {\n"
" return litterId;\n"
" }\n"
"\n"
" void setMother(Cat mother) {\n"
" this.mother = mother;\n"
" }\n"
" public Cat getMother() {\n"
" return mother;\n"
" }\n"
" void setKittens(Set kittens) {\n"
" this.kittens = kittens;\n"
" }\n"
" public Set getKittens() {\n"
" return kittens;\n"
" }\n"
" \n"
" // addKitten not needed by Hibernate\n"
" public void addKitten(Cat kitten) {\n"
" kitten.setMother(this);\n"
"kitten.setLitterId( kittens.size() ); \n"
" kittens.add(kitten);\n"
" }\n"
"}"
#. Tag: para
#: persistent_classes.xml:57
#, no-c-format
msgid ""
"The four main rules of persistent classes are explored in more detail in the "
"following sections."
msgstr ""
#. Tag: title
#: persistent_classes.xml:62
#, no-c-format
msgid "Implement a no-argument constructor"
msgstr "引数のないコンストラクタを実装する"
#. Tag: para
#: persistent_classes.xml:64
#, fuzzy, no-c-format
msgid ""
"<classname>Cat has a no-argument constructor. All persistent "
"classes must have a default constructor (which can be non-public) so that "
"Hibernate can instantiate them using <literal>java.lang.reflect."
"Constructor</classname>.newInstance(). It is recommended that this "
"constructor be defined with at least <emphasis>package visibility "
"in order for runtime proxy generation to work properly."
msgstr ""
"<literal>Cat には引数のないコンストラクタがあります。 Hibernate が "
"<literal>Constructor.newInstance() を使って永続クラスのインスタンス"
"化を行えるように、すべての永続クラスにはデフォルトコンストラクタ （public で"
"なくても構いません） がなければなりません。 Hibernate の実行時プロキシ生成の"
"ために、少なくとも <emphasis>package の可視性を持つデフォルトコン"
"ストラクタを強くお勧めします。"
#. Tag: title
#: persistent_classes.xml:74
#, fuzzy, no-c-format
msgid "Provide an identifier property"
msgstr "識別子プロパティを用意する（オプション）"
#. Tag: para
#: persistent_classes.xml:77
#, no-c-format
msgid ""
"Historically this was considered option. While still not (yet) enforced, "
"this should be considered a deprecated feature as it will be completely "
"required to provide a identifier property in an upcoming release."
msgstr ""
#. Tag: para
#: persistent_classes.xml:84
#, no-c-format
msgid ""
"<classname>Cat has a property named id. This "
"property maps to the primary key column(s) of the underlying database table. "
"The type of the identifier property can be any \"basic\" type (see <xref "
"linkend=\"types.value.basic\"/>). See <xref linkend=\"components-compositeid"
"\"/> for information on mapping composite (multi-column) identifiers."
msgstr ""
#. Tag: para
#: persistent_classes.xml:92
#, no-c-format
msgid ""
"Identifiers do not necessarily need to identify column(s) in the database "
"physically defined as a primary key. They should just identify columns that "
"can be used to uniquely identify rows in the underlying table."
msgstr ""
#. Tag: para
#: persistent_classes.xml:99
#, no-c-format
msgid ""
"We recommend that you declare consistently-named identifier properties on "
"persistent classes and that you use a nullable (i.e., non-primitive) type."
msgstr ""
"永続クラスには、一貫した名前の識別子プロパティを定義することをお勧めします。"
"さらに null 値を取れる(つまりプリミティブではない)型を使った方がよいでしょ"
"う。"
#. Tag: title
#: persistent_classes.xml:107
#, fuzzy, no-c-format
msgid "Prefer non-final classes (semi-optional)"
msgstr "final クラスにしない（オプション）"
#. Tag: para
#: persistent_classes.xml:109
#, no-c-format
msgid ""
"A central feature of Hibernate, <emphasis>proxies (lazy loading), "
"depends upon the persistent class being either non-final, or the "
"implementation of an interface that declares all public methods. You can "
"persist <literal>final classes that do not implement an interface "
"with Hibernate; you will not, however, be able to use proxies for lazy "
"association fetching which will ultimately limit your options for "
"performance tuning. To persist a <literal>final class which does "
"not implement a \"full\" interface you must disable proxy generation. See "
"<xref linkend=\"persistent-classes-pojo-final-example-disable-proxies-xml\"/"
"> and <xref linkend=\"persistent-classes-pojo-final-example-disable-proxies-"
"ann\"/>."
msgstr ""
#. Tag: title
#: persistent_classes.xml:121
#, no-c-format
msgid "Disabling proxies in <literal>hbm.xml"
msgstr ""
#. Tag: programlisting
#: persistent_classes.xml:122
#, no-c-format
msgid "<![CDATA[]]>"
msgstr ""
#. Tag: title
#: persistent_classes.xml:126
#, no-c-format
msgid "Disabling proxies in annotations"
msgstr ""
#. Tag: programlisting
#: persistent_classes.xml:127
#, no-c-format
msgid "<![CDATA[@Entity @Proxy(lazy=false) public class Cat { ... }]]>"
msgstr ""
#. Tag: para
#: persistent_classes.xml:130
#, no-c-format
msgid ""
"If the <literal>final class does implement a proper interface, you "
"could alternatively tell Hibernate to use the interface instead when "
"generating the proxies. See <xref linkend=\"persistent-classes-pojo-final-"
"example-proxy-interface-xml\"/> and <xref linkend=\"persistent-classes-pojo-"
"final-example-proxy-interface-ann\"/>."
msgstr ""
#. Tag: title
#: persistent_classes.xml:139
#, no-c-format
msgid "Proxying an interface in <literal>hbm.xml"
msgstr ""
#. Tag: programlisting
#: persistent_classes.xml:140
#, no-c-format
msgid "<![CDATA[]]>"
msgstr ""
#. Tag: title
#: persistent_classes.xml:144
#, no-c-format
msgid "Proxying an interface in annotations"
msgstr ""
#. Tag: programlisting
#: persistent_classes.xml:145
#, no-c-format
msgid ""
"<![CDATA[@Entity @Proxy(proxyClass=ICat.class) public class Cat implements "
"ICat { ... }]]>"
msgstr ""
#. Tag: para
#: persistent_classes.xml:148
#, fuzzy, no-c-format
msgid ""
"You should also avoid declaring <literal>public final methods as "
"this will again limit the ability to generate <emphasis>proxies "
"from this class. If you want to use a class with <literal>public final メソッドを定義すること"
"も避けるべきです。 <literal>public final メソッドを持つクラスを使い"
"たければ、 <literal>lazy=\"false\" と設定して明示的にプロキシを無効"
"にしなければなりません。"
#. Tag: title
#: persistent_classes.xml:158
#, no-c-format
msgid "Declare accessors and mutators for persistent fields (optional)"
msgstr "永続フィールドに対するアクセサとミューテータを定義する（オプション）"
#. Tag: para
#: persistent_classes.xml:160
#, fuzzy, no-c-format
msgid ""
"<classname>Cat declares accessor methods for all its persistent "
"fields. Many other ORM tools directly persist instance variables. 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>getFooisFoo and setFoo. If "
"required, you can switch to direct field access for particular properties."
msgstr ""
"<literal>Cat ではすべての永続フィールドに対してアクセサメソッドを定"
"義しています。他の多くの ORM ツールは、永続インスタンス変数を直接永続化しま"
"す。私たちはリレーショナルスキーマとクラスの内部構造を分離する方が良いと信じ"
"ています。デフォルトでは、 Hibernate は JavaBean スタイルのプロパティを永続化"
"し、 <literal>getFoo, isFoo, setFoo be declared public. Hibernate can "
"persist a property declared with <literal>package, "
"<literal>protected or private visibility as "
"well."
msgstr ""
"プロパティは public で宣言する必要は <emphasis>ありません 。 "
"Hibernate はデフォルトで、 <literal>protected もしくは "
"<literal>private の get / set のペアを持つプロパティを永続化するこ"
"とができます。"
#. Tag: title
#: persistent_classes.xml:178
#, no-c-format
msgid "Implementing inheritance"
msgstr "継承の実装"
#. Tag: para
#: persistent_classes.xml:180
#, no-c-format
msgid ""
"A subclass must also observe the first and second rules. It inherits its "
"identifier property from the superclass, <literal>Cat. For example:"
msgstr ""
"サブクラスも1番目と2番目のルールを守らなければなりません。サブクラスはスー"
"パークラス <literal>Cat から識別子プロパティを継承します。"
#. Tag: programlisting
#: persistent_classes.xml:184
#, fuzzy, no-c-format
msgid ""
"package eg;\n"
"\n"
"public class DomesticCat extends Cat {\n"
" private String name;\n"
"\n"
" public String getName() {\n"
" return name;\n"
" }\n"
" protected void setName(String name) {\n"
" this.name=name;\n"
" }\n"
"}"
msgstr ""
"package eg;\n"
"\n"
"public class DomesticCat extends Cat {\n"
" private String name;\n"
"\n"
" public String getName() {\n"
" return name;\n"
" }\n"
" protected void setName(String name) {\n"
" this.name=name;\n"
" }\n"
"}"
#. Tag: title
#: persistent_classes.xml:188
#, no-c-format
msgid ""
"Implementing <literal>equals() and hashCode()"
msgstr "<literal>equals() と hashCode()の実装"
#. Tag: para
#: persistent_classes.xml:191
#, no-c-format
msgid ""
"You have to override the <literal>equals() and hashCode()"
"</literal> methods if you:"
msgstr ""
"以下の条件の場合、 <literal>equals() と hashCode() "
"(the recommended way to represent many-valued associations); <emphasis>and に置く場合。 （これは多値の"
"関連を表現するおすすめの方法です） <emphasis>そして同時に"
#. Tag: para
#: persistent_classes.xml:202
#, no-c-format
msgid "intend to use reattachment of detached instances"
msgstr "分離インスタンスをセッションへ再追加する場合。"
#. Tag: para
#: persistent_classes.xml:206
#, no-c-format
msgid ""
"Hibernate guarantees equivalence of persistent identity (database row) and "
"Java identity only inside a particular session scope. When you mix instances "
"retrieved in different sessions, you must implement <literal>equals()hashCode() if you wish to have meaningful "
"semantics for <literal>Sets."
msgstr ""
"Hibernate は、永続 ID （データベースの行）と、特定のセッションスコープ内に限"
"定ですが Java ID とが等価であることを保証します。ですから異なるセッションで検"
"索したインスタンスを組み合わせる場合、 <literal>Set に意味のあるセ"
"マンティクスを持たせようと思っているならすぐに <literal>equals() "
"と <literal>hashCode() を実装しなければなりません。"
#. Tag: para
#: persistent_classes.xml:212
#, no-c-format
msgid ""
"The most obvious way is to implement <literal>equals()/"
"<literal>hashCode() by comparing the identifier value of both "
"objects. If the value is the same, both must be the same database row, "
"because they are equal. If both are added to a <literal>Set, you "
"will only have one element in the <literal>Set). Unfortunately, "
"you cannot use that approach with generated identifiers. Hibernate will only "
"assign identifier values to objects that are persistent; a newly created "
"instance will not have any identifier value. Furthermore, if an instance is "
"unsaved and currently in a <literal>Set, saving it will assign an "
"identifier value to the object. If <literal>equals() and "
"<literal>hashCode() are based on the identifier value, the hash "
"code would change, breaking the contract of the <literal>Set. See "
"the Hibernate website for a full discussion of this problem. This is not a "
"Hibernate issue, but normal Java semantics of object identity and equality."
msgstr ""
"最も明白な方法は、両方のオブジェクトの識別子の値の比較によって "
"<literal>equals()と hashCode() を実装する方法で"
"す。値が同じなら、両者はデータベースの同じ行でなければならないため等しくなり"
"ます。 （両者が <literal>Set に追加されても、 Set の中にあれば、セーブするとオブジェクトへ識別子の値を代"
"入することになります。もし <literal>equals() と hashCode()"
"</literal> が識別子の値に基づいているなら、ハッシュコードが変更されると "
"<literal>Set の規約が破られます。この問題についての完全な議論は、 "
"Hibernate のウェブサイトを見てください。これは Hibernate の問題ではなく、オブ"
"ジェクトの同一性と等価性についての、通常の Java のセマンティクスであることに"
"注意してください。"
#. Tag: para
#: persistent_classes.xml:228
#, no-c-format
msgid ""
"It is recommended that you implement <literal>equals() and "
"<literal>hashCode() using Business key equalityequals() "
"method compares only the properties that form the business key. It is a key "
"that would identify our instance in the real world (a <emphasis>natural を使って、 equals()hashCode() を実装することをお勧めします。ビジ"
"ネスキーの等価性とは、 <literal>equals() メソッドが、ビジネスキー、"
"つまり現実の世界においてインスタンスを特定するキー（<emphasis>自然s of Maps at runtime) "
"and the representation of entities as DOM4J trees. With this approach, you "
"do not write persistent classes, only mapping files."
msgstr ""
"永続エンティティは、必ずしも実行時に POJO クラスや JavaBean オブジェクトで表"
"現する必要はありません。 Hibernate は（実行時に <literal>Map の "
"<literal>Map を使う）動的モデルと、 DOM4J ツリーとしてのエンティ"
"ティの表現もサポートします。このアプローチを使うと永続クラスを書かず、マッピ"
"ングファイルだけを書くことになります。"
#. Tag: para
#: persistent_classes.xml:259
#, fuzzy, no-c-format
msgid ""
"By default, Hibernate works in normal POJO mode. You can set a default "
"entity representation mode for a particular <literal>SessionFactorydefault_entity_mode configuration "
"option (see <xref linkend=\"configuration-optional-properties\"/>)."
msgstr ""
"デフォルトでは、 Hibernate は通常の POJO モードで動作します。 "
"<literal>default_entity_mode 設定オプションを使って、特定の "
"<literal>SessionFactory に対するデフォルトのエンティティ表現モード"
"を設定することができます （<xref linkend=\"configuration-optional-properties"
"\"/> を見てください）。"
#. Tag: para
#: persistent_classes.xml:265
#, no-c-format
msgid ""
"The following examples demonstrate the representation using <literal>Mapentity-name has "
"to be declared instead of, or in addition to, a class name:"
msgstr ""
"以下の例では <literal>Map を使った表現を紹介します。まずマッピング"
"ファイルで、クラス名の代わりに（またはそれに加えて） <literal>entity-name for "
"the <literal>SessionFactory, you can, at runtime, work with "
"<literal>Maps of Maps:"
msgstr ""
"<literal>SessionFactory に対してデフォルトのエンティティモードを "
"<literal>dynamic-map に設定した後、実行時に Map "
"の <literal>Map を使うことができます："
#. Tag: programlisting
#: persistent_classes.xml:281
#, fuzzy, no-c-format
msgid ""
"Session s = openSession();\n"
"Transaction tx = s.beginTransaction();\n"
"\n"
"// Create a customer\n"
"Map david = new HashMap();\n"
"david.put(\"name\", \"David\");\n"
"\n"
"// Create an organization\n"
"Map foobar = new HashMap();\n"
"foobar.put(\"name\", \"Foobar Inc.\");\n"
"\n"
"// Link both\n"
"david.put(\"organization\", foobar);\n"
"\n"
"// Save both\n"
"s.save(\"Customer\", david);\n"
"s.save(\"Organization\", foobar);\n"
"\n"
"tx.commit();\n"
"s.close();"
msgstr ""
"Session s = openSession();\n"
"Transaction tx = s.beginTransaction();\n"
"Session s = openSession();\n"
"\n"
"// Create a customer\n"
"Map david = new HashMap();\n"
"david.put(\"name\", \"David\");\n"
"\n"
"// Create an organization\n"
"Map foobar = new HashMap();\n"
"foobar.put(\"name\", \"Foobar Inc.\");\n"
"\n"
"// Link both\n"
"david.put(\"organization\", foobar);\n"
"\n"
"// Save both\n"
"s.save(\"Customer\", david);\n"
"s.save(\"Organization\", foobar);\n"
"\n"
"tx.commit();\n"
"s.close();"
#. Tag: para
#: persistent_classes.xml:283
#, no-c-format
msgid ""
"One of the main advantages of dynamic mapping is quick turnaround time for "
"prototyping, without the need for entity class implementation. However, you "
"lose compile-time type checking and will likely deal with many exceptions at "
"runtime. As a result of the Hibernate mapping, the database schema can "
"easily be normalized and sound, allowing to add a proper domain model "
"implementation on top later on."
msgstr ""
"動的なマッピングの利点は、エンティティクラスの実装を必要としないため、プロト"
"タイピングに要するターンアラウンドタイムが早いということです。しかしコンパイ"
"ル時の型チェックがないので、実行時に非常に多くの例外処理を扱わなければならな"
"いでしょう。 Hibernate マッピングのおかげで、データベーススキーマは容易に正規"
"化でき、健全になり、後で適切なドメインモデルの実装を追加することが可能になり"
"ます。"
#. Tag: para
#: persistent_classes.xml:290
#, no-c-format
msgid ""
"Entity representation modes can also be set on a per <literal>Session ごとに設定することも可能"
"です。"
#. Tag: programlisting
#: persistent_classes.xml:293
#, fuzzy, no-c-format
msgid ""
"Session dynamicSession = pojoSession.getSession(EntityMode.MAP);\n"
"\n"
"// Create a customer\n"
"Map david = new HashMap();\n"
"david.put(\"name\", \"David\");\n"
"dynamicSession.save(\"Customer\", david);\n"
"...\n"
"dynamicSession.flush();\n"
"dynamicSession.close()\n"
"...\n"
"// Continue on pojoSession"
msgstr ""
"Session dynamicSession = pojoSession.getSession(EntityMode.MAP);\n"
"\n"
"// Create a customer\n"
"Map david = new HashMap();\n"
"david.put(\"name\", \"David\");\n"
"dynamicSession.save(\"Customer\", david);\n"
"...\n"
"dynamicSession.flush();\n"
"dynamicSession.close()\n"
"...\n"
"// Continue on pojoSession"
#. Tag: para
#: persistent_classes.xml:295
#, no-c-format
msgid ""
"Please note that the call to <literal>getSession() using an "
"<literal>EntityMode is on the Session API, not "
"the <literal>SessionFactory. That way, the new Sessionclose() on the secondary Session を使った getSession() の呼び"
"出しは <literal>SessionFactory ではなく Session "
"APIにあることに注意してください。その方法では、新しい <literal>Session では "
"<literal>flush() と close() を呼ぶ必要がないとい"
"うこと、そのためトランザクションとコネクションの管理を1番目の作業単位(Unit "
"of Work)に任せることができるということです。"
#. Tag: para
#: persistent_classes.xml:304
#, fuzzy, no-c-format
msgid ""
"More information about the XML representation capabilities can be found in "
"<xref linkend=\"xml\"/>."
msgstr ""
"XML 表現の能力についてのさらなる情報は <xref linkend=\"xml\"/> に記述されてい"
"ます。"
#. Tag: title
#: persistent_classes.xml:310
#, no-c-format
msgid "Tuplizers"
msgstr "Tuplizer"
#. Tag: para
#: persistent_classes.xml:312
#, fuzzy, no-c-format
msgid ""
"<interfacename>org.hibernate.tuple.Tuplizer and its sub-"
"interfaces are responsible for managing a particular representation of a "
"piece of data given that representation's <classname>org.hibernate."
"EntityMode</classname>. If a given piece of data is thought of as a data "
"structure, then a tuplizer is the thing that knows how to create such a data "
"structure, how to extract values from such a data structure and how to "
"inject values into such a data structure. For example, for the POJO entity "
"mode, the corresponding tuplizer knows how create the POJO through its "
"constructor. It also knows how to access the POJO properties using the "
"defined property accessors."
msgstr ""
"<literal>org.hibernate.tuple.Tuplizer とそのサブインターフェース"
"は、表現の <literal>org.hibernate.EntityMode を利用して、データ断片"
"のある表現の管理に責任を持ちます。与えられたデータ断片をデータ構造として考え"
"るなら、 Tuplizer はそのようなデータ構造をどのように作成するかを知り、そのよ"
"うなデータ構造からどのように値を抽出し、注入するかを知っています。例えば "
"POJO エンティティモードでは、対応する Tuplizer はコンストラクタを通して、 "
"POJO をどのように作成するか、定義されたプロパティアクセサを使い、 POJO プロパ"
"ティにどのようにアクセスするかを知ります。"
#. Tag: para
#: persistent_classes.xml:322
#, no-c-format
msgid "There are two (high-level) types of Tuplizers:"
msgstr ""
#. Tag: para
#: persistent_classes.xml:326
#, no-c-format
msgid ""
"<interfacename>org.hibernate.tuple.entity.EntityTuplizer "
"which is responsible for managing the above mentioned contracts in regards "
"to entities"
msgstr ""
#. Tag: para
#: persistent_classes.xml:332
#, no-c-format
msgid ""
"<interfacename>org.hibernate.tuple.component.ComponentTuplizer implementation other than "
"<classname>java.util.HashMap be used while in the dynamic-map "
"entity-mode. Or perhaps you need to define a different proxy generation "
"strategy than the one used by default. Both would be achieved by defining a "
"custom tuplizer implementation. Tuplizer definitions are attached to the "
"entity or component mapping they are meant to manage. Going back to the "
"example of our <classname>Customer entity, "
"using annotations while <xref linkend=\"example-specify-custom-tuplizer-xml"
"\"/> shows how to do the same in <literal>hbm.xml"
msgstr ""
"ユーザーは独自の Tuplizer に差し替えることも可能です。おそらく dynamic-map "
"entity-mode の際に <literal>java.util.HashMap を使うのではなく、 "
"<literal>java.util.Map の実装が必要でしょう。もしくは、おそらくデ"
"フォルトのものではなく、別のプロキシ生成戦略の定義が必要でしょう。両者とも、"
"カスタムの Tuplizer 実装を定義することで達成されます。 Tuplizer の定義は、管"
"理しようとするエンティティやコンポーネントのマッピングに結び付けられます。顧"
"客エンティティの例は以下になります："
#. Tag: title
#: persistent_classes.xml:353
#, no-c-format
msgid "Specify custom tuplizers in annotations"
msgstr ""
#. Tag: programlisting
#: persistent_classes.xml:354
#, no-c-format
msgid ""
"@Entity\n"
"@Tuplizer(impl = DynamicEntityTuplizer.class)\n"
"public interface Cuisine {\n"
" @Id\n"
" @GeneratedValue\n"
" public Long getId();\n"
" public void setId(Long id);\n"
"\n"
" public String getName();\n"
" public void setName(String name);\n"
"\n"
" @Tuplizer(impl = DynamicComponentTuplizer.class)\n"
" public Country getCountry();\n"
" public void setCountry(Country country);\n"
"}"
msgstr ""
#. Tag: title
#: persistent_classes.xml:357
#, no-c-format
msgid "Specify custom tuplizers in <literal>hbm.xml"
msgstr ""
#. Tag: programlisting
#: persistent_classes.xml:358
#, no-c-format
msgid ""
"<hibernate-mapping>\n"
" <class entity-name=\"Customer\">\n"
" <!--\n"
" Override the dynamic-map entity-mode\n"
" tuplizer for the customer entity\n"
" -->\n"
" <tuplizer entity-mode=\"dynamic-map\"\n"
" class=\"CustomMapTuplizerImpl\"/>\n"
"\n"
" <id name=\"id\" type=\"long\" column=\"ID\">\n"
" <generator class=\"sequence\"/>\n"
" </id>\n"
"\n"
" <!-- other properties -->\n"
" ...\n"
" </class>\n"
"</hibernate-mapping>"
msgstr ""
#. Tag: title
#: persistent_classes.xml:363
#, fuzzy, no-c-format
msgid "EntityNameResolvers"
msgstr "エンティティリゾルバ"
#. Tag: para
#: persistent_classes.xml:365
#, no-c-format
msgid ""
"<interfacename>org.hibernate.EntityNameResolver is a "
"contract for resolving the entity name of a given entity instance. The "
"interface defines a single method <methodname>resolveEntityName "
"which is passed the entity instance and is expected to return the "
"appropriate entity name (null is allowed and would indicate that the "
"resolver does not know how to resolve the entity name of the given entity "
"instance). Generally speaking, an <interfacename>org.hibernate."
"EntityNameResolver</interfacename> is going to be most useful in the case of "
"dynamic models. One example might be using proxied interfaces as your domain "
"model. The hibernate test suite has an example of this exact style of usage "
"under the <package>org.hibernate.test.dynamicentity.tuplizer2. "
"Here is some of the code from that package for illustration."
msgstr ""
#. Tag: programlisting
#: persistent_classes.xml:377
#, no-c-format
msgid ""
"/**\n"
" * A very trivial JDK Proxy InvocationHandler implementation where we proxy "
"an\n"
" * interface as the domain model and simply store persistent state in an "
"internal\n"
" * Map. This is an extremely trivial example meant only for illustration.\n"
" */\n"
"public final class DataProxyHandler implements InvocationHandler {\n"
" private String entityName;\n"
" private HashMap data = new HashMap();\n"
"\n"
" public DataProxyHandler(String entityName, Serializable id) {\n"
" this.entityName = entityName;\n"
" data.put( \"Id\", id );\n"
" }\n"
"\n"
" public Object invoke(Object proxy, Method method, Object[] args) "
"throws Throwable {\n"
" String methodName = method.getName();\n"
" if ( methodName.startsWith( \"set\" ) ) {\n"
" String propertyName = methodName.substring( 3 );\n"
" data.put( propertyName, args[0] );\n"
" }\n"
" else if ( methodName.startsWith( \"get\" ) ) {\n"
" String propertyName = methodName.substring( 3 );\n"
" return data.get( propertyName );\n"
" }\n"
" else if ( \"toString\".equals( methodName ) ) {\n"
" return entityName + \"#\" + data.get( \"Id\" );\n"
" }\n"
" else if ( \"hashCode\".equals( methodName ) ) {\n"
" return new Integer( this.hashCode() );\n"
" }\n"
" return null;\n"
" }\n"
"\n"
" public String getEntityName() {\n"
" return entityName;\n"
" }\n"
"\n"
" public HashMap getData() {\n"
" return data;\n"
" }\n"
"}\n"
"\n"
"public class ProxyHelper {\n"
" public static String extractEntityName(Object object) {\n"
" // Our custom java.lang.reflect.Proxy instances actually bundle\n"
" // their appropriate entity name, so we simply extract it from "
"there\n"
" // if this represents one of our proxies; otherwise, we return null\n"
" if ( Proxy.isProxyClass( object.getClass() ) ) {\n"
" InvocationHandler handler = Proxy.getInvocationHandler"
"( object );\n"
" if ( DataProxyHandler.class.isAssignableFrom( handler.getClass"
"() ) ) {\n"
" DataProxyHandler myHandler = ( DataProxyHandler ) handler;\n"
" return myHandler.getEntityName();\n"
" }\n"
" }\n"
" return null;\n"
" }\n"
"\n"
" // various other utility methods ....\n"
"\n"
"}\n"
"\n"
"/**\n"
" * The EntityNameResolver implementation.\n"
" *\n"
" * IMPL NOTE : An EntityNameResolver really defines a strategy for how "
"entity names\n"
" * should be resolved. Since this particular impl can handle resolution for "
"all of our\n"
" * entities we want to take advantage of the fact that SessionFactoryImpl "
"keeps these\n"
" * in a Set so that we only ever have one instance registered. Why? Well, "
"when it\n"
" * comes time to resolve an entity name, Hibernate must iterate over all the "
"registered\n"
" * resolvers. So keeping that number down helps that process be as speedy "
"as possible.\n"
" * Hence the equals and hashCode implementations as is\n"
" */\n"
"public class MyEntityNameResolver implements EntityNameResolver {\n"
" public static final MyEntityNameResolver INSTANCE = new "
"MyEntityNameResolver();\n"
"\n"
" public String resolveEntityName(Object entity) {\n"
" return ProxyHelper.extractEntityName( entity );\n"
" }\n"
"\n"
" public boolean equals(Object obj) {\n"
" return getClass().equals( obj.getClass() );\n"
" }\n"
"\n"
" public int hashCode() {\n"
" return getClass().hashCode();\n"
" }\n"
"}\n"
"\n"
"public class MyEntityTuplizer extends PojoEntityTuplizer {\n"
" public MyEntityTuplizer(EntityMetamodel entityMetamodel, "
"PersistentClass mappedEntity) {\n"
" super( entityMetamodel, mappedEntity );\n"
" }\n"
"\n"
" public EntityNameResolver[] getEntityNameResolvers() {\n"
" return new EntityNameResolver[] { MyEntityNameResolver."
"INSTANCE };\n"
" }\n"
"\n"
" public String determineConcreteSubclassEntityName(Object entityInstance, "
"SessionFactoryImplementor factory) {\n"
" String entityName = ProxyHelper.extractEntityName"
"( entityInstance );\n"
" if ( entityName == null ) {\n"
" entityName = super.determineConcreteSubclassEntityName"
"( entityInstance, factory );\n"
" }\n"
" return entityName;\n"
" }\n"
"\n"
" ..."
msgstr ""
#. Tag: para
#: persistent_classes.xml:379
#, no-c-format
msgid ""
"In order to register an <interfacename>org.hibernate.EntityNameResolvergetEntityNameResolvers "
"method"
msgstr ""
#. Tag: para
#: persistent_classes.xml:389
#, no-c-format
msgid ""
"Register it with the <classname>org.hibernate.impl.SessionFactoryImplorg."
"hibernate.SessionFactory</interfacename>) using the "
"<methodname>registerEntityNameResolver method."
msgstr ""
#, fuzzy
#~ msgid ""
#~ "Most Java applications require a persistent class representing felines. "
#~ "For example:"
#~ msgstr "以下はネコ科の動物を表現する永続クラスです。"
#, fuzzy
#~ msgid ""
#~ "<literal>Cat has a property called id. This "
#~ "property maps to the primary key column of a database table. The property "
#~ "might have been called anything, and its type might have been any "
#~ "primitive type, any primitive \"wrapper\" type, <literal>java.lang."
#~ "String</literal> or java.util.Date. If your legacy "
#~ "database table has composite keys, you can use a user-defined class with "
#~ "properties of these types (see the section on composite identifiers later "
#~ "in the chapter.)"
#~ msgstr ""
#~ "<literal>Cat には id というプロパティがありま"
#~ "す。このプロパティはデータベーステーブルの主キーカラムへマッピングされま"
#~ "す。このプロパティの名前は何でも構いませんし、型はどのようなプリミティブ型"
#~ "でも、プリミティブの「ラッパー」型でも、 <literal>java.lang.Stringjava.util.Date でも構いません。 （もしレガ"
#~ "シーデータベーステーブルが複合キーを持つならば、今述べたような型のプロパ"
#~ "ティを持つユーザー定義のクラスを使うことさえ可能です。後で複合識別子のセク"
#~ "ションを見てください。）"
#~ msgid ""
#~ "The identifier property is strictly optional. You can leave them off and "
#~ "let Hibernate keep track of object identifiers internally. We do not "
#~ "recommend this, however."
#~ msgstr ""
#~ "識別子プロパティは厳密にはオプションです。これを省略して、 Hibernate に内"
#~ "部的にオブジェクトの識別子を追跡させることは可能です。しかしお勧めはしませ"
#~ "ん。"
#~ msgid ""
#~ "In fact, some functionality is available only to classes that declare an "
#~ "identifier property:"
#~ msgstr ""
#~ "実際に、識別子プロパティを宣言するクラスだけが利用可能な機能がいくつかあり"
#~ "ます："
#, fuzzy
#~ msgid ""
#~ "Transitive reattachment for detached objects (cascade update or cascade "
#~ "merge) - see <xref linkend=\"objectstate-transitive\" />"
#~ msgstr ""
#~ "分離オブジェクトの連鎖的な再追加（カスケード更新やカスケードマージ） - "
#~ "<xref linkend=\"objectstate-transitive\" />次を参照してください。"
#, fuzzy
#~ msgid "<literal>Session.saveOrUpdate()"
#~ msgstr "<xref linkend=\"objectstate-transitive\" />"
#, fuzzy
#~ msgid "<literal>Session.merge()"
#~ msgstr "<literal>Session.merge()"
#~ msgid ""
#~ "A central feature of Hibernate, <emphasis>proxies, depends "
#~ "upon the persistent class being either non-final, or the implementation "
#~ "of an interface that declares all public methods."
#~ msgstr ""
#~ "Hibernate の中心的な特徴である <emphasis>プロキシ は、永続クラ"
#~ "スが final でないこと、またはメソッドを全部 public で宣言しているインター"
#~ "フェースが実装されているかに依存しています。"
#~ msgid ""
#~ "You can persist <literal>final classes that do not implement an "
#~ "interface with Hibernate. You will not, however, be able to use proxies "
#~ "for lazy association fetching which will ultimately limit your options "
#~ "for performance tuning."
#~ msgstr ""
#~ "Hibernate でインターフェースを実装していない <literal>final クラ"
#~ "スを永続化することはできますが、遅延関連フェッチに対してプロキシを使うこと"
#~ "はできなくなります。これはパフォーマンスチューニングへの選択肢を狭めること"
#~ "になります。"
#~ msgid ""
#~ "There are two high-level types of Tuplizers, represented by the "
#~ "<literal>org.hibernate.tuple.entity.EntityTuplizer and "
#~ "<literal>org.hibernate.tuple.component.ComponentTuplizer "
#~ "interfaces. <literal>EntityTuplizers are responsible for "
#~ "managing the above mentioned contracts in regards to entities, while "
#~ "<literal>ComponentTuplizers do the same for components."
#~ msgstr ""
#~ "Tuplizer には二つのハイレベルの型があります。それらは、<literal>org."
#~ "hibernate.tuple.entity.EntityTuplizer</literal> と org.hibernate."
#~ "tuple.component.ComponentTuplizer</literal> インターフェースで表現されま"
#~ "す。 <literal>EntityTuplizer は上で述べたようなエンティティに関"
#~ "する契約の管理に責任を持ちます。一方、 <literal>ComponentTuplizer
Other Hibernate examples (source code examples)
Here is a short list of links related to this Hibernate persistent_classes.po source code file:
|
The search page
Other Hibernate source code examples at this package level
Click here to learn more about this project
