[webbeans-commits] Webbeans SVN: r1130 - in doc/trunk/reference: en-US and 8 other directories.
webbeans-commits at lists.jboss.org
webbeans-commits at lists.jboss.org
Tue Jan 20 15:33:42 EST 2009
Author: nico.ben
Date: 2009-01-20 15:33:41 -0500 (Tue, 20 Jan 2009)
New Revision: 1130
Modified:
doc/trunk/reference/de-DE/ee.po
doc/trunk/reference/de-DE/events.po
doc/trunk/reference/de-DE/injection.po
doc/trunk/reference/de-DE/interceptors.po
doc/trunk/reference/de-DE/intro.po
doc/trunk/reference/de-DE/part3.po
doc/trunk/reference/de-DE/scopescontexts.po
doc/trunk/reference/en-US/ee.xml
doc/trunk/reference/en-US/events.xml
doc/trunk/reference/en-US/injection.xml
doc/trunk/reference/en-US/interceptors.xml
doc/trunk/reference/en-US/intro.xml
doc/trunk/reference/en-US/part3.xml
doc/trunk/reference/en-US/scopescontexts.xml
doc/trunk/reference/es-ES/ee.po
doc/trunk/reference/es-ES/events.po
doc/trunk/reference/es-ES/injection.po
doc/trunk/reference/es-ES/interceptors.po
doc/trunk/reference/es-ES/intro.po
doc/trunk/reference/es-ES/part3.po
doc/trunk/reference/es-ES/scopescontexts.po
doc/trunk/reference/fr-FR/ee.po
doc/trunk/reference/fr-FR/events.po
doc/trunk/reference/fr-FR/injection.po
doc/trunk/reference/fr-FR/interceptors.po
doc/trunk/reference/fr-FR/intro.po
doc/trunk/reference/fr-FR/part3.po
doc/trunk/reference/fr-FR/scopescontexts.po
doc/trunk/reference/it-IT/ee.po
doc/trunk/reference/it-IT/events.po
doc/trunk/reference/it-IT/injection.po
doc/trunk/reference/it-IT/interceptors.po
doc/trunk/reference/it-IT/intro.po
doc/trunk/reference/it-IT/part3.po
doc/trunk/reference/it-IT/scopescontexts.po
doc/trunk/reference/ja-JP/ee.po
doc/trunk/reference/ja-JP/events.po
doc/trunk/reference/ja-JP/injection.po
doc/trunk/reference/ja-JP/interceptors.po
doc/trunk/reference/ja-JP/intro.po
doc/trunk/reference/ja-JP/part3.po
doc/trunk/reference/ja-JP/scopescontexts.po
doc/trunk/reference/ko-KR/ee.po
doc/trunk/reference/ko-KR/events.po
doc/trunk/reference/ko-KR/injection.po
doc/trunk/reference/ko-KR/interceptors.po
doc/trunk/reference/ko-KR/intro.po
doc/trunk/reference/ko-KR/part3.po
doc/trunk/reference/ko-KR/scopescontexts.po
doc/trunk/reference/pt-BR/ee.po
doc/trunk/reference/pt-BR/events.po
doc/trunk/reference/pt-BR/injection.po
doc/trunk/reference/pt-BR/interceptors.po
doc/trunk/reference/pt-BR/intro.po
doc/trunk/reference/pt-BR/part3.po
doc/trunk/reference/pt-BR/scopescontexts.po
doc/trunk/reference/zh-CN/ee.po
doc/trunk/reference/zh-CN/events.po
doc/trunk/reference/zh-CN/injection.po
doc/trunk/reference/zh-CN/interceptors.po
doc/trunk/reference/zh-CN/intro.po
doc/trunk/reference/zh-CN/part3.po
doc/trunk/reference/zh-CN/scopescontexts.po
doc/trunk/reference/zh-TW/ee.po
doc/trunk/reference/zh-TW/events.po
doc/trunk/reference/zh-TW/injection.po
doc/trunk/reference/zh-TW/interceptors.po
doc/trunk/reference/zh-TW/intro.po
doc/trunk/reference/zh-TW/part3.po
doc/trunk/reference/zh-TW/scopescontexts.po
Log:
Inserted space before and after —
Modified: doc/trunk/reference/de-DE/ee.po
===================================================================
--- doc/trunk/reference/de-DE/ee.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/de-DE/ee.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -311,7 +311,7 @@
#, no-c-format
msgid ""
"Web Beans doesn't define any special deployment archive. You can package Web "
-"Beans in JARs, EJB-JARs or WARs—any deployment location in the "
+"Beans in JARs, EJB-JARs or WARs — any deployment location in the "
"application classpath. However, each archive that contains Web Beans must "
"include a file named <literal>web-beans.xml</literal> in the <literal>META-"
"INF</literal> or <literal>WEB-INF</literal> directory. The file may be "
Modified: doc/trunk/reference/de-DE/events.po
===================================================================
--- doc/trunk/reference/de-DE/events.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/de-DE/events.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -117,7 +117,7 @@
#: events.xml:48
#, no-c-format
msgid ""
-"An observer method need not specify any event bindings—in this case it "
+"An observer method need not specify any event bindings — in this case it "
"is interested in <emphasis>all</emphasis> events of a particular type. If it "
"does specify event bindings, it is only interested in events which also have "
"those event bindings."
Modified: doc/trunk/reference/de-DE/injection.po
===================================================================
--- doc/trunk/reference/de-DE/injection.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/de-DE/injection.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -653,8 +653,8 @@
#, no-c-format
msgid ""
"If you've been paying attention, you're probably wondering how the Web Bean "
-"manager decides which implementation—<literal>ExternalPaymentProcessor</"
-"literal> or <literal>MockPaymentProcessor</literal>—to choose. Consider "
+"manager decides which implementation — <literal>ExternalPaymentProcessor</"
+"literal> or <literal>MockPaymentProcessor</literal> — to choose. Consider "
"what happens when the manager encounters this injection point:"
msgstr ""
@@ -794,7 +794,7 @@
msgid ""
"To fix an <literal>UnsatisfiedDependencyException</literal>, simply provide "
"a Web Bean which implements the API type and has the binding types of the "
-"injection point—or enable the deployment type of a Web Bean that "
+"injection point — or enable the deployment type of a Web Bean that "
"already implements the API type and has the binding types."
msgstr ""
@@ -973,7 +973,7 @@
#, no-c-format
msgid ""
"If the binding type has an annotation member, we can't use an anonymous "
-"subclass of <literal>AnnotationLiteral</literal>—instead we'll need to "
+"subclass of <literal>AnnotationLiteral</literal> — instead we'll need to "
"create a named subclass:"
msgstr ""
@@ -1053,8 +1053,8 @@
#: injection.xml:442
#, no-c-format
msgid ""
-"There are certain kinds of dependent objects—Web Beans with scope "
-"<literal>@Dependent</literal>—that need to know something about the "
+"There are certain kinds of dependent objects — Web Beans with scope "
+"<literal>@Dependent</literal> — that need to know something about the "
"object or injection point into which they are injected in order to be able "
"to do what they do. For example:"
msgstr ""
Modified: doc/trunk/reference/de-DE/interceptors.po
===================================================================
--- doc/trunk/reference/de-DE/interceptors.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/de-DE/interceptors.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -486,7 +486,7 @@
msgid ""
"Well, fortunately, Web Beans works around this missing feature of Java. We "
"may annotate one interceptor binding type with other interceptor binding "
-"types. The interceptor bindings are transitive—any Web Bean with the "
+"types. The interceptor bindings are transitive — any Web Bean with the "
"first interceptor binding inherits the interceptor bindings declared as meta-"
"annotations."
msgstr ""
@@ -560,7 +560,7 @@
#: interceptors.xml:212
#, no-c-format
msgid ""
-"the interceptor ordering is non-global—it is determined by the order in "
+"the interceptor ordering is non-global — it is determined by the order in "
"which interceptors are listed at the class level."
msgstr ""
Modified: doc/trunk/reference/de-DE/intro.po
===================================================================
--- doc/trunk/reference/de-DE/intro.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/de-DE/intro.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -49,14 +49,14 @@
"Furthermore, every EJB 3-style session bean is a Web Bean. Sure, the "
"JavaBeans and EJBs you've been writing every day have not been able to take "
"advantage of the new services defined by the Web Beans specification, but "
-"you'll be able to use every one of them as Web Beans—injecting them "
+"you'll be able to use every one of them as Web Beans — injecting them "
"into other Web Beans, configuring them via the Web Beans XML configuration "
-"facility, even adding interceptors and decorators to them—without "
+"facility, even adding interceptors and decorators to them — without "
"touching your existing code."
msgstr ""
"Mit bestimmten, ganz besonderen Ausnahmen ist jede Java-Klasse mit einem Konstruktor, die keine Parameter akzeptiert ein Web Bean. Das beinhaltet jedes JavaBean. "
"Desweiteren ist jedes EJB 3-artige Session Bean ein Web Bean. Sicher, die von Ihnen täglich geschriebenen "
-"JavaBeans und EJBs konnten die neuen, in der Web Beans Spezifikation definierten Dienste nicht nutzen, aber Sie werden diese allesamt benutzen können können, das Web Beans—diese in andere "
+"JavaBeans und EJBs konnten die neuen, in der Web Beans Spezifikation definierten Dienste nicht nutzen, aber Sie werden diese allesamt benutzen können können, das Web Beans — diese in andere "
"Web Beans einspeisen, diese via der Web Beans XML-Konfigurationseinrichtung konfigurieren "
"und diesen sogar Interzeptoren und Dekoratoren hinzufügen, ohne den bestehenden Code anzurühren."
@@ -252,14 +252,14 @@
"At system initialization time, the Web Bean manager must validate that "
"exactly one Web Bean exists which satisfies each injection point. In our "
"example, if no implementation of <literal>Translator</literal> "
-"available—if the <literal>SentenceTranslator</literal> EJB was not "
-"deployed—the Web Bean manager would throw an "
+"available — if the <literal>SentenceTranslator</literal> EJB was not "
+"deployed — the Web Bean manager would throw an "
"<literal>UnsatisfiedDependencyException</literal>. If more than one "
"implementation of <literal>Translator</literal> was available, the Web Bean "
"manager would throw an <literal>AmbiguousDependencyException</literal>."
msgstr ""
"Zum Zeitpunkt der Systeminitialisierung muss der Web Bean Manager validieren, dass genau ein "
-"Web Bean existiert, das jedem Einspeisungspunkt gerecht wird. Für unser Beispiel bedeutet das, wenn keine Implementierung von <literal>Translator</literal> verfügbar ist—wenn der <literal>SentenceTranslator</literal> EJB nicht deployt wurde—dass der Web Bean Manager eine <literal>UnsatisfiedDependencyException</literal> melden würde. Wäre mehr als eine Implementierung von <literal>Translator</literal> verfügbar, so würde der Web Bean "
+"Web Bean existiert, das jedem Einspeisungspunkt gerecht wird. Für unser Beispiel bedeutet das, wenn keine Implementierung von <literal>Translator</literal> verfügbar ist — wenn der <literal>SentenceTranslator</literal> EJB nicht deployt wurde — dass der Web Bean Manager eine <literal>UnsatisfiedDependencyException</literal> melden würde. Wäre mehr als eine Implementierung von <literal>Translator</literal> verfügbar, so würde der Web Bean "
"Manager eine <literal>AmbiguousDependencyException</literal> melden."
#. Tag: title
@@ -387,8 +387,8 @@
#, no-c-format
msgid ""
"Note that not all clients of a Web Bean are Web Beans. Other objects such as "
-"Servlets or Message-Driven Beans—which are by nature not injectable, "
-"contextual objects—may also obtain references to Web Beans by injection."
+"Servlets or Message-Driven Beans — which are by nature not injectable, "
+"contextual objects — may also obtain references to Web Beans by injection."
msgstr ""
#. Tag: para
@@ -759,7 +759,7 @@
#: intro.xml:289
#, no-c-format
msgid ""
-"In this case, the name defaults to <literal>shoppingCart</literal>—the "
+"In this case, the name defaults to <literal>shoppingCart</literal> — the "
"unqualified class name, with the first character changed to lowercase."
msgstr ""
@@ -908,8 +908,8 @@
msgid ""
"The specification says that all EJB 3-style session and singleton beans are "
"<emphasis>enterprise</emphasis> Web Beans. Message driven beans are not Web "
-"Beans—since they are not intended to be injected into other "
-"objects—but they can take advantage of most of the functionality of Web "
+"Beans — since they are not intended to be injected into other "
+"objects — but they can take advantage of most of the functionality of Web "
"Beans, including dependency injection and interceptors."
msgstr ""
Modified: doc/trunk/reference/de-DE/part3.po
===================================================================
--- doc/trunk/reference/de-DE/part3.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/de-DE/part3.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -28,8 +28,8 @@
#, no-c-format
msgid ""
"You don't see string-based identifiers in Web Beans code, not because the "
-"framework is hiding them from you using clever defaulting rules—so-"
-"called \"configuration by convention\"—but because there are simply no "
+"framework is hiding them from you using clever defaulting rules — so-"
+"called \"configuration by convention\" — but because there are simply no "
"strings there to begin with!"
msgstr ""
Modified: doc/trunk/reference/de-DE/scopescontexts.po
===================================================================
--- doc/trunk/reference/de-DE/scopescontexts.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/de-DE/scopescontexts.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -421,7 +421,7 @@
"The Web Bean manager is permitted to destroy a conversation and all state "
"held in its context at any time in order to preserve resources. A Web Bean "
"manager implementation will normally do this on the basis of some kind of "
-"timeout—though this is not required by the Web Beans specification. The "
+"timeout — though this is not required by the Web Beans specification. The "
"timeout is the period of inactivity before the conversation is destroyed."
msgstr ""
Modified: doc/trunk/reference/en-US/ee.xml
===================================================================
--- doc/trunk/reference/en-US/ee.xml 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/en-US/ee.xml 2009-01-20 20:33:41 UTC (rev 1130)
@@ -170,7 +170,7 @@
<title>Packaging and deployment</title>
<para>Web Beans doesn't define any special deployment archive. You can package
- Web Beans in JARs, EJB-JARs or WARs—any deployment location in the application
+ Web Beans in JARs, EJB-JARs or WARs — any deployment location in the application
classpath. However, each archive that contains Web Beans must include a file named
<literal>web-beans.xml</literal> in the <literal>META-INF</literal> or
<literal>WEB-INF</literal> directory. The file may be empty. Web Beans deployed in
Modified: doc/trunk/reference/en-US/events.xml
===================================================================
--- doc/trunk/reference/en-US/events.xml 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/en-US/events.xml 2009-01-20 20:33:41 UTC (rev 1130)
@@ -48,7 +48,7 @@
<programlisting role="JAVA"><![CDATA[public void afterDocumentUpdate(@Observes @Updated Document document) { ... }]]></programlisting>
- <para>An observer method need not specify any event bindings—in this case it
+ <para>An observer method need not specify any event bindings — in this case it
is interested in <emphasis>all</emphasis> events of a particular type. If it does
specify event bindings, it is only interested in events which also have those
event bindings.</para>
Modified: doc/trunk/reference/en-US/injection.xml
===================================================================
--- doc/trunk/reference/en-US/injection.xml 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/en-US/injection.xml 2009-01-20 20:33:41 UTC (rev 1130)
@@ -324,8 +324,8 @@
<title>Deployment type precedence</title>
<para>If you've been paying attention, you're probably wondering how the Web Bean
-manager decides which implementation—<literal>ExternalPaymentProcessor</literal>
-or <literal>MockPaymentProcessor</literal>—to choose. Consider what happens when
+manager decides which implementation — <literal>ExternalPaymentProcessor</literal>
+or <literal>MockPaymentProcessor</literal> — to choose. Consider what happens when
the manager encounters this injection point:</para>
<programlisting role="JAVA"><![CDATA[@Current PaymentProcessor paymentProcessor]]></programlisting>
@@ -402,7 +402,7 @@
<para>To fix an <literal>UnsatisfiedDependencyException</literal>, simply provide
a Web Bean which implements the API type and has the binding types of the injection
- point—or enable the deployment type of a Web Bean that already implements the
+ point — or enable the deployment type of a Web Bean that already implements the
API type and has the binding types.</para>
<para>To fix an <literal>AmbiguousDependencyException</literal>, introduce a
@@ -489,7 +489,7 @@
new AnnotationLiteral<CreditCard>(){});]]></programlisting>
<para>If the binding type has an annotation member, we can't use an anonymous subclass of
- <literal>AnnotationLiteral</literal>—instead we'll need to create a named subclass:</para>
+ <literal>AnnotationLiteral</literal> — instead we'll need to create a named subclass:</para>
<programlisting role="JAVA"><![CDATA[abstract class CreditCardBinding
extends AnnotationLiteral<CreditCard>
@@ -525,8 +525,8 @@
<section>
<title>The <literal>InjectionPoint</literal> object</title>
- <para>There are certain kinds of dependent objects—Web Beans with scope
- <literal>@Dependent</literal>—that need to know something about the object or injection
+ <para>There are certain kinds of dependent objects — Web Beans with scope
+ <literal>@Dependent</literal> — that need to know something about the object or injection
point into which they are injected in order to be able to do what they do. For example:</para>
<itemizedlist>
Modified: doc/trunk/reference/en-US/interceptors.xml
===================================================================
--- doc/trunk/reference/en-US/interceptors.xml 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/en-US/interceptors.xml 2009-01-20 20:33:41 UTC (rev 1130)
@@ -232,7 +232,7 @@
<para>Well, fortunately, Web Beans works around this missing feature of Java.
We may annotate one interceptor binding type with other interceptor binding
- types. The interceptor bindings are transitive—any Web Bean with the first
+ types. The interceptor bindings are transitive — any Web Bean with the first
interceptor binding inherits the interceptor bindings declared as meta-annotations.</para>
<programlisting role="JAVA"><![CDATA[@Transactional @Secure
@@ -268,7 +268,7 @@
<para>interceptors may not be easily disabled at deployment time, and</para>
</listitem>
<listitem>
- <para>the interceptor ordering is non-global—it is determined
+ <para>the interceptor ordering is non-global — it is determined
by the order in which interceptors are listed at the class level.</para>
</listitem>
</itemizedlist>
Modified: doc/trunk/reference/en-US/intro.xml
===================================================================
--- doc/trunk/reference/en-US/intro.xml 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/en-US/intro.xml 2009-01-20 20:33:41 UTC (rev 1130)
@@ -17,9 +17,9 @@
JavaBean. Furthermore, every EJB 3-style session bean is a Web Bean. Sure,
the JavaBeans and EJBs you've been writing every day have not been able to
take advantage of the new services defined by the Web Beans specification,
- but you'll be able to use every one of them as Web Beans—injecting them
+ but you'll be able to use every one of them as Web Beans — injecting them
into other Web Beans, configuring them via the Web Beans XML configuration
- facility, even adding interceptors and decorators to them—without
+ facility, even adding interceptors and decorators to them — without
touching your existing code.</para>
<para>Suppose that we have two existing Java classes, that we've been using
@@ -97,8 +97,8 @@
<para>At system initialization time, the Web Bean manager must validate that
exactly one Web Bean exists which satisfies each injection point. In our example,
- if no implementation of <literal>Translator</literal> available—if the
- <literal>SentenceTranslator</literal> EJB was not deployed—the Web Bean
+ if no implementation of <literal>Translator</literal> available — if the
+ <literal>SentenceTranslator</literal> EJB was not deployed — the Web Bean
manager would throw an <literal>UnsatisfiedDependencyException</literal>. If
more than one implementation of <literal>Translator</literal> was available,
the Web Bean manager would throw an
@@ -173,8 +173,8 @@
see in <xref linkend="deploymenttypes"/>.</para>
<para>Note that not all clients of a Web Bean are Web Beans. Other objects
- such as Servlets or Message-Driven Beans—which are by nature not injectable,
- contextual objects—may also obtain references to Web Beans by injection.</para>
+ such as Servlets or Message-Driven Beans — which are by nature not injectable,
+ contextual objects — may also obtain references to Web Beans by injection.</para>
<para>Enough hand-waving. More formally, according to the spec:</para>
@@ -328,7 +328,7 @@
<programlisting role="JAVA"><![CDATA[@SessionScoped @Named
public class ShoppingCart { ... }]]></programlisting>
- <para>In this case, the name defaults to <literal>shoppingCart</literal>—the
+ <para>In this case, the name defaults to <literal>shoppingCart</literal> — the
unqualified class name, with the first character changed to lowercase.</para>
</section>
@@ -404,8 +404,8 @@
<para>The specification says that all EJB 3-style session and singleton beans
are <emphasis>enterprise</emphasis> Web Beans. Message driven beans are not
- Web Beans—since they are not intended to be injected into other
- objects—but they can take advantage of most of the functionality of Web
+ Web Beans — since they are not intended to be injected into other
+ objects — but they can take advantage of most of the functionality of Web
Beans, including dependency injection and interceptors.</para>
<para>Every local interface of an enterprise Web Bean that does not have a
Modified: doc/trunk/reference/en-US/part3.xml
===================================================================
--- doc/trunk/reference/en-US/part3.xml 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/en-US/part3.xml 2009-01-20 20:33:41 UTC (rev 1130)
@@ -8,8 +8,8 @@
contained in typesafe Java constructs that may be validated by the compiler.</para>
<para>You don't see string-based identifiers in Web Beans code, not because the
- framework is hiding them from you using clever defaulting rules—so-called
- "configuration by convention"—but because there are simply no strings there
+ framework is hiding them from you using clever defaulting rules — so-called
+ "configuration by convention" — but because there are simply no strings there
to begin with!</para>
<para>The obvious benefit of this approach is that <emphasis>any</emphasis> IDE can
Modified: doc/trunk/reference/en-US/scopescontexts.xml
===================================================================
--- doc/trunk/reference/en-US/scopescontexts.xml 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/en-US/scopescontexts.xml 2009-01-20 20:33:41 UTC (rev 1130)
@@ -236,7 +236,7 @@
<para>The Web Bean manager is permitted to destroy a conversation and all state
held in its context at any time in order to preserve resources. A Web Bean
manager implementation will normally do this on the basis of some kind of
- timeout—though this is not required by the Web Beans specification.
+ timeout — though this is not required by the Web Beans specification.
The timeout is the period of inactivity before the conversation is destroyed.</para>
<para>The <literal>Conversation</literal> object provides a method to set
Modified: doc/trunk/reference/es-ES/ee.po
===================================================================
--- doc/trunk/reference/es-ES/ee.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/es-ES/ee.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -412,7 +412,7 @@
#, no-c-format
msgid ""
"Web Beans doesn't define any special deployment archive. You can package Web "
-"Beans in JARs, EJB-JARs or WARs—any deployment location in the "
+"Beans in JARs, EJB-JARs or WARs — any deployment location in the "
"application classpath. However, each archive that contains Web Beans must "
"include a file named <literal>web-beans.xml</literal> in the <literal>META-"
"INF</literal> or <literal>WEB-INF</literal> directory. The file may be "
@@ -420,7 +420,7 @@
"xml</literal> file will not be available for use in the application."
msgstr ""
"Web Beans no define ningún despliegue especial de archivo. Se puede empaquetar Web "
-"Beans en JAR, EJB-JAR o WAR—cualquier ubicación de despliegue en la aplicación classpath. No obstante, cada archivo que contiene Web Beans debe incluir un archivo llamado <literal>web-beans.xml</literal> en <literal>META-INF</literal> o en el directorio <literal>WEB-INF</literal>. El archivo puede estar vacío. Los Web Beans desplegados en archivos que no tienen un archivo <literal>web-beans."
+"Beans en JAR, EJB-JAR o WAR — cualquier ubicación de despliegue en la aplicación classpath. No obstante, cada archivo que contiene Web Beans debe incluir un archivo llamado <literal>web-beans.xml</literal> en <literal>META-INF</literal> o en el directorio <literal>WEB-INF</literal>. El archivo puede estar vacío. Los Web Beans desplegados en archivos que no tienen un archivo <literal>web-beans."
"xml</literal> no estarán disponibles para uso en la aplicación."
#. Tag: para
Modified: doc/trunk/reference/es-ES/events.po
===================================================================
--- doc/trunk/reference/es-ES/events.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/es-ES/events.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -133,11 +133,11 @@
#: events.xml:48
#, no-c-format
msgid ""
-"An observer method need not specify any event bindings—in this case it "
+"An observer method need not specify any event bindings — in this case it "
"is interested in <emphasis>all</emphasis> events of a particular type. If it "
"does specify event bindings, it is only interested in events which also have "
"those event bindings."
-msgstr "Un método de observador no necesita especificar ningún enlace de evento —en este caso está interesado en <emphasis>todos</emphasis> los eventos de un tipo determinado. Si no especifica enlaces de eventos, sólo está interesado en eventos que también tienen esos enlaces de eventos."
+msgstr "Un método de observador no necesita especificar ningún enlace de evento — en este caso está interesado en <emphasis>todos</emphasis> los eventos de un tipo determinado. Si no especifica enlaces de eventos, sólo está interesado en eventos que también tienen esos enlaces de eventos."
#. Tag: para
#: events.xml:53
Modified: doc/trunk/reference/es-ES/injection.po
===================================================================
--- doc/trunk/reference/es-ES/injection.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/es-ES/injection.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -766,13 +766,13 @@
#, no-c-format
msgid ""
"If you've been paying attention, you're probably wondering how the Web Bean "
-"manager decides which implementation—<literal>ExternalPaymentProcessor</"
-"literal> or <literal>MockPaymentProcessor</literal>—to choose. Consider "
+"manager decides which implementation — <literal>ExternalPaymentProcessor</"
+"literal> or <literal>MockPaymentProcessor</literal> — to choose. Consider "
"what happens when the manager encounters this injection point:"
msgstr ""
"Si ha prestado atención, probablemente se estará preguntando cómo escoge Web Bean "
-"la aplicación—<literal>ExternalPaymentProcessor</"
-"literal> o <literal>MockPaymentProcessor</literal>—. Piense en lo que sucede cuando el administrador encuentra este punto de inyección:"
+"la aplicación — <literal>ExternalPaymentProcessor</"
+"literal> o <literal>MockPaymentProcessor</literal> — . Piense en lo que sucede cuando el administrador encuentra este punto de inyección:"
#. Tag: programlisting
#: injection.xml:251
@@ -917,9 +917,9 @@
msgid ""
"To fix an <literal>UnsatisfiedDependencyException</literal>, simply provide "
"a Web Bean which implements the API type and has the binding types of the "
-"injection point—or enable the deployment type of a Web Bean that "
+"injection point — or enable the deployment type of a Web Bean that "
"already implements the API type and has the binding types."
-msgstr "Para corregir una <literal>UnsatisfiedDependencyException</literal>, basta con proporcionar un Web Bean que implemente el tipo API y tenga los tipos de enlace del punto de inyección—o permita el tipo de despliegue de un Web Bean que ya implemente el tipo API y tenga los tipos de enlace."
+msgstr "Para corregir una <literal>UnsatisfiedDependencyException</literal>, basta con proporcionar un Web Bean que implemente el tipo API y tenga los tipos de enlace del punto de inyección — o permita el tipo de despliegue de un Web Bean que ya implemente el tipo API y tenga los tipos de enlace."
#. Tag: para
#: injection.xml:328
@@ -1111,9 +1111,9 @@
#, no-c-format
msgid ""
"If the binding type has an annotation member, we can't use an anonymous "
-"subclass of <literal>AnnotationLiteral</literal>—instead we'll need to "
+"subclass of <literal>AnnotationLiteral</literal> — instead we'll need to "
"create a named subclass:"
-msgstr "Si el tipo de vinculación tiene un miembro de anotación, no podemos utilizar una subclase anónima de <literal>AnnotationLiteral</literal>—en su lugar, necesitaremos crear una subclase llamada:"
+msgstr "Si el tipo de vinculación tiene un miembro de anotación, no podemos utilizar una subclase anónima de <literal>AnnotationLiteral</literal> — en su lugar, necesitaremos crear una subclase llamada:"
#. Tag: programlisting
#: injection.xml:413
@@ -1210,11 +1210,11 @@
#: injection.xml:442
#, no-c-format
msgid ""
-"There are certain kinds of dependent objects—Web Beans with scope "
-"<literal>@Dependent</literal>—that need to know something about the "
+"There are certain kinds of dependent objects — Web Beans with scope "
+"<literal>@Dependent</literal> — that need to know something about the "
"object or injection point into which they are injected in order to be able "
"to do what they do. For example:"
-msgstr "Hay algunas clases de objetos—con ámbito <literal>@Dependent</literal>—que necesitan saber algo acerca del objeto o punto de inyección dentro del cual son inyectados para poder hacer lo que hacen. Por ejemplo:"
+msgstr "Hay algunas clases de objetos — con ámbito <literal>@Dependent</literal> — que necesitan saber algo acerca del objeto o punto de inyección dentro del cual son inyectados para poder hacer lo que hacen. Por ejemplo:"
#. Tag: para
#: injection.xml:448
Modified: doc/trunk/reference/es-ES/interceptors.po
===================================================================
--- doc/trunk/reference/es-ES/interceptors.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/es-ES/interceptors.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -568,10 +568,10 @@
msgid ""
"Well, fortunately, Web Beans works around this missing feature of Java. We "
"may annotate one interceptor binding type with other interceptor binding "
-"types. The interceptor bindings are transitive—any Web Bean with the "
+"types. The interceptor bindings are transitive — any Web Bean with the "
"first interceptor binding inherits the interceptor bindings declared as meta-"
"annotations."
-msgstr "Bueno, afortunadamente, Web Beans funciona en torno a esta característica de Java. Podemos anotar un interceptor de tipo de enlace con otros tipos de interceptores de enlace. Los enlaces de interceptor son transitivos—cualquier Web Bean con el primer enlace de interceptor hereda los enlaces de interceptor declarados como meta-anotaciones."
+msgstr "Bueno, afortunadamente, Web Beans funciona en torno a esta característica de Java. Podemos anotar un interceptor de tipo de enlace con otros tipos de interceptores de enlace. Los enlaces de interceptor son transitivos — cualquier Web Bean con el primer enlace de interceptor hereda los enlaces de interceptor declarados como meta-anotaciones."
#. Tag: programlisting
#: interceptors.xml:186
@@ -655,9 +655,9 @@
#: interceptors.xml:212
#, no-c-format
msgid ""
-"the interceptor ordering is non-global—it is determined by the order in "
+"the interceptor ordering is non-global — it is determined by the order in "
"which interceptors are listed at the class level."
-msgstr "la orden del interceptor es no-global—es determinada por la orden en que se listan los interceptores en el nivel de clase."
+msgstr "la orden del interceptor es no-global — es determinada por la orden en que se listan los interceptores en el nivel de clase."
#. Tag: para
#: interceptors.xml:217
Modified: doc/trunk/reference/es-ES/intro.po
===================================================================
--- doc/trunk/reference/es-ES/intro.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/es-ES/intro.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -48,11 +48,11 @@
"Furthermore, every EJB 3-style session bean is a Web Bean. Sure, the "
"JavaBeans and EJBs you've been writing every day have not been able to take "
"advantage of the new services defined by the Web Beans specification, but "
-"you'll be able to use every one of them as Web Beans—injecting them "
+"you'll be able to use every one of them as Web Beans — injecting them "
"into other Web Beans, configuring them via the Web Beans XML configuration "
-"facility, even adding interceptors and decorators to them—without "
+"facility, even adding interceptors and decorators to them — without "
"touching your existing code."
-msgstr "Con determinadas excepciones, muy especiales, toda clase de Java con un constructor que no acepte parámetros es un Web Bean. Esto incluye cada JavaBean. Además, cada sesión estilo EJB 3 es un Web Bean. Por supuesto, los JavaBeans y EJB que usted ha escrito a diario no han podido aprovechar los nuevos servicios definidos por la especificación de Web Beans, pero podrá utilizar cada uno de ellos como Web Beans—inyectándolos en otros Web Beans, configurándolos a través de los servicios de configuración, incluso agregándoles interceptores y decoradores—sin tocar su código existente."
+msgstr "Con determinadas excepciones, muy especiales, toda clase de Java con un constructor que no acepte parámetros es un Web Bean. Esto incluye cada JavaBean. Además, cada sesión estilo EJB 3 es un Web Bean. Por supuesto, los JavaBeans y EJB que usted ha escrito a diario no han podido aprovechar los nuevos servicios definidos por la especificación de Web Beans, pero podrá utilizar cada uno de ellos como Web Beans — inyectándolos en otros Web Beans, configurándolos a través de los servicios de configuración, incluso agregándoles interceptores y decoradores — sin tocar su código existente."
#. Tag: para
#: intro.xml:25
@@ -245,12 +245,12 @@
"At system initialization time, the Web Bean manager must validate that "
"exactly one Web Bean exists which satisfies each injection point. In our "
"example, if no implementation of <literal>Translator</literal> "
-"available—if the <literal>SentenceTranslator</literal> EJB was not "
-"deployed—the Web Bean manager would throw an "
+"available — if the <literal>SentenceTranslator</literal> EJB was not "
+"deployed — the Web Bean manager would throw an "
"<literal>UnsatisfiedDependencyException</literal>. If more than one "
"implementation of <literal>Translator</literal> was available, the Web Bean "
"manager would throw an <literal>AmbiguousDependencyException</literal>."
-msgstr "En el momento de inicialización, el administrador de Web Bean debe confirmar que exista exactamente un Web Bean que complete cada punto de inyección. En nuestro ejemplo, si no estaba disponible ninguna implementación de <literal>Translator</literal> —si el EJB de <literal>SentenceTranslator</literal> no estaba desplegado—el administrador de Web Bean produciría una <literal>UnsatisfiedDependencyException</literal>. Si más de una implementación de <literal>Translator</literal> estuviera disponible, el administrador de Web Bean produciría una <literal>AmbiguousDependencyException</literal>."
+msgstr "En el momento de inicialización, el administrador de Web Bean debe confirmar que exista exactamente un Web Bean que complete cada punto de inyección. En nuestro ejemplo, si no estaba disponible ninguna implementación de <literal>Translator</literal> — si el EJB de <literal>SentenceTranslator</literal> no estaba desplegado — el administrador de Web Bean produciría una <literal>UnsatisfiedDependencyException</literal>. Si más de una implementación de <literal>Translator</literal> estuviera disponible, el administrador de Web Bean produciría una <literal>AmbiguousDependencyException</literal>."
#. Tag: title
#: intro.xml:80
@@ -382,11 +382,11 @@
#, no-c-format
msgid ""
"Note that not all clients of a Web Bean are Web Beans. Other objects such as "
-"Servlets or Message-Driven Beans—which are by nature not injectable, "
-"contextual objects—may also obtain references to Web Beans by injection."
+"Servlets or Message-Driven Beans — which are by nature not injectable, "
+"contextual objects — may also obtain references to Web Beans by injection."
msgstr ""
"Observe que todos los clientes de una Web Bean son Web Beans. Otros objetos tales como "
-"Servlets o Message-Driven Beans—los cuales son por naturaleza no inyectables, objetos contextuales—también pueden obtener referencias a Web Beans por inyección."
+"Servlets o Message-Driven Beans — los cuales son por naturaleza no inyectables, objetos contextuales — también pueden obtener referencias a Web Beans por inyección."
#. Tag: para
#: intro.xml:149
@@ -765,9 +765,9 @@
#: intro.xml:289
#, no-c-format
msgid ""
-"In this case, the name defaults to <literal>shoppingCart</literal>—the "
+"In this case, the name defaults to <literal>shoppingCart</literal> — the "
"unqualified class name, with the first character changed to lowercase."
-msgstr "En este caso, el nombre predetermina al <literal>shoppingCart</literal>—el nombre de clase no calificado, con el primer caracter cambiado a minúsculas."
+msgstr "En este caso, el nombre predetermina al <literal>shoppingCart</literal> — el nombre de clase no calificado, con el primer caracter cambiado a minúsculas."
#. Tag: title
#: intro.xml:295
@@ -919,13 +919,13 @@
msgid ""
"The specification says that all EJB 3-style session and singleton beans are "
"<emphasis>enterprise</emphasis> Web Beans. Message driven beans are not Web "
-"Beans—since they are not intended to be injected into other "
-"objects—but they can take advantage of most of the functionality of Web "
+"Beans — since they are not intended to be injected into other "
+"objects — but they can take advantage of most of the functionality of Web "
"Beans, including dependency injection and interceptors."
msgstr ""
"La especificación dice que todos los beans de sesión estilo EJB 3- y singleton son "
"<emphasis>empresariales</emphasis>. Los mensajes de beans no son Web "
-"Beans—porque no están diseñados para ser inyectados en otros objetos—pero pueden aprovechar la mayoría de las funcionalidades de los Web Beans, incluyendo la inyección de dependencia y los interceptores."
+"Beans — porque no están diseñados para ser inyectados en otros objetos — pero pueden aprovechar la mayoría de las funcionalidades de los Web Beans, incluyendo la inyección de dependencia y los interceptores."
#. Tag: para
#: intro.xml:366
Modified: doc/trunk/reference/es-ES/part3.po
===================================================================
--- doc/trunk/reference/es-ES/part3.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/es-ES/part3.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -25,8 +25,8 @@
#. Tag: para
#: part3.xml:10
#, no-c-format
-msgid "You don't see string-based identifiers in Web Beans code, not because the framework is hiding them from you using clever defaulting rules—so-called \"configuration by convention\"—but because there are simply no strings there to begin with!"
-msgstr "No necesita ver los identificadores de cadena en código de Web Beans, no porque el marco los esté escondiendo del uso inteligente de las reglas—llamadas\"configuración por convención\"—sino porque simplemente ¡no hay cadenas con qué comenzar!"
+msgid "You don't see string-based identifiers in Web Beans code, not because the framework is hiding them from you using clever defaulting rules — so-called \"configuration by convention\" — but because there are simply no strings there to begin with!"
+msgstr "No necesita ver los identificadores de cadena en código de Web Beans, no porque el marco los esté escondiendo del uso inteligente de las reglas — llamadas\"configuración por convención\" — sino porque simplemente ¡no hay cadenas con qué comenzar!"
#. Tag: para
#: part3.xml:15
Modified: doc/trunk/reference/es-ES/scopescontexts.po
===================================================================
--- doc/trunk/reference/es-ES/scopescontexts.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/es-ES/scopescontexts.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -473,9 +473,9 @@
"The Web Bean manager is permitted to destroy a conversation and all state "
"held in its context at any time in order to preserve resources. A Web Bean "
"manager implementation will normally do this on the basis of some kind of "
-"timeout—though this is not required by the Web Beans specification. The "
+"timeout — though this is not required by the Web Beans specification. The "
"timeout is the period of inactivity before the conversation is destroyed."
-msgstr "Con el fin de preservar recursos, el administrador de Web Bean puede destruir una conversación y todo el estado en su contexto en cualquier momento. Una implementación del administrador de Web Bean normalmente hace esto con base en alguna clase de pausa—aunque la especificación de Web Beans no lo requiere. La pausa es el periodo de inactividad anterior a la destrucción de la conversación."
+msgstr "Con el fin de preservar recursos, el administrador de Web Bean puede destruir una conversación y todo el estado en su contexto en cualquier momento. Una implementación del administrador de Web Bean normalmente hace esto con base en alguna clase de pausa — aunque la especificación de Web Beans no lo requiere. La pausa es el periodo de inactividad anterior a la destrucción de la conversación."
#. Tag: para
#: scopescontexts.xml:208
Modified: doc/trunk/reference/fr-FR/ee.po
===================================================================
--- doc/trunk/reference/fr-FR/ee.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/fr-FR/ee.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -311,7 +311,7 @@
#, no-c-format
msgid ""
"Web Beans doesn't define any special deployment archive. You can package Web "
-"Beans in JARs, EJB-JARs or WARs—any deployment location in the "
+"Beans in JARs, EJB-JARs or WARs — any deployment location in the "
"application classpath. However, each archive that contains Web Beans must "
"include a file named <literal>web-beans.xml</literal> in the <literal>META-"
"INF</literal> or <literal>WEB-INF</literal> directory. The file may be "
Modified: doc/trunk/reference/fr-FR/events.po
===================================================================
--- doc/trunk/reference/fr-FR/events.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/fr-FR/events.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -117,7 +117,7 @@
#: events.xml:48
#, no-c-format
msgid ""
-"An observer method need not specify any event bindings—in this case it "
+"An observer method need not specify any event bindings — in this case it "
"is interested in <emphasis>all</emphasis> events of a particular type. If it "
"does specify event bindings, it is only interested in events which also have "
"those event bindings."
Modified: doc/trunk/reference/fr-FR/injection.po
===================================================================
--- doc/trunk/reference/fr-FR/injection.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/fr-FR/injection.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -653,8 +653,8 @@
#, no-c-format
msgid ""
"If you've been paying attention, you're probably wondering how the Web Bean "
-"manager decides which implementation—<literal>ExternalPaymentProcessor</"
-"literal> or <literal>MockPaymentProcessor</literal>—to choose. Consider "
+"manager decides which implementation — <literal>ExternalPaymentProcessor</"
+"literal> or <literal>MockPaymentProcessor</literal> — to choose. Consider "
"what happens when the manager encounters this injection point:"
msgstr ""
@@ -794,7 +794,7 @@
msgid ""
"To fix an <literal>UnsatisfiedDependencyException</literal>, simply provide "
"a Web Bean which implements the API type and has the binding types of the "
-"injection point—or enable the deployment type of a Web Bean that "
+"injection point — or enable the deployment type of a Web Bean that "
"already implements the API type and has the binding types."
msgstr ""
@@ -973,7 +973,7 @@
#, no-c-format
msgid ""
"If the binding type has an annotation member, we can't use an anonymous "
-"subclass of <literal>AnnotationLiteral</literal>—instead we'll need to "
+"subclass of <literal>AnnotationLiteral</literal> — instead we'll need to "
"create a named subclass:"
msgstr ""
@@ -1053,8 +1053,8 @@
#: injection.xml:442
#, no-c-format
msgid ""
-"There are certain kinds of dependent objects—Web Beans with scope "
-"<literal>@Dependent</literal>—that need to know something about the "
+"There are certain kinds of dependent objects — Web Beans with scope "
+"<literal>@Dependent</literal> — that need to know something about the "
"object or injection point into which they are injected in order to be able "
"to do what they do. For example:"
msgstr ""
Modified: doc/trunk/reference/fr-FR/interceptors.po
===================================================================
--- doc/trunk/reference/fr-FR/interceptors.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/fr-FR/interceptors.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -486,7 +486,7 @@
msgid ""
"Well, fortunately, Web Beans works around this missing feature of Java. We "
"may annotate one interceptor binding type with other interceptor binding "
-"types. The interceptor bindings are transitive—any Web Bean with the "
+"types. The interceptor bindings are transitive — any Web Bean with the "
"first interceptor binding inherits the interceptor bindings declared as meta-"
"annotations."
msgstr ""
@@ -560,7 +560,7 @@
#: interceptors.xml:212
#, no-c-format
msgid ""
-"the interceptor ordering is non-global—it is determined by the order in "
+"the interceptor ordering is non-global — it is determined by the order in "
"which interceptors are listed at the class level."
msgstr ""
Modified: doc/trunk/reference/fr-FR/intro.po
===================================================================
--- doc/trunk/reference/fr-FR/intro.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/fr-FR/intro.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -45,9 +45,9 @@
"Furthermore, every EJB 3-style session bean is a Web Bean. Sure, the "
"JavaBeans and EJBs you've been writing every day have not been able to take "
"advantage of the new services defined by the Web Beans specification, but "
-"you'll be able to use every one of them as Web Beans—injecting them "
+"you'll be able to use every one of them as Web Beans — injecting them "
"into other Web Beans, configuring them via the Web Beans XML configuration "
-"facility, even adding interceptors and decorators to them—without "
+"facility, even adding interceptors and decorators to them — without "
"touching your existing code."
msgstr ""
@@ -202,8 +202,8 @@
"At system initialization time, the Web Bean manager must validate that "
"exactly one Web Bean exists which satisfies each injection point. In our "
"example, if no implementation of <literal>Translator</literal> "
-"available—if the <literal>SentenceTranslator</literal> EJB was not "
-"deployed—the Web Bean manager would throw an "
+"available — if the <literal>SentenceTranslator</literal> EJB was not "
+"deployed — the Web Bean manager would throw an "
"<literal>UnsatisfiedDependencyException</literal>. If more than one "
"implementation of <literal>Translator</literal> was available, the Web Bean "
"manager would throw an <literal>AmbiguousDependencyException</literal>."
@@ -330,8 +330,8 @@
#, no-c-format
msgid ""
"Note that not all clients of a Web Bean are Web Beans. Other objects such as "
-"Servlets or Message-Driven Beans—which are by nature not injectable, "
-"contextual objects—may also obtain references to Web Beans by injection."
+"Servlets or Message-Driven Beans — which are by nature not injectable, "
+"contextual objects — may also obtain references to Web Beans by injection."
msgstr ""
#. Tag: para
@@ -681,7 +681,7 @@
#: intro.xml:289
#, no-c-format
msgid ""
-"In this case, the name defaults to <literal>shoppingCart</literal>—the "
+"In this case, the name defaults to <literal>shoppingCart</literal> — the "
"unqualified class name, with the first character changed to lowercase."
msgstr ""
@@ -825,8 +825,8 @@
msgid ""
"The specification says that all EJB 3-style session and singleton beans are "
"<emphasis>enterprise</emphasis> Web Beans. Message driven beans are not Web "
-"Beans—since they are not intended to be injected into other "
-"objects—but they can take advantage of most of the functionality of Web "
+"Beans — since they are not intended to be injected into other "
+"objects — but they can take advantage of most of the functionality of Web "
"Beans, including dependency injection and interceptors."
msgstr ""
Modified: doc/trunk/reference/fr-FR/part3.po
===================================================================
--- doc/trunk/reference/fr-FR/part3.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/fr-FR/part3.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -28,8 +28,8 @@
#, no-c-format
msgid ""
"You don't see string-based identifiers in Web Beans code, not because the "
-"framework is hiding them from you using clever defaulting rules—so-"
-"called \"configuration by convention\"—but because there are simply no "
+"framework is hiding them from you using clever defaulting rules — so-"
+"called \"configuration by convention\" — but because there are simply no "
"strings there to begin with!"
msgstr ""
Modified: doc/trunk/reference/fr-FR/scopescontexts.po
===================================================================
--- doc/trunk/reference/fr-FR/scopescontexts.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/fr-FR/scopescontexts.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -421,7 +421,7 @@
"The Web Bean manager is permitted to destroy a conversation and all state "
"held in its context at any time in order to preserve resources. A Web Bean "
"manager implementation will normally do this on the basis of some kind of "
-"timeout—though this is not required by the Web Beans specification. The "
+"timeout — though this is not required by the Web Beans specification. The "
"timeout is the period of inactivity before the conversation is destroyed."
msgstr ""
Modified: doc/trunk/reference/it-IT/ee.po
===================================================================
--- doc/trunk/reference/it-IT/ee.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/it-IT/ee.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -329,8 +329,8 @@
#. Tag: para
#: ee.xml:108
#, no-c-format
-msgid "Web Beans doesn't define any special deployment archive. You can package Web Beans in JARs, EJB-JARs or WARs—any deployment location in the application classpath. However, each archive that contains Web Beans must include a file named <literal>web-beans.xml</literal> in the <literal>META-INF</literal> or <literal>WEB-INF</literal> directory. The file may be empty. Web Beans deployed in archives that do not have a <literal>web-beans.xml</literal> file will not be available for use in the application."
-msgstr "Web Beans non definisce nessuno archivio speciale per il deploy. Si può impacchettare i Web Beans in JAR, EJB-JAR o WAR—qualsiasi locazione di deploy nel classpath dell'applicazione. Comunque ciascun archivio che contiene Web Beans devi includere un file chiamato <literal>web-beans.xml</literal> nella directory <literal>META-INF</literal> o <literal>WEB-INF</literal>. Il file può essere vuoto. I Web Beans collocati negli archivi che non hanno un file <literal>web-beans.xml</literal> non saranno disponibili per l'uso nell'applicazione."
+msgid "Web Beans doesn't define any special deployment archive. You can package Web Beans in JARs, EJB-JARs or WARs — any deployment location in the application classpath. However, each archive that contains Web Beans must include a file named <literal>web-beans.xml</literal> in the <literal>META-INF</literal> or <literal>WEB-INF</literal> directory. The file may be empty. Web Beans deployed in archives that do not have a <literal>web-beans.xml</literal> file will not be available for use in the application."
+msgstr "Web Beans non definisce nessuno archivio speciale per il deploy. Si può impacchettare i Web Beans in JAR, EJB-JAR o WAR — qualsiasi locazione di deploy nel classpath dell'applicazione. Comunque ciascun archivio che contiene Web Beans devi includere un file chiamato <literal>web-beans.xml</literal> nella directory <literal>META-INF</literal> o <literal>WEB-INF</literal>. Il file può essere vuoto. I Web Beans collocati negli archivi che non hanno un file <literal>web-beans.xml</literal> non saranno disponibili per l'uso nell'applicazione."
#. Tag: para
#: ee.xml:116
Modified: doc/trunk/reference/it-IT/events.po
===================================================================
--- doc/trunk/reference/it-IT/events.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/it-IT/events.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -97,8 +97,8 @@
#. Tag: para
#: events.xml:48
#, no-c-format
-msgid "An observer method need not specify any event bindings—in this case it is interested in <emphasis>all</emphasis> events of a particular type. If it does specify event bindings, it is only interested in events which also have those event bindings."
-msgstr "Un metodo osservatore non ha bisogno di specificare alcun binding di evento—in questo caso è interessato a <emphasis>tutti</emphasis> gli eventi di un particolare tipo. Se specifica dei binding di evento, è solamente interessato agli eventi che hanno anche gli stessi binding di evento."
+msgid "An observer method need not specify any event bindings — in this case it is interested in <emphasis>all</emphasis> events of a particular type. If it does specify event bindings, it is only interested in events which also have those event bindings."
+msgstr "Un metodo osservatore non ha bisogno di specificare alcun binding di evento — in questo caso è interessato a <emphasis>tutti</emphasis> gli eventi di un particolare tipo. Se specifica dei binding di evento, è solamente interessato agli eventi che hanno anche gli stessi binding di evento."
#. Tag: para
#: events.xml:53
Modified: doc/trunk/reference/it-IT/injection.po
===================================================================
--- doc/trunk/reference/it-IT/injection.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/it-IT/injection.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -6,7 +6,7 @@
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-12-19 20:26+0000\n"
-"PO-Revision-Date: 2009-01-06 15:50+0100\n"
+"PO-Revision-Date: 2009-01-20 21:28+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -673,7 +673,7 @@
#: injection.xml:246
#, no-c-format
msgid "If you've been paying attention, you're probably wondering how the Web Bean manager decides which implementation—<literal>ExternalPaymentProcessor</literal> or <literal>MockPaymentProcessor</literal>—to choose. Consider what happens when the manager encounters this injection point:"
-msgstr "Se avete prestato attenzione, vi state probabilmente chiedendo come il manager Web Bean decida quale implementatione—<literal>ExternalPaymentProcessor</literal> o <literal>MockPaymentProcessor</literal>—scegliere. Si consideri cosa succede quando il manager incontra questo punto di iniezione:"
+msgstr "Se avete prestato attenzione, vi state probabilmente chiedendo come il manager Web Bean decida quale implementazione — <literal>ExternalPaymentProcessor</literal> o <literal>MockPaymentProcessor</literal> — scegliere. Si consideri cosa succede quando il manager incontra questo punto di iniezione:"
#. Tag: programlisting
#: injection.xml:251
Modified: doc/trunk/reference/it-IT/interceptors.po
===================================================================
--- doc/trunk/reference/it-IT/interceptors.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/it-IT/interceptors.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -502,8 +502,8 @@
#. Tag: para
#: interceptors.xml:181
#, no-c-format
-msgid "Well, fortunately, Web Beans works around this missing feature of Java. We may annotate one interceptor binding type with other interceptor binding types. The interceptor bindings are transitive—any Web Bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
-msgstr "Fortunatamente Web Beans provvede a questa mancanza di Java. E' possibile annotare un tipo di interceptor binding con altri tipi di interceptor binding. Gli interceptor binding sono transitivi—qualsiasi Web Bean con il primo interceptor binding eredita gli interceptor binding dichiarati come meta-annotazioni."
+msgid "Well, fortunately, Web Beans works around this missing feature of Java. We may annotate one interceptor binding type with other interceptor binding types. The interceptor bindings are transitive — any Web Bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
+msgstr "Fortunatamente Web Beans provvede a questa mancanza di Java. E' possibile annotare un tipo di interceptor binding con altri tipi di interceptor binding. Gli interceptor binding sono transitivi — qualsiasi Web Bean con il primo interceptor binding eredita gli interceptor binding dichiarati come meta-annotazioni."
#. Tag: programlisting
#: interceptors.xml:186
@@ -574,8 +574,8 @@
#. Tag: para
#: interceptors.xml:212
#, no-c-format
-msgid "the interceptor ordering is non-global—it is determined by the order in which interceptors are listed at the class level."
-msgstr "l'ordinamento degli interceptor è non-globale—è determinata dall'ordine in cui gli interceptor sono elencati al livello di classe."
+msgid "the interceptor ordering is non-global — it is determined by the order in which interceptors are listed at the class level."
+msgstr "l'ordinamento degli interceptor è non-globale — è determinata dall'ordine in cui gli interceptor sono elencati al livello di classe."
#. Tag: para
#: interceptors.xml:217
Modified: doc/trunk/reference/it-IT/intro.po
===================================================================
--- doc/trunk/reference/it-IT/intro.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/it-IT/intro.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -35,8 +35,8 @@
#. Tag: para
#: intro.xml:15
#, no-c-format
-msgid "With certain, very special exceptions, every Java class with a constructor that accepts no parameters is a Web Bean. That includes every JavaBean. Furthermore, every EJB 3-style session bean is a Web Bean. Sure, the JavaBeans and EJBs you've been writing every day have not been able to take advantage of the new services defined by the Web Beans specification, but you'll be able to use every one of them as Web Beans—injecting them into other Web Beans, configuring them via the Web Beans XML configuration facility, even adding interceptors and decorators to them—without touching your existing code."
-msgstr "Con alcune eccezioni molto particolari, ogni classe Java con un costruttore che non accetta parametri è un Web Bean. Questo include ogni JavaBean. Inoltre, ogni session bean di stile EJB3 è un Web Bean. Sicuramente i JavaBean e gli EJB3 che si sono sempre scritti non erano in grado di sfruttare i nuovi servizi definiti dalla specifica Web Beans, ma si sarà presto in grado di usare ciascuno di essi come Web Bean—iniettandoli in altri Web Beans, configurandoli tramite strumenti di configurazione XML Web Bean, e perfino aggiungendo a loro interceptor e decoratori—senza toccare il codice esistente."
+msgid "With certain, very special exceptions, every Java class with a constructor that accepts no parameters is a Web Bean. That includes every JavaBean. Furthermore, every EJB 3-style session bean is a Web Bean. Sure, the JavaBeans and EJBs you've been writing every day have not been able to take advantage of the new services defined by the Web Beans specification, but you'll be able to use every one of them as Web Beans — injecting them into other Web Beans, configuring them via the Web Beans XML configuration facility, even adding interceptors and decorators to them — without touching your existing code."
+msgstr "Con alcune eccezioni molto particolari, ogni classe Java con un costruttore che non accetta parametri è un Web Bean. Questo include ogni JavaBean. Inoltre, ogni session bean di stile EJB3 è un Web Bean. Sicuramente i JavaBean e gli EJB3 che si sono sempre scritti non erano in grado di sfruttare i nuovi servizi definiti dalla specifica Web Beans, ma si sarà presto in grado di usare ciascuno di essi come Web Bean — iniettandoli in altri Web Beans, configurandoli tramite strumenti di configurazione XML Web Bean, e perfino aggiungendo a loro interceptor e decoratori — senza toccare il codice esistente."
#. Tag: para
#: intro.xml:25
@@ -195,8 +195,8 @@
#. Tag: para
#: intro.xml:68
#, no-c-format
-msgid "At system initialization time, the Web Bean manager must validate that exactly one Web Bean exists which satisfies each injection point. In our example, if no implementation of <literal>Translator</literal> available—if the <literal>SentenceTranslator</literal> EJB was not deployed—the Web Bean manager would throw an <literal>UnsatisfiedDependencyException</literal>. If more than one implementation of <literal>Translator</literal> was available, the Web Bean manager would throw an <literal>AmbiguousDependencyException</literal>."
-msgstr "In fase di inizializzazione del sistema, il manager Web Bean deve convalidare che esattamente un solo Web Bean esista e soddisfi ciascun punto di iniezione. Nell'esempio, se nessuna implementazione di <literal>Translator</literal> fosse disponibile—se l'EJB <literal>SentenceTranslator</literal> non venisse deployato—il manager Web Bean lancerebbe una <literal>UnsatisfiedDependencyException</literal>. Se più di un'implementazione di <literal>Translator</literal> fosse disponibile, il manager Web Bean lancerebbe una <literal>AmbiguousDependencyException</literal>."
+msgid "At system initialization time, the Web Bean manager must validate that exactly one Web Bean exists which satisfies each injection point. In our example, if no implementation of <literal>Translator</literal> available — if the <literal>SentenceTranslator</literal> EJB was not deployed — the Web Bean manager would throw an <literal>UnsatisfiedDependencyException</literal>. If more than one implementation of <literal>Translator</literal> was available, the Web Bean manager would throw an <literal>AmbiguousDependencyException</literal>."
+msgstr "In fase di inizializzazione del sistema, il manager Web Bean deve convalidare che esattamente un solo Web Bean esista e soddisfi ciascun punto di iniezione. Nell'esempio, se nessuna implementazione di <literal>Translator</literal> fosse disponibile — se l'EJB <literal>SentenceTranslator</literal> non venisse deployato — il manager Web Bean lancerebbe una <literal>UnsatisfiedDependencyException</literal>. Se più di un'implementazione di <literal>Translator</literal> fosse disponibile, il manager Web Bean lancerebbe una <literal>AmbiguousDependencyException</literal>."
#. Tag: title
#: intro.xml:80
@@ -279,8 +279,8 @@
#. Tag: para
#: intro.xml:145
#, no-c-format
-msgid "Note that not all clients of a Web Bean are Web Beans. Other objects such as Servlets or Message-Driven Beans—which are by nature not injectable, contextual objects—may also obtain references to Web Beans by injection."
-msgstr "Si noti che non tutti i client dei un Web Bean sono Web Bean. Altri oggetti come Servlet o Message-Driven Beans—che sono per natura non iniettabili, oggetti contestuali—possono pure ottenere riferimenti a Web Bean tramite iniezione."
+msgid "Note that not all clients of a Web Bean are Web Beans. Other objects such as Servlets or Message-Driven Beans — which are by nature not injectable, contextual objects — may also obtain references to Web Beans by injection."
+msgstr "Si noti che non tutti i client dei un Web Bean sono Web Bean. Altri oggetti come Servlet o Message-Driven Beans — che sono per natura non iniettabili, oggetti contestuali — possono pure ottenere riferimenti a Web Bean tramite iniezione."
# Tolto "Enough hand-waving."
#. Tag: para
@@ -588,8 +588,8 @@
#. Tag: para
#: intro.xml:289
#, no-c-format
-msgid "In this case, the name defaults to <literal>shoppingCart</literal>—the unqualified class name, with the first character changed to lowercase."
-msgstr "In questo caso il nome di default è <literal>shoppingCart</literal>—il nome della classe non qualificata, con il primo carattere messo in minuscolo."
+msgid "In this case, the name defaults to <literal>shoppingCart</literal> — the unqualified class name, with the first character changed to lowercase."
+msgstr "In questo caso il nome di default è <literal>shoppingCart</literal> — il nome della classe non qualificata, con il primo carattere messo in minuscolo."
#. Tag: title
#: intro.xml:295
@@ -713,8 +713,8 @@
#. Tag: para
#: intro.xml:360
#, no-c-format
-msgid "The specification says that all EJB 3-style session and singleton beans are <emphasis>enterprise</emphasis> Web Beans. Message driven beans are not Web Beans—since they are not intended to be injected into other objects—but they can take advantage of most of the functionality of Web Beans, including dependency injection and interceptors."
-msgstr "La specifica dice che tutti i bean di sessione stile EJB3 e quelli singleton sono Web Bean <emphasis>enterprise</emphasis>. I bean message driven non sono Web Bean—poiché non sono intesi per essere iniettati in altri oggetti—ma possono sfruttare la maggior parte della funzionalità dei Web Bean, inclusi dependency injection e interceptor."
+msgid "The specification says that all EJB 3-style session and singleton beans are <emphasis>enterprise</emphasis> Web Beans. Message driven beans are not Web Beans — since they are not intended to be injected into other objects — but they can take advantage of most of the functionality of Web Beans, including dependency injection and interceptors."
+msgstr "La specifica dice che tutti i bean di sessione stile EJB3 e quelli singleton sono Web Bean <emphasis>enterprise</emphasis>. I bean message driven non sono Web Bean — poiché non sono intesi per essere iniettati in altri oggetti — ma possono sfruttare la maggior parte della funzionalità dei Web Bean, inclusi dependency injection e interceptor."
# bean class local view = ?
#. Tag: para
Modified: doc/trunk/reference/it-IT/part3.po
===================================================================
--- doc/trunk/reference/it-IT/part3.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/it-IT/part3.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -23,8 +23,8 @@
#. Tag: para
#: part3.xml:10
#, no-c-format
-msgid "You don't see string-based identifiers in Web Beans code, not because the framework is hiding them from you using clever defaulting rules—so-called \"configuration by convention\"—but because there are simply no strings there to begin with!"
-msgstr "Non si vedono identificatori di tipo stringa nel codice basato su Web Beans, non perché il framework li nasconde usando regole intelligenti nell'assegnamento dei valori di default—la cosiddetta \"configurazione per convenzione (configuration by convention)\"—ma semplicemente perché non ci sono stringhe, tanto per cominciare!"
+msgid "You don't see string-based identifiers in Web Beans code, not because the framework is hiding them from you using clever defaulting rules — so-called \"configuration by convention\" — but because there are simply no strings there to begin with!"
+msgstr "Non si vedono identificatori di tipo stringa nel codice basato su Web Beans, non perché il framework li nasconde usando regole intelligenti nell'assegnamento dei valori di default — la cosiddetta \"configurazione per convenzione (configuration by convention)\" — ma semplicemente perché non ci sono stringhe, tanto per cominciare!"
# senza che sia necessario realizzare dei tools appositi
#. Tag: para
Modified: doc/trunk/reference/it-IT/scopescontexts.po
===================================================================
--- doc/trunk/reference/it-IT/scopescontexts.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/it-IT/scopescontexts.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -382,8 +382,8 @@
#. Tag: para
#: scopescontexts.xml:202
#, no-c-format
-msgid "The Web Bean manager is permitted to destroy a conversation and all state held in its context at any time in order to preserve resources. A Web Bean manager implementation will normally do this on the basis of some kind of timeout—though this is not required by the Web Beans specification. The timeout is the period of inactivity before the conversation is destroyed."
-msgstr "Al manager Web Bean è permesso di distruggere una conversazione e tutto lo stato mantenuto nel contesto in qualsiasi momento al fine di preservare le risorse. Un'implementazione di un manager Web Bean eseguirà questo sulla base di un qualche timeout—sebbene non sia richiesto dalla specifica Web Beans. Il timeout è il periodo di inattività prima che la conversazione venga distrutta."
+msgid "The Web Bean manager is permitted to destroy a conversation and all state held in its context at any time in order to preserve resources. A Web Bean manager implementation will normally do this on the basis of some kind of timeout — though this is not required by the Web Beans specification. The timeout is the period of inactivity before the conversation is destroyed."
+msgstr "Al manager Web Bean è permesso di distruggere una conversazione e tutto lo stato mantenuto nel contesto in qualsiasi momento al fine di preservare le risorse. Un'implementazione di un manager Web Bean eseguirà questo sulla base di un qualche timeout — sebbene non sia richiesto dalla specifica Web Beans. Il timeout è il periodo di inattività prima che la conversazione venga distrutta."
#. Tag: para
#: scopescontexts.xml:208
Modified: doc/trunk/reference/ja-JP/ee.po
===================================================================
--- doc/trunk/reference/ja-JP/ee.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/ja-JP/ee.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -311,7 +311,7 @@
#, no-c-format
msgid ""
"Web Beans doesn't define any special deployment archive. You can package Web "
-"Beans in JARs, EJB-JARs or WARs—any deployment location in the "
+"Beans in JARs, EJB-JARs or WARs — any deployment location in the "
"application classpath. However, each archive that contains Web Beans must "
"include a file named <literal>web-beans.xml</literal> in the <literal>META-"
"INF</literal> or <literal>WEB-INF</literal> directory. The file may be "
Modified: doc/trunk/reference/ja-JP/events.po
===================================================================
--- doc/trunk/reference/ja-JP/events.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/ja-JP/events.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -117,7 +117,7 @@
#: events.xml:48
#, no-c-format
msgid ""
-"An observer method need not specify any event bindings—in this case it "
+"An observer method need not specify any event bindings — in this case it "
"is interested in <emphasis>all</emphasis> events of a particular type. If it "
"does specify event bindings, it is only interested in events which also have "
"those event bindings."
Modified: doc/trunk/reference/ja-JP/injection.po
===================================================================
--- doc/trunk/reference/ja-JP/injection.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/ja-JP/injection.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -653,8 +653,8 @@
#, no-c-format
msgid ""
"If you've been paying attention, you're probably wondering how the Web Bean "
-"manager decides which implementation—<literal>ExternalPaymentProcessor</"
-"literal> or <literal>MockPaymentProcessor</literal>—to choose. Consider "
+"manager decides which implementation — <literal>ExternalPaymentProcessor</"
+"literal> or <literal>MockPaymentProcessor</literal> — to choose. Consider "
"what happens when the manager encounters this injection point:"
msgstr ""
@@ -794,7 +794,7 @@
msgid ""
"To fix an <literal>UnsatisfiedDependencyException</literal>, simply provide "
"a Web Bean which implements the API type and has the binding types of the "
-"injection point—or enable the deployment type of a Web Bean that "
+"injection point — or enable the deployment type of a Web Bean that "
"already implements the API type and has the binding types."
msgstr ""
@@ -973,7 +973,7 @@
#, no-c-format
msgid ""
"If the binding type has an annotation member, we can't use an anonymous "
-"subclass of <literal>AnnotationLiteral</literal>—instead we'll need to "
+"subclass of <literal>AnnotationLiteral</literal> — instead we'll need to "
"create a named subclass:"
msgstr ""
@@ -1053,8 +1053,8 @@
#: injection.xml:442
#, no-c-format
msgid ""
-"There are certain kinds of dependent objects—Web Beans with scope "
-"<literal>@Dependent</literal>—that need to know something about the "
+"There are certain kinds of dependent objects — Web Beans with scope "
+"<literal>@Dependent</literal> — that need to know something about the "
"object or injection point into which they are injected in order to be able "
"to do what they do. For example:"
msgstr ""
Modified: doc/trunk/reference/ja-JP/interceptors.po
===================================================================
--- doc/trunk/reference/ja-JP/interceptors.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/ja-JP/interceptors.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -486,7 +486,7 @@
msgid ""
"Well, fortunately, Web Beans works around this missing feature of Java. We "
"may annotate one interceptor binding type with other interceptor binding "
-"types. The interceptor bindings are transitive—any Web Bean with the "
+"types. The interceptor bindings are transitive — any Web Bean with the "
"first interceptor binding inherits the interceptor bindings declared as meta-"
"annotations."
msgstr ""
@@ -560,7 +560,7 @@
#: interceptors.xml:212
#, no-c-format
msgid ""
-"the interceptor ordering is non-global—it is determined by the order in "
+"the interceptor ordering is non-global — it is determined by the order in "
"which interceptors are listed at the class level."
msgstr ""
Modified: doc/trunk/reference/ja-JP/intro.po
===================================================================
--- doc/trunk/reference/ja-JP/intro.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/ja-JP/intro.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -45,9 +45,9 @@
"Furthermore, every EJB 3-style session bean is a Web Bean. Sure, the "
"JavaBeans and EJBs you've been writing every day have not been able to take "
"advantage of the new services defined by the Web Beans specification, but "
-"you'll be able to use every one of them as Web Beans—injecting them "
+"you'll be able to use every one of them as Web Beans — injecting them "
"into other Web Beans, configuring them via the Web Beans XML configuration "
-"facility, even adding interceptors and decorators to them—without "
+"facility, even adding interceptors and decorators to them — without "
"touching your existing code."
msgstr ""
@@ -202,8 +202,8 @@
"At system initialization time, the Web Bean manager must validate that "
"exactly one Web Bean exists which satisfies each injection point. In our "
"example, if no implementation of <literal>Translator</literal> "
-"available—if the <literal>SentenceTranslator</literal> EJB was not "
-"deployed—the Web Bean manager would throw an "
+"available — if the <literal>SentenceTranslator</literal> EJB was not "
+"deployed — the Web Bean manager would throw an "
"<literal>UnsatisfiedDependencyException</literal>. If more than one "
"implementation of <literal>Translator</literal> was available, the Web Bean "
"manager would throw an <literal>AmbiguousDependencyException</literal>."
@@ -330,8 +330,8 @@
#, no-c-format
msgid ""
"Note that not all clients of a Web Bean are Web Beans. Other objects such as "
-"Servlets or Message-Driven Beans—which are by nature not injectable, "
-"contextual objects—may also obtain references to Web Beans by injection."
+"Servlets or Message-Driven Beans — which are by nature not injectable, "
+"contextual objects — may also obtain references to Web Beans by injection."
msgstr ""
#. Tag: para
@@ -681,7 +681,7 @@
#: intro.xml:289
#, no-c-format
msgid ""
-"In this case, the name defaults to <literal>shoppingCart</literal>—the "
+"In this case, the name defaults to <literal>shoppingCart</literal> — the "
"unqualified class name, with the first character changed to lowercase."
msgstr ""
@@ -825,8 +825,8 @@
msgid ""
"The specification says that all EJB 3-style session and singleton beans are "
"<emphasis>enterprise</emphasis> Web Beans. Message driven beans are not Web "
-"Beans—since they are not intended to be injected into other "
-"objects—but they can take advantage of most of the functionality of Web "
+"Beans — since they are not intended to be injected into other "
+"objects — but they can take advantage of most of the functionality of Web "
"Beans, including dependency injection and interceptors."
msgstr ""
Modified: doc/trunk/reference/ja-JP/part3.po
===================================================================
--- doc/trunk/reference/ja-JP/part3.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/ja-JP/part3.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -28,8 +28,8 @@
#, no-c-format
msgid ""
"You don't see string-based identifiers in Web Beans code, not because the "
-"framework is hiding them from you using clever defaulting rules—so-"
-"called \"configuration by convention\"—but because there are simply no "
+"framework is hiding them from you using clever defaulting rules — so-"
+"called \"configuration by convention\" — but because there are simply no "
"strings there to begin with!"
msgstr ""
Modified: doc/trunk/reference/ja-JP/scopescontexts.po
===================================================================
--- doc/trunk/reference/ja-JP/scopescontexts.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/ja-JP/scopescontexts.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -421,7 +421,7 @@
"The Web Bean manager is permitted to destroy a conversation and all state "
"held in its context at any time in order to preserve resources. A Web Bean "
"manager implementation will normally do this on the basis of some kind of "
-"timeout—though this is not required by the Web Beans specification. The "
+"timeout — though this is not required by the Web Beans specification. The "
"timeout is the period of inactivity before the conversation is destroyed."
msgstr ""
Modified: doc/trunk/reference/ko-KR/ee.po
===================================================================
--- doc/trunk/reference/ko-KR/ee.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/ko-KR/ee.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -407,14 +407,14 @@
#, no-c-format
msgid ""
"Web Beans doesn't define any special deployment archive. You can package Web "
-"Beans in JARs, EJB-JARs or WARs—any deployment location in the "
+"Beans in JARs, EJB-JARs or WARs — any deployment location in the "
"application classpath. However, each archive that contains Web Beans must "
"include a file named <literal>web-beans.xml</literal> in the <literal>META-"
"INF</literal> or <literal>WEB-INF</literal> directory. The file may be "
"empty. Web Beans deployed in archives that do not have a <literal>web-beans."
"xml</literal> file will not be available for use in the application."
msgstr ""
-"Web Beans는 특정 배포 아카이브를 지정하지 않습니다. JAR, EJB-JAR 또는 WAR에 있는 Web Beans — 애플리케이션 classpath에 있는 배포 위치를 패키지화할 수 있습니다. 하지만 Web Beans이 있는 각각의 아카이브에는 <literal>META-INF</literal> 또는 <literal>WEB-INF</literal> 디렉토리에 있는 <literal>web-beans.xml</literal>라는 파일이 들어 있어야 합니다. 파일은 비어 있을 수 도 있습니다. <literal>web-beans."
+"Web Beans는 특정 배포 아카이브를 지정하지 않습니다. JAR, EJB-JAR 또는 WAR에 있는 Web Beans — 애플리케이션 classpath에 있는 배포 위치를 패키지화할 수 있습니다. 하지만 Web Beans이 있는 각각의 아카이브에는 <literal>META-INF</literal> 또는 <literal>WEB-INF</literal> 디렉토리에 있는 <literal>web-beans.xml</literal>라는 파일이 들어 있어야 합니다. 파일은 비어 있을 수 도 있습니다. <literal>web-beans."
"xml</literal> 파일이 없는 아카이브에 배포된 Web Beans는 애플리케이션에서 사용할 수 없습니다. "
#. Tag: para
Modified: doc/trunk/reference/ko-KR/events.po
===================================================================
--- doc/trunk/reference/ko-KR/events.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/ko-KR/events.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -138,11 +138,11 @@
#: events.xml:48
#, no-c-format
msgid ""
-"An observer method need not specify any event bindings—in this case it "
+"An observer method need not specify any event bindings — in this case it "
"is interested in <emphasis>all</emphasis> events of a particular type. If it "
"does specify event bindings, it is only interested in events which also have "
"those event bindings."
-msgstr "옵저버 방식은 어떤 이벤트 바인딩도 지정할 필요가 없습니다—이러한 경우 특정 유형의 <emphasis>모든</emphasis> 이벤트에 관심을 갖게 됩니다. 이벤트 바인딩을 지정하지 않을 경우, 이러한 이벤트 바인딩이 있는 이벤트에만 관심을 갖게 됩니다. "
+msgstr "옵저버 방식은 어떤 이벤트 바인딩도 지정할 필요가 없습니다 — 이러한 경우 특정 유형의 <emphasis>모든</emphasis> 이벤트에 관심을 갖게 됩니다. 이벤트 바인딩을 지정하지 않을 경우, 이러한 이벤트 바인딩이 있는 이벤트에만 관심을 갖게 됩니다. "
#. Tag: para
#: events.xml:53
Modified: doc/trunk/reference/ko-KR/injection.po
===================================================================
--- doc/trunk/reference/ko-KR/injection.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/ko-KR/injection.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -766,8 +766,8 @@
#, no-c-format
msgid ""
"If you've been paying attention, you're probably wondering how the Web Bean "
-"manager decides which implementation—<literal>ExternalPaymentProcessor</"
-"literal> or <literal>MockPaymentProcessor</literal>—to choose. Consider "
+"manager decides which implementation — <literal>ExternalPaymentProcessor</"
+"literal> or <literal>MockPaymentProcessor</literal> — to choose. Consider "
"what happens when the manager encounters this injection point:"
msgstr ""
@@ -906,7 +906,7 @@
msgid ""
"To fix an <literal>UnsatisfiedDependencyException</literal>, simply provide "
"a Web Bean which implements the API type and has the binding types of the "
-"injection point—or enable the deployment type of a Web Bean that "
+"injection point — or enable the deployment type of a Web Bean that "
"already implements the API type and has the binding types."
msgstr ""
@@ -1091,7 +1091,7 @@
#, no-c-format
msgid ""
"If the binding type has an annotation member, we can't use an anonymous "
-"subclass of <literal>AnnotationLiteral</literal>—instead we'll need to "
+"subclass of <literal>AnnotationLiteral</literal> — instead we'll need to "
"create a named subclass:"
msgstr ""
@@ -1180,8 +1180,8 @@
#: injection.xml:442
#, no-c-format
msgid ""
-"There are certain kinds of dependent objects—Web Beans with scope "
-"<literal>@Dependent</literal>—that need to know something about the "
+"There are certain kinds of dependent objects — Web Beans with scope "
+"<literal>@Dependent</literal> — that need to know something about the "
"object or injection point into which they are injected in order to be able "
"to do what they do. For example:"
msgstr ""
Modified: doc/trunk/reference/ko-KR/interceptors.po
===================================================================
--- doc/trunk/reference/ko-KR/interceptors.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/ko-KR/interceptors.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -569,10 +569,10 @@
msgid ""
"Well, fortunately, Web Beans works around this missing feature of Java. We "
"may annotate one interceptor binding type with other interceptor binding "
-"types. The interceptor bindings are transitive—any Web Bean with the "
+"types. The interceptor bindings are transitive — any Web Bean with the "
"first interceptor binding inherits the interceptor bindings declared as meta-"
"annotations."
-msgstr "다행히도 Web Beans는 이러한 생략된 Java의 기능을 해결하여 하나의 인터셉터 바인딩 유형을 다른 인터셉터 바인딩 유형과 어노테이션할 수 있습니다. 인터셉터 바인딩은 트렌젝션 가능하여 — 첫번째 인터셉터 바인딩이 있는 Web Bean은 메타 어노테이션으로 명시된 인터셉터 바인딩을 상속할 수 있습니다. "
+msgstr "다행히도 Web Beans는 이러한 생략된 Java의 기능을 해결하여 하나의 인터셉터 바인딩 유형을 다른 인터셉터 바인딩 유형과 어노테이션할 수 있습니다. 인터셉터 바인딩은 트렌젝션 가능하여 — 첫번째 인터셉터 바인딩이 있는 Web Bean은 메타 어노테이션으로 명시된 인터셉터 바인딩을 상속할 수 있습니다. "
#. Tag: programlisting
#: interceptors.xml:186
@@ -653,9 +653,9 @@
#: interceptors.xml:212
#, no-c-format
msgid ""
-"the interceptor ordering is non-global—it is determined by the order in "
+"the interceptor ordering is non-global — it is determined by the order in "
"which interceptors are listed at the class level."
-msgstr "인터셉터 순서는 비전역적입니다—이는 클래스 레벨로 열거된 인터셉터 순서에 의해 결정됩니다. "
+msgstr "인터셉터 순서는 비전역적입니다 — 이는 클래스 레벨로 열거된 인터셉터 순서에 의해 결정됩니다. "
#. Tag: para
#: interceptors.xml:217
Modified: doc/trunk/reference/ko-KR/intro.po
===================================================================
--- doc/trunk/reference/ko-KR/intro.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/ko-KR/intro.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -53,9 +53,9 @@
"Furthermore, every EJB 3-style session bean is a Web Bean. Sure, the "
"JavaBeans and EJBs you've been writing every day have not been able to take "
"advantage of the new services defined by the Web Beans specification, but "
-"you'll be able to use every one of them as Web Beans—injecting them "
+"you'll be able to use every one of them as Web Beans — injecting them "
"into other Web Beans, configuring them via the Web Beans XML configuration "
-"facility, even adding interceptors and decorators to them—without "
+"facility, even adding interceptors and decorators to them — without "
"touching your existing code."
msgstr ""
@@ -248,8 +248,8 @@
"At system initialization time, the Web Bean manager must validate that "
"exactly one Web Bean exists which satisfies each injection point. In our "
"example, if no implementation of <literal>Translator</literal> "
-"available—if the <literal>SentenceTranslator</literal> EJB was not "
-"deployed—the Web Bean manager would throw an "
+"available — if the <literal>SentenceTranslator</literal> EJB was not "
+"deployed — the Web Bean manager would throw an "
"<literal>UnsatisfiedDependencyException</literal>. If more than one "
"implementation of <literal>Translator</literal> was available, the Web Bean "
"manager would throw an <literal>AmbiguousDependencyException</literal>."
@@ -375,8 +375,8 @@
#, no-c-format
msgid ""
"Note that not all clients of a Web Bean are Web Beans. Other objects such as "
-"Servlets or Message-Driven Beans—which are by nature not injectable, "
-"contextual objects—may also obtain references to Web Beans by injection."
+"Servlets or Message-Driven Beans — which are by nature not injectable, "
+"contextual objects — may also obtain references to Web Beans by injection."
msgstr ""
#. Tag: para
@@ -743,7 +743,7 @@
#: intro.xml:289
#, no-c-format
msgid ""
-"In this case, the name defaults to <literal>shoppingCart</literal>—the "
+"In this case, the name defaults to <literal>shoppingCart</literal> — the "
"unqualified class name, with the first character changed to lowercase."
msgstr ""
@@ -892,8 +892,8 @@
msgid ""
"The specification says that all EJB 3-style session and singleton beans are "
"<emphasis>enterprise</emphasis> Web Beans. Message driven beans are not Web "
-"Beans—since they are not intended to be injected into other "
-"objects—but they can take advantage of most of the functionality of Web "
+"Beans — since they are not intended to be injected into other "
+"objects — but they can take advantage of most of the functionality of Web "
"Beans, including dependency injection and interceptors."
msgstr ""
Modified: doc/trunk/reference/ko-KR/part3.po
===================================================================
--- doc/trunk/reference/ko-KR/part3.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/ko-KR/part3.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -26,8 +26,8 @@
#. Tag: para
#: part3.xml:10
#, no-c-format
-msgid "You don't see string-based identifiers in Web Beans code, not because the framework is hiding them from you using clever defaulting rules—so-called \"configuration by convention\"—but because there are simply no strings there to begin with!"
-msgstr "Web Beans 코드에서 문자열 기반 식별자를 보실 수 없습니다. 그 이유는 프레임워크가 —\"관례에 의한 설정\"이라고 부르는— 기본값 규칙을 사용하여 이를 숨기려하기 때문이 아니라 시작할 수 있는 문자열이 없기 때문입니다! "
+msgid "You don't see string-based identifiers in Web Beans code, not because the framework is hiding them from you using clever defaulting rules — so-called \"configuration by convention\" — but because there are simply no strings there to begin with!"
+msgstr "Web Beans 코드에서 문자열 기반 식별자를 보실 수 없습니다. 그 이유는 프레임워크가 — \"관례에 의한 설정\"이라고 부르는 — 기본값 규칙을 사용하여 이를 숨기려하기 때문이 아니라 시작할 수 있는 문자열이 없기 때문입니다! "
#. Tag: para
#: part3.xml:15
Modified: doc/trunk/reference/ko-KR/scopescontexts.po
===================================================================
--- doc/trunk/reference/ko-KR/scopescontexts.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/ko-KR/scopescontexts.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -463,7 +463,7 @@
"The Web Bean manager is permitted to destroy a conversation and all state "
"held in its context at any time in order to preserve resources. A Web Bean "
"manager implementation will normally do this on the basis of some kind of "
-"timeout—though this is not required by the Web Beans specification. The "
+"timeout — though this is not required by the Web Beans specification. The "
"timeout is the period of inactivity before the conversation is destroyed."
msgstr ""
Modified: doc/trunk/reference/pt-BR/ee.po
===================================================================
--- doc/trunk/reference/pt-BR/ee.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/pt-BR/ee.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -311,7 +311,7 @@
#, no-c-format
msgid ""
"Web Beans doesn't define any special deployment archive. You can package Web "
-"Beans in JARs, EJB-JARs or WARs—any deployment location in the "
+"Beans in JARs, EJB-JARs or WARs — any deployment location in the "
"application classpath. However, each archive that contains Web Beans must "
"include a file named <literal>web-beans.xml</literal> in the <literal>META-"
"INF</literal> or <literal>WEB-INF</literal> directory. The file may be "
Modified: doc/trunk/reference/pt-BR/events.po
===================================================================
--- doc/trunk/reference/pt-BR/events.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/pt-BR/events.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -117,7 +117,7 @@
#: events.xml:48
#, no-c-format
msgid ""
-"An observer method need not specify any event bindings—in this case it "
+"An observer method need not specify any event bindings — in this case it "
"is interested in <emphasis>all</emphasis> events of a particular type. If it "
"does specify event bindings, it is only interested in events which also have "
"those event bindings."
Modified: doc/trunk/reference/pt-BR/injection.po
===================================================================
--- doc/trunk/reference/pt-BR/injection.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/pt-BR/injection.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -653,8 +653,8 @@
#, no-c-format
msgid ""
"If you've been paying attention, you're probably wondering how the Web Bean "
-"manager decides which implementation—<literal>ExternalPaymentProcessor</"
-"literal> or <literal>MockPaymentProcessor</literal>—to choose. Consider "
+"manager decides which implementation — <literal>ExternalPaymentProcessor</"
+"literal> or <literal>MockPaymentProcessor</literal> — to choose. Consider "
"what happens when the manager encounters this injection point:"
msgstr ""
@@ -794,7 +794,7 @@
msgid ""
"To fix an <literal>UnsatisfiedDependencyException</literal>, simply provide "
"a Web Bean which implements the API type and has the binding types of the "
-"injection point—or enable the deployment type of a Web Bean that "
+"injection point — or enable the deployment type of a Web Bean that "
"already implements the API type and has the binding types."
msgstr ""
@@ -973,7 +973,7 @@
#, no-c-format
msgid ""
"If the binding type has an annotation member, we can't use an anonymous "
-"subclass of <literal>AnnotationLiteral</literal>—instead we'll need to "
+"subclass of <literal>AnnotationLiteral</literal> — instead we'll need to "
"create a named subclass:"
msgstr ""
@@ -1053,8 +1053,8 @@
#: injection.xml:442
#, no-c-format
msgid ""
-"There are certain kinds of dependent objects—Web Beans with scope "
-"<literal>@Dependent</literal>—that need to know something about the "
+"There are certain kinds of dependent objects — Web Beans with scope "
+"<literal>@Dependent</literal> — that need to know something about the "
"object or injection point into which they are injected in order to be able "
"to do what they do. For example:"
msgstr ""
Modified: doc/trunk/reference/pt-BR/interceptors.po
===================================================================
--- doc/trunk/reference/pt-BR/interceptors.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/pt-BR/interceptors.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -486,7 +486,7 @@
msgid ""
"Well, fortunately, Web Beans works around this missing feature of Java. We "
"may annotate one interceptor binding type with other interceptor binding "
-"types. The interceptor bindings are transitive—any Web Bean with the "
+"types. The interceptor bindings are transitive — any Web Bean with the "
"first interceptor binding inherits the interceptor bindings declared as meta-"
"annotations."
msgstr ""
@@ -560,7 +560,7 @@
#: interceptors.xml:212
#, no-c-format
msgid ""
-"the interceptor ordering is non-global—it is determined by the order in "
+"the interceptor ordering is non-global — it is determined by the order in "
"which interceptors are listed at the class level."
msgstr ""
Modified: doc/trunk/reference/pt-BR/intro.po
===================================================================
--- doc/trunk/reference/pt-BR/intro.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/pt-BR/intro.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -45,9 +45,9 @@
"Furthermore, every EJB 3-style session bean is a Web Bean. Sure, the "
"JavaBeans and EJBs you've been writing every day have not been able to take "
"advantage of the new services defined by the Web Beans specification, but "
-"you'll be able to use every one of them as Web Beans—injecting them "
+"you'll be able to use every one of them as Web Beans — injecting them "
"into other Web Beans, configuring them via the Web Beans XML configuration "
-"facility, even adding interceptors and decorators to them—without "
+"facility, even adding interceptors and decorators to them — without "
"touching your existing code."
msgstr ""
@@ -202,8 +202,8 @@
"At system initialization time, the Web Bean manager must validate that "
"exactly one Web Bean exists which satisfies each injection point. In our "
"example, if no implementation of <literal>Translator</literal> "
-"available—if the <literal>SentenceTranslator</literal> EJB was not "
-"deployed—the Web Bean manager would throw an "
+"available — if the <literal>SentenceTranslator</literal> EJB was not "
+"deployed — the Web Bean manager would throw an "
"<literal>UnsatisfiedDependencyException</literal>. If more than one "
"implementation of <literal>Translator</literal> was available, the Web Bean "
"manager would throw an <literal>AmbiguousDependencyException</literal>."
@@ -330,8 +330,8 @@
#, no-c-format
msgid ""
"Note that not all clients of a Web Bean are Web Beans. Other objects such as "
-"Servlets or Message-Driven Beans—which are by nature not injectable, "
-"contextual objects—may also obtain references to Web Beans by injection."
+"Servlets or Message-Driven Beans — which are by nature not injectable, "
+"contextual objects — may also obtain references to Web Beans by injection."
msgstr ""
#. Tag: para
@@ -681,7 +681,7 @@
#: intro.xml:289
#, no-c-format
msgid ""
-"In this case, the name defaults to <literal>shoppingCart</literal>—the "
+"In this case, the name defaults to <literal>shoppingCart</literal> — the "
"unqualified class name, with the first character changed to lowercase."
msgstr ""
@@ -825,8 +825,8 @@
msgid ""
"The specification says that all EJB 3-style session and singleton beans are "
"<emphasis>enterprise</emphasis> Web Beans. Message driven beans are not Web "
-"Beans—since they are not intended to be injected into other "
-"objects—but they can take advantage of most of the functionality of Web "
+"Beans — since they are not intended to be injected into other "
+"objects — but they can take advantage of most of the functionality of Web "
"Beans, including dependency injection and interceptors."
msgstr ""
Modified: doc/trunk/reference/pt-BR/part3.po
===================================================================
--- doc/trunk/reference/pt-BR/part3.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/pt-BR/part3.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -28,8 +28,8 @@
#, no-c-format
msgid ""
"You don't see string-based identifiers in Web Beans code, not because the "
-"framework is hiding them from you using clever defaulting rules—so-"
-"called \"configuration by convention\"—but because there are simply no "
+"framework is hiding them from you using clever defaulting rules — so-"
+"called \"configuration by convention\" — but because there are simply no "
"strings there to begin with!"
msgstr ""
Modified: doc/trunk/reference/pt-BR/scopescontexts.po
===================================================================
--- doc/trunk/reference/pt-BR/scopescontexts.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/pt-BR/scopescontexts.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -421,7 +421,7 @@
"The Web Bean manager is permitted to destroy a conversation and all state "
"held in its context at any time in order to preserve resources. A Web Bean "
"manager implementation will normally do this on the basis of some kind of "
-"timeout—though this is not required by the Web Beans specification. The "
+"timeout — though this is not required by the Web Beans specification. The "
"timeout is the period of inactivity before the conversation is destroyed."
msgstr ""
Modified: doc/trunk/reference/zh-CN/ee.po
===================================================================
--- doc/trunk/reference/zh-CN/ee.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/zh-CN/ee.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -311,7 +311,7 @@
#, no-c-format
msgid ""
"Web Beans doesn't define any special deployment archive. You can package Web "
-"Beans in JARs, EJB-JARs or WARs—any deployment location in the "
+"Beans in JARs, EJB-JARs or WARs — any deployment location in the "
"application classpath. However, each archive that contains Web Beans must "
"include a file named <literal>web-beans.xml</literal> in the <literal>META-"
"INF</literal> or <literal>WEB-INF</literal> directory. The file may be "
Modified: doc/trunk/reference/zh-CN/events.po
===================================================================
--- doc/trunk/reference/zh-CN/events.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/zh-CN/events.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -117,7 +117,7 @@
#: events.xml:48
#, no-c-format
msgid ""
-"An observer method need not specify any event bindings—in this case it "
+"An observer method need not specify any event bindings — in this case it "
"is interested in <emphasis>all</emphasis> events of a particular type. If it "
"does specify event bindings, it is only interested in events which also have "
"those event bindings."
Modified: doc/trunk/reference/zh-CN/injection.po
===================================================================
--- doc/trunk/reference/zh-CN/injection.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/zh-CN/injection.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -653,8 +653,8 @@
#, no-c-format
msgid ""
"If you've been paying attention, you're probably wondering how the Web Bean "
-"manager decides which implementation—<literal>ExternalPaymentProcessor</"
-"literal> or <literal>MockPaymentProcessor</literal>—to choose. Consider "
+"manager decides which implementation — <literal>ExternalPaymentProcessor</"
+"literal> or <literal>MockPaymentProcessor</literal> — to choose. Consider "
"what happens when the manager encounters this injection point:"
msgstr ""
@@ -794,7 +794,7 @@
msgid ""
"To fix an <literal>UnsatisfiedDependencyException</literal>, simply provide "
"a Web Bean which implements the API type and has the binding types of the "
-"injection point—or enable the deployment type of a Web Bean that "
+"injection point — or enable the deployment type of a Web Bean that "
"already implements the API type and has the binding types."
msgstr ""
@@ -973,7 +973,7 @@
#, no-c-format
msgid ""
"If the binding type has an annotation member, we can't use an anonymous "
-"subclass of <literal>AnnotationLiteral</literal>—instead we'll need to "
+"subclass of <literal>AnnotationLiteral</literal> — instead we'll need to "
"create a named subclass:"
msgstr ""
@@ -1053,8 +1053,8 @@
#: injection.xml:442
#, no-c-format
msgid ""
-"There are certain kinds of dependent objects—Web Beans with scope "
-"<literal>@Dependent</literal>—that need to know something about the "
+"There are certain kinds of dependent objects — Web Beans with scope "
+"<literal>@Dependent</literal> — that need to know something about the "
"object or injection point into which they are injected in order to be able "
"to do what they do. For example:"
msgstr ""
Modified: doc/trunk/reference/zh-CN/interceptors.po
===================================================================
--- doc/trunk/reference/zh-CN/interceptors.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/zh-CN/interceptors.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -486,7 +486,7 @@
msgid ""
"Well, fortunately, Web Beans works around this missing feature of Java. We "
"may annotate one interceptor binding type with other interceptor binding "
-"types. The interceptor bindings are transitive—any Web Bean with the "
+"types. The interceptor bindings are transitive — any Web Bean with the "
"first interceptor binding inherits the interceptor bindings declared as meta-"
"annotations."
msgstr ""
@@ -560,7 +560,7 @@
#: interceptors.xml:212
#, no-c-format
msgid ""
-"the interceptor ordering is non-global—it is determined by the order in "
+"the interceptor ordering is non-global — it is determined by the order in "
"which interceptors are listed at the class level."
msgstr ""
Modified: doc/trunk/reference/zh-CN/intro.po
===================================================================
--- doc/trunk/reference/zh-CN/intro.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/zh-CN/intro.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -34,7 +34,7 @@
#. Tag: para
#: intro.xml:15
#, no-c-format
-msgid "With certain, very special exceptions, every Java class with a constructor that accepts no parameters is a Web Bean. That includes every JavaBean. Furthermore, every EJB 3-style session bean is a Web Bean. Sure, the JavaBeans and EJBs you've been writing every day have not been able to take advantage of the new services defined by the Web Beans specification, but you'll be able to use every one of them as Web Beans—injecting them into other Web Beans, configuring them via the Web Beans XML configuration facility, even adding interceptors and decorators to them—without touching your existing code."
+msgid "With certain, very special exceptions, every Java class with a constructor that accepts no parameters is a Web Bean. That includes every JavaBean. Furthermore, every EJB 3-style session bean is a Web Bean. Sure, the JavaBeans and EJBs you've been writing every day have not been able to take advantage of the new services defined by the Web Beans specification, but you'll be able to use every one of them as Web Beans — injecting them into other Web Beans, configuring them via the Web Beans XML configuration facility, even adding interceptors and decorators to them — without touching your existing code."
msgstr "除非特殊情况，每个具有一个非参构造器的Java类都可以是一个Web Bean。这包括了每个JavaBean, 并且每个EJB3的会话Bean都是一个Web Bean。当然，你每天已经写过的JavaBean和EJB无法使用Web Beans规范定义的新服务，但是你能够通过Web Beans的XML配置将这些组件配置为Web Bean，然后将其注入到其他Web Bean中。你甚至可以不用修改已有代码就可以为其添加拦截器和装饰器。"
#. Tag: para
@@ -194,8 +194,8 @@
#. Tag: para
#: intro.xml:68
#, no-c-format
-msgid "At system initialization time, the Web Bean manager must validate that exactly one Web Bean exists which satisfies each injection point. In our example, if no implementation of <literal>Translator</literal> available—if the <literal>SentenceTranslator</literal> EJB was not deployed—the Web Bean manager would throw an <literal>UnsatisfiedDependencyException</literal>. If more than one implementation of <literal>Translator</literal> was available, the Web Bean manager would throw an <literal>AmbiguousDependencyException</literal>."
-msgstr "在系统初始化的时候，Web Bean管理器必须验证只存在一个Web Bean能够满足每个注入点。在我们的例子中，如果没有<literal>Translator</literal>实现—如果<literal>SentenceTranslator</literal> EJB没有被部署—Web Bean管理器将会抛出一个<literal>UnsatisfiedDependencyException</literal>异常。如果多于一个<literal>Translator</literal>实现，Web Bean管理器将会抛出一个<literal>AmbiguousDependencyException</literal>异常。"
+msgid "At system initialization time, the Web Bean manager must validate that exactly one Web Bean exists which satisfies each injection point. In our example, if no implementation of <literal>Translator</literal> available — if the <literal>SentenceTranslator</literal> EJB was not deployed — the Web Bean manager would throw an <literal>UnsatisfiedDependencyException</literal>. If more than one implementation of <literal>Translator</literal> was available, the Web Bean manager would throw an <literal>AmbiguousDependencyException</literal>."
+msgstr "在系统初始化的时候，Web Bean管理器必须验证只存在一个Web Bean能够满足每个注入点。在我们的例子中，如果没有<literal>Translator</literal>实现 — 如果<literal>SentenceTranslator</literal> EJB没有被部署 — Web Bean管理器将会抛出一个<literal>UnsatisfiedDependencyException</literal>异常。如果多于一个<literal>Translator</literal>实现，Web Bean管理器将会抛出一个<literal>AmbiguousDependencyException</literal>异常。"
#. Tag: title
#: intro.xml:80
@@ -278,8 +278,8 @@
#. Tag: para
#: intro.xml:145
#, no-c-format
-msgid "Note that not all clients of a Web Bean are Web Beans. Other objects such as Servlets or Message-Driven Beans—which are by nature not injectable, contextual objects—may also obtain references to Web Beans by injection."
-msgstr "需要注意的是并非所有的Web Bean的客户端都是Web Bean。其他对象诸如Servlet或者消息驱动Bean#151;天生不可注入的, 具备上下文的对象—也可以通过注入获得Web Bean的引用。"
+msgid "Note that not all clients of a Web Bean are Web Beans. Other objects such as Servlets or Message-Driven Beans — which are by nature not injectable, contextual objects — may also obtain references to Web Beans by injection."
+msgstr "需要注意的是并非所有的Web Bean的客户端都是Web Bean。其他对象诸如Servlet或者消息驱动Bean#151;天生不可注入的, 具备上下文的对象 — 也可以通过注入获得Web Bean的引用。"
#. Tag: para
#: intro.xml:149
@@ -584,8 +584,8 @@
#. Tag: para
#: intro.xml:289
#, no-c-format
-msgid "In this case, the name defaults to <literal>shoppingCart</literal>—the unqualified class name, with the first character changed to lowercase."
-msgstr "在这种情况下，Web Bean的名字默认为<literal>shoppingCart</literal>—非完整的类名，首字母改为小写"
+msgid "In this case, the name defaults to <literal>shoppingCart</literal> — the unqualified class name, with the first character changed to lowercase."
+msgstr "在这种情况下，Web Bean的名字默认为<literal>shoppingCart</literal> — 非完整的类名，首字母改为小写"
#. Tag: title
#: intro.xml:295
@@ -708,8 +708,8 @@
#. Tag: para
#: intro.xml:360
#, no-c-format
-msgid "The specification says that all EJB 3-style session and singleton beans are <emphasis>enterprise</emphasis> Web Beans. Message driven beans are not Web Beans—since they are not intended to be injected into other objects—but they can take advantage of most of the functionality of Web Beans, including dependency injection and interceptors."
-msgstr "规范指出所有EJB3类型的会话Bean或者单例Bean都是<emphasis>企业级</emphasis>Web Bean。消息驱动Bean不是Web Beans—因为它们不能被注入到其他对象中#151;但是它们可以使用大部分Web Bean的功能，包括依赖注入和拦截器。"
+msgid "The specification says that all EJB 3-style session and singleton beans are <emphasis>enterprise</emphasis> Web Beans. Message driven beans are not Web Beans — since they are not intended to be injected into other objects — but they can take advantage of most of the functionality of Web Beans, including dependency injection and interceptors."
+msgstr "规范指出所有EJB3类型的会话Bean或者单例Bean都是<emphasis>企业级</emphasis>Web Bean。消息驱动Bean不是Web Beans — 因为它们不能被注入到其他对象中#151;但是它们可以使用大部分Web Bean的功能，包括依赖注入和拦截器。"
#. Tag: para
#: intro.xml:366
Modified: doc/trunk/reference/zh-CN/part3.po
===================================================================
--- doc/trunk/reference/zh-CN/part3.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/zh-CN/part3.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -22,8 +22,8 @@
#. Tag: para
#: part3.xml:10
#, no-c-format
-msgid "You don't see string-based identifiers in Web Beans code, not because the framework is hiding them from you using clever defaulting rules—so-called \"configuration by convention\"—but because there are simply no strings there to begin with!"
-msgstr "在Web Bean代码中，你不会看到基于字符串的标识符。这不是因为这个框架使用智能默认规则—也叫\"按惯例配置\"—将它们隐藏起来，这是因为从开始就没有任何字符串！"
+msgid "You don't see string-based identifiers in Web Beans code, not because the framework is hiding them from you using clever defaulting rules — so-called \"configuration by convention\" — but because there are simply no strings there to begin with!"
+msgstr "在Web Bean代码中，你不会看到基于字符串的标识符。这不是因为这个框架使用智能默认规则 — 也叫\"按惯例配置\" — 将它们隐藏起来，这是因为从开始就没有任何字符串！"
#. Tag: para
#: part3.xml:15
Modified: doc/trunk/reference/zh-CN/scopescontexts.po
===================================================================
--- doc/trunk/reference/zh-CN/scopescontexts.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/zh-CN/scopescontexts.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -421,7 +421,7 @@
"The Web Bean manager is permitted to destroy a conversation and all state "
"held in its context at any time in order to preserve resources. A Web Bean "
"manager implementation will normally do this on the basis of some kind of "
-"timeout—though this is not required by the Web Beans specification. The "
+"timeout — though this is not required by the Web Beans specification. The "
"timeout is the period of inactivity before the conversation is destroyed."
msgstr ""
Modified: doc/trunk/reference/zh-TW/ee.po
===================================================================
--- doc/trunk/reference/zh-TW/ee.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/zh-TW/ee.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -399,13 +399,13 @@
#, no-c-format
msgid ""
"Web Beans doesn't define any special deployment archive. You can package Web "
-"Beans in JARs, EJB-JARs or WARs—any deployment location in the "
+"Beans in JARs, EJB-JARs or WARs — any deployment location in the "
"application classpath. However, each archive that contains Web Beans must "
"include a file named <literal>web-beans.xml</literal> in the <literal>META-"
"INF</literal> or <literal>WEB-INF</literal> directory. The file may be "
"empty. Web Beans deployed in archives that do not have a <literal>web-beans."
"xml</literal> file will not be available for use in the application."
-msgstr "Web Bean 不會定義任何特殊的建置 archive。您可將 Web Bean 封裝在 JARs、EJB-JARs 或是 WARs— 中，應用程式 classpath 中的任何建置位置上。不過，各個包含著 Web Bean 的 archive 在 <literal>META-INF</literal> 或是 <literal>WEB-INF</literal> 目錄中都必須包含著一個稱為 <literal>web-beans.xml</literal> 的檔案。該檔案能是空的。建置於一個沒有 <literal>web-beans.xml</literal> 檔案的 archive 中的 Web Bean 將無法使用於應用程式中。"
+msgstr "Web Bean 不會定義任何特殊的建置 archive。您可將 Web Bean 封裝在 JARs、EJB-JARs 或是 WARs — 中，應用程式 classpath 中的任何建置位置上。不過，各個包含著 Web Bean 的 archive 在 <literal>META-INF</literal> 或是 <literal>WEB-INF</literal> 目錄中都必須包含著一個稱為 <literal>web-beans.xml</literal> 的檔案。該檔案能是空的。建置於一個沒有 <literal>web-beans.xml</literal> 檔案的 archive 中的 Web Bean 將無法使用於應用程式中。"
#. Tag: para
#: ee.xml:116
Modified: doc/trunk/reference/zh-TW/events.po
===================================================================
--- doc/trunk/reference/zh-TW/events.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/zh-TW/events.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -128,11 +128,11 @@
#: events.xml:48
#, no-c-format
msgid ""
-"An observer method need not specify any event bindings—in this case it "
+"An observer method need not specify any event bindings — in this case it "
"is interested in <emphasis>all</emphasis> events of a particular type. If it "
"does specify event bindings, it is only interested in events which also have "
"those event bindings."
-msgstr "一個 observer method 不需要指定任何的事件綁定—在此情況下它會專注於特定 type 的<emphasis>所有</emphasis>事件。若它指定了事件綁定的話，它就只會專注於也具有這些事件綁定的事件。"
+msgstr "一個 observer method 不需要指定任何的事件綁定 — 在此情況下它會專注於特定 type 的<emphasis>所有</emphasis>事件。若它指定了事件綁定的話，它就只會專注於也具有這些事件綁定的事件。"
#. Tag: para
#: events.xml:53
Modified: doc/trunk/reference/zh-TW/injection.po
===================================================================
--- doc/trunk/reference/zh-TW/injection.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/zh-TW/injection.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -760,12 +760,12 @@
#, no-c-format
msgid ""
"If you've been paying attention, you're probably wondering how the Web Bean "
-"manager decides which implementation—<literal>ExternalPaymentProcessor</"
-"literal> or <literal>MockPaymentProcessor</literal>—to choose. Consider "
+"manager decides which implementation — <literal>ExternalPaymentProcessor</"
+"literal> or <literal>MockPaymentProcessor</literal> — to choose. Consider "
"what happens when the manager encounters this injection point:"
msgstr ""
-"若您有在細心注意的話，您應該會疑惑 Web Bean 管理員如何決定哪個實做—<literal>ExternalPaymentProcessor</"
-"literal> 和 <literal>MockPaymentProcessor</literal>—中選擇哪一個。請思考當管理員遇上了這個注入點時會如何："
+"若您有在細心注意的話，您應該會疑惑 Web Bean 管理員如何決定哪個實做 — <literal>ExternalPaymentProcessor</"
+"literal> 和 <literal>MockPaymentProcessor</literal> — 中選擇哪一個。請思考當管理員遇上了這個注入點時會如何："
#. Tag: programlisting
#: injection.xml:251
@@ -902,9 +902,9 @@
msgid ""
"To fix an <literal>UnsatisfiedDependencyException</literal>, simply provide "
"a Web Bean which implements the API type and has the binding types of the "
-"injection point—or enable the deployment type of a Web Bean that "
+"injection point — or enable the deployment type of a Web Bean that "
"already implements the API type and has the binding types."
-msgstr "若要修正一項 <literal>UnsatisfiedDependencyException</literal>，只要提供一個實做 API 類型並且擁有注入點的綁定類型的 Web Bean 即可—或是啟用一個已實做 API 類型並且擁有綁定類型的 Web Bean 的 deployment type 即可。"
+msgstr "若要修正一項 <literal>UnsatisfiedDependencyException</literal>，只要提供一個實做 API 類型並且擁有注入點的綁定類型的 Web Bean 即可 — 或是啟用一個已實做 API 類型並且擁有綁定類型的 Web Bean 的 deployment type 即可。"
#. Tag: para
#: injection.xml:328
@@ -1087,9 +1087,9 @@
#, no-c-format
msgid ""
"If the binding type has an annotation member, we can't use an anonymous "
-"subclass of <literal>AnnotationLiteral</literal>—instead we'll need to "
+"subclass of <literal>AnnotationLiteral</literal> — instead we'll need to "
"create a named subclass:"
-msgstr "若綁定類型有個標記成員，我們便無法使用 <literal>AnnotationLiteral</literal> 的一個匿名 subclass—我們需要建立一個有命名的 subclass："
+msgstr "若綁定類型有個標記成員，我們便無法使用 <literal>AnnotationLiteral</literal> 的一個匿名 subclass — 我們需要建立一個有命名的 subclass："
#. Tag: programlisting
#: injection.xml:413
@@ -1176,11 +1176,11 @@
#: injection.xml:442
#, no-c-format
msgid ""
-"There are certain kinds of dependent objects—Web Beans with scope "
-"<literal>@Dependent</literal>—that need to know something about the "
+"There are certain kinds of dependent objects — Web Beans with scope "
+"<literal>@Dependent</literal> — that need to know something about the "
"object or injection point into which they are injected in order to be able "
"to do what they do. For example:"
-msgstr "有幾種特定相依物件—含有 <literal>@Dependent</literal> 這個 scope 的 Web Bean—需要知道有關於物件或是它們被注入的注入點相關資訊才能進行它們本應進行的工作。比方說："
+msgstr "有幾種特定相依物件 — 含有 <literal>@Dependent</literal> 這個 scope 的 Web Bean — 需要知道有關於物件或是它們被注入的注入點相關資訊才能進行它們本應進行的工作。比方說："
#. Tag: para
#: injection.xml:448
Modified: doc/trunk/reference/zh-TW/interceptors.po
===================================================================
--- doc/trunk/reference/zh-TW/interceptors.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/zh-TW/interceptors.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -566,10 +566,10 @@
msgid ""
"Well, fortunately, Web Beans works around this missing feature of Java. We "
"may annotate one interceptor binding type with other interceptor binding "
-"types. The interceptor bindings are transitive—any Web Bean with the "
+"types. The interceptor bindings are transitive — any Web Bean with the "
"first interceptor binding inherits the interceptor bindings declared as meta-"
"annotations."
-msgstr "幸運的是，Web Bean 有方法來解決 Java 所缺少的這項功能上的問題。我們可利用其它攔截器綁定類型來標記某個攔截器綁定類型。攔截器綁定為可轉變的—任何含有第一個攔截器綁定的 Web Bean 都會繼承宣告為 meta-annotation 的攔截器綁定。"
+msgstr "幸運的是，Web Bean 有方法來解決 Java 所缺少的這項功能上的問題。我們可利用其它攔截器綁定類型來標記某個攔截器綁定類型。攔截器綁定為可轉變的 — 任何含有第一個攔截器綁定的 Web Bean 都會繼承宣告為 meta-annotation 的攔截器綁定。"
#. Tag: programlisting
#: interceptors.xml:186
@@ -650,9 +650,9 @@
#: interceptors.xml:212
#, no-c-format
msgid ""
-"the interceptor ordering is non-global—it is determined by the order in "
+"the interceptor ordering is non-global — it is determined by the order in "
"which interceptors are listed at the class level."
-msgstr "攔截器的順序會是非全域性的—會由攔截器被列於 class 層級的順序來取決。"
+msgstr "攔截器的順序會是非全域性的 — 會由攔截器被列於 class 層級的順序來取決。"
#. Tag: para
#: interceptors.xml:217
Modified: doc/trunk/reference/zh-TW/intro.po
===================================================================
--- doc/trunk/reference/zh-TW/intro.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/zh-TW/intro.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -48,11 +48,11 @@
"Furthermore, every EJB 3-style session bean is a Web Bean. Sure, the "
"JavaBeans and EJBs you've been writing every day have not been able to take "
"advantage of the new services defined by the Web Beans specification, but "
-"you'll be able to use every one of them as Web Beans—injecting them "
+"you'll be able to use every one of them as Web Beans — injecting them "
"into other Web Beans, configuring them via the Web Beans XML configuration "
-"facility, even adding interceptors and decorators to them—without "
+"facility, even adding interceptors and decorators to them — without "
"touching your existing code."
-msgstr "我們能夠很明確地告訴您，在絕大部分的情況下，所有含有不接受參數的 constructor 的 java class 都是個 Web Bean。這包含了所有的 JavaBean。另外，所有 EJB 3-style 的 session bean 也都屬於 Web Bean。當然，您先前所編寫的 JavaBean 和 EJB 皆無法有效利用 Web Bean 規格所定義的新服務，不過您卻可將它們全部作為 Web Bean 來使用—將它們注入其它 Web Bean 中，透過 Web Bean XML 配置功能來配置它們，甚至是加入攔截器（interceptor）與裝飾器（decorator）—無須變動到您現有的程式碼。"
+msgstr "我們能夠很明確地告訴您，在絕大部分的情況下，所有含有不接受參數的 constructor 的 java class 都是個 Web Bean。這包含了所有的 JavaBean。另外，所有 EJB 3-style 的 session bean 也都屬於 Web Bean。當然，您先前所編寫的 JavaBean 和 EJB 皆無法有效利用 Web Bean 規格所定義的新服務，不過您卻可將它們全部作為 Web Bean 來使用 — 將它們注入其它 Web Bean 中，透過 Web Bean XML 配置功能來配置它們，甚至是加入攔截器（interceptor）與裝飾器（decorator） — 無須變動到您現有的程式碼。"
#. Tag: para
#: intro.xml:25
@@ -243,12 +243,12 @@
"At system initialization time, the Web Bean manager must validate that "
"exactly one Web Bean exists which satisfies each injection point. In our "
"example, if no implementation of <literal>Translator</literal> "
-"available—if the <literal>SentenceTranslator</literal> EJB was not "
-"deployed—the Web Bean manager would throw an "
+"available — if the <literal>SentenceTranslator</literal> EJB was not "
+"deployed — the Web Bean manager would throw an "
"<literal>UnsatisfiedDependencyException</literal>. If more than one "
"implementation of <literal>Translator</literal> was available, the Web Bean "
"manager would throw an <literal>AmbiguousDependencyException</literal>."
-msgstr "當系統初始化時，Web Bean 管理員必須驗證是否有正好一個滿足所有注入點的 Web Bean 存在。在我們的範例中，若沒有可用的 <literal>Translator</literal> 實做—若 <literal>SentenceTranslator</literal> EJB 沒有被建置—Web Bean 管理員便會回傳一個 <literal>UnsatisfiedDependencyException</literal>。若有超過一個可使用的 <literal>Translator</literal> 實做，那麼 Web Bean 管理員便會回傳一個 <literal>AmbiguousDependencyException</literal>。"
+msgstr "當系統初始化時，Web Bean 管理員必須驗證是否有正好一個滿足所有注入點的 Web Bean 存在。在我們的範例中，若沒有可用的 <literal>Translator</literal> 實做 — 若 <literal>SentenceTranslator</literal> EJB 沒有被建置 — Web Bean 管理員便會回傳一個 <literal>UnsatisfiedDependencyException</literal>。若有超過一個可使用的 <literal>Translator</literal> 實做，那麼 Web Bean 管理員便會回傳一個 <literal>AmbiguousDependencyException</literal>。"
#. Tag: title
#: intro.xml:80
@@ -370,9 +370,9 @@
#, no-c-format
msgid ""
"Note that not all clients of a Web Bean are Web Beans. Other objects such as "
-"Servlets or Message-Driven Beans—which are by nature not injectable, "
-"contextual objects—may also obtain references to Web Beans by injection."
-msgstr "請注意，並非所有 Web Bean 的客戶端都是 Web Bean。像是 Servlet 或訊息導向的 Bean 之類的其它物件—無法被注入，並屬於 contextual object—也能透過注入來取得 Web Bean 的參照。"
+"Servlets or Message-Driven Beans — which are by nature not injectable, "
+"contextual objects — may also obtain references to Web Beans by injection."
+msgstr "請注意，並非所有 Web Bean 的客戶端都是 Web Bean。像是 Servlet 或訊息導向的 Bean 之類的其它物件 — 無法被注入，並屬於 contextual object — 也能透過注入來取得 Web Bean 的參照。"
#. Tag: para
#: intro.xml:149
@@ -738,9 +738,9 @@
#: intro.xml:289
#, no-c-format
msgid ""
-"In this case, the name defaults to <literal>shoppingCart</literal>—the "
+"In this case, the name defaults to <literal>shoppingCart</literal> — the "
"unqualified class name, with the first character changed to lowercase."
-msgstr "在此情況下，名稱將被預設為 <literal>shoppingCart</literal>—這是個不完整的 class 名稱，並且第一個字元已被改變為小寫。"
+msgstr "在此情況下，名稱將被預設為 <literal>shoppingCart</literal> — 這是個不完整的 class 名稱，並且第一個字元已被改變為小寫。"
#. Tag: title
#: intro.xml:295
@@ -888,8 +888,8 @@
msgid ""
"The specification says that all EJB 3-style session and singleton beans are "
"<emphasis>enterprise</emphasis> Web Beans. Message driven beans are not Web "
-"Beans—since they are not intended to be injected into other "
-"objects—but they can take advantage of most of the functionality of Web "
+"Beans — since they are not intended to be injected into other "
+"objects — but they can take advantage of most of the functionality of Web "
"Beans, including dependency injection and interceptors."
msgstr "依賴注入"
Modified: doc/trunk/reference/zh-TW/part3.po
===================================================================
--- doc/trunk/reference/zh-TW/part3.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/zh-TW/part3.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -31,10 +31,10 @@
#, no-c-format
msgid ""
"You don't see string-based identifiers in Web Beans code, not because the "
-"framework is hiding them from you using clever defaulting rules—so-"
-"called \"configuration by convention\"—but because there are simply no "
+"framework is hiding them from you using clever defaulting rules — so-"
+"called \"configuration by convention\" — but because there are simply no "
"strings there to begin with!"
-msgstr "您在 Web Bean 的程式碼中不會看見基於字串的識別符號，這不是因為 framework 透過使用預設的規則來將它隱藏起來—又稱為「configuration by convention」—而是因為一開始根本就沒有任何字串！"
+msgstr "您在 Web Bean 的程式碼中不會看見基於字串的識別符號，這不是因為 framework 透過使用預設的規則來將它隱藏起來 — 又稱為「configuration by convention」 — 而是因為一開始根本就沒有任何字串！"
#. Tag: para
#: part3.xml:15
Modified: doc/trunk/reference/zh-TW/scopescontexts.po
===================================================================
--- doc/trunk/reference/zh-TW/scopescontexts.po 2009-01-20 16:30:56 UTC (rev 1129)
+++ doc/trunk/reference/zh-TW/scopescontexts.po 2009-01-20 20:33:41 UTC (rev 1130)
@@ -461,9 +461,9 @@
"The Web Bean manager is permitted to destroy a conversation and all state "
"held in its context at any time in order to preserve resources. A Web Bean "
"manager implementation will normally do this on the basis of some kind of "
-"timeout—though this is not required by the Web Beans specification. The "
+"timeout — though this is not required by the Web Beans specification. The "
"timeout is the period of inactivity before the conversation is destroyed."
-msgstr "Web Bean 管理員能夠隨時隨地刪除它 context 中的 conversation 以及所有狀態以保留資源。一個 Web Bean 管理員實做一般會利用某種形式的 timeout 來這麼作—儘管這在 Web Bean 規格中是非必要的。Timeout 代表 conversation 在被刪除之前所經過的休止狀態時間。"
+msgstr "Web Bean 管理員能夠隨時隨地刪除它 context 中的 conversation 以及所有狀態以保留資源。一個 Web Bean 管理員實做一般會利用某種形式的 timeout 來這麼作 — 儘管這在 Web Bean 規格中是非必要的。Timeout 代表 conversation 在被刪除之前所經過的休止狀態時間。"
#. Tag: para
#: scopescontexts.xml:208
More information about the weld-commits
mailing list