[jboss-cvs] JBossAS SVN: r96786 - projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/pt-BR.

[jboss-cvs-commits at lists.jboss.org]

Author: ldelima at redhat.com
Date: 2009-11-23 23:31:28 -0500 (Mon, 23 Nov 2009)
New Revision: 96786

Modified:
   projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/pt-BR/entity.po
Log:
translation ongoing

Modified: projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/pt-BR/entity.po
===================================================================
--- projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/pt-BR/entity.po	2009-11-24 03:54:10 UTC (rev 96785)
+++ projects/docs/enterprise/5.0/Hibernate/Hibernate_Annotations_Reference_Guide/pt-BR/entity.po	2009-11-24 04:31:28 UTC (rev 96786)
@@ -8,7 +8,7 @@
 msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2009-11-24 10:09+1000\n"
+"PO-Revision-Date: 2009-11-24 14:31+1000\n"
 "Project-Id-Version: entity\n"
 "Language-Team:  <en at li.org>\n"
 "X-Generator: KBabel 1.11.4\n"
@@ -2658,9 +2658,7 @@
 "literal> to <literal>Monkey</literal> (property name, <keycap>_</keycap>, "
 "Tiger primary column).</para> </sect5>"
 msgstr ""
-"<sect5> <title>Bidirectional</title> <para>Since many to one are (almost) "
-"always the owner side of a bidirectional relationship in the EJB3 spec, the "
-"one to many association is annotated by <literal>@OneToMany( mappedBy=... )</"
+"<sect5> <title>Bidirecional</title> <para> Uma vez que muitos-para-um estão (quase) sempre ao lado do propriedtário de uma relação bidirecional no EJB3 spec, a associação uma-para-muitos é anotada pelo <literal>@OneToMany( mappedBy=... )</"
 "literal></para> <programlisting>@Entity\n"
 "public class Troop {\n"
 "    @OneToMany(mappedBy=\"troop\")\n"
@@ -2674,15 +2672,9 @@
 "    @JoinColumn(name=\"troop_fk\")\n"
 "    public Troop getTroop() {\n"
 "    ...\n"
-"}              </programlisting> <para><classname>Troop</classname> has a "
-"bidirectional one to many relationship with <literal>Soldier</literal> "
-"through the <literal>troop</literal> property. You don't have to (must not) "
-"define any physical mapping in the <literal>mappedBy</literal> side.</para> "
-"<para>To map a bidirectional one to many, with the one-to-many side as the "
-"owning side, you have to remove the <literal>mappedBy</literal> element and "
-"set the many to one <literal>@JoinColumn</literal> as insertable and "
-"updatable to false. This solution is obviously not optimized and will "
-"produce some additional UPDATE statements.</para> <programlisting>@Entity\n"
+"}              </programlisting> <para><classname>Troop</classname> possui uma relação um-para-muito bidirecional com <literal>Soldier</literal> "
+"através da propriedade <literal>troop</literal>. Você não precisa definir (não deve) qualquer mapeamento ao lado <literal>mappedBy</literal>. </para> "
+"<para>Para mapear um-para-muitos direcional, com o lado um-para-muitos como o lado proprietário, você precisa remover o elemento <literal>mappedBy</literal> e configurar o <literal>@JoinColumn</literal> muitos-para-um como inserível e atualizável para falso. Esta solução não é otimizada e produzirá algumas declarações UPDATE adicionais.</para> <programlisting>@Entity\n"
 "public class Troop {\n"
 "    @OneToMany\n"
 "    @JoinColumn(name=\"troop_fk\") //we need to duplicate the physical "
@@ -2697,7 +2689,7 @@
 "    @JoinColumn(name=\"troop_fk\", insertable=false, updatable=false)\n"
 "    public Troop getTroop() {\n"
 "    ...\n"
-"}</programlisting> </sect5> <sect5> <title>Unidirectional</title> <para>A "
+"}</programlisting> </sect5> <sect5> <title>Unidirecional</title> <para> Um-para-muitos unidirecional usando uma coluna chave exterior na entidade proprietária   A "
 "unidirectional one to many using a foreign key column in the owned entity is "
 "not that common and not really recommended. We strongly advise you to use a "
 "join table for this kind of association (as explained in the next section). "