-NB: Your key can be obtained by logging in to [Flies](https://translate.jboss.org/flies/),
-visiting the [Profile page](https://translate.jboss.org/flies/profile/view) and
+NB: Your key can be obtained by logging in to [Zanata](https://translate.jboss.org/),
+visiting the [Profile page](https://translate.jboss.org/profile/view) and
clicking "generate API key" at the bottom.
The Scripts
@@ -74,18 +74,18 @@ The Scripts
1. Import job (run after documentation freeze):
This script will update the POT files in `src/main/docbook/pot` and
- push them to Flies for translation.
- `src/main/scripts/flies_import_source`
+ push them to Zanata for translation.
+ `src/main/scripts/zanata_import_source`
2. Build docs with latest translations (probably run nightly):
This script will fetch the latest translations to temporary files
in `target/draft` and build the documentation for review purposes.
- `src/main/scripts/flies_draft_build`
+ `src/main/scripts/zanata_draft_build`
3. Documentation release build:
This script will fetch the latest translations so that the release
build can be run.
- `src/main/scripts/flies_export_translations`
+ `src/main/scripts/zanata_export_translations`
`git checkin src/main/docbook`
_run existing ant build_
diff --git a/docs/reference/pom.xml b/docs/reference/pom.xml
index 3122004c4bb..75232ccfa10 100644
--- a/docs/reference/pom.xml
+++ b/docs/reference/pom.xml
@@ -1,11 +1,10 @@
-
+4.0.0org.jboss.weld.reference-guideweld-reference-guide
- 1.1.3-SNAPSHOT
+ 1.2.0-SNAPSHOTjdocbookWeld Reference Guidehttp://www.seamframework.org/Weld
@@ -20,7 +19,7 @@
org.jboss.weldweld-core-parent
- 1.1.3-SNAPSHOT
+ 1.2.0-SNAPSHOT../../pom.xml
@@ -28,9 +27,16 @@
weld-reference.pdf1.1.1-Beta5src/main/docbook
- 1.3
- src/main/docbook
- src/main/docbook
+ 1.6.0
+
+
+ src/main/docbook/pot
+
+ src/main/docbook
@@ -52,8 +58,7 @@
process-classes
-
+
@@ -114,7 +119,9 @@
+ fr-FRit-IT
+ ja-JPzh-CNzh-TWes-ES
@@ -133,9 +140,9 @@
- scm:git:git://github.com/weld/core.git
- scm:git:git://github.com/weld/core.git
- scm:git:git://github.com/weld/core.git
+ scm:git:git@github.com:weld/core.git
+ scm:git:git@github.com:weld/core.git
+ scm:git:git@github.com:weld/core.git
diff --git a/docs/reference/src/main/docbook/de-DE/Weld_-_JSR-299_Reference_Implementation.po b/docs/reference/src/main/docbook/de-DE/Weld_-_JSR-299_Reference_Implementation.po
new file mode 100644
index 00000000000..f4baccac014
--- /dev/null
+++ b/docs/reference/src/main/docbook/de-DE/Weld_-_JSR-299_Reference_Implementation.po
@@ -0,0 +1,59 @@
+#
+# AUTHOR , YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "A note about naming and nomenclature"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Shortly before the final draft of JSR-299 was submitted, the specification changed its name from \"Web Beans\" to \"Java Contexts and Dependency Injection for the Java EE platform\", abbreviated CDI. For a brief period after the renaming, the reference implementation adopted the name \"Web Beans\". However, this ended up causing more confusion than it solved and Red Hat decided to change the name of the reference implementation to \"Weld\". You may still find other documentation, blogs, forum posts, etc. that use the old nomenclature. Please update any references you can. The naming game is over."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You'll also find that some of the functionality that once existed in the specification is now missing, such as defining beans in XML. These features will be available as portable extensions for CDI in the Weld project, and perhaps other implementations."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this reference guide was started while changes were still being made to the specification. We've done our best to update it for accuracy. If you discover a conflict between what is written in this guide and the specification, the specification is the authority—assume it is correct. If you believe you have found an error in the specification, please report it to the JSR-299 EG."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Beans"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Start with Weld, the CDI Reference Implementation"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Loose coupling with strong typing"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "CDI and the Java EE ecosystem"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Weld Reference Guide"
+msgstr ""
+
diff --git a/docs/reference/src/main/docbook/de-DE/beans.po b/docs/reference/src/main/docbook/de-DE/beans.po
index 771c19991eb..9ee797fcca2 100644
--- a/docs/reference/src/main/docbook/de-DE/beans.po
+++ b/docs/reference/src/main/docbook/de-DE/beans.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
+msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
msgstr ""
#. Tag: para
@@ -56,7 +56,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
+msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
msgstr ""
#. Tag: para
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
+msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
msgstr ""
#. Tag: title
@@ -131,7 +131,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's see what all this new terminology means."
+msgid "Let's see what all this new terminology means."
msgstr ""
#. Tag: title
@@ -141,7 +141,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a "contract" that must be satisfied by the bean to be injected. The contract is:"
+msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a \"contract\" that must be satisfied by the bean to be injected. The contract is:"
msgstr ""
#. Tag: para
@@ -164,14 +164,14 @@ msgstr ""
msgid ""
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
+msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
msgstr ""
#. Tag: para
@@ -192,12 +192,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
+msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
+msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
msgstr ""
#. Tag: programlisting
@@ -206,19 +206,19 @@ msgid ""
"@Typed(Shop.class)\n"
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of "quality" using a qualifier."
+msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of \"quality\" using a qualifier."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
+msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
msgstr ""
#. Tag: programlisting
@@ -232,12 +232,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
+msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
+msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
msgstr ""
#. Tag: para
@@ -252,12 +252,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
+msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
msgstr ""
#. Tag: para
@@ -275,12 +270,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If a bean does not explicitly specify a qualifier, it has the default qualifier, @Default."
+msgid "If a bean or an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
+msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
msgstr ""
#. Tag: title
@@ -312,7 +307,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
+msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
msgstr ""
#. Tag: para
@@ -322,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk more about scopes in ."
+msgid "We'll talk more about scopes in ."
msgstr ""
#. Tag: title
@@ -343,7 +338,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"public @SessionScoped @Named("cart")\n"
+"public @SessionScoped @Named(\"cart\")\n"
"class ShoppingCart implements Serializable { ... }"
msgstr ""
@@ -355,9 +350,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:dataTable value="#{cart.lineItems}" var="item">\n"
+"<h:dataTable value=\"#{cart.lineItems}\" var=\"item\">\n"
" ...\n"
-"</h:dataTable>"
+"</h:dataTable>"
msgstr ""
#. Tag: para
@@ -389,7 +384,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
+msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
msgstr ""
#. Tag: programlisting
@@ -416,12 +411,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
+msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
+msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
msgstr ""
#. Tag: para
@@ -470,17 +465,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
+msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
+msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
+msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
msgstr ""
#. Tag: title
@@ -490,7 +485,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
+msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
msgstr ""
#. Tag: title
@@ -500,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
+msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
msgstr ""
#. Tag: para
@@ -525,7 +520,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It has an appropriate constructor—either:"
+msgid "It has an appropriate constructor—either:"
msgstr ""
#. Tag: para
@@ -540,7 +535,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
+msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
msgstr ""
#. Tag: para
@@ -585,12 +580,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
+msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
+msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
msgstr ""
#. Tag: para
@@ -625,7 +620,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
+msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
msgstr ""
#. Tag: para
@@ -640,17 +635,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
+msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
+msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're "heavyweight". It's nothing more than superstition to think that something is "heavier" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like "heavyweight"."
+msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're \"heavyweight\". It's nothing more than superstition to think that something is \"heavier\" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like \"heavyweight\"."
msgstr ""
#. Tag: title
@@ -690,7 +685,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
+msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
msgstr ""
#. Tag: programlisting
@@ -705,7 +700,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<p>Your raffle number is #{randomNumber}.</p>"
+msgid "<p>Your raffle number is #{randomNumber}.</p>"
msgstr ""
#. Tag: para
@@ -746,14 +741,14 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces Set<Roles> getRoles(User user) {\n"
+"@Produces Set<Roles> getRoles(User user) {\n"
" return user.getRoles();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk much more about producer methods in ."
+msgid "We'll talk much more about producer methods in ."
msgstr ""
#. Tag: title
@@ -763,7 +758,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
+msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
msgstr ""
#. Tag: programlisting
@@ -771,7 +766,7 @@ msgstr ""
msgid ""
"public class Shop {\n"
" @Produces PaymentProcessor paymentProcessor = ....;\n"
-" @Produces @Catalog List<Product> products = ....;\n"
+" @Produces @Catalog List<Product> products = ....;\n"
"}"
msgstr ""
@@ -782,5 +777,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
+msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
msgstr ""
diff --git a/docs/reference/src/main/docbook/de-DE/configure.po b/docs/reference/src/main/docbook/de-DE/configure.po
index eeba87f0a16..01ef2ccd8ab 100644
--- a/docs/reference/src/main/docbook/de-DE/configure.po
+++ b/docs/reference/src/main/docbook/de-DE/configure.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -30,50 +30,50 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
+msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<?xml version="1.0" encoding="UTF-8"?>\n"
-"<beans xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \n"
-" xmlns:weld="http://jboss.org/schema/weld/beans" \n"
-" xsi:schemaLocation="\n"
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<beans xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" \n"
+" xmlns:weld=\"http://jboss.org/schema/weld/beans\" \n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee http://docs.jboss.org/cdi/beans_1_0.xsd\n"
-" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">\n"
+" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd\">\n"
" \n"
-" <weld:scan>\n"
+" <weld:scan>\n"
" \n"
-" <!-- Don't deploy the classes for the swing app! -->\n"
-" <weld:exclude name="com.acme.swing.**" />\n"
+" <!-- Don't deploy the classes for the swing app! -->\n"
+" <weld:exclude name=\"com.acme.swing.**\" />\n"
" \n"
-" <!-- Don't include GWT support if GWT is not installed -->\n"
-" <weld:exclude name="com.acme.gwt.**">\n"
-" <weld:if-class-available name="!com.google.GWT"/>\n"
-" </weld:exclude>\n"
+" <!-- Don't include GWT support if GWT is not installed -->\n"
+" <weld:exclude name=\"com.acme.gwt.**\">\n"
+" <weld:if-class-available name=\"!com.google.GWT\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
+" <!--\n"
" Exclude classes which end in Blether if the system property verbosity is set to low\n"
" i.e.\n"
" java ... -Dverbosity=low \n"
-" --> \n"
-" <weld:exclude pattern="^(.*)Blether$">\n"
-" <weld:if-system-property name="verbosity" value="low"/>\n"
-" </weld:exclude>\n"
+" --> \n"
+" <weld:exclude pattern=\"^(.*)Blether$\">\n"
+" <weld:if-system-property name=\"verbosity\" value=\"low\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
-" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
+" <!--\n"
+" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
" property is not set\n"
-" -->\n"
-" <weld:exclude name="com.acme.jsf.**">\n"
-" <weld:if-class-available name="org.apahce.wicket.Wicket"/>\n"
-" <weld:if-system-property name="!viewlayer"/>\n"
-" </weld:exclude>\n"
-" </weld:scan>\n"
+" -->\n"
+" <weld:exclude name=\"com.acme.jsf.**\">\n"
+" <weld:if-class-available name=\"org.apahce.wicket.Wicket\"/>\n"
+" <weld:if-system-property name=\"!viewlayer\"/>\n"
+" </weld:exclude>\n"
+" </weld:scan>\n"
" \n"
-"</beans>"
+"</beans>"
msgstr ""
#. Tag: para
@@ -83,7 +83,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
+msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
msgstr ""
#. Tag: para
@@ -93,12 +93,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
+msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
+msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
msgstr ""
#. Tag: para
@@ -113,5 +113,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
+msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
msgstr ""
diff --git a/docs/reference/src/main/docbook/de-DE/contexts.po b/docs/reference/src/main/docbook/de-DE/contexts.po
index 998addb61d4..6503057daf1 100644
--- a/docs/reference/src/main/docbook/de-DE/contexts.po
+++ b/docs/reference/src/main/docbook/de-DE/contexts.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,17 +25,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld allows you to easiy manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivaed (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
+msgid "Weld allows you to easily manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivated (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and discociating the data store after calling activate."
+msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and dissociating the data store after calling activate."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld automatically controls context lifecycle in many scenarios such as Http Requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
+msgid "Weld automatically controls context lifecycle in many scenarios such as HTTP requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
msgstr ""
#. Tag: para
@@ -145,7 +145,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
+msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
msgstr ""
#. Tag: entry
@@ -245,12 +245,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implmentations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
+msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implementations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
+msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
msgstr ""
#. Tag: programlisting
@@ -263,14 +263,14 @@ msgid ""
" ...\n"
" \n"
" /* Start the request, providing a data store which will last the lifetime of the request */\n"
-" public void startRequest(Map<String, Object> requestDataStore) {\n"
+" public void startRequest(Map<String, Object> requestDataStore) {\n"
" // Associate the store with the context and acticate the context\n"
" requestContext.associate(requestDataStore);\n"
" requestContext.activate();\n"
" }\n"
" \n"
" /* End the request, providing the same data store as was used to start the request */\n"
-" public void endRequest(Map<String, Object> requestDataStore) {\n"
+" public void endRequest(Map<String, Object> requestDataStore) {\n"
" try {\n"
" /* Invalidate the request (all bean instances will be scheduled for destruction) */\n"
" requestContext.invalidate();\n"
@@ -290,7 +290,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's session contexts are "lazy" and don't require a session to actually exist until a bean instance must be written."
+msgid "Weld's session contexts are \"lazy\" and don't require a session to actually exist until a bean instance must be written."
msgstr ""
#. Tag: para
@@ -308,16 +308,16 @@ msgid ""
" /* Start a transient conversation */\n"
" /* Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */\n"
-" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" resumeOrStartConversation(requestDataStore, sessionDataStore, null);\n"
" }\n"
"\n"
" /* Start a transient conversation (if cid is null) or resume a non-transient */\n"
" /* conversation. Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */ \n"
-" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore, \n"
+" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore, \n"
" String cid) {\n"
" /* Associate the stores with the context and acticate the context */\n"
" * BoundRequest just wraps the two datastores */\n"
@@ -329,8 +329,8 @@ msgid ""
" /* End the conversations, providing the same data store as was used to start */\n"
" /* the request. Any transient conversations will be destroyed, any newly-promoted */\n"
" /* conversations will be placed into the session */\n"
-" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" try {\n"
" /* Invalidate the conversation (all transient conversations will be scheduled for destruction) */\n"
" conversationContext.invalidate();\n"
@@ -345,15 +345,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the containber), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
+msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the container), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the abilty to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
+msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the ability to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's conversations are not assigned ids until they become non-transient."
+msgid "Weld's conversations are not assigned ids until they become non-transient."
msgstr ""
diff --git a/docs/reference/src/main/docbook/de-DE/decorators.po b/docs/reference/src/main/docbook/de-DE/decorators.po
index f4874de56ca..064f87679e8 100644
--- a/docs/reference/src/main/docbook/de-DE/decorators.po
+++ b/docs/reference/src/main/docbook/de-DE/decorators.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: decorators\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-02 09:30+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -23,12 +23,12 @@ msgstr "Dekoratoren"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
+msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
msgstr "Interzeptoren bieten eine leistungsfähige Weise, Probleme, die orthogonal zum Typensystem sind, festzuhalten und zu trennen. Jeder Interzeptor kann Aufrufe jedes Java Typs abfangen. Dies macht ihn perfekt für die Lösung technischer Probleme wie etwa Transaktionsmanagement und Sicherheit.Jedoch sind Interzeptoren ihrem Wesen nach nicht der tatsächlichen Semantik der Ereignisse gewahr, die sie abfangen. Interzeptoren sind daher nicht die geeigneten Tools zur Separierung von unternehmensbezogenen Problemen."
#. Tag: para
#, fuzzy, no-c-format
-msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
+msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
msgstr "Das Gegenteil gilt für Dekoratoren. Ein Dekorator fängt Aufrufe nur für ein bestimmtes Java-Interface ab und kennt daher die zu diesem Interface gehörende Semantik. Dadurch sind Dekoratoren das perfekte Tool zur Bearbeitung einige unternehmensbezogener Probleme. Es bedeutet auch, dass Dekoratoren nicht diesselbe Allgemeingültigkeit wie Interzeptoren besitzen. Dekoratoren können keine technischen Probleme lösen, die sich über viele disparate Typen verteilen."
#. Tag: para
@@ -126,7 +126,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
+msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
msgstr "Anders als andere einfache Web Beans, kann ein Dekorator eine abstrakte Klasse sein. Falls es nichts besonderes ist, dass der Dekorator für eine bestimmte Methode des dekorierten Interface tun muss, so brauchen Sie diese Methode nicht zu implementieren."
#. Tag: para
@@ -210,14 +210,14 @@ msgid ""
" \n"
" public void withdraw(BigDecimal amount) {\n"
" account.withdraw(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedWithdrawl(amount) );\n"
" }\n"
" }\n"
" \n"
" public void deposit(BigDecimal amount);\n"
" account.deposit(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedDeposit(amount) );\n"
" }\n"
" }\n"
@@ -260,21 +260,21 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <decorators>\n"
-" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
-" </decorators>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <decorators>\n"
+" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
+" </decorators>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
+msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
msgstr "Diese Deklaration dient demselben Zweck für Dekoratoren, den die<Interceptors>-Deklaration für Interzeptoren erfüllt:"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/de-DE/ee.po b/docs/reference/src/main/docbook/de-DE/ee.po
index 312f823dd54..355b26a9edc 100644
--- a/docs/reference/src/main/docbook/de-DE/ee.po
+++ b/docs/reference/src/main/docbook/de-DE/ee.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: ee\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-09 20:55+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -58,7 +58,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
+msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
msgstr ""
#. Tag: para
@@ -83,7 +83,7 @@ msgstr "Einspeisung von Java EE Ressourcen in ein Web Bean"
#. Tag: para
#, fuzzy, no-c-format
-msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
+msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
msgstr "Alle einfachen wie auch Enterprise Web Beans können die Java EE \"Dependency\"-Einspeisung mittels @Resource, @EJB und @PersistenceContext verwenden. Wir haben bereits einige Beispiele hierfür gesehen, obwohl wir diesen zum damaligen Zeitpunkt nicht viel Beachtung geschenkt haben:"
#. Tag: programlisting
@@ -142,7 +142,7 @@ msgstr "Aufruf eines Web Bean von einem Servlet"
#. Tag: para
#, fuzzy, no-c-format
-msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
+msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
msgstr "In Java EE 6 ist die Verwendung eines Web Beans von einem Servlet ganz einfach. Speisen Sie einfach das Web Bean mittels Web Beans Field oder Initialisierungsmethodeneinspeisung (sog. \"Initializer Method Injection\") ein."
#. Tag: programlisting
@@ -155,14 +155,14 @@ msgid ""
" @Override\n"
" public void service(HttpServletRequest request, HttpServletResponse response)\n"
" throws ServletException, IOException {\n"
-" credentials.setUsername(request.getParameter("username")):\n"
-" credentials.setPassword(request.getParameter("password")):\n"
+" credentials.setUsername(request.getParameter(\"username\")):\n"
+" credentials.setPassword(request.getParameter(\"password\")):\n"
" login.login();\n"
" if ( login.isLoggedIn() ) {\n"
-" response.sendRedirect("/home.jsp");\n"
+" response.sendRedirect(\"/home.jsp\");\n"
" }\n"
" else {\n"
-" response.sendRedirect("/loginError.jsp");\n"
+" response.sendRedirect(\"/loginError.jsp\");\n"
" }\n"
" }\n"
" \n"
@@ -201,7 +201,7 @@ msgstr "Aufruf eines Web Beans von einem Message-Driven Bean"
#. Tag: para
#, no-c-format
-msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
+msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
msgstr ""
#. Tag: para
@@ -263,10 +263,10 @@ msgstr ""
#, no-c-format
msgid ""
"public class OrderResources {\n"
-" @Resource(name="jms/ConnectionFactory")\n"
+" @Resource(name=\"jms/ConnectionFactory\")\n"
" private ConnectionFactory connectionFactory;\n"
" \n"
-" @Resource(name="jms/OrderQueue")\n"
+" @Resource(name=\"jms/OrderQueue\")\n"
" private Queue orderQueue;\n"
" \n"
" @Produces @OrderConnection\n"
@@ -317,7 +317,7 @@ msgid ""
"\n"
"public void sendMessage() {\n"
" MapMessage msg = orderSession.createMapMessage();\n"
-" msg.setLong("orderId", order.getId());\n"
+" msg.setLong(\"orderId\", order.getId());\n"
" ...\n"
" producer.send(msg);\n"
"}"
@@ -343,7 +343,7 @@ msgstr "Packen und Deployment"
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a "bean archive". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
+msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a \"bean archive\". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
msgstr "Web Beans definiert kein spezielles Deployment-Archiv. Sie können Web Beans in JARs, EJB-JARs oder WARs verpacken, jedem Deployment Speicherort im Klassenpfad der Anwendung. Allerdings muss jedes Web Beans enthaltene Archiv eine Datei namens web-beans.xml im META-INF oder WEB-INF-Verzeichnis enthalten. Die Datei kann leer sein. Web Beans die in Archiven deployt werden, die keine web-beans.xml-Datei enthalten, sind nicht für die Verwendung in der Anwendung verfügbar."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/de-DE/environments.po b/docs/reference/src/main/docbook/de-DE/environments.po
index 94327047b22..1c0ac5e8025 100644
--- a/docs/reference/src/main/docbook/de-DE/environments.po
+++ b/docs/reference/src/main/docbook/de-DE/environments.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-28 17:09+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -56,12 +56,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
+msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an "uber-jar", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
+msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an \"uber-jar\", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
msgstr ""
#. Tag: para
@@ -72,9 +72,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
#. Tag: title
@@ -84,18 +84,18 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
+msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<Context>\n"
-" <Resource name="BeanManager" \n"
-" auth="Container"\n"
-" type="javax.enterprise.inject.spi.BeanManager"\n"
-" factory="org.jboss.weld.resources.ManagerObjectFactory"/>\n"
-"</Context>"
+"<Context>\n"
+" <Resource name=\"BeanManager\" \n"
+" auth=\"Container\"\n"
+" type=\"javax.enterprise.inject.spi.BeanManager\"\n"
+" factory=\"org.jboss.weld.resources.ManagerObjectFactory\"/>\n"
+"</Context>"
msgstr ""
#. Tag: para
@@ -106,12 +106,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<resource-env-ref>\n"
-" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
-" <resource-env-ref-type>\n"
+"<resource-env-ref>\n"
+" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
+" <resource-env-ref-type>\n"
" javax.enterprise.inject.spi.BeanManager\n"
-" </resource-env-ref-type>\n"
-"</resource-env-ref>"
+" </resource-env-ref-type>\n"
+"</resource-env-ref>"
msgstr ""
#. Tag: para
@@ -131,27 +131,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
+msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.mortbay.jetty.plus.naming.Resource">\n"
-" <Arg><Ref id="webAppCtx"/></Arg> \n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.mortbay.jetty.plus.naming.Resource\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg> \n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure>"
msgstr ""
#. Tag: para
@@ -162,22 +162,22 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://www.eclipse.org/jetty/configure.dtd">\n"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://www.eclipse.org/jetty/configure.dtd\">\n"
"\n"
-"<Configure id="webAppCtx" class="org.eclipse.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.eclipse.jetty.plus.jndi.Resource">\n"
-" <Arg> <Ref id="webAppCtx"/> </Arg>\n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure> "
+"<Configure id=\"webAppCtx\" class=\"org.eclipse.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.eclipse.jetty.plus.jndi.Resource\">\n"
+" <Arg> <Ref id=\"webAppCtx\"/> </Arg>\n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure> "
msgstr ""
#. Tag: para
@@ -187,7 +187,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
+msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
msgstr ""
#. Tag: para
@@ -197,19 +197,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file META-INF/jetty-web.xml with the following content to your war:"
+msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file WEB-INF/jetty-web.xml with the following content to your war:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <Call class="org.jboss.weld.environment.jetty.WeldServletHandler" name="process">\n"
-" <Arg><Ref id="webAppCtx"/></Arg>\n"
-" </Call>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <Call class=\"org.jboss.weld.environment.jetty.WeldServletHandler\" name=\"process\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg>\n"
+" </Call>\n"
+"</Configure>"
msgstr ""
#. Tag: title
@@ -219,7 +219,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In addition to improved integration of the Enterprise Java stack, the "Contexts and Dependency Injection for the Java EE platform" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
+msgid "In addition to improved integration of the Enterprise Java stack, the \"Contexts and Dependency Injection for the Java EE platform\" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
msgstr ""
#. Tag: para
@@ -279,7 +279,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Parameters List<String> params;"
+msgid "@Inject @Parameters List<String> params;"
msgstr ""
#. Tag: programlisting
@@ -299,7 +299,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example of a simple CDI SE application:"
+msgid "Here's an example of a simple CDI SE application:"
msgstr ""
#. Tag: programlisting
@@ -308,8 +308,8 @@ msgid ""
"@Singleton\n"
"public class HelloWorld\n"
"{\n"
-" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
-" System.out.println("Hello " + parameters.get(0));\n"
+" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
+" System.out.println(\"Hello \" + parameters.get(0));\n"
" }\n"
"}"
msgstr ""
@@ -331,7 +331,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
+msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
msgstr ""
#. Tag: para
@@ -341,17 +341,17 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "java org.jboss.weld.environment.se.StartMain <args>"
+msgid "java org.jboss.weld.environment.se.StartMain <args>"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Programatic Bootstrap API"
+msgid "Programmatic Bootstrap API"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
+msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
msgstr ""
#. Tag: programlisting
@@ -377,10 +377,10 @@ msgid ""
"{\n"
"\n"
" /** Provides access to all beans within the application. */\n"
-" public Instance<Object> instance() {...}\n"
+" public Instance<Object> instance() {...}\n"
"\n"
" /** Provides access to all events within the application. */\n"
-" public Event<Object> event() {...}\n"
+" public Event<Object> event() {...}\n"
"\n"
" /** Provides direct access to the BeanManager. */\n"
" public BeanManager getBeanManager() {...}\n"
@@ -390,7 +390,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
+msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
msgstr ""
#. Tag: programlisting
@@ -430,22 +430,22 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
+msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans>\n"
-" <decorators>\n"
-" <decorator>org.jboss.weld.environment.se.threading.RunnableDecorator</decorator>\n"
-" </decorator>\n"
-"</beans>"
+"<beans>\n"
+" <decorators>\n"
+" <class>org.jboss.weld.environment.se.threading.RunnableDecorator</class>\n"
+" </decorator>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situtations where you would otherwise have used ThreadLocal directly, which are typically rare."
+msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situations where you would otherwise have used ThreadLocal directly, which are typically rare."
msgstr ""
#. Tag: title
@@ -455,7 +455,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
+msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/de-DE/events.po b/docs/reference/src/main/docbook/de-DE/events.po
index 5cd3c91f544..e9ed2074b15 100644
--- a/docs/reference/src/main/docbook/de-DE/events.po
+++ b/docs/reference/src/main/docbook/de-DE/events.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: events\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-13 08:17+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -38,7 +38,7 @@ msgstr "nicht nur sind Ereignis-Producer von Observern abgekoppelt, Observer sin
#. Tag: para
#, fuzzy, no-c-format
-msgid "observers can specify a combination of "selectors" to narrow the set of event notifications they will receive, and"
+msgid "observers can specify a combination of \"selectors\" to narrow the set of event notifications they will receive, and"
msgstr "Observer können eine Kombination von \"Selektoren\" festlegen, um den Satz von Ereignisbenachrichtigungen einzugrenzen, die sie erhalten und "
#. Tag: para
@@ -48,7 +48,7 @@ msgstr "Observer können sofort benachrichtigt werden oder sie können festlegen
#. Tag: para
#, no-c-format
-msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
+msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
msgstr ""
#. Tag: title
@@ -63,7 +63,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
+msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
msgstr ""
#. Tag: programlisting
@@ -106,7 +106,7 @@ msgstr "only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
+msgid "An observer method need not specify any event qualifiers—in this case it is interested in only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
msgstr "Eine Observer-Methode muss keine Ereignis-Bindings festlegen, in diesem Fall interessiert sie sich für alle Ereignisse eines bestimmten Typs. Legt sie Ereignis-Bindings fest, so interessiert sie sich nur für Ereignisse, die diese Ereignis-Bindings besitzen."
#. Tag: para
@@ -131,7 +131,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Event<Document> documentEvent;"
+msgid "@Inject @Any Event<Document> documentEvent;"
msgstr " documentEvent]]>"
#. Tag: para
@@ -186,7 +186,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
+msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
msgstr " documentUpdatedEvent]]>"
#. Tag: para
@@ -206,12 +206,12 @@ msgstr "kein Ereignis-Binding festlegt außer für die an <
#. Tag: para
#, no-c-format
-msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
+msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
+msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
msgstr "(){} );]]>"
#. Tag: para
@@ -226,7 +226,7 @@ msgstr "Transaktionale Observer"
#. Tag: para
#, no-c-format
-msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
+msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
msgstr ""
#. Tag: para
@@ -288,7 +288,7 @@ msgstr "Typenmitglieder von Ereignis-Bindings können durch den Ereignis-Produce
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
+msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
msgstr " LoggedInEvent;}}]]>"
#. Tag: para
@@ -300,7 +300,7 @@ msgstr "Alternativ kann der Wert des Typenmitglieds des Ereignis-Bindings dynami
#, fuzzy, no-c-format
msgid ""
"abstract class RoleBinding \n"
-" extends AnnotationLiteral<Role> \n"
+" extends AnnotationLiteral<Role> \n"
" implements Role {}"
msgstr ""
" blogEvent;\n"
"...\n"
@@ -444,12 +444,12 @@ msgid ""
"\n"
" @PersistenceContext EntityManager em;\n"
" \n"
-" List<Product> products;\n"
+" List<Product> products;\n"
"\n"
" @Produces @Catalog \n"
-" List<Product> getCatalog() {\n"
+" List<Product> getCatalog() {\n"
" if (products==null) {\n"
-" products = em.createQuery("select p from Product p where p.deleted = false")\n"
+" products = em.createQuery(\"select p from Product p where p.deleted = false\")\n"
" .getResultList();\n"
" }\n"
" return products;\n"
@@ -491,16 +491,16 @@ msgid ""
"@Stateless\n"
"public class ProductManager {\n"
" @PersistenceContext EntityManager em;\n"
-" @Inject @Any Event<Product> productEvent;\n"
+" @Inject @Any Event<Product> productEvent;\n"
"\n"
" public void delete(Product product) {\n"
" em.delete(product);\n"
-" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
" }\n"
" \n"
" public void persist(Product product) {\n"
" em.persist(product);\n"
-" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
" }\n"
" ...\n"
"}"
diff --git a/docs/reference/src/main/docbook/de-DE/example.po b/docs/reference/src/main/docbook/de-DE/example.po
index 02ed91889cb..41b6e651d60 100644
--- a/docs/reference/src/main/docbook/de-DE/example.po
+++ b/docs/reference/src/main/docbook/de-DE/example.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: example\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-28 07:53+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -23,7 +23,7 @@ msgstr "Beispiel einer JSF-Webanwendung"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
+msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
msgstr "Illustrieren wir diese Ideen an einem vollständigen Beispiel. Wir werden einen Benutzer Login/Logout für eine JSF verwendende Anwendung implementieren. Zunächst definieren wir ein Web Bean das den während des Logins eingegebenen Benutzernamen und das Passwort verwahrt:"
#. Tag: programlisting
@@ -65,18 +65,18 @@ msgstr "Dieses Web Bean ist an den Login-Prompt in folgendem JSF-Formular gebund
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:form>\n"
-" <h:panelGrid columns="2" rendered="#{!login.loggedIn}">\n"
-" <f:validateBean>\n"
-" <h:outputLabel for="username">Username:</h:outputLabel>\n"
-" <h:inputText id="username" value="#{credentials.username}"/>\n"
-" <h:outputLabel for="password">Password:</h:outputLabel>\n"
-" <h:inputSecret id="password" value="#{credentials.password}"/>\n"
-" </f:validateBean>\n"
-" </h:panelGrid>\n"
-" <h:commandButton value="Login" action="#{login.login}" rendered="#{!login.loggedIn}"/>\n"
-" <h:commandButton value="Logout" action="#{login.logout}" rendered="#{login.loggedIn}"/>\n"
-"</h:form>"
+"<h:form>\n"
+" <h:panelGrid columns=\"2\" rendered=\"#{!login.loggedIn}\">\n"
+" <f:validateBean>\n"
+" <h:outputLabel for=\"username\">Username:</h:outputLabel>\n"
+" <h:inputText id=\"username\" value=\"#{credentials.username}\"/>\n"
+" <h:outputLabel for=\"password\">Password:</h:outputLabel>\n"
+" <h:inputSecret id=\"password\" value=\"#{credentials.password}\"/>\n"
+" </f:validateBean>\n"
+" </h:panelGrid>\n"
+" <h:commandButton value=\"Login\" action=\"#{login.login}\" rendered=\"#{!login.loggedIn}\"/>\n"
+" <h:commandButton value=\"Logout\" action=\"#{login.logout}\" rendered=\"#{login.loggedIn}\"/>\n"
+"</h:form>"
msgstr ""
"\n"
" \n"
@@ -123,7 +123,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
+msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
msgstr ""
#. Tag: para
@@ -143,10 +143,10 @@ msgid ""
" private User user;\n"
" \n"
" public void login() {\n"
-" List<User> results = userDatabase.createQuery(\n"
-" "select u from User u where u.username = :username and u.password = :password")\n"
-" .setParameter("username", credentials.getUsername())\n"
-" .setParameter("password", credentials.getPassword())\n"
+" List<User> results = userDatabase.createQuery(\n"
+" \"select u from User u where u.username = :username and u.password = :password\")\n"
+" .setParameter(\"username\", credentials.getUsername())\n"
+" .setParameter(\"password\", credentials.getPassword())\n"
" .getResultList();\n"
" \n"
" if (!results.isEmpty()) {\n"
@@ -292,14 +292,14 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:panelGroup rendered="#{login.loggedIn}">\n"
+"<h:panelGroup rendered=\"#{login.loggedIn}\">\n"
" signed in as #{currentUser.username}\n"
-"</h:panelGroup>"
+"</h:panelGroup>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
+msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
msgstr "Wir hoffen, dass Ihnen dieses Beispiel einen Vorgeschmack auf das Web Bean Programmiermodell gegeben hat. Im nächsten Kapitel sehen wir uns die Web Beans Dependency-Einspeisung näher an."
#~ msgid "Of course, @LoggedIn is a binding annotation:"
diff --git a/docs/reference/src/main/docbook/de-DE/extend.po b/docs/reference/src/main/docbook/de-DE/extend.po
index f0e7cdc0671..613065fab13 100644
--- a/docs/reference/src/main/docbook/de-DE/extend.po
+++ b/docs/reference/src/main/docbook/de-DE/extend.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: extend\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-14 06:59+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -78,7 +78,7 @@ msgstr "Die Bean-Klasse"
#. Tag: para
#, no-c-format
-msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
+msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
msgstr ""
#. Tag: programlisting
@@ -166,15 +166,15 @@ msgid ""
"class MyExtension implements Extension {\n"
" \n"
" void beforeBeanDiscovery(@Observes BeforeBeanDiscovery bbd) {\n"
-" Logger.global.debug("beginning the scanning process");\n"
+" Logger.global.debug(\"beginning the scanning process\");\n"
" }\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
-" Logger.global.debug("scanning type: " + pat.getAnnotatedType().getJavaClass().getName());\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" Logger.global.debug(\"scanning type: \" + pat.getAnnotatedType().getJavaClass().getName());\n"
" } \n"
"\n"
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd) {\n"
-" Logger.global.debug("finished the scanning process");\n"
+" Logger.global.debug(\"finished the scanning process\");\n"
" }\n"
" \n"
"}"
@@ -182,7 +182,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
+msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
msgstr ""
#. Tag: programlisting
@@ -190,7 +190,7 @@ msgstr ""
msgid ""
"class MyExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" //tell the container to ignore the type if it is annotated @Ignore\n"
" if ( pat.getAnnotatedType().isAnnotionPresent(Ignore.class) ) pat.veto(); \n"
" } \n"
@@ -205,7 +205,7 @@ msgstr "Der zentrale Kern zur Erweiterung von Web Beans ist das Manager
#. Tag: programlisting
#, no-c-format
-msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
+msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
msgstr ""
#. Tag: title
@@ -222,31 +222,31 @@ msgstr "Das Manager-Interface die programmatische Registrieru
#, no-c-format
msgid ""
"public interface BeanManager {\n"
-" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
-" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
-" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
-" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
-" public Set<Bean<?>> getBeans(String name);\n"
-" public Bean<?> getPassivationCapableBean(String id);\n"
-" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
+" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
+" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
+" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
+" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
+" public Set<Bean<?>> getBeans(String name);\n"
+" public Bean<?> getPassivationCapableBean(String id);\n"
+" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
" public void validate(InjectionPoint injectionPoint);\n"
" public void fireEvent(Object event, Annotation... qualifiers);\n"
-" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
-" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
-" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
-" public boolean isScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
-" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
-" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
-" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
-" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
-" public Context getContext(Class<? extends Annotation> scopeType);\n"
+" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
+" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
+" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
+" public boolean isScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
+" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
+" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
+" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
+" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
+" public Context getContext(Class<? extends Annotation> scopeType);\n"
" public ELResolver getELResolver();\n"
" public ExpressionFactory wrapExpressionFactory(ExpressionFactory expressionFactory);\n"
-" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
-" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
+" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
+" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
"}"
msgstr ""
@@ -267,7 +267,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's study some of the interfaces exposed by the BeanManager."
+msgid "Let's study some of the interfaces exposed by the BeanManager."
msgstr "Der zentrale Kern zur Erweiterung von Web Beans ist das Manager-Objekt."
#. Tag: title
@@ -282,21 +282,21 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to instatiate the object itself, and so only method and field injection will be supported."
+msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to insntatiate the object itself, and so only method and field injection will be supported."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"//get the BeanManager from JNDI\n"
-"BeanManager beanManager = (BeanManager) new InitialContext().lookup("java:comp/BeanManager");\n"
+"BeanManager beanManager = (BeanManager) new InitialContext().lookup(\"java:comp/BeanManager\");\n"
"\n"
"//CDI uses an AnnotatedType object to read the annotations of a class\n"
-"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
+"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
"\n"
"//The extension uses an InjectionTarget to delegate instantiation, dependency injection \n"
"//and lifecycle callbacks to the CDI container\n"
-"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
+"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
"\n"
"//each instance needs its own CDI CreationalContext\n"
"CreationalContext ctx = beanManager.createCreationalContext(null);\n"
@@ -326,33 +326,33 @@ msgstr "Instanzen der abstrakten Klasse Bean repräsentieren
#. Tag: para
#, no-c-format
-msgid "The Bean interface exposes all the interesting things we dicussed in ."
+msgid "The Bean interface exposes all the interesting things we discussed in ."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"public interface Bean<T> extends Contextual<T> {\n"
-" public Set<Type> getTypes();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Class<? extends Annotation> getScope();\n"
+"public interface Bean<T> extends Contextual<T> {\n"
+" public Set<Type> getTypes();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Class<? extends Annotation> getScope();\n"
" public String getName();\n"
-" public Set<Class<? extends Annotation>> getStereotypes();\n"
-" public Class<?> getBeanClass();\n"
+" public Set<Class<? extends Annotation>> getStereotypes();\n"
+" public Class<?> getBeanClass();\n"
" public boolean isAlternative();\n"
" public boolean isNullable();\n"
-" public Set<InjectionPoint> getInjectionPoints();\n"
+" public Set<InjectionPoint> getInjectionPoints();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's an easy way to find out what beans exist in the application:"
+msgid "There's an easy way to find out what beans exist in the application:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
+msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
msgstr ""
#. Tag: para
@@ -372,7 +372,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
+msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
msgstr ""
#. Tag: programlisting
@@ -383,49 +383,49 @@ msgid ""
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd, BeanManager bm) {\n"
" \n"
" //use this to read annotations of the class\n"
-" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
+" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
"\n"
" //use this to instantiate the class and inject dependencies\n"
-" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
+" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
"\n"
-" abd.addBean( new Bean<SecurityManager>() {\n"
+" abd.addBean( new Bean<SecurityManager>() {\n"
"\n"
" @Override\n"
-" public Class<?> getBeanClass() {\n"
+" public Class<?> getBeanClass() {\n"
" return SecurityManager.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
" public String getName() {\n"
-" return "securityManager";\n"
+" return \"securityManager\";\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getQualifiers() {\n"
-" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
-" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
-" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
+" public Set<Annotation> getQualifiers() {\n"
+" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
+" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
+" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
" return qualifiers;\n"
" }\n"
"\n"
" @Override\n"
-" public Class<? extends Annotation> getScope() {\n"
+" public Class<? extends Annotation> getScope() {\n"
" return SessionScoped.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Class<? extends Annotation>> getStereotypes() {\n"
+" public Set<Class<? extends Annotation>> getStereotypes() {\n"
" return Collections.emptySet();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypes() {\n"
-" Set<Type> types = new HashSet<Type>();\n"
+" public Set<Type> getTypes() {\n"
+" Set<Type> types = new HashSet<Type>();\n"
" types.add(SecurityManager.class);\n"
" types.add(Object.class);\n"
" return types;\n"
@@ -442,7 +442,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
+" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
" SecurityManager instance = it.produce(ctx);\n"
" it.inject(instance, ctx);\n"
" it.postConstruct(instance);\n"
@@ -451,7 +451,7 @@ msgid ""
"\n"
" @Override\n"
" public void destroy(SecurityManager instance, \n"
-" CreationalContext<SecurityManager> ctx) {\n"
+" CreationalContext<SecurityManager> ctx) {\n"
" it.preDestroy(instance);\n"
" it.dispose(instance);\n"
" ctx.release();\n"
@@ -480,7 +480,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
+msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
msgstr ""
#. Tag: programlisting
@@ -488,38 +488,38 @@ msgstr ""
msgid ""
"public class QualifiedNameExtension implements Extension {\n"
"\n"
-" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
+" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
"\n"
" //wrap this to override the annotations of the class\n"
-" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
+" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
" \n"
-" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
+" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
"\n"
" @Override\n"
-" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
+" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
" return at.getConstructors();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedField<? super X>> getFields() {\n"
+" public Set<AnnotatedField<? super X>> getFields() {\n"
" return at.getFields();\n"
" }\n"
"\n"
" @Override\n"
-" public Class<X> getJavaClass() {\n"
+" public Class<X> getJavaClass() {\n"
" return at.getJavaClass();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
+" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
" return at.getMethods();\n"
" }\n"
"\n"
" @Override\n"
-" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
+" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
" if ( Named.class.equals(annType) ) {\n"
" class NamedLiteral \n"
-" extends AnnotationLiteral<Named> \n"
+" extends AnnotationLiteral<Named> \n"
" implements Named {\n"
" @Override\n"
" public String value() {\n"
@@ -528,7 +528,7 @@ msgid ""
" final String qualifiedName;\n"
" if ( pkg.isAnnotationPresent(Named.class) ) {\n"
" qualifiedName = pkg.getAnnotation(Named.class).value() \n"
-" + '.' + unqualifiedName;\n"
+" + '.' + unqualifiedName;\n"
" }\n"
" else {\n"
" qualifiedName = unqualifiedName;\n"
@@ -544,7 +544,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getAnnotations() {\n"
+" public Set<Annotation> getAnnotations() {\n"
" return at.getAnnotations();\n"
" }\n"
"\n"
@@ -554,12 +554,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypeClosure() {\n"
+" public Set<Type> getTypeClosure() {\n"
" return at.getTypeClosure();\n"
" }\n"
"\n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
" return at.isAnnotationPresent(annType);\n"
" }\n"
" \n"
@@ -573,7 +573,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
+msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
msgstr ""
#. Tag: programlisting
@@ -581,17 +581,17 @@ msgstr ""
msgid ""
"class ServiceAlternativeExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" \n"
-" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
+" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
" \n"
" if ( Service.class.isAssignableFrom( type.getJavaClass() ) ) {\n"
" \n"
" //if the class implements Service, make it an @Alternative\n"
-" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
+" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
" \n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
" return annotationType.equals(Alternative.class) ? \n"
" true : type.isAnnotationPresent(annotationType);\n"
" }\n"
@@ -624,7 +624,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
+msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
msgstr ""
#. Tag: programlisting
@@ -644,25 +644,25 @@ msgstr ""
msgid ""
"public class ConfigExtension implements Extension {\n"
"\n"
-"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
+"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
"\t\t\n"
"\t\t//wrap this to intercept the component lifecycle\n"
-"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
+"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
"\t \n"
-" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
+" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
" \n"
" //use this to read annotations of the class and its members\n"
-" AnnotatedType<X> at = pit.getAnnotatedType();\n"
+" AnnotatedType<X> at = pit.getAnnotatedType();\n"
" \n"
" //read the properties file\n"
-" String propsFileName = at.getClass().getSimpleName() + ".properties";\n"
+" String propsFileName = at.getClass().getSimpleName() + \".properties\";\n"
" InputStream stream = at.getJavaClass().getResourceAsStream(propsFileName);\n"
" if (stream!=null) {\n"
" \n"
" try {\n"
" Properties props = new Properties();\n"
" props.load(stream);\n"
-" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
+" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
" String fieldName = property.getKey().toString();\n"
" Object value = property.getValue();\n"
" try {\n"
@@ -674,7 +674,7 @@ msgid ""
" else {\n"
" //TODO: do type conversion automatically\n"
" pit.addDefinitionError( new InjectionException(\n"
-" "field is not of type String: " + field ) );\n"
+" \"field is not of type String: \" + field ) );\n"
" }\n"
" }\n"
" catch (NoSuchFieldException nsfe) {\n"
@@ -690,14 +690,14 @@ msgid ""
" }\n"
" }\n"
" \n"
-" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
+" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
"\n"
" @Override\n"
-" public void inject(X instance, CreationalContext<X> ctx) {\n"
+" public void inject(X instance, CreationalContext<X> ctx) {\n"
" it.inject(instance, ctx);\n"
" \n"
" //set the values onto the new instance of the component\n"
-" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
+" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
" try {\n"
" configuredValue.getKey().set(instance, configuredValue.getValue());\n"
" }\n"
@@ -723,12 +723,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
-" public X produce(CreationalContext<X> ctx) {\n"
+" public X produce(CreationalContext<X> ctx) {\n"
" return it.produce(ctx);\n"
" }\n"
" \n"
@@ -743,7 +743,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
+msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
msgstr ""
#. Tag: title
@@ -760,9 +760,9 @@ msgstr "Das Context-Interface unterstützt die Hinzufügung n
#, fuzzy, no-c-format
msgid ""
"public interface Context {\n"
-" public Class<? extends Annotation> getScope();\n"
-" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
-" public <T> T get(Contextual<T> contextual);\n"
+" public Class<? extends Annotation> getScope();\n"
+" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
+" public <T> T get(Contextual<T> contextual);\n"
" boolean isActive();\n"
"}"
msgstr ""
diff --git a/docs/reference/src/main/docbook/de-DE/gettingstarted.po b/docs/reference/src/main/docbook/de-DE/gettingstarted.po
index 9fbc93ecf16..612a599d57a 100644
--- a/docs/reference/src/main/docbook/de-DE/gettingstarted.po
+++ b/docs/reference/src/main/docbook/de-DE/gettingstarted.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: ri\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-27 15:36+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -23,7 +23,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, Glassfish 3.0 or any compliant Java EE 6 container."
+msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, GlassFish 3.0 or any compliant Java EE 6 container."
msgstr ""
#. Tag: para
@@ -38,7 +38,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To run the examples with the provided build scripts, you'll need the following:"
+msgid "To run the examples with the provided build scripts, you'll need the following:"
msgstr ""
#. Tag: para
@@ -83,12 +83,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
+msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
+msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
msgstr ""
#. Tag: para
@@ -98,7 +98,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
+msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
msgstr ""
#. Tag: title
@@ -108,19 +108,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
+msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
+msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> unzip jboss-6.0.*.zip\n"
-"$> mv jboss-6.0.*/ jboss-as-6.0"
+"$> unzip jboss-6.0.*.zip\n"
+"$> mv jboss-6.0.*/ jboss-as-6.0"
msgstr ""
#. Tag: para
@@ -135,7 +135,7 @@ msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
#, fuzzy, no-c-format
-msgid "You're now ready to deploy your first example!"
+msgid "You're now ready to deploy your first example!"
msgstr "Jetzt können Sie Ihr erstes Beispiel deployen!"
#. Tag: para
@@ -146,22 +146,22 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant deploy"
msgstr ""
"$ cd examples/numberguess\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
+msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/jboss-as-6.0\n"
-"$> ./bin/run.sh"
+"$> cd /path/to/jboss-as-6.0\n"
+"$> ./bin/run.sh"
msgstr "$ /Application/jboss-5.0.0.GA/bin/run.sh"
#. Tag: para
@@ -170,11 +170,11 @@ msgid "a Windows command window:"
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
-"$> run"
-msgstr ""
+"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
+"$> run"
+msgstr "$ /Application/jboss-5.0.0.GA/bin/run.sh"
#. Tag: para
#, no-c-format
@@ -229,20 +229,20 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/translator\n"
-"$> ant deploy"
+"$> cd examples/jsf/translator\n"
+"$> ant deploy"
msgstr ""
"$ cd examples/translator\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
+msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
+msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
msgstr "Hier setzen wir den Kontextpfad, der uns eine schöne url liefert (http://localhost:8080/webbeans-translator)."
#. Tag: title
@@ -252,41 +252,43 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
+msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
+msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> chmod 755 glassfish-v3-unix.sh\n"
-"$> ./glassfish-v3-unix.sh"
+"$> chmod 755 glassfish-v3-unix.sh\n"
+"$> ./glassfish-v3-unix.sh"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
+msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
+msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
-"$> ant package"
+"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
+"$> ant package"
msgstr ""
+"$ cd examples/numberguess\n"
+"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
+msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
msgstr ""
#. Tag: para
@@ -296,12 +298,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin start-domain domain1"
+msgid "$> asadmin start-domain domain1"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on "Applications", then click on the "Deploy..." button under the heading "Applications" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
+msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on \"Applications\", then click on the \"Deploy...\" button under the heading \"Applications\" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
msgstr ""
#. Tag: para
@@ -311,7 +313,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin deploy target/weld-numberguess.war"
+msgid "$> asadmin deploy target/weld-numberguess.war"
msgstr ""
#. Tag: para
@@ -331,24 +333,24 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
+msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
+msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
msgstr "Anschließend laden Sie die Web Beans RI unter seamframework.org herunter und entzippen diese. Zum Beispiel "
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "$> unzip apache-tomcat-6.0.18.zip"
+msgid "$> unzip apache-tomcat-6.0.18.zip"
msgstr ""
""
#. Tag: para
#, no-c-format
-msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
+msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
msgstr ""
#. Tag: title
@@ -358,7 +360,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
+msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
msgstr ""
#. Tag: programlisting
@@ -368,7 +370,7 @@ msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now you're ready to deploy the numberguess example to Tomcat!"
+msgid "Now you're ready to deploy the numberguess example to Tomcat!"
msgstr "Um das numberguess Beispiel zu deployen:"
#. Tag: para
@@ -379,15 +381,15 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant tomcat.deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant tomcat.deploy"
msgstr ""
"$ cd examples/numberguess\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with "tomcat."."
+msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with \"tomcat.\"."
msgstr ""
#. Tag: para
@@ -412,21 +414,21 @@ msgstr "ant undeploy - das Beispiel vom Server entfernen"
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
+msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/apache-tomcat-6\n"
-"$> ./bin/start.sh"
+"$> cd /path/to/apache-tomcat-6\n"
+"$> ./bin/start.sh"
msgstr "$ /Application/jboss-5.0.0.GA/bin/run.sh"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
-"$> start"
+"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
+"$> start"
msgstr ""
""
@@ -443,12 +445,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
+msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
+msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
msgstr ""
#. Tag: para
@@ -458,7 +460,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<user username="admin" password="" roles="manager"/>"
+msgid "<user username=\"admin\" password=\"\" roles=\"manager\"/>"
msgstr ""
#. Tag: para
@@ -468,7 +470,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
+msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
msgstr ""
#. Tag: para
@@ -478,7 +480,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn tomcat:redeploy -Ptomcat"
+msgid "$> mvn tomcat:redeploy -Ptomcat"
msgstr ""
#. Tag: para
@@ -493,7 +495,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace tomcat:run -Ptomcat"
+msgid "$> mvn war:inplace tomcat:run -Ptomcat"
msgstr ""
#. Tag: para
@@ -503,12 +505,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Ptomcat"
+msgid "$> mvn compile war:inplace -Ptomcat"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
+msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
msgstr ""
#. Tag: title
@@ -523,12 +525,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
+msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
+msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
msgstr ""
#. Tag: para
@@ -537,11 +539,13 @@ msgid "To run the weld-numberguess example on Jetty, switch t
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> mvn war:inplace jetty:run -Pjetty"
+"$> cd examples/jsf/numberguess\n"
+"$> mvn war:inplace jetty:run -Pjetty"
msgstr ""
+"$ cd examples/numberguess\n"
+"ant deploy"
#. Tag: para
#, no-c-format
@@ -555,7 +559,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Pjetty"
+msgid "$> mvn compile war:inplace -Pjetty"
msgstr ""
#. Tag: para
@@ -565,7 +569,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclispe[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
+msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclipse[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
msgstr ""
#. Tag: para
@@ -575,7 +579,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
+msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
msgstr ""
#. Tag: para
@@ -585,12 +589,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace -Pjetty-ide"
+msgid "$> mvn war:inplace -Pjetty-ide"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using "Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
+msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using \"Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/de-DE/injection.po b/docs/reference/src/main/docbook/de-DE/injection.po
index 11b7cde51a5..7b5387ec7ca 100644
--- a/docs/reference/src/main/docbook/de-DE/injection.po
+++ b/docs/reference/src/main/docbook/de-DE/injection.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: injection\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-15 15:56+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -23,7 +23,7 @@ msgstr "Dependency-Einspeisung"
#. Tag: para
#, no-c-format
-msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
+msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
msgstr ""
#. Tag: title
@@ -148,7 +148,7 @@ msgstr "Als nächstes initialisiert der Web Bean Manager die Werte aller eingesp
#. Tag: para
#, fuzzy, no-c-format
-msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
+msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
msgstr "Anschließend ruft der Web Bean Manager alle Initialisierermethoden des Web Beans auf."
#. Tag: para
@@ -184,7 +184,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
+msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
msgstr ""
#. Tag: title
@@ -194,7 +194,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
+msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
msgstr "Die Web Beans Spezifikation definiert eine Prozedur namens typesicherer Auflösungsalgorithmus (sog. typesafe resolution algorithm), den der Web Bean Manager bei der Identifizierung des an einem Einspeisungspunkt einzuspeisenden Web Beans folgt. Dieser Algorithmus sieht auf den ersten Blick recht komplex aus, ist es aber nach kurzer Eingewöhnung nicht. Typensichere Auflösung wird zum Initialisierungszeitpunkt des Systems durchgeführt, was bedeutet, dass der Manager den Benutzer sofort darüber informiert, falls die Abhängigkeiten eines Web Beans nicht erfüllt werden können - dies erfolgt durch Meldung von UnsatisfiedDependencyException oder AmbiguousDependencyException."
#. Tag: para
@@ -219,12 +219,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
+msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
+msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
msgstr ""
#. Tag: title
@@ -385,7 +385,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you may be thinking, "What's the different between using a qualifier and just specifying the exact implementation class you want?" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alterative implementations of @Asynchronous PaymentProcessor!"
+msgid "Now, you may be thinking, \"What's the different between using a qualifier and just specifying the exact implementation class you want?\" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alternative implementations of @Asynchronous PaymentProcessor!"
msgstr ""
#. Tag: title
@@ -395,7 +395,7 @@ msgstr "Einfache Web Beans unterstützen nur die @PostConstruct@Default. From time to time, you'll need to decare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
+msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to declare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
msgstr ""
#. Tag: para
@@ -407,7 +407,7 @@ msgstr ""
#, no-c-format
msgid ""
"@Inject \n"
-"void initServices(@Any Instance<Service> services) { \n"
+"void initServices(@Any Instance<Service> services) { \n"
" for (Service service: services) {\n"
" service.init();\n"
" }\n"
@@ -443,7 +443,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then we select one of the possible member values when appling the qualifier:"
+msgid "Then we select one of the possible member values when applying the qualifier:"
msgstr ""
#. Tag: programlisting
@@ -464,7 +464,7 @@ msgid ""
"@Target({METHOD, FIELD, PARAMETER, TYPE})\n"
"public @interface PayBy {\n"
" PaymentMethod value();\n"
-" @Nonbinding String comment() default "";\n"
+" @Nonbinding String comment() default \"\";\n"
"}"
msgstr ""
"this FAQ for step-by-step instructions for how to resolve an ambigous resolution exception between a raw bean type and a producer method that returns the same bean type."
+msgid "See this FAQ for step-by-step instructions for how to resolve an ambiguous resolution exception between a raw bean type and a producer method that returns the same bean type."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Just remember: "There can be only one.""
+msgid "Just remember: \"There can be only one.\""
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
+msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
+msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
msgstr "Es gibt eine weitere Sache, derer man sich bei der Verwendung von \"Dependency\"-Einspeisung in Web Beans gewahr sein sollte."
#. Tag: title
@@ -647,7 +647,7 @@ msgstr "Clients eines eingespeisten Web Beans enthalten in der Regel keinen dire
#. Tag: para
#, fuzzy, no-c-format
-msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
+msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
msgstr "Stellen wir uns vor, ein an den Geltungsbereich der Anwendung gebundenes Web Bean hielte einen direkten Verweis auf ein an den Geltungsbereich der Anfrage gebundenes Web Bean. Das an den Geltungsbereich der Anwendung gebundene Web Bean wird von vielen verschiedenen Anfragen geteilt. Jedoch sollte jede Anfrage eine andere Instanz des an den Geltungsbereich der Anfrage gebundenen Web Beans sehen!"
#. Tag: para
@@ -672,7 +672,7 @@ msgstr "Die folgenden Java-Typen können nicht durch den Web Bean Manager geprox
#. Tag: para
#, fuzzy, no-c-format
-msgid "classes which don't have a non-private constructor with no parameters, and"
+msgid "classes which don't have a non-private constructor with no parameters, and"
msgstr "Klassen, die keinen nicht-privaten Konstruktor ohne Parameter besitzen sowie "
#. Tag: para
@@ -687,7 +687,7 @@ msgstr "Arrays und primitive Typen."
#. Tag: para
#, no-c-format
-msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
+msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
msgstr ""
#. Tag: para
@@ -697,7 +697,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "change the type of the injection point to Instance<X>,"
+msgid "change the type of the injection point to Instance<X>,"
msgstr ""
#. Tag: para
@@ -727,7 +727,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But we didn't get around to implementing this yet."
+msgid "But we didn't get around to implementing this yet."
msgstr ""
#. Tag: title
@@ -762,7 +762,7 @@ msgstr "Die Anwendung kann durch Einspeisung eine Instanz des Interface "
#. Tag: para
@@ -797,7 +797,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -812,19 +812,19 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, we need to obtain an instance of our qualifier type. Since annotatons are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
+msgid "Next, we need to obtain an instance of our qualifier type. Since annotations are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"abstract class AsynchronousQualifier\n"
-"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
+"class AsynchronousQualifier\n"
+"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
msgstr ""
" \n"
@@ -839,14 +839,14 @@ msgstr ""
#, fuzzy, no-c-format
msgid ""
"PaymentProcessor p = paymentProcessorSource\n"
-" .select(new AnnotationLiteral<Asynchronous>() {});"
+" .select(new AnnotationLiteral<Asynchronous>() {});"
msgstr ""
"(){});]]>"
#. Tag: para
#, no-c-format
-msgid "We can't use an anonymous class to implement a qualifier type with members."
+msgid "However, we can't use an anonymous class to implement a qualifier type with members."
msgstr ""
#. Tag: para
@@ -894,7 +894,7 @@ msgstr "Ein Web Bean mit Geltungsbereich @Dependent kann eine
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
+msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
msgstr "Sehen wir uns ein Beispiel an. Der folgende Code ist umfangreich und empfänglich für Refaktorierungsprobleme:"
#. Tag: programlisting
@@ -938,7 +938,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
+msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
msgstr "Sie sind noch nicht ganz überzeugt? Dann sehen Sie sich ein weiteres Beispiel an. Zur Einspeisung von HTTP-Parametern müssen wir einen Binding-Typ festlegen:"
#. Tag: programlisting
@@ -966,8 +966,8 @@ msgstr "Wir würden diesen Binding-Typ an Einspeisungspunkten wie folgt verwende
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@HttpParam("username") String username;\n"
-"@HttpParam("password") String password;"
+"@HttpParam(\"username\") String username;\n"
+"@HttpParam(\"password\") String password;"
msgstr ""
""
@@ -982,7 +982,7 @@ msgstr "Die folgende Producer-Methode erledigt die Arbeit:"
msgid ""
"class HttpParams\n"
"\n"
-" @Produces @HttpParam("")\n"
+" @Produces @HttpParam(\"\")\n"
" String getParamValue(InjectionPoint ip) {\n"
" ServletRequest request = (ServletRequest) FacesContext.getCurrentInstance().getExternalContext().getRequest();\n"
" return request.getParameter(ip.getAnnotated().getAnnotation(HttpParam.class).value());\n"
@@ -1001,7 +1001,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own prodcuer for the request and have it injected as a method parameter."
+msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own producer for the request and have it injected as a method parameter."
msgstr ""
#. Tag: para
@@ -1019,8 +1019,8 @@ msgstr "Der Web Bean Manager liefert ein eingebautes Web Bean, das das
msgid ""
"public interface InjectionPoint { \n"
" public Type getType();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Bean<?> getBean();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Bean<?> getBean();\n"
" public Member getMember();\n"
" public Annotated getAnnotated();\n"
" public boolean isDelegate();\n"
diff --git a/docs/reference/src/main/docbook/de-DE/interceptors.po b/docs/reference/src/main/docbook/de-DE/interceptors.po
index 3615cb66772..17b5b0aadf9 100644
--- a/docs/reference/src/main/docbook/de-DE/interceptors.po
+++ b/docs/reference/src/main/docbook/de-DE/interceptors.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: interceptors\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-15 19:11+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -109,7 +109,7 @@ msgstr "Interzeptor-Bindings"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
+msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
msgstr "Nehmen wir an, wir wollten deklarieren, dass einige unserer Web Beans transaktional sind. Das erste, was wir benötigen ist eine Interzeptor bindende Annotation, um festzulegen, für welches Web Bean wir uns interessieren:"
#. Tag: programlisting
@@ -162,7 +162,7 @@ msgstr "Implementierung von Interzeptoren"
#. Tag: para
#, fuzzy, no-c-format
-msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
+msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
msgstr "Das ist toll, aber irgendwann müssen wir den den Managementaspekt dieser Transaktion liefert, implementieren. Wir müssen nur einen standardmäßigen EJB-Interzeptor erstellen und ihn mit @Interceptor und @Transactional annotieren."
#. Tag: programlisting
@@ -224,16 +224,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -264,17 +264,17 @@ msgstr "Zum Beispiel könnten wir festlegen, dass unser Sicherheitsinterzeptor v
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -377,7 +377,7 @@ msgstr "In der Regel verwenden wir Kombinationen von Interzeptor-Binding-Typen,
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Secure(rolesAllowed="admin") @Transactional\n"
+"@Secure(rolesAllowed=\"admin\") @Transactional\n"
"public class ShoppingCart { ... }"
msgstr ""
"meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
+msgid "Well, fortunately, CDI works around this missing feature of Java. We may annotate one interceptor binding type with other interceptor binding types (termed a meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
msgstr "Nun, zum Glück umgeht Web Beans dieses fehlende Feature von Java. Wir können einen Interzeptor Binding-Typ mit anderen Interzeptor Binding-Typen annotieren. Die Interzeptor-Bindings sind transitive jedes Web Bean mit demselben Interzeptor-Binding erbt die als Meta-Annotationen deklarierten Interzeptor-Bindings."
#. Tag: programlisting
@@ -532,7 +532,7 @@ msgstr "Interzeptoren können zum Deployment-Zeitpunkt nicht einfach deaktiviert
#. Tag: para
#, fuzzy, 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."
+msgid "the interceptor ordering is non-global — it is determined by the order in which interceptors are listed at the class level."
msgstr "Die Interzeptorreihenfolge ist nicht allgemeingültig sie wird durch die Reihenfolge, in der Interzeptoren auf Klassenebene aufgeführt sind, festgelegt."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/de-DE/intro.po b/docs/reference/src/main/docbook/de-DE/intro.po
index 32e52d1d598..0810cb7aea7 100644
--- a/docs/reference/src/main/docbook/de-DE/intro.po
+++ b/docs/reference/src/main/docbook/de-DE/intro.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: intro\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-22 13:52+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -23,7 +23,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
+msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
msgstr "Können Sie es jetzt kaum erwarten Ihr erstes Web Bean zu schreiben? Oder sind Sie etwas skeptisch und fragen sich, welche Hürden Ihnen bei der Web Beans Spezifikation bevorstehen? Die gute Nachricht ist, dass Sie wahrscheinlich schon hunderte, wenn nicht tausende von Web Beans geschrieben haben. Vielleicht erinnern Sie sich nicht einmal an das erste Web Bean, das Sie je geschrieben haben."
#. Tag: title
@@ -38,27 +38,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Prior to Java EE 6, there was no clear definition of the term "bean" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications "beans" for years. There were even a couple of different kinds of things called "beans" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a "bean". What we've been missing is a common definition."
+msgid "Prior to Java EE 6, there was no clear definition of the term \"bean\" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications \"beans\" for years. There were even a couple of different kinds of things called \"beans\" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a \"bean\". What we've been missing is a common definition."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
+msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
+msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
+msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now let's see how to create your first bean that actually uses CDI."
+msgid "Now let's see how to create your first bean that actually uses CDI."
msgstr ""
#. Tag: title
@@ -68,14 +68,14 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
+msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
msgstr "Nehmen wir an, Sie besitzen zwei bestehende Java Klassen, die bis dato in verschiedenen Anwendungen verwendet wurden. Die erste Klasse parst einen String in eine Liste von Sätzen:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
"public class SentenceParser {\n"
-" public List<String> parse(String text) { ... }\n"
+" public List<String> parse(String text) { ... }\n"
"}"
msgstr ""
"TextTranslator besitzt keinen Konstr
#. Tag: para
#, fuzzy, no-c-format
-msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
+msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
msgstr "Wie Sie wahrscheinlich bereits erraten haben, hat die @Initializer-Annotation etwas mit Dependency-Einspeisung zu tun! @Initializer kann am Konstruktor oder der Methode eines Web Beans angewendet werden und teilt dem Web Bean Manager mit, diesen Konstruktor oder diese Methode bei Instantiierung des Web Beans aufzurufen. Der Web Bean Manager speist andere Web Beans in die Parameter des Konstruktors oder der Methode ein."
#. Tag: para
@@ -183,7 +183,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
+msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
msgstr ""
#. Tag: programlisting
@@ -222,7 +222,7 @@ msgstr "Wo Translator das lokale Interface ist:"
#. Tag: para
#, no-c-format
-msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
+msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
msgstr ""
#. Tag: para
@@ -233,7 +233,7 @@ msgstr "Wir erhalten eine Instanz von TextTranslator durch de
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
+"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
"...\n"
"public void translate() {\n"
" textTranslatorInstance.get().translate(inputText);\n"
@@ -246,17 +246,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
+msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
+msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
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 Translator verfügbar ist wenn der SentenceTranslator EJB nicht deployt wurde dass der Web Bean Manager eine UnsatisfiedDependencyException melden würde. Wäre mehr als eine Implementierung von Translator verfügbar, so würde der Web Bean Manager eine AmbiguousDependencyException melden."
#. Tag: para
#, no-c-format
-msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
+msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
msgstr ""
#~ msgid "Getting started with Web Beans"
diff --git a/docs/reference/src/main/docbook/de-DE/next.po b/docs/reference/src/main/docbook/de-DE/next.po
index 9d671082b3e..079a4d3cbd7 100644
--- a/docs/reference/src/main/docbook/de-DE/next.po
+++ b/docs/reference/src/main/docbook/de-DE/next.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: next\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-28 06:27+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -23,12 +23,12 @@ msgstr "Die nächsten Schritte"
#. Tag: para
#, no-c-format
-msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
+msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
+msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
msgstr "Die Web Beans Referenzimplementierung wird unter http://seamframework.org/WebBeans entwickelt. Das RI Entwicklungsteam und die Web Beans Spezifikation führen unter http://in.relation.to einen Blog. Dieser Artikel basiert im Wesentlichen auf eine dort veröffentlichte Reihe von Blog-Einträgen."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/de-DE/part1.po b/docs/reference/src/main/docbook/de-DE/part1.po
index ba0d26894c6..e57dd47f3cd 100644
--- a/docs/reference/src/main/docbook/de-DE/part1.po
+++ b/docs/reference/src/main/docbook/de-DE/part1.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: part1\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-22 16:09+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -128,7 +128,7 @@ msgstr "muss ich es explizit löschen?"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Where should I keep the reference to it when I'm not currently using it?"
+msgid "Where should I keep the reference to it when I'm not currently using it?"
msgstr "wo sollte ich meinen Verweis darauf aufbewahren, wenn ich es nicht direkt verwende?"
#. Tag: para
@@ -143,7 +143,7 @@ msgstr "wie kann ich dieses Objekt mit anderen Objekten teilen?"
#. Tag: para
#, no-c-format
-msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
+msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
msgstr ""
#. Tag: para
@@ -173,12 +173,12 @@ msgstr "Dekoratoren erlauben die Kompartmentalisierung von
#. Tag: para
#, fuzzy, no-c-format
-msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
+msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
msgstr "Und das Wichtigste - Web Beans bieten all diese Facilities auf typensichere Weise. Web Beans verwenden nie string-basierte Bezeichner, um zu bestimmen, wie zusammenarbeitende Objekte zusammenpassen. Und XML wird - obwohl es nach wie vor eine Option bleibt - wird selten verwendet. Stattdessen verwenden Web Beans die bereits im Java-Objektmodell verfügbaren Typinformationen gemeinsam mit einem neuen Muster namens Binding-Annotationen, um Web Beans, deren Abhängigkeiten, deren Interzeptoren und Dekoratoren sowie deren Ereignis-Consumer zu verbinden."
#. Tag: para
#, no-c-format
-msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
+msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
msgstr ""
#. Tag: para
@@ -188,7 +188,7 @@ msgstr "Web Beans bieten sogar die nötigen Integrationspunkte, so dass andere A
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
+msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
msgstr "Web Beans wurden durch eine Reihe bestehender Java Frameworks beeinflusst, darunter Seam, Guice und Spring. Jedoch besitzen Web Beans ihre eigenen Eigenschaften: Typesicherer als Seam, mehr stateful und weniger XML-zentrisch als Spring, mehr Web- und Enterprise-anwendungsfähig als Guice."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/de-DE/part3.po b/docs/reference/src/main/docbook/de-DE/part3.po
index 80efa601ee2..f957322812e 100644
--- a/docs/reference/src/main/docbook/de-DE/part3.po
+++ b/docs/reference/src/main/docbook/de-DE/part3.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: part3\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-07 15:34+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -18,7 +18,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
+msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
msgstr ""
#. Tag: para
@@ -73,7 +73,7 @@ msgstr "Das zweite wichtige Thema von Web Beans ist starke Typisierung
#. Tag: para
#, fuzzy, no-c-format
-msgid "You don't see string-based identifiers in CDI 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!"
+msgid "You don't see string-based identifiers in CDI 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 "Sie sehen keine String-basierten Bezeichner in Web Beans Code; dies ist nicht der Fall weil das Framework diese unter Verwendung irgendwelcher Defaulting-Regeln vor Ihnen verbirgt; sogenannte \"Konfiguration nach Konvention\" sondern weil einfach keine Strings existieren!"
#. Tag: para
@@ -143,7 +143,7 @@ msgstr "Web Beans Stereotypen erweitern diese Idee um einen
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
+msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
msgstr "Wir können jetzt einige fortgeschrittenere Features von Web Beans kennenlernen. Vergessen Sie nicht, dass diese Features unseren Code sowohl einfacher zu validieren als auch leserlicher machen sollen. Meist werden Sie diese Features nicht verwenden müssen, wenn Sie dies aber auf kluge Weise tun, so werden Sie deren Vorteile schnell zu schätzen wissen."
#~ msgid "Even Web Beans XML metadata is strongly typed! There's no compiler for XML, so Web Beans takes advantage of XML schemas to validate the Java types and attributes that appear in XML. This approach turns out to make the XML more literate, just like annotations made our Java code more literate."
diff --git a/docs/reference/src/main/docbook/de-DE/part4.po b/docs/reference/src/main/docbook/de-DE/part4.po
index ee97d5b1709..fbb0944ee4e 100644
--- a/docs/reference/src/main/docbook/de-DE/part4.po
+++ b/docs/reference/src/main/docbook/de-DE/part4.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: part4\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-28 06:47+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -18,7 +18,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
+msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
msgstr ""
#. Tag: para
@@ -28,7 +28,7 @@ msgstr "Wir haben bereits gesehen, wie Web Beans bei der Integration von EJB und
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
+msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
msgstr "Wir wollen Ihnen jetzt zeigen, wie Sie die Java EE platform in einer Web Beans verwendenden Anwendung am besten nutzen. Wir sehen uns auch kurz einen Satz von SPIs an, die portable Erweiterungen zu Web Beans unterstützen sollen. Sie werden diese SPIs vielleicht nie direkt benutzen müssen, aber es ist hilfreich diese zu kennen, falls Sie sie einmal brauchen. Primär ist wichtig, dass Sie diese bei jeder Verwendung von Erweiterungen Dritter indirekt nutzen können."
#~ msgid "The third theme of Web Beans is integration. Web Beans was designed to work in concert with other technologies, helping the application developer fit the other technologies together. Web Beans is an open technology. It forms a part of the Java EE ecosystem, and is itself the foundation for a new ecosystem of portable extensions and integration with existing frameworks and technologies."
diff --git a/docs/reference/src/main/docbook/de-DE/part5.po b/docs/reference/src/main/docbook/de-DE/part5.po
index 3425ffa346b..67b58bc6cde 100644
--- a/docs/reference/src/main/docbook/de-DE/part5.po
+++ b/docs/reference/src/main/docbook/de-DE/part5.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-28 17:09+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and Glassfish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
+msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and GlassFish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/de-DE/producermethods.po b/docs/reference/src/main/docbook/de-DE/producermethods.po
index d3c6d8224f8..0fdd95c8a14 100644
--- a/docs/reference/src/main/docbook/de-DE/producermethods.po
+++ b/docs/reference/src/main/docbook/de-DE/producermethods.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: producermethods\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-23 08:08+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -23,7 +23,7 @@ msgstr "Producer-Methoden"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
+msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
msgstr "Producer-Methoden gestatten es uns, bestimmte Beschränkungen zu umgehen, die auftreten, wenn der Web Bean Manager statt die Anwendung für die Instantiierung von Objekten verantwortlich ist. Sie sind auch die einfachste Art der Integration von Objekten in die Web Beans Umgebung, die keine Web Beans sind. (In lernen wir eine zweite Weise kennen.)"
#. Tag: para
@@ -78,7 +78,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
+msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
msgstr ""
#. Tag: programlisting
@@ -160,7 +160,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
+msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
msgstr "Wird jetzt die Producer-Methode aufgerufen, so wird die wiedergegebene PaymentStrategy an den Session-Kontext gebunden. Die Producer-Methode wird in drselben Session nicht mehr aufgerufen."
#. Tag: para
@@ -175,12 +175,12 @@ msgstr "Einspeisung in Producer-Methoden"
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
+msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
msgstr "Es gibt ein potenzielles Problem mit dem Code oben. Die Implementierungen von CreditCardPaymentStrategy werden unter Verwendung des Java new Operators instantiiert. Direkt durch die Anwendung instantiierte Objekte können die Dependency-Einspeisung nicht nutzen und besitzen keine Interzeptoren."
#. Tag: para
#, fuzzy, no-c-format
-msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
+msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
msgstr "Falls dies nicht das ist was wir wünschen, so können wir Dependency-Einspeisung in die Producer-Methode verwenden, um Web Bean Instanzen zu erhalten: "
#. Tag: programlisting
@@ -212,12 +212,12 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of "promoting" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left "hanging" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
+msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of \"promoting\" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left \"hanging\" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
msgstr "Aber Moment mal, was wenn CreditCardPaymentStrategy ein anfragenbegrenztes Web Bean ist? Dann hat die Producer-Methode die Wirkung, dass Sie die aktuelle anfragenbegrenzte Instanz in den Geltungsbereich der Session \"befördert\". Das ist mit ziemlicher Sicherheit ein Fehler! Das anfragenbegrenzte Objekt wird vom Web Bean Manager gelöscht ehe die Session endet, aber der Verweis auf das Objekt bleibt im Geltungsbereich der Session \"hängen\" in the session scope. Dieser Fehler wird nicht vom Web Bean Manager aufgespürt, daher seien Sie besonders vorsichtig wenn Sie Web Bean Instanzen von Producer-Methoden wiedergeben!"
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
+msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
msgstr "Es existieren mindestens drei Arten, wie dieser Fehler behoben werden kann. Wir könnten den Geltungsbereich der CreditCardPaymentStrategy-Implementierung ändern, aber das würde auch andere Clients dieses Web Beans betreffen. Eine bessere Option wäre es, den Geltungsbereich der Producer-Methode auf @Dependent oder @RequestScoped zu ändern."
#. Tag: para
@@ -264,7 +264,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
+msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
msgstr "Dann wird eine neue abhängige Instanz von CreditCardPaymentStrategy erstellt, an die Producer-Methode weitergegeben, von der Producer-Methode wiedergegeben und schließlich an den Session-Kontext gebunden. Das abhängige Objekt wird nicht gelöscht bis das Preferences-Objekt gelöscht wird, meist am Ende der Session."
#. Tag: title
diff --git a/docs/reference/src/main/docbook/de-DE/resources.po b/docs/reference/src/main/docbook/de-DE/resources.po
index 9177a15cee6..31dfe153927 100644
--- a/docs/reference/src/main/docbook/de-DE/resources.po
+++ b/docs/reference/src/main/docbook/de-DE/resources.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a nonportable "mapped name"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
+msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a non-portable \"mapped name\"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
msgstr ""
#. Tag: para
@@ -72,35 +72,35 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @WebServiceRef(lookup="java:app/service/Catalog")\n"
+"@Produces @WebServiceRef(lookup=\"java:app/service/Catalog\")\n"
"Catalog catalog;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @Resource(lookup="java:global/env/jdbc/CustomerDatasource") \n"
+"@Produces @Resource(lookup=\"java:global/env/jdbc/CustomerDatasource\") \n"
"@CustomerDatabase Datasource customerDatabase;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceContext(unitName="CustomerDatabase")\n"
+"@Produces @PersistenceContext(unitName=\"CustomerDatabase\")\n"
"@CustomerDatabase EntityManager customerDatabasePersistenceContext;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceUnit(unitName="CustomerDatabase") \n"
+"@Produces @PersistenceUnit(unitName=\"CustomerDatabase\") \n"
"@CustomerDatabase EntityManagerFactory customerDatabasePersistenceUnit;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @EJB(ejbLink="../their.jar#PaymentService") \n"
+"@Produces @EJB(ejbLink=\"../their.jar#PaymentService\") \n"
"PaymentService paymentService;"
msgstr ""
@@ -126,7 +126,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
+msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
msgstr ""
#. Tag: title
@@ -171,7 +171,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
+msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
msgstr ""
#. Tag: programlisting
@@ -186,7 +186,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@PersistenceContext(unitName="CustomerDatabase") EntityManager"
+msgid "@PersistenceContext(unitName=\"CustomerDatabase\") EntityManager"
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/de-DE/ri-spi.po b/docs/reference/src/main/docbook/de-DE/ri-spi.po
index 9bad706fa61..20ff8ffa5d7 100644
--- a/docs/reference/src/main/docbook/de-DE/ri-spi.po
+++ b/docs/reference/src/main/docbook/de-DE/ri-spi.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: ri-spi\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-05 14:40+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -33,7 +33,7 @@ msgstr "Laden von Ressourcen"
#. Tag: para
#, no-c-format
-msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the "Weld: Servlets" extension will be sufficient, and will work in any container supporting the Servlet API."
+msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the \"Weld: Servlets\" extension will be sufficient, and will work in any container supporting the Servlet API."
msgstr ""
#. Tag: para
@@ -58,7 +58,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
+msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
msgstr ""
#. Tag: para
@@ -78,7 +78,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
+msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
msgstr ""
#. Tag: para
@@ -98,7 +98,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
+msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
msgstr ""
#. Tag: para
@@ -108,12 +108,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
+msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
+msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
msgstr ""
#. Tag: para
@@ -128,7 +128,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
+msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
msgstr ""
#. Tag: para
@@ -158,7 +158,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
+msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
msgstr ""
#. Tag: para
@@ -198,7 +198,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
+msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
msgstr ""
#. Tag: title
@@ -213,7 +213,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
+msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
msgstr ""
#. Tag: para
@@ -278,7 +278,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); intercepter will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
+msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); interceptor will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
msgstr ""
#. Tag: para
@@ -353,7 +353,7 @@ msgstr "Der Applikationskontext"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
+msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
msgstr "Web Beans erwartet, dass der Applikations-Server oder anderer Container den Speicher für den Kontext jeder Applikation bereitstellt. Der org.jboss.webbeans.context.api.BeanStore sollte implementiert sein, um einen durch die Applikation begrenzten Speicher bereitzustellen. Vielleicht finden Sie in diesem Zusammenhang org.jboss.webbeans.context.api.helpers.ConcurrentHashMapBeanStore hilfreich."
#. Tag: title
@@ -368,7 +368,7 @@ msgstr "Das org.jboss.webbeans.bootstrap.api.Bootstrap-Interf
#. Tag: para
#, fuzzy, no-c-format
-msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programtically, or built in). Bean validation will validate all beans."
+msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programmatically, or built in). Bean validation will validate all beans."
msgstr "Der Bootstrap ist in Phasen aufgeteilt, Bootstrap Initialisierung und Bootstrap. Die Initialisierung erstellt einen Manager und fügt die Standard-Kontexte (spezifikationsdefiniert) hinzu. Bootstrap findet EJBs, Klassen und XML auf; fügt unter Verwendung von Annotationen definierte Beans hinzu; fügt unter Verwendung von XML definierte Beans hinzu; und validiert alle Beans."
#. Tag: para
@@ -428,7 +428,7 @@ msgstr "Klassenlader-Isolierung"
#. Tag: para
#, fuzzy, no-c-format
-msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuation, classloader isolation for each CDI application."
+msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuration, classloader isolation for each CDI application."
msgstr "Falls Sie die Web Beans RI in eine Umgebung integrieren, die das Deployment mehrerer Anwendungen unterstützt, so müssen Sie automatisch oder über Benutzerkonfiguration die Klassenlader-Isolierung für jede Web Beans Anwendung aktivieren."
#. Tag: term
@@ -443,7 +443,7 @@ msgstr "Falls Sie Web Beans in eine Servlet Umgebung integrieren, müssen Sie WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
+msgid "You must ensure that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
msgstr ""
#. Tag: term
@@ -584,7 +584,7 @@ msgid ""
"InjectionTarget it = weldBeanManager.fireProcessInjectionTarget(clazz);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
+"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
"\n"
"// Produce the instance, performing any constructor injection required\n"
"Object instance = it.produce();\n"
@@ -618,16 +618,16 @@ msgstr ""
msgid ""
"// Obtain the EjbDescriptor for the EJB\n"
"// You may choose to use this utility method to get the descriptor\n"
-"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
+"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
"\n"
"// Get an the Bean object\n"
-"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
+"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
"\n"
"// Create the injection target\n"
"InjectionTarget it = deploymentBeanManager.createInjectionTarget(ejbDescriptor);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
+"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
"\n"
"// Perform injection and call initializers\n"
"it.inject(instance, cc);\n"
diff --git a/docs/reference/src/main/docbook/de-DE/scopescontexts.po b/docs/reference/src/main/docbook/de-DE/scopescontexts.po
index 582e0c3a68d..c28d8c5b178 100644
--- a/docs/reference/src/main/docbook/de-DE/scopescontexts.po
+++ b/docs/reference/src/main/docbook/de-DE/scopescontexts.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: scopescontexts\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-05 17:54+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -23,7 +23,7 @@ msgstr "Geltungsbereiche und Kontexte"
#. Tag: para
#, fuzzy, no-c-format
-msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
+msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
msgstr "Bis jetzt haben wir ein paar Beispiele von Geltungsbereichtyp-Annotationen gesehen. Der Geltungsbereich eines Web Beans bestimmt den Lebenszyklus der Instanzen des Web Beans. Der Geltungsbereich bestimmt auch, welche Clients sich auf welche Instanzen des Web Beans beziehen. Gemäß der Web Beans Spezifikation bestimmt ein Geltungsbereich:"
#. Tag: para
@@ -48,7 +48,7 @@ msgstr "Wenn wir etwa ein session-begrenztes Web Bean CurrentUser@Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
+msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
msgstr ""
#. Tag: title
@@ -58,7 +58,7 @@ msgstr "Typen von Geltungsbereichen"
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
+msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
msgstr "Web Beans besitzen ein erweiterbares Kontextmodell. Es ist möglich, neue Geltungsbereiche zu definieren, indem man eine neue Annotation für einen Geltungsbereich-Typ erstellt:"
#. Tag: programlisting
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
+msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
msgstr "Natürlich ist dies der einfache Teil des Jobs. Damit dieser Typ von Geltungsbereich von Nutzen ist, müssen wir außerdem ein Context-Objekt definieren, das den Geltungsbereich implementiert! Die Implementierung eines Context ist in der Regel ein sehr technisches Unterfangen, das nur für Framework-Entwicklung vorgesehen ist."
#. Tag: para
@@ -95,7 +95,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Usually, you'll use one of CDI's built-in scopes."
+msgid "Usually, you'll use one of CDI's built-in scopes."
msgstr "In der Regel verwenden Sie einen der eingebauten Geltungsbereiche der Web Beans."
#. Tag: title
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
+msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
msgstr "Drei der vier eingebauten Geltungsbereiche solltem jedem Java EE Entwickler sehr vertraut sein, daher wollen wir hier nicht weiter auf diese eingehen. Einer der Geltungsbereiche jedoch ist neu."
#. Tag: title
@@ -220,7 +220,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
+msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
msgstr "Eine Konversation repräsentiert aus Perspektive des Benutzers eine Aufgabe, eine Arbeitseinheit. Der Konversationskontext enthält den Status dessen, woran der Benutzer gerade arbeitet. Arbeitet der Benutzer gleichzeitig an mehreren Dingen, so existieren mehrere Konversationen."
#. Tag: para
@@ -343,25 +343,25 @@ msgstr "Daher pflanzt das folgende Link die Konversation fort:"
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "<a href="/addProduct.jsp?cid=#{conversation.id}">Add Product</a>"
+msgid "<a href=\"/addProduct.jsp?cid=#{conversation.id}\">Add Product</a>"
msgstr "Add Product]]>"
#. Tag: para
#, no-c-format
-msgid "It's probably better to use one of the link components in JSF 2:"
+msgid "It's probably better to use one of the link components in JSF 2:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:link outcome="/addProduct.xhtml" value="Add Product">\n"
-" <f:param name="cid" value="#{javax.enterprise.context.conversation.id}"/>\n"
-"</h:link>"
+"<h:link outcome=\"/addProduct.xhtml\" value=\"Add Product\">\n"
+" <f:param name=\"cid\" value=\"#{javax.enterprise.context.conversation.id}\"/>\n"
+"</h:link>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a "flash" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
+msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a \"flash\" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
msgstr "Der Web Bean Manager muss auch Konversationen über ein Redirect fortpflanzen, selbst wenn die Konversation nicht als lange laufend gekennzeichnet ist. Dies macht die Implementierung des POST-then-redirect Musters sehr einfach, ohne dass man sich auf anfällige Konstrukte wie etwa ein \"Flash\"-Objekt stützen müsste. In tdiesem Fall fügt der Web Bean Manager automatisch einen Anfragenparameter hinzu, um die URL umzuleiten."
#. Tag: title
@@ -371,7 +371,7 @@ msgstr "Konversations-Timeout"
#. Tag: para
#, fuzzy, no-c-format
-msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
+msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
msgstr "Dem Web Bean Manager ist gestattet, eine Konversation und alle Stati innerhalb seines Kontexts zu jedem Zeitpunkt zu löschen, um Ressourcen zu schonen. Eine Implementierung des Web Bean Managers wird dies in der Regel auf der Basis einer Art von Timeout tun, obwohl dies nicht durch die Web Beans Spezifikation gefordert wird. Beim Timeout handelt es sich um den Zeitraum von Inaktivität, ehe die Konversation gelöscht wird."
#. Tag: para
@@ -401,12 +401,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can guess what "singleton" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
+msgid "You can guess what \"singleton\" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
+msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
msgstr ""
#. Tag: para
@@ -426,7 +426,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
+msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
msgstr ""
#. Tag: para
@@ -466,12 +466,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
+msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
+msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
msgstr ""
#. Tag: para
@@ -540,7 +540,7 @@ msgstr "In das calculator-Feld wird eine konversationsbegrenz
#. Tag: para
#, fuzzy, no-c-format
-msgid "This feature is particularly useful with producer methods, as we'll see in the next chapter."
+msgid "This feature is particularly useful with producer methods, as we'll see in ."
msgstr "Dieses Feature ist insbesondere im Zusammenhang mit Producer-Methoden von Nutzen, wie wir im folgenden Kapitel noch sehen werden."
#~ msgid "@RequestScoped"
diff --git a/docs/reference/src/main/docbook/de-DE/specialization.po b/docs/reference/src/main/docbook/de-DE/specialization.po
index 3409a88ee97..c446e276020 100644
--- a/docs/reference/src/main/docbook/de-DE/specialization.po
+++ b/docs/reference/src/main/docbook/de-DE/specialization.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: specialization\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-06 15:52+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -23,7 +23,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
+msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
msgstr ""
#. Tag: para
@@ -43,12 +43,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
+msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
+msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
msgstr ""
#. Tag: title
@@ -77,7 +77,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
+msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
msgstr "Aber in unserer Staging-Umgebung setzen wir diese Implementierung von PaymentProcessor mit einem anderen Web Bean außer Kraft:"
#. Tag: programlisting
@@ -117,12 +117,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
+msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
+msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
msgstr ""
#. Tag: programlisting
@@ -163,16 +163,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <alternatives>\n"
-" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
-" </alternatives>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <alternatives>\n"
+" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
+" </alternatives>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -197,7 +197,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
+msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
msgstr ""
#. Tag: para
@@ -257,7 +257,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
+msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/de-DE/stereotypes.po b/docs/reference/src/main/docbook/de-DE/stereotypes.po
index d0e297ad111..c30735a2e8d 100644
--- a/docs/reference/src/main/docbook/de-DE/stereotypes.po
+++ b/docs/reference/src/main/docbook/de-DE/stereotypes.po
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: stereotypes\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-06 16:50+1100\n"
"Last-Translator: \n"
"Language-Team: \n"
@@ -101,7 +101,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
+msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
msgstr ""
#. Tag: title
@@ -144,7 +144,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
+msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
msgstr ""
#. Tag: title
@@ -264,12 +264,12 @@ msgstr "Stereotypen"
#. Tag: para
#, no-c-format
-msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
+msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
+msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
msgstr ""
#. Tag: programlisting
@@ -296,7 +296,7 @@ msgstr "Standard-Stereotypen"
#. Tag: para
#, fuzzy, no-c-format
-msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
+msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
msgstr "Wir haben bereits zwei Standard-Stereotypen kennengelernt, die durch die Web Beans Spezifikation definiert werden: @Interceptor und @Decorator."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/de-DE/weldexamples.po b/docs/reference/src/main/docbook/de-DE/weldexamples.po
index a3888e8d1f1..253c84cf6b4 100644
--- a/docs/reference/src/main/docbook/de-DE/weldexamples.po
+++ b/docs/reference/src/main/docbook/de-DE/weldexamples.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
+msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
msgstr ""
#. Tag: title
@@ -31,75 +31,75 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
+msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
+msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
+msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<faces-config version="2.0"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<faces-config version=\"2.0\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd">\n"
-"</faces-config>"
+" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd\">\n"
+"</faces-config>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
+msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, there's the familiar web.xml:"
+msgid "Finally, there's the familiar web.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<web-app version="2.5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<web-app version=\"2.5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd\">\n"
" \n"
-" <display-name>weld-jsf-numberguess-war</display-name>\n"
-" <description>Weld JSF numberguess example (war)</description>\n"
+" <display-name>weld-jsf-numberguess-war</display-name>\n"
+" <description>Weld JSF numberguess example (war)</description>\n"
"\n"
-" <servlet>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
-" <load-on-startup>1</load-on-startup>\n"
-" </servlet>\n"
+" <servlet>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
+" <load-on-startup>1</load-on-startup>\n"
+" </servlet>\n"
"\n"
-" <servlet-mapping>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <url-pattern>*.jsf</url-pattern>\n"
-" </servlet-mapping>\n"
+" <servlet-mapping>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <url-pattern>*.jsf</url-pattern>\n"
+" </servlet-mapping>\n"
" \n"
-" <context-param>\n"
-" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
-" <param-value>.xhtml</param-value>\n"
-" </context-param>\n"
+" <context-param>\n"
+" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
+" <param-value>.xhtml</param-value>\n"
+" </context-param>\n"
"\n"
-" <session-config>\n"
-" <session-timeout>10</session-timeout>\n"
-" </session-config>\n"
+" <session-config>\n"
+" <session-timeout>10</session-timeout>\n"
+" </session-config>\n"
"\n"
-"</web-app>"
+"</web-app>"
msgstr ""
#. Tag: para
@@ -129,51 +129,51 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
+msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"\n"
-" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">\n"
-"<html xmlns="http://www.w3.org/1999/xhtml"\n"
-" xmlns:ui="http://java.sun.com/jsf/facelets"\n"
-" xmlns:h="http://java.sun.com/jsf/html"\n"
-" xmlns:f="http://java.sun.com/jsf/core">\n"
+"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
+" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n"
+"<html xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" xmlns:ui=\"http://java.sun.com/jsf/facelets\"\n"
+" xmlns:h=\"http://java.sun.com/jsf/html\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\">\n"
"\n"
-" <ui:composition template="/template.xhtml">\n"
-" <ui:define name="content">\n"
-" <h1>Guess a number...</h1>\n"
-" <h:form id="numberGuess">\n"
-" <div style="color: red">\n"
-" <h:messages id="messages" globalOnly="false"/>\n"
-" <h:outputText id="Higher" value="Higher!"\n"
-" rendered="#{game.number gt game.guess and game.guess ne 0}"/>\n"
-" <h:outputText id="Lower" value="Lower!"\n"
-" rendered="#{game.number lt game.guess and game.guess ne 0}"/>\n"
-" </div>\n"
+" <ui:composition template=\"/template.xhtml\">\n"
+" <ui:define name=\"content\">\n"
+" <h1>Guess a number...</h1>\n"
+" <h:form id=\"numberGuess\">\n"
+" <div style=\"color: red\">\n"
+" <h:messages id=\"messages\" globalOnly=\"false\"/>\n"
+" <h:outputText id=\"Higher\" value=\"Higher!\"\n"
+" rendered=\"#{game.number gt game.guess and game.guess ne 0}\"/>\n"
+" <h:outputText id=\"Lower\" value=\"Lower!\"\n"
+" rendered=\"#{game.number lt game.guess and game.guess ne 0}\"/>\n"
+" </div>\n"
" \n"
-" <div>\n"
-" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
+" <div>\n"
+" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
" You have #{game.remainingGuesses} guesses remaining.\n"
-" </div>\n"
+" </div>\n"
" \n"
-" <div>\n"
+" <div>\n"
" Your guess: \n"
-" <h:inputText id="inputGuess" value="#{game.guess}"\n"
-" size="3" required="true" disabled="#{game.number eq game.guess}"\n"
-" validator="#{game.validateNumberRange}"/>\n"
-" <h:commandButton id="guessButton" value="Guess" \n"
-" action="#{game.check}" disabled="#{game.number eq game.guess}"/>\n"
-" </div>\n"
-" <div>\n"
-" <h:commandButton id="restartButton" value="Reset" action="#{game.reset}" immediate="true"/>\n"
-" </div>\n"
-" </h:form>\n"
-" </ui:define>\n"
-" </ui:composition>\n"
-"</html>"
+" <h:inputText id=\"inputGuess\" value=\"#{game.guess}\"\n"
+" size=\"3\" required=\"true\" disabled=\"#{game.number eq game.guess}\"\n"
+" validator=\"#{game.validateNumberRange}\"/>\n"
+" <h:commandButton id=\"guessButton\" value=\"Guess\" \n"
+" action=\"#{game.check}\" disabled=\"#{game.number eq game.guess}\"/>\n"
+" </div>\n"
+" <div>\n"
+" <h:commandButton id=\"restartButton\" value=\"Reset\" action=\"#{game.reset}\" immediate=\"true\"/>\n"
+" </div>\n"
+" </h:form>\n"
+" </ui:define>\n"
+" </ui:composition>\n"
+"</html>"
msgstr ""
#. Tag: para
@@ -183,7 +183,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are a number of messages which can be sent to the user, "Higher!", "Lower!" and "Correct!""
+msgid "There are a number of messages which can be sent to the user, \"Higher!\", \"Lower!\" and \"Correct!\""
msgstr ""
#. Tag: para
@@ -198,7 +198,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
+msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
msgstr ""
#. Tag: para
@@ -266,7 +266,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Generator is application scoped, so we don't get a different random each time."
+msgid "The Generator is application scoped, so we don't get a different random each time."
msgstr ""
#. Tag: para
@@ -276,12 +276,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
+msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
+msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
msgstr ""
#. Tag: programlisting
@@ -298,19 +298,19 @@ msgid ""
" private int remainingGuesses;\n"
"\n"
" @Inject @MaxNumber private int maxNumber;\n"
-" @Inject @Random Instance<Integer> randomNumber;\n"
+" @Inject @Random Instance<Integer> randomNumber;\n"
" \n"
" public Game() {}\n"
" \n"
" public void check() {\n"
-" if (guess > number) {\n"
+" if (guess > number) {\n"
" biggest = guess - 1;\n"
" }\n"
-" else if (guess < number) {\n"
+" else if (guess < number) {\n"
" smallest = guess + 1;\n"
" }\n"
" else if (guess == number) {\n"
-" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage("Correct!"));\n"
+" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage(\"Correct!\"));\n"
" }\n"
" remainingGuesses--;\n"
" }\n"
@@ -325,18 +325,18 @@ msgid ""
" }\n"
" \n"
" public void validateNumberRange(FacesContext context, UIComponent toValidate, Object value) {\n"
-" if (remainingGuesses <= 0) {\n"
-" FacesMessage message = new FacesMessage("No guesses left!");\n"
+" if (remainingGuesses <= 0) {\n"
+" FacesMessage message = new FacesMessage(\"No guesses left!\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" ((UIInput) toValidate).setValid(false);\n"
" return;\n"
" }\n"
" int input = (Integer) value;\n"
"\n"
-" if (input < smallest || input > biggest) {\n"
+" if (input < smallest || input > biggest) {\n"
" ((UIInput) toValidate).setValid(false);\n"
"\n"
-" FacesMessage message = new FacesMessage("Invalid guess");\n"
+" FacesMessage message = new FacesMessage(\"Invalid guess\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" }\n"
" }\n"
@@ -385,20 +385,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
+msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
+msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
msgstr ""
#. Tag: title
@@ -418,17 +418,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin ."
+msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects . Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
+msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects. Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This will create a project in your workspace called weld-se-numberguess ."
+msgid "This will create a project in your workspace called weld-se-numberguess."
msgstr ""
#. Tag: para
@@ -438,7 +438,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to get the example running!"
+msgid "It's time to get the example running!"
msgstr ""
#. Tag: title
@@ -448,12 +448,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
+msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right click on the project, and choose Run As -> Run As Application:"
+msgid "Right click on the project, and choose Run As -> Run As Application:"
msgstr ""
#. Tag: para
@@ -503,7 +503,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's have a look at the significant code and configuration files that make up this example."
+msgid "Let's have a look at the significant code and configuration files that make up this example."
msgstr ""
#. Tag: para
@@ -513,7 +513,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
+msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
msgstr ""
#. Tag: programlisting
@@ -558,7 +558,7 @@ msgid ""
"\n"
" public boolean isGameLost()\n"
" {\n"
-" return guess != number && remainingGuesses <= 0;\n"
+" return guess != number && remainingGuesses <= 0;\n"
" }\n"
"\n"
" public boolean check()\n"
@@ -567,12 +567,12 @@ msgid ""
"\n"
" if (checkNewNumberRangeIsValid())\n"
" {\n"
-" if (guess > number)\n"
+" if (guess > number)\n"
" {\n"
" biggest = guess - 1;\n"
" }\n"
"\n"
-" if (guess < number)\n"
+" if (guess < number)\n"
" {\n"
" smallest = guess + 1;\n"
" }\n"
@@ -590,7 +590,7 @@ msgid ""
"\n"
" private boolean checkNewNumberRangeIsValid()\n"
" {\n"
-" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
+" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
" }\n"
"\n"
" @PostConstruct\n"
@@ -607,12 +607,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
+msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
+msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
msgstr ""
#. Tag: para
@@ -642,12 +642,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
+msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
+msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
msgstr ""
#. Tag: programlisting
@@ -660,11 +660,11 @@ msgid ""
"\n"
" public String getChallengeMessage()\n"
" {\n"
-" StringBuilder challengeMsg = new StringBuilder("I'm thinking of a number between ");\n"
+" StringBuilder challengeMsg = new StringBuilder(\"I'm thinking of a number between \");\n"
" challengeMsg.append(game.getSmallest());\n"
-" challengeMsg.append(" and ");\n"
+" challengeMsg.append(\" and \");\n"
" challengeMsg.append(game.getBiggest());\n"
-" challengeMsg.append(". Can you guess what it is?");\n"
+" challengeMsg.append(\". Can you guess what it is?\");\n"
"\n"
" return challengeMsg.toString();\n"
" }\n"
@@ -673,34 +673,34 @@ msgid ""
" {\n"
" if (game.isGameWon())\n"
" {\n"
-" return "You guessed it! The number was " + game.getNumber();\n"
+" return \"You guessed it! The number was \" + game.getNumber();\n"
" }\n"
" else if (game.isGameLost())\n"
" {\n"
-" return "You are fail! The number was " + game.getNumber();\n"
+" return \"You are fail! The number was \" + game.getNumber();\n"
" }\n"
" else if (!game.isValidNumberRange())\n"
" {\n"
-" return "Invalid number range!";\n"
+" return \"Invalid number range!\";\n"
" }\n"
" else if (game.getRemainingGuesses() == Game.MAX_NUM_GUESSES)\n"
" {\n"
-" return "What is your first guess?";\n"
+" return \"What is your first guess?\";\n"
" }\n"
" else\n"
" {\n"
" String direction = null;\n"
"\n"
-" if (game.getGuess() < game.getNumber())\n"
+" if (game.getGuess() < game.getNumber())\n"
" {\n"
-" direction = "Higher";\n"
+" direction = \"Higher\";\n"
" }\n"
" else\n"
" {\n"
-" direction = "Lower";\n"
+" direction = \"Lower\";\n"
" }\n"
"\n"
-" return direction + "! You have " + game.getRemainingGuesses() + " guesses left.";\n"
+" return direction + \"! You have \" + game.getRemainingGuesses() + \" guesses left.\";\n"
" }\n"
" }\n"
"}"
@@ -713,7 +713,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
+msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
msgstr ""
#. Tag: para
@@ -783,7 +783,7 @@ msgid ""
" private void refreshUI() {\n"
" mainLabel.setText( msgGenerator.getChallengeMessage() );\n"
" messageLabel.setText( msgGenerator.getResultMessage() );\n"
-" guessText.setText( "" );\n"
+" guessText.setText( \"\" );\n"
" guessesLeftBar.setValue( game.getRemainingGuesses() );\n"
" guessText.requestFocus();\n"
" }\n"
@@ -818,7 +818,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
+msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
msgstr ""
#. Tag: para
@@ -828,7 +828,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Calls game.check() to validate and perform one 'turn' of the game"
+msgid "Calls game.check() to validate and perform one 'turn' of the game"
msgstr ""
#. Tag: para
@@ -853,7 +853,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
+msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
msgstr ""
#. Tag: para
@@ -863,25 +863,25 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
+msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<plugin>\n"
-" <groupId>org.apache.maven.plugins</groupId>\n"
-" <artifactId>maven-ear-plugin</artifactId>\n"
-" <configuration>\n"
-" <modules>\n"
-" <webModule>\n"
-" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
-" <artifactId>weld-jsf-translator-war</artifactId>\n"
-" <contextRoot>/weld-translator</contextRoot>\n"
-" </webModule>\n"
-" </modules>\n"
-" </configuration>\n"
-"</plugin>"
+"<plugin>\n"
+" <groupId>org.apache.maven.plugins</groupId>\n"
+" <artifactId>maven-ear-plugin</artifactId>\n"
+" <configuration>\n"
+" <modules>\n"
+" <webModule>\n"
+" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
+" <artifactId>weld-jsf-translator-war</artifactId>\n"
+" <contextRoot>/weld-translator</contextRoot>\n"
+" </webModule>\n"
+" </modules>\n"
+" </configuration>\n"
+"</plugin>"
msgstr ""
#. Tag: para
@@ -891,72 +891,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
+msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<application version="5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<application version=\"5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/application_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/application_5.xsd\">\n"
"\n"
-" <display-name>weld-jsf-translator-ear</display-name>\n"
-" <description>The Weld JSF translator example (ear)</description>\n"
+" <display-name>weld-jsf-translator-ear</display-name>\n"
+" <description>The Weld JSF translator example (ear)</description>\n"
" \n"
-" <module>\n"
-" <web>\n"
-" <web-uri>weld-translator.war</web-uri>\n"
-" <context-root>/weld-translator</context-root>\n"
-" </web>\n"
-" </module>\n"
-" <module>\n"
-" <ejb>weld-translator.jar</ejb>\n"
-" </module>\n"
-"</application>"
+" <module>\n"
+" <web>\n"
+" <web-uri>weld-translator.war</web-uri>\n"
+" <context-root>/weld-translator</context-root>\n"
+" </web>\n"
+" </module>\n"
+" <module>\n"
+" <ejb>weld-translator.jar</ejb>\n"
+" </module>\n"
+"</application>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
+msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (ommitted here for brevity):"
+msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (omitted here for brevity):"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:form id="translator">\n"
+"<h:form id=\"translator\">\n"
"\n"
-" <table>\n"
-" <tr align="center" style="font-weight: bold">\n"
-" <td>\n"
+" <table>\n"
+" <tr align=\"center\" style=\"font-weight: bold\">\n"
+" <td>\n"
" Your text\n"
-" </td>\n"
-" <td>\n"
+" </td>\n"
+" <td>\n"
" Translation\n"
-" </td>\n"
-" </tr>\n"
-" <tr>\n"
-" <td>\n"
-" <h:inputTextarea id="text" value="#{translator.text}" required="true" rows="5" cols="80"/>\n"
-" </td>\n"
-" <td>\n"
-" <h:outputText value="#{translator.translatedText}"/>\n"
-" </td>\n"
-" </tr>\n"
-" </table>\n"
-" <div>\n"
-" <h:commandButton id="button" value="Translate" action="#{translator.translate}"/>\n"
-" </div>\n"
+" </td>\n"
+" </tr>\n"
+" <tr>\n"
+" <td>\n"
+" <h:inputTextarea id=\"text\" value=\"#{translator.text}\" required=\"true\" rows=\"5\" cols=\"80\"/>\n"
+" </td>\n"
+" <td>\n"
+" <h:outputText value=\"#{translator.translatedText}\"/>\n"
+" </td>\n"
+" </tr>\n"
+" </table>\n"
+" <div>\n"
+" <h:commandButton id=\"button\" value=\"Translate\" action=\"#{translator.translate}\"/>\n"
+" </div>\n"
" \n"
-"</h:form>"
+"</h:form>"
msgstr ""
#. Tag: para
@@ -966,12 +966,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
+msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
+msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
msgstr ""
#. Tag: para
@@ -995,7 +995,7 @@ msgid ""
" public String translate(String text) { \n"
" StringBuilder sb = new StringBuilder(); \n"
" for (String sentence: sentenceParser.parse(text)) { \n"
-" sb.append(translator.translate(sentence)).append(". "); \n"
+" sb.append(translator.translate(sentence)).append(\". \"); \n"
" } \n"
" return sb.toString().trim(); \n"
" }\n"
@@ -1005,7 +1005,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
+msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
msgstr ""
#. Tag: programlisting
@@ -1015,7 +1015,7 @@ msgid ""
"public class SentenceTranslator implements Translator { \n"
"\n"
" public String translate(String sentence) { \n"
-" return "Lorem ipsum dolor sit amet"; \n"
+" return \"Lorem ipsum dolor sit amet\"; \n"
" }\n"
"\n"
"}"
@@ -1031,7 +1031,7 @@ msgstr ""
msgid ""
"@Stateful\n"
"@RequestScoped\n"
-"@Named("translator")\n"
+"@Named(\"translator\")\n"
"public class TranslatorControllerBean implements TranslatorController {\n"
"\n"
" @Inject private TextTranslator translator;\n"
diff --git a/docs/reference/src/main/docbook/en-US/environments.xml b/docs/reference/src/main/docbook/en-US/environments.xml
index e2638349f76..00a8e0815b7 100644
--- a/docs/reference/src/main/docbook/en-US/environments.xml
+++ b/docs/reference/src/main/docbook/en-US/environments.xml
@@ -1,119 +1,144 @@
+ "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]>
- Application servers and environments supported by Weld
-
-
- Using Weld with JBoss AS
-
-
- If you are using JBoss AS 6.0, no additional configuration is required to use Weld (or CDI for that matter).
- All you need to do is make your application a bean bean archive by adding META-INF/beans.xml
- to the classpath or WEB-INF/beans.xml to the web root!
-
-
-
-
- Additionally, Weld Servlet supports JBoss EAP 5.1, to do this use the jboss5 variant
- of Weld Servlet.
-
-
-
-
-
-
- GlassFish
-
-
- Weld is also built into GlassFish from V3 onwards. Since GlassFish V3 is the Java EE 6 reference
- implementation, it must support all features of CDI. What better way for GlassFish to support these features
- than to use Weld, the JSR-299 reference implementation? Just package up your CDI application and deploy.
-
-
-
-
- Servlet containers (such as Tomcat or Jetty)
-
-
- While JSR-299 does not require support for servlet environments, Weld can be used in a servlet container,
- such as Tomcat 6.0 or Jetty 6.1.
-
-
-
-
- There is a major limitation to using a servlet container. Weld doesn't support deploying session beans,
- injection using @EJB or @PersistenceContext, or using transactional
- events in servlet containers. For enterprise features such as these, you should really be looking at a Java
- EE application server.
-
-
-
-
- Weld can be used as a library in an web application that is deployed to a Servlet container. You should place
- weld-servlet.jar within the WEB-INF/lib directory relative to the web
- root. weld-servlet.jar is an "uber-jar", meaning it bundles all the bits of Weld and CDI
- required for running in a Servlet container, for your convenience. Alternatively, you can use its component
- jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file
- inside the weld-servlet.jar artifact.
-
-
-
- You also need to explicitly specify the servlet listener (used to boot Weld, and control its interaction
- with requests) in WEB-INF/web.xml in the web root:
-
-
-
+ Application servers and environments supported by Weld
+
+
+ Using Weld with JBoss AS
+
+
+ If you are using JBoss AS 6.0, no additional configuration is required to use Weld (or CDI for that matter).
+ All you need to do is make your application a bean bean archive by adding
+ META-INF/beans.xml
+ to the classpath or
+ WEB-INF/beans.xml
+ to the web root!
+
+
+
+
+ Additionally, Weld Servlet supports JBoss EAP 5.1, to do this use the
+ jboss5
+ variant
+ of Weld Servlet.
+
+
+
+
+
+
+ GlassFish
+
+
+ Weld is also built into GlassFish from V3 onwards. Since GlassFish V3 is the Java EE 6 reference
+ implementation, it must support all features of CDI. What better way for GlassFish to support these features
+ than to use Weld, the JSR-299 reference implementation? Just package up your CDI application and deploy.
+
+
+
+
+ Servlet containers (such as Tomcat or Jetty)
+
+
+ While JSR-299 does not require support for servlet environments, Weld can be used in a servlet container,
+ such as Tomcat 6.0 or Jetty 6.1.
+
+
+
+
+ There is a major limitation to using a servlet container. Weld doesn't support deploying session beans,
+ injection using
+ @EJB
+ or@PersistenceContext, or using transactional
+ events in servlet containers. For enterprise features such as these, you should really be looking at a
+ Java
+ EE application server.
+
+
+
+
+ Weld can be used as a library in an web application that is deployed to a Servlet container. You should
+ place
+ weld-servlet.jar
+ within the
+ WEB-INF/lib
+ directory relative to the web
+ root.
+ weld-servlet.jar
+ is an "uber-jar", meaning it bundles all the bits of Weld and CDI
+ required for running in a Servlet container, for your convenience. Alternatively, you can use its component
+ jars. A list of transitive dependencies can be found in the
+ META-INF/DEPENDENCIES.txt
+ file
+ inside the
+ weld-servlet.jar
+ artifact.
+
+
+
+ You also need to explicitly specify the servlet listener (used to boot Weld, and control its interaction
+ with requests) in
+ WEB-INF/web.xml
+ in the web root:
+
+
+ org.jboss.weld.environment.servlet.Listener
]]>
-
- Tomcat
+
+ Tomcat
-
- Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind
- the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with
- the following contents:
-
-
-
+
+ Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind
+ the BeanManager into JNDI, you should populate
+ META-INF/context.xml
+ in the web root with
+ the following contents:
+
+
+
]]>
-
- and make it available to your deployment by adding this to the bottom of web.xml:
-
-
-
+
+ and make it available to your deployment by adding this to the bottom ofweb.xml:
+
+
+ BeanManager
javax.enterprise.inject.spi.BeanManager
]]>
-
- Tomcat only allows you to bind entries to java:comp/env, so the BeanManager will be
- available at java:comp/env/BeanManager
-
-
-
- Weld also supports Servlet injection in Tomcat 6.
-
-
-
-
-
- Jetty
-
-
- Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To
- bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with
- the following contents:
-
-
-
+ Tomcat only allows you to bind entries tojava:comp/env, so the BeanManager will be
+ available at
+ java:comp/env/BeanManager
+
+
+
+ Weld also supports Servlet injection in Tomcat 6.
+
+
+
+
+
+ Jetty
+
+
+ Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To
+ bind the BeanManager to JNDI in Jetty 6, you should populate
+ WEB-INF/jetty-env.xml
+ with
+ the following contents:
+
+
+
@@ -129,12 +154,12 @@
]]>
-
- Jetty 7 has moved to the Eclipse Foundation; if you are using Jetty 7 put the following in your
- WEB-INF/jetty-env.xml:
-
-
-
+ Jetty 7 has moved to the Eclipse Foundation; if you are using Jetty 7 put the following in your
+ WEB-INF/jetty-env.xml:
+
+
+
@@ -151,34 +176,40 @@
]]>
-
- Just like in Tomcat, you need to make it available to your deployment by adding this to the bottom of web.xml:
-
-
-
+
+ Just like in Tomcat, you need to make it available to your deployment by adding this to the bottom of
+ web.xml:
+
+
+ BeanManager
javax.enterprise.inject.spi.BeanManager
]]>
-
- Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory
- like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap
- around it.
-
+
+ Notice that Jetty doesn't not have built-in support for an
+ javax.naming.spi.ObjectFactory
+ like Tomcat, so it's necessary to manually create the
+ javax.naming.Reference
+ to wrap
+ around it.
+
-
- Jetty only allows you to bind entries to java:comp/env, so the BeanManager will be
- available at java:comp/env/BeanManager
-
+
+ Jetty only allows you to bind entries tojava:comp/env, so the BeanManager will be
+ available at
+ java:comp/env/BeanManager
+
-
- Weld also supports Servlet injection in Jetty 6. To enable this, add the file
- WEB-INF/jetty-web.xml with the following content to your war:
-
+
+ Weld also supports Servlet injection in Jetty 6. To enable this, add the file
+ WEB-INF/jetty-web.xml
+ with the following content to your war:
+
-
@@ -186,100 +217,109 @@
]]>
-
-
-
-
-
- Java SE
-
-
- In addition to improved integration of the Enterprise Java stack, the "Contexts and Dependency Injection for
- the Java EE platform" specification also defines a state of the art typesafe, stateful dependency injection
- framework, which can prove useful in a wide range of application types. To help developers take advantage of
- this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment
- independently of any Java EE APIs.
-
-
-
- When executing in the SE environment the following features of Weld are available:
-
-
-
-
-
- Managed beans with @PostConstruct and @PreDestroy
- lifecycle callbacks
-
-
-
-
- Dependency injection with qualifiers and alternatives
-
-
-
-
- @Application, @Dependent and
- @Singleton scopes
-
-
-
-
- Interceptors and decorators
-
-
-
-
- Stereotypes
-
-
-
+
+
+
+
+
+ Java SE
+
+
+ In addition to improved integration of the Enterprise Java stack, the "Contexts and Dependency Injection for
+ the Java EE platform" specification also defines a state of the art typesafe, stateful dependency injection
+ framework, which can prove useful in a wide range of application types. To help developers take advantage of
+ this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment
+ independently of any Java EE APIs.
+
+
+
+ When executing in the SE environment the following features of Weld are available:
+
+
+
+
+
+ Managed beans with
+ @PostConstruct
+ and
+ @PreDestroy
+ lifecycle callbacks
+
+
+
+
+ Dependency injection with qualifiers and alternatives
+
+
+
+
+ @Application,
+ @Dependent
+ and
+ @Singleton
+ scopes
+
+
+
+
+ Interceptors and decorators
+
+
+
+
+ Stereotypes
+
+
+
+
+ Events
+
+
+
+
+ Portable extension support
+
+
+
+
+
+ EJB beans are not supported.
+
+
+
+ CDI SE Module
+
- Events
+ Weld provides an extension which will boot a CDI bean manager in Java SE, automatically registering all
+ simple beans found on the classpath. The command line parameters can be injected using either of the
+ following:
-
-
+
+ params;]]>
+
+
+
- Portable extension support
+ The second form is useful for compatibility with existing classes.
-
-
-
-
- EJB beans are not supported.
-
-
-
- CDI SE Module
-
-
- Weld provides an extension which will boot a CDI bean manager in Java SE, automatically registering all
- simple beans found on the classpath. The command line parameters can be injected using either of the following:
-
-
- params;]]>
-
-
-
-
- The second form is useful for compatibility with existing classes.
-
-
-
+
+
+
+ The command line parameters do not become available for injection until the
+ ContainerInitialized
+ event is fired. If you need access to the parameters during
+ initialization you can do so via the
+ public static String[] getParameters()
+ method in
+ StartMain.
+
+
+
- The command line parameters do not become available for injection until the
- ContainerInitialized event is fired. If you need access to the parameters during
- initialization you can do so via the
- public static String[] getParameters() method in
- StartMain.
+ Here's an example of a simple CDI SE application:
-
-
-
- Here's an example of a simple CDI SE application:
-
- parameters) {
@@ -287,10 +327,10 @@ public class HelloWorld
}
}]]>
-
+
+
+
-
-
Bootstrapping CDI SE
@@ -299,34 +339,44 @@ public class HelloWorld
- The ContainerInitialized Event
+ The ContainerInitialized Event
-
- Thanks to the power of CDI's typesafe event model, application developers
- need not write any bootstrapping code. The Weld SE module comes
- with a built-in main method which will bootstrap CDI for you and
- then fire a ContainerInitialized event. The entry
- point for your application code would therefore be a simple bean which observes
- the ContainerInitialized event, as in the previous example.
+
+ Thanks to the power of CDI's typesafe event model, application developers
+ need not write any bootstrapping code. The Weld SE module comes
+ with a built-in main method which will bootstrap CDI for you and
+ then fire a
+ ContainerInitialized
+ event. The entry
+ point for your application code would therefore be a simple bean which observes
+ the
+ ContainerInitialized
+ event, as in the previous example.
+
- In this case your application can be started by calling the provided
- main method like so:
+ In this case your application can be started by calling the provided
+ main method like so:
+
- ]]>
+
+ ]]>
- Programmatic Bootstrap API
+ Programmatic Bootstrap API
- For added flexibility, CDI SE also comes with a bootstrap API
- which can be called from within your application in order to initialize
- CDI and obtain references to your application's beans and events. The
- API consists of two classes: Weld and
- WeldContainer.
+ For added flexibility, CDI SE also comes with a bootstrap API
+ which can be called from within your application in order to initialize
+ CDI and obtain references to your application's beans and events. The
+ API consists of two classes:
+ Weld
+ and
+ WeldContainer.
+
-
-
- Here's an example application main method which uses this API
- to initialize a bean of type MyApplicationBean.
+ Here's an example application main method which uses this API
+ to initialize a bean of typeMyApplicationBean.
+
-
- Alternatively the application could be started by firing a custom
- event which would then be observed by another simple bean. The following
- example fires MyEvent on startup.
-
- Alternatively the application could be started by firing a custom
+ event which would then be observed by another simple bean. The following
+ example fires
+ MyEvent
+ on startup.
+
+
+
-
+
-
+ Thread ContextIn contrast to Java EE applications, Java SE applications place no restrictions
- on developers regarding the creation and usage of threads.
- Therefore Weld SE provides a custom scope annotation, @ThreadScoped,
- and corresponding context implementation which can be used to bind bean instances
- to the current thread. It is intended to be used in scenarios where you might otherwise
- use ThreadLocal, and does in fact use
- ThreadLocal under the hood.
+ on developers regarding the creation and usage of threads.
+ Therefore Weld SE provides a custom scope annotation,@ThreadScoped,
+ and corresponding context implementation which can be used to bind bean instances
+ to the current thread. It is intended to be used in scenarios where you might otherwise
+ useThreadLocal, and does in fact use
+ ThreadLocal
+ under the hood.
- To use the @ThreadScoped annotation you need to enable the RunnableDecorator
- which 'listens' for all executions of Runnable.run() and
- decorates them by setting up the thread context beforehand, bound to
- the current thread, and destroying the context afterwards.
+ To use the @ThreadScoped annotation you need to enable the
+ RunnableDecorator
+ which 'listens' for all executions of
+ Runnable.run()
+ and
+ decorates them by setting up the thread context beforehand, bound to
+ the current thread, and destroying the context afterwards.
-
+
- org.jboss.weld.environment.se.threading.RunnableDecorator
+ org.jboss.weld.environment.se.threading.RunnableDecorator
]]>
- It is not necessary to use @ThreadScoped in all
- multithreaded applications. The thread context is not intended
- as a replacement for defining your own application-specific contexts.
- It is generally only useful in situations where you would otherwise
- have used ThreadLocal directly, which are typically rare.
-
+ It is not necessary to use @ThreadScoped in all
+ multithreaded applications. The thread context is not intended
+ as a replacement for defining your own application-specific contexts.
+ It is generally only useful in situations where you would otherwise
+ have used ThreadLocal directly, which are typically rare.
+
-
+ Setting the ClasspathWeld SE comes packaged as a 'shaded' jar which includes the CDI API,
- Weld Core and all dependant classes bundled into a single jar. Therefore the
- only Weld jar you need on the classpath, in addition to your application's
- classes and dependant jars, is the Weld SE jar. If you are working with a pure
- Java SE application you launch using java, this may be simpler
- for you.
+ Weld Core and all dependant classes bundled into a single jar. Therefore the
+ only Weld jar you need on the classpath, in addition to your application's
+ classes and dependant jars, is the Weld SE jar. If you are working with a pure
+ Java SE application you launch usingjava, this may be simpler
+ for you.
-
+
- If you prefer to work with individual dependencies, then you can use the
- weld-core jar which just contains the Weld SE classes.
- Of course in this mode you will need to assemble the classpath yourself.
- This mode is useful, for example, if you wish to use an alternative slf4j
- log binding.
+ If you prefer to work with individual dependencies, then you can use the
+ weld-core
+ jar which just contains the Weld SE classes.
+ Of course in this mode you will need to assemble the classpath yourself.
+ This mode is useful, for example, if you wish to use an alternative slf4j
+ log binding.
-
+
- If you work with a dependency management solution such as
- Maven you can declare a dependency on org.jboss.weld.se:weld-se-core.
+ If you work with a dependency management solution such as
+ Maven you can declare a dependency onorg.jboss.weld.se:weld-se-core.
-
+
-
+
diff --git a/docs/reference/src/main/docbook/en-US/injection.xml b/docs/reference/src/main/docbook/en-US/injection.xml
index 2aeae503e6a..5bf30aca598 100644
--- a/docs/reference/src/main/docbook/en-US/injection.xml
+++ b/docs/reference/src/main/docbook/en-US/injection.xml
@@ -1,26 +1,31 @@
+ "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]>
- Dependency injection and programmatic lookup
-
-
- One of the most significant features of CDI—certainly the most recognized—is dependency injection;
- excuse me, typesafe dependency injection.
-
-
-
- Injection points
-
-
- The @Inject annotation lets us define an injection point that is injected during bean
- instantiation. Injection can occur via three different mechanisms.
-
-
-
- Bean constructor parameter injection:
-
-
- Dependency injection and programmatic lookup
+
+
+ One of the most significant features of CDI—certainly the most recognized—is dependency injection;
+ excuse me,
+ typesafe
+ dependency injection.
+
+
+
+ Injection points
+
+
+ The
+ @Inject
+ annotation lets us define an injection point that is injected during bean
+ instantiation. Injection can occur via three different mechanisms.
+
+
+
+ Bean constructor
+ parameter injection:
+
+
+
-
- A bean can only have one injectable constructor.
-
+
+ A bean can only have one injectable constructor.
+
-
- Initializer method parameter injection:
-
+
+ Initializer method
+ parameter injection:
+
-
-
-
- A bean can have multiple initializer methods. If the bean is a session bean, the initializer method
- is not required to be a business method of the session bean.
-
-
+
+
+ A bean can have multiple initializer methods. If the bean is a session bean, the initializer method
+ is not required to be a business method of the session bean.
+
+
-
- And direct field injection:
-
+
+ And direct field injection:
+
-
-
-
- Getter and setter methods are not required for field injection to work (unlike with JSF managed beans).
-
-
-
-
- Dependency injection always occurs when the bean instance is first instantiated by the container.
- Simplifying just a little, things happen in this order:
-
-
-
-
-
- First, the container calls the bean constructor (the default constructor or the one annotated
- @Inject), to obtain an instance of the bean.
-
-
-
-
- Next, the container initializes the values of all injected fields of the bean.
-
-
-
+
- Next, the container calls all initializer methods of bean (the call order is not portable, don't
- rely on it).
+ Getter and setter methods are not required for field injection to work (unlike with JSF managed beans).
-
-
+
+
+
+ Dependency injection always occurs when the bean instance is first instantiated by the container.
+ Simplifying just a little, things happen in this order:
+
+
+
+
+
+ First, the container calls the bean constructor (the default constructor or the one annotated
+ @Inject), to obtain an instance of the bean.
+
+
+
+
+ Next, the container initializes the values of all injected fields of the bean.
+
+
+
+
+ Next, the container calls all initializer methods of bean (the call order is not portable, don't
+ rely on it).
+
+
+
+
+ Finally, the
+ @PostConstruct
+ method, if any, is called.
+
+
+
+
+ (The only complication is that the container might call initializer methods declared by a superclass
+ before initializing injected fields declared by a subclass.)
+
+
+
- Finally, the @PostConstruct method, if any, is called.
+ One major advantage of constructor injection is that it allows the bean to be immutable.
-
-
-
- (The only complication is that the container might call initializer methods declared by a superclass
- before initializing injected fields declared by a subclass.)
-
-
-
- One major advantage of constructor injection is that it allows the bean to be immutable.
-
-
-
-
- CDI also supports parameter injection for some other methods that are invoked by the container. For instance,
- parameter injection is supported for producer methods:
-
-
-
+
+
+ CDI also supports parameter injection for some other methods that are invoked by the container. For
+ instance,
+ parameter injection is supported for producer methods:
+
+
+
-
- This is a case where the @Inject annotation is not required at the
- injection point. The same is true for observer methods (which we'll meet in ) and
- disposer methods.
-
-
-
-
- What gets injected
-
-
- The CDI specification defines a procedure, called typesafe resolution, that the container
- follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but
- once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization
- time, which means that the container will inform the developer immediately if a bean's
- dependencies cannot be satisfied.
-
-
-
- The purpose of this algorithm is to allow multiple beans to implement the same bean type and either:
-
-
-
-
-
- allow the client to select which implementation it requires using a qualifier or
-
-
-
-
- allow the application deployer to select which implementation is appropriate for a particular deployment,
- without changes to the client, by enabling or disabling an alternative, or
-
-
-
-
- allow the beans to be isolated into separate modules.
-
-
-
-
-
- Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is
- going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll
- likely have lots of those.
-
-
-
- But then, things start to get complicated. Let's explore how the container determines which bean to inject in
- more advanced cases. We'll start by taking a closer look at qualifiers.
-
-
-
-
-
- Qualifier annotations
-
-
- If we have more than one bean that implements a particular bean type, the injection point can specify exactly
- which bean should be injected using a qualifier annotation. For example, there might be two implementations of
- PaymentProcessor:
-
-
-
+ This is a case where the
+ @Inject
+ annotation
+ is not
+ required at the
+ injection point. The same is true for observer methods (which we'll meet in) and
+ disposer methods.
+
+
+
+
+ What gets injected
+
+
+ The CDI specification defines a procedure, calledtypesafe resolution, that the
+ container
+ follows when identifying the bean to inject to an injection point. This algorithm looks complex at first,
+ but
+ once you understand it, it's really quite intuitive. Typesafe resolution is performed at system
+ initialization
+ time, which means that the container will inform the developer immediately if a bean's
+ dependencies cannot be satisfied.
+
+
+
+ The purpose of this algorithm is to allow multiple beans to implement the same bean type and either:
+
+
+
+
+
+ allow the client to select which implementation it requires using a
+ qualifier
+ or
+
+
+
+
+ allow the application deployer to select which implementation is appropriate for a particular
+ deployment,
+ without changes to the client, by enabling or disabling analternative, or
+
+
+
+
+ allow the beans to be isolated into separate modules.
+
+
+
+
+
+ Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then
+ bean A is
+ going to go into slot A. That's the simplest possible scenario. When you first start your application,
+ you'll
+ likely have lots of those.
+
+
+
+ But then, things start to get complicated. Let's explore how the container determines which bean to inject
+ in
+ more advanced cases. We'll start by taking a closer look at qualifiers.
+
+
+
+
+
+ Qualifier annotations
+
+
+ If we have more than one bean that implements a particular bean type, the injection point can specify
+ exactly
+ which bean should be injected using a qualifier annotation. For example, there might be two implementations
+ of
+ PaymentProcessor:
+
+
+
+}]]>
-
-
- Where @Synchronous and @Asynchronous are qualifier annotations:
-
+
+ Where
+ @Synchronous
+ and
+ @Asynchronous
+ are qualifier annotations:
+
-
-
-
- A client bean developer uses the qualifier annotation to specify exactly which bean should be injected.
-
+
+ A client bean developer uses the qualifier annotation to specify exactly which bean should be injected.
+
- Using field injection:
+ Using field injection:
-
- Using initializer method injection:
+ Using initializer method injection:
-
- Using constructor injection:
+ Using constructor injection:
-
-
- Qualifier annotations can also qualify method arguments of producer, disposer and observer methods. Combining
- qualified arguments with producer methods is a good way to have an implementation of a bean type
- selected at runtime based on the state of the system:
-
+
+ Qualifier annotations can also qualify method arguments of producer, disposer and observer methods.
+ Combining
+ qualified arguments with producer methods is a good way to have an implementation of a bean type
+ selected at runtime based on the state of the system:
+
-
-
-
- If an injected field or a parameter of a bean constructor or initializer method is not explicitly annotated
- with a qualifier, the default qualifier, @Default, is assumed.
-
-
-
- Now, you may be thinking, "What's the different between using a qualifier and just specifying the
- exact implementation class you want?" It's important to understand that a qualifier is like an
- extension of the interface. It does not create a direct dependency to any particular implementation. There
- may be multiple alternative implementations of @Asynchronous PaymentProcessor!
-
-
-
-
-
- The built-in qualifiers @Default and @Any
-
- Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the
- qualifier @Default. From time to time, you'll need to declare an injection point without
- specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any.
- Therefore, by explicitly specifying @Any at an injection point, you suppress the default
- qualifier, without otherwise restricting the beans that are eligible for injection.
-
- This is especially useful if you want to iterate over all beans with a certain bean type. For example:
-
+
+
+ If an injected field or a parameter of a bean constructor or initializer method is not explicitly annotated
+ with a qualifier, the default qualifier,@Default, is assumed.
+
+
+
+ Now, you may be thinking,
+ "What's the different between using a qualifier and just specifying the
+ exact implementation class you want?"
+
+ It's important to understand that a qualifier is like an
+ extension of the interface. It does not create a direct dependency to any particular implementation. There
+ may be multiple alternative implementations of@Asynchronous PaymentProcessor!
+
+
+
+
+
+ The built-in qualifiers
+ @Default
+ and
+ @Any
+
+
+ Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the
+ qualifier@Default. From time to time, you'll need to declare an injection point without
+ specifying a qualifier. There's a qualifier for that too. All beans have the qualifier
+ @Any.
+ Therefore, by explicitly specifying
+ @Any
+ at an injection point, you suppress the default
+ qualifier, without otherwise restricting the beans that are eligible for injection.
+
+
+ This is especially useful if you want to iterate over all beans with a certain bean type. For example:
+
+ services) {
for (Service service: services) {
service.init();
}
}]]>
-
-
-
- Qualifiers with members
+
+
+
+ Qualifiers with members
-
- Java annotations can have members. We can use annotation members to further discriminate a qualifier. This
- prevents a potential explosion of new annotations. For example, instead of creating several qualifiers
+
+ Java annotations can have members. We can use annotation members to further discriminate a qualifier. This
+ prevents a potential explosion of new annotations. For example, instead of creating several qualifiers
representing different payment methods, we could aggregate them into a single annotation with a member:
-
+
-
-
-
+}]]>
+
+
Then we select one of the possible member values when applying the qualifier:
-
+
-
+
+
-
- We can force the container to ignore a member of a qualifier type by annotating the member
+
+ We can force the container to ignore a member of a qualifier type by annotating the member
@Nonbinding.
-
+
-
+}]]>
-
+
-
- Multiple qualifiers
+
+ Multiple qualifiers
-
+
An injection point may specify multiple qualifiers:
-
+
-
+
+
-
- Then only a bean which has both qualifier annotations would be eligible for
+
+ Then only a bean which has
+ both
+ qualifier annotations would be eligible for
injection.
-
+
-
-
-
-
- Alternatives
-
- Alternatives are beans whose implementation is specific to a particular client module or deployment
- scenario. This alternative defines a mock implementation of both @Synchronous PaymentProcessor
- and @Asynchronous PaymentProcessor, all in one:
-
-
+
+
+ Alternatives
+
+ Alternatives are beans whose implementation is specific to a particular client module or deployment
+ scenario. This alternative defines a mock implementation of both
+ @Synchronous PaymentProcessor
+ and@Asynchronous PaymentProcessor, all in one:
+
+
+
-
-
- By default, @Alternative beans are disabled. We need to enable an
- alternative in the beans.xml descriptor of a bean archive to make it available for
- instantiation and injection. This activation only applies to the beans in that archive.
-
-
-
+ By default,
+ @Alternative
+ beans are disabled. We need to
+ enable
+ an
+ alternative in the
+ beans.xml
+ descriptor of a bean archive to make it available for
+ instantiation and injection. This activation only applies to the beans in that archive.
+
+
+ org.mycompany.mock.MockPaymentProcessor
]]>
-
-
- When an ambiguous dependency exists at an injection point, the container attempts to resolve the ambiguity
- by looking for an enabled alternative among the beans that could be injected. If there is exactly one
- enabled alternative, that's the bean that will be injected.
-
-
-
-
-
- Fixing unsatisfied and ambiguous dependencies
-
-
- The typesafe resolution algorithm fails when, after considering the qualifier annotations on all beans that
- implement the bean type of an injection point and filtering out disabled beans (@Alternative
- beans which are not explicitly enabled), the container is unable to identify exactly one bean to inject. The
- container will abort deployment, informing us of the unsatisfied or ambiguous dependency.
-
-
-
- During the course of your development, you're going to encounter this situation. Let's learn how to resolve it.
-
-
-
- To fix an unsatisfied dependency, either:
-
-
-
-
-
- create a bean which implements the bean type and has all the qualifier types of the injection point,
-
-
-
-
- make sure that the bean you already have is in the classpath of the module with the injection point, or
-
-
-
-
- explicitly enable an @Alternative bean that implements the bean type and has the
- appropriate qualifier types, using beans.xml.
-
-
-
-
-
- To fix an ambiguous dependency, either:
-
-
-
-
-
- introduce a qualifier to distinguish between the two implementations of the bean type,
-
-
-
-
- disable one of the beans by annotating it @Alternative,
-
-
-
-
- move one of the implementations to a module that is not in the classpath of the module with the
- injection point, or
-
-
-
-
- disable one of two @Alternative beans that are trying to occupy the same space,
- using beans.xml.
-
-
-
-
-
- See this
- FAQ for step-by-step instructions for how to resolve an ambiguous resolution exception between a raw
- bean type and a producer method that returns the same bean type.
-
-
- Just remember: "There can be only one."
-
-
- On the other hand, if you really do have an optional or multivalued injection point, you should change
- the type of your injection point to Instance, as we'll see in .
-
-
-
- Now there's one more issue you need to be aware of when using the dependency injection service.
-
-
-
-
-
- Client proxies
-
-
- Clients of an injected bean do not usually hold a direct reference to a bean instance, unless the bean is
- a dependent object (scope @Dependent).
-
-
-
- Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request
- scope. The application-scoped bean is shared between many different requests. However, each request should see
- a different instance of the request scoped bean—the current one!
-
-
-
- Now imagine that a bean bound to the session scope holds a direct reference to a bean bound to the application
- scope. From time to time, the session context is serialized to disk in order to use memory more efficiently.
- However, the application scoped bean instance should not be serialized along with the session scoped bean! It
- can get that reference any time. No need to hoard it!
-
-
-
- Therefore, unless a bean has the default scope @Dependent, the container must indirect all
- injected references to the bean through a proxy object. This client proxy is responsible
- for ensuring that the bean instance that receives a method invocation is the instance that is associated with
- the current context. The client proxy also allows beans bound to contexts such as the session context to be
- serialized to disk without recursively serializing other injected beans.
-
-
-
- Unfortunately, due to limitations of the Java language, some Java types cannot be proxied by the container.
- If an injection point declared with one of these types resolves to a bean with any scope other than
- @Dependent, the container will abort deployment, informing us of the problem.
-
-
- The following Java types cannot be proxied by the container:
-
-
-
- classes which don't have a non-private constructor with no parameters, and
-
-
-
- classes which are declared final or have a final method,
-
-
-
- arrays and primitive types.
-
-
-
-
- It's usually very easy to fix an unproxyable dependency problem. If an injection point of type
- X results in an unproxyable dependency, simply:
-
-
-
-
-
- add a constructor with no parameters to X,
-
-
-
-
- change the type of the injection point to Instance<X>,
-
-
-
-
- introduce an interface Y, implemented by the injected bean, and change
- the type of the injection point to Y, or
-
-
-
-
- if all else fails, change the scope of the injected bean to @Dependent.
-
-
-
-
-
-
- A future release of Weld will likely support a non-standard workaround for this limitation, using
- non-portable JVM APIs:
-
-
-
-
-
- Sun, IcedTea, Mac: Unsafe.allocateInstance() (The most efficient)
-
-
-
-
- IBM, JRockit: ReflectionFactory.newConstructorForSerialization()
-
-
-
-
-
- But we didn't get around to implementing this yet.
-
-
-
-
-
-
-
- Obtaining a contextual instance by programmatic lookup
-
-
- In certain situations, injection is not the most convenient way to obtain a contextual reference. For example,
- it may not be used when:
-
-
-
-
-
- the bean type or qualifiers vary dynamically at runtime, or
-
-
-
+
+
+ When an ambiguous dependency exists at an injection point, the container attempts to resolve the ambiguity
+ by looking for an enabled alternative among the beans that could be injected. If there is exactly one
+ enabled alternative, that's the bean that will be injected.
+
+
+
+
+
+ Fixing unsatisfied and ambiguous dependencies
+
+
+ The typesafe resolution algorithm fails when, after considering the qualifier annotations on all beans that
+ implement the bean type of an injection point and filtering out disabled beans (
+ @Alternative
+ beans which are not explicitly enabled), the container is unable to identify exactly one bean to inject. The
+ container will abort deployment, informing us of the unsatisfied or ambiguous dependency.
+
+
+
+ During the course of your development, you're going to encounter this situation. Let's learn how to resolve
+ it.
+
+
+
+ To fix anunsatisfied dependency, either:
+
+
+
+
+
+ create a bean which implements the bean type and has all the qualifier types of the injection point,
+
+
+
+
+ make sure that the bean you already have is in the classpath of the module with the injection point,
+ or
+
+
+
+
+ explicitly enable an
+ @Alternative
+ bean that implements the bean type and has the
+ appropriate qualifier types, usingbeans.xml.
+
+
+
+
+
+ To fix anambiguous dependency, either:
+
+
+
+
+
+ introduce a qualifier to distinguish between the two implementations of the bean type,
+
+
+
+
+ disable one of the beans by annotating it@Alternative,
+
+
+
+
+ move one of the implementations to a module that is not in the classpath of the module with the
+ injection point, or
+
+
+
+
+ disable one of two
+ @Alternative
+ beans that are trying to occupy the same space,
+ usingbeans.xml.
+
+
+
+
+
+ See
+
+ this
+ FAQ
+
+ for step-by-step instructions for how to resolve an ambiguous resolution exception between a raw
+ bean type and a producer method that returns the same bean type.
+
+
+ Just remember: "There can be only one."
+
+
+ On the other hand, if you really do have an optional or multivalued injection point, you should change
+ the type of your injection point toInstance, as we'll see in.
+
+
+
+ Now there's one more issue you need to be aware of when using the dependency injection service.
+
+
+
+
+
+ Client proxies
+
+
+ Clients of an injected bean do not usually hold a direct reference to a bean instance, unless the bean is
+ a dependent object (scope@Dependent).
+
+
+
+ Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request
+ scope. The application-scoped bean is shared between many different requests. However, each request should
+ see
+ a different instance of the request scoped bean—the current one!
+
+
+
+ Now imagine that a bean bound to the session scope holds a direct reference to a bean bound to the
+ application
+ scope. From time to time, the session context is serialized to disk in order to use memory more efficiently.
+ However, the application scoped bean instance should not be serialized along with the session scoped bean!
+ It
+ can get that reference any time. No need to hoard it!
+
+
+
+ Therefore, unless a bean has the default scope@Dependent, the container must indirect all
+ injected references to the bean through a proxy object. This
+ client proxy
+ is responsible
+ for ensuring that the bean instance that receives a method invocation is the instance that is associated
+ with
+ the current context. The client proxy also allows beans bound to contexts such as the session context to be
+ serialized to disk without recursively serializing other injected beans.
+
+
+
+ Unfortunately, due to limitations of the Java language, some Java types cannot be proxied by the container.
+ If an injection point declared with one of these types resolves to a bean with any scope other than
+ @Dependent, the container will abort deployment, informing us of the problem.
+
+
+ The following Java types cannot be proxied by the container:
+
+
+
+ classes which don't have a non-private constructor with no parameters, and
+
+
+
+ classes which are declared
+ final
+ or have a
+ final
+ method,
+
+
+
+ arrays and primitive types.
+
+
+
+
+ It's usually very easy to fix an unproxyable dependency problem. If an injection point of type
+ X
+ results in an unproxyable dependency, simply:
+
+
+
+
+
+ add a constructor with no parameters toX,
+
+
+
+
+ change the type of the injection point toInstance<X>,
+
+
+
+
+ introduce an interfaceY, implemented by the injected bean, and change
+ the type of the injection point toY, or
+
+
+
+
+ if all else fails, change the scope of the injected bean to@Dependent.
+
+
+
+
+
- depending upon the deployment, there may be no bean which satisfies the type and qualifiers, or
+ A future release of Weld will likely support a non-standard workaround for this limitation, using
+ non-portable JVM APIs:
-
-
+
+
+
+
+ Sun, IcedTea, Mac:
+ Unsafe.allocateInstance()
+ (The most efficient)
+
+
+
+
+ IBM, JRockit:
+ ReflectionFactory.newConstructorForSerialization()
+
+
+
+
- we would like to iterate over all beans of a certain type.
+ But we didn't get around to implementing this yet.
-
-
-
-
- In these situations, the application may obtain an instance of the interface Instance,
- parameterized for the bean type, by injection:
-
-
- paymentProcessorSource;]]>
-
-
- The get() method of Instance produces a contextual instance of the bean.
-
-
-
-
-
- Qualifiers can be specified in one of two ways:
-
-
-
-
- by annotating the Instance injection point, or
-
-
- by passing qualifiers to the select() of Event.
-
-
-
-
- Specifying the qualifiers at the injection point is much, much easier:
-
-
- paymentProcessorSource;]]>
-
-
- Now, the PaymentProcessor returned by get() will have the qualifier
- @Asynchronous.
-
-
-
- Alternatively, we can specify the qualifier dynamically. First, we add the @Any qualifier to
- the injection point, to suppress the default qualifier. (All beans have the qualifier @Any.)
-
-
- paymentProcessorSource;]]>
-
-
- Next, we need to obtain an instance of our qualifier type. Since annotations are interfaces, we can't just write
- new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation
- type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class
- AnnotationLiteral.
-
-
-
+
+
+
+
+
+ Obtaining a contextual instance by programmatic lookup
+
+
+ In certain situations, injection is not the most convenient way to obtain a contextual reference. For
+ example,
+ it may not be used when:
+
+
+
+
+
+ the bean type or qualifiers vary dynamically at runtime, or
+
+
+
+
+ depending upon the deployment, there may be no bean which satisfies the type and qualifiers, or
+
+
+
+
+ we would like to iterate over all beans of a certain type.
+
+
+
+
+
+ In these situations, the application may obtain an instance of the interfaceInstance,
+ parameterized for the bean type, by injection:
+
+
+
+ paymentProcessorSource;]]>
+
+
+ The
+ get()
+ method of
+ Instance
+ produces a contextual instance of the bean.
+
+
+
+
+
+ Qualifiers can be specified in one of two ways:
+
+
+
+
+ by annotating the
+ Instance
+ injection point, or
+
+
+
+ by passing qualifiers to the
+ select()
+ ofEvent.
+
+
+
+
+
+ Specifying the qualifiers at the injection point is much, much easier:
+
+
+
+ paymentProcessorSource;]]>
+
+
+ Now, the
+ PaymentProcessor
+ returned by
+ get()
+ will have the qualifier
+ @Asynchronous.
+
+
+
+ Alternatively, we can specify the qualifier dynamically. First, we add the
+ @Any
+ qualifier to
+ the injection point, to suppress the default qualifier. (All beans have the qualifier@Any
+ .)
+
+
+
+ paymentProcessorSource;]]>
+
+
+ Next, we need to obtain an instance of our qualifier type. Since annotations are interfaces, we can't just
+ write
+ new Asynchronous(). It's also quite tedious to create a concrete implementation of an
+ annotation
+ type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class
+ AnnotationLiteral.
+
+
+ implements Asynchronous {}]]>
-
- In some cases, we can use an anonymous class:
-
+
+ In some cases, we can use an anonymous class:
+
- () {});]]>
-
-
- However, we can't use an anonymous class to implement a qualifier type with members.
-
-
-
- Now, finally, we can pass the qualifier to the select() method of Instance.
-
-
-
+ However, we can't use an anonymous class to implement a qualifier type with members.
+
+
+
+ Now, finally, we can pass the qualifier to the
+ select()
+ method ofInstance.
+
+
+
-
-
-
-
- The InjectionPoint object
-
- There are certain kinds of dependent objects (beans with scope @Dependent)
- 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:
-
-
-
- The log category for a Logger depends upon the class of the object
- that owns it.
-
-
- Injection of a HTTP parameter or header value depends upon what parameter
- or header name was specified at the injection point.
-
-
- Injection of the result of an EL expression evaluation depends upon the
- expression that was specified at the injection point.
-
-
-
- A bean with scope @Dependent may inject an instance of
- InjectionPoint and access metadata relating to the injection point to which
- it belongs.
-
- Let's look at an example. The following code is verbose, and vulnerable to refactoring
- problems:
-
-
-
- This clever little producer method lets you inject a JDK Logger without
- explicitly specifying the log category:
-
-
+
+
+
+
+ The
+ InjectionPoint
+ object
+
+
+ There are certain kinds of dependent objects (beans with scope@Dependent)
+ 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:
+
+
+
+
+ The log category for a
+ Logger
+ depends upon the class of the object
+ that owns it.
+
+
+
+ Injection of a HTTP parameter or header value depends upon what parameter
+ or header name was specified at the injection point.
+
+
+
+ Injection of the result of an EL expression evaluation depends upon the
+ expression that was specified at the injection point.
+
+
+
+
+ A bean with scope
+ @Dependent
+ may inject an instance of
+ InjectionPoint
+ and access metadata relating to the injection point to which
+ it belongs.
+
+
+ Let's look at an example. The following code is verbose, and vulnerable to refactoring
+ problems:
+
+
+
+
+ This clever little producer method lets you inject a JDK
+ Logger
+ without
+ explicitly specifying the log category:
+
+
+
- We can now write:
+ We can now write:
-
+
- Not convinced? Then here's a second example. To inject HTTP parameters, we need to define
- a qualifier type:
+ Not convinced? Then here's a second example. To inject HTTP parameters, we need to define
+ a qualifier type:
+
-
- We would use this qualifier type at injection points as follows:
+ We would use this qualifier type at injection points as follows:
-
- The following producer method does the work:
+ The following producer method does the work:
-
- Note that acquiring of the request in this example is JSF-centric. For a more generic solution
- you could write your own producer for the request and have it injected as a method parameter.
+ Note that acquiring of the request in this example is JSF-centric. For a more generic solution
+ you could write your own producer for the request and have it injected as a method parameter.
+
- Note also that the value() member of the HttpParam
- annotation is ignored by the container since it is annotated @Nonbinding.
+ Note also that the
+ value()
+ member of the
+ HttpParam
+ annotation is ignored by the container since it is annotated
+ @Nonbinding.
+
- The container provides a built-in bean that implements the InjectionPoint
- interface:
+ The container provides a built-in bean that implements the
+ InjectionPoint
+ interface:
+
- getQualifiers();
public Bean> getBean();
@@ -761,9 +891,9 @@ public @interface HttpParam {
public boolean isTransient();
}]]>
-
+
-
+
diff --git a/docs/reference/src/main/docbook/en-US/scopescontexts.xml b/docs/reference/src/main/docbook/en-US/scopescontexts.xml
index deebcc288b4..1a0388ab19a 100644
--- a/docs/reference/src/main/docbook/en-US/scopescontexts.xml
+++ b/docs/reference/src/main/docbook/en-US/scopescontexts.xml
@@ -248,14 +248,15 @@ public class OrderBuilder {
We can force the conversation to propagate with a non-faces request by including the unique identifier of
the conversation as a request parameter. The CDI specification reserves the request parameter named
cid for this use. The unique identifier of the conversation may be obtained from the
- Conversation object, which has the EL bean name conversation.
+ Conversation object, which has the EL bean name
+ javax.enterprise.context.conversation.
Therefore, the following link propagates the conversation:
- Add Product]]>
+ Add Product]]>
It's probably better to use one of the link components in JSF 2:
diff --git a/docs/reference/src/main/docbook/es-ES/Weld_-_JSR-299_Reference_Implementation.po b/docs/reference/src/main/docbook/es-ES/Weld_-_JSR-299_Reference_Implementation.po
new file mode 100644
index 00000000000..f4baccac014
--- /dev/null
+++ b/docs/reference/src/main/docbook/es-ES/Weld_-_JSR-299_Reference_Implementation.po
@@ -0,0 +1,59 @@
+#
+# AUTHOR , YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "A note about naming and nomenclature"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Shortly before the final draft of JSR-299 was submitted, the specification changed its name from \"Web Beans\" to \"Java Contexts and Dependency Injection for the Java EE platform\", abbreviated CDI. For a brief period after the renaming, the reference implementation adopted the name \"Web Beans\". However, this ended up causing more confusion than it solved and Red Hat decided to change the name of the reference implementation to \"Weld\". You may still find other documentation, blogs, forum posts, etc. that use the old nomenclature. Please update any references you can. The naming game is over."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You'll also find that some of the functionality that once existed in the specification is now missing, such as defining beans in XML. These features will be available as portable extensions for CDI in the Weld project, and perhaps other implementations."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this reference guide was started while changes were still being made to the specification. We've done our best to update it for accuracy. If you discover a conflict between what is written in this guide and the specification, the specification is the authority—assume it is correct. If you believe you have found an error in the specification, please report it to the JSR-299 EG."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Beans"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Start with Weld, the CDI Reference Implementation"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Loose coupling with strong typing"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "CDI and the Java EE ecosystem"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Weld Reference Guide"
+msgstr ""
+
diff --git a/docs/reference/src/main/docbook/es-ES/beans.po b/docs/reference/src/main/docbook/es-ES/beans.po
index 89c9f5c493b..433bce210a8 100644
--- a/docs/reference/src/main/docbook/es-ES/beans.po
+++ b/docs/reference/src/main/docbook/es-ES/beans.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
+msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
msgstr ""
#. Tag: para
@@ -56,7 +56,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
+msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
msgstr ""
#. Tag: para
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
+msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
msgstr ""
#. Tag: title
@@ -131,7 +131,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's see what all this new terminology means."
+msgid "Let's see what all this new terminology means."
msgstr ""
#. Tag: title
@@ -141,7 +141,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a "contract" that must be satisfied by the bean to be injected. The contract is:"
+msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a \"contract\" that must be satisfied by the bean to be injected. The contract is:"
msgstr ""
#. Tag: para
@@ -164,14 +164,14 @@ msgstr ""
msgid ""
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
+msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
msgstr ""
#. Tag: para
@@ -192,12 +192,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
+msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
+msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
msgstr ""
#. Tag: programlisting
@@ -206,19 +206,19 @@ msgid ""
"@Typed(Shop.class)\n"
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of "quality" using a qualifier."
+msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of \"quality\" using a qualifier."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
+msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
msgstr ""
#. Tag: programlisting
@@ -232,12 +232,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
+msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
+msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
msgstr ""
#. Tag: para
@@ -252,12 +252,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
+msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
msgstr ""
#. Tag: para
@@ -275,12 +270,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If a bean does not explicitly specify a qualifier, it has the default qualifier, @Default."
+msgid "If a bean or an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
+msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
msgstr ""
#. Tag: title
@@ -312,7 +307,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
+msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
msgstr ""
#. Tag: para
@@ -322,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk more about scopes in ."
+msgid "We'll talk more about scopes in ."
msgstr ""
#. Tag: title
@@ -343,7 +338,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"public @SessionScoped @Named("cart")\n"
+"public @SessionScoped @Named(\"cart\")\n"
"class ShoppingCart implements Serializable { ... }"
msgstr ""
@@ -355,9 +350,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:dataTable value="#{cart.lineItems}" var="item">\n"
+"<h:dataTable value=\"#{cart.lineItems}\" var=\"item\">\n"
" ...\n"
-"</h:dataTable>"
+"</h:dataTable>"
msgstr ""
#. Tag: para
@@ -389,7 +384,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
+msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
msgstr ""
#. Tag: programlisting
@@ -416,12 +411,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
+msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
+msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
msgstr ""
#. Tag: para
@@ -470,17 +465,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
+msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
+msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
+msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
msgstr ""
#. Tag: title
@@ -490,7 +485,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
+msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
msgstr ""
#. Tag: title
@@ -500,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
+msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
msgstr ""
#. Tag: para
@@ -525,7 +520,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It has an appropriate constructor—either:"
+msgid "It has an appropriate constructor—either:"
msgstr ""
#. Tag: para
@@ -540,7 +535,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
+msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
msgstr ""
#. Tag: para
@@ -585,12 +580,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
+msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
+msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
msgstr ""
#. Tag: para
@@ -625,7 +620,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
+msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
msgstr ""
#. Tag: para
@@ -640,17 +635,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
+msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
+msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're "heavyweight". It's nothing more than superstition to think that something is "heavier" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like "heavyweight"."
+msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're \"heavyweight\". It's nothing more than superstition to think that something is \"heavier\" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like \"heavyweight\"."
msgstr ""
#. Tag: title
@@ -690,7 +685,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
+msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
msgstr ""
#. Tag: programlisting
@@ -705,7 +700,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<p>Your raffle number is #{randomNumber}.</p>"
+msgid "<p>Your raffle number is #{randomNumber}.</p>"
msgstr ""
#. Tag: para
@@ -746,14 +741,14 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces Set<Roles> getRoles(User user) {\n"
+"@Produces Set<Roles> getRoles(User user) {\n"
" return user.getRoles();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk much more about producer methods in ."
+msgid "We'll talk much more about producer methods in ."
msgstr ""
#. Tag: title
@@ -763,7 +758,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
+msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
msgstr ""
#. Tag: programlisting
@@ -771,7 +766,7 @@ msgstr ""
msgid ""
"public class Shop {\n"
" @Produces PaymentProcessor paymentProcessor = ....;\n"
-" @Produces @Catalog List<Product> products = ....;\n"
+" @Produces @Catalog List<Product> products = ....;\n"
"}"
msgstr ""
@@ -782,5 +777,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
+msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
msgstr ""
diff --git a/docs/reference/src/main/docbook/es-ES/configure.po b/docs/reference/src/main/docbook/es-ES/configure.po
index eeba87f0a16..01ef2ccd8ab 100644
--- a/docs/reference/src/main/docbook/es-ES/configure.po
+++ b/docs/reference/src/main/docbook/es-ES/configure.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -30,50 +30,50 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
+msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<?xml version="1.0" encoding="UTF-8"?>\n"
-"<beans xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \n"
-" xmlns:weld="http://jboss.org/schema/weld/beans" \n"
-" xsi:schemaLocation="\n"
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<beans xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" \n"
+" xmlns:weld=\"http://jboss.org/schema/weld/beans\" \n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee http://docs.jboss.org/cdi/beans_1_0.xsd\n"
-" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">\n"
+" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd\">\n"
" \n"
-" <weld:scan>\n"
+" <weld:scan>\n"
" \n"
-" <!-- Don't deploy the classes for the swing app! -->\n"
-" <weld:exclude name="com.acme.swing.**" />\n"
+" <!-- Don't deploy the classes for the swing app! -->\n"
+" <weld:exclude name=\"com.acme.swing.**\" />\n"
" \n"
-" <!-- Don't include GWT support if GWT is not installed -->\n"
-" <weld:exclude name="com.acme.gwt.**">\n"
-" <weld:if-class-available name="!com.google.GWT"/>\n"
-" </weld:exclude>\n"
+" <!-- Don't include GWT support if GWT is not installed -->\n"
+" <weld:exclude name=\"com.acme.gwt.**\">\n"
+" <weld:if-class-available name=\"!com.google.GWT\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
+" <!--\n"
" Exclude classes which end in Blether if the system property verbosity is set to low\n"
" i.e.\n"
" java ... -Dverbosity=low \n"
-" --> \n"
-" <weld:exclude pattern="^(.*)Blether$">\n"
-" <weld:if-system-property name="verbosity" value="low"/>\n"
-" </weld:exclude>\n"
+" --> \n"
+" <weld:exclude pattern=\"^(.*)Blether$\">\n"
+" <weld:if-system-property name=\"verbosity\" value=\"low\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
-" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
+" <!--\n"
+" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
" property is not set\n"
-" -->\n"
-" <weld:exclude name="com.acme.jsf.**">\n"
-" <weld:if-class-available name="org.apahce.wicket.Wicket"/>\n"
-" <weld:if-system-property name="!viewlayer"/>\n"
-" </weld:exclude>\n"
-" </weld:scan>\n"
+" -->\n"
+" <weld:exclude name=\"com.acme.jsf.**\">\n"
+" <weld:if-class-available name=\"org.apahce.wicket.Wicket\"/>\n"
+" <weld:if-system-property name=\"!viewlayer\"/>\n"
+" </weld:exclude>\n"
+" </weld:scan>\n"
" \n"
-"</beans>"
+"</beans>"
msgstr ""
#. Tag: para
@@ -83,7 +83,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
+msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
msgstr ""
#. Tag: para
@@ -93,12 +93,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
+msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
+msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
msgstr ""
#. Tag: para
@@ -113,5 +113,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
+msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
msgstr ""
diff --git a/docs/reference/src/main/docbook/es-ES/contexts.po b/docs/reference/src/main/docbook/es-ES/contexts.po
index 998addb61d4..6503057daf1 100644
--- a/docs/reference/src/main/docbook/es-ES/contexts.po
+++ b/docs/reference/src/main/docbook/es-ES/contexts.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,17 +25,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld allows you to easiy manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivaed (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
+msgid "Weld allows you to easily manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivated (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and discociating the data store after calling activate."
+msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and dissociating the data store after calling activate."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld automatically controls context lifecycle in many scenarios such as Http Requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
+msgid "Weld automatically controls context lifecycle in many scenarios such as HTTP requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
msgstr ""
#. Tag: para
@@ -145,7 +145,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
+msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
msgstr ""
#. Tag: entry
@@ -245,12 +245,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implmentations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
+msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implementations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
+msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
msgstr ""
#. Tag: programlisting
@@ -263,14 +263,14 @@ msgid ""
" ...\n"
" \n"
" /* Start the request, providing a data store which will last the lifetime of the request */\n"
-" public void startRequest(Map<String, Object> requestDataStore) {\n"
+" public void startRequest(Map<String, Object> requestDataStore) {\n"
" // Associate the store with the context and acticate the context\n"
" requestContext.associate(requestDataStore);\n"
" requestContext.activate();\n"
" }\n"
" \n"
" /* End the request, providing the same data store as was used to start the request */\n"
-" public void endRequest(Map<String, Object> requestDataStore) {\n"
+" public void endRequest(Map<String, Object> requestDataStore) {\n"
" try {\n"
" /* Invalidate the request (all bean instances will be scheduled for destruction) */\n"
" requestContext.invalidate();\n"
@@ -290,7 +290,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's session contexts are "lazy" and don't require a session to actually exist until a bean instance must be written."
+msgid "Weld's session contexts are \"lazy\" and don't require a session to actually exist until a bean instance must be written."
msgstr ""
#. Tag: para
@@ -308,16 +308,16 @@ msgid ""
" /* Start a transient conversation */\n"
" /* Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */\n"
-" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" resumeOrStartConversation(requestDataStore, sessionDataStore, null);\n"
" }\n"
"\n"
" /* Start a transient conversation (if cid is null) or resume a non-transient */\n"
" /* conversation. Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */ \n"
-" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore, \n"
+" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore, \n"
" String cid) {\n"
" /* Associate the stores with the context and acticate the context */\n"
" * BoundRequest just wraps the two datastores */\n"
@@ -329,8 +329,8 @@ msgid ""
" /* End the conversations, providing the same data store as was used to start */\n"
" /* the request. Any transient conversations will be destroyed, any newly-promoted */\n"
" /* conversations will be placed into the session */\n"
-" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" try {\n"
" /* Invalidate the conversation (all transient conversations will be scheduled for destruction) */\n"
" conversationContext.invalidate();\n"
@@ -345,15 +345,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the containber), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
+msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the container), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the abilty to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
+msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the ability to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's conversations are not assigned ids until they become non-transient."
+msgid "Weld's conversations are not assigned ids until they become non-transient."
msgstr ""
diff --git a/docs/reference/src/main/docbook/es-ES/decorators.po b/docs/reference/src/main/docbook/es-ES/decorators.po
index 6dcf34c0a11..b4f0c1d90c7 100644
--- a/docs/reference/src/main/docbook/es-ES/decorators.po
+++ b/docs/reference/src/main/docbook/es-ES/decorators.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: decorators\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-19 11:35+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -24,12 +24,12 @@ msgstr "Decoradores"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
+msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
msgstr "Los interceptores son una forma potente de capturar y distinguir cuestiones que son ortogonales al tipo de sistema. Cualquier interceptor puede interceptar invocaciones de cualquier tipo de Java. Esto los hace perfectos para resolver cuestiones técnicas como la administración de transacción y la seguridad. Sin embargo, por naturaleza, los interceptores desconocen la semántica real de los eventos que interceptan. Por lo tanto, los interceptores no son una herramienta apropiada para distinguir cuestiones relacionadas con negocios."
#. Tag: para
#, fuzzy, no-c-format
-msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
+msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
msgstr "En cambio, los decoradores interceptan invocaciones únicamente para una determinada interfaz de Java y por lo tanto, conocen toda la semántica asociada a la interfaz. Esto los hace una herramienta perfecta para representar algunas clases de cuestiones de negocios. También significa que los decoradores no tienen la generalidad de un interceptor. Los decoradores no pueden resolver problemas técnicos que atraviesan muchos tipos dispares."
#. Tag: para
@@ -127,7 +127,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
+msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
msgstr "A diferencia de otros Web Beans sencillos, un decorador puede ser una clase abstracta. Si no hay nada especial que el decorador tenga que hacer para un método particular de la interfaz decorada, usted no necesita implementar ese método."
#. Tag: para
@@ -211,14 +211,14 @@ msgid ""
" \n"
" public void withdraw(BigDecimal amount) {\n"
" account.withdraw(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedWithdrawl(amount) );\n"
" }\n"
" }\n"
" \n"
" public void deposit(BigDecimal amount);\n"
" account.deposit(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedDeposit(amount) );\n"
" }\n"
" }\n"
@@ -261,21 +261,21 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <decorators>\n"
-" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
-" </decorators>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <decorators>\n"
+" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
+" </decorators>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
+msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
msgstr "Esta declaración sirve para decoradores al igual que la declaración <Interceptores> sirve para interceptores:"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/es-ES/ee.po b/docs/reference/src/main/docbook/es-ES/ee.po
index b67c1ae32ff..f28cb5dcbb9 100644
--- a/docs/reference/src/main/docbook/es-ES/ee.po
+++ b/docs/reference/src/main/docbook/es-ES/ee.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: ee\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-19 11:56+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -59,7 +59,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
+msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
msgstr ""
#. Tag: para
@@ -84,7 +84,7 @@ msgstr "Inyección de recursos de Java EE en un Web Bean"
#. Tag: para
#, fuzzy, no-c-format
-msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
+msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
msgstr "Todos los Web Beans sencillos y empresariales pueden aprovechar la inyección de dependencia de Java EE utilizando@Resource, @EJB y @PersistenceContext. Ya hemos visto algunos ejemplos de esto, aunque no prestamos mucha atención en el momento."
#. Tag: programlisting
@@ -143,7 +143,7 @@ msgstr "Llamando a Web Bean desde un Servlet"
#. Tag: para
#, fuzzy, no-c-format
-msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
+msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
msgstr "Es fácil utilizar un Web Bean desde un Servlet en Java EE 6. Simplemente inyecte el Web Bean mediante campo de Web Beans o Inyección de método inicializador."
#. Tag: programlisting
@@ -156,14 +156,14 @@ msgid ""
" @Override\n"
" public void service(HttpServletRequest request, HttpServletResponse response)\n"
" throws ServletException, IOException {\n"
-" credentials.setUsername(request.getParameter("username")):\n"
-" credentials.setPassword(request.getParameter("password")):\n"
+" credentials.setUsername(request.getParameter(\"username\")):\n"
+" credentials.setPassword(request.getParameter(\"password\")):\n"
" login.login();\n"
" if ( login.isLoggedIn() ) {\n"
-" response.sendRedirect("/home.jsp");\n"
+" response.sendRedirect(\"/home.jsp\");\n"
" }\n"
" else {\n"
-" response.sendRedirect("/loginError.jsp");\n"
+" response.sendRedirect(\"/loginError.jsp\");\n"
" }\n"
" }\n"
" \n"
@@ -202,7 +202,7 @@ msgstr "Llamada a un Web Bean desde un Message-Driven Bean"
#. Tag: para
#, no-c-format
-msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
+msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
msgstr ""
#. Tag: para
@@ -264,10 +264,10 @@ msgstr ""
#, no-c-format
msgid ""
"public class OrderResources {\n"
-" @Resource(name="jms/ConnectionFactory")\n"
+" @Resource(name=\"jms/ConnectionFactory\")\n"
" private ConnectionFactory connectionFactory;\n"
" \n"
-" @Resource(name="jms/OrderQueue")\n"
+" @Resource(name=\"jms/OrderQueue\")\n"
" private Queue orderQueue;\n"
" \n"
" @Produces @OrderConnection\n"
@@ -318,7 +318,7 @@ msgid ""
"\n"
"public void sendMessage() {\n"
" MapMessage msg = orderSession.createMapMessage();\n"
-" msg.setLong("orderId", order.getId());\n"
+" msg.setLong(\"orderId\", order.getId());\n"
" ...\n"
" producer.send(msg);\n"
"}"
@@ -344,7 +344,7 @@ msgstr "Empaquetamiento y despliegue."
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a "bean archive". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
+msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a \"bean archive\". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml 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 web-beans.xml en META-INF o en el directorio WEB-INF. El archivo puede estar vacío. Los Web Beans desplegados en archivos que no tienen un archivo web-beans.xml no estarán disponibles para uso en la aplicación."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/es-ES/environments.po b/docs/reference/src/main/docbook/es-ES/environments.po
index 5ff9f7e8f7c..9cdf59af186 100644
--- a/docs/reference/src/main/docbook/es-ES/environments.po
+++ b/docs/reference/src/main/docbook/es-ES/environments.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-28 17:09+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -56,12 +56,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
+msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an "uber-jar", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
+msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an \"uber-jar\", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
msgstr ""
#. Tag: para
@@ -72,9 +72,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
#. Tag: title
@@ -84,18 +84,18 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
+msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<Context>\n"
-" <Resource name="BeanManager" \n"
-" auth="Container"\n"
-" type="javax.enterprise.inject.spi.BeanManager"\n"
-" factory="org.jboss.weld.resources.ManagerObjectFactory"/>\n"
-"</Context>"
+"<Context>\n"
+" <Resource name=\"BeanManager\" \n"
+" auth=\"Container\"\n"
+" type=\"javax.enterprise.inject.spi.BeanManager\"\n"
+" factory=\"org.jboss.weld.resources.ManagerObjectFactory\"/>\n"
+"</Context>"
msgstr ""
#. Tag: para
@@ -106,12 +106,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<resource-env-ref>\n"
-" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
-" <resource-env-ref-type>\n"
+"<resource-env-ref>\n"
+" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
+" <resource-env-ref-type>\n"
" javax.enterprise.inject.spi.BeanManager\n"
-" </resource-env-ref-type>\n"
-"</resource-env-ref>"
+" </resource-env-ref-type>\n"
+"</resource-env-ref>"
msgstr ""
#. Tag: para
@@ -131,27 +131,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
+msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.mortbay.jetty.plus.naming.Resource">\n"
-" <Arg><Ref id="webAppCtx"/></Arg> \n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.mortbay.jetty.plus.naming.Resource\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg> \n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure>"
msgstr ""
#. Tag: para
@@ -162,22 +162,22 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://www.eclipse.org/jetty/configure.dtd">\n"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://www.eclipse.org/jetty/configure.dtd\">\n"
"\n"
-"<Configure id="webAppCtx" class="org.eclipse.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.eclipse.jetty.plus.jndi.Resource">\n"
-" <Arg> <Ref id="webAppCtx"/> </Arg>\n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure> "
+"<Configure id=\"webAppCtx\" class=\"org.eclipse.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.eclipse.jetty.plus.jndi.Resource\">\n"
+" <Arg> <Ref id=\"webAppCtx\"/> </Arg>\n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure> "
msgstr ""
#. Tag: para
@@ -187,7 +187,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
+msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
msgstr ""
#. Tag: para
@@ -197,19 +197,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file META-INF/jetty-web.xml with the following content to your war:"
+msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file WEB-INF/jetty-web.xml with the following content to your war:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <Call class="org.jboss.weld.environment.jetty.WeldServletHandler" name="process">\n"
-" <Arg><Ref id="webAppCtx"/></Arg>\n"
-" </Call>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <Call class=\"org.jboss.weld.environment.jetty.WeldServletHandler\" name=\"process\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg>\n"
+" </Call>\n"
+"</Configure>"
msgstr ""
#. Tag: title
@@ -219,7 +219,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In addition to improved integration of the Enterprise Java stack, the "Contexts and Dependency Injection for the Java EE platform" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
+msgid "In addition to improved integration of the Enterprise Java stack, the \"Contexts and Dependency Injection for the Java EE platform\" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
msgstr ""
#. Tag: para
@@ -279,7 +279,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Parameters List<String> params;"
+msgid "@Inject @Parameters List<String> params;"
msgstr ""
#. Tag: programlisting
@@ -299,7 +299,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example of a simple CDI SE application:"
+msgid "Here's an example of a simple CDI SE application:"
msgstr ""
#. Tag: programlisting
@@ -308,8 +308,8 @@ msgid ""
"@Singleton\n"
"public class HelloWorld\n"
"{\n"
-" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
-" System.out.println("Hello " + parameters.get(0));\n"
+" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
+" System.out.println(\"Hello \" + parameters.get(0));\n"
" }\n"
"}"
msgstr ""
@@ -331,7 +331,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
+msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
msgstr ""
#. Tag: para
@@ -341,17 +341,17 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "java org.jboss.weld.environment.se.StartMain <args>"
+msgid "java org.jboss.weld.environment.se.StartMain <args>"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Programatic Bootstrap API"
+msgid "Programmatic Bootstrap API"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
+msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
msgstr ""
#. Tag: programlisting
@@ -377,10 +377,10 @@ msgid ""
"{\n"
"\n"
" /** Provides access to all beans within the application. */\n"
-" public Instance<Object> instance() {...}\n"
+" public Instance<Object> instance() {...}\n"
"\n"
" /** Provides access to all events within the application. */\n"
-" public Event<Object> event() {...}\n"
+" public Event<Object> event() {...}\n"
"\n"
" /** Provides direct access to the BeanManager. */\n"
" public BeanManager getBeanManager() {...}\n"
@@ -390,7 +390,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
+msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
msgstr ""
#. Tag: programlisting
@@ -430,22 +430,22 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
+msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans>\n"
-" <decorators>\n"
-" <decorator>org.jboss.weld.environment.se.threading.RunnableDecorator</decorator>\n"
-" </decorator>\n"
-"</beans>"
+"<beans>\n"
+" <decorators>\n"
+" <class>org.jboss.weld.environment.se.threading.RunnableDecorator</class>\n"
+" </decorator>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situtations where you would otherwise have used ThreadLocal directly, which are typically rare."
+msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situations where you would otherwise have used ThreadLocal directly, which are typically rare."
msgstr ""
#. Tag: title
@@ -455,7 +455,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
+msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/es-ES/events.po b/docs/reference/src/main/docbook/es-ES/events.po
index ae7d82016c7..1d9fea2d7a7 100644
--- a/docs/reference/src/main/docbook/es-ES/events.po
+++ b/docs/reference/src/main/docbook/es-ES/events.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: events\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-19 13:59+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -39,7 +39,7 @@ msgstr "no solamente los productores de eventos están disociados de los observa
#. Tag: para
#, fuzzy, no-c-format
-msgid "observers can specify a combination of "selectors" to narrow the set of event notifications they will receive, and"
+msgid "observers can specify a combination of \"selectors\" to narrow the set of event notifications they will receive, and"
msgstr "los observadores pueden especificar una combinación de \"selectores\" para limitar el conjunto de notificaciones de eventos que recibirán y"
#. Tag: para
@@ -49,7 +49,7 @@ msgstr "los observadores pueden ser notificados inmediatamente o pueden especifi
#. Tag: para
#, no-c-format
-msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
+msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
msgstr ""
#. Tag: title
@@ -64,7 +64,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
+msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
msgstr ""
#. Tag: programlisting
@@ -107,7 +107,7 @@ msgstr "only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
+msgid "An observer method need not specify any event qualifiers—in this case it is interested in only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
msgstr "Un método de observador no necesita especificar ningún enlace de evento en este caso está interesado en todos 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
@@ -132,7 +132,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Event<Document> documentEvent;"
+msgid "@Inject @Any Event<Document> documentEvent;"
msgstr " documentEvent]]>"
#. Tag: para
@@ -187,7 +187,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
+msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
msgstr " documentUpdatedEvent]]>"
#. Tag: para
@@ -207,12 +207,12 @@ msgstr "no especifique ningún enlace de evento excepto par
#. Tag: para
#, no-c-format
-msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
+msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
+msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
msgstr "(){} );]]>"
#. Tag: para
@@ -227,7 +227,7 @@ msgstr "Observadores transaccionales"
#. Tag: para
#, no-c-format
-msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
+msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
msgstr ""
#. Tag: para
@@ -289,7 +289,7 @@ msgstr "Los miembros de tipo de enlace de evento se pueden especificar estática
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
+msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
msgstr " LoggedInEvent;}}]]>"
#. Tag: para
@@ -301,7 +301,7 @@ msgstr "Alternativamente, el valor del miembro de tipo de enlace de evento puede
#, fuzzy, no-c-format
msgid ""
"abstract class RoleBinding \n"
-" extends AnnotationLiteral<Role> \n"
+" extends AnnotationLiteral<Role> \n"
" implements Role {}"
msgstr ""
" blogEvent;\n"
"...\n"
@@ -445,12 +445,12 @@ msgid ""
"\n"
" @PersistenceContext EntityManager em;\n"
" \n"
-" List<Product> products;\n"
+" List<Product> products;\n"
"\n"
" @Produces @Catalog \n"
-" List<Product> getCatalog() {\n"
+" List<Product> getCatalog() {\n"
" if (products==null) {\n"
-" products = em.createQuery("select p from Product p where p.deleted = false")\n"
+" products = em.createQuery(\"select p from Product p where p.deleted = false\")\n"
" .getResultList();\n"
" }\n"
" return products;\n"
@@ -492,16 +492,16 @@ msgid ""
"@Stateless\n"
"public class ProductManager {\n"
" @PersistenceContext EntityManager em;\n"
-" @Inject @Any Event<Product> productEvent;\n"
+" @Inject @Any Event<Product> productEvent;\n"
"\n"
" public void delete(Product product) {\n"
" em.delete(product);\n"
-" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
" }\n"
" \n"
" public void persist(Product product) {\n"
" em.persist(product);\n"
-" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
" }\n"
" ...\n"
"}"
diff --git a/docs/reference/src/main/docbook/es-ES/example.po b/docs/reference/src/main/docbook/es-ES/example.po
index 6bfa3a541da..952f83d3992 100644
--- a/docs/reference/src/main/docbook/es-ES/example.po
+++ b/docs/reference/src/main/docbook/es-ES/example.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: example\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-20 10:54+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -24,7 +24,7 @@ msgstr "ejemplo de aplicación de red JSF"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
+msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
msgstr "Ilustremos estas ideas con un ejemplo. Vamos a implementar inicio/cierre de sesión de usuario para una aplicación que utiliza JSF. Primero, definiremos un Web Bean para mantener el nombre de usuario y contraseña escritos durante el inicio de sesión:"
#. Tag: programlisting
@@ -66,18 +66,18 @@ msgstr "Este Web Bean está vinculado al intérprete de comandos de inicio de se
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:form>\n"
-" <h:panelGrid columns="2" rendered="#{!login.loggedIn}">\n"
-" <f:validateBean>\n"
-" <h:outputLabel for="username">Username:</h:outputLabel>\n"
-" <h:inputText id="username" value="#{credentials.username}"/>\n"
-" <h:outputLabel for="password">Password:</h:outputLabel>\n"
-" <h:inputSecret id="password" value="#{credentials.password}"/>\n"
-" </f:validateBean>\n"
-" </h:panelGrid>\n"
-" <h:commandButton value="Login" action="#{login.login}" rendered="#{!login.loggedIn}"/>\n"
-" <h:commandButton value="Logout" action="#{login.logout}" rendered="#{login.loggedIn}"/>\n"
-"</h:form>"
+"<h:form>\n"
+" <h:panelGrid columns=\"2\" rendered=\"#{!login.loggedIn}\">\n"
+" <f:validateBean>\n"
+" <h:outputLabel for=\"username\">Username:</h:outputLabel>\n"
+" <h:inputText id=\"username\" value=\"#{credentials.username}\"/>\n"
+" <h:outputLabel for=\"password\">Password:</h:outputLabel>\n"
+" <h:inputSecret id=\"password\" value=\"#{credentials.password}\"/>\n"
+" </f:validateBean>\n"
+" </h:panelGrid>\n"
+" <h:commandButton value=\"Login\" action=\"#{login.login}\" rendered=\"#{!login.loggedIn}\"/>\n"
+" <h:commandButton value=\"Logout\" action=\"#{login.logout}\" rendered=\"#{login.loggedIn}\"/>\n"
+"</h:form>"
msgstr ""
"\n"
" \n"
@@ -124,7 +124,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
+msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
msgstr ""
#. Tag: para
@@ -144,10 +144,10 @@ msgid ""
" private User user;\n"
" \n"
" public void login() {\n"
-" List<User> results = userDatabase.createQuery(\n"
-" "select u from User u where u.username = :username and u.password = :password")\n"
-" .setParameter("username", credentials.getUsername())\n"
-" .setParameter("password", credentials.getPassword())\n"
+" List<User> results = userDatabase.createQuery(\n"
+" \"select u from User u where u.username = :username and u.password = :password\")\n"
+" .setParameter(\"username\", credentials.getUsername())\n"
+" .setParameter(\"password\", credentials.getPassword())\n"
" .getResultList();\n"
" \n"
" if (!results.isEmpty()) {\n"
@@ -293,14 +293,14 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:panelGroup rendered="#{login.loggedIn}">\n"
+"<h:panelGroup rendered=\"#{login.loggedIn}\">\n"
" signed in as #{currentUser.username}\n"
-"</h:panelGroup>"
+"</h:panelGroup>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
+msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
msgstr "Esperamos que este ejemplo de una idea del modelo de programación de Web Bean. En el próximo capítulo, estudiaremos más a fondo la inyección de dependencia de Web Beans."
#~ msgid "Of course, @LoggedIn is a binding annotation:"
diff --git a/docs/reference/src/main/docbook/es-ES/extend.po b/docs/reference/src/main/docbook/es-ES/extend.po
index d5be7d70a0a..df72f5e6473 100644
--- a/docs/reference/src/main/docbook/es-ES/extend.po
+++ b/docs/reference/src/main/docbook/es-ES/extend.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: extend\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-19 14:15+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -79,7 +79,7 @@ msgstr "La clase Bean"
#. Tag: para
#, no-c-format
-msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
+msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
msgstr ""
#. Tag: programlisting
@@ -167,15 +167,15 @@ msgid ""
"class MyExtension implements Extension {\n"
" \n"
" void beforeBeanDiscovery(@Observes BeforeBeanDiscovery bbd) {\n"
-" Logger.global.debug("beginning the scanning process");\n"
+" Logger.global.debug(\"beginning the scanning process\");\n"
" }\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
-" Logger.global.debug("scanning type: " + pat.getAnnotatedType().getJavaClass().getName());\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" Logger.global.debug(\"scanning type: \" + pat.getAnnotatedType().getJavaClass().getName());\n"
" } \n"
"\n"
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd) {\n"
-" Logger.global.debug("finished the scanning process");\n"
+" Logger.global.debug(\"finished the scanning process\");\n"
" }\n"
" \n"
"}"
@@ -183,7 +183,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
+msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
msgstr ""
#. Tag: programlisting
@@ -191,7 +191,7 @@ msgstr ""
msgid ""
"class MyExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" //tell the container to ignore the type if it is annotated @Ignore\n"
" if ( pat.getAnnotatedType().isAnnotionPresent(Ignore.class) ) pat.veto(); \n"
" } \n"
@@ -206,7 +206,7 @@ msgstr "El centro nervioso para extender Web Beans es el objeto Manager
#. Tag: programlisting
#, no-c-format
-msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
+msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
msgstr ""
#. Tag: title
@@ -223,31 +223,31 @@ msgstr "La interfaz Manager nos permite registrar y obtener W
#, no-c-format
msgid ""
"public interface BeanManager {\n"
-" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
-" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
-" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
-" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
-" public Set<Bean<?>> getBeans(String name);\n"
-" public Bean<?> getPassivationCapableBean(String id);\n"
-" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
+" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
+" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
+" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
+" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
+" public Set<Bean<?>> getBeans(String name);\n"
+" public Bean<?> getPassivationCapableBean(String id);\n"
+" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
" public void validate(InjectionPoint injectionPoint);\n"
" public void fireEvent(Object event, Annotation... qualifiers);\n"
-" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
-" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
-" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
-" public boolean isScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
-" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
-" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
-" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
-" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
-" public Context getContext(Class<? extends Annotation> scopeType);\n"
+" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
+" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
+" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
+" public boolean isScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
+" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
+" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
+" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
+" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
+" public Context getContext(Class<? extends Annotation> scopeType);\n"
" public ELResolver getELResolver();\n"
" public ExpressionFactory wrapExpressionFactory(ExpressionFactory expressionFactory);\n"
-" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
-" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
+" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
+" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
"}"
msgstr ""
@@ -268,7 +268,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's study some of the interfaces exposed by the BeanManager."
+msgid "Let's study some of the interfaces exposed by the BeanManager."
msgstr "El centro nervioso para extender Web Beans es el objeto Manager. "
#. Tag: title
@@ -283,21 +283,21 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to instatiate the object itself, and so only method and field injection will be supported."
+msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to insntatiate the object itself, and so only method and field injection will be supported."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"//get the BeanManager from JNDI\n"
-"BeanManager beanManager = (BeanManager) new InitialContext().lookup("java:comp/BeanManager");\n"
+"BeanManager beanManager = (BeanManager) new InitialContext().lookup(\"java:comp/BeanManager\");\n"
"\n"
"//CDI uses an AnnotatedType object to read the annotations of a class\n"
-"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
+"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
"\n"
"//The extension uses an InjectionTarget to delegate instantiation, dependency injection \n"
"//and lifecycle callbacks to the CDI container\n"
-"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
+"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
"\n"
"//each instance needs its own CDI CreationalContext\n"
"CreationalContext ctx = beanManager.createCreationalContext(null);\n"
@@ -327,33 +327,33 @@ msgstr "Instancias de clase abstracta Bean representan Web Be
#. Tag: para
#, no-c-format
-msgid "The Bean interface exposes all the interesting things we dicussed in ."
+msgid "The Bean interface exposes all the interesting things we discussed in ."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"public interface Bean<T> extends Contextual<T> {\n"
-" public Set<Type> getTypes();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Class<? extends Annotation> getScope();\n"
+"public interface Bean<T> extends Contextual<T> {\n"
+" public Set<Type> getTypes();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Class<? extends Annotation> getScope();\n"
" public String getName();\n"
-" public Set<Class<? extends Annotation>> getStereotypes();\n"
-" public Class<?> getBeanClass();\n"
+" public Set<Class<? extends Annotation>> getStereotypes();\n"
+" public Class<?> getBeanClass();\n"
" public boolean isAlternative();\n"
" public boolean isNullable();\n"
-" public Set<InjectionPoint> getInjectionPoints();\n"
+" public Set<InjectionPoint> getInjectionPoints();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's an easy way to find out what beans exist in the application:"
+msgid "There's an easy way to find out what beans exist in the application:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
+msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
msgstr ""
#. Tag: para
@@ -373,7 +373,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
+msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
msgstr ""
#. Tag: programlisting
@@ -384,49 +384,49 @@ msgid ""
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd, BeanManager bm) {\n"
" \n"
" //use this to read annotations of the class\n"
-" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
+" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
"\n"
" //use this to instantiate the class and inject dependencies\n"
-" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
+" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
"\n"
-" abd.addBean( new Bean<SecurityManager>() {\n"
+" abd.addBean( new Bean<SecurityManager>() {\n"
"\n"
" @Override\n"
-" public Class<?> getBeanClass() {\n"
+" public Class<?> getBeanClass() {\n"
" return SecurityManager.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
" public String getName() {\n"
-" return "securityManager";\n"
+" return \"securityManager\";\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getQualifiers() {\n"
-" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
-" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
-" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
+" public Set<Annotation> getQualifiers() {\n"
+" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
+" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
+" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
" return qualifiers;\n"
" }\n"
"\n"
" @Override\n"
-" public Class<? extends Annotation> getScope() {\n"
+" public Class<? extends Annotation> getScope() {\n"
" return SessionScoped.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Class<? extends Annotation>> getStereotypes() {\n"
+" public Set<Class<? extends Annotation>> getStereotypes() {\n"
" return Collections.emptySet();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypes() {\n"
-" Set<Type> types = new HashSet<Type>();\n"
+" public Set<Type> getTypes() {\n"
+" Set<Type> types = new HashSet<Type>();\n"
" types.add(SecurityManager.class);\n"
" types.add(Object.class);\n"
" return types;\n"
@@ -443,7 +443,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
+" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
" SecurityManager instance = it.produce(ctx);\n"
" it.inject(instance, ctx);\n"
" it.postConstruct(instance);\n"
@@ -452,7 +452,7 @@ msgid ""
"\n"
" @Override\n"
" public void destroy(SecurityManager instance, \n"
-" CreationalContext<SecurityManager> ctx) {\n"
+" CreationalContext<SecurityManager> ctx) {\n"
" it.preDestroy(instance);\n"
" it.dispose(instance);\n"
" ctx.release();\n"
@@ -481,7 +481,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
+msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
msgstr ""
#. Tag: programlisting
@@ -489,38 +489,38 @@ msgstr ""
msgid ""
"public class QualifiedNameExtension implements Extension {\n"
"\n"
-" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
+" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
"\n"
" //wrap this to override the annotations of the class\n"
-" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
+" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
" \n"
-" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
+" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
"\n"
" @Override\n"
-" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
+" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
" return at.getConstructors();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedField<? super X>> getFields() {\n"
+" public Set<AnnotatedField<? super X>> getFields() {\n"
" return at.getFields();\n"
" }\n"
"\n"
" @Override\n"
-" public Class<X> getJavaClass() {\n"
+" public Class<X> getJavaClass() {\n"
" return at.getJavaClass();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
+" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
" return at.getMethods();\n"
" }\n"
"\n"
" @Override\n"
-" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
+" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
" if ( Named.class.equals(annType) ) {\n"
" class NamedLiteral \n"
-" extends AnnotationLiteral<Named> \n"
+" extends AnnotationLiteral<Named> \n"
" implements Named {\n"
" @Override\n"
" public String value() {\n"
@@ -529,7 +529,7 @@ msgid ""
" final String qualifiedName;\n"
" if ( pkg.isAnnotationPresent(Named.class) ) {\n"
" qualifiedName = pkg.getAnnotation(Named.class).value() \n"
-" + '.' + unqualifiedName;\n"
+" + '.' + unqualifiedName;\n"
" }\n"
" else {\n"
" qualifiedName = unqualifiedName;\n"
@@ -545,7 +545,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getAnnotations() {\n"
+" public Set<Annotation> getAnnotations() {\n"
" return at.getAnnotations();\n"
" }\n"
"\n"
@@ -555,12 +555,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypeClosure() {\n"
+" public Set<Type> getTypeClosure() {\n"
" return at.getTypeClosure();\n"
" }\n"
"\n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
" return at.isAnnotationPresent(annType);\n"
" }\n"
" \n"
@@ -574,7 +574,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
+msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
msgstr ""
#. Tag: programlisting
@@ -582,17 +582,17 @@ msgstr ""
msgid ""
"class ServiceAlternativeExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" \n"
-" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
+" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
" \n"
" if ( Service.class.isAssignableFrom( type.getJavaClass() ) ) {\n"
" \n"
" //if the class implements Service, make it an @Alternative\n"
-" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
+" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
" \n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
" return annotationType.equals(Alternative.class) ? \n"
" true : type.isAnnotationPresent(annotationType);\n"
" }\n"
@@ -625,7 +625,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
+msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
msgstr ""
#. Tag: programlisting
@@ -645,25 +645,25 @@ msgstr ""
msgid ""
"public class ConfigExtension implements Extension {\n"
"\n"
-"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
+"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
"\t\t\n"
"\t\t//wrap this to intercept the component lifecycle\n"
-"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
+"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
"\t \n"
-" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
+" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
" \n"
" //use this to read annotations of the class and its members\n"
-" AnnotatedType<X> at = pit.getAnnotatedType();\n"
+" AnnotatedType<X> at = pit.getAnnotatedType();\n"
" \n"
" //read the properties file\n"
-" String propsFileName = at.getClass().getSimpleName() + ".properties";\n"
+" String propsFileName = at.getClass().getSimpleName() + \".properties\";\n"
" InputStream stream = at.getJavaClass().getResourceAsStream(propsFileName);\n"
" if (stream!=null) {\n"
" \n"
" try {\n"
" Properties props = new Properties();\n"
" props.load(stream);\n"
-" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
+" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
" String fieldName = property.getKey().toString();\n"
" Object value = property.getValue();\n"
" try {\n"
@@ -675,7 +675,7 @@ msgid ""
" else {\n"
" //TODO: do type conversion automatically\n"
" pit.addDefinitionError( new InjectionException(\n"
-" "field is not of type String: " + field ) );\n"
+" \"field is not of type String: \" + field ) );\n"
" }\n"
" }\n"
" catch (NoSuchFieldException nsfe) {\n"
@@ -691,14 +691,14 @@ msgid ""
" }\n"
" }\n"
" \n"
-" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
+" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
"\n"
" @Override\n"
-" public void inject(X instance, CreationalContext<X> ctx) {\n"
+" public void inject(X instance, CreationalContext<X> ctx) {\n"
" it.inject(instance, ctx);\n"
" \n"
" //set the values onto the new instance of the component\n"
-" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
+" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
" try {\n"
" configuredValue.getKey().set(instance, configuredValue.getValue());\n"
" }\n"
@@ -724,12 +724,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
-" public X produce(CreationalContext<X> ctx) {\n"
+" public X produce(CreationalContext<X> ctx) {\n"
" return it.produce(ctx);\n"
" }\n"
" \n"
@@ -744,7 +744,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
+msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
msgstr ""
#. Tag: title
@@ -761,9 +761,9 @@ msgstr "La interfaz Contexto soporta la adición de nuevos á
#, fuzzy, no-c-format
msgid ""
"public interface Context {\n"
-" public Class<? extends Annotation> getScope();\n"
-" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
-" public <T> T get(Contextual<T> contextual);\n"
+" public Class<? extends Annotation> getScope();\n"
+" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
+" public <T> T get(Contextual<T> contextual);\n"
" boolean isActive();\n"
"}"
msgstr ""
diff --git a/docs/reference/src/main/docbook/es-ES/gettingstarted.po b/docs/reference/src/main/docbook/es-ES/gettingstarted.po
index 5b29ec7e37b..38e4db7438b 100644
--- a/docs/reference/src/main/docbook/es-ES/gettingstarted.po
+++ b/docs/reference/src/main/docbook/es-ES/gettingstarted.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: ri\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-20 10:55+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -24,7 +24,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, Glassfish 3.0 or any compliant Java EE 6 container."
+msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, GlassFish 3.0 or any compliant Java EE 6 container."
msgstr ""
#. Tag: para
@@ -39,7 +39,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To run the examples with the provided build scripts, you'll need the following:"
+msgid "To run the examples with the provided build scripts, you'll need the following:"
msgstr ""
#. Tag: para
@@ -84,12 +84,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
+msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
+msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
msgstr ""
#. Tag: para
@@ -99,7 +99,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
+msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
msgstr ""
#. Tag: title
@@ -109,19 +109,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
+msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
+msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> unzip jboss-6.0.*.zip\n"
-"$> mv jboss-6.0.*/ jboss-as-6.0"
+"$> unzip jboss-6.0.*.zip\n"
+"$> mv jboss-6.0.*/ jboss-as-6.0"
msgstr ""
#. Tag: para
@@ -136,7 +136,7 @@ msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
#, fuzzy, no-c-format
-msgid "You're now ready to deploy your first example!"
+msgid "You're now ready to deploy your first example!"
msgstr "Ahora, ¡está listo para desplegar su primer ejemplo!"
#. Tag: para
@@ -147,22 +147,22 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant deploy"
msgstr ""
"$ cd examples/numberguess\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
+msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/jboss-as-6.0\n"
-"$> ./bin/run.sh"
+"$> cd /path/to/jboss-as-6.0\n"
+"$> ./bin/run.sh"
msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
@@ -171,11 +171,11 @@ msgid "a Windows command window:"
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
-"$> run"
-msgstr ""
+"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
+"$> run"
+msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
#, no-c-format
@@ -230,20 +230,20 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/translator\n"
-"$> ant deploy"
+"$> cd examples/jsf/translator\n"
+"$> ant deploy"
msgstr ""
"$ cd examples/translator\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
+msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
+msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
msgstr "Aquí establecemos la ruta de contexto, la cual nos da una url interesante (http://localhost:8080/webbeans-translator)."
#. Tag: title
@@ -253,41 +253,43 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
+msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
+msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> chmod 755 glassfish-v3-unix.sh\n"
-"$> ./glassfish-v3-unix.sh"
+"$> chmod 755 glassfish-v3-unix.sh\n"
+"$> ./glassfish-v3-unix.sh"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
+msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
+msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
-"$> ant package"
+"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
+"$> ant package"
msgstr ""
+"$ cd examples/numberguess\n"
+"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
+msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
msgstr ""
#. Tag: para
@@ -297,12 +299,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin start-domain domain1"
+msgid "$> asadmin start-domain domain1"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on "Applications", then click on the "Deploy..." button under the heading "Applications" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
+msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on \"Applications\", then click on the \"Deploy...\" button under the heading \"Applications\" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
msgstr ""
#. Tag: para
@@ -312,7 +314,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin deploy target/weld-numberguess.war"
+msgid "$> asadmin deploy target/weld-numberguess.war"
msgstr ""
#. Tag: para
@@ -332,24 +334,24 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
+msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
+msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
msgstr "Luego, descargue la IR de Web Beans desde seamframework.org, y descomprímalo. Por ejemplo:"
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "$> unzip apache-tomcat-6.0.18.zip"
+msgid "$> unzip apache-tomcat-6.0.18.zip"
msgstr ""
""
#. Tag: para
#, no-c-format
-msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
+msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
msgstr ""
#. Tag: title
@@ -359,7 +361,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
+msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
msgstr ""
#. Tag: programlisting
@@ -369,7 +371,7 @@ msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now you're ready to deploy the numberguess example to Tomcat!"
+msgid "Now you're ready to deploy the numberguess example to Tomcat!"
msgstr "Para desplegar el ejemplo numberguess:"
#. Tag: para
@@ -380,15 +382,15 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant tomcat.deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant tomcat.deploy"
msgstr ""
"$ cd examples/numberguess\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with "tomcat."."
+msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with \"tomcat.\"."
msgstr ""
#. Tag: para
@@ -413,21 +415,21 @@ msgstr "ant undeploy - quita el ejemplo del servidor"
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
+msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/apache-tomcat-6\n"
-"$> ./bin/start.sh"
+"$> cd /path/to/apache-tomcat-6\n"
+"$> ./bin/start.sh"
msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
-"$> start"
+"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
+"$> start"
msgstr ""
""
@@ -444,12 +446,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
+msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
+msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
msgstr ""
#. Tag: para
@@ -459,7 +461,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<user username="admin" password="" roles="manager"/>"
+msgid "<user username=\"admin\" password=\"\" roles=\"manager\"/>"
msgstr ""
#. Tag: para
@@ -469,7 +471,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
+msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
msgstr ""
#. Tag: para
@@ -479,7 +481,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn tomcat:redeploy -Ptomcat"
+msgid "$> mvn tomcat:redeploy -Ptomcat"
msgstr ""
#. Tag: para
@@ -494,7 +496,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace tomcat:run -Ptomcat"
+msgid "$> mvn war:inplace tomcat:run -Ptomcat"
msgstr ""
#. Tag: para
@@ -504,12 +506,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Ptomcat"
+msgid "$> mvn compile war:inplace -Ptomcat"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
+msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
msgstr ""
#. Tag: title
@@ -524,12 +526,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
+msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
+msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
msgstr ""
#. Tag: para
@@ -538,11 +540,13 @@ msgid "To run the weld-numberguess example on Jetty, switch t
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> mvn war:inplace jetty:run -Pjetty"
+"$> cd examples/jsf/numberguess\n"
+"$> mvn war:inplace jetty:run -Pjetty"
msgstr ""
+"$ cd examples/numberguess\n"
+"ant deploy"
#. Tag: para
#, no-c-format
@@ -556,7 +560,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Pjetty"
+msgid "$> mvn compile war:inplace -Pjetty"
msgstr ""
#. Tag: para
@@ -566,7 +570,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclispe[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
+msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclipse[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
msgstr ""
#. Tag: para
@@ -576,7 +580,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
+msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
msgstr ""
#. Tag: para
@@ -586,12 +590,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace -Pjetty-ide"
+msgid "$> mvn war:inplace -Pjetty-ide"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using "Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
+msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using \"Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/es-ES/injection.po b/docs/reference/src/main/docbook/es-ES/injection.po
index 2b112d3795e..229410c62dc 100644
--- a/docs/reference/src/main/docbook/es-ES/injection.po
+++ b/docs/reference/src/main/docbook/es-ES/injection.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: injection\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-19 15:18+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -24,7 +24,7 @@ msgstr "Inyección de dependencia"
#. Tag: para
#, no-c-format
-msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
+msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
msgstr ""
#. Tag: title
@@ -149,7 +149,7 @@ msgstr "Luego, el administrador de Web Bean inicializa los valores de los campos
#. Tag: para
#, fuzzy, no-c-format
-msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
+msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
msgstr "Más tarde, el administrador de Web Bean llama a todos los métodos inicializadores del Web Bean."
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
+msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
msgstr ""
#. Tag: title
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
+msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
msgstr "La especificación de Web Beans define un procedimiento, llamado algoritmo de resolución de typesafe que el administrador de Web Bean sigue al identificar el Web Bean para inyectar a un punto de inyección. Este algoritmo parece complejo en un principio, pero una vez que lo entienda, es en realidad muy intuitivo. La resolución de Typesafe se realiza al inicializar el sistema, lo que significa que el administrador informará al usuario inmediatamente si se pueden cumplir las dependencias de un Web Bean, produciendo una UnsatisfiedDependencyException o una AmbiguousDependencyException."
#. Tag: para
@@ -220,12 +220,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
+msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
+msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
msgstr ""
#. Tag: title
@@ -386,7 +386,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you may be thinking, "What's the different between using a qualifier and just specifying the exact implementation class you want?" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alterative implementations of @Asynchronous PaymentProcessor!"
+msgid "Now, you may be thinking, \"What's the different between using a qualifier and just specifying the exact implementation class you want?\" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alternative implementations of @Asynchronous PaymentProcessor!"
msgstr ""
#. Tag: title
@@ -396,7 +396,7 @@ msgstr "Los Web Beans sencillos admiten únicamente las devoluciones de llamadas
#. Tag: para
#, no-c-format
-msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to decare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
+msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to declare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
msgstr ""
#. Tag: para
@@ -408,7 +408,7 @@ msgstr ""
#, no-c-format
msgid ""
"@Inject \n"
-"void initServices(@Any Instance<Service> services) { \n"
+"void initServices(@Any Instance<Service> services) { \n"
" for (Service service: services) {\n"
" service.init();\n"
" }\n"
@@ -444,7 +444,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then we select one of the possible member values when appling the qualifier:"
+msgid "Then we select one of the possible member values when applying the qualifier:"
msgstr ""
#. Tag: programlisting
@@ -465,7 +465,7 @@ msgid ""
"@Target({METHOD, FIELD, PARAMETER, TYPE})\n"
"public @interface PayBy {\n"
" PaymentMethod value();\n"
-" @Nonbinding String comment() default "";\n"
+" @Nonbinding String comment() default \"\";\n"
"}"
msgstr ""
"this FAQ for step-by-step instructions for how to resolve an ambigous resolution exception between a raw bean type and a producer method that returns the same bean type."
+msgid "See this FAQ for step-by-step instructions for how to resolve an ambiguous resolution exception between a raw bean type and a producer method that returns the same bean type."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Just remember: "There can be only one.""
+msgid "Just remember: \"There can be only one.\""
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
+msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
+msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
msgstr "Hay algo más que necesita saber cuando utilice inyección de dependencia en Web Beans."
#. Tag: title
@@ -648,7 +648,7 @@ msgstr "Los clientes de un Web Bean inyectado no suelen mantener una referencia
#. Tag: para
#, fuzzy, no-c-format
-msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
+msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
msgstr "Imagine que un Web Bean vinculado al ámbito de aplicación mantiene una referencia directa a un Web Bean vinculado al ámbito de petición. La aplicación en el ámbito de Web Bean es compartida entre muchas peticiones diferentes. No obstante, cada petición ¡debe ver una instancia diferente de la petición en el ámbito de WebBean!"
#. Tag: para
@@ -673,7 +673,7 @@ msgstr "El administrador de Web Bean no puede aplicar proxy en los siguientes ti
#. Tag: para
#, fuzzy, no-c-format
-msgid "classes which don't have a non-private constructor with no parameters, and"
+msgid "classes which don't have a non-private constructor with no parameters, and"
msgstr "las clases que no tienen un constructor no-privado sin parámetros y "
#. Tag: para
@@ -688,7 +688,7 @@ msgstr "matrices y tipos primarios."
#. Tag: para
#, no-c-format
-msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
+msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
msgstr ""
#. Tag: para
@@ -698,7 +698,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "change the type of the injection point to Instance<X>,"
+msgid "change the type of the injection point to Instance<X>,"
msgstr ""
#. Tag: para
@@ -728,7 +728,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But we didn't get around to implementing this yet."
+msgid "But we didn't get around to implementing this yet."
msgstr ""
#. Tag: title
@@ -763,7 +763,7 @@ msgstr "La aplicación puede obtener una instancia de la interfaz Manag
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -798,7 +798,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -813,19 +813,19 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, we need to obtain an instance of our qualifier type. Since annotatons are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
+msgid "Next, we need to obtain an instance of our qualifier type. Since annotations are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"abstract class AsynchronousQualifier\n"
-"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
+"class AsynchronousQualifier\n"
+"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
msgstr ""
" \n"
@@ -840,14 +840,14 @@ msgstr ""
#, fuzzy, no-c-format
msgid ""
"PaymentProcessor p = paymentProcessorSource\n"
-" .select(new AnnotationLiteral<Asynchronous>() {});"
+" .select(new AnnotationLiteral<Asynchronous>() {});"
msgstr ""
"(){});]]>"
#. Tag: para
#, no-c-format
-msgid "We can't use an anonymous class to implement a qualifier type with members."
+msgid "However, we can't use an anonymous class to implement a qualifier type with members."
msgstr ""
#. Tag: para
@@ -895,7 +895,7 @@ msgstr "Un Web Bean con ámbito @Dependent puede inyectar una
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
+msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
msgstr "Veamos un ejemplo. El código siguiente es detallado, y vulnerable a problemas de refactorización:"
#. Tag: programlisting
@@ -939,7 +939,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
+msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
msgstr "¿No está convencido? Entonces, veamos un segundo ejemplo. Para inyectar parámetros, necesitamos definir el tipo de vinculación:"
#. Tag: programlisting
@@ -967,8 +967,8 @@ msgstr "Utilizaríamos este tipo de enlace en puntos de inyección, como a conti
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@HttpParam("username") String username;\n"
-"@HttpParam("password") String password;"
+"@HttpParam(\"username\") String username;\n"
+"@HttpParam(\"password\") String password;"
msgstr ""
""
@@ -983,7 +983,7 @@ msgstr "El siguiente método de productor sí funciona:"
msgid ""
"class HttpParams\n"
"\n"
-" @Produces @HttpParam("")\n"
+" @Produces @HttpParam(\"\")\n"
" String getParamValue(InjectionPoint ip) {\n"
" ServletRequest request = (ServletRequest) FacesContext.getCurrentInstance().getExternalContext().getRequest();\n"
" return request.getParameter(ip.getAnnotated().getAnnotation(HttpParam.class).value());\n"
@@ -1002,7 +1002,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own prodcuer for the request and have it injected as a method parameter."
+msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own producer for the request and have it injected as a method parameter."
msgstr ""
#. Tag: para
@@ -1020,8 +1020,8 @@ msgstr "El administrador de Web Bean proporciona un Web Bean incorporado que imp
msgid ""
"public interface InjectionPoint { \n"
" public Type getType();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Bean<?> getBean();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Bean<?> getBean();\n"
" public Member getMember();\n"
" public Annotated getAnnotated();\n"
" public boolean isDelegate();\n"
diff --git a/docs/reference/src/main/docbook/es-ES/interceptors.po b/docs/reference/src/main/docbook/es-ES/interceptors.po
index c8cfcb5358f..ee4a06ccba4 100644
--- a/docs/reference/src/main/docbook/es-ES/interceptors.po
+++ b/docs/reference/src/main/docbook/es-ES/interceptors.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: interceptors\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-19 15:37+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -110,7 +110,7 @@ msgstr "Enlaces de interceptor"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
+msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
msgstr "Suponga que deseamos declarar que algunos de nuestros Web Beans son transaccionales. La primera cosa que necesitamos es una anotación de enlace de interceptor para especificar exactamente en cuáles Web Beans estamos interesados:"
#. Tag: programlisting
@@ -163,7 +163,7 @@ msgstr "Implementación de interceptores"
#. Tag: para
#, fuzzy, no-c-format
-msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
+msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
msgstr "Es maravilloso, pero en alguna parte de la línea vamos a tener que implementar realmente el interceptor que proporciona este aspecto de manejo de transacción. Todo lo que debemos hacer es crear un interceptor estándar EJB, y anotar @Interceptor y @Transactional."
#. Tag: programlisting
@@ -225,16 +225,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -265,17 +265,17 @@ msgstr "Por ejemplo, podemos especificar que nuestro interceptor de seguridad se
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -378,7 +378,7 @@ msgstr "Generalmente utilizamos combinaciones de tipos de interceptores de enlac
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Secure(rolesAllowed="admin") @Transactional\n"
+"@Secure(rolesAllowed=\"admin\") @Transactional\n"
"public class ShoppingCart { ... }"
msgstr ""
"meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
+msgid "Well, fortunately, CDI works around this missing feature of Java. We may annotate one interceptor binding type with other interceptor binding types (termed a meta-annotation). The interceptor bindings are transitive — any 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."
#. Tag: programlisting
@@ -533,7 +533,7 @@ msgstr "los interceptores no se pueden fácilmente inhabilitar en el momento del
#. Tag: para
#, fuzzy, 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."
+msgid "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."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/es-ES/intro.po b/docs/reference/src/main/docbook/es-ES/intro.po
index 9b9c0d021c9..7e9707bf336 100644
--- a/docs/reference/src/main/docbook/es-ES/intro.po
+++ b/docs/reference/src/main/docbook/es-ES/intro.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: intro\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-19 16:28+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -24,7 +24,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
+msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
msgstr "Entonces, ¿está preparado para empezar a escribir su primer Web Bean? O quizás está escéptico, preguntándose por qué tipos de arcos le hará ¡saltar la especificación de Web Beans! La buena noticia es que probablemente ya ha escrito y utilizado cientos, quizás miles de Web Beans. Podría no recordar incluso el primer Web Bean que escribió."
#. Tag: title
@@ -39,27 +39,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Prior to Java EE 6, there was no clear definition of the term "bean" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications "beans" for years. There were even a couple of different kinds of things called "beans" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a "bean". What we've been missing is a common definition."
+msgid "Prior to Java EE 6, there was no clear definition of the term \"bean\" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications \"beans\" for years. There were even a couple of different kinds of things called \"beans\" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a \"bean\". What we've been missing is a common definition."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
+msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
+msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
+msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now let's see how to create your first bean that actually uses CDI."
+msgid "Now let's see how to create your first bean that actually uses CDI."
msgstr ""
#. Tag: title
@@ -69,14 +69,14 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
+msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
msgstr "Suponga que tenemos dos clases existentes de Java, las cuales hemos estado utilizando por años en varias aplicaciones. La primera clase analiza una cadena en un lista de oraciones:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
"public class SentenceParser {\n"
-" public List<String> parse(String text) { ... }\n"
+" public List<String> parse(String text) { ... }\n"
"}"
msgstr ""
"TextTranslator no tiene un constructor
#. Tag: para
#, fuzzy, no-c-format
-msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
+msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
msgstr "Como pudo adivinar, la anotación @Initializer tiene algo que ver con la ¡inyección de dependencia! @Initializer puede aplicarse a un constructor o método de un Web Bean, y pide a un administrador de Bean llamar a ese constructor o método cuando inicia el Web Bean. El administrador de Web Bean inyectará otros Web Beans a los parámetros del constructor o método."
#. Tag: para
@@ -184,7 +184,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
+msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
msgstr ""
#. Tag: programlisting
@@ -223,7 +223,7 @@ msgstr "Donde Translator es la interfaz local:"
#. Tag: para
#, no-c-format
-msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
+msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
msgstr ""
#. Tag: para
@@ -234,7 +234,7 @@ msgstr "Podemos obtener una instancia de TextTranslator inyec
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
+"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
"...\n"
"public void translate() {\n"
" textTranslatorInstance.get().translate(inputText);\n"
@@ -247,17 +247,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
+msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
+msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
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 Translator si el EJB de SentenceTranslator no estaba desplegado el administrador de Web Bean produciría una UnsatisfiedDependencyException. Si más de una implementación de Translator estuviera disponible, el administrador de Web Bean produciría una AmbiguousDependencyException."
#. Tag: para
#, no-c-format
-msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
+msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
msgstr ""
#~ msgid "Getting started with Web Beans"
diff --git a/docs/reference/src/main/docbook/es-ES/next.po b/docs/reference/src/main/docbook/es-ES/next.po
index b73ab9a7a11..4b9247954a4 100644
--- a/docs/reference/src/main/docbook/es-ES/next.po
+++ b/docs/reference/src/main/docbook/es-ES/next.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: next\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-20 09:48+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -24,12 +24,12 @@ msgstr "Siguientes pasos"
#. Tag: para
#, no-c-format
-msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
+msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
+msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
msgstr "La implementación de Referencia (IR) de Web Beans se desarrolla en http://seamframework.org/WebBeans. El equipo de desarrollo de la IR y la especificación de Web Beans lideran el Blog en http://in.relation.to. Este artículo se base en una serie de entradas de Blog publicadas allí."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/es-ES/part1.po b/docs/reference/src/main/docbook/es-ES/part1.po
index 950a91c8033..68c5aba3257 100644
--- a/docs/reference/src/main/docbook/es-ES/part1.po
+++ b/docs/reference/src/main/docbook/es-ES/part1.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: part1\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-19 16:38+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -129,7 +129,7 @@ msgstr "¿Necesito destruirlo explícitamente?"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Where should I keep the reference to it when I'm not currently using it?"
+msgid "Where should I keep the reference to it when I'm not currently using it?"
msgstr "¿Dónde debo guardar mi referencia a éste cuando no lo estoy usando directamente?"
#. Tag: para
@@ -144,7 +144,7 @@ msgstr "¿Cómo hago para compartir este objeto con otros objetos?"
#. Tag: para
#, no-c-format
-msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
+msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
msgstr ""
#. Tag: para
@@ -174,12 +174,12 @@ msgstr "los decoradores permiten la compartimentación de l
#. Tag: para
#, fuzzy, no-c-format
-msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
+msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
msgstr "Más importante, Web Beans ofrece todos los servicios en formatypesafe. Web Beans nunca utiliza identificadores de cadena para determinar cómo los se ajustan entre sí objetos de colaboración. Además, aunque XML sigue siendo una opción, muy rara vez se utiliza. En su lugar, Web Beans usa la información de teclado disponible en el modelo de objeto Java junto con un nuevo patrón, llamado anotaciones de enlace, para conectar a Web Beans, las dependencias, los interceptores y decoradores y sus consumidores de evento."
#. Tag: para
#, no-c-format
-msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
+msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
msgstr ""
#. Tag: para
@@ -189,7 +189,7 @@ msgstr "Web Beans incluso provee los puntos de integración necesarios para que
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
+msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
msgstr "Una gran cantidad de marcos existentes de Java, incluyendo Seam, Guice y Spring, influyeron en Web Beans. No obstante, Web Beans tiene su propio carácter distintivo: más typesafe que Seam, más con estado y menos centrada en XML que Spring, red y aplicación empresarial más capaz que Guice."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/es-ES/part3.po b/docs/reference/src/main/docbook/es-ES/part3.po
index 0d7cb1ddd5b..6b7c6f1177d 100644
--- a/docs/reference/src/main/docbook/es-ES/part3.po
+++ b/docs/reference/src/main/docbook/es-ES/part3.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: part3\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-19 16:46+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -19,7 +19,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
+msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
msgstr ""
#. Tag: para
@@ -74,7 +74,7 @@ msgstr "El segundo tema importante de Web Beans es el tecleado fuerte<
#. Tag: para
#, fuzzy, no-c-format
-msgid "You don't see string-based identifiers in CDI 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!"
+msgid "You don't see string-based identifiers in CDI 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
@@ -144,7 +144,7 @@ msgstr "Los estereotipos de Web Beans van más allá de est
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
+msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
msgstr "Ahora estamos listos para conocer otras funciones más avanzadas de Web Beans. Tenga en cuenta que estas funciones hacen a nuestro código más fácil de validar y más entendible. La mayoría del tiempo no se necesita realmente utilizarlas, pero si se utilizan de modo inteligente, se llegará a apreciar su poder."
#~ msgid "Even Web Beans XML metadata is strongly typed! There's no compiler for XML, so Web Beans takes advantage of XML schemas to validate the Java types and attributes that appear in XML. This approach turns out to make the XML more literate, just like annotations made our Java code more literate."
diff --git a/docs/reference/src/main/docbook/es-ES/part4.po b/docs/reference/src/main/docbook/es-ES/part4.po
index 32d7466ffda..a39b015b699 100644
--- a/docs/reference/src/main/docbook/es-ES/part4.po
+++ b/docs/reference/src/main/docbook/es-ES/part4.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: part4\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-19 16:49+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -19,7 +19,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
+msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
msgstr ""
#. Tag: para
@@ -29,7 +29,7 @@ msgstr "Ya hemos visto cómo Web Beans ayuda a integrar EJB y JSF, permitiendo a
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
+msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
msgstr "Ya estamos a punto de ver cómo aprovechar completamente la plataforma de Java EE en una aplicación que utiliza Web Beans. También veremos brevemente una serie de SPI provistas para soportar extensiones a Web Beans. Puede que nunca las tenga que utilizar directamente, pero es conveniente saber que están allí si se necesitan. Lo más importante, es que podrá aprovecharlas indirectamente cada vez que utilice una extensión de terceras partes."
#~ msgid "The third theme of Web Beans is integration. Web Beans was designed to work in concert with other technologies, helping the application developer fit the other technologies together. Web Beans is an open technology. It forms a part of the Java EE ecosystem, and is itself the foundation for a new ecosystem of portable extensions and integration with existing frameworks and technologies."
diff --git a/docs/reference/src/main/docbook/es-ES/part5.po b/docs/reference/src/main/docbook/es-ES/part5.po
index 77158485b28..bc449a7ea8e 100644
--- a/docs/reference/src/main/docbook/es-ES/part5.po
+++ b/docs/reference/src/main/docbook/es-ES/part5.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-28 17:09+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and Glassfish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
+msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and GlassFish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/es-ES/producermethods.po b/docs/reference/src/main/docbook/es-ES/producermethods.po
index cbbc6fe92cb..8de60c2fa33 100644
--- a/docs/reference/src/main/docbook/es-ES/producermethods.po
+++ b/docs/reference/src/main/docbook/es-ES/producermethods.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: producermethods\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-19 17:00+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -24,7 +24,7 @@ msgstr "Métodos de productor"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
+msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
msgstr "Los métodos de productor nos permiten sobrepasar algunas limitaciones que se presentan cuando el administrador de Web Bean, en lugar de la aplicación, es responsable de instanciar objetos. También son la forma más fácil de integrar objetos que no son Web Beans dentro del entorno de Web Beans. (Veremos un segundo método en .)"
#. Tag: para
@@ -79,7 +79,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
+msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
msgstr ""
#. Tag: programlisting
@@ -161,7 +161,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
+msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
msgstr "Ahora, cuando el método de productor es llamado, el PaymentStrategy devuelto se enlazará con el contexto de sesión. El método de productor no será llamado otra vez en la misma sesión."
#. Tag: para
@@ -176,12 +176,12 @@ msgstr "Inyección dentro de métodos de productor"
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
+msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
msgstr "No hay un problema en potencia con el código anterior. Las implementaciones de CreditCardPaymentStrategy son instanciadas mediante el operador nuevo de Java. Los objetos instanciados directamente por la aplicación no pueden hacer uso de la inyección de dependencia y no tienen interceptores."
#. Tag: para
#, fuzzy, no-c-format
-msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
+msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
msgstr "Si esto no es lo que deseamos podemos utilizar la inyección de dependencia dentro del método del productor para obtener las instancias de Web Bean:"
#. Tag: programlisting
@@ -213,12 +213,12 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of "promoting" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left "hanging" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
+msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of \"promoting\" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left \"hanging\" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
msgstr "Espere, ¿qué sucede si CreditCardPaymentStrategy es una petición en ámbito de Web Bean? Entonces el método del productor tiene el efecto de \"promover\" la instancia de petición en ámbito actual dentro del ámbito de sesión. ¡Esto casi seguro es un error! El objeto en ámbito de petición será destruido por el administrador de Web Bean antes de finalizar la sesión, pero la referencia al objeto se dejará \"colgando\" en el ámbito de sesión. Este error no será detectado por el administrador de Web Bean, entonces, ¡por favor tenga un cuidado especial al retornar instancias de Web Bean desde métodos de productor!"
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
+msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
msgstr "Hay por lo menos tres formas de corregir este error. Podemos cambiar el ámbito de la implementación CreditCardPaymentStrategy, pero podría afectar a otros clientes de ese Web Bean. Una mejor opción sería cambiar el ámbito del método del productor a @Dependent o @RequestScoped."
#. Tag: para
@@ -265,7 +265,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
+msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
msgstr "Entonces una nueva instancia dependiente deCreditCardPaymentStrategy será creada, pasada al método de productor, devuelta por el método de productor y finalmente vinculada al contexto de sesión. El objeto dependiente no será destruido hasta que el objeto Preferencias sea destruido, al final de la sesión."
#. Tag: title
diff --git a/docs/reference/src/main/docbook/es-ES/resources.po b/docs/reference/src/main/docbook/es-ES/resources.po
index d235c43a42a..e2c7b2227c1 100644
--- a/docs/reference/src/main/docbook/es-ES/resources.po
+++ b/docs/reference/src/main/docbook/es-ES/resources.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a nonportable "mapped name"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
+msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a non-portable \"mapped name\"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
msgstr ""
#. Tag: para
@@ -72,35 +72,35 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @WebServiceRef(lookup="java:app/service/Catalog")\n"
+"@Produces @WebServiceRef(lookup=\"java:app/service/Catalog\")\n"
"Catalog catalog;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @Resource(lookup="java:global/env/jdbc/CustomerDatasource") \n"
+"@Produces @Resource(lookup=\"java:global/env/jdbc/CustomerDatasource\") \n"
"@CustomerDatabase Datasource customerDatabase;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceContext(unitName="CustomerDatabase")\n"
+"@Produces @PersistenceContext(unitName=\"CustomerDatabase\")\n"
"@CustomerDatabase EntityManager customerDatabasePersistenceContext;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceUnit(unitName="CustomerDatabase") \n"
+"@Produces @PersistenceUnit(unitName=\"CustomerDatabase\") \n"
"@CustomerDatabase EntityManagerFactory customerDatabasePersistenceUnit;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @EJB(ejbLink="../their.jar#PaymentService") \n"
+"@Produces @EJB(ejbLink=\"../their.jar#PaymentService\") \n"
"PaymentService paymentService;"
msgstr ""
@@ -126,7 +126,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
+msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
msgstr ""
#. Tag: title
@@ -171,7 +171,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
+msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
msgstr ""
#. Tag: programlisting
@@ -186,7 +186,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@PersistenceContext(unitName="CustomerDatabase") EntityManager"
+msgid "@PersistenceContext(unitName=\"CustomerDatabase\") EntityManager"
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/es-ES/ri-spi.po b/docs/reference/src/main/docbook/es-ES/ri-spi.po
index 6b21d87663c..bedd7eb847e 100644
--- a/docs/reference/src/main/docbook/es-ES/ri-spi.po
+++ b/docs/reference/src/main/docbook/es-ES/ri-spi.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: ri-spi\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-20 10:15+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -34,7 +34,7 @@ msgstr "Carga de recurso"
#. Tag: para
#, no-c-format
-msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the "Weld: Servlets" extension will be sufficient, and will work in any container supporting the Servlet API."
+msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the \"Weld: Servlets\" extension will be sufficient, and will work in any container supporting the Servlet API."
msgstr ""
#. Tag: para
@@ -59,7 +59,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
+msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
msgstr ""
#. Tag: para
@@ -79,7 +79,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
+msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
msgstr ""
#. Tag: para
@@ -99,7 +99,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
+msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
msgstr ""
#. Tag: para
@@ -109,12 +109,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
+msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
+msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
msgstr ""
#. Tag: para
@@ -129,7 +129,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
+msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
msgstr ""
#. Tag: para
@@ -159,7 +159,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
+msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
msgstr ""
#. Tag: para
@@ -199,7 +199,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
+msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
msgstr ""
#. Tag: title
@@ -214,7 +214,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
+msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
msgstr ""
#. Tag: para
@@ -279,7 +279,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); intercepter will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
+msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); interceptor will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
msgstr ""
#. Tag: para
@@ -354,7 +354,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
+msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
msgstr ""
#. Tag: title
@@ -369,7 +369,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programtically, or built in). Bean validation will validate all beans."
+msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programmatically, or built in). Bean validation will validate all beans."
msgstr ""
#. Tag: para
@@ -429,7 +429,7 @@ msgstr "Aislamiento de classloader"
#. Tag: para
#, fuzzy, no-c-format
-msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuation, classloader isolation for each CDI application."
+msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuration, classloader isolation for each CDI application."
msgstr "Si se está integrando la IR de Web Beans dentro de un entorno que admite despliegue de varias aplicaciones, debe habilitar el aislamiento de classloader para cada aplicación de Web Beans, de forma automática o a través de la configuración del usuario."
#. Tag: term
@@ -444,7 +444,7 @@ msgstr "Si usted está integrando el Web Beans en un entorno de Servlet debe reg
#. Tag: para
#, no-c-format
-msgid "You must ensure that that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
+msgid "You must ensure that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
msgstr ""
#. Tag: term
@@ -585,7 +585,7 @@ msgid ""
"InjectionTarget it = weldBeanManager.fireProcessInjectionTarget(clazz);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
+"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
"\n"
"// Produce the instance, performing any constructor injection required\n"
"Object instance = it.produce();\n"
@@ -619,16 +619,16 @@ msgstr ""
msgid ""
"// Obtain the EjbDescriptor for the EJB\n"
"// You may choose to use this utility method to get the descriptor\n"
-"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
+"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
"\n"
"// Get an the Bean object\n"
-"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
+"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
"\n"
"// Create the injection target\n"
"InjectionTarget it = deploymentBeanManager.createInjectionTarget(ejbDescriptor);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
+"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
"\n"
"// Perform injection and call initializers\n"
"it.inject(instance, cc);\n"
diff --git a/docs/reference/src/main/docbook/es-ES/scopescontexts.po b/docs/reference/src/main/docbook/es-ES/scopescontexts.po
index 8edaa9947c6..f34f2004143 100644
--- a/docs/reference/src/main/docbook/es-ES/scopescontexts.po
+++ b/docs/reference/src/main/docbook/es-ES/scopescontexts.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: scopescontexts\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-20 11:45+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -24,7 +24,7 @@ msgstr "Ámbitos y contextos"
#. Tag: para
#, fuzzy, no-c-format
-msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
+msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
msgstr "Hasta ahora, hemos visto algunos ejemplos de anotaciones de tipo ámbito. El ámbito de un Web Bean determina el ciclo de vida de instancias del Web Bean. El ámbito también determina qué clientes se refieren a qué instancias del Web Bean. Según la especificación de Web Beans, un ámbito determina:"
#. Tag: para
@@ -49,7 +49,7 @@ msgstr "Por ejemplo, si tenemos una sesión con ámbito Web Bean, Usuar
#. Tag: para
#, no-c-format
-msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
+msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
msgstr ""
#. Tag: title
@@ -59,7 +59,7 @@ msgstr "Tipos de ámbito"
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
+msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
msgstr "Web Beans ofrece un modelo contextual extensible. Es posible definir nuevos ámbitos creando una nueva anotación de tipo de ámbito:"
#. Tag: programlisting
@@ -77,7 +77,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
+msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
msgstr "Claro está que esa es la parte fácil. Para que este tipo de ámbito sea útil, necesitaremos también definir un objeto Contexto que implemente el ámbito. La implementación de un Contexto suele ser una tarea muy técnica, únicamente destinada a desarrollo de marco."
#. Tag: para
@@ -96,7 +96,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Usually, you'll use one of CDI's built-in scopes."
+msgid "Usually, you'll use one of CDI's built-in scopes."
msgstr "Por lo general, se utilizará uno de los ámbitos incorporados de Web Beans."
#. Tag: title
@@ -196,7 +196,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
+msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
msgstr "Tres de los ámbitos incorporados deben ser extremadamente familiares a cualquier desarrollador de Java EE, por eso no perdamos tiempo en explicarlos aquí. No obstante, uno de los ámbitos es nuevo."
#. Tag: title
@@ -221,7 +221,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
+msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
msgstr "Una conversación representa una tarea, una unidad de trabajo desde el punto de vista del usuario. El contexto de conversación mantiene un estado asociado con lo que el usuario está actualmente trabajando. Si el usuario está trabajando en varias tareas al mismo tiempo, habrá múltiples conversaciones."
#. Tag: para
@@ -344,25 +344,25 @@ msgstr "Por consiguiente, el siguiente enlace propaga la conversación:"
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "<a href="/addProduct.jsp?cid=#{conversation.id}">Add Product</a>"
+msgid "<a href=\"/addProduct.jsp?cid=#{conversation.id}\">Add Product</a>"
msgstr "Add Product]]>"
#. Tag: para
#, no-c-format
-msgid "It's probably better to use one of the link components in JSF 2:"
+msgid "It's probably better to use one of the link components in JSF 2:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:link outcome="/addProduct.xhtml" value="Add Product">\n"
-" <f:param name="cid" value="#{javax.enterprise.context.conversation.id}"/>\n"
-"</h:link>"
+"<h:link outcome=\"/addProduct.xhtml\" value=\"Add Product\">\n"
+" <f:param name=\"cid\" value=\"#{javax.enterprise.context.conversation.id}\"/>\n"
+"</h:link>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a "flash" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
+msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a \"flash\" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
msgstr "El administrador de Web Bean también se requiere para propagar conversaciones a través de cualquier redirección, incluso si la conversación no está marcada como larga. Esto facilita mucho la implementación del patrón de POST-luego-redirigir, sin recurrir a construcciones frágiles tales como un objeto \"flash\". En este caso, el administrador de Web Bean agrega automáticamente un parámetro a la URL de redirección."
#. Tag: title
@@ -372,7 +372,7 @@ msgstr "Pausa de conversación"
#. Tag: para
#, fuzzy, no-c-format
-msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
+msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
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
@@ -402,12 +402,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can guess what "singleton" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
+msgid "You can guess what \"singleton\" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
+msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
msgstr ""
#. Tag: para
@@ -427,7 +427,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
+msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
msgstr ""
#. Tag: para
@@ -467,12 +467,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
+msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
+msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
msgstr ""
#. Tag: para
@@ -541,7 +541,7 @@ msgstr "El campo calculadora tiene una instancia de conversac
#. Tag: para
#, fuzzy, no-c-format
-msgid "This feature is particularly useful with producer methods, as we'll see in the next chapter."
+msgid "This feature is particularly useful with producer methods, as we'll see in ."
msgstr "La función es particularmente útil con métodos de productor, así como veremos en el siguiente capítulo."
#~ msgid "@RequestScoped"
diff --git a/docs/reference/src/main/docbook/es-ES/specialization.po b/docs/reference/src/main/docbook/es-ES/specialization.po
index badcff8b9ae..72f28820b3d 100644
--- a/docs/reference/src/main/docbook/es-ES/specialization.po
+++ b/docs/reference/src/main/docbook/es-ES/specialization.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: specialization\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-20 11:16+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -24,7 +24,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
+msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
msgstr ""
#. Tag: para
@@ -44,12 +44,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
+msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
+msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
msgstr ""
#. Tag: title
@@ -78,7 +78,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
+msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
msgstr "Pero en nuestro entorno, omitimos esa implementación de PaymentProcessor con un Web Bean diferente:"
#. Tag: programlisting
@@ -118,12 +118,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
+msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
+msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
msgstr ""
#. Tag: programlisting
@@ -164,16 +164,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <alternatives>\n"
-" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
-" </alternatives>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <alternatives>\n"
+" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
+" </alternatives>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -198,7 +198,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
+msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
msgstr ""
#. Tag: para
@@ -258,7 +258,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
+msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/es-ES/stereotypes.po b/docs/reference/src/main/docbook/es-ES/stereotypes.po
index c7c5a837622..1caec8a8b5d 100644
--- a/docs/reference/src/main/docbook/es-ES/stereotypes.po
+++ b/docs/reference/src/main/docbook/es-ES/stereotypes.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: stereotypes\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-20 11:23+1000\n"
"Last-Translator: Gladys Guerrero Lozano \n"
"Language-Team: Spanish \n"
@@ -102,7 +102,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
+msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
msgstr ""
#. Tag: title
@@ -145,7 +145,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
+msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
msgstr ""
#. Tag: title
@@ -265,12 +265,12 @@ msgstr "Estereotipos"
#. Tag: para
#, no-c-format
-msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
+msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
+msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
msgstr ""
#. Tag: programlisting
@@ -297,7 +297,7 @@ msgstr "Estereotipos estándar"
#. Tag: para
#, fuzzy, no-c-format
-msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
+msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
msgstr "Ya hemos visto dos estereotipos estándar definidos por la especificación de Web Beans: @Interceptor y @Decorator."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/es-ES/weldexamples.po b/docs/reference/src/main/docbook/es-ES/weldexamples.po
index 9a03b2ac778..6d2b64a26eb 100644
--- a/docs/reference/src/main/docbook/es-ES/weldexamples.po
+++ b/docs/reference/src/main/docbook/es-ES/weldexamples.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
+msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
msgstr ""
#. Tag: title
@@ -31,75 +31,75 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
+msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
+msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
+msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<faces-config version="2.0"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<faces-config version=\"2.0\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd">\n"
-"</faces-config>"
+" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd\">\n"
+"</faces-config>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
+msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, there's the familiar web.xml:"
+msgid "Finally, there's the familiar web.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<web-app version="2.5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<web-app version=\"2.5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd\">\n"
" \n"
-" <display-name>weld-jsf-numberguess-war</display-name>\n"
-" <description>Weld JSF numberguess example (war)</description>\n"
+" <display-name>weld-jsf-numberguess-war</display-name>\n"
+" <description>Weld JSF numberguess example (war)</description>\n"
"\n"
-" <servlet>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
-" <load-on-startup>1</load-on-startup>\n"
-" </servlet>\n"
+" <servlet>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
+" <load-on-startup>1</load-on-startup>\n"
+" </servlet>\n"
"\n"
-" <servlet-mapping>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <url-pattern>*.jsf</url-pattern>\n"
-" </servlet-mapping>\n"
+" <servlet-mapping>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <url-pattern>*.jsf</url-pattern>\n"
+" </servlet-mapping>\n"
" \n"
-" <context-param>\n"
-" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
-" <param-value>.xhtml</param-value>\n"
-" </context-param>\n"
+" <context-param>\n"
+" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
+" <param-value>.xhtml</param-value>\n"
+" </context-param>\n"
"\n"
-" <session-config>\n"
-" <session-timeout>10</session-timeout>\n"
-" </session-config>\n"
+" <session-config>\n"
+" <session-timeout>10</session-timeout>\n"
+" </session-config>\n"
"\n"
-"</web-app>"
+"</web-app>"
msgstr ""
#. Tag: para
@@ -129,51 +129,51 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
+msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"\n"
-" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">\n"
-"<html xmlns="http://www.w3.org/1999/xhtml"\n"
-" xmlns:ui="http://java.sun.com/jsf/facelets"\n"
-" xmlns:h="http://java.sun.com/jsf/html"\n"
-" xmlns:f="http://java.sun.com/jsf/core">\n"
+"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
+" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n"
+"<html xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" xmlns:ui=\"http://java.sun.com/jsf/facelets\"\n"
+" xmlns:h=\"http://java.sun.com/jsf/html\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\">\n"
"\n"
-" <ui:composition template="/template.xhtml">\n"
-" <ui:define name="content">\n"
-" <h1>Guess a number...</h1>\n"
-" <h:form id="numberGuess">\n"
-" <div style="color: red">\n"
-" <h:messages id="messages" globalOnly="false"/>\n"
-" <h:outputText id="Higher" value="Higher!"\n"
-" rendered="#{game.number gt game.guess and game.guess ne 0}"/>\n"
-" <h:outputText id="Lower" value="Lower!"\n"
-" rendered="#{game.number lt game.guess and game.guess ne 0}"/>\n"
-" </div>\n"
+" <ui:composition template=\"/template.xhtml\">\n"
+" <ui:define name=\"content\">\n"
+" <h1>Guess a number...</h1>\n"
+" <h:form id=\"numberGuess\">\n"
+" <div style=\"color: red\">\n"
+" <h:messages id=\"messages\" globalOnly=\"false\"/>\n"
+" <h:outputText id=\"Higher\" value=\"Higher!\"\n"
+" rendered=\"#{game.number gt game.guess and game.guess ne 0}\"/>\n"
+" <h:outputText id=\"Lower\" value=\"Lower!\"\n"
+" rendered=\"#{game.number lt game.guess and game.guess ne 0}\"/>\n"
+" </div>\n"
" \n"
-" <div>\n"
-" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
+" <div>\n"
+" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
" You have #{game.remainingGuesses} guesses remaining.\n"
-" </div>\n"
+" </div>\n"
" \n"
-" <div>\n"
+" <div>\n"
" Your guess: \n"
-" <h:inputText id="inputGuess" value="#{game.guess}"\n"
-" size="3" required="true" disabled="#{game.number eq game.guess}"\n"
-" validator="#{game.validateNumberRange}"/>\n"
-" <h:commandButton id="guessButton" value="Guess" \n"
-" action="#{game.check}" disabled="#{game.number eq game.guess}"/>\n"
-" </div>\n"
-" <div>\n"
-" <h:commandButton id="restartButton" value="Reset" action="#{game.reset}" immediate="true"/>\n"
-" </div>\n"
-" </h:form>\n"
-" </ui:define>\n"
-" </ui:composition>\n"
-"</html>"
+" <h:inputText id=\"inputGuess\" value=\"#{game.guess}\"\n"
+" size=\"3\" required=\"true\" disabled=\"#{game.number eq game.guess}\"\n"
+" validator=\"#{game.validateNumberRange}\"/>\n"
+" <h:commandButton id=\"guessButton\" value=\"Guess\" \n"
+" action=\"#{game.check}\" disabled=\"#{game.number eq game.guess}\"/>\n"
+" </div>\n"
+" <div>\n"
+" <h:commandButton id=\"restartButton\" value=\"Reset\" action=\"#{game.reset}\" immediate=\"true\"/>\n"
+" </div>\n"
+" </h:form>\n"
+" </ui:define>\n"
+" </ui:composition>\n"
+"</html>"
msgstr ""
#. Tag: para
@@ -183,7 +183,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are a number of messages which can be sent to the user, "Higher!", "Lower!" and "Correct!""
+msgid "There are a number of messages which can be sent to the user, \"Higher!\", \"Lower!\" and \"Correct!\""
msgstr ""
#. Tag: para
@@ -198,7 +198,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
+msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
msgstr ""
#. Tag: para
@@ -266,7 +266,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Generator is application scoped, so we don't get a different random each time."
+msgid "The Generator is application scoped, so we don't get a different random each time."
msgstr ""
#. Tag: para
@@ -276,12 +276,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
+msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
+msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
msgstr ""
#. Tag: programlisting
@@ -298,19 +298,19 @@ msgid ""
" private int remainingGuesses;\n"
"\n"
" @Inject @MaxNumber private int maxNumber;\n"
-" @Inject @Random Instance<Integer> randomNumber;\n"
+" @Inject @Random Instance<Integer> randomNumber;\n"
" \n"
" public Game() {}\n"
" \n"
" public void check() {\n"
-" if (guess > number) {\n"
+" if (guess > number) {\n"
" biggest = guess - 1;\n"
" }\n"
-" else if (guess < number) {\n"
+" else if (guess < number) {\n"
" smallest = guess + 1;\n"
" }\n"
" else if (guess == number) {\n"
-" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage("Correct!"));\n"
+" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage(\"Correct!\"));\n"
" }\n"
" remainingGuesses--;\n"
" }\n"
@@ -325,18 +325,18 @@ msgid ""
" }\n"
" \n"
" public void validateNumberRange(FacesContext context, UIComponent toValidate, Object value) {\n"
-" if (remainingGuesses <= 0) {\n"
-" FacesMessage message = new FacesMessage("No guesses left!");\n"
+" if (remainingGuesses <= 0) {\n"
+" FacesMessage message = new FacesMessage(\"No guesses left!\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" ((UIInput) toValidate).setValid(false);\n"
" return;\n"
" }\n"
" int input = (Integer) value;\n"
"\n"
-" if (input < smallest || input > biggest) {\n"
+" if (input < smallest || input > biggest) {\n"
" ((UIInput) toValidate).setValid(false);\n"
"\n"
-" FacesMessage message = new FacesMessage("Invalid guess");\n"
+" FacesMessage message = new FacesMessage(\"Invalid guess\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" }\n"
" }\n"
@@ -385,20 +385,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
+msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
+msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
msgstr ""
#. Tag: title
@@ -418,17 +418,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin ."
+msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects . Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
+msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects. Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This will create a project in your workspace called weld-se-numberguess ."
+msgid "This will create a project in your workspace called weld-se-numberguess."
msgstr ""
#. Tag: para
@@ -438,7 +438,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to get the example running!"
+msgid "It's time to get the example running!"
msgstr ""
#. Tag: title
@@ -448,12 +448,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
+msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right click on the project, and choose Run As -> Run As Application:"
+msgid "Right click on the project, and choose Run As -> Run As Application:"
msgstr ""
#. Tag: para
@@ -503,7 +503,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's have a look at the significant code and configuration files that make up this example."
+msgid "Let's have a look at the significant code and configuration files that make up this example."
msgstr ""
#. Tag: para
@@ -513,7 +513,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
+msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
msgstr ""
#. Tag: programlisting
@@ -558,7 +558,7 @@ msgid ""
"\n"
" public boolean isGameLost()\n"
" {\n"
-" return guess != number && remainingGuesses <= 0;\n"
+" return guess != number && remainingGuesses <= 0;\n"
" }\n"
"\n"
" public boolean check()\n"
@@ -567,12 +567,12 @@ msgid ""
"\n"
" if (checkNewNumberRangeIsValid())\n"
" {\n"
-" if (guess > number)\n"
+" if (guess > number)\n"
" {\n"
" biggest = guess - 1;\n"
" }\n"
"\n"
-" if (guess < number)\n"
+" if (guess < number)\n"
" {\n"
" smallest = guess + 1;\n"
" }\n"
@@ -590,7 +590,7 @@ msgid ""
"\n"
" private boolean checkNewNumberRangeIsValid()\n"
" {\n"
-" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
+" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
" }\n"
"\n"
" @PostConstruct\n"
@@ -607,12 +607,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
+msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
+msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
msgstr ""
#. Tag: para
@@ -642,12 +642,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
+msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
+msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
msgstr ""
#. Tag: programlisting
@@ -660,11 +660,11 @@ msgid ""
"\n"
" public String getChallengeMessage()\n"
" {\n"
-" StringBuilder challengeMsg = new StringBuilder("I'm thinking of a number between ");\n"
+" StringBuilder challengeMsg = new StringBuilder(\"I'm thinking of a number between \");\n"
" challengeMsg.append(game.getSmallest());\n"
-" challengeMsg.append(" and ");\n"
+" challengeMsg.append(\" and \");\n"
" challengeMsg.append(game.getBiggest());\n"
-" challengeMsg.append(". Can you guess what it is?");\n"
+" challengeMsg.append(\". Can you guess what it is?\");\n"
"\n"
" return challengeMsg.toString();\n"
" }\n"
@@ -673,34 +673,34 @@ msgid ""
" {\n"
" if (game.isGameWon())\n"
" {\n"
-" return "You guessed it! The number was " + game.getNumber();\n"
+" return \"You guessed it! The number was \" + game.getNumber();\n"
" }\n"
" else if (game.isGameLost())\n"
" {\n"
-" return "You are fail! The number was " + game.getNumber();\n"
+" return \"You are fail! The number was \" + game.getNumber();\n"
" }\n"
" else if (!game.isValidNumberRange())\n"
" {\n"
-" return "Invalid number range!";\n"
+" return \"Invalid number range!\";\n"
" }\n"
" else if (game.getRemainingGuesses() == Game.MAX_NUM_GUESSES)\n"
" {\n"
-" return "What is your first guess?";\n"
+" return \"What is your first guess?\";\n"
" }\n"
" else\n"
" {\n"
" String direction = null;\n"
"\n"
-" if (game.getGuess() < game.getNumber())\n"
+" if (game.getGuess() < game.getNumber())\n"
" {\n"
-" direction = "Higher";\n"
+" direction = \"Higher\";\n"
" }\n"
" else\n"
" {\n"
-" direction = "Lower";\n"
+" direction = \"Lower\";\n"
" }\n"
"\n"
-" return direction + "! You have " + game.getRemainingGuesses() + " guesses left.";\n"
+" return direction + \"! You have \" + game.getRemainingGuesses() + \" guesses left.\";\n"
" }\n"
" }\n"
"}"
@@ -713,7 +713,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
+msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
msgstr ""
#. Tag: para
@@ -783,7 +783,7 @@ msgid ""
" private void refreshUI() {\n"
" mainLabel.setText( msgGenerator.getChallengeMessage() );\n"
" messageLabel.setText( msgGenerator.getResultMessage() );\n"
-" guessText.setText( "" );\n"
+" guessText.setText( \"\" );\n"
" guessesLeftBar.setValue( game.getRemainingGuesses() );\n"
" guessText.requestFocus();\n"
" }\n"
@@ -818,7 +818,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
+msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
msgstr ""
#. Tag: para
@@ -828,7 +828,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Calls game.check() to validate and perform one 'turn' of the game"
+msgid "Calls game.check() to validate and perform one 'turn' of the game"
msgstr ""
#. Tag: para
@@ -853,7 +853,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
+msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
msgstr ""
#. Tag: para
@@ -863,25 +863,25 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
+msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<plugin>\n"
-" <groupId>org.apache.maven.plugins</groupId>\n"
-" <artifactId>maven-ear-plugin</artifactId>\n"
-" <configuration>\n"
-" <modules>\n"
-" <webModule>\n"
-" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
-" <artifactId>weld-jsf-translator-war</artifactId>\n"
-" <contextRoot>/weld-translator</contextRoot>\n"
-" </webModule>\n"
-" </modules>\n"
-" </configuration>\n"
-"</plugin>"
+"<plugin>\n"
+" <groupId>org.apache.maven.plugins</groupId>\n"
+" <artifactId>maven-ear-plugin</artifactId>\n"
+" <configuration>\n"
+" <modules>\n"
+" <webModule>\n"
+" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
+" <artifactId>weld-jsf-translator-war</artifactId>\n"
+" <contextRoot>/weld-translator</contextRoot>\n"
+" </webModule>\n"
+" </modules>\n"
+" </configuration>\n"
+"</plugin>"
msgstr ""
#. Tag: para
@@ -891,72 +891,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
+msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<application version="5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<application version=\"5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/application_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/application_5.xsd\">\n"
"\n"
-" <display-name>weld-jsf-translator-ear</display-name>\n"
-" <description>The Weld JSF translator example (ear)</description>\n"
+" <display-name>weld-jsf-translator-ear</display-name>\n"
+" <description>The Weld JSF translator example (ear)</description>\n"
" \n"
-" <module>\n"
-" <web>\n"
-" <web-uri>weld-translator.war</web-uri>\n"
-" <context-root>/weld-translator</context-root>\n"
-" </web>\n"
-" </module>\n"
-" <module>\n"
-" <ejb>weld-translator.jar</ejb>\n"
-" </module>\n"
-"</application>"
+" <module>\n"
+" <web>\n"
+" <web-uri>weld-translator.war</web-uri>\n"
+" <context-root>/weld-translator</context-root>\n"
+" </web>\n"
+" </module>\n"
+" <module>\n"
+" <ejb>weld-translator.jar</ejb>\n"
+" </module>\n"
+"</application>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
+msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (ommitted here for brevity):"
+msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (omitted here for brevity):"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:form id="translator">\n"
+"<h:form id=\"translator\">\n"
"\n"
-" <table>\n"
-" <tr align="center" style="font-weight: bold">\n"
-" <td>\n"
+" <table>\n"
+" <tr align=\"center\" style=\"font-weight: bold\">\n"
+" <td>\n"
" Your text\n"
-" </td>\n"
-" <td>\n"
+" </td>\n"
+" <td>\n"
" Translation\n"
-" </td>\n"
-" </tr>\n"
-" <tr>\n"
-" <td>\n"
-" <h:inputTextarea id="text" value="#{translator.text}" required="true" rows="5" cols="80"/>\n"
-" </td>\n"
-" <td>\n"
-" <h:outputText value="#{translator.translatedText}"/>\n"
-" </td>\n"
-" </tr>\n"
-" </table>\n"
-" <div>\n"
-" <h:commandButton id="button" value="Translate" action="#{translator.translate}"/>\n"
-" </div>\n"
+" </td>\n"
+" </tr>\n"
+" <tr>\n"
+" <td>\n"
+" <h:inputTextarea id=\"text\" value=\"#{translator.text}\" required=\"true\" rows=\"5\" cols=\"80\"/>\n"
+" </td>\n"
+" <td>\n"
+" <h:outputText value=\"#{translator.translatedText}\"/>\n"
+" </td>\n"
+" </tr>\n"
+" </table>\n"
+" <div>\n"
+" <h:commandButton id=\"button\" value=\"Translate\" action=\"#{translator.translate}\"/>\n"
+" </div>\n"
" \n"
-"</h:form>"
+"</h:form>"
msgstr ""
#. Tag: para
@@ -966,12 +966,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
+msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
+msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
msgstr ""
#. Tag: para
@@ -995,7 +995,7 @@ msgid ""
" public String translate(String text) { \n"
" StringBuilder sb = new StringBuilder(); \n"
" for (String sentence: sentenceParser.parse(text)) { \n"
-" sb.append(translator.translate(sentence)).append(". "); \n"
+" sb.append(translator.translate(sentence)).append(\". \"); \n"
" } \n"
" return sb.toString().trim(); \n"
" }\n"
@@ -1005,7 +1005,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
+msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
msgstr ""
#. Tag: programlisting
@@ -1015,7 +1015,7 @@ msgid ""
"public class SentenceTranslator implements Translator { \n"
"\n"
" public String translate(String sentence) { \n"
-" return "Lorem ipsum dolor sit amet"; \n"
+" return \"Lorem ipsum dolor sit amet\"; \n"
" }\n"
"\n"
"}"
@@ -1031,7 +1031,7 @@ msgstr ""
msgid ""
"@Stateful\n"
"@RequestScoped\n"
-"@Named("translator")\n"
+"@Named(\"translator\")\n"
"public class TranslatorControllerBean implements TranslatorController {\n"
"\n"
" @Inject private TextTranslator translator;\n"
diff --git a/docs/reference/src/main/docbook/fr-FR/Weld_-_JSR-299_Reference_Implementation.po b/docs/reference/src/main/docbook/fr-FR/Weld_-_JSR-299_Reference_Implementation.po
new file mode 100644
index 00000000000..f4baccac014
--- /dev/null
+++ b/docs/reference/src/main/docbook/fr-FR/Weld_-_JSR-299_Reference_Implementation.po
@@ -0,0 +1,59 @@
+#
+# AUTHOR , YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "A note about naming and nomenclature"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Shortly before the final draft of JSR-299 was submitted, the specification changed its name from \"Web Beans\" to \"Java Contexts and Dependency Injection for the Java EE platform\", abbreviated CDI. For a brief period after the renaming, the reference implementation adopted the name \"Web Beans\". However, this ended up causing more confusion than it solved and Red Hat decided to change the name of the reference implementation to \"Weld\". You may still find other documentation, blogs, forum posts, etc. that use the old nomenclature. Please update any references you can. The naming game is over."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You'll also find that some of the functionality that once existed in the specification is now missing, such as defining beans in XML. These features will be available as portable extensions for CDI in the Weld project, and perhaps other implementations."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this reference guide was started while changes were still being made to the specification. We've done our best to update it for accuracy. If you discover a conflict between what is written in this guide and the specification, the specification is the authority—assume it is correct. If you believe you have found an error in the specification, please report it to the JSR-299 EG."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Beans"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Start with Weld, the CDI Reference Implementation"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Loose coupling with strong typing"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "CDI and the Java EE ecosystem"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Weld Reference Guide"
+msgstr ""
+
diff --git a/docs/reference/src/main/docbook/fr-FR/beans.po b/docs/reference/src/main/docbook/fr-FR/beans.po
index af527b69df8..daff26f3fd3 100644
--- a/docs/reference/src/main/docbook/fr-FR/beans.po
+++ b/docs/reference/src/main/docbook/fr-FR/beans.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
+msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
msgstr ""
#. Tag: para
@@ -56,7 +56,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
+msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
msgstr ""
#. Tag: para
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
+msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
msgstr ""
#. Tag: title
@@ -131,7 +131,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's see what all this new terminology means."
+msgid "Let's see what all this new terminology means."
msgstr ""
#. Tag: title
@@ -141,7 +141,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a "contract" that must be satisfied by the bean to be injected. The contract is:"
+msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a \"contract\" that must be satisfied by the bean to be injected. The contract is:"
msgstr ""
#. Tag: para
@@ -164,14 +164,14 @@ msgstr ""
msgid ""
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
+msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
msgstr ""
#. Tag: para
@@ -192,12 +192,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
+msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
+msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
msgstr ""
#. Tag: programlisting
@@ -206,19 +206,19 @@ msgid ""
"@Typed(Shop.class)\n"
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of "quality" using a qualifier."
+msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of \"quality\" using a qualifier."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
+msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
msgstr ""
#. Tag: programlisting
@@ -232,12 +232,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
+msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
+msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
msgstr ""
#. Tag: para
@@ -252,12 +252,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
+msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
msgstr ""
#. Tag: para
@@ -275,12 +270,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If a bean does not explicitly specify a qualifier, it has the default qualifier, @Default."
+msgid "If a bean or an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
+msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
msgstr ""
#. Tag: title
@@ -312,7 +307,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
+msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
msgstr ""
#. Tag: para
@@ -322,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk more about scopes in ."
+msgid "We'll talk more about scopes in ."
msgstr ""
#. Tag: title
@@ -343,7 +338,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"public @SessionScoped @Named("cart")\n"
+"public @SessionScoped @Named(\"cart\")\n"
"class ShoppingCart implements Serializable { ... }"
msgstr ""
@@ -355,9 +350,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:dataTable value="#{cart.lineItems}" var="item">\n"
+"<h:dataTable value=\"#{cart.lineItems}\" var=\"item\">\n"
" ...\n"
-"</h:dataTable>"
+"</h:dataTable>"
msgstr ""
#. Tag: para
@@ -389,7 +384,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
+msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
msgstr ""
#. Tag: programlisting
@@ -416,12 +411,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
+msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
+msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
msgstr ""
#. Tag: para
@@ -470,17 +465,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
+msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
+msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
+msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
msgstr ""
#. Tag: title
@@ -490,7 +485,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
+msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
msgstr ""
#. Tag: title
@@ -500,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
+msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
msgstr ""
#. Tag: para
@@ -525,7 +520,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It has an appropriate constructor—either:"
+msgid "It has an appropriate constructor—either:"
msgstr ""
#. Tag: para
@@ -540,7 +535,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
+msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
msgstr ""
#. Tag: para
@@ -585,12 +580,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
+msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
+msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
msgstr ""
#. Tag: para
@@ -625,7 +620,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
+msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
msgstr ""
#. Tag: para
@@ -640,17 +635,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
+msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
+msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're "heavyweight". It's nothing more than superstition to think that something is "heavier" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like "heavyweight"."
+msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're \"heavyweight\". It's nothing more than superstition to think that something is \"heavier\" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like \"heavyweight\"."
msgstr ""
#. Tag: title
@@ -690,7 +685,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
+msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
msgstr ""
#. Tag: programlisting
@@ -705,7 +700,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<p>Your raffle number is #{randomNumber}.</p>"
+msgid "<p>Your raffle number is #{randomNumber}.</p>"
msgstr ""
#. Tag: para
@@ -746,14 +741,14 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces Set<Roles> getRoles(User user) {\n"
+"@Produces Set<Roles> getRoles(User user) {\n"
" return user.getRoles();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk much more about producer methods in ."
+msgid "We'll talk much more about producer methods in ."
msgstr ""
#. Tag: title
@@ -763,7 +758,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
+msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
msgstr ""
#. Tag: programlisting
@@ -771,7 +766,7 @@ msgstr ""
msgid ""
"public class Shop {\n"
" @Produces PaymentProcessor paymentProcessor = ....;\n"
-" @Produces @Catalog List<Product> products = ....;\n"
+" @Produces @Catalog List<Product> products = ....;\n"
"}"
msgstr ""
@@ -782,5 +777,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
+msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
msgstr ""
diff --git a/docs/reference/src/main/docbook/fr-FR/configure.po b/docs/reference/src/main/docbook/fr-FR/configure.po
index eeba87f0a16..01ef2ccd8ab 100644
--- a/docs/reference/src/main/docbook/fr-FR/configure.po
+++ b/docs/reference/src/main/docbook/fr-FR/configure.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -30,50 +30,50 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
+msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<?xml version="1.0" encoding="UTF-8"?>\n"
-"<beans xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \n"
-" xmlns:weld="http://jboss.org/schema/weld/beans" \n"
-" xsi:schemaLocation="\n"
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<beans xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" \n"
+" xmlns:weld=\"http://jboss.org/schema/weld/beans\" \n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee http://docs.jboss.org/cdi/beans_1_0.xsd\n"
-" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">\n"
+" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd\">\n"
" \n"
-" <weld:scan>\n"
+" <weld:scan>\n"
" \n"
-" <!-- Don't deploy the classes for the swing app! -->\n"
-" <weld:exclude name="com.acme.swing.**" />\n"
+" <!-- Don't deploy the classes for the swing app! -->\n"
+" <weld:exclude name=\"com.acme.swing.**\" />\n"
" \n"
-" <!-- Don't include GWT support if GWT is not installed -->\n"
-" <weld:exclude name="com.acme.gwt.**">\n"
-" <weld:if-class-available name="!com.google.GWT"/>\n"
-" </weld:exclude>\n"
+" <!-- Don't include GWT support if GWT is not installed -->\n"
+" <weld:exclude name=\"com.acme.gwt.**\">\n"
+" <weld:if-class-available name=\"!com.google.GWT\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
+" <!--\n"
" Exclude classes which end in Blether if the system property verbosity is set to low\n"
" i.e.\n"
" java ... -Dverbosity=low \n"
-" --> \n"
-" <weld:exclude pattern="^(.*)Blether$">\n"
-" <weld:if-system-property name="verbosity" value="low"/>\n"
-" </weld:exclude>\n"
+" --> \n"
+" <weld:exclude pattern=\"^(.*)Blether$\">\n"
+" <weld:if-system-property name=\"verbosity\" value=\"low\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
-" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
+" <!--\n"
+" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
" property is not set\n"
-" -->\n"
-" <weld:exclude name="com.acme.jsf.**">\n"
-" <weld:if-class-available name="org.apahce.wicket.Wicket"/>\n"
-" <weld:if-system-property name="!viewlayer"/>\n"
-" </weld:exclude>\n"
-" </weld:scan>\n"
+" -->\n"
+" <weld:exclude name=\"com.acme.jsf.**\">\n"
+" <weld:if-class-available name=\"org.apahce.wicket.Wicket\"/>\n"
+" <weld:if-system-property name=\"!viewlayer\"/>\n"
+" </weld:exclude>\n"
+" </weld:scan>\n"
" \n"
-"</beans>"
+"</beans>"
msgstr ""
#. Tag: para
@@ -83,7 +83,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
+msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
msgstr ""
#. Tag: para
@@ -93,12 +93,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
+msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
+msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
msgstr ""
#. Tag: para
@@ -113,5 +113,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
+msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
msgstr ""
diff --git a/docs/reference/src/main/docbook/fr-FR/contexts.po b/docs/reference/src/main/docbook/fr-FR/contexts.po
index 998addb61d4..6503057daf1 100644
--- a/docs/reference/src/main/docbook/fr-FR/contexts.po
+++ b/docs/reference/src/main/docbook/fr-FR/contexts.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,17 +25,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld allows you to easiy manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivaed (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
+msgid "Weld allows you to easily manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivated (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and discociating the data store after calling activate."
+msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and dissociating the data store after calling activate."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld automatically controls context lifecycle in many scenarios such as Http Requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
+msgid "Weld automatically controls context lifecycle in many scenarios such as HTTP requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
msgstr ""
#. Tag: para
@@ -145,7 +145,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
+msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
msgstr ""
#. Tag: entry
@@ -245,12 +245,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implmentations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
+msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implementations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
+msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
msgstr ""
#. Tag: programlisting
@@ -263,14 +263,14 @@ msgid ""
" ...\n"
" \n"
" /* Start the request, providing a data store which will last the lifetime of the request */\n"
-" public void startRequest(Map<String, Object> requestDataStore) {\n"
+" public void startRequest(Map<String, Object> requestDataStore) {\n"
" // Associate the store with the context and acticate the context\n"
" requestContext.associate(requestDataStore);\n"
" requestContext.activate();\n"
" }\n"
" \n"
" /* End the request, providing the same data store as was used to start the request */\n"
-" public void endRequest(Map<String, Object> requestDataStore) {\n"
+" public void endRequest(Map<String, Object> requestDataStore) {\n"
" try {\n"
" /* Invalidate the request (all bean instances will be scheduled for destruction) */\n"
" requestContext.invalidate();\n"
@@ -290,7 +290,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's session contexts are "lazy" and don't require a session to actually exist until a bean instance must be written."
+msgid "Weld's session contexts are \"lazy\" and don't require a session to actually exist until a bean instance must be written."
msgstr ""
#. Tag: para
@@ -308,16 +308,16 @@ msgid ""
" /* Start a transient conversation */\n"
" /* Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */\n"
-" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" resumeOrStartConversation(requestDataStore, sessionDataStore, null);\n"
" }\n"
"\n"
" /* Start a transient conversation (if cid is null) or resume a non-transient */\n"
" /* conversation. Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */ \n"
-" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore, \n"
+" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore, \n"
" String cid) {\n"
" /* Associate the stores with the context and acticate the context */\n"
" * BoundRequest just wraps the two datastores */\n"
@@ -329,8 +329,8 @@ msgid ""
" /* End the conversations, providing the same data store as was used to start */\n"
" /* the request. Any transient conversations will be destroyed, any newly-promoted */\n"
" /* conversations will be placed into the session */\n"
-" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" try {\n"
" /* Invalidate the conversation (all transient conversations will be scheduled for destruction) */\n"
" conversationContext.invalidate();\n"
@@ -345,15 +345,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the containber), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
+msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the container), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the abilty to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
+msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the ability to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's conversations are not assigned ids until they become non-transient."
+msgid "Weld's conversations are not assigned ids until they become non-transient."
msgstr ""
diff --git a/docs/reference/src/main/docbook/fr-FR/decorators.po b/docs/reference/src/main/docbook/fr-FR/decorators.po
index d9bf7a0440d..f58be5b0b09 100644
--- a/docs/reference/src/main/docbook/fr-FR/decorators.po
+++ b/docs/reference/src/main/docbook/fr-FR/decorators.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-02 22:25+0100\n"
"Last-Translator: Vincent Latombe \n"
"Language-Team: none\n"
@@ -21,12 +21,12 @@ msgstr "Décorateurs"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
+msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
msgstr "Les intercepteurs sont une manière puissante de capter et de séparer les problèmes qui sont orthogonaux au type de système. Tout intercepteur est capable d'intercepter les invocations à tout type Java. Cela les rend parfait pour résoudre des problèmes techniques tels que la gestion transactionnelle et la sécurité.Cependant, par nature, les intercepteurs ne sont pas conscients de la sémantique réelle des évênements qu'ils interceptent. En conséquence, les intercepteurs ne sont pas un outil approprié pour séparer problèmes métiers."
#. Tag: para
#, fuzzy, no-c-format
-msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
+msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
msgstr "L'inverse est vrai pour les décorateurs. Un décorateur intercepte les invocations uniquement pour une certain interface Java, et est donc conscient de toute la sémantique rattachée à cette interface. Cela fait des décorateurs un outil parfait pour modéliser certains concepts métiers. Cela veut aussi dire qu'un décorateur n'est pas aussi générique qu'un intercepteur. Les décorateurs ne sont pas capables de résoudres des problèmes techniques qui peuvent toucher des types très disparates."
#. Tag: para
@@ -124,7 +124,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
+msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
msgstr "Contrairement à d'autres Web Beans simples, un décorateur peut être une classe abstraite. Si le décorateur n'a rien de spécial à faire pour une méthode particulière d'une interface décorée, vous n'avez pas besoin d'implémenter cette méthode."
#. Tag: para
@@ -208,14 +208,14 @@ msgid ""
" \n"
" public void withdraw(BigDecimal amount) {\n"
" account.withdraw(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedWithdrawl(amount) );\n"
" }\n"
" }\n"
" \n"
" public void deposit(BigDecimal amount);\n"
" account.deposit(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedDeposit(amount) );\n"
" }\n"
" }\n"
@@ -258,21 +258,21 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <decorators>\n"
-" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
-" </decorators>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <decorators>\n"
+" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
+" </decorators>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
+msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
msgstr "Cette déclaration a le même but pour les décorateurs que la déclaration <Interceptors> pour les intercepteurs:"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/fr-FR/ee.po b/docs/reference/src/main/docbook/fr-FR/ee.po
index 54a42701989..b5d95a43cbc 100644
--- a/docs/reference/src/main/docbook/fr-FR/ee.po
+++ b/docs/reference/src/main/docbook/fr-FR/ee.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-02 22:49+0100\n"
"Last-Translator: Vincent Latombe \n"
"Language-Team: none\n"
@@ -56,7 +56,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
+msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
msgstr ""
#. Tag: para
@@ -81,7 +81,7 @@ msgstr "Injecter des ressources Java EE dans un Web Bean"
#. Tag: para
#, fuzzy, no-c-format
-msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
+msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
msgstr "Tous les Web Beans, qu'ils soient simples ou d'entreprise peuvent bénéficier de l'injection de dépendance de Java EE en utilisant @Resource; @EJB et @PersistenceContext. Nous avons déjà vu quelques exemples de cela, bien que nous n'y ayons pas fait attention sur le moment:"
#. Tag: programlisting
@@ -140,7 +140,7 @@ msgstr "Appeler un Web Bean à partir d'un Servlet"
#. Tag: para
#, fuzzy, no-c-format
-msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
+msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
msgstr "Il est facile d'utiliser un Web Bean à partir d'une Servlet dans Java EE 6. Injectez simplement le Web Bean en utilisant les méthodes d'injection de champs ou de méthode d'initialisation."
#. Tag: programlisting
@@ -153,14 +153,14 @@ msgid ""
" @Override\n"
" public void service(HttpServletRequest request, HttpServletResponse response)\n"
" throws ServletException, IOException {\n"
-" credentials.setUsername(request.getParameter("username")):\n"
-" credentials.setPassword(request.getParameter("password")):\n"
+" credentials.setUsername(request.getParameter(\"username\")):\n"
+" credentials.setPassword(request.getParameter(\"password\")):\n"
" login.login();\n"
" if ( login.isLoggedIn() ) {\n"
-" response.sendRedirect("/home.jsp");\n"
+" response.sendRedirect(\"/home.jsp\");\n"
" }\n"
" else {\n"
-" response.sendRedirect("/loginError.jsp");\n"
+" response.sendRedirect(\"/loginError.jsp\");\n"
" }\n"
" }\n"
" \n"
@@ -199,7 +199,7 @@ msgstr "Appeler un Web Bean à partir d'un Message-Driven Bean"
#. Tag: para
#, no-c-format
-msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
+msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
msgstr ""
#. Tag: para
@@ -261,10 +261,10 @@ msgstr ""
#, no-c-format
msgid ""
"public class OrderResources {\n"
-" @Resource(name="jms/ConnectionFactory")\n"
+" @Resource(name=\"jms/ConnectionFactory\")\n"
" private ConnectionFactory connectionFactory;\n"
" \n"
-" @Resource(name="jms/OrderQueue")\n"
+" @Resource(name=\"jms/OrderQueue\")\n"
" private Queue orderQueue;\n"
" \n"
" @Produces @OrderConnection\n"
@@ -315,7 +315,7 @@ msgid ""
"\n"
"public void sendMessage() {\n"
" MapMessage msg = orderSession.createMapMessage();\n"
-" msg.setLong("orderId", order.getId());\n"
+" msg.setLong(\"orderId\", order.getId());\n"
" ...\n"
" producer.send(msg);\n"
"}"
@@ -341,7 +341,7 @@ msgstr "Paquetage et déploiement"
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a "bean archive". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
+msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a \"bean archive\". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
msgstr "Les Web Beans ne définissent aucune archive spéciale pour le déploiement. Vous pouvez paqueter des Web Beans dans des JARs, des EJB-JARs ou des WARs : tout emplacement de déploiement dans le classpath de l'application. Cependant, chaque archive contenant des Web Beans doit contenir un fichier nommé web-beans.xml dans le dossier META-INF ou WEB-INF. Le fichier peut être vide. Les Web Beans déployés dans des archives n'ayant pas de fichier web-beans.xml ne seront pas disponibles pour utilisation dans l'application."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/fr-FR/environments.po b/docs/reference/src/main/docbook/fr-FR/environments.po
index 10b5a1bcb3f..27d64ccf650 100644
--- a/docs/reference/src/main/docbook/fr-FR/environments.po
+++ b/docs/reference/src/main/docbook/fr-FR/environments.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-28 17:09+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -56,12 +56,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
+msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an "uber-jar", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
+msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an \"uber-jar\", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
msgstr ""
#. Tag: para
@@ -72,9 +72,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
#. Tag: title
@@ -84,18 +84,18 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
+msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<Context>\n"
-" <Resource name="BeanManager" \n"
-" auth="Container"\n"
-" type="javax.enterprise.inject.spi.BeanManager"\n"
-" factory="org.jboss.weld.resources.ManagerObjectFactory"/>\n"
-"</Context>"
+"<Context>\n"
+" <Resource name=\"BeanManager\" \n"
+" auth=\"Container\"\n"
+" type=\"javax.enterprise.inject.spi.BeanManager\"\n"
+" factory=\"org.jboss.weld.resources.ManagerObjectFactory\"/>\n"
+"</Context>"
msgstr ""
#. Tag: para
@@ -106,12 +106,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<resource-env-ref>\n"
-" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
-" <resource-env-ref-type>\n"
+"<resource-env-ref>\n"
+" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
+" <resource-env-ref-type>\n"
" javax.enterprise.inject.spi.BeanManager\n"
-" </resource-env-ref-type>\n"
-"</resource-env-ref>"
+" </resource-env-ref-type>\n"
+"</resource-env-ref>"
msgstr ""
#. Tag: para
@@ -131,27 +131,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
+msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.mortbay.jetty.plus.naming.Resource">\n"
-" <Arg><Ref id="webAppCtx"/></Arg> \n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.mortbay.jetty.plus.naming.Resource\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg> \n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure>"
msgstr ""
#. Tag: para
@@ -162,22 +162,22 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://www.eclipse.org/jetty/configure.dtd">\n"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://www.eclipse.org/jetty/configure.dtd\">\n"
"\n"
-"<Configure id="webAppCtx" class="org.eclipse.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.eclipse.jetty.plus.jndi.Resource">\n"
-" <Arg> <Ref id="webAppCtx"/> </Arg>\n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure> "
+"<Configure id=\"webAppCtx\" class=\"org.eclipse.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.eclipse.jetty.plus.jndi.Resource\">\n"
+" <Arg> <Ref id=\"webAppCtx\"/> </Arg>\n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure> "
msgstr ""
#. Tag: para
@@ -187,7 +187,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
+msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
msgstr ""
#. Tag: para
@@ -197,19 +197,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file META-INF/jetty-web.xml with the following content to your war:"
+msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file WEB-INF/jetty-web.xml with the following content to your war:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <Call class="org.jboss.weld.environment.jetty.WeldServletHandler" name="process">\n"
-" <Arg><Ref id="webAppCtx"/></Arg>\n"
-" </Call>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <Call class=\"org.jboss.weld.environment.jetty.WeldServletHandler\" name=\"process\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg>\n"
+" </Call>\n"
+"</Configure>"
msgstr ""
#. Tag: title
@@ -219,7 +219,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In addition to improved integration of the Enterprise Java stack, the "Contexts and Dependency Injection for the Java EE platform" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
+msgid "In addition to improved integration of the Enterprise Java stack, the \"Contexts and Dependency Injection for the Java EE platform\" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
msgstr ""
#. Tag: para
@@ -279,7 +279,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Parameters List<String> params;"
+msgid "@Inject @Parameters List<String> params;"
msgstr ""
#. Tag: programlisting
@@ -299,7 +299,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example of a simple CDI SE application:"
+msgid "Here's an example of a simple CDI SE application:"
msgstr ""
#. Tag: programlisting
@@ -308,8 +308,8 @@ msgid ""
"@Singleton\n"
"public class HelloWorld\n"
"{\n"
-" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
-" System.out.println("Hello " + parameters.get(0));\n"
+" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
+" System.out.println(\"Hello \" + parameters.get(0));\n"
" }\n"
"}"
msgstr ""
@@ -331,7 +331,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
+msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
msgstr ""
#. Tag: para
@@ -341,17 +341,17 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "java org.jboss.weld.environment.se.StartMain <args>"
+msgid "java org.jboss.weld.environment.se.StartMain <args>"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Programatic Bootstrap API"
+msgid "Programmatic Bootstrap API"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
+msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
msgstr ""
#. Tag: programlisting
@@ -377,10 +377,10 @@ msgid ""
"{\n"
"\n"
" /** Provides access to all beans within the application. */\n"
-" public Instance<Object> instance() {...}\n"
+" public Instance<Object> instance() {...}\n"
"\n"
" /** Provides access to all events within the application. */\n"
-" public Event<Object> event() {...}\n"
+" public Event<Object> event() {...}\n"
"\n"
" /** Provides direct access to the BeanManager. */\n"
" public BeanManager getBeanManager() {...}\n"
@@ -390,7 +390,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
+msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
msgstr ""
#. Tag: programlisting
@@ -430,22 +430,22 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
+msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans>\n"
-" <decorators>\n"
-" <decorator>org.jboss.weld.environment.se.threading.RunnableDecorator</decorator>\n"
-" </decorator>\n"
-"</beans>"
+"<beans>\n"
+" <decorators>\n"
+" <class>org.jboss.weld.environment.se.threading.RunnableDecorator</class>\n"
+" </decorator>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situtations where you would otherwise have used ThreadLocal directly, which are typically rare."
+msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situations where you would otherwise have used ThreadLocal directly, which are typically rare."
msgstr ""
#. Tag: title
@@ -455,7 +455,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
+msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/fr-FR/events.po b/docs/reference/src/main/docbook/fr-FR/events.po
index dd79c8bcdd8..a85c6fe6948 100644
--- a/docs/reference/src/main/docbook/fr-FR/events.po
+++ b/docs/reference/src/main/docbook/fr-FR/events.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-02 23:28+0100\n"
"Last-Translator: Vincent Latombe \n"
"Language-Team: none\n"
@@ -36,7 +36,7 @@ msgstr "non seulement les producteurs d'évènements sont découplés des observ
#. Tag: para
#, fuzzy, no-c-format
-msgid "observers can specify a combination of "selectors" to narrow the set of event notifications they will receive, and"
+msgid "observers can specify a combination of \"selectors\" to narrow the set of event notifications they will receive, and"
msgstr "les observateurs peuvent spécifier une combinaison de \"sélécteurs\" pour limiter le nobmre de notifications d'évènemtns qu'ils vont recevoir, et"
#. Tag: para
@@ -46,7 +46,7 @@ msgstr "les observateurs peuvent être notifiés immédiatement, ou peuvent spé
#. Tag: para
#, no-c-format
-msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
+msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
msgstr ""
#. Tag: title
@@ -61,7 +61,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
+msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
msgstr ""
#. Tag: programlisting
@@ -104,7 +104,7 @@ msgstr "only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
+msgid "An observer method need not specify any event qualifiers—in this case it is interested in only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
msgstr "Il n'est pas obligatoire de spécifier une quelconque liaison d'évènement sur une méthode observatrice : dans ce cas elle s'intéresse à tous les évènements d'un type particulier. Si elle spécifie des liaisons d'évènements, elle s'intéresse uniquement aux évènements qui ont ces liaisons d'évènements."
#. Tag: para
@@ -129,7 +129,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Event<Document> documentEvent;"
+msgid "@Inject @Any Event<Document> documentEvent;"
msgstr " documentEvent]]>"
#. Tag: para
@@ -184,7 +184,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
+msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
msgstr " documentUpdatedEvent]]>"
#. Tag: para
@@ -204,12 +204,12 @@ msgstr "ne spécifie aucune liaision d'évènement excepté
#. Tag: para
#, no-c-format
-msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
+msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
+msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
msgstr "(){} );]]>"
#. Tag: para
@@ -224,7 +224,7 @@ msgstr "Observateurs transactionnels"
#. Tag: para
#, no-c-format
-msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
+msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
msgstr ""
#. Tag: para
@@ -286,7 +286,7 @@ msgstr "Les membres de type de liaison d'évènement peuvent être spécifiés s
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
+msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
msgstr " LoggedInEvent;}}]]>"
#. Tag: para
@@ -298,7 +298,7 @@ msgstr "Alternativement, la valeur du membre du type de liaision d'évènement p
#, fuzzy, no-c-format
msgid ""
"abstract class RoleBinding \n"
-" extends AnnotationLiteral<Role> \n"
+" extends AnnotationLiteral<Role> \n"
" implements Role {}"
msgstr ""
" blogEvent;\n"
"...\n"
@@ -442,12 +442,12 @@ msgid ""
"\n"
" @PersistenceContext EntityManager em;\n"
" \n"
-" List<Product> products;\n"
+" List<Product> products;\n"
"\n"
" @Produces @Catalog \n"
-" List<Product> getCatalog() {\n"
+" List<Product> getCatalog() {\n"
" if (products==null) {\n"
-" products = em.createQuery("select p from Product p where p.deleted = false")\n"
+" products = em.createQuery(\"select p from Product p where p.deleted = false\")\n"
" .getResultList();\n"
" }\n"
" return products;\n"
@@ -489,16 +489,16 @@ msgid ""
"@Stateless\n"
"public class ProductManager {\n"
" @PersistenceContext EntityManager em;\n"
-" @Inject @Any Event<Product> productEvent;\n"
+" @Inject @Any Event<Product> productEvent;\n"
"\n"
" public void delete(Product product) {\n"
" em.delete(product);\n"
-" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
" }\n"
" \n"
" public void persist(Product product) {\n"
" em.persist(product);\n"
-" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
" }\n"
" ...\n"
"}"
diff --git a/docs/reference/src/main/docbook/fr-FR/example.po b/docs/reference/src/main/docbook/fr-FR/example.po
index 377eba1a116..0aa63f78983 100644
--- a/docs/reference/src/main/docbook/fr-FR/example.po
+++ b/docs/reference/src/main/docbook/fr-FR/example.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-04 23:07+0100\n"
"Last-Translator: Vincent Latombe \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "Exemple d'une web application JSF"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
+msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
msgstr "Illustrons ces idées avec un exemple complet. Nous allons implémenter la connexion/déconnexion d'un utilisateur à une application utilisant JSF. D'abord, nous allons définir un Web Bean pour stocker le nom d'utilisateur et le mot de passe saisis lors de l'identification:"
#. Tag: programlisting
@@ -63,18 +63,18 @@ msgstr "Ce Web Bean est lié à l'invite de connexion dans le formulaire JSF sui
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:form>\n"
-" <h:panelGrid columns="2" rendered="#{!login.loggedIn}">\n"
-" <f:validateBean>\n"
-" <h:outputLabel for="username">Username:</h:outputLabel>\n"
-" <h:inputText id="username" value="#{credentials.username}"/>\n"
-" <h:outputLabel for="password">Password:</h:outputLabel>\n"
-" <h:inputSecret id="password" value="#{credentials.password}"/>\n"
-" </f:validateBean>\n"
-" </h:panelGrid>\n"
-" <h:commandButton value="Login" action="#{login.login}" rendered="#{!login.loggedIn}"/>\n"
-" <h:commandButton value="Logout" action="#{login.logout}" rendered="#{login.loggedIn}"/>\n"
-"</h:form>"
+"<h:form>\n"
+" <h:panelGrid columns=\"2\" rendered=\"#{!login.loggedIn}\">\n"
+" <f:validateBean>\n"
+" <h:outputLabel for=\"username\">Username:</h:outputLabel>\n"
+" <h:inputText id=\"username\" value=\"#{credentials.username}\"/>\n"
+" <h:outputLabel for=\"password\">Password:</h:outputLabel>\n"
+" <h:inputSecret id=\"password\" value=\"#{credentials.password}\"/>\n"
+" </f:validateBean>\n"
+" </h:panelGrid>\n"
+" <h:commandButton value=\"Login\" action=\"#{login.login}\" rendered=\"#{!login.loggedIn}\"/>\n"
+" <h:commandButton value=\"Logout\" action=\"#{login.logout}\" rendered=\"#{login.loggedIn}\"/>\n"
+"</h:form>"
msgstr ""
"\n"
" \n"
@@ -121,7 +121,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
+msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
msgstr ""
#. Tag: para
@@ -141,10 +141,10 @@ msgid ""
" private User user;\n"
" \n"
" public void login() {\n"
-" List<User> results = userDatabase.createQuery(\n"
-" "select u from User u where u.username = :username and u.password = :password")\n"
-" .setParameter("username", credentials.getUsername())\n"
-" .setParameter("password", credentials.getPassword())\n"
+" List<User> results = userDatabase.createQuery(\n"
+" \"select u from User u where u.username = :username and u.password = :password\")\n"
+" .setParameter(\"username\", credentials.getUsername())\n"
+" .setParameter(\"password\", credentials.getPassword())\n"
" .getResultList();\n"
" \n"
" if (!results.isEmpty()) {\n"
@@ -290,14 +290,14 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:panelGroup rendered="#{login.loggedIn}">\n"
+"<h:panelGroup rendered=\"#{login.loggedIn}\">\n"
" signed in as #{currentUser.username}\n"
-"</h:panelGroup>"
+"</h:panelGroup>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
+msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
msgstr "Cet exemple vous donne une idée du modèle de programmation Web Bean. Dans le prochain chapitre, nous explorerons l'injection de dépendance des Web Beans plus en détail."
#~ msgid "Of course, @LoggedIn is a binding annotation:"
diff --git a/docs/reference/src/main/docbook/fr-FR/extend.po b/docs/reference/src/main/docbook/fr-FR/extend.po
index c5f5289512f..eec864b74dc 100644
--- a/docs/reference/src/main/docbook/fr-FR/extend.po
+++ b/docs/reference/src/main/docbook/fr-FR/extend.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-04 23:17+0100\n"
"Last-Translator: Vincent Latombe \n"
"Language-Team: none\n"
@@ -76,7 +76,7 @@ msgstr "La classe Bean"
#. Tag: para
#, no-c-format
-msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
+msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
msgstr ""
#. Tag: programlisting
@@ -164,15 +164,15 @@ msgid ""
"class MyExtension implements Extension {\n"
" \n"
" void beforeBeanDiscovery(@Observes BeforeBeanDiscovery bbd) {\n"
-" Logger.global.debug("beginning the scanning process");\n"
+" Logger.global.debug(\"beginning the scanning process\");\n"
" }\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
-" Logger.global.debug("scanning type: " + pat.getAnnotatedType().getJavaClass().getName());\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" Logger.global.debug(\"scanning type: \" + pat.getAnnotatedType().getJavaClass().getName());\n"
" } \n"
"\n"
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd) {\n"
-" Logger.global.debug("finished the scanning process");\n"
+" Logger.global.debug(\"finished the scanning process\");\n"
" }\n"
" \n"
"}"
@@ -180,7 +180,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
+msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
msgstr ""
#. Tag: programlisting
@@ -188,7 +188,7 @@ msgstr ""
msgid ""
"class MyExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" //tell the container to ignore the type if it is annotated @Ignore\n"
" if ( pat.getAnnotatedType().isAnnotionPresent(Ignore.class) ) pat.veto(); \n"
" } \n"
@@ -203,7 +203,7 @@ msgstr "Le centre nerveux pour l'extension des Web Beans est l'objet Ma
#. Tag: programlisting
#, no-c-format
-msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
+msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
msgstr ""
#. Tag: title
@@ -220,31 +220,31 @@ msgstr "L'interface Manager nous permet d'enregistrer et d'ob
#, no-c-format
msgid ""
"public interface BeanManager {\n"
-" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
-" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
-" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
-" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
-" public Set<Bean<?>> getBeans(String name);\n"
-" public Bean<?> getPassivationCapableBean(String id);\n"
-" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
+" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
+" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
+" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
+" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
+" public Set<Bean<?>> getBeans(String name);\n"
+" public Bean<?> getPassivationCapableBean(String id);\n"
+" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
" public void validate(InjectionPoint injectionPoint);\n"
" public void fireEvent(Object event, Annotation... qualifiers);\n"
-" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
-" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
-" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
-" public boolean isScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
-" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
-" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
-" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
-" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
-" public Context getContext(Class<? extends Annotation> scopeType);\n"
+" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
+" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
+" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
+" public boolean isScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
+" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
+" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
+" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
+" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
+" public Context getContext(Class<? extends Annotation> scopeType);\n"
" public ELResolver getELResolver();\n"
" public ExpressionFactory wrapExpressionFactory(ExpressionFactory expressionFactory);\n"
-" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
-" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
+" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
+" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
"}"
msgstr ""
@@ -265,7 +265,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's study some of the interfaces exposed by the BeanManager."
+msgid "Let's study some of the interfaces exposed by the BeanManager."
msgstr "Le centre nerveux pour l'extension des Web Beans est l'objet Manager."
#. Tag: title
@@ -280,21 +280,21 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to instatiate the object itself, and so only method and field injection will be supported."
+msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to insntatiate the object itself, and so only method and field injection will be supported."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"//get the BeanManager from JNDI\n"
-"BeanManager beanManager = (BeanManager) new InitialContext().lookup("java:comp/BeanManager");\n"
+"BeanManager beanManager = (BeanManager) new InitialContext().lookup(\"java:comp/BeanManager\");\n"
"\n"
"//CDI uses an AnnotatedType object to read the annotations of a class\n"
-"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
+"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
"\n"
"//The extension uses an InjectionTarget to delegate instantiation, dependency injection \n"
"//and lifecycle callbacks to the CDI container\n"
-"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
+"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
"\n"
"//each instance needs its own CDI CreationalContext\n"
"CreationalContext ctx = beanManager.createCreationalContext(null);\n"
@@ -324,33 +324,33 @@ msgstr "Les instances de la class abstraite Bean représenten
#. Tag: para
#, no-c-format
-msgid "The Bean interface exposes all the interesting things we dicussed in ."
+msgid "The Bean interface exposes all the interesting things we discussed in ."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"public interface Bean<T> extends Contextual<T> {\n"
-" public Set<Type> getTypes();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Class<? extends Annotation> getScope();\n"
+"public interface Bean<T> extends Contextual<T> {\n"
+" public Set<Type> getTypes();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Class<? extends Annotation> getScope();\n"
" public String getName();\n"
-" public Set<Class<? extends Annotation>> getStereotypes();\n"
-" public Class<?> getBeanClass();\n"
+" public Set<Class<? extends Annotation>> getStereotypes();\n"
+" public Class<?> getBeanClass();\n"
" public boolean isAlternative();\n"
" public boolean isNullable();\n"
-" public Set<InjectionPoint> getInjectionPoints();\n"
+" public Set<InjectionPoint> getInjectionPoints();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's an easy way to find out what beans exist in the application:"
+msgid "There's an easy way to find out what beans exist in the application:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
+msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
msgstr ""
#. Tag: para
@@ -370,7 +370,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
+msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
msgstr ""
#. Tag: programlisting
@@ -381,49 +381,49 @@ msgid ""
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd, BeanManager bm) {\n"
" \n"
" //use this to read annotations of the class\n"
-" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
+" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
"\n"
" //use this to instantiate the class and inject dependencies\n"
-" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
+" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
"\n"
-" abd.addBean( new Bean<SecurityManager>() {\n"
+" abd.addBean( new Bean<SecurityManager>() {\n"
"\n"
" @Override\n"
-" public Class<?> getBeanClass() {\n"
+" public Class<?> getBeanClass() {\n"
" return SecurityManager.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
" public String getName() {\n"
-" return "securityManager";\n"
+" return \"securityManager\";\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getQualifiers() {\n"
-" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
-" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
-" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
+" public Set<Annotation> getQualifiers() {\n"
+" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
+" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
+" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
" return qualifiers;\n"
" }\n"
"\n"
" @Override\n"
-" public Class<? extends Annotation> getScope() {\n"
+" public Class<? extends Annotation> getScope() {\n"
" return SessionScoped.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Class<? extends Annotation>> getStereotypes() {\n"
+" public Set<Class<? extends Annotation>> getStereotypes() {\n"
" return Collections.emptySet();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypes() {\n"
-" Set<Type> types = new HashSet<Type>();\n"
+" public Set<Type> getTypes() {\n"
+" Set<Type> types = new HashSet<Type>();\n"
" types.add(SecurityManager.class);\n"
" types.add(Object.class);\n"
" return types;\n"
@@ -440,7 +440,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
+" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
" SecurityManager instance = it.produce(ctx);\n"
" it.inject(instance, ctx);\n"
" it.postConstruct(instance);\n"
@@ -449,7 +449,7 @@ msgid ""
"\n"
" @Override\n"
" public void destroy(SecurityManager instance, \n"
-" CreationalContext<SecurityManager> ctx) {\n"
+" CreationalContext<SecurityManager> ctx) {\n"
" it.preDestroy(instance);\n"
" it.dispose(instance);\n"
" ctx.release();\n"
@@ -478,7 +478,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
+msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
msgstr ""
#. Tag: programlisting
@@ -486,38 +486,38 @@ msgstr ""
msgid ""
"public class QualifiedNameExtension implements Extension {\n"
"\n"
-" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
+" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
"\n"
" //wrap this to override the annotations of the class\n"
-" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
+" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
" \n"
-" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
+" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
"\n"
" @Override\n"
-" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
+" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
" return at.getConstructors();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedField<? super X>> getFields() {\n"
+" public Set<AnnotatedField<? super X>> getFields() {\n"
" return at.getFields();\n"
" }\n"
"\n"
" @Override\n"
-" public Class<X> getJavaClass() {\n"
+" public Class<X> getJavaClass() {\n"
" return at.getJavaClass();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
+" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
" return at.getMethods();\n"
" }\n"
"\n"
" @Override\n"
-" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
+" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
" if ( Named.class.equals(annType) ) {\n"
" class NamedLiteral \n"
-" extends AnnotationLiteral<Named> \n"
+" extends AnnotationLiteral<Named> \n"
" implements Named {\n"
" @Override\n"
" public String value() {\n"
@@ -526,7 +526,7 @@ msgid ""
" final String qualifiedName;\n"
" if ( pkg.isAnnotationPresent(Named.class) ) {\n"
" qualifiedName = pkg.getAnnotation(Named.class).value() \n"
-" + '.' + unqualifiedName;\n"
+" + '.' + unqualifiedName;\n"
" }\n"
" else {\n"
" qualifiedName = unqualifiedName;\n"
@@ -542,7 +542,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getAnnotations() {\n"
+" public Set<Annotation> getAnnotations() {\n"
" return at.getAnnotations();\n"
" }\n"
"\n"
@@ -552,12 +552,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypeClosure() {\n"
+" public Set<Type> getTypeClosure() {\n"
" return at.getTypeClosure();\n"
" }\n"
"\n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
" return at.isAnnotationPresent(annType);\n"
" }\n"
" \n"
@@ -571,7 +571,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
+msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
msgstr ""
#. Tag: programlisting
@@ -579,17 +579,17 @@ msgstr ""
msgid ""
"class ServiceAlternativeExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" \n"
-" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
+" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
" \n"
" if ( Service.class.isAssignableFrom( type.getJavaClass() ) ) {\n"
" \n"
" //if the class implements Service, make it an @Alternative\n"
-" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
+" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
" \n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
" return annotationType.equals(Alternative.class) ? \n"
" true : type.isAnnotationPresent(annotationType);\n"
" }\n"
@@ -622,7 +622,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
+msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
msgstr ""
#. Tag: programlisting
@@ -642,25 +642,25 @@ msgstr ""
msgid ""
"public class ConfigExtension implements Extension {\n"
"\n"
-"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
+"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
"\t\t\n"
"\t\t//wrap this to intercept the component lifecycle\n"
-"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
+"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
"\t \n"
-" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
+" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
" \n"
" //use this to read annotations of the class and its members\n"
-" AnnotatedType<X> at = pit.getAnnotatedType();\n"
+" AnnotatedType<X> at = pit.getAnnotatedType();\n"
" \n"
" //read the properties file\n"
-" String propsFileName = at.getClass().getSimpleName() + ".properties";\n"
+" String propsFileName = at.getClass().getSimpleName() + \".properties\";\n"
" InputStream stream = at.getJavaClass().getResourceAsStream(propsFileName);\n"
" if (stream!=null) {\n"
" \n"
" try {\n"
" Properties props = new Properties();\n"
" props.load(stream);\n"
-" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
+" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
" String fieldName = property.getKey().toString();\n"
" Object value = property.getValue();\n"
" try {\n"
@@ -672,7 +672,7 @@ msgid ""
" else {\n"
" //TODO: do type conversion automatically\n"
" pit.addDefinitionError( new InjectionException(\n"
-" "field is not of type String: " + field ) );\n"
+" \"field is not of type String: \" + field ) );\n"
" }\n"
" }\n"
" catch (NoSuchFieldException nsfe) {\n"
@@ -688,14 +688,14 @@ msgid ""
" }\n"
" }\n"
" \n"
-" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
+" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
"\n"
" @Override\n"
-" public void inject(X instance, CreationalContext<X> ctx) {\n"
+" public void inject(X instance, CreationalContext<X> ctx) {\n"
" it.inject(instance, ctx);\n"
" \n"
" //set the values onto the new instance of the component\n"
-" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
+" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
" try {\n"
" configuredValue.getKey().set(instance, configuredValue.getValue());\n"
" }\n"
@@ -721,12 +721,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
-" public X produce(CreationalContext<X> ctx) {\n"
+" public X produce(CreationalContext<X> ctx) {\n"
" return it.produce(ctx);\n"
" }\n"
" \n"
@@ -741,7 +741,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
+msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
msgstr ""
#. Tag: title
@@ -758,9 +758,9 @@ msgstr "L'interface Context supporte l'ajout de nouvelles por
#, fuzzy, no-c-format
msgid ""
"public interface Context {\n"
-" public Class<? extends Annotation> getScope();\n"
-" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
-" public <T> T get(Contextual<T> contextual);\n"
+" public Class<? extends Annotation> getScope();\n"
+" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
+" public <T> T get(Contextual<T> contextual);\n"
" boolean isActive();\n"
"}"
msgstr ""
diff --git a/docs/reference/src/main/docbook/fr-FR/gettingstarted.po b/docs/reference/src/main/docbook/fr-FR/gettingstarted.po
index d4c158b190a..ddab19570d9 100644
--- a/docs/reference/src/main/docbook/fr-FR/gettingstarted.po
+++ b/docs/reference/src/main/docbook/fr-FR/gettingstarted.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml \n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-19 20:26+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, Glassfish 3.0 or any compliant Java EE 6 container."
+msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, GlassFish 3.0 or any compliant Java EE 6 container."
msgstr ""
#. Tag: para
@@ -36,7 +36,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To run the examples with the provided build scripts, you'll need the following:"
+msgid "To run the examples with the provided build scripts, you'll need the following:"
msgstr ""
#. Tag: para
@@ -81,12 +81,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
+msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
+msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
msgstr ""
#. Tag: para
@@ -96,7 +96,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
+msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
msgstr ""
#. Tag: title
@@ -106,19 +106,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
+msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
+msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> unzip jboss-6.0.*.zip\n"
-"$> mv jboss-6.0.*/ jboss-as-6.0"
+"$> unzip jboss-6.0.*.zip\n"
+"$> mv jboss-6.0.*/ jboss-as-6.0"
msgstr ""
#. Tag: para
@@ -133,7 +133,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You're now ready to deploy your first example!"
+msgid "You're now ready to deploy your first example!"
msgstr ""
#. Tag: para
@@ -144,20 +144,20 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant deploy"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
+msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> cd /path/to/jboss-as-6.0\n"
-"$> ./bin/run.sh"
+"$> cd /path/to/jboss-as-6.0\n"
+"$> ./bin/run.sh"
msgstr ""
#. Tag: para
@@ -168,8 +168,8 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
-"$> run"
+"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
+"$> run"
msgstr ""
#. Tag: para
@@ -225,18 +225,18 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> cd examples/jsf/translator\n"
-"$> ant deploy"
+"$> cd examples/jsf/translator\n"
+"$> ant deploy"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
+msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
+msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
msgstr ""
#. Tag: title
@@ -246,41 +246,41 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
+msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
+msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> chmod 755 glassfish-v3-unix.sh\n"
-"$> ./glassfish-v3-unix.sh"
+"$> chmod 755 glassfish-v3-unix.sh\n"
+"$> ./glassfish-v3-unix.sh"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
+msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
+msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
-"$> ant package"
+"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
+"$> ant package"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
+msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
msgstr ""
#. Tag: para
@@ -290,12 +290,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin start-domain domain1"
+msgid "$> asadmin start-domain domain1"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on "Applications", then click on the "Deploy..." button under the heading "Applications" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
+msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on \"Applications\", then click on the \"Deploy...\" button under the heading \"Applications\" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
msgstr ""
#. Tag: para
@@ -305,7 +305,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin deploy target/weld-numberguess.war"
+msgid "$> asadmin deploy target/weld-numberguess.war"
msgstr ""
#. Tag: para
@@ -325,22 +325,22 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
+msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
+msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> unzip apache-tomcat-6.0.18.zip"
+msgid "$> unzip apache-tomcat-6.0.18.zip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
+msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
msgstr ""
#. Tag: title
@@ -350,7 +350,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
+msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
msgstr ""
#. Tag: programlisting
@@ -360,7 +360,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now you're ready to deploy the numberguess example to Tomcat!"
+msgid "Now you're ready to deploy the numberguess example to Tomcat!"
msgstr ""
#. Tag: para
@@ -371,13 +371,13 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant tomcat.deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant tomcat.deploy"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with "tomcat."."
+msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with \"tomcat.\"."
msgstr ""
#. Tag: para
@@ -402,21 +402,21 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
+msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> cd /path/to/apache-tomcat-6\n"
-"$> ./bin/start.sh"
+"$> cd /path/to/apache-tomcat-6\n"
+"$> ./bin/start.sh"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
-"$> start"
+"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
+"$> start"
msgstr ""
#. Tag: para
@@ -431,12 +431,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
+msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
+msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
msgstr ""
#. Tag: para
@@ -446,7 +446,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<user username="admin" password="" roles="manager"/>"
+msgid "<user username=\"admin\" password=\"\" roles=\"manager\"/>"
msgstr ""
#. Tag: para
@@ -456,7 +456,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
+msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
msgstr ""
#. Tag: para
@@ -466,7 +466,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn tomcat:redeploy -Ptomcat"
+msgid "$> mvn tomcat:redeploy -Ptomcat"
msgstr ""
#. Tag: para
@@ -481,7 +481,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace tomcat:run -Ptomcat"
+msgid "$> mvn war:inplace tomcat:run -Ptomcat"
msgstr ""
#. Tag: para
@@ -491,12 +491,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Ptomcat"
+msgid "$> mvn compile war:inplace -Ptomcat"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
+msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
msgstr ""
#. Tag: title
@@ -511,12 +511,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
+msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
+msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
msgstr ""
#. Tag: para
@@ -527,8 +527,8 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> mvn war:inplace jetty:run -Pjetty"
+"$> cd examples/jsf/numberguess\n"
+"$> mvn war:inplace jetty:run -Pjetty"
msgstr ""
#. Tag: para
@@ -543,7 +543,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Pjetty"
+msgid "$> mvn compile war:inplace -Pjetty"
msgstr ""
#. Tag: para
@@ -553,7 +553,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclispe[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
+msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclipse[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
msgstr ""
#. Tag: para
@@ -563,7 +563,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
+msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
msgstr ""
#. Tag: para
@@ -573,12 +573,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace -Pjetty-ide"
+msgid "$> mvn war:inplace -Pjetty-ide"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using "Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
+msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using \"Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/fr-FR/injection.po b/docs/reference/src/main/docbook/fr-FR/injection.po
index 6d2603d9db1..ddc54f19202 100644
--- a/docs/reference/src/main/docbook/fr-FR/injection.po
+++ b/docs/reference/src/main/docbook/fr-FR/injection.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-05 00:00+0100\n"
"Last-Translator: Vincent Latombe \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "Injection de dépendance"
#. Tag: para
#, no-c-format
-msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
+msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
msgstr ""
#. Tag: title
@@ -146,7 +146,7 @@ msgstr "Ensuite, le gestionnaire de Web Bean initialise les valeurs de tous les
#. Tag: para
#, fuzzy, no-c-format
-msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
+msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
msgstr "Puis, le gestionnaire de Web Bean appelle toutes les méthodes d'initalisation du Web Bean."
#. Tag: para
@@ -182,7 +182,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
+msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
msgstr ""
#. Tag: title
@@ -192,7 +192,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
+msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
msgstr "La spécification Web Beans définie une procédure, appelée algorithme de résolution typesafe, que le gestionnaire de Web Beans suit lorsqu'il identifie le Web Bean à injecter dans un point d'injection. Cet algorithme paraît complexe à première vue, mais une fois que vous l'avez compris, il est plutôt intuitif. La résolution typesafe est effectuée au moment de l'initialisation du système, ce qui veut dire que le gestionnaire informera l'utilisateur immédiatement si une dépendance d'un Web Bean ne peut être satisfaite, en lançant une UnsatisfiedDependencyException ou une AmbiguousDependencyException."
#. Tag: para
@@ -217,12 +217,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
+msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
+msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
msgstr ""
#. Tag: title
@@ -383,7 +383,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you may be thinking, "What's the different between using a qualifier and just specifying the exact implementation class you want?" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alterative implementations of @Asynchronous PaymentProcessor!"
+msgid "Now, you may be thinking, \"What's the different between using a qualifier and just specifying the exact implementation class you want?\" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alternative implementations of @Asynchronous PaymentProcessor!"
msgstr ""
#. Tag: title
@@ -393,7 +393,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to decare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
+msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to declare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
msgstr ""
#. Tag: para
@@ -405,7 +405,7 @@ msgstr ""
#, no-c-format
msgid ""
"@Inject \n"
-"void initServices(@Any Instance<Service> services) { \n"
+"void initServices(@Any Instance<Service> services) { \n"
" for (Service service: services) {\n"
" service.init();\n"
" }\n"
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then we select one of the possible member values when appling the qualifier:"
+msgid "Then we select one of the possible member values when applying the qualifier:"
msgstr ""
#. Tag: programlisting
@@ -462,7 +462,7 @@ msgid ""
"@Target({METHOD, FIELD, PARAMETER, TYPE})\n"
"public @interface PayBy {\n"
" PaymentMethod value();\n"
-" @Nonbinding String comment() default "";\n"
+" @Nonbinding String comment() default \"\";\n"
"}"
msgstr ""
"this FAQ for step-by-step instructions for how to resolve an ambigous resolution exception between a raw bean type and a producer method that returns the same bean type."
+msgid "See this FAQ for step-by-step instructions for how to resolve an ambiguous resolution exception between a raw bean type and a producer method that returns the same bean type."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Just remember: "There can be only one.""
+msgid "Just remember: \"There can be only one.\""
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
+msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
+msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
msgstr ""
#. Tag: title
@@ -645,7 +645,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
+msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
msgstr ""
#. Tag: para
@@ -670,7 +670,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "classes which don't have a non-private constructor with no parameters, and"
+msgid "classes which don't have a non-private constructor with no parameters, and"
msgstr ""
#. Tag: para
@@ -685,7 +685,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
+msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
msgstr ""
#. Tag: para
@@ -695,7 +695,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "change the type of the injection point to Instance<X>,"
+msgid "change the type of the injection point to Instance<X>,"
msgstr ""
#. Tag: para
@@ -725,7 +725,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But we didn't get around to implementing this yet."
+msgid "But we didn't get around to implementing this yet."
msgstr ""
#. Tag: title
@@ -760,7 +760,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -795,7 +795,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -810,19 +810,19 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, we need to obtain an instance of our qualifier type. Since annotatons are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
+msgid "Next, we need to obtain an instance of our qualifier type. Since annotations are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"abstract class AsynchronousQualifier\n"
-"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
+"class AsynchronousQualifier\n"
+"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
msgstr ""
#. Tag: para
@@ -831,15 +831,15 @@ msgid "In some cases, we can use an anonymous class:"
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
"PaymentProcessor p = paymentProcessorSource\n"
-" .select(new AnnotationLiteral<Asynchronous>() {});"
-msgstr ""
+" .select(new AnnotationLiteral<Asynchronous>() {});"
+msgstr ""
#. Tag: para
#, no-c-format
-msgid "We can't use an anonymous class to implement a qualifier type with members."
+msgid "However, we can't use an anonymous class to implement a qualifier type with members."
msgstr ""
#. Tag: para
@@ -887,7 +887,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
+msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
msgstr ""
#. Tag: programlisting
@@ -924,7 +924,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
+msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
msgstr ""
#. Tag: programlisting
@@ -952,8 +952,8 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@HttpParam("username") String username;\n"
-"@HttpParam("password") String password;"
+"@HttpParam(\"username\") String username;\n"
+"@HttpParam(\"password\") String password;"
msgstr ""
#. Tag: para
@@ -966,7 +966,7 @@ msgstr ""
msgid ""
"class HttpParams\n"
"\n"
-" @Produces @HttpParam("")\n"
+" @Produces @HttpParam(\"\")\n"
" String getParamValue(InjectionPoint ip) {\n"
" ServletRequest request = (ServletRequest) FacesContext.getCurrentInstance().getExternalContext().getRequest();\n"
" return request.getParameter(ip.getAnnotated().getAnnotation(HttpParam.class).value());\n"
@@ -977,7 +977,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own prodcuer for the request and have it injected as a method parameter."
+msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own producer for the request and have it injected as a method parameter."
msgstr ""
#. Tag: para
@@ -995,8 +995,8 @@ msgstr ""
msgid ""
"public interface InjectionPoint { \n"
" public Type getType();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Bean<?> getBean();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Bean<?> getBean();\n"
" public Member getMember();\n"
" public Annotated getAnnotated();\n"
" public boolean isDelegate();\n"
diff --git a/docs/reference/src/main/docbook/fr-FR/interceptors.po b/docs/reference/src/main/docbook/fr-FR/interceptors.po
index 3239c4d6f2d..974929b2557 100644
--- a/docs/reference/src/main/docbook/fr-FR/interceptors.po
+++ b/docs/reference/src/main/docbook/fr-FR/interceptors.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml \n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-19 20:26+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -98,7 +98,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
+msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
msgstr ""
#. Tag: programlisting
@@ -142,7 +142,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
+msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
msgstr ""
#. Tag: programlisting
@@ -192,16 +192,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -232,17 +232,17 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -327,7 +327,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Secure(rolesAllowed="admin") @Transactional\n"
+"@Secure(rolesAllowed=\"admin\") @Transactional\n"
"public class ShoppingCart { ... }"
msgstr ""
@@ -400,7 +400,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Well, fortunately, CDI works around this missing feature of Java. We may annotate one interceptor binding type with other interceptor binding types (termed a meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
+msgid "Well, fortunately, CDI works around this missing feature of Java. We may annotate one interceptor binding type with other interceptor binding types (termed a meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
msgstr ""
#. Tag: programlisting
@@ -454,7 +454,7 @@ msgstr ""
#. Tag: para
#, 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."
+msgid "the interceptor ordering is non-global — it is determined by the order in which interceptors are listed at the class level."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/fr-FR/intro.po b/docs/reference/src/main/docbook/fr-FR/intro.po
index e4d14970c64..6fcc800c79f 100644
--- a/docs/reference/src/main/docbook/fr-FR/intro.po
+++ b/docs/reference/src/main/docbook/fr-FR/intro.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml \n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-19 20:26+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
+msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
msgstr ""
#. Tag: title
@@ -36,27 +36,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Prior to Java EE 6, there was no clear definition of the term "bean" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications "beans" for years. There were even a couple of different kinds of things called "beans" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a "bean". What we've been missing is a common definition."
+msgid "Prior to Java EE 6, there was no clear definition of the term \"bean\" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications \"beans\" for years. There were even a couple of different kinds of things called \"beans\" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a \"bean\". What we've been missing is a common definition."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
+msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
+msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
+msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now let's see how to create your first bean that actually uses CDI."
+msgid "Now let's see how to create your first bean that actually uses CDI."
msgstr ""
#. Tag: title
@@ -66,14 +66,14 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
+msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"public class SentenceParser {\n"
-" public List<String> parse(String text) { ... }\n"
+" public List<String> parse(String text) { ... }\n"
"}"
msgstr ""
@@ -107,7 +107,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unfortunately, we don't have a class that translates whole text documents. So let's write a bean for this job:"
+msgid "Unfortunately, we don't have a class that translates whole text documents. So let's write a bean for this job:"
msgstr ""
#. Tag: programlisting
@@ -140,7 +140,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
+msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
msgstr ""
#. Tag: para
@@ -150,7 +150,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
+msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
msgstr ""
#. Tag: programlisting
@@ -189,7 +189,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
+msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
msgstr ""
#. Tag: para
@@ -200,7 +200,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
+"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
"...\n"
"public void translate() {\n"
" textTranslatorInstance.get().translate(inputText);\n"
@@ -209,15 +209,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
+msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
+msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
+msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
msgstr ""
diff --git a/docs/reference/src/main/docbook/fr-FR/next.po b/docs/reference/src/main/docbook/fr-FR/next.po
index 1f911bd49fa..6f9b2f31960 100644
--- a/docs/reference/src/main/docbook/fr-FR/next.po
+++ b/docs/reference/src/main/docbook/fr-FR/next.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-02 23:32+0100\n"
"Last-Translator: Vincent Latombe \n"
"Language-Team: none\n"
@@ -21,12 +21,12 @@ msgstr "Etapes suivantes"
#. Tag: para
#, no-c-format
-msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
+msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
+msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
msgstr "L'implémentation de référence des Web Beans est en train d'être développée sur http://seamframework.org/WebBeans. L'équipe de développement de l'implémentation de référence et le blog du chef de spec des Web Beans est disponible sur http://in.relation.to. Cet article se base en grande partie sur une série de billets publiées là."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/fr-FR/part1.po b/docs/reference/src/main/docbook/fr-FR/part1.po
index 2c049170bbc..ac09c7c0613 100644
--- a/docs/reference/src/main/docbook/fr-FR/part1.po
+++ b/docs/reference/src/main/docbook/fr-FR/part1.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml \n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-19 20:26+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -126,7 +126,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Where should I keep the reference to it when I'm not currently using it?"
+msgid "Where should I keep the reference to it when I'm not currently using it?"
msgstr ""
#. Tag: para
@@ -141,7 +141,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
+msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
msgstr ""
#. Tag: para
@@ -171,12 +171,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
+msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
+msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
msgstr ""
#. Tag: para
@@ -186,7 +186,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
+msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/fr-FR/part3.po b/docs/reference/src/main/docbook/fr-FR/part3.po
index 9fd1172719d..9917644546f 100644
--- a/docs/reference/src/main/docbook/fr-FR/part3.po
+++ b/docs/reference/src/main/docbook/fr-FR/part3.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-07 15:15+0100\n"
"Last-Translator: Vincent Latombe \n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
+msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
msgstr ""
#. Tag: para
@@ -71,7 +71,7 @@ msgstr "Le second thème majeur des Web Beans est le typage fortstéréotypes Web Beans poussent cette idée d'
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
+msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
msgstr "Nous commes maintenant prêts à découvrir quelques fonctionnalités plus avancées des Web Beans. Gardez à l'esprit que ces fonctionnalités existent pour rendre notre code à la fois plus facile à valider et plus compréhensible. La plupart du temps nous n'avons pas réellement besoin d'utiliser ces fonctionnalités, mais si vous les utilisez sagement, vous en viendrez à apprécier leur pouvoir."
#~ msgid "Even Web Beans XML metadata is strongly typed! There's no compiler for XML, so Web Beans takes advantage of XML schemas to validate the Java types and attributes that appear in XML. This approach turns out to make the XML more literate, just like annotations made our Java code more literate."
diff --git a/docs/reference/src/main/docbook/fr-FR/part4.po b/docs/reference/src/main/docbook/fr-FR/part4.po
index e4f90ee0fd0..b083af8bff3 100644
--- a/docs/reference/src/main/docbook/fr-FR/part4.po
+++ b/docs/reference/src/main/docbook/fr-FR/part4.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-07 15:02+0100\n"
"Last-Translator: Vincent Latombe \n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
+msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
msgstr ""
#. Tag: para
@@ -26,7 +26,7 @@ msgstr "Nous avons déjà vu comment les Web Beans aident à intégrer les EJB e
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
+msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
msgstr "Nous sommes sur le point de tirer plein avantage de la plateforme Java EE dans une application utilisant les Web Beans. Nous rencontrerons aussi brièvement un ensemble de SPIs qui sont fournies pour supporter des extensions portables à Web Beans. Vous pouvez ne pas avoir besoin d'utiliser ces SPIs directement, mais il est bon de savoir qu'elles sont là si vous avez besoin d'elles. Et plus important , vous en tirerez avantage indirectement chaque fois que vous utilisez une extension tierce."
#~ msgid "The third theme of Web Beans is integration. Web Beans was designed to work in concert with other technologies, helping the application developer fit the other technologies together. Web Beans is an open technology. It forms a part of the Java EE ecosystem, and is itself the foundation for a new ecosystem of portable extensions and integration with existing frameworks and technologies."
diff --git a/docs/reference/src/main/docbook/fr-FR/part5.po b/docs/reference/src/main/docbook/fr-FR/part5.po
index 06f8b8358f1..1c9d1037270 100644
--- a/docs/reference/src/main/docbook/fr-FR/part5.po
+++ b/docs/reference/src/main/docbook/fr-FR/part5.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-28 17:09+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and Glassfish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
+msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and GlassFish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/fr-FR/producermethods.po b/docs/reference/src/main/docbook/fr-FR/producermethods.po
index 662aead45d0..564e23ea58a 100644
--- a/docs/reference/src/main/docbook/fr-FR/producermethods.po
+++ b/docs/reference/src/main/docbook/fr-FR/producermethods.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml \n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-19 20:26+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
+msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
msgstr ""
#. Tag: para
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
+msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
msgstr ""
#. Tag: programlisting
@@ -139,7 +139,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
+msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
msgstr ""
#. Tag: para
@@ -154,12 +154,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
+msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
+msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
msgstr ""
#. Tag: programlisting
@@ -180,12 +180,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of "promoting" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left "hanging" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
+msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of \"promoting\" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left \"hanging\" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
+msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
msgstr ""
#. Tag: para
@@ -221,7 +221,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
+msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
msgstr ""
#. Tag: title
diff --git a/docs/reference/src/main/docbook/fr-FR/resources.po b/docs/reference/src/main/docbook/fr-FR/resources.po
index a51e357fa01..01fdf580a62 100644
--- a/docs/reference/src/main/docbook/fr-FR/resources.po
+++ b/docs/reference/src/main/docbook/fr-FR/resources.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a nonportable "mapped name"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
+msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a non-portable \"mapped name\"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
msgstr ""
#. Tag: para
@@ -72,35 +72,35 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @WebServiceRef(lookup="java:app/service/Catalog")\n"
+"@Produces @WebServiceRef(lookup=\"java:app/service/Catalog\")\n"
"Catalog catalog;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @Resource(lookup="java:global/env/jdbc/CustomerDatasource") \n"
+"@Produces @Resource(lookup=\"java:global/env/jdbc/CustomerDatasource\") \n"
"@CustomerDatabase Datasource customerDatabase;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceContext(unitName="CustomerDatabase")\n"
+"@Produces @PersistenceContext(unitName=\"CustomerDatabase\")\n"
"@CustomerDatabase EntityManager customerDatabasePersistenceContext;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceUnit(unitName="CustomerDatabase") \n"
+"@Produces @PersistenceUnit(unitName=\"CustomerDatabase\") \n"
"@CustomerDatabase EntityManagerFactory customerDatabasePersistenceUnit;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @EJB(ejbLink="../their.jar#PaymentService") \n"
+"@Produces @EJB(ejbLink=\"../their.jar#PaymentService\") \n"
"PaymentService paymentService;"
msgstr ""
@@ -126,7 +126,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
+msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
msgstr ""
#. Tag: title
@@ -171,7 +171,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
+msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
msgstr ""
#. Tag: programlisting
@@ -186,7 +186,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@PersistenceContext(unitName="CustomerDatabase") EntityManager"
+msgid "@PersistenceContext(unitName=\"CustomerDatabase\") EntityManager"
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/fr-FR/ri-spi.po b/docs/reference/src/main/docbook/fr-FR/ri-spi.po
index 4cdd6345ab1..3d52b6ba643 100644
--- a/docs/reference/src/main/docbook/fr-FR/ri-spi.po
+++ b/docs/reference/src/main/docbook/fr-FR/ri-spi.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml \n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-20 22:07+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -31,7 +31,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the "Weld: Servlets" extension will be sufficient, and will work in any container supporting the Servlet API."
+msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the \"Weld: Servlets\" extension will be sufficient, and will work in any container supporting the Servlet API."
msgstr ""
#. Tag: para
@@ -56,7 +56,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
+msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
msgstr ""
#. Tag: para
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
+msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
msgstr ""
#. Tag: para
@@ -96,7 +96,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
+msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
msgstr ""
#. Tag: para
@@ -106,12 +106,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
+msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
+msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
msgstr ""
#. Tag: para
@@ -126,7 +126,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
+msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
msgstr ""
#. Tag: para
@@ -156,7 +156,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
+msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
msgstr ""
#. Tag: para
@@ -196,7 +196,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
+msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
msgstr ""
#. Tag: title
@@ -211,7 +211,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
+msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
msgstr ""
#. Tag: para
@@ -276,7 +276,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); intercepter will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
+msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); interceptor will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
msgstr ""
#. Tag: para
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
+msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
msgstr ""
#. Tag: title
@@ -366,7 +366,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programtically, or built in). Bean validation will validate all beans."
+msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programmatically, or built in). Bean validation will validate all beans."
msgstr ""
#. Tag: para
@@ -426,7 +426,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuation, classloader isolation for each CDI application."
+msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuration, classloader isolation for each CDI application."
msgstr ""
#. Tag: term
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You must ensure that that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
+msgid "You must ensure that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
msgstr ""
#. Tag: term
@@ -582,7 +582,7 @@ msgid ""
"InjectionTarget it = weldBeanManager.fireProcessInjectionTarget(clazz);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
+"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
"\n"
"// Produce the instance, performing any constructor injection required\n"
"Object instance = it.produce();\n"
@@ -616,16 +616,16 @@ msgstr ""
msgid ""
"// Obtain the EjbDescriptor for the EJB\n"
"// You may choose to use this utility method to get the descriptor\n"
-"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
+"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
"\n"
"// Get an the Bean object\n"
-"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
+"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
"\n"
"// Create the injection target\n"
"InjectionTarget it = deploymentBeanManager.createInjectionTarget(ejbDescriptor);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
+"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
"\n"
"// Perform injection and call initializers\n"
"it.inject(instance, cc);\n"
diff --git a/docs/reference/src/main/docbook/fr-FR/scopescontexts.po b/docs/reference/src/main/docbook/fr-FR/scopescontexts.po
index ebc0dcc5982..811f4ac3ea3 100644
--- a/docs/reference/src/main/docbook/fr-FR/scopescontexts.po
+++ b/docs/reference/src/main/docbook/fr-FR/scopescontexts.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml \n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-19 20:26+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
+msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
msgstr ""
#. Tag: para
@@ -46,7 +46,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
+msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
msgstr ""
#. Tag: title
@@ -56,7 +56,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
+msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
msgstr ""
#. Tag: programlisting
@@ -70,7 +70,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
+msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
msgstr ""
#. Tag: para
@@ -87,7 +87,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Usually, you'll use one of CDI's built-in scopes."
+msgid "Usually, you'll use one of CDI's built-in scopes."
msgstr ""
#. Tag: title
@@ -187,7 +187,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
+msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
msgstr ""
#. Tag: title
@@ -212,7 +212,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
+msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
msgstr ""
#. Tag: para
@@ -305,25 +305,25 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<a href="/addProduct.jsp?cid=#{conversation.id}">Add Product</a>"
+msgid "<a href=\"/addProduct.jsp?cid=#{conversation.id}\">Add Product</a>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's probably better to use one of the link components in JSF 2:"
+msgid "It's probably better to use one of the link components in JSF 2:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:link outcome="/addProduct.xhtml" value="Add Product">\n"
-" <f:param name="cid" value="#{javax.enterprise.context.conversation.id}"/>\n"
-"</h:link>"
+"<h:link outcome=\"/addProduct.xhtml\" value=\"Add Product\">\n"
+" <f:param name=\"cid\" value=\"#{javax.enterprise.context.conversation.id}\"/>\n"
+"</h:link>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a "flash" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
+msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a \"flash\" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
msgstr ""
#. Tag: title
@@ -333,7 +333,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
+msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
msgstr ""
#. Tag: para
@@ -363,12 +363,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can guess what "singleton" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
+msgid "You can guess what \"singleton\" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
+msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
msgstr ""
#. Tag: para
@@ -388,7 +388,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
+msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
msgstr ""
#. Tag: para
@@ -428,12 +428,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
+msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
+msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
msgstr ""
#. Tag: para
@@ -494,5 +494,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This feature is particularly useful with producer methods, as we'll see in the next chapter."
+msgid "This feature is particularly useful with producer methods, as we'll see in ."
msgstr ""
diff --git a/docs/reference/src/main/docbook/fr-FR/specialization.po b/docs/reference/src/main/docbook/fr-FR/specialization.po
index 206d76833fb..9863de15e9d 100644
--- a/docs/reference/src/main/docbook/fr-FR/specialization.po
+++ b/docs/reference/src/main/docbook/fr-FR/specialization.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml \n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-19 20:26+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
+msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
msgstr ""
#. Tag: para
@@ -41,12 +41,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
+msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
+msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
msgstr ""
#. Tag: title
@@ -70,7 +70,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
+msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
msgstr ""
#. Tag: programlisting
@@ -100,12 +100,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
+msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
+msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
msgstr ""
#. Tag: programlisting
@@ -141,16 +141,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <alternatives>\n"
-" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
-" </alternatives>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <alternatives>\n"
+" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
+" </alternatives>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -175,7 +175,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
+msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
msgstr ""
#. Tag: para
@@ -230,7 +230,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
+msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/fr-FR/stereotypes.po b/docs/reference/src/main/docbook/fr-FR/stereotypes.po
index 313abd786c5..993ded7aee4 100644
--- a/docs/reference/src/main/docbook/fr-FR/stereotypes.po
+++ b/docs/reference/src/main/docbook/fr-FR/stereotypes.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml \n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-19 20:26+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -93,7 +93,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
+msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
msgstr ""
#. Tag: title
@@ -130,7 +130,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
+msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
msgstr ""
#. Tag: title
@@ -227,12 +227,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
+msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
+msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
msgstr ""
#. Tag: programlisting
@@ -253,7 +253,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
+msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/fr-FR/weldexamples.po b/docs/reference/src/main/docbook/fr-FR/weldexamples.po
index b3c1876a727..d6848def8b9 100644
--- a/docs/reference/src/main/docbook/fr-FR/weldexamples.po
+++ b/docs/reference/src/main/docbook/fr-FR/weldexamples.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
+msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
msgstr ""
#. Tag: title
@@ -31,75 +31,75 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
+msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
+msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
+msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<faces-config version="2.0"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<faces-config version=\"2.0\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd">\n"
-"</faces-config>"
+" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd\">\n"
+"</faces-config>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
+msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, there's the familiar web.xml:"
+msgid "Finally, there's the familiar web.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<web-app version="2.5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<web-app version=\"2.5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd\">\n"
" \n"
-" <display-name>weld-jsf-numberguess-war</display-name>\n"
-" <description>Weld JSF numberguess example (war)</description>\n"
+" <display-name>weld-jsf-numberguess-war</display-name>\n"
+" <description>Weld JSF numberguess example (war)</description>\n"
"\n"
-" <servlet>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
-" <load-on-startup>1</load-on-startup>\n"
-" </servlet>\n"
+" <servlet>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
+" <load-on-startup>1</load-on-startup>\n"
+" </servlet>\n"
"\n"
-" <servlet-mapping>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <url-pattern>*.jsf</url-pattern>\n"
-" </servlet-mapping>\n"
+" <servlet-mapping>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <url-pattern>*.jsf</url-pattern>\n"
+" </servlet-mapping>\n"
" \n"
-" <context-param>\n"
-" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
-" <param-value>.xhtml</param-value>\n"
-" </context-param>\n"
+" <context-param>\n"
+" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
+" <param-value>.xhtml</param-value>\n"
+" </context-param>\n"
"\n"
-" <session-config>\n"
-" <session-timeout>10</session-timeout>\n"
-" </session-config>\n"
+" <session-config>\n"
+" <session-timeout>10</session-timeout>\n"
+" </session-config>\n"
"\n"
-"</web-app>"
+"</web-app>"
msgstr ""
#. Tag: para
@@ -129,51 +129,51 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
+msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"\n"
-" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">\n"
-"<html xmlns="http://www.w3.org/1999/xhtml"\n"
-" xmlns:ui="http://java.sun.com/jsf/facelets"\n"
-" xmlns:h="http://java.sun.com/jsf/html"\n"
-" xmlns:f="http://java.sun.com/jsf/core">\n"
+"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
+" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n"
+"<html xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" xmlns:ui=\"http://java.sun.com/jsf/facelets\"\n"
+" xmlns:h=\"http://java.sun.com/jsf/html\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\">\n"
"\n"
-" <ui:composition template="/template.xhtml">\n"
-" <ui:define name="content">\n"
-" <h1>Guess a number...</h1>\n"
-" <h:form id="numberGuess">\n"
-" <div style="color: red">\n"
-" <h:messages id="messages" globalOnly="false"/>\n"
-" <h:outputText id="Higher" value="Higher!"\n"
-" rendered="#{game.number gt game.guess and game.guess ne 0}"/>\n"
-" <h:outputText id="Lower" value="Lower!"\n"
-" rendered="#{game.number lt game.guess and game.guess ne 0}"/>\n"
-" </div>\n"
+" <ui:composition template=\"/template.xhtml\">\n"
+" <ui:define name=\"content\">\n"
+" <h1>Guess a number...</h1>\n"
+" <h:form id=\"numberGuess\">\n"
+" <div style=\"color: red\">\n"
+" <h:messages id=\"messages\" globalOnly=\"false\"/>\n"
+" <h:outputText id=\"Higher\" value=\"Higher!\"\n"
+" rendered=\"#{game.number gt game.guess and game.guess ne 0}\"/>\n"
+" <h:outputText id=\"Lower\" value=\"Lower!\"\n"
+" rendered=\"#{game.number lt game.guess and game.guess ne 0}\"/>\n"
+" </div>\n"
" \n"
-" <div>\n"
-" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
+" <div>\n"
+" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
" You have #{game.remainingGuesses} guesses remaining.\n"
-" </div>\n"
+" </div>\n"
" \n"
-" <div>\n"
+" <div>\n"
" Your guess: \n"
-" <h:inputText id="inputGuess" value="#{game.guess}"\n"
-" size="3" required="true" disabled="#{game.number eq game.guess}"\n"
-" validator="#{game.validateNumberRange}"/>\n"
-" <h:commandButton id="guessButton" value="Guess" \n"
-" action="#{game.check}" disabled="#{game.number eq game.guess}"/>\n"
-" </div>\n"
-" <div>\n"
-" <h:commandButton id="restartButton" value="Reset" action="#{game.reset}" immediate="true"/>\n"
-" </div>\n"
-" </h:form>\n"
-" </ui:define>\n"
-" </ui:composition>\n"
-"</html>"
+" <h:inputText id=\"inputGuess\" value=\"#{game.guess}\"\n"
+" size=\"3\" required=\"true\" disabled=\"#{game.number eq game.guess}\"\n"
+" validator=\"#{game.validateNumberRange}\"/>\n"
+" <h:commandButton id=\"guessButton\" value=\"Guess\" \n"
+" action=\"#{game.check}\" disabled=\"#{game.number eq game.guess}\"/>\n"
+" </div>\n"
+" <div>\n"
+" <h:commandButton id=\"restartButton\" value=\"Reset\" action=\"#{game.reset}\" immediate=\"true\"/>\n"
+" </div>\n"
+" </h:form>\n"
+" </ui:define>\n"
+" </ui:composition>\n"
+"</html>"
msgstr ""
#. Tag: para
@@ -183,7 +183,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are a number of messages which can be sent to the user, "Higher!", "Lower!" and "Correct!""
+msgid "There are a number of messages which can be sent to the user, \"Higher!\", \"Lower!\" and \"Correct!\""
msgstr ""
#. Tag: para
@@ -198,7 +198,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
+msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
msgstr ""
#. Tag: para
@@ -266,7 +266,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Generator is application scoped, so we don't get a different random each time."
+msgid "The Generator is application scoped, so we don't get a different random each time."
msgstr ""
#. Tag: para
@@ -276,12 +276,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
+msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
+msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
msgstr ""
#. Tag: programlisting
@@ -298,19 +298,19 @@ msgid ""
" private int remainingGuesses;\n"
"\n"
" @Inject @MaxNumber private int maxNumber;\n"
-" @Inject @Random Instance<Integer> randomNumber;\n"
+" @Inject @Random Instance<Integer> randomNumber;\n"
" \n"
" public Game() {}\n"
" \n"
" public void check() {\n"
-" if (guess > number) {\n"
+" if (guess > number) {\n"
" biggest = guess - 1;\n"
" }\n"
-" else if (guess < number) {\n"
+" else if (guess < number) {\n"
" smallest = guess + 1;\n"
" }\n"
" else if (guess == number) {\n"
-" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage("Correct!"));\n"
+" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage(\"Correct!\"));\n"
" }\n"
" remainingGuesses--;\n"
" }\n"
@@ -325,18 +325,18 @@ msgid ""
" }\n"
" \n"
" public void validateNumberRange(FacesContext context, UIComponent toValidate, Object value) {\n"
-" if (remainingGuesses <= 0) {\n"
-" FacesMessage message = new FacesMessage("No guesses left!");\n"
+" if (remainingGuesses <= 0) {\n"
+" FacesMessage message = new FacesMessage(\"No guesses left!\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" ((UIInput) toValidate).setValid(false);\n"
" return;\n"
" }\n"
" int input = (Integer) value;\n"
"\n"
-" if (input < smallest || input > biggest) {\n"
+" if (input < smallest || input > biggest) {\n"
" ((UIInput) toValidate).setValid(false);\n"
"\n"
-" FacesMessage message = new FacesMessage("Invalid guess");\n"
+" FacesMessage message = new FacesMessage(\"Invalid guess\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" }\n"
" }\n"
@@ -385,20 +385,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
+msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
+msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
msgstr ""
#. Tag: title
@@ -418,17 +418,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin ."
+msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects . Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
+msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects. Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This will create a project in your workspace called weld-se-numberguess ."
+msgid "This will create a project in your workspace called weld-se-numberguess."
msgstr ""
#. Tag: para
@@ -438,7 +438,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to get the example running!"
+msgid "It's time to get the example running!"
msgstr ""
#. Tag: title
@@ -448,12 +448,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
+msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right click on the project, and choose Run As -> Run As Application:"
+msgid "Right click on the project, and choose Run As -> Run As Application:"
msgstr ""
#. Tag: para
@@ -503,7 +503,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's have a look at the significant code and configuration files that make up this example."
+msgid "Let's have a look at the significant code and configuration files that make up this example."
msgstr ""
#. Tag: para
@@ -513,7 +513,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
+msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
msgstr ""
#. Tag: programlisting
@@ -558,7 +558,7 @@ msgid ""
"\n"
" public boolean isGameLost()\n"
" {\n"
-" return guess != number && remainingGuesses <= 0;\n"
+" return guess != number && remainingGuesses <= 0;\n"
" }\n"
"\n"
" public boolean check()\n"
@@ -567,12 +567,12 @@ msgid ""
"\n"
" if (checkNewNumberRangeIsValid())\n"
" {\n"
-" if (guess > number)\n"
+" if (guess > number)\n"
" {\n"
" biggest = guess - 1;\n"
" }\n"
"\n"
-" if (guess < number)\n"
+" if (guess < number)\n"
" {\n"
" smallest = guess + 1;\n"
" }\n"
@@ -590,7 +590,7 @@ msgid ""
"\n"
" private boolean checkNewNumberRangeIsValid()\n"
" {\n"
-" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
+" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
" }\n"
"\n"
" @PostConstruct\n"
@@ -607,12 +607,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
+msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
+msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
msgstr ""
#. Tag: para
@@ -642,12 +642,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
+msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
+msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
msgstr ""
#. Tag: programlisting
@@ -660,11 +660,11 @@ msgid ""
"\n"
" public String getChallengeMessage()\n"
" {\n"
-" StringBuilder challengeMsg = new StringBuilder("I'm thinking of a number between ");\n"
+" StringBuilder challengeMsg = new StringBuilder(\"I'm thinking of a number between \");\n"
" challengeMsg.append(game.getSmallest());\n"
-" challengeMsg.append(" and ");\n"
+" challengeMsg.append(\" and \");\n"
" challengeMsg.append(game.getBiggest());\n"
-" challengeMsg.append(". Can you guess what it is?");\n"
+" challengeMsg.append(\". Can you guess what it is?\");\n"
"\n"
" return challengeMsg.toString();\n"
" }\n"
@@ -673,34 +673,34 @@ msgid ""
" {\n"
" if (game.isGameWon())\n"
" {\n"
-" return "You guessed it! The number was " + game.getNumber();\n"
+" return \"You guessed it! The number was \" + game.getNumber();\n"
" }\n"
" else if (game.isGameLost())\n"
" {\n"
-" return "You are fail! The number was " + game.getNumber();\n"
+" return \"You are fail! The number was \" + game.getNumber();\n"
" }\n"
" else if (!game.isValidNumberRange())\n"
" {\n"
-" return "Invalid number range!";\n"
+" return \"Invalid number range!\";\n"
" }\n"
" else if (game.getRemainingGuesses() == Game.MAX_NUM_GUESSES)\n"
" {\n"
-" return "What is your first guess?";\n"
+" return \"What is your first guess?\";\n"
" }\n"
" else\n"
" {\n"
" String direction = null;\n"
"\n"
-" if (game.getGuess() < game.getNumber())\n"
+" if (game.getGuess() < game.getNumber())\n"
" {\n"
-" direction = "Higher";\n"
+" direction = \"Higher\";\n"
" }\n"
" else\n"
" {\n"
-" direction = "Lower";\n"
+" direction = \"Lower\";\n"
" }\n"
"\n"
-" return direction + "! You have " + game.getRemainingGuesses() + " guesses left.";\n"
+" return direction + \"! You have \" + game.getRemainingGuesses() + \" guesses left.\";\n"
" }\n"
" }\n"
"}"
@@ -713,7 +713,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
+msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
msgstr ""
#. Tag: para
@@ -783,7 +783,7 @@ msgid ""
" private void refreshUI() {\n"
" mainLabel.setText( msgGenerator.getChallengeMessage() );\n"
" messageLabel.setText( msgGenerator.getResultMessage() );\n"
-" guessText.setText( "" );\n"
+" guessText.setText( \"\" );\n"
" guessesLeftBar.setValue( game.getRemainingGuesses() );\n"
" guessText.requestFocus();\n"
" }\n"
@@ -818,7 +818,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
+msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
msgstr ""
#. Tag: para
@@ -828,7 +828,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Calls game.check() to validate and perform one 'turn' of the game"
+msgid "Calls game.check() to validate and perform one 'turn' of the game"
msgstr ""
#. Tag: para
@@ -853,7 +853,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
+msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
msgstr ""
#. Tag: para
@@ -863,25 +863,25 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
+msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<plugin>\n"
-" <groupId>org.apache.maven.plugins</groupId>\n"
-" <artifactId>maven-ear-plugin</artifactId>\n"
-" <configuration>\n"
-" <modules>\n"
-" <webModule>\n"
-" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
-" <artifactId>weld-jsf-translator-war</artifactId>\n"
-" <contextRoot>/weld-translator</contextRoot>\n"
-" </webModule>\n"
-" </modules>\n"
-" </configuration>\n"
-"</plugin>"
+"<plugin>\n"
+" <groupId>org.apache.maven.plugins</groupId>\n"
+" <artifactId>maven-ear-plugin</artifactId>\n"
+" <configuration>\n"
+" <modules>\n"
+" <webModule>\n"
+" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
+" <artifactId>weld-jsf-translator-war</artifactId>\n"
+" <contextRoot>/weld-translator</contextRoot>\n"
+" </webModule>\n"
+" </modules>\n"
+" </configuration>\n"
+"</plugin>"
msgstr ""
#. Tag: para
@@ -891,72 +891,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
+msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<application version="5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<application version=\"5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/application_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/application_5.xsd\">\n"
"\n"
-" <display-name>weld-jsf-translator-ear</display-name>\n"
-" <description>The Weld JSF translator example (ear)</description>\n"
+" <display-name>weld-jsf-translator-ear</display-name>\n"
+" <description>The Weld JSF translator example (ear)</description>\n"
" \n"
-" <module>\n"
-" <web>\n"
-" <web-uri>weld-translator.war</web-uri>\n"
-" <context-root>/weld-translator</context-root>\n"
-" </web>\n"
-" </module>\n"
-" <module>\n"
-" <ejb>weld-translator.jar</ejb>\n"
-" </module>\n"
-"</application>"
+" <module>\n"
+" <web>\n"
+" <web-uri>weld-translator.war</web-uri>\n"
+" <context-root>/weld-translator</context-root>\n"
+" </web>\n"
+" </module>\n"
+" <module>\n"
+" <ejb>weld-translator.jar</ejb>\n"
+" </module>\n"
+"</application>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
+msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (ommitted here for brevity):"
+msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (omitted here for brevity):"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:form id="translator">\n"
+"<h:form id=\"translator\">\n"
"\n"
-" <table>\n"
-" <tr align="center" style="font-weight: bold">\n"
-" <td>\n"
+" <table>\n"
+" <tr align=\"center\" style=\"font-weight: bold\">\n"
+" <td>\n"
" Your text\n"
-" </td>\n"
-" <td>\n"
+" </td>\n"
+" <td>\n"
" Translation\n"
-" </td>\n"
-" </tr>\n"
-" <tr>\n"
-" <td>\n"
-" <h:inputTextarea id="text" value="#{translator.text}" required="true" rows="5" cols="80"/>\n"
-" </td>\n"
-" <td>\n"
-" <h:outputText value="#{translator.translatedText}"/>\n"
-" </td>\n"
-" </tr>\n"
-" </table>\n"
-" <div>\n"
-" <h:commandButton id="button" value="Translate" action="#{translator.translate}"/>\n"
-" </div>\n"
+" </td>\n"
+" </tr>\n"
+" <tr>\n"
+" <td>\n"
+" <h:inputTextarea id=\"text\" value=\"#{translator.text}\" required=\"true\" rows=\"5\" cols=\"80\"/>\n"
+" </td>\n"
+" <td>\n"
+" <h:outputText value=\"#{translator.translatedText}\"/>\n"
+" </td>\n"
+" </tr>\n"
+" </table>\n"
+" <div>\n"
+" <h:commandButton id=\"button\" value=\"Translate\" action=\"#{translator.translate}\"/>\n"
+" </div>\n"
" \n"
-"</h:form>"
+"</h:form>"
msgstr ""
#. Tag: para
@@ -966,12 +966,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
+msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
+msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
msgstr ""
#. Tag: para
@@ -995,7 +995,7 @@ msgid ""
" public String translate(String text) { \n"
" StringBuilder sb = new StringBuilder(); \n"
" for (String sentence: sentenceParser.parse(text)) { \n"
-" sb.append(translator.translate(sentence)).append(". "); \n"
+" sb.append(translator.translate(sentence)).append(\". \"); \n"
" } \n"
" return sb.toString().trim(); \n"
" }\n"
@@ -1005,7 +1005,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
+msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
msgstr ""
#. Tag: programlisting
@@ -1015,7 +1015,7 @@ msgid ""
"public class SentenceTranslator implements Translator { \n"
"\n"
" public String translate(String sentence) { \n"
-" return "Lorem ipsum dolor sit amet"; \n"
+" return \"Lorem ipsum dolor sit amet\"; \n"
" }\n"
"\n"
"}"
@@ -1031,7 +1031,7 @@ msgstr ""
msgid ""
"@Stateful\n"
"@RequestScoped\n"
-"@Named("translator")\n"
+"@Named(\"translator\")\n"
"public class TranslatorControllerBean implements TranslatorController {\n"
"\n"
" @Inject private TextTranslator translator;\n"
diff --git a/docs/reference/src/main/docbook/it-IT/Weld_-_JSR-299_Reference_Implementation.po b/docs/reference/src/main/docbook/it-IT/Weld_-_JSR-299_Reference_Implementation.po
new file mode 100644
index 00000000000..f4baccac014
--- /dev/null
+++ b/docs/reference/src/main/docbook/it-IT/Weld_-_JSR-299_Reference_Implementation.po
@@ -0,0 +1,59 @@
+#
+# AUTHOR , YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "A note about naming and nomenclature"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Shortly before the final draft of JSR-299 was submitted, the specification changed its name from \"Web Beans\" to \"Java Contexts and Dependency Injection for the Java EE platform\", abbreviated CDI. For a brief period after the renaming, the reference implementation adopted the name \"Web Beans\". However, this ended up causing more confusion than it solved and Red Hat decided to change the name of the reference implementation to \"Weld\". You may still find other documentation, blogs, forum posts, etc. that use the old nomenclature. Please update any references you can. The naming game is over."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You'll also find that some of the functionality that once existed in the specification is now missing, such as defining beans in XML. These features will be available as portable extensions for CDI in the Weld project, and perhaps other implementations."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this reference guide was started while changes were still being made to the specification. We've done our best to update it for accuracy. If you discover a conflict between what is written in this guide and the specification, the specification is the authority—assume it is correct. If you believe you have found an error in the specification, please report it to the JSR-299 EG."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Beans"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Start with Weld, the CDI Reference Implementation"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Loose coupling with strong typing"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "CDI and the Java EE ecosystem"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Weld Reference Guide"
+msgstr ""
+
diff --git a/docs/reference/src/main/docbook/it-IT/beans.po b/docs/reference/src/main/docbook/it-IT/beans.po
index ba4a04031ec..81120cc310d 100644
--- a/docs/reference/src/main/docbook/it-IT/beans.po
+++ b/docs/reference/src/main/docbook/it-IT/beans.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-24 16:04+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
+msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
msgstr ""
#. Tag: para
@@ -56,7 +56,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
+msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
msgstr ""
#. Tag: para
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
+msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
msgstr ""
#. Tag: title
@@ -131,7 +131,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's see what all this new terminology means."
+msgid "Let's see what all this new terminology means."
msgstr ""
#. Tag: title
@@ -141,7 +141,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a "contract" that must be satisfied by the bean to be injected. The contract is:"
+msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a \"contract\" that must be satisfied by the bean to be injected. The contract is:"
msgstr ""
#. Tag: para
@@ -164,7 +164,7 @@ msgstr ""
msgid ""
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
@@ -176,7 +176,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
+msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
msgstr ""
#. Tag: para
@@ -203,12 +203,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
+msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
+msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
msgstr ""
#. Tag: programlisting
@@ -217,7 +217,7 @@ msgid ""
"@Typed(Shop.class)\n"
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
@@ -230,12 +230,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of "quality" using a qualifier."
+msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of \"quality\" using a qualifier."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
+msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
msgstr ""
#. Tag: programlisting
@@ -253,12 +253,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
+msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
+msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
msgstr ""
#. Tag: para
@@ -273,12 +273,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
+msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
msgstr ""
#. Tag: para
@@ -299,12 +294,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If a bean does not explicitly specify a qualifier, it has the default qualifier, @Default."
+msgid "If a bean or an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
+msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
msgstr ""
#. Tag: title
@@ -338,7 +333,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
+msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
msgstr ""
#. Tag: para
@@ -348,7 +343,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk more about scopes in ."
+msgid "We'll talk more about scopes in ."
msgstr ""
#. Tag: title
@@ -369,10 +364,10 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"public @SessionScoped @Named("cart")\n"
+"public @SessionScoped @Named(\"cart\")\n"
"class ShoppingCart implements Serializable { ... }"
msgstr ""
-""
#. Tag: para
@@ -383,9 +378,9 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:dataTable value="#{cart.lineItems}" var="item">\n"
+"<h:dataTable value=\"#{cart.lineItems}\" var=\"item\">\n"
" ...\n"
-"</h:dataTable>"
+"</h:dataTable>"
msgstr ""
"\n"
" ...\n"
@@ -422,7 +417,7 @@ msgstr "Alternative"
#. Tag: para
#, no-c-format
-msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
+msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
msgstr ""
#. Tag: programlisting
@@ -451,12 +446,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
+msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
+msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
msgstr ""
#. Tag: para
@@ -514,17 +509,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
+msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
+msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
+msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
msgstr ""
#. Tag: title
@@ -534,7 +529,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
+msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
msgstr ""
#. Tag: title
@@ -544,7 +539,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
+msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
msgstr ""
#. Tag: para
@@ -569,7 +564,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It has an appropriate constructor—either:"
+msgid "It has an appropriate constructor—either:"
msgstr ""
#. Tag: para
@@ -584,7 +579,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
+msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
msgstr ""
#. Tag: para
@@ -629,12 +624,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
+msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
+msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
msgstr ""
#. Tag: para
@@ -669,7 +664,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
+msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
msgstr ""
#. Tag: para
@@ -684,17 +679,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
+msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
+msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're "heavyweight". It's nothing more than superstition to think that something is "heavier" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like "heavyweight"."
+msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're \"heavyweight\". It's nothing more than superstition to think that something is \"heavier\" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like \"heavyweight\"."
msgstr ""
#. Tag: title
@@ -744,7 +739,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
+msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
msgstr ""
#. Tag: programlisting
@@ -759,7 +754,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "<p>Your raffle number is #{randomNumber}.</p>"
+msgid "<p>Your raffle number is #{randomNumber}.</p>"
msgstr "Your raffle number is #{randomNumber}.
]]>"
#. Tag: para
@@ -800,7 +795,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Produces Set<Roles> getRoles(User user) {\n"
+"@Produces Set<Roles> getRoles(User user) {\n"
" return user.getRoles();\n"
"}"
msgstr ""
@@ -810,7 +805,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk much more about producer methods in ."
+msgid "We'll talk much more about producer methods in ."
msgstr ""
#. Tag: title
@@ -820,7 +815,7 @@ msgstr "Campi produttori"
#. Tag: para
#, no-c-format
-msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
+msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
msgstr ""
#. Tag: programlisting
@@ -828,7 +823,7 @@ msgstr ""
msgid ""
"public class Shop {\n"
" @Produces PaymentProcessor paymentProcessor = ....;\n"
-" @Produces @Catalog List<Product> products = ....;\n"
+" @Produces @Catalog List<Product> products = ....;\n"
"}"
msgstr ""
". Because we can't wait to get to work on some examples."
+msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
msgstr ""
+#, fuzzy
+#~ msgid ""
+#~ "public @SessionScoped @Named("cart")\n"
+#~ "class ShoppingCart implements Serializable { ... }"
+#~ msgstr ""
+#~ ""
+
#, fuzzy
#~ msgid "alternatives"
#~ msgstr "Alternative"
diff --git a/docs/reference/src/main/docbook/it-IT/configure.po b/docs/reference/src/main/docbook/it-IT/configure.po
index eeba87f0a16..01ef2ccd8ab 100644
--- a/docs/reference/src/main/docbook/it-IT/configure.po
+++ b/docs/reference/src/main/docbook/it-IT/configure.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -30,50 +30,50 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
+msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<?xml version="1.0" encoding="UTF-8"?>\n"
-"<beans xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \n"
-" xmlns:weld="http://jboss.org/schema/weld/beans" \n"
-" xsi:schemaLocation="\n"
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<beans xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" \n"
+" xmlns:weld=\"http://jboss.org/schema/weld/beans\" \n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee http://docs.jboss.org/cdi/beans_1_0.xsd\n"
-" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">\n"
+" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd\">\n"
" \n"
-" <weld:scan>\n"
+" <weld:scan>\n"
" \n"
-" <!-- Don't deploy the classes for the swing app! -->\n"
-" <weld:exclude name="com.acme.swing.**" />\n"
+" <!-- Don't deploy the classes for the swing app! -->\n"
+" <weld:exclude name=\"com.acme.swing.**\" />\n"
" \n"
-" <!-- Don't include GWT support if GWT is not installed -->\n"
-" <weld:exclude name="com.acme.gwt.**">\n"
-" <weld:if-class-available name="!com.google.GWT"/>\n"
-" </weld:exclude>\n"
+" <!-- Don't include GWT support if GWT is not installed -->\n"
+" <weld:exclude name=\"com.acme.gwt.**\">\n"
+" <weld:if-class-available name=\"!com.google.GWT\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
+" <!--\n"
" Exclude classes which end in Blether if the system property verbosity is set to low\n"
" i.e.\n"
" java ... -Dverbosity=low \n"
-" --> \n"
-" <weld:exclude pattern="^(.*)Blether$">\n"
-" <weld:if-system-property name="verbosity" value="low"/>\n"
-" </weld:exclude>\n"
+" --> \n"
+" <weld:exclude pattern=\"^(.*)Blether$\">\n"
+" <weld:if-system-property name=\"verbosity\" value=\"low\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
-" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
+" <!--\n"
+" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
" property is not set\n"
-" -->\n"
-" <weld:exclude name="com.acme.jsf.**">\n"
-" <weld:if-class-available name="org.apahce.wicket.Wicket"/>\n"
-" <weld:if-system-property name="!viewlayer"/>\n"
-" </weld:exclude>\n"
-" </weld:scan>\n"
+" -->\n"
+" <weld:exclude name=\"com.acme.jsf.**\">\n"
+" <weld:if-class-available name=\"org.apahce.wicket.Wicket\"/>\n"
+" <weld:if-system-property name=\"!viewlayer\"/>\n"
+" </weld:exclude>\n"
+" </weld:scan>\n"
" \n"
-"</beans>"
+"</beans>"
msgstr ""
#. Tag: para
@@ -83,7 +83,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
+msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
msgstr ""
#. Tag: para
@@ -93,12 +93,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
+msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
+msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
msgstr ""
#. Tag: para
@@ -113,5 +113,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
+msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
msgstr ""
diff --git a/docs/reference/src/main/docbook/it-IT/contexts.po b/docs/reference/src/main/docbook/it-IT/contexts.po
index 998addb61d4..6503057daf1 100644
--- a/docs/reference/src/main/docbook/it-IT/contexts.po
+++ b/docs/reference/src/main/docbook/it-IT/contexts.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,17 +25,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld allows you to easiy manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivaed (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
+msgid "Weld allows you to easily manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivated (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and discociating the data store after calling activate."
+msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and dissociating the data store after calling activate."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld automatically controls context lifecycle in many scenarios such as Http Requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
+msgid "Weld automatically controls context lifecycle in many scenarios such as HTTP requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
msgstr ""
#. Tag: para
@@ -145,7 +145,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
+msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
msgstr ""
#. Tag: entry
@@ -245,12 +245,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implmentations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
+msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implementations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
+msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
msgstr ""
#. Tag: programlisting
@@ -263,14 +263,14 @@ msgid ""
" ...\n"
" \n"
" /* Start the request, providing a data store which will last the lifetime of the request */\n"
-" public void startRequest(Map<String, Object> requestDataStore) {\n"
+" public void startRequest(Map<String, Object> requestDataStore) {\n"
" // Associate the store with the context and acticate the context\n"
" requestContext.associate(requestDataStore);\n"
" requestContext.activate();\n"
" }\n"
" \n"
" /* End the request, providing the same data store as was used to start the request */\n"
-" public void endRequest(Map<String, Object> requestDataStore) {\n"
+" public void endRequest(Map<String, Object> requestDataStore) {\n"
" try {\n"
" /* Invalidate the request (all bean instances will be scheduled for destruction) */\n"
" requestContext.invalidate();\n"
@@ -290,7 +290,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's session contexts are "lazy" and don't require a session to actually exist until a bean instance must be written."
+msgid "Weld's session contexts are \"lazy\" and don't require a session to actually exist until a bean instance must be written."
msgstr ""
#. Tag: para
@@ -308,16 +308,16 @@ msgid ""
" /* Start a transient conversation */\n"
" /* Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */\n"
-" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" resumeOrStartConversation(requestDataStore, sessionDataStore, null);\n"
" }\n"
"\n"
" /* Start a transient conversation (if cid is null) or resume a non-transient */\n"
" /* conversation. Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */ \n"
-" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore, \n"
+" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore, \n"
" String cid) {\n"
" /* Associate the stores with the context and acticate the context */\n"
" * BoundRequest just wraps the two datastores */\n"
@@ -329,8 +329,8 @@ msgid ""
" /* End the conversations, providing the same data store as was used to start */\n"
" /* the request. Any transient conversations will be destroyed, any newly-promoted */\n"
" /* conversations will be placed into the session */\n"
-" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" try {\n"
" /* Invalidate the conversation (all transient conversations will be scheduled for destruction) */\n"
" conversationContext.invalidate();\n"
@@ -345,15 +345,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the containber), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
+msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the container), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the abilty to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
+msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the ability to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's conversations are not assigned ids until they become non-transient."
+msgid "Weld's conversations are not assigned ids until they become non-transient."
msgstr ""
diff --git a/docs/reference/src/main/docbook/it-IT/decorators.po b/docs/reference/src/main/docbook/it-IT/decorators.po
index 486cc2ef1ce..1baa18f47c8 100644
--- a/docs/reference/src/main/docbook/it-IT/decorators.po
+++ b/docs/reference/src/main/docbook/it-IT/decorators.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-07-17 18:52+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -21,13 +21,13 @@ msgstr "Decoratori"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
+msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
msgstr "Gli interceptor sono un potente modo per catturare e separare i concern (N.d.T. un concern è un particolare concetto o area di interesse) che sono ortogonali al sistema tipo. Qualsiasi interceptor è capace di intercettare le invocazioni di qualsiasi tipo Java. Questo li rende perfetti per risolvere concern tecnici quali gestione delle transazioni e la sicurezza. Comunque, per natura, gli interceptor non sono consapevoli dell'attuale semantica degli eventi che intercettano. Quindi gli interceptor non sono il giusto strumento per separare i concern di tipo business."
# ...concerns that cut across many disparate types = ?
#. Tag: para
#, fuzzy, no-c-format
-msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
+msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
msgstr "Il contrario è vero per i decoratori. Un decoratore intercetta le invocazioni solamente per una certa interfaccia Java, e quindi è consapevole della semantica legata a questa. Ciò rende i decoratori uno strumento perfetto per modellare alcuni tipi di concern di business. E significa pure che un decoratore non ha la generalità di un interceptor. I decoratori non sono capaci di risolvere i concern tecnici che agiscono per diversi tipi."
#. Tag: para
@@ -119,7 +119,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
+msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
msgstr "Diversamente dai semplici Web Beans, un decoratore può essere una classe astratta. Se un decoratore non ha niente da fare per un particolare metodo, allora non occorre implementare quel metodo."
#. Tag: para
@@ -208,14 +208,14 @@ msgid ""
" \n"
" public void withdraw(BigDecimal amount) {\n"
" account.withdraw(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedWithdrawl(amount) );\n"
" }\n"
" }\n"
" \n"
" public void deposit(BigDecimal amount);\n"
" account.deposit(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedDeposit(amount) );\n"
" }\n"
" }\n"
@@ -256,16 +256,16 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <decorators>\n"
-" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
-" </decorators>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <decorators>\n"
+" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
+" </decorators>\n"
+"</beans>"
msgstr ""
"<interceptors> declaration serves for interceptors:"
+msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
msgstr "Questa dichiarazione provvede per i decoratori alle stesse finalità di quanto la dichiarazione <interceptors> fa per gli interceptor."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/it-IT/ee.po b/docs/reference/src/main/docbook/it-IT/ee.po
index 85ae102c579..99e3564c3c3 100644
--- a/docs/reference/src/main/docbook/it-IT/ee.po
+++ b/docs/reference/src/main/docbook/it-IT/ee.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-23 21:16+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -56,7 +56,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
+msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
msgstr ""
#. Tag: para
@@ -81,7 +81,7 @@ msgstr "Iniettare risorse Java EE in un Web Bean"
#. Tag: para
#, fuzzy, no-c-format
-msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
+msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
msgstr "Tutti i Web Beans sia semplici che enterprise si avvantaggiano della dependency injection di Java EE usando @Resource, @EJB e @PersistenceContext. Abbiamo già visto un paio di esempi a riguardo, sebbene non ci siamo soffermati molto a suo tempo."
#. Tag: programlisting
@@ -135,7 +135,7 @@ msgstr "Chiamare un Web Bean da un servlet"
#. Tag: para
#, fuzzy, no-c-format
-msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
+msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
msgstr "E' facile utilizzare i Web Beans da un Servlet in Java EE 6. Semplicemente si inietti il Web Bean utilizzando l'injection del campo Web Bean o del metodo inizializzatore."
#. Tag: programlisting
@@ -148,14 +148,14 @@ msgid ""
" @Override\n"
" public void service(HttpServletRequest request, HttpServletResponse response)\n"
" throws ServletException, IOException {\n"
-" credentials.setUsername(request.getParameter("username")):\n"
-" credentials.setPassword(request.getParameter("password")):\n"
+" credentials.setUsername(request.getParameter(\"username\")):\n"
+" credentials.setPassword(request.getParameter(\"password\")):\n"
" login.login();\n"
" if ( login.isLoggedIn() ) {\n"
-" response.sendRedirect("/home.jsp");\n"
+" response.sendRedirect(\"/home.jsp\");\n"
" }\n"
" else {\n"
-" response.sendRedirect("/loginError.jsp");\n"
+" response.sendRedirect(\"/loginError.jsp\");\n"
" }\n"
" }\n"
" \n"
@@ -193,7 +193,7 @@ msgstr "Chiamare un Web Bean da un Message-Driven Bean"
#. Tag: para
#, no-c-format
-msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
+msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
msgstr ""
# Web Beans interceptor bindings =?
@@ -254,10 +254,10 @@ msgstr ""
#, fuzzy, no-c-format
msgid ""
"public class OrderResources {\n"
-" @Resource(name="jms/ConnectionFactory")\n"
+" @Resource(name=\"jms/ConnectionFactory\")\n"
" private ConnectionFactory connectionFactory;\n"
" \n"
-" @Resource(name="jms/OrderQueue")\n"
+" @Resource(name=\"jms/OrderQueue\")\n"
" private Queue orderQueue;\n"
" \n"
" @Produces @OrderConnection\n"
@@ -347,7 +347,7 @@ msgid ""
"\n"
"public void sendMessage() {\n"
" MapMessage msg = orderSession.createMapMessage();\n"
-" msg.setLong("orderId", order.getId());\n"
+" msg.setLong(\"orderId\", order.getId());\n"
" ...\n"
" producer.send(msg);\n"
"}"
@@ -375,7 +375,7 @@ msgstr "Packaging and deployment"
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a "bean archive". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
+msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a \"bean archive\". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml 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 web-beans.xml nella directory META-INF o WEB-INF. Il file può essere vuoto. I Web Beans collocati negli archivi che non hanno un file web-beans.xml non saranno disponibili per l'uso nell'applicazione."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/it-IT/environments.po b/docs/reference/src/main/docbook/it-IT/environments.po
index a8065328015..13539059644 100644
--- a/docs/reference/src/main/docbook/it-IT/environments.po
+++ b/docs/reference/src/main/docbook/it-IT/environments.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-23 21:17+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -56,12 +56,12 @@ msgstr "Web Beans può essere usato in ogni Servlet container come Tomcat 6.0 o
#. Tag: para
#, fuzzy, no-c-format
-msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
+msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
msgstr "Web Beans non supporta il deploy di session bean, l'injection usando @EJB, o @PersistenceContext o l'uso di eventi transazionali nei Servlet container."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an "uber-jar", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
+msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an \"uber-jar\", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
msgstr "Web Beans dovrebbe essere usata come libreria per web application in un servlet container. Si dovrebbe mettere webbeans-servlet.jar in WEB-INF/lib. webbeans-servlet.jar è un \"sovra-jar\" fornito per comodità. Invece, è possibile usare i suoi jar componenti:"
#. Tag: para
@@ -72,9 +72,9 @@ msgstr "Occorre esplicitamente specificare il servlet listener (usato per avviar
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
"\n"
" org.jboss.weld.environment.servlet.Listener\n"
@@ -87,18 +87,18 @@ msgstr "Tomcat"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
+msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
msgstr "Tomcat ha un JNDI read-only, e quindi Web Beans non può automaticamente associare il Manager. Per associare il Manager a JNDI occorre popolare META-INF/context.xml con i seguenti contesti:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<Context>\n"
-" <Resource name="BeanManager" \n"
-" auth="Container"\n"
-" type="javax.enterprise.inject.spi.BeanManager"\n"
-" factory="org.jboss.weld.resources.ManagerObjectFactory"/>\n"
-"</Context>"
+"<Context>\n"
+" <Resource name=\"BeanManager\" \n"
+" auth=\"Container\"\n"
+" type=\"javax.enterprise.inject.spi.BeanManager\"\n"
+" factory=\"org.jboss.weld.resources.ManagerObjectFactory\"/>\n"
+"</Context>"
msgstr ""
"\n"
" \n"
" BeanManager\n"
@@ -146,27 +146,27 @@ msgstr "Jetty"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
+msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
msgstr "Come Tomcat, Jetty ha un JNDI read-only, e quindi Web Beans non può automaticamente associare il Manager. Per associare il Manager a JNDI occorre popolare META-INF/jetty-env.xml con i seguenti contesti:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.mortbay.jetty.plus.naming.Resource">\n"
-" <Arg><Ref id="webAppCtx"/></Arg> \n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.mortbay.jetty.plus.naming.Resource\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg> \n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure>"
msgstr ""
"\n"
@@ -192,22 +192,22 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://www.eclipse.org/jetty/configure.dtd">\n"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://www.eclipse.org/jetty/configure.dtd\">\n"
"\n"
-"<Configure id="webAppCtx" class="org.eclipse.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.eclipse.jetty.plus.jndi.Resource">\n"
-" <Arg> <Ref id="webAppCtx"/> </Arg>\n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure> "
+"<Configure id=\"webAppCtx\" class=\"org.eclipse.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.eclipse.jetty.plus.jndi.Resource\">\n"
+" <Arg> <Ref id=\"webAppCtx\"/> </Arg>\n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure> "
msgstr ""
"\n"
@@ -232,7 +232,7 @@ msgstr "e renderlo disponibile nel proprio deploy aggiungendo questo in fondo a
#. Tag: para
#, fuzzy, no-c-format
-msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
+msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
msgstr "Si noti che Jetty non ha un supporto predefinito per javax.naming.spi.ObjectFactory come Tomcat, quindi è necessario creare manualmente il javax.naming.Reference con cui fare il wrap."
#. Tag: para
@@ -242,19 +242,19 @@ msgstr "Jetty consente solo di associare le entry a java:comp/envMETA-INF/jetty-web.xml with the following content to your war:"
+msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file WEB-INF/jetty-web.xml with the following content to your war:"
msgstr "Web Beans supporta anche l'iniezione dei servlet in Tomcat. Per abilitarla, collocare webbeans-tomcat-support.jar in $TOMCAT_HOME/lib, ed aggiungere il seguente codice a META-INF/context.xml:"
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <Call class="org.jboss.weld.environment.jetty.WeldServletHandler" name="process">\n"
-" <Arg><Ref id="webAppCtx"/></Arg>\n"
-" </Call>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <Call class=\"org.jboss.weld.environment.jetty.WeldServletHandler\" name=\"process\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg>\n"
+" </Call>\n"
+"</Configure>"
msgstr ""
#. Tag: title
@@ -264,7 +264,7 @@ msgstr "Java SE"
#. Tag: para
#, fuzzy, no-c-format
-msgid "In addition to improved integration of the Enterprise Java stack, the "Contexts and Dependency Injection for the Java EE platform" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
+msgid "In addition to improved integration of the Enterprise Java stack, the \"Contexts and Dependency Injection for the Java EE platform\" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
msgstr "Oltre alla migliorata integrazione dello stack Java Enterprise, Web Beans fornisce anche uno stato dell'arte typesafe, con dependency injection stateful . Questo è utile in un ampio raggio di applicazioni tipo, enterprise o altre. Per facilitare ciò, Web Beans fornisce semplici mezzi per eseguire in ambiente Java Standard Edition indipendentemente da qualsiasi caratteristica Enterprise Edition."
#. Tag: para
@@ -324,7 +324,7 @@ msgstr "Per semplificare la vita agli sviluppatori Web Beans fornisce un modulo
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Parameters List<String> params;"
+msgid "@Inject @Parameters List<String> params;"
msgstr ""
#. Tag: programlisting
@@ -344,7 +344,7 @@ msgstr "I parametri da linea di comando non sono disponibili per l'injection fin
#. Tag: para
#, fuzzy, no-c-format
-msgid "Here's an example of a simple CDI SE application:"
+msgid "Here's an example of a simple CDI SE application:"
msgstr "Ecco un esempio di una semplice applicazione Web Beans SE:"
#. Tag: programlisting
@@ -353,8 +353,8 @@ msgid ""
"@Singleton\n"
"public class HelloWorld\n"
"{\n"
-" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
-" System.out.println("Hello " + parameters.get(0));\n"
+" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
+" System.out.println(\"Hello \" + parameters.get(0));\n"
" }\n"
"}"
msgstr ""
@@ -385,7 +385,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
+msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
msgstr ""
#. Tag: para
@@ -395,17 +395,17 @@ msgstr "Le applicazioni Web Beans SE vengono avviate eseguendo il seguente metod
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "java org.jboss.weld.environment.se.StartMain <args>"
+msgid "java org.jboss.weld.environment.se.StartMain <args>"
msgstr "]]>"
#. Tag: title
#, no-c-format
-msgid "Programatic Bootstrap API"
+msgid "Programmatic Bootstrap API"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
+msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
msgstr ""
#. Tag: programlisting
@@ -431,10 +431,10 @@ msgid ""
"{\n"
"\n"
" /** Provides access to all beans within the application. */\n"
-" public Instance<Object> instance() {...}\n"
+" public Instance<Object> instance() {...}\n"
"\n"
" /** Provides access to all events within the application. */\n"
-" public Event<Object> event() {...}\n"
+" public Event<Object> event() {...}\n"
"\n"
" /** Provides direct access to the BeanManager. */\n"
" public BeanManager getBeanManager() {...}\n"
@@ -444,7 +444,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
+msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
msgstr ""
#. Tag: programlisting
@@ -484,22 +484,22 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
+msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans>\n"
-" <decorators>\n"
-" <decorator>org.jboss.weld.environment.se.threading.RunnableDecorator</decorator>\n"
-" </decorator>\n"
-"</beans>"
+"<beans>\n"
+" <decorators>\n"
+" <class>org.jboss.weld.environment.se.threading.RunnableDecorator</class>\n"
+" </decorator>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situtations where you would otherwise have used ThreadLocal directly, which are typically rare."
+msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situations where you would otherwise have used ThreadLocal directly, which are typically rare."
msgstr ""
#. Tag: title
@@ -509,7 +509,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
+msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/it-IT/events.po b/docs/reference/src/main/docbook/it-IT/events.po
index 5599cf3ea5c..f86d6fc9ea4 100644
--- a/docs/reference/src/main/docbook/it-IT/events.po
+++ b/docs/reference/src/main/docbook/it-IT/events.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-23 21:18+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -36,7 +36,7 @@ msgstr "non solo i produttori di eventi sono disaccoppiati dagli osservatori; gl
#. Tag: para
#, fuzzy, no-c-format
-msgid "observers can specify a combination of "selectors" to narrow the set of event notifications they will receive, and"
+msgid "observers can specify a combination of \"selectors\" to narrow the set of event notifications they will receive, and"
msgstr "gli osservatori possono specificare una combinazione di \"selettori\" per restringere il set di notifiche di eventi da ricevere, e"
#. Tag: para
@@ -46,7 +46,7 @@ msgstr "gli osservatori possono essere notificati immediatamente, o possono spec
#. Tag: para
#, no-c-format
-msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
+msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
msgstr ""
#. Tag: title
@@ -61,7 +61,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
+msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
msgstr ""
#. Tag: programlisting
@@ -104,7 +104,7 @@ msgstr "only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
+msgid "An observer method need not specify any event qualifiers—in this case it is interested in only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
msgstr "Un metodo osservatore non ha bisogno di specificare alcun binding di evento in questo caso è interessato a tutti 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
@@ -129,7 +129,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Event<Document> documentEvent;"
+msgid "@Inject @Any Event<Document> documentEvent;"
msgstr " documentEvent;]]>"
#. Tag: para
@@ -184,7 +184,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
+msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
msgstr " documentUpdatedEvent;]]>"
#. Tag: para
@@ -204,12 +204,12 @@ msgstr "non specifica alcun event binding tranne per gli ev
#. Tag: para
#, no-c-format
-msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
+msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
+msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
msgstr "(){}).fire(document);]]>"
#. Tag: para
@@ -224,7 +224,7 @@ msgstr "Osservatori transazionali"
#. Tag: para
#, no-c-format
-msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
+msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
msgstr ""
#. Tag: para
@@ -286,7 +286,7 @@ msgstr "I membri del tipo di eventbinding possono essere specificati staticament
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
+msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
msgstr " loggedInEvent;]]>"
#. Tag: para
@@ -298,7 +298,7 @@ msgstr "Alternativamente il valore del membro del tipo di event binding può ess
#, fuzzy, no-c-format
msgid ""
"abstract class RoleBinding \n"
-" extends AnnotationLiteral<Role> \n"
+" extends AnnotationLiteral<Role> \n"
" implements Role {}"
msgstr ""
" blogEvent;\n"
"...\n"
@@ -445,12 +445,12 @@ msgid ""
"\n"
" @PersistenceContext EntityManager em;\n"
" \n"
-" List<Product> products;\n"
+" List<Product> products;\n"
"\n"
" @Produces @Catalog \n"
-" List<Product> getCatalog() {\n"
+" List<Product> getCatalog() {\n"
" if (products==null) {\n"
-" products = em.createQuery("select p from Product p where p.deleted = false")\n"
+" products = em.createQuery(\"select p from Product p where p.deleted = false\")\n"
" .getResultList();\n"
" }\n"
" return products;\n"
@@ -492,16 +492,16 @@ msgid ""
"@Stateless\n"
"public class ProductManager {\n"
" @PersistenceContext EntityManager em;\n"
-" @Inject @Any Event<Product> productEvent;\n"
+" @Inject @Any Event<Product> productEvent;\n"
"\n"
" public void delete(Product product) {\n"
" em.delete(product);\n"
-" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
" }\n"
" \n"
" public void persist(Product product) {\n"
" em.persist(product);\n"
-" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
" }\n"
" ...\n"
"}"
diff --git a/docs/reference/src/main/docbook/it-IT/example.po b/docs/reference/src/main/docbook/it-IT/example.po
index 06c417e6519..f3f3cd6dd2a 100644
--- a/docs/reference/src/main/docbook/it-IT/example.po
+++ b/docs/reference/src/main/docbook/it-IT/example.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-23 21:19+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "Esempio di applicazione web JSF"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
+msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
msgstr "Illustriamo queste idee con un esempio completo. Implementiamo il login/logout dell'utente per un'applicazione che utilizza JSF. Innanzitutto definiamo un Web Bean che mantenga username e password digitati durante il login:"
#. Tag: programlisting
@@ -61,18 +61,18 @@ msgstr "Questo Web Bean è associato al login all'interno della seguente form JS
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:form>\n"
-" <h:panelGrid columns="2" rendered="#{!login.loggedIn}">\n"
-" <f:validateBean>\n"
-" <h:outputLabel for="username">Username:</h:outputLabel>\n"
-" <h:inputText id="username" value="#{credentials.username}"/>\n"
-" <h:outputLabel for="password">Password:</h:outputLabel>\n"
-" <h:inputSecret id="password" value="#{credentials.password}"/>\n"
-" </f:validateBean>\n"
-" </h:panelGrid>\n"
-" <h:commandButton value="Login" action="#{login.login}" rendered="#{!login.loggedIn}"/>\n"
-" <h:commandButton value="Logout" action="#{login.logout}" rendered="#{login.loggedIn}"/>\n"
-"</h:form>"
+"<h:form>\n"
+" <h:panelGrid columns=\"2\" rendered=\"#{!login.loggedIn}\">\n"
+" <f:validateBean>\n"
+" <h:outputLabel for=\"username\">Username:</h:outputLabel>\n"
+" <h:inputText id=\"username\" value=\"#{credentials.username}\"/>\n"
+" <h:outputLabel for=\"password\">Password:</h:outputLabel>\n"
+" <h:inputSecret id=\"password\" value=\"#{credentials.password}\"/>\n"
+" </f:validateBean>\n"
+" </h:panelGrid>\n"
+" <h:commandButton value=\"Login\" action=\"#{login.login}\" rendered=\"#{!login.loggedIn}\"/>\n"
+" <h:commandButton value=\"Logout\" action=\"#{login.logout}\" rendered=\"#{login.loggedIn}\"/>\n"
+"</h:form>"
msgstr ""
"\n"
" \n"
@@ -117,7 +117,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
+msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
msgstr ""
#. Tag: para
@@ -137,10 +137,10 @@ msgid ""
" private User user;\n"
" \n"
" public void login() {\n"
-" List<User> results = userDatabase.createQuery(\n"
-" "select u from User u where u.username = :username and u.password = :password")\n"
-" .setParameter("username", credentials.getUsername())\n"
-" .setParameter("password", credentials.getPassword())\n"
+" List<User> results = userDatabase.createQuery(\n"
+" \"select u from User u where u.username = :username and u.password = :password\")\n"
+" .setParameter(\"username\", credentials.getUsername())\n"
+" .setParameter(\"password\", credentials.getPassword())\n"
" .getResultList();\n"
" \n"
" if (!results.isEmpty()) {\n"
@@ -288,9 +288,9 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:panelGroup rendered="#{login.loggedIn}">\n"
+"<h:panelGroup rendered=\"#{login.loggedIn}\">\n"
" signed in as #{currentUser.username}\n"
-"</h:panelGroup>"
+"</h:panelGroup>"
msgstr ""
"\n"
" signed in as #{currentUser.username}\n"
@@ -298,7 +298,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
+msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
msgstr "Quest'esempio è un assaggio del modello di programmazione con Web Bean. Nel prossimo capitolo esploreremo la dependency injection dei Web Bean con maggior profondità."
#~ msgid "Of course, @LoggedIn is a binding annotation:"
diff --git a/docs/reference/src/main/docbook/it-IT/extend.po b/docs/reference/src/main/docbook/it-IT/extend.po
index 7220ee4befd..8ce5edf43ce 100644
--- a/docs/reference/src/main/docbook/it-IT/extend.po
+++ b/docs/reference/src/main/docbook/it-IT/extend.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-20 16:41+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -76,7 +76,7 @@ msgstr "La classe Bean"
#. Tag: para
#, no-c-format
-msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
+msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
msgstr ""
#. Tag: programlisting
@@ -164,15 +164,15 @@ msgid ""
"class MyExtension implements Extension {\n"
" \n"
" void beforeBeanDiscovery(@Observes BeforeBeanDiscovery bbd) {\n"
-" Logger.global.debug("beginning the scanning process");\n"
+" Logger.global.debug(\"beginning the scanning process\");\n"
" }\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
-" Logger.global.debug("scanning type: " + pat.getAnnotatedType().getJavaClass().getName());\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" Logger.global.debug(\"scanning type: \" + pat.getAnnotatedType().getJavaClass().getName());\n"
" } \n"
"\n"
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd) {\n"
-" Logger.global.debug("finished the scanning process");\n"
+" Logger.global.debug(\"finished the scanning process\");\n"
" }\n"
" \n"
"}"
@@ -180,7 +180,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
+msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
msgstr ""
#. Tag: programlisting
@@ -188,7 +188,7 @@ msgstr ""
msgid ""
"class MyExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" //tell the container to ignore the type if it is annotated @Ignore\n"
" if ( pat.getAnnotatedType().isAnnotionPresent(Ignore.class) ) pat.veto(); \n"
" } \n"
@@ -203,7 +203,7 @@ msgstr "Il nervo centrale per l'estensione di Web Beans è l'oggetto Ma
#. Tag: programlisting
#, no-c-format
-msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
+msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
msgstr ""
#. Tag: title
@@ -220,31 +220,31 @@ msgstr "L'interfaccia Manager consente di registrare ed otten
#, no-c-format
msgid ""
"public interface BeanManager {\n"
-" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
-" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
-" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
-" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
-" public Set<Bean<?>> getBeans(String name);\n"
-" public Bean<?> getPassivationCapableBean(String id);\n"
-" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
+" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
+" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
+" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
+" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
+" public Set<Bean<?>> getBeans(String name);\n"
+" public Bean<?> getPassivationCapableBean(String id);\n"
+" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
" public void validate(InjectionPoint injectionPoint);\n"
" public void fireEvent(Object event, Annotation... qualifiers);\n"
-" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
-" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
-" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
-" public boolean isScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
-" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
-" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
-" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
-" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
-" public Context getContext(Class<? extends Annotation> scopeType);\n"
+" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
+" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
+" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
+" public boolean isScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
+" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
+" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
+" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
+" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
+" public Context getContext(Class<? extends Annotation> scopeType);\n"
" public ELResolver getELResolver();\n"
" public ExpressionFactory wrapExpressionFactory(ExpressionFactory expressionFactory);\n"
-" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
-" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
+" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
+" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
"}"
msgstr ""
@@ -265,7 +265,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's study some of the interfaces exposed by the BeanManager."
+msgid "Let's study some of the interfaces exposed by the BeanManager."
msgstr "Il nervo centrale per l'estensione di Web Beans è l'oggetto Manager."
#. Tag: title
@@ -280,21 +280,21 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to instatiate the object itself, and so only method and field injection will be supported."
+msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to insntatiate the object itself, and so only method and field injection will be supported."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"//get the BeanManager from JNDI\n"
-"BeanManager beanManager = (BeanManager) new InitialContext().lookup("java:comp/BeanManager");\n"
+"BeanManager beanManager = (BeanManager) new InitialContext().lookup(\"java:comp/BeanManager\");\n"
"\n"
"//CDI uses an AnnotatedType object to read the annotations of a class\n"
-"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
+"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
"\n"
"//The extension uses an InjectionTarget to delegate instantiation, dependency injection \n"
"//and lifecycle callbacks to the CDI container\n"
-"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
+"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
"\n"
"//each instance needs its own CDI CreationalContext\n"
"CreationalContext ctx = beanManager.createCreationalContext(null);\n"
@@ -324,33 +324,33 @@ msgstr "Istanze della classe astratta Bean rappresentano i We
#. Tag: para
#, no-c-format
-msgid "The Bean interface exposes all the interesting things we dicussed in ."
+msgid "The Bean interface exposes all the interesting things we discussed in ."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"public interface Bean<T> extends Contextual<T> {\n"
-" public Set<Type> getTypes();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Class<? extends Annotation> getScope();\n"
+"public interface Bean<T> extends Contextual<T> {\n"
+" public Set<Type> getTypes();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Class<? extends Annotation> getScope();\n"
" public String getName();\n"
-" public Set<Class<? extends Annotation>> getStereotypes();\n"
-" public Class<?> getBeanClass();\n"
+" public Set<Class<? extends Annotation>> getStereotypes();\n"
+" public Class<?> getBeanClass();\n"
" public boolean isAlternative();\n"
" public boolean isNullable();\n"
-" public Set<InjectionPoint> getInjectionPoints();\n"
+" public Set<InjectionPoint> getInjectionPoints();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's an easy way to find out what beans exist in the application:"
+msgid "There's an easy way to find out what beans exist in the application:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
+msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
msgstr ""
#. Tag: para
@@ -370,7 +370,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
+msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
msgstr ""
#. Tag: programlisting
@@ -381,49 +381,49 @@ msgid ""
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd, BeanManager bm) {\n"
" \n"
" //use this to read annotations of the class\n"
-" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
+" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
"\n"
" //use this to instantiate the class and inject dependencies\n"
-" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
+" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
"\n"
-" abd.addBean( new Bean<SecurityManager>() {\n"
+" abd.addBean( new Bean<SecurityManager>() {\n"
"\n"
" @Override\n"
-" public Class<?> getBeanClass() {\n"
+" public Class<?> getBeanClass() {\n"
" return SecurityManager.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
" public String getName() {\n"
-" return "securityManager";\n"
+" return \"securityManager\";\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getQualifiers() {\n"
-" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
-" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
-" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
+" public Set<Annotation> getQualifiers() {\n"
+" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
+" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
+" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
" return qualifiers;\n"
" }\n"
"\n"
" @Override\n"
-" public Class<? extends Annotation> getScope() {\n"
+" public Class<? extends Annotation> getScope() {\n"
" return SessionScoped.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Class<? extends Annotation>> getStereotypes() {\n"
+" public Set<Class<? extends Annotation>> getStereotypes() {\n"
" return Collections.emptySet();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypes() {\n"
-" Set<Type> types = new HashSet<Type>();\n"
+" public Set<Type> getTypes() {\n"
+" Set<Type> types = new HashSet<Type>();\n"
" types.add(SecurityManager.class);\n"
" types.add(Object.class);\n"
" return types;\n"
@@ -440,7 +440,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
+" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
" SecurityManager instance = it.produce(ctx);\n"
" it.inject(instance, ctx);\n"
" it.postConstruct(instance);\n"
@@ -449,7 +449,7 @@ msgid ""
"\n"
" @Override\n"
" public void destroy(SecurityManager instance, \n"
-" CreationalContext<SecurityManager> ctx) {\n"
+" CreationalContext<SecurityManager> ctx) {\n"
" it.preDestroy(instance);\n"
" it.dispose(instance);\n"
" ctx.release();\n"
@@ -478,7 +478,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
+msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
msgstr ""
#. Tag: programlisting
@@ -486,38 +486,38 @@ msgstr ""
msgid ""
"public class QualifiedNameExtension implements Extension {\n"
"\n"
-" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
+" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
"\n"
" //wrap this to override the annotations of the class\n"
-" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
+" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
" \n"
-" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
+" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
"\n"
" @Override\n"
-" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
+" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
" return at.getConstructors();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedField<? super X>> getFields() {\n"
+" public Set<AnnotatedField<? super X>> getFields() {\n"
" return at.getFields();\n"
" }\n"
"\n"
" @Override\n"
-" public Class<X> getJavaClass() {\n"
+" public Class<X> getJavaClass() {\n"
" return at.getJavaClass();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
+" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
" return at.getMethods();\n"
" }\n"
"\n"
" @Override\n"
-" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
+" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
" if ( Named.class.equals(annType) ) {\n"
" class NamedLiteral \n"
-" extends AnnotationLiteral<Named> \n"
+" extends AnnotationLiteral<Named> \n"
" implements Named {\n"
" @Override\n"
" public String value() {\n"
@@ -526,7 +526,7 @@ msgid ""
" final String qualifiedName;\n"
" if ( pkg.isAnnotationPresent(Named.class) ) {\n"
" qualifiedName = pkg.getAnnotation(Named.class).value() \n"
-" + '.' + unqualifiedName;\n"
+" + '.' + unqualifiedName;\n"
" }\n"
" else {\n"
" qualifiedName = unqualifiedName;\n"
@@ -542,7 +542,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getAnnotations() {\n"
+" public Set<Annotation> getAnnotations() {\n"
" return at.getAnnotations();\n"
" }\n"
"\n"
@@ -552,12 +552,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypeClosure() {\n"
+" public Set<Type> getTypeClosure() {\n"
" return at.getTypeClosure();\n"
" }\n"
"\n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
" return at.isAnnotationPresent(annType);\n"
" }\n"
" \n"
@@ -571,7 +571,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
+msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
msgstr ""
#. Tag: programlisting
@@ -579,17 +579,17 @@ msgstr ""
msgid ""
"class ServiceAlternativeExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" \n"
-" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
+" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
" \n"
" if ( Service.class.isAssignableFrom( type.getJavaClass() ) ) {\n"
" \n"
" //if the class implements Service, make it an @Alternative\n"
-" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
+" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
" \n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
" return annotationType.equals(Alternative.class) ? \n"
" true : type.isAnnotationPresent(annotationType);\n"
" }\n"
@@ -622,7 +622,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
+msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
msgstr ""
#. Tag: programlisting
@@ -642,25 +642,25 @@ msgstr ""
msgid ""
"public class ConfigExtension implements Extension {\n"
"\n"
-"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
+"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
"\t\t\n"
"\t\t//wrap this to intercept the component lifecycle\n"
-"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
+"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
"\t \n"
-" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
+" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
" \n"
" //use this to read annotations of the class and its members\n"
-" AnnotatedType<X> at = pit.getAnnotatedType();\n"
+" AnnotatedType<X> at = pit.getAnnotatedType();\n"
" \n"
" //read the properties file\n"
-" String propsFileName = at.getClass().getSimpleName() + ".properties";\n"
+" String propsFileName = at.getClass().getSimpleName() + \".properties\";\n"
" InputStream stream = at.getJavaClass().getResourceAsStream(propsFileName);\n"
" if (stream!=null) {\n"
" \n"
" try {\n"
" Properties props = new Properties();\n"
" props.load(stream);\n"
-" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
+" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
" String fieldName = property.getKey().toString();\n"
" Object value = property.getValue();\n"
" try {\n"
@@ -672,7 +672,7 @@ msgid ""
" else {\n"
" //TODO: do type conversion automatically\n"
" pit.addDefinitionError( new InjectionException(\n"
-" "field is not of type String: " + field ) );\n"
+" \"field is not of type String: \" + field ) );\n"
" }\n"
" }\n"
" catch (NoSuchFieldException nsfe) {\n"
@@ -688,14 +688,14 @@ msgid ""
" }\n"
" }\n"
" \n"
-" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
+" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
"\n"
" @Override\n"
-" public void inject(X instance, CreationalContext<X> ctx) {\n"
+" public void inject(X instance, CreationalContext<X> ctx) {\n"
" it.inject(instance, ctx);\n"
" \n"
" //set the values onto the new instance of the component\n"
-" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
+" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
" try {\n"
" configuredValue.getKey().set(instance, configuredValue.getValue());\n"
" }\n"
@@ -721,12 +721,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
-" public X produce(CreationalContext<X> ctx) {\n"
+" public X produce(CreationalContext<X> ctx) {\n"
" return it.produce(ctx);\n"
" }\n"
" \n"
@@ -741,7 +741,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
+msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
msgstr ""
#. Tag: title
@@ -758,9 +758,9 @@ msgstr "L'interfaccia Context supporta l'aggiunta di nuovi sc
#, fuzzy, no-c-format
msgid ""
"public interface Context {\n"
-" public Class<? extends Annotation> getScope();\n"
-" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
-" public <T> T get(Contextual<T> contextual);\n"
+" public Class<? extends Annotation> getScope();\n"
+" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
+" public <T> T get(Contextual<T> contextual);\n"
" boolean isActive();\n"
"}"
msgstr ""
diff --git a/docs/reference/src/main/docbook/it-IT/gettingstarted.po b/docs/reference/src/main/docbook/it-IT/gettingstarted.po
index 76df928aa4e..674a1f66b8c 100644
--- a/docs/reference/src/main/docbook/it-IT/gettingstarted.po
+++ b/docs/reference/src/main/docbook/it-IT/gettingstarted.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-06-08 21:39+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, Glassfish 3.0 or any compliant Java EE 6 container."
+msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, GlassFish 3.0 or any compliant Java EE 6 container."
msgstr ""
#. Tag: para
@@ -36,7 +36,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To run the examples with the provided build scripts, you'll need the following:"
+msgid "To run the examples with the provided build scripts, you'll need the following:"
msgstr ""
#. Tag: para
@@ -81,12 +81,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
+msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
+msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
msgstr ""
#. Tag: para
@@ -96,7 +96,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
+msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
msgstr ""
#. Tag: title
@@ -106,19 +106,19 @@ msgstr "Usare JBoss AS 5"
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
+msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
+msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> unzip jboss-6.0.*.zip\n"
-"$> mv jboss-6.0.*/ jboss-as-6.0"
+"$> unzip jboss-6.0.*.zip\n"
+"$> mv jboss-6.0.*/ jboss-as-6.0"
msgstr ""
#. Tag: para
@@ -133,7 +133,7 @@ msgstr "jboss.home=/Applications/jboss-5.0.1.GA"
#. Tag: para
#, fuzzy, no-c-format
-msgid "You're now ready to deploy your first example!"
+msgid "You're now ready to deploy your first example!"
msgstr "Ora, siete pronti a fare il deploy del primo esempio!"
#. Tag: para
@@ -144,22 +144,22 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant deploy"
msgstr ""
"$ cd examples/numberguess\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
+msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/jboss-as-6.0\n"
-"$> ./bin/run.sh"
+"$> cd /path/to/jboss-as-6.0\n"
+"$> ./bin/run.sh"
msgstr "$ /Application/jboss-5.0.0.GA/bin/run.sh"
#. Tag: para
@@ -168,11 +168,11 @@ msgid "a Windows command window:"
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
-"$> run"
-msgstr ""
+"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
+"$> run"
+msgstr "$ /Application/jboss-5.0.0.GA/bin/run.sh"
#. Tag: para
#, no-c-format
@@ -227,20 +227,20 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/translator\n"
-"$> ant deploy"
+"$> cd examples/jsf/translator\n"
+"$> ant deploy"
msgstr ""
"$ cd examples/translator\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
+msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
+msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
msgstr "Qua viene impostato il context path, in modo da avere un url gradevole (http://localhost:8080/webbeans-translator)."
#. Tag: title
@@ -250,41 +250,43 @@ msgstr "Usare GlassFish"
#. Tag: para
#, no-c-format
-msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
+msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
+msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> chmod 755 glassfish-v3-unix.sh\n"
-"$> ./glassfish-v3-unix.sh"
+"$> chmod 755 glassfish-v3-unix.sh\n"
+"$> ./glassfish-v3-unix.sh"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
+msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
+msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
-"$> ant package"
+"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
+"$> ant package"
msgstr ""
+"$ cd examples/numberguess\n"
+"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
+msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
msgstr ""
#. Tag: para
@@ -294,12 +296,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin start-domain domain1"
+msgid "$> asadmin start-domain domain1"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on "Applications", then click on the "Deploy..." button under the heading "Applications" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
+msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on \"Applications\", then click on the \"Deploy...\" button under the heading \"Applications\" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
msgstr ""
#. Tag: para
@@ -309,7 +311,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin deploy target/weld-numberguess.war"
+msgid "$> asadmin deploy target/weld-numberguess.war"
msgstr ""
#. Tag: para
@@ -329,24 +331,24 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
+msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
+msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
msgstr "Scaricare Tomcat 6.0.18 o successivo da tomcat.apache.org, e scompattarlo. Per esempio"
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "$> unzip apache-tomcat-6.0.18.zip"
+msgid "$> unzip apache-tomcat-6.0.18.zip"
msgstr ""
""
#. Tag: para
#, no-c-format
-msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
+msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
msgstr ""
#. Tag: title
@@ -356,7 +358,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
+msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
msgstr ""
#. Tag: programlisting
@@ -366,7 +368,7 @@ msgstr "tomcat.home=/Applications/apache-tomcat-6.0.18"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now you're ready to deploy the numberguess example to Tomcat!"
+msgid "Now you're ready to deploy the numberguess example to Tomcat!"
msgstr "Per eseguire il deploy dell'esempio Indovina Numero per tomcat:"
#. Tag: para
@@ -377,15 +379,15 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant tomcat.deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant tomcat.deploy"
msgstr ""
"$ cd examples/numberguess\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with "tomcat."."
+msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with \"tomcat.\"."
msgstr ""
#. Tag: para
@@ -410,21 +412,21 @@ msgstr "ant undeploy - rimuove l'esempio dal server"
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
+msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/apache-tomcat-6\n"
-"$> ./bin/start.sh"
+"$> cd /path/to/apache-tomcat-6\n"
+"$> ./bin/start.sh"
msgstr "$ /Applications/apache-tomcat-6.0.18/bin/startup.sh"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
-"$> start"
+"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
+"$> start"
msgstr ""
""
@@ -441,12 +443,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
+msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
+msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
msgstr ""
#. Tag: para
@@ -456,7 +458,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<user username="admin" password="" roles="manager"/>"
+msgid "<user username=\"admin\" password=\"\" roles=\"manager\"/>"
msgstr ""
#. Tag: para
@@ -466,7 +468,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
+msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
msgstr ""
#. Tag: para
@@ -476,7 +478,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn tomcat:redeploy -Ptomcat"
+msgid "$> mvn tomcat:redeploy -Ptomcat"
msgstr ""
#. Tag: para
@@ -491,7 +493,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace tomcat:run -Ptomcat"
+msgid "$> mvn war:inplace tomcat:run -Ptomcat"
msgstr ""
#. Tag: para
@@ -501,12 +503,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Ptomcat"
+msgid "$> mvn compile war:inplace -Ptomcat"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
+msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
msgstr ""
#. Tag: title
@@ -521,12 +523,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
+msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
+msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
msgstr ""
#. Tag: para
@@ -537,8 +539,8 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> mvn war:inplace jetty:run -Pjetty"
+"$> cd examples/jsf/numberguess\n"
+"$> mvn war:inplace jetty:run -Pjetty"
msgstr ""
""
@@ -555,7 +557,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Pjetty"
+msgid "$> mvn compile war:inplace -Pjetty"
msgstr ""
#. Tag: para
@@ -565,7 +567,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclispe[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
+msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclipse[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
msgstr ""
#. Tag: para
@@ -575,7 +577,7 @@ msgstr "Creazione di un progetto Eclipse"
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
+msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
msgstr ""
#. Tag: para
@@ -585,12 +587,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace -Pjetty-ide"
+msgid "$> mvn war:inplace -Pjetty-ide"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using "Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
+msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using \"Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/it-IT/injection.po b/docs/reference/src/main/docbook/it-IT/injection.po
index e5b6559b842..8713f6cb3a7 100644
--- a/docs/reference/src/main/docbook/it-IT/injection.po
+++ b/docs/reference/src/main/docbook/it-IT/injection.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-24 19:22+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "Dependency injection"
#. Tag: para
#, no-c-format
-msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
+msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
msgstr ""
#. Tag: title
@@ -148,7 +148,7 @@ msgstr "Quindi, il Web Bean manager inizializza i valori di tutti i campi del We
#. Tag: para
#, fuzzy, no-c-format
-msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
+msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
msgstr "Quindi, il Web Bean manager chiama tutti i metodi inizializzatori del Web Bean."
#. Tag: para
@@ -184,7 +184,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
+msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
msgstr ""
#. Tag: title
@@ -196,7 +196,7 @@ msgstr ""
# il che significa?
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
+msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
msgstr "Le specifiche Web Beans definiscono una procedura, chiamata typesafe resolution algorithm (algoritmo di risoluzione sicura rispetto ai tipi), che il manager Web Bean segue quando deve identificare il Web Beanda iniettare in punto di iniezione. Questo algoritmo di primo acchito sembra complesso, ma una volta che lo si è compreso, in realtà, risulta piuttosto intuitivo. La risoluzione sicura dei tipi viene eseguita durante l'inizializzazione del sistema (system initialization time), il che significa che il manager Web Bean informerà immediatamente un utente se le dipendenze di un Web Bean non possono essere soddisfatte, lanciando una UnsatisfiedDependencyException o una AmbiguousDependencyException."
#. Tag: para
@@ -221,12 +221,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
+msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
+msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
msgstr ""
#. Tag: title
@@ -388,7 +388,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you may be thinking, "What's the different between using a qualifier and just specifying the exact implementation class you want?" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alterative implementations of @Asynchronous PaymentProcessor!"
+msgid "Now, you may be thinking, \"What's the different between using a qualifier and just specifying the exact implementation class you want?\" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alternative implementations of @Asynchronous PaymentProcessor!"
msgstr ""
#. Tag: title
@@ -398,7 +398,7 @@ msgstr "Semplici Web Bean supportano soltanto le callback @PostConstruc
#. Tag: para
#, no-c-format
-msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to decare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
+msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to declare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
msgstr ""
#. Tag: para
@@ -410,7 +410,7 @@ msgstr ""
#, no-c-format
msgid ""
"@Inject \n"
-"void initServices(@Any Instance<Service> services) { \n"
+"void initServices(@Any Instance<Service> services) { \n"
" for (Service service: services) {\n"
" service.init();\n"
" }\n"
@@ -446,7 +446,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then we select one of the possible member values when appling the qualifier:"
+msgid "Then we select one of the possible member values when applying the qualifier:"
msgstr ""
#. Tag: programlisting
@@ -468,7 +468,7 @@ msgid ""
"@Target({METHOD, FIELD, PARAMETER, TYPE})\n"
"public @interface PayBy {\n"
" PaymentMethod value();\n"
-" @Nonbinding String comment() default "";\n"
+" @Nonbinding String comment() default \"\";\n"
"}"
msgstr ""
"this FAQ for step-by-step instructions for how to resolve an ambigous resolution exception between a raw bean type and a producer method that returns the same bean type."
+msgid "See this FAQ for step-by-step instructions for how to resolve an ambiguous resolution exception between a raw bean type and a producer method that returns the same bean type."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Just remember: "There can be only one.""
+msgid "Just remember: \"There can be only one.\""
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
+msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
+msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
msgstr "Vi è un ulteriore questione di cui occorre essere a conoscenza quando si usa la dependency injection in Web Beans."
#. Tag: title
@@ -651,7 +651,7 @@ msgstr "I client di un Web Bean che sono stati iniettati solitamente non hanno u
#. Tag: para
#, fuzzy, no-c-format
-msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
+msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
msgstr "Immaginiamo che un Web Bean associato allo scope applicazione tenga un riferimento diretto a un Web Bean associato allo scope richiesta. Il Web Bean con scope applicazione è condiviso fra molte diverse richieste. Comunque, ciascuna richiesta dovrebbe vedere una diversa istanza del Web bean con scope richiesta!"
# con scope sessione andrebbe meglio tardotto con->che sta in sessione (e zosì per tutte le situazioni analoghe?)?
@@ -677,7 +677,7 @@ msgstr "I seguenti tipi Java non possono essere gestiti tramite proxy dal manage
#. Tag: para
#, fuzzy, no-c-format
-msgid "classes which don't have a non-private constructor with no parameters, and"
+msgid "classes which don't have a non-private constructor with no parameters, and"
msgstr "classi che non abbiano costruttori non privati (non-private) senza parametri, e"
#. Tag: para
@@ -692,7 +692,7 @@ msgstr "array e tipi primitivi."
#. Tag: para
#, no-c-format
-msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
+msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
msgstr ""
#. Tag: para
@@ -702,7 +702,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "change the type of the injection point to Instance<X>,"
+msgid "change the type of the injection point to Instance<X>,"
msgstr ""
#. Tag: para
@@ -732,7 +732,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But we didn't get around to implementing this yet."
+msgid "But we didn't get around to implementing this yet."
msgstr ""
#. Tag: title
@@ -768,7 +768,7 @@ msgstr "L'applicazione può ottenere un'istanza dell'interfaccia Manage
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -803,7 +803,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -818,19 +818,19 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, we need to obtain an instance of our qualifier type. Since annotatons are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
+msgid "Next, we need to obtain an instance of our qualifier type. Since annotations are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"abstract class AsynchronousQualifier\n"
-"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
+"class AsynchronousQualifier\n"
+"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
msgstr ""
" \n"
@@ -845,14 +845,14 @@ msgstr ""
#, fuzzy, no-c-format
msgid ""
"PaymentProcessor p = paymentProcessorSource\n"
-" .select(new AnnotationLiteral<Asynchronous>() {});"
+" .select(new AnnotationLiteral<Asynchronous>() {});"
msgstr ""
"(){});]]>"
#. Tag: para
#, no-c-format
-msgid "We can't use an anonymous class to implement a qualifier type with members."
+msgid "However, we can't use an anonymous class to implement a qualifier type with members."
msgstr ""
#. Tag: para
@@ -900,7 +900,7 @@ msgstr "Un Web Bean con scope @Dependent può essere iniettat
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
+msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
msgstr "Vediamo un esempio. Il codice seguente è prolisso e vulnerabile a problemi di refactoring:"
#. Tag: programlisting
@@ -944,7 +944,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
+msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
msgstr "Non siete convinti? Eccovi un secondo esempio. Per iniettare parametri HTTP, è necessario definire un tipo di binding:"
#. Tag: programlisting
@@ -972,8 +972,8 @@ msgstr "Potremmo usare questo tipo di binding in corrispondenza ai punti di inie
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@HttpParam("username") String username;\n"
-"@HttpParam("password") String password;"
+"@HttpParam(\"username\") String username;\n"
+"@HttpParam(\"password\") String password;"
msgstr ""
""
@@ -988,7 +988,7 @@ msgstr "Il seguente metodo produttore esegue il lavoro:"
msgid ""
"class HttpParams\n"
"\n"
-" @Produces @HttpParam("")\n"
+" @Produces @HttpParam(\"\")\n"
" String getParamValue(InjectionPoint ip) {\n"
" ServletRequest request = (ServletRequest) FacesContext.getCurrentInstance().getExternalContext().getRequest();\n"
" return request.getParameter(ip.getAnnotated().getAnnotation(HttpParam.class).value());\n"
@@ -1007,7 +1007,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own prodcuer for the request and have it injected as a method parameter."
+msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own producer for the request and have it injected as a method parameter."
msgstr ""
#. Tag: para
@@ -1026,8 +1026,8 @@ msgstr "Il manager Web Bean fornisce un Web Bean di sistema che implementa l'int
msgid ""
"public interface InjectionPoint { \n"
" public Type getType();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Bean<?> getBean();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Bean<?> getBean();\n"
" public Member getMember();\n"
" public Annotated getAnnotated();\n"
" public boolean isDelegate();\n"
diff --git a/docs/reference/src/main/docbook/it-IT/interceptors.po b/docs/reference/src/main/docbook/it-IT/interceptors.po
index 35d3cde7c2d..fa71ffcd010 100644
--- a/docs/reference/src/main/docbook/it-IT/interceptors.po
+++ b/docs/reference/src/main/docbook/it-IT/interceptors.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-05 00:26+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -110,7 +110,7 @@ msgstr "Interceptor bindings"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
+msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
msgstr "Si supponga di voler dichiarare transazionali alcuni Web Beans. La prima cosa necessaria è un'annotazione di interceptor binding per specificare esattamente quali Web Beans sono interessati:"
#. Tag: programlisting
@@ -163,7 +163,7 @@ msgstr "Implementare gli interceptor"
#. Tag: para
#, fuzzy, no-c-format
-msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
+msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
msgstr "Bene, ma da qualche parte è necessario implementare l'interceptor che fornisce l'aspect di gestione della transazione. Occore quindi creare un interceptor EJB standard e annotarlo con @Interceptor e @Transactional.\""
#. Tag: programlisting
@@ -225,16 +225,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -265,17 +265,17 @@ msgstr "Per esempio è possibile specificare che l'interceptor di sicurezza veng
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -378,7 +378,7 @@ msgstr "Solitamente si usano combinazioni di tipi di interceptor binding per ass
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Secure(rolesAllowed="admin") @Transactional\n"
+"@Secure(rolesAllowed=\"admin\") @Transactional\n"
"public class ShoppingCart { ... }"
msgstr ""
"meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
+msgid "Well, fortunately, CDI works around this missing feature of Java. We may annotate one interceptor binding type with other interceptor binding types (termed a meta-annotation). The interceptor bindings are transitive — any 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
@@ -533,7 +533,7 @@ msgstr "gli interceptor possono non essere facilmente disabilitati a deployment
#. Tag: para
#, fuzzy, 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."
+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
diff --git a/docs/reference/src/main/docbook/it-IT/intro.po b/docs/reference/src/main/docbook/it-IT/intro.po
index 3ababcacb39..d97a1fdbef8 100644
--- a/docs/reference/src/main/docbook/it-IT/intro.po
+++ b/docs/reference/src/main/docbook/it-IT/intro.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-25 12:11+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -22,7 +22,7 @@ msgstr ""
# Rendere la frase "wondering what kinds of hoops the Web Beans specification will make you jump through!" più italiana.
#. Tag: para
#, fuzzy, no-c-format
-msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
+msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
msgstr "Non vedi l'ora di iniziare a scrivere il primo Web Beans? O forse sei un pò scettico e ti domandi quali virtuosismi ti farà fare la specifica Web Beans! La buona notizia è che probabilmente hai già scritto e usato centinaia, forse migliaia di Web Beans. Potresti addirittura non ricordare il primo Web Bean scritto."
#. Tag: title
@@ -37,27 +37,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Prior to Java EE 6, there was no clear definition of the term "bean" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications "beans" for years. There were even a couple of different kinds of things called "beans" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a "bean". What we've been missing is a common definition."
+msgid "Prior to Java EE 6, there was no clear definition of the term \"bean\" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications \"beans\" for years. There were even a couple of different kinds of things called \"beans\" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a \"bean\". What we've been missing is a common definition."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
+msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
+msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
+msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now let's see how to create your first bean that actually uses CDI."
+msgid "Now let's see how to create your first bean that actually uses CDI."
msgstr ""
#. Tag: title
@@ -67,14 +67,14 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
+msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
msgstr "Si supponga di avere due classi Java esistenti, usate da anni in varie applicazioni. La prima classe esegue il parsing di una stringa in una lista di frasi:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
"public class SentenceParser {\n"
-" public List<String> parse(String text) { ... }\n"
+" public List<String> parse(String text) { ... }\n"
"}"
msgstr ""
"TextTranslator non ha un costruttore con nessun pa
#. Tag: para
#, fuzzy, no-c-format
-msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
+msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
msgstr "Come hai indovinato, l'annotazione @Initializer ha qualcosa che fare con la dependency injection! @Initializer può essere applicato ad un costruttore od un metodo di un Web Bean, e dice al manager Web Bean di chiamare quel costruttore o metodo quando si istanzia il Web Bean. Il manager Web Bean inietterà altri Web Bean nei parametri del costruttore o del metodo."
#. Tag: para
@@ -182,7 +182,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
+msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
msgstr ""
#. Tag: programlisting
@@ -221,7 +221,7 @@ msgstr "Dove Translator è l'interfaccia locale:"
#. Tag: para
#, no-c-format
-msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
+msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
msgstr ""
#. Tag: para
@@ -232,7 +232,7 @@ msgstr "Si può ottenere un'istanza di TextTranslator inietta
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
+"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
"...\n"
"public void translate() {\n"
" textTranslatorInstance.get().translate(inputText);\n"
@@ -245,17 +245,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
+msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
+msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
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 Translator fosse disponibile se l'EJB SentenceTranslator non venisse deployato il manager Web Bean lancerebbe una UnsatisfiedDependencyException. Se più di un'implementazione di Translator fosse disponibile, il manager Web Bean lancerebbe una AmbiguousDependencyException."
#. Tag: para
#, no-c-format
-msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
+msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
msgstr ""
#~ msgid "Getting started with Web Beans"
diff --git a/docs/reference/src/main/docbook/it-IT/next.po b/docs/reference/src/main/docbook/it-IT/next.po
index c5f39f9cbfe..7b3906384e5 100644
--- a/docs/reference/src/main/docbook/it-IT/next.po
+++ b/docs/reference/src/main/docbook/it-IT/next.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-20 01:10+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -21,12 +21,12 @@ msgstr "Prossimi passi"
#. Tag: para
#, no-c-format
-msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
+msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
+msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
msgstr "L'implementazione della documentazione Web Beans è stata sviluppata in http://seamframework.org/WebBeans. Il team di sviluppo di RI ed il blog per la specifica Web Beans si trova in http://in.relation.to. Quest'articolo è sostanzialmente basato su una serie di articoli pubblicati sul blog."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/it-IT/part1.po b/docs/reference/src/main/docbook/it-IT/part1.po
index 6ed8a03b9f7..474b7ca05aa 100644
--- a/docs/reference/src/main/docbook/it-IT/part1.po
+++ b/docs/reference/src/main/docbook/it-IT/part1.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-24 19:21+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -130,7 +130,7 @@ msgstr "devo distruggerlo esplicitamente?"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Where should I keep the reference to it when I'm not currently using it?"
+msgid "Where should I keep the reference to it when I'm not currently using it?"
msgstr "dove dovrei tenerne il riferimento quando non lo sto usando direttamente?"
#. Tag: para
@@ -146,7 +146,7 @@ msgstr "cosa dovrei fare per condividere questo oggetto con altri oggetti?"
#. Tag: para
#, no-c-format
-msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
+msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
msgstr ""
# implementazione concreta mi pare pleonastico
@@ -181,12 +181,12 @@ msgstr "i decoratori permettono di compartimentare i proble
# loro consumatori di eventi? destinatari è meglio?
#. Tag: para
#, fuzzy, no-c-format
-msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
+msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
msgstr "Soprattutto, Web Beans fornisce tutti questi strumenti in un modo typesafe. Web Beans non usa mai identificatori di tipo stringa per determinare come interagiscono oggetti che collaborano fra di loro. Sebbene resti un'opzione, il linguaggio XML è usato raramente. Invece Web Beans utilizza l'informazione di tipo già presente nel modello a oggetti di Java, insieme ad un nuovo pattern, chiamato binding annotations, per assemblare i Web Beans, le loro dipendenze, i loro interceptor e decoratori e i loro consumatori di eventi."
#. Tag: para
#, no-c-format
-msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
+msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
msgstr ""
#. Tag: para
@@ -196,7 +196,7 @@ msgstr "Web Beans fornisce anche i necessari punti di integrazione in modo che a
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
+msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
msgstr "Web Beans è stata influenzata da un buon numero di framework Java esistenti, inclusi Seam, Guice and Spring. Comunque, Web Beans ha un proprio chiaro carattere distintivo: è più sicuro nell'uso dei tipi (typesafe) di Seam, è più orientato allo stato (stateful) e meno basato su XML di Spring, e più capace di Guice nelle applicazioni web ed enterprise."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/it-IT/part3.po b/docs/reference/src/main/docbook/it-IT/part3.po
index 86f8c1c1a66..462d6fa7e83 100644
--- a/docs/reference/src/main/docbook/it-IT/part3.po
+++ b/docs/reference/src/main/docbook/it-IT/part3.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-15 20:46+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
+msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
msgstr ""
#. Tag: para
@@ -72,7 +72,7 @@ msgstr "Il secondo tema saliente di Web Beans è lo tipizzazione forte
#. Tag: para
#, fuzzy, no-c-format
-msgid "You don't see string-based identifiers in CDI 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!"
+msgid "You don't see string-based identifiers in CDI 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
@@ -144,7 +144,7 @@ msgstr "Gli stereotipi (stereotypes) di Web Beans fanno far
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
+msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
msgstr "Ora siamo pronti ad incontrare alcune caratteristiche più avanzate di Web Beans. Tenete a mente che tali caratteristiche esistono sia per rendere il nostro codice più facile da validare che per renderlo più comprensibile. La maggior parte delle volte non è necessario usare tali carattestiche, ma, se usate con accortezza, si arriverà ad apprezzerne l'efficacia."
# literate=elegante (come in altri contesti)? oppure = letterato/informato/cosciente. Qui scelgo informato... nel senso di cosciente di se stesso.
diff --git a/docs/reference/src/main/docbook/it-IT/part4.po b/docs/reference/src/main/docbook/it-IT/part4.po
index 63130a499c3..b742c09bffd 100644
--- a/docs/reference/src/main/docbook/it-IT/part4.po
+++ b/docs/reference/src/main/docbook/it-IT/part4.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-24 19:34+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
+msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
msgstr ""
# modelli a componenti o architetture a componenti?
@@ -27,7 +27,7 @@ msgstr "Abbiamo già visto come Web Beans aiuti ad integrare EJB con JSF, permet
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
+msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
msgstr "Stiamo per scoprire come sfruttare appieno la piattaforma Java EE in applicazioni che usano Web Beans. Scorreremo anche velocemente un insieme di SPI (Service Provider Interface) fornite per permettere la realizzazione di estensioni portabili di Web Beans. Potrebbe non essere mai necessario usare queste SPI direttamente, ma è opportuno sapere che esistono, qualora possano servire. Soprattutto, le si sfrutterà in modo indiretto ogni volta che si utilizzeranno estensioni di terze parti."
#~ msgid "The third theme of Web Beans is integration. Web Beans was designed to work in concert with other technologies, helping the application developer fit the other technologies together. Web Beans is an open technology. It forms a part of the Java EE ecosystem, and is itself the foundation for a new ecosystem of portable extensions and integration with existing frameworks and technologies."
diff --git a/docs/reference/src/main/docbook/it-IT/part5.po b/docs/reference/src/main/docbook/it-IT/part5.po
index c08341a27f2..5831cc86652 100644
--- a/docs/reference/src/main/docbook/it-IT/part5.po
+++ b/docs/reference/src/main/docbook/it-IT/part5.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-31 10:42+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and Glassfish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
+msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and GlassFish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
msgstr "Web Beans è la reference implementatio di JSR-299, ed è usata da JBoss AS e Glassfish per fornire i servizi JSR-299 per le applicazioni Java Enterprise Edition. Web Beans va oltre gli ambienti e le API definite dalla specifica JSR-299 e fornisce supporto ad un numero di altri ambienti (quali servlet container quali Tomcat o Java SE) ed API e moduli addizionali (quali il logging la generazione XSD per i descrittori di deploy XML JSR-299)."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/it-IT/producermethods.po b/docs/reference/src/main/docbook/it-IT/producermethods.po
index 082b1e993db..f906e748987 100644
--- a/docs/reference/src/main/docbook/it-IT/producermethods.po
+++ b/docs/reference/src/main/docbook/it-IT/producermethods.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-31 11:05+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "Metodi produttori"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
+msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
msgstr "I metodi produttori consentono di superare alcune limitazioni che sorgono quando il manager Web Bean è responsabile dell'istanziamento degli oggetti al posto dell'applicazione. Questi metodi sono anche il modo migliore per integrare gli oggetti che non sono Web Beans dentro l'ambiente Web Beans. (Si incontrerà un secondo approccio in .)"
#. Tag: para
@@ -76,7 +76,7 @@ msgstr "varia l'implementazione di un tipo di API a runtime."
#. Tag: para
#, fuzzy, no-c-format
-msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
+msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
msgstr "In particolare i metodi produttori consentono l'uso del polimorfismo a runtime con Web Beans. Come visto, i tipi di deploy sono soluzioni potenti al problema del polimorfismo a deployment-time. Ma una volta che il sistema è deployato, l'implementazione Web Bean è sistemata. Un metodo produttore non ha tali limitazioni:"
#. Tag: programlisting
@@ -161,7 +161,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
+msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
msgstr "Ora, quando il metodo produttore viene chiamato, il PaymentStrategy restituito verrà associato al contesto di sessione. Il metodo produttore non verrà più chiamato nella stessa sessione."
#. Tag: para
@@ -176,12 +176,12 @@ msgstr "Iniezione nei metodi produttori"
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
+msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
msgstr "C'è un potenziale problema con il codice visto sopra. Le implementazioni di CreditCardPaymentStrategy vengono istanziate usando l'operatore Java new. Gli oggetti istanziati direttamente dall'applicazione non possono sfruttare la dependency injection e non hanno interceptor."
#. Tag: para
#, fuzzy, no-c-format
-msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
+msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
msgstr "Se questo non è ciò che si vuole, è possibile usare la dependency injection nel metodo produttore per ottenere istanze Web Bean:"
#. Tag: programlisting
@@ -213,12 +213,12 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of "promoting" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left "hanging" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
+msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of \"promoting\" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left \"hanging\" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
msgstr "Ma cosa succede se CreditCardPaymentStrategy è un Web Bean con scope di tipo richiesta? Il metodo produttore ha l'effetto di \"promuovere\" l'istanza corrente con scope di tipo richiesta a scope di tipo sessione. Questo è quasi certamente un bug! L'oggetto con scope richiesta verrà distrutto dal manager Web Bean prima che la sessione termini. Quest'errore non verrà rilevato dal manager Web Bean, quindi si faccia attenzione quando si restituiscono istanze Web Bean dai metodi produttori!"
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
+msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
msgstr "Ci sono almeno 3 modi per correggere questo bug. Si può cambiare lo scope dell'implementazione di CreditCardPaymentStrategy, ma questo non influenzerebbe gli altri client di questo Web Bean. Un'opzione migliore sarebbe quella di cambiare lo scope del metodo produttore a @Dependent o @RequestScoped."
#. Tag: para
@@ -265,7 +265,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
+msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
msgstr "Quindi verrebbe creata una nuova istanza dipendente di CreditCardPaymentStrategy, passata al metodo produttore, ritornata al metodo produttore ed infine associata al contesto di sessione. L'oggetto dipendente non verrebbe distrutto finché l'oggetto Preferences non viene distrutto, cioè a fine sessione."
#. Tag: title
diff --git a/docs/reference/src/main/docbook/it-IT/resources.po b/docs/reference/src/main/docbook/it-IT/resources.po
index 62862914b02..ae17b5091bc 100644
--- a/docs/reference/src/main/docbook/it-IT/resources.po
+++ b/docs/reference/src/main/docbook/it-IT/resources.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a nonportable "mapped name"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
+msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a non-portable \"mapped name\"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
msgstr ""
#. Tag: para
@@ -72,35 +72,35 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @WebServiceRef(lookup="java:app/service/Catalog")\n"
+"@Produces @WebServiceRef(lookup=\"java:app/service/Catalog\")\n"
"Catalog catalog;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @Resource(lookup="java:global/env/jdbc/CustomerDatasource") \n"
+"@Produces @Resource(lookup=\"java:global/env/jdbc/CustomerDatasource\") \n"
"@CustomerDatabase Datasource customerDatabase;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceContext(unitName="CustomerDatabase")\n"
+"@Produces @PersistenceContext(unitName=\"CustomerDatabase\")\n"
"@CustomerDatabase EntityManager customerDatabasePersistenceContext;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceUnit(unitName="CustomerDatabase") \n"
+"@Produces @PersistenceUnit(unitName=\"CustomerDatabase\") \n"
"@CustomerDatabase EntityManagerFactory customerDatabasePersistenceUnit;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @EJB(ejbLink="../their.jar#PaymentService") \n"
+"@Produces @EJB(ejbLink=\"../their.jar#PaymentService\") \n"
"PaymentService paymentService;"
msgstr ""
@@ -126,7 +126,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
+msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
msgstr ""
#. Tag: title
@@ -171,7 +171,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
+msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
msgstr ""
#. Tag: programlisting
@@ -186,7 +186,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@PersistenceContext(unitName="CustomerDatabase") EntityManager"
+msgid "@PersistenceContext(unitName=\"CustomerDatabase\") EntityManager"
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/it-IT/ri-spi.po b/docs/reference/src/main/docbook/it-IT/ri-spi.po
index e752086e620..5dfa743015d 100644
--- a/docs/reference/src/main/docbook/it-IT/ri-spi.po
+++ b/docs/reference/src/main/docbook/it-IT/ri-spi.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-06-08 21:35+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -31,7 +31,7 @@ msgstr "Servizi di risorse"
#. Tag: para
#, no-c-format
-msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the "Weld: Servlets" extension will be sufficient, and will work in any container supporting the Servlet API."
+msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the \"Weld: Servlets\" extension will be sufficient, and will work in any container supporting the Servlet API."
msgstr ""
#. Tag: para
@@ -56,7 +56,7 @@ msgstr "Tutte le interfacce in SPI supportano il pattern decorator e forniscono
#. Tag: para
#, fuzzy, no-c-format
-msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
+msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
msgstr "Il bootstrap supporta più ambienti. Un ambiente viene definito da un'implementazione dell'interfaccia Environment. Un numero di ambienti standard sono predefiniti nell'enumeration Environments. Diversi ambienti richiedono diversi servizi presenti (per esempio servlet non richiede i servizi di transazione, EJB o JPA). Di default viene assunto un ambiente EE, ma si può impostare un ambiente chiamando bootstrap.setEnvironment()."
#. Tag: para
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
+msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
msgstr ""
#. Tag: para
@@ -96,7 +96,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
+msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
msgstr ""
#. Tag: para
@@ -106,12 +106,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
+msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
+msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
msgstr ""
#. Tag: para
@@ -126,7 +126,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
+msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
msgstr ""
#. Tag: para
@@ -156,7 +156,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
+msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
msgstr ""
#. Tag: para
@@ -196,7 +196,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
+msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
msgstr ""
#. Tag: title
@@ -211,7 +211,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
+msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
msgstr "Risolvendo gli EJB locali (usati per mappare i session bean) viene restituito un wrapper (SessionObjectReference) attorno al riferimento EJB. Questo wrapper consente a Web Beans di richiedere un riferimento che implementi l'interfaccia di business data e, nel caso di SFSB, la richiesta di rimozione dell'EJB dal container."
#. Tag: para
@@ -276,7 +276,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); intercepter will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
+msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); interceptor will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
msgstr ""
#. Tag: para
@@ -351,7 +351,7 @@ msgstr "Il contesto applicazione"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
+msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
msgstr "Web Beans si aspetta che l'Application Server od un altro container fornisca la memorizzazione per ogni contesto applicazione. org.jboss.webbeans.context.api.BeanStore dovrebbe essere implementato per fornire uno storage con scope applicazione."
#. Tag: title
@@ -366,7 +366,7 @@ msgstr "L'interfaccia org.jboss.webbeans.bootstrap.api.BootstrapWeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
+msgid "You must ensure that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
msgstr ""
#. Tag: term
@@ -582,7 +582,7 @@ msgid ""
"InjectionTarget it = weldBeanManager.fireProcessInjectionTarget(clazz);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
+"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
"\n"
"// Produce the instance, performing any constructor injection required\n"
"Object instance = it.produce();\n"
@@ -616,16 +616,16 @@ msgstr ""
msgid ""
"// Obtain the EjbDescriptor for the EJB\n"
"// You may choose to use this utility method to get the descriptor\n"
-"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
+"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
"\n"
"// Get an the Bean object\n"
-"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
+"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
"\n"
"// Create the injection target\n"
"InjectionTarget it = deploymentBeanManager.createInjectionTarget(ejbDescriptor);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
+"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
"\n"
"// Perform injection and call initializers\n"
"it.inject(instance, cc);\n"
diff --git a/docs/reference/src/main/docbook/it-IT/scopescontexts.po b/docs/reference/src/main/docbook/it-IT/scopescontexts.po
index 845c3d77a1f..57af82cd29b 100644
--- a/docs/reference/src/main/docbook/it-IT/scopescontexts.po
+++ b/docs/reference/src/main/docbook/it-IT/scopescontexts.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-26 13:03+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "Scope e contesti"
#. Tag: para
#, fuzzy, no-c-format
-msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
+msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
msgstr "Finora si sono visti pochi esempi di annotazioni di tipi di scope. Gli scope di un Web Bean determinano il ciclo di vita del Web Bean. Lo scope determina anche quali client fanno riferimento a quali istanze di Web Bean. Secondo la specifica Web Bean, uno scope determina:"
#. Tag: para
@@ -46,7 +46,7 @@ msgstr "Per esempio, se esiste un Web Bean con scope di sessione, Curre
#. Tag: para
#, no-c-format
-msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
+msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
msgstr ""
#. Tag: title
@@ -56,7 +56,7 @@ msgstr "Tipi di scope"
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
+msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
msgstr "Web Bean fornisce un modello di contesto estensibile. E' possibile definire nuovi scope creando una nuova annotazione di un tipo di scope."
#. Tag: programlisting
@@ -74,7 +74,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
+msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
msgstr "Sicuramente questa è la parte facile del lavoro. Affinché questo tipo di scope sia utile, avremo bisogno di definire un oggetto Contesto che implementi lo scope! Implementare un Contesto è compito molto tecnico, inteso solo per lo sviluppo di framework."
#. Tag: para
@@ -93,7 +93,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Usually, you'll use one of CDI's built-in scopes."
+msgid "Usually, you'll use one of CDI's built-in scopes."
msgstr "Solitamente si userà uno degli scopi predefiniti di Web Beans."
#. Tag: title
@@ -193,7 +193,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
+msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
msgstr "Tre dei quattro scope predefiniti dovrebbero essere estremamente familiari ad ogni sviluppatore Java EE, quindi non si procede oltre nella discussione. Uno degli scope è comunque nuovo."
#. Tag: title
@@ -218,7 +218,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
+msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
msgstr "Una conversazione rappresenta un task, un'unità di lavoro dal punto di vista dell'utente. Il contesto di conversazione mantiene uno stato associato all'utente che sta lavorando. Se l'utente sta facendo più cose contemporaneamente ci saranno più conversazioni."
#. Tag: para
@@ -341,25 +341,25 @@ msgstr "Quindi il seguente link propaga la conversazione:"
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "<a href="/addProduct.jsp?cid=#{conversation.id}">Add Product</a>"
+msgid "<a href=\"/addProduct.jsp?cid=#{conversation.id}\">Add Product</a>"
msgstr "Add Product]]>"
#. Tag: para
#, no-c-format
-msgid "It's probably better to use one of the link components in JSF 2:"
+msgid "It's probably better to use one of the link components in JSF 2:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:link outcome="/addProduct.xhtml" value="Add Product">\n"
-" <f:param name="cid" value="#{javax.enterprise.context.conversation.id}"/>\n"
-"</h:link>"
+"<h:link outcome=\"/addProduct.xhtml\" value=\"Add Product\">\n"
+" <f:param name=\"cid\" value=\"#{javax.enterprise.context.conversation.id}\"/>\n"
+"</h:link>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a "flash" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
+msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a \"flash\" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
msgstr "Il manager Web Bean deve propagare le conversazioni attraverso i redirect, anche se la conversazione non è marcata long-running. Questo rende facile implementare il comune pattern POST-then-redirect, senza impiegare fragili costrutti quali oggetti \"flash\". In questo caso il manager Web Bean aggiunge automaticamente un parametro di richiesta all'URL di redirect."
#. Tag: title
@@ -369,7 +369,7 @@ msgstr "Timeout della conversazione"
#. Tag: para
#, fuzzy, no-c-format
-msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
+msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
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
@@ -399,12 +399,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can guess what "singleton" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
+msgid "You can guess what \"singleton\" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
+msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
msgstr ""
#. Tag: para
@@ -424,7 +424,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
+msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
msgstr ""
#. Tag: para
@@ -464,12 +464,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
+msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
+msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
msgstr ""
#. Tag: para
@@ -538,7 +538,7 @@ msgstr "Il campo calculator ha iniettata un'istanza con scope
#. Tag: para
#, fuzzy, no-c-format
-msgid "This feature is particularly useful with producer methods, as we'll see in the next chapter."
+msgid "This feature is particularly useful with producer methods, as we'll see in ."
msgstr "Questa caratteristica è particolarmente utile con i metodi produttori, come si vedrà nel prossimo capitolo."
#~ msgid "@RequestScoped"
diff --git a/docs/reference/src/main/docbook/it-IT/specialization.po b/docs/reference/src/main/docbook/it-IT/specialization.po
index 06648be5afa..076b49e0ccb 100644
--- a/docs/reference/src/main/docbook/it-IT/specialization.po
+++ b/docs/reference/src/main/docbook/it-IT/specialization.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-05 00:30+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
+msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
msgstr ""
#. Tag: para
@@ -41,12 +41,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
+msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
+msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
msgstr ""
#. Tag: title
@@ -75,7 +75,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
+msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
msgstr "Ma in quest'ambiente di prova si procede con l'override dell'implementazione di PaymentProcessor con un Web Bean differente:"
#. Tag: programlisting
@@ -115,12 +115,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
+msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
+msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
msgstr ""
#. Tag: programlisting
@@ -161,16 +161,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <alternatives>\n"
-" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
-" </alternatives>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <alternatives>\n"
+" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
+" </alternatives>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
+msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
msgstr ""
#. Tag: para
@@ -255,7 +255,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
+msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/it-IT/stereotypes.po b/docs/reference/src/main/docbook/it-IT/stereotypes.po
index 62f55b0ff60..00e1a6bcce5 100644
--- a/docs/reference/src/main/docbook/it-IT/stereotypes.po
+++ b/docs/reference/src/main/docbook/it-IT/stereotypes.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-25 22:17+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -99,7 +99,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
+msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
msgstr ""
#. Tag: title
@@ -142,7 +142,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
+msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
msgstr ""
#. Tag: title
@@ -262,12 +262,12 @@ msgstr "Stereotipi"
#. Tag: para
#, no-c-format
-msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
+msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
+msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
msgstr ""
#. Tag: programlisting
@@ -294,7 +294,7 @@ msgstr "Stereotipi standard"
#. Tag: para
#, fuzzy, no-c-format
-msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
+msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
msgstr "Si sono già visti due stereotipi standard definiti dalla specifica Web Bean: @Interceptor e @Decorator."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/it-IT/weldexamples.po b/docs/reference/src/main/docbook/it-IT/weldexamples.po
index c9a2222541b..23eb3ff2a38 100644
--- a/docs/reference/src/main/docbook/it-IT/weldexamples.po
+++ b/docs/reference/src/main/docbook/it-IT/weldexamples.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-23 21:23+0100\n"
"Last-Translator: Nicola Benaglia \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
+msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
msgstr ""
#. Tag: title
@@ -31,29 +31,29 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
+msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
+msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
+msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<faces-config version="2.0"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<faces-config version=\"2.0\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd">\n"
-"</faces-config>"
+" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd\">\n"
+"</faces-config>"
msgstr ""
"beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
+msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, there's the familiar web.xml:"
+msgid "Finally, there's the familiar web.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<web-app version="2.5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<web-app version=\"2.5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd\">\n"
" \n"
-" <display-name>weld-jsf-numberguess-war</display-name>\n"
-" <description>Weld JSF numberguess example (war)</description>\n"
-"\n"
-" <servlet>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
-" <load-on-startup>1</load-on-startup>\n"
-" </servlet>\n"
-"\n"
-" <servlet-mapping>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <url-pattern>*.jsf</url-pattern>\n"
-" </servlet-mapping>\n"
+" <display-name>weld-jsf-numberguess-war</display-name>\n"
+" <description>Weld JSF numberguess example (war)</description>\n"
+"\n"
+" <servlet>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
+" <load-on-startup>1</load-on-startup>\n"
+" </servlet>\n"
+"\n"
+" <servlet-mapping>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <url-pattern>*.jsf</url-pattern>\n"
+" </servlet-mapping>\n"
" \n"
-" <context-param>\n"
-" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
-" <param-value>.xhtml</param-value>\n"
-" </context-param>\n"
+" <context-param>\n"
+" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
+" <param-value>.xhtml</param-value>\n"
+" </context-param>\n"
"\n"
-" <session-config>\n"
-" <session-timeout>10</session-timeout>\n"
-" </session-config>\n"
+" <session-config>\n"
+" <session-timeout>10</session-timeout>\n"
+" </session-config>\n"
"\n"
-"</web-app>"
+"</web-app>"
msgstr ""
#. Tag: para
@@ -136,51 +136,51 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
+msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"\n"
-" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">\n"
-"<html xmlns="http://www.w3.org/1999/xhtml"\n"
-" xmlns:ui="http://java.sun.com/jsf/facelets"\n"
-" xmlns:h="http://java.sun.com/jsf/html"\n"
-" xmlns:f="http://java.sun.com/jsf/core">\n"
-"\n"
-" <ui:composition template="/template.xhtml">\n"
-" <ui:define name="content">\n"
-" <h1>Guess a number...</h1>\n"
-" <h:form id="numberGuess">\n"
-" <div style="color: red">\n"
-" <h:messages id="messages" globalOnly="false"/>\n"
-" <h:outputText id="Higher" value="Higher!"\n"
-" rendered="#{game.number gt game.guess and game.guess ne 0}"/>\n"
-" <h:outputText id="Lower" value="Lower!"\n"
-" rendered="#{game.number lt game.guess and game.guess ne 0}"/>\n"
-" </div>\n"
+"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
+" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n"
+"<html xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" xmlns:ui=\"http://java.sun.com/jsf/facelets\"\n"
+" xmlns:h=\"http://java.sun.com/jsf/html\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\">\n"
+"\n"
+" <ui:composition template=\"/template.xhtml\">\n"
+" <ui:define name=\"content\">\n"
+" <h1>Guess a number...</h1>\n"
+" <h:form id=\"numberGuess\">\n"
+" <div style=\"color: red\">\n"
+" <h:messages id=\"messages\" globalOnly=\"false\"/>\n"
+" <h:outputText id=\"Higher\" value=\"Higher!\"\n"
+" rendered=\"#{game.number gt game.guess and game.guess ne 0}\"/>\n"
+" <h:outputText id=\"Lower\" value=\"Lower!\"\n"
+" rendered=\"#{game.number lt game.guess and game.guess ne 0}\"/>\n"
+" </div>\n"
" \n"
-" <div>\n"
-" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
+" <div>\n"
+" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
" You have #{game.remainingGuesses} guesses remaining.\n"
-" </div>\n"
+" </div>\n"
" \n"
-" <div>\n"
+" <div>\n"
" Your guess: \n"
-" <h:inputText id="inputGuess" value="#{game.guess}"\n"
-" size="3" required="true" disabled="#{game.number eq game.guess}"\n"
-" validator="#{game.validateNumberRange}"/>\n"
-" <h:commandButton id="guessButton" value="Guess" \n"
-" action="#{game.check}" disabled="#{game.number eq game.guess}"/>\n"
-" </div>\n"
-" <div>\n"
-" <h:commandButton id="restartButton" value="Reset" action="#{game.reset}" immediate="true"/>\n"
-" </div>\n"
-" </h:form>\n"
-" </ui:define>\n"
-" </ui:composition>\n"
-"</html>"
+" <h:inputText id=\"inputGuess\" value=\"#{game.guess}\"\n"
+" size=\"3\" required=\"true\" disabled=\"#{game.number eq game.guess}\"\n"
+" validator=\"#{game.validateNumberRange}\"/>\n"
+" <h:commandButton id=\"guessButton\" value=\"Guess\" \n"
+" action=\"#{game.check}\" disabled=\"#{game.number eq game.guess}\"/>\n"
+" </div>\n"
+" <div>\n"
+" <h:commandButton id=\"restartButton\" value=\"Reset\" action=\"#{game.reset}\" immediate=\"true\"/>\n"
+" </div>\n"
+" </h:form>\n"
+" </ui:define>\n"
+" </ui:composition>\n"
+"</html>"
msgstr ""
#. Tag: para
@@ -190,7 +190,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are a number of messages which can be sent to the user, "Higher!", "Lower!" and "Correct!""
+msgid "There are a number of messages which can be sent to the user, \"Higher!\", \"Lower!\" and \"Correct!\""
msgstr ""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
+msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
msgstr ""
#. Tag: para
@@ -301,7 +301,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Generator is application scoped, so we don't get a different random each time."
+msgid "The Generator is application scoped, so we don't get a different random each time."
msgstr ""
#. Tag: para
@@ -311,12 +311,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
+msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
+msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
msgstr ""
#. Tag: programlisting
@@ -333,19 +333,19 @@ msgid ""
" private int remainingGuesses;\n"
"\n"
" @Inject @MaxNumber private int maxNumber;\n"
-" @Inject @Random Instance<Integer> randomNumber;\n"
+" @Inject @Random Instance<Integer> randomNumber;\n"
" \n"
" public Game() {}\n"
" \n"
" public void check() {\n"
-" if (guess > number) {\n"
+" if (guess > number) {\n"
" biggest = guess - 1;\n"
" }\n"
-" else if (guess < number) {\n"
+" else if (guess < number) {\n"
" smallest = guess + 1;\n"
" }\n"
" else if (guess == number) {\n"
-" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage("Correct!"));\n"
+" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage(\"Correct!\"));\n"
" }\n"
" remainingGuesses--;\n"
" }\n"
@@ -360,18 +360,18 @@ msgid ""
" }\n"
" \n"
" public void validateNumberRange(FacesContext context, UIComponent toValidate, Object value) {\n"
-" if (remainingGuesses <= 0) {\n"
-" FacesMessage message = new FacesMessage("No guesses left!");\n"
+" if (remainingGuesses <= 0) {\n"
+" FacesMessage message = new FacesMessage(\"No guesses left!\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" ((UIInput) toValidate).setValid(false);\n"
" return;\n"
" }\n"
" int input = (Integer) value;\n"
"\n"
-" if (input < smallest || input > biggest) {\n"
+" if (input < smallest || input > biggest) {\n"
" ((UIInput) toValidate).setValid(false);\n"
"\n"
-" FacesMessage message = new FacesMessage("Invalid guess");\n"
+" FacesMessage message = new FacesMessage(\"Invalid guess\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" }\n"
" }\n"
@@ -499,15 +499,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
+msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
"\n"
" org.jboss.weld.environment.servlet.Listener\n"
@@ -515,7 +515,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
+msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
msgstr ""
#. Tag: title
@@ -535,17 +535,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin ."
+msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects . Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
+msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects. Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This will create a project in your workspace called weld-se-numberguess ."
+msgid "This will create a project in your workspace called weld-se-numberguess."
msgstr ""
#. Tag: para
@@ -555,7 +555,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to get the example running!"
+msgid "It's time to get the example running!"
msgstr ""
#. Tag: title
@@ -565,12 +565,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
+msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right click on the project, and choose Run As -> Run As Application:"
+msgid "Right click on the project, and choose Run As -> Run As Application:"
msgstr ""
#. Tag: para
@@ -620,7 +620,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's have a look at the significant code and configuration files that make up this example."
+msgid "Let's have a look at the significant code and configuration files that make up this example."
msgstr ""
#. Tag: para
@@ -630,7 +630,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
+msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
msgstr ""
#. Tag: programlisting
@@ -675,7 +675,7 @@ msgid ""
"\n"
" public boolean isGameLost()\n"
" {\n"
-" return guess != number && remainingGuesses <= 0;\n"
+" return guess != number && remainingGuesses <= 0;\n"
" }\n"
"\n"
" public boolean check()\n"
@@ -684,12 +684,12 @@ msgid ""
"\n"
" if (checkNewNumberRangeIsValid())\n"
" {\n"
-" if (guess > number)\n"
+" if (guess > number)\n"
" {\n"
" biggest = guess - 1;\n"
" }\n"
"\n"
-" if (guess < number)\n"
+" if (guess < number)\n"
" {\n"
" smallest = guess + 1;\n"
" }\n"
@@ -707,7 +707,7 @@ msgid ""
"\n"
" private boolean checkNewNumberRangeIsValid()\n"
" {\n"
-" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
+" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
" }\n"
"\n"
" @PostConstruct\n"
@@ -724,12 +724,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
+msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
+msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
msgstr ""
#. Tag: para
@@ -759,12 +759,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
+msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
+msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
msgstr ""
#. Tag: programlisting
@@ -777,11 +777,11 @@ msgid ""
"\n"
" public String getChallengeMessage()\n"
" {\n"
-" StringBuilder challengeMsg = new StringBuilder("I'm thinking of a number between ");\n"
+" StringBuilder challengeMsg = new StringBuilder(\"I'm thinking of a number between \");\n"
" challengeMsg.append(game.getSmallest());\n"
-" challengeMsg.append(" and ");\n"
+" challengeMsg.append(\" and \");\n"
" challengeMsg.append(game.getBiggest());\n"
-" challengeMsg.append(". Can you guess what it is?");\n"
+" challengeMsg.append(\". Can you guess what it is?\");\n"
"\n"
" return challengeMsg.toString();\n"
" }\n"
@@ -790,34 +790,34 @@ msgid ""
" {\n"
" if (game.isGameWon())\n"
" {\n"
-" return "You guessed it! The number was " + game.getNumber();\n"
+" return \"You guessed it! The number was \" + game.getNumber();\n"
" }\n"
" else if (game.isGameLost())\n"
" {\n"
-" return "You are fail! The number was " + game.getNumber();\n"
+" return \"You are fail! The number was \" + game.getNumber();\n"
" }\n"
" else if (!game.isValidNumberRange())\n"
" {\n"
-" return "Invalid number range!";\n"
+" return \"Invalid number range!\";\n"
" }\n"
" else if (game.getRemainingGuesses() == Game.MAX_NUM_GUESSES)\n"
" {\n"
-" return "What is your first guess?";\n"
+" return \"What is your first guess?\";\n"
" }\n"
" else\n"
" {\n"
" String direction = null;\n"
"\n"
-" if (game.getGuess() < game.getNumber())\n"
+" if (game.getGuess() < game.getNumber())\n"
" {\n"
-" direction = "Higher";\n"
+" direction = \"Higher\";\n"
" }\n"
" else\n"
" {\n"
-" direction = "Lower";\n"
+" direction = \"Lower\";\n"
" }\n"
"\n"
-" return direction + "! You have " + game.getRemainingGuesses() + " guesses left.";\n"
+" return direction + \"! You have \" + game.getRemainingGuesses() + \" guesses left.\";\n"
" }\n"
" }\n"
"}"
@@ -830,7 +830,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
+msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
msgstr ""
#. Tag: para
@@ -900,7 +900,7 @@ msgid ""
" private void refreshUI() {\n"
" mainLabel.setText( msgGenerator.getChallengeMessage() );\n"
" messageLabel.setText( msgGenerator.getResultMessage() );\n"
-" guessText.setText( "" );\n"
+" guessText.setText( \"\" );\n"
" guessesLeftBar.setValue( game.getRemainingGuesses() );\n"
" guessText.requestFocus();\n"
" }\n"
@@ -935,7 +935,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
+msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
msgstr ""
#. Tag: para
@@ -945,7 +945,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Calls game.check() to validate and perform one 'turn' of the game"
+msgid "Calls game.check() to validate and perform one 'turn' of the game"
msgstr ""
#. Tag: para
@@ -970,7 +970,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
+msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
msgstr ""
#. Tag: para
@@ -980,25 +980,25 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
+msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<plugin>\n"
-" <groupId>org.apache.maven.plugins</groupId>\n"
-" <artifactId>maven-ear-plugin</artifactId>\n"
-" <configuration>\n"
-" <modules>\n"
-" <webModule>\n"
-" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
-" <artifactId>weld-jsf-translator-war</artifactId>\n"
-" <contextRoot>/weld-translator</contextRoot>\n"
-" </webModule>\n"
-" </modules>\n"
-" </configuration>\n"
-"</plugin>"
+"<plugin>\n"
+" <groupId>org.apache.maven.plugins</groupId>\n"
+" <artifactId>maven-ear-plugin</artifactId>\n"
+" <configuration>\n"
+" <modules>\n"
+" <webModule>\n"
+" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
+" <artifactId>weld-jsf-translator-war</artifactId>\n"
+" <contextRoot>/weld-translator</contextRoot>\n"
+" </webModule>\n"
+" </modules>\n"
+" </configuration>\n"
+"</plugin>"
msgstr ""
"\n"
" org.apache.maven.plugins\n"
@@ -1021,32 +1021,32 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
+msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<application version="5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<application version=\"5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/application_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/application_5.xsd\">\n"
"\n"
-" <display-name>weld-jsf-translator-ear</display-name>\n"
-" <description>The Weld JSF translator example (ear)</description>\n"
+" <display-name>weld-jsf-translator-ear</display-name>\n"
+" <description>The Weld JSF translator example (ear)</description>\n"
" \n"
-" <module>\n"
-" <web>\n"
-" <web-uri>weld-translator.war</web-uri>\n"
-" <context-root>/weld-translator</context-root>\n"
-" </web>\n"
-" </module>\n"
-" <module>\n"
-" <ejb>weld-translator.jar</ejb>\n"
-" </module>\n"
-"</application>"
+" <module>\n"
+" <web>\n"
+" <web-uri>weld-translator.war</web-uri>\n"
+" <context-root>/weld-translator</context-root>\n"
+" </web>\n"
+" </module>\n"
+" <module>\n"
+" <ejb>weld-translator.jar</ejb>\n"
+" </module>\n"
+"</application>"
msgstr ""
"war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
+msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (ommitted here for brevity):"
+msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (omitted here for brevity):"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:form id="translator">\n"
+"<h:form id=\"translator\">\n"
"\n"
-" <table>\n"
-" <tr align="center" style="font-weight: bold">\n"
-" <td>\n"
+" <table>\n"
+" <tr align=\"center\" style=\"font-weight: bold\">\n"
+" <td>\n"
" Your text\n"
-" </td>\n"
-" <td>\n"
+" </td>\n"
+" <td>\n"
" Translation\n"
-" </td>\n"
-" </tr>\n"
-" <tr>\n"
-" <td>\n"
-" <h:inputTextarea id="text" value="#{translator.text}" required="true" rows="5" cols="80"/>\n"
-" </td>\n"
-" <td>\n"
-" <h:outputText value="#{translator.translatedText}"/>\n"
-" </td>\n"
-" </tr>\n"
-" </table>\n"
-" <div>\n"
-" <h:commandButton id="button" value="Translate" action="#{translator.translate}"/>\n"
-" </div>\n"
+" </td>\n"
+" </tr>\n"
+" <tr>\n"
+" <td>\n"
+" <h:inputTextarea id=\"text\" value=\"#{translator.text}\" required=\"true\" rows=\"5\" cols=\"80\"/>\n"
+" </td>\n"
+" <td>\n"
+" <h:outputText value=\"#{translator.translatedText}\"/>\n"
+" </td>\n"
+" </tr>\n"
+" </table>\n"
+" <div>\n"
+" <h:commandButton id=\"button\" value=\"Translate\" action=\"#{translator.translate}\"/>\n"
+" </div>\n"
" \n"
-"</h:form>"
+"</h:form>"
msgstr ""
"\n"
"\n"
@@ -1141,12 +1141,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
+msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
+msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
msgstr ""
#. Tag: para
@@ -1170,7 +1170,7 @@ msgid ""
" public String translate(String text) { \n"
" StringBuilder sb = new StringBuilder(); \n"
" for (String sentence: sentenceParser.parse(text)) { \n"
-" sb.append(translator.translate(sentence)).append(". "); \n"
+" sb.append(translator.translate(sentence)).append(\". \"); \n"
" } \n"
" return sb.toString().trim(); \n"
" }\n"
@@ -1199,7 +1199,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
+msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
msgstr ""
#. Tag: programlisting
@@ -1209,7 +1209,7 @@ msgid ""
"public class SentenceTranslator implements Translator { \n"
"\n"
" public String translate(String sentence) { \n"
-" return "Lorem ipsum dolor sit amet"; \n"
+" return \"Lorem ipsum dolor sit amet\"; \n"
" }\n"
"\n"
"}"
@@ -1233,7 +1233,7 @@ msgstr ""
msgid ""
"@Stateful\n"
"@RequestScoped\n"
-"@Named("translator")\n"
+"@Named(\"translator\")\n"
"public class TranslatorControllerBean implements TranslatorController {\n"
"\n"
" @Inject private TextTranslator translator;\n"
diff --git a/docs/reference/src/main/docbook/ja-JP/Weld_-_JSR-299_Reference_Implementation.po b/docs/reference/src/main/docbook/ja-JP/Weld_-_JSR-299_Reference_Implementation.po
new file mode 100644
index 00000000000..f4baccac014
--- /dev/null
+++ b/docs/reference/src/main/docbook/ja-JP/Weld_-_JSR-299_Reference_Implementation.po
@@ -0,0 +1,59 @@
+#
+# AUTHOR , YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "A note about naming and nomenclature"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Shortly before the final draft of JSR-299 was submitted, the specification changed its name from \"Web Beans\" to \"Java Contexts and Dependency Injection for the Java EE platform\", abbreviated CDI. For a brief period after the renaming, the reference implementation adopted the name \"Web Beans\". However, this ended up causing more confusion than it solved and Red Hat decided to change the name of the reference implementation to \"Weld\". You may still find other documentation, blogs, forum posts, etc. that use the old nomenclature. Please update any references you can. The naming game is over."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You'll also find that some of the functionality that once existed in the specification is now missing, such as defining beans in XML. These features will be available as portable extensions for CDI in the Weld project, and perhaps other implementations."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this reference guide was started while changes were still being made to the specification. We've done our best to update it for accuracy. If you discover a conflict between what is written in this guide and the specification, the specification is the authority—assume it is correct. If you believe you have found an error in the specification, please report it to the JSR-299 EG."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Beans"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Start with Weld, the CDI Reference Implementation"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Loose coupling with strong typing"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "CDI and the Java EE ecosystem"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Weld Reference Guide"
+msgstr ""
+
diff --git a/docs/reference/src/main/docbook/ja-JP/beans.po b/docs/reference/src/main/docbook/ja-JP/beans.po
index 1c5c7e32f08..d0838857a34 100644
--- a/docs/reference/src/main/docbook/ja-JP/beans.po
+++ b/docs/reference/src/main/docbook/ja-JP/beans.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
+msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
msgstr ""
#. Tag: para
@@ -56,7 +56,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
+msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
msgstr ""
#. Tag: para
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
+msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
msgstr ""
#. Tag: title
@@ -131,7 +131,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's see what all this new terminology means."
+msgid "Let's see what all this new terminology means."
msgstr ""
#. Tag: title
@@ -141,7 +141,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a "contract" that must be satisfied by the bean to be injected. The contract is:"
+msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a \"contract\" that must be satisfied by the bean to be injected. The contract is:"
msgstr ""
#. Tag: para
@@ -164,14 +164,14 @@ msgstr ""
msgid ""
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
+msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
msgstr ""
#. Tag: para
@@ -192,12 +192,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
+msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
+msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
msgstr ""
#. Tag: programlisting
@@ -206,19 +206,19 @@ msgid ""
"@Typed(Shop.class)\n"
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of "quality" using a qualifier."
+msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of \"quality\" using a qualifier."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
+msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
msgstr ""
#. Tag: programlisting
@@ -232,12 +232,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
+msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
+msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
msgstr ""
#. Tag: para
@@ -252,12 +252,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
+msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
msgstr ""
#. Tag: para
@@ -275,12 +270,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If a bean does not explicitly specify a qualifier, it has the default qualifier, @Default."
+msgid "If a bean or an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
+msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
msgstr ""
#. Tag: title
@@ -312,7 +307,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
+msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
msgstr ""
#. Tag: para
@@ -322,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk more about scopes in ."
+msgid "We'll talk more about scopes in ."
msgstr ""
#. Tag: title
@@ -343,7 +338,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"public @SessionScoped @Named("cart")\n"
+"public @SessionScoped @Named(\"cart\")\n"
"class ShoppingCart implements Serializable { ... }"
msgstr ""
@@ -355,9 +350,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:dataTable value="#{cart.lineItems}" var="item">\n"
+"<h:dataTable value=\"#{cart.lineItems}\" var=\"item\">\n"
" ...\n"
-"</h:dataTable>"
+"</h:dataTable>"
msgstr ""
#. Tag: para
@@ -389,7 +384,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
+msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
msgstr ""
#. Tag: programlisting
@@ -416,12 +411,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
+msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
+msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
msgstr ""
#. Tag: para
@@ -470,17 +465,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
+msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
+msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
+msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
msgstr ""
#. Tag: title
@@ -490,7 +485,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
+msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
msgstr ""
#. Tag: title
@@ -500,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
+msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
msgstr ""
#. Tag: para
@@ -525,7 +520,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It has an appropriate constructor—either:"
+msgid "It has an appropriate constructor—either:"
msgstr ""
#. Tag: para
@@ -540,7 +535,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
+msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
msgstr ""
#. Tag: para
@@ -585,12 +580,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
+msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
+msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
msgstr ""
#. Tag: para
@@ -625,7 +620,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
+msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
msgstr ""
#. Tag: para
@@ -640,17 +635,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
+msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
+msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're "heavyweight". It's nothing more than superstition to think that something is "heavier" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like "heavyweight"."
+msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're \"heavyweight\". It's nothing more than superstition to think that something is \"heavier\" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like \"heavyweight\"."
msgstr ""
#. Tag: title
@@ -690,7 +685,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
+msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
msgstr ""
#. Tag: programlisting
@@ -705,7 +700,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<p>Your raffle number is #{randomNumber}.</p>"
+msgid "<p>Your raffle number is #{randomNumber}.</p>"
msgstr ""
#. Tag: para
@@ -746,14 +741,14 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces Set<Roles> getRoles(User user) {\n"
+"@Produces Set<Roles> getRoles(User user) {\n"
" return user.getRoles();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk much more about producer methods in ."
+msgid "We'll talk much more about producer methods in ."
msgstr ""
#. Tag: title
@@ -763,7 +758,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
+msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
msgstr ""
#. Tag: programlisting
@@ -771,7 +766,7 @@ msgstr ""
msgid ""
"public class Shop {\n"
" @Produces PaymentProcessor paymentProcessor = ....;\n"
-" @Produces @Catalog List<Product> products = ....;\n"
+" @Produces @Catalog List<Product> products = ....;\n"
"}"
msgstr ""
@@ -782,5 +777,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
+msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
msgstr ""
diff --git a/docs/reference/src/main/docbook/ja-JP/configure.po b/docs/reference/src/main/docbook/ja-JP/configure.po
index eeba87f0a16..01ef2ccd8ab 100644
--- a/docs/reference/src/main/docbook/ja-JP/configure.po
+++ b/docs/reference/src/main/docbook/ja-JP/configure.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -30,50 +30,50 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
+msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<?xml version="1.0" encoding="UTF-8"?>\n"
-"<beans xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \n"
-" xmlns:weld="http://jboss.org/schema/weld/beans" \n"
-" xsi:schemaLocation="\n"
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<beans xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" \n"
+" xmlns:weld=\"http://jboss.org/schema/weld/beans\" \n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee http://docs.jboss.org/cdi/beans_1_0.xsd\n"
-" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">\n"
+" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd\">\n"
" \n"
-" <weld:scan>\n"
+" <weld:scan>\n"
" \n"
-" <!-- Don't deploy the classes for the swing app! -->\n"
-" <weld:exclude name="com.acme.swing.**" />\n"
+" <!-- Don't deploy the classes for the swing app! -->\n"
+" <weld:exclude name=\"com.acme.swing.**\" />\n"
" \n"
-" <!-- Don't include GWT support if GWT is not installed -->\n"
-" <weld:exclude name="com.acme.gwt.**">\n"
-" <weld:if-class-available name="!com.google.GWT"/>\n"
-" </weld:exclude>\n"
+" <!-- Don't include GWT support if GWT is not installed -->\n"
+" <weld:exclude name=\"com.acme.gwt.**\">\n"
+" <weld:if-class-available name=\"!com.google.GWT\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
+" <!--\n"
" Exclude classes which end in Blether if the system property verbosity is set to low\n"
" i.e.\n"
" java ... -Dverbosity=low \n"
-" --> \n"
-" <weld:exclude pattern="^(.*)Blether$">\n"
-" <weld:if-system-property name="verbosity" value="low"/>\n"
-" </weld:exclude>\n"
+" --> \n"
+" <weld:exclude pattern=\"^(.*)Blether$\">\n"
+" <weld:if-system-property name=\"verbosity\" value=\"low\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
-" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
+" <!--\n"
+" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
" property is not set\n"
-" -->\n"
-" <weld:exclude name="com.acme.jsf.**">\n"
-" <weld:if-class-available name="org.apahce.wicket.Wicket"/>\n"
-" <weld:if-system-property name="!viewlayer"/>\n"
-" </weld:exclude>\n"
-" </weld:scan>\n"
+" -->\n"
+" <weld:exclude name=\"com.acme.jsf.**\">\n"
+" <weld:if-class-available name=\"org.apahce.wicket.Wicket\"/>\n"
+" <weld:if-system-property name=\"!viewlayer\"/>\n"
+" </weld:exclude>\n"
+" </weld:scan>\n"
" \n"
-"</beans>"
+"</beans>"
msgstr ""
#. Tag: para
@@ -83,7 +83,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
+msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
msgstr ""
#. Tag: para
@@ -93,12 +93,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
+msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
+msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
msgstr ""
#. Tag: para
@@ -113,5 +113,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
+msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
msgstr ""
diff --git a/docs/reference/src/main/docbook/ja-JP/contexts.po b/docs/reference/src/main/docbook/ja-JP/contexts.po
index 998addb61d4..6503057daf1 100644
--- a/docs/reference/src/main/docbook/ja-JP/contexts.po
+++ b/docs/reference/src/main/docbook/ja-JP/contexts.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,17 +25,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld allows you to easiy manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivaed (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
+msgid "Weld allows you to easily manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivated (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and discociating the data store after calling activate."
+msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and dissociating the data store after calling activate."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld automatically controls context lifecycle in many scenarios such as Http Requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
+msgid "Weld automatically controls context lifecycle in many scenarios such as HTTP requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
msgstr ""
#. Tag: para
@@ -145,7 +145,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
+msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
msgstr ""
#. Tag: entry
@@ -245,12 +245,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implmentations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
+msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implementations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
+msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
msgstr ""
#. Tag: programlisting
@@ -263,14 +263,14 @@ msgid ""
" ...\n"
" \n"
" /* Start the request, providing a data store which will last the lifetime of the request */\n"
-" public void startRequest(Map<String, Object> requestDataStore) {\n"
+" public void startRequest(Map<String, Object> requestDataStore) {\n"
" // Associate the store with the context and acticate the context\n"
" requestContext.associate(requestDataStore);\n"
" requestContext.activate();\n"
" }\n"
" \n"
" /* End the request, providing the same data store as was used to start the request */\n"
-" public void endRequest(Map<String, Object> requestDataStore) {\n"
+" public void endRequest(Map<String, Object> requestDataStore) {\n"
" try {\n"
" /* Invalidate the request (all bean instances will be scheduled for destruction) */\n"
" requestContext.invalidate();\n"
@@ -290,7 +290,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's session contexts are "lazy" and don't require a session to actually exist until a bean instance must be written."
+msgid "Weld's session contexts are \"lazy\" and don't require a session to actually exist until a bean instance must be written."
msgstr ""
#. Tag: para
@@ -308,16 +308,16 @@ msgid ""
" /* Start a transient conversation */\n"
" /* Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */\n"
-" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" resumeOrStartConversation(requestDataStore, sessionDataStore, null);\n"
" }\n"
"\n"
" /* Start a transient conversation (if cid is null) or resume a non-transient */\n"
" /* conversation. Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */ \n"
-" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore, \n"
+" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore, \n"
" String cid) {\n"
" /* Associate the stores with the context and acticate the context */\n"
" * BoundRequest just wraps the two datastores */\n"
@@ -329,8 +329,8 @@ msgid ""
" /* End the conversations, providing the same data store as was used to start */\n"
" /* the request. Any transient conversations will be destroyed, any newly-promoted */\n"
" /* conversations will be placed into the session */\n"
-" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" try {\n"
" /* Invalidate the conversation (all transient conversations will be scheduled for destruction) */\n"
" conversationContext.invalidate();\n"
@@ -345,15 +345,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the containber), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
+msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the container), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the abilty to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
+msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the ability to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's conversations are not assigned ids until they become non-transient."
+msgid "Weld's conversations are not assigned ids until they become non-transient."
msgstr ""
diff --git a/docs/reference/src/main/docbook/ja-JP/decorators.po b/docs/reference/src/main/docbook/ja-JP/decorators.po
index e3b1808168d..14bf0bf4af0 100644
--- a/docs/reference/src/main/docbook/ja-JP/decorators.po
+++ b/docs/reference/src/main/docbook/ja-JP/decorators.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-04-30 23:45+0900\n"
"Last-Translator: Fusayuki Minamoto \n"
"Language-Team: none\n"
@@ -21,12 +21,12 @@ msgstr "デコレータ"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
+msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
msgstr "インタセプタは、型システムとは 直交した (複数の)関心事をとらえて、それらを分離する強力な方法です。インタセプタは任意のJavaの型の呼び出しに割り込むことができます。しかし、これは当然のこととして、トランザクション管理やセキュリティ管理のような技術的関心事を完全に解決します。しかし、インタセプタは割り込む対象となる事象の実際のセマンティクスまでは気づきません。したがって、インタセプタはビジネス関連の関心事を分離するには適したツールではありません。"
#. Tag: para
#, fuzzy, no-c-format
-msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
+msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
msgstr "反対のことは デコレータ についても言えます。デコレータは特定のJavaインタフェースのみの呼び出しに割り込むので、そのインタフェースに付随するすべてのセマンティクスを知っています。このことによってデコレータはある種のビジネス関心事をモデリングするための完全なツールになります。また、それはデコレータがインタセプタが持つ一般性を備えていないことも意味します。デコレータは多くの異なる型に対して横断的な技術的関心事を解決することはできないのです。"
#. Tag: para
@@ -124,7 +124,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
+msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
msgstr "他のシンプル Web Beans とは異なり、デコレータは抽象クラスにすることができます。修飾されたインタフェースの特定のメソッドのためにデコレータとして何も特別なことをする必要がなければ、そのメソッドを実装する必要はありません。"
#. Tag: para
@@ -208,14 +208,14 @@ msgid ""
" \n"
" public void withdraw(BigDecimal amount) {\n"
" account.withdraw(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedWithdrawl(amount) );\n"
" }\n"
" }\n"
" \n"
" public void deposit(BigDecimal amount);\n"
" account.deposit(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedDeposit(amount) );\n"
" }\n"
" }\n"
@@ -258,21 +258,21 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <decorators>\n"
-" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
-" </decorators>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <decorators>\n"
+" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
+" </decorators>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
+msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
msgstr "この宣言はデコレータに対して <Interceptors> 宣言がインタセプタに対するものと同じ目的を持ちます。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ja-JP/ee.po b/docs/reference/src/main/docbook/ja-JP/ee.po
index 949ce1c6c50..6bb9b5d32c0 100644
--- a/docs/reference/src/main/docbook/ja-JP/ee.po
+++ b/docs/reference/src/main/docbook/ja-JP/ee.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-04-19 01:59+0900\n"
"Last-Translator: wadahiro \n"
"Language-Team: none\n"
@@ -57,7 +57,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
+msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
msgstr ""
#. Tag: para
@@ -82,7 +82,7 @@ msgstr "Java EEリソースをWeb Beansにインジェクトする"
#. Tag: para
#, fuzzy, no-c-format
-msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
+msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
msgstr "すべてのシンプル、エンタープライズ Web Beansは、@Resource、@EJB、および@PersistenceContextを使用することでJava EEの依存性注入を利用できます。ここまでは注意を払いませんでしたが、既にいくつかの例を見てきました。"
#. Tag: programlisting
@@ -141,7 +141,7 @@ msgstr "サーブレットからWeb Beanを呼び出す"
#. Tag: para
#, fuzzy, no-c-format
-msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
+msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
msgstr "Java EE 6でサーブレットからWeb Beanを使用することは簡単です。フィールドか初期化メソッドによるインジェクションを使用して、Web Beansをインジェクトしてください。"
#. Tag: programlisting
@@ -154,14 +154,14 @@ msgid ""
" @Override\n"
" public void service(HttpServletRequest request, HttpServletResponse response)\n"
" throws ServletException, IOException {\n"
-" credentials.setUsername(request.getParameter("username")):\n"
-" credentials.setPassword(request.getParameter("password")):\n"
+" credentials.setUsername(request.getParameter(\"username\")):\n"
+" credentials.setPassword(request.getParameter(\"password\")):\n"
" login.login();\n"
" if ( login.isLoggedIn() ) {\n"
-" response.sendRedirect("/home.jsp");\n"
+" response.sendRedirect(\"/home.jsp\");\n"
" }\n"
" else {\n"
-" response.sendRedirect("/loginError.jsp");\n"
+" response.sendRedirect(\"/loginError.jsp\");\n"
" }\n"
" }\n"
" \n"
@@ -200,7 +200,7 @@ msgstr "Web Beanからメッセージ駆動型Beanを呼び出す"
#. Tag: para
#, no-c-format
-msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
+msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
msgstr ""
#. Tag: para
@@ -262,10 +262,10 @@ msgstr ""
#, no-c-format
msgid ""
"public class OrderResources {\n"
-" @Resource(name="jms/ConnectionFactory")\n"
+" @Resource(name=\"jms/ConnectionFactory\")\n"
" private ConnectionFactory connectionFactory;\n"
" \n"
-" @Resource(name="jms/OrderQueue")\n"
+" @Resource(name=\"jms/OrderQueue\")\n"
" private Queue orderQueue;\n"
" \n"
" @Produces @OrderConnection\n"
@@ -316,7 +316,7 @@ msgid ""
"\n"
"public void sendMessage() {\n"
" MapMessage msg = orderSession.createMapMessage();\n"
-" msg.setLong("orderId", order.getId());\n"
+" msg.setLong(\"orderId\", order.getId());\n"
" ...\n"
" producer.send(msg);\n"
"}"
@@ -342,7 +342,7 @@ msgstr "パッケージとデプロイ"
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a "bean archive". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
+msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a \"bean archive\". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
msgstr "Web Beansはどのような特別なデプロイのアーカイブも定義しません。アプリケーションのクラスパスにおいてデプロイの場所である、JAR、EJB-JARまたはWARの中にWeb Beansをパッケージできます。しかしながら、Web Beansを含む各アーカイブは、META-INFかWEB-INFディレクトリにweb-beans.xmlというファイルを含む必要があります。そのファイルは空でもよいです。web-beans.xmlファイルを持たないアーカイブでデプロイされたWeb Beansは、アプリケーションで利用できないでしょう。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ja-JP/environments.po b/docs/reference/src/main/docbook/ja-JP/environments.po
index b46c33d2416..45dfeebeb85 100644
--- a/docs/reference/src/main/docbook/ja-JP/environments.po
+++ b/docs/reference/src/main/docbook/ja-JP/environments.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-05-22 21:50+0900\n"
"Last-Translator: TANABE Junnichi \n"
"Language-Team: none\n"
@@ -56,12 +56,12 @@ msgstr "Web BeansはTomcat 6.0やJetty 6.1のようなサーブレットコン
#. Tag: para
#, fuzzy, no-c-format
-msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
+msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
msgstr "Web BeansはサーブレットコンテナではセッションBean、 @EJB アノテーションや @PersistenceContext アノテーションを使用したり、トランザクションイベントを使用したインジェクションのデプロイをサポートしません。"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an "uber-jar", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
+msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an \"uber-jar\", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
msgstr "Web Beansはサーブレットコンテナの中でWebアプリケーションライブラリとして使われるべきです。あなたがすべきことは、WEB-INF/lib 中に webbeans-servlet.jar を置くことです。webbeans-serv;et.jar(←TYPO!!!) はあなたの便利のために提供された\"スーパーjar\"です。代わりに、あなたは以下のコンポーネントjarを使うことも出来ます。"
#. Tag: para
@@ -72,9 +72,9 @@ msgstr "あなたは web.xml に(Web Beansをブートして
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
"\n"
" org.jboss.webbeans.environment.servlet.Listener\n"
@@ -87,18 +87,18 @@ msgstr "Tomcat"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
+msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
msgstr "Tomcatは読み取り専用のJNDIを持っていて、従ってWeb Beansは自動的にはマネージャをバインドすることができません。マネージャをJNDIにバインドするために、あなたは META-INF/context.xml に以下を追加すべきです。"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<Context>\n"
-" <Resource name="BeanManager" \n"
-" auth="Container"\n"
-" type="javax.enterprise.inject.spi.BeanManager"\n"
-" factory="org.jboss.weld.resources.ManagerObjectFactory"/>\n"
-"</Context>"
+"<Context>\n"
+" <Resource name=\"BeanManager\" \n"
+" auth=\"Container\"\n"
+" type=\"javax.enterprise.inject.spi.BeanManager\"\n"
+" factory=\"org.jboss.weld.resources.ManagerObjectFactory\"/>\n"
+"</Context>"
msgstr ""
"web.xml に以下を追加すること
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<resource-env-ref>\n"
-" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
-" <resource-env-ref-type>\n"
+"<resource-env-ref>\n"
+" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
+" <resource-env-ref-type>\n"
" javax.enterprise.inject.spi.BeanManager\n"
-" </resource-env-ref-type>\n"
-"</resource-env-ref>"
+" </resource-env-ref-type>\n"
+"</resource-env-ref>"
msgstr ""
"\n"
" \n"
@@ -147,27 +147,27 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
+msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
msgstr "Tomcatは読み取り専用のJNDIを持っていて、従ってWeb Beansは自動的にはマネージャをバインドすることができません。マネージャをJNDIにバインドするために、あなたは META-INF/context.xml に以下を追加すべきです。"
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.mortbay.jetty.plus.naming.Resource">\n"
-" <Arg><Ref id="webAppCtx"/></Arg> \n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.mortbay.jetty.plus.naming.Resource\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg> \n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure>"
msgstr ""
#. Tag: para
@@ -178,22 +178,22 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://www.eclipse.org/jetty/configure.dtd">\n"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://www.eclipse.org/jetty/configure.dtd\">\n"
"\n"
-"<Configure id="webAppCtx" class="org.eclipse.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.eclipse.jetty.plus.jndi.Resource">\n"
-" <Arg> <Ref id="webAppCtx"/> </Arg>\n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure> "
+"<Configure id=\"webAppCtx\" class=\"org.eclipse.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.eclipse.jetty.plus.jndi.Resource\">\n"
+" <Arg> <Ref id=\"webAppCtx\"/> </Arg>\n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure> "
msgstr ""
#. Tag: para
@@ -203,7 +203,7 @@ msgstr "そして、 web.xml に以下を追加すること
#. Tag: para
#, no-c-format
-msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
+msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
msgstr ""
#. Tag: para
@@ -213,19 +213,19 @@ msgstr "Tomcatは java:comp/env にエンティティをバ
#. Tag: para
#, fuzzy, no-c-format
-msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file META-INF/jetty-web.xml with the following content to your war:"
+msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file WEB-INF/jetty-web.xml with the following content to your war:"
msgstr "Web Beansは、Tomcatへのサーブレットインジェクションもサポートします。これを有効化するために、 $TOMCAT_HOME/lib に webbeans-tomcat-support.jar を置いて、 META-INF/context.xml に下記を追加します。"
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <Call class="org.jboss.weld.environment.jetty.WeldServletHandler" name="process">\n"
-" <Arg><Ref id="webAppCtx"/></Arg>\n"
-" </Call>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <Call class=\"org.jboss.weld.environment.jetty.WeldServletHandler\" name=\"process\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg>\n"
+" </Call>\n"
+"</Configure>"
msgstr ""
#. Tag: title
@@ -235,7 +235,7 @@ msgstr "Java SE"
#. Tag: para
#, fuzzy, no-c-format
-msgid "In addition to improved integration of the Enterprise Java stack, the "Contexts and Dependency Injection for the Java EE platform" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
+msgid "In addition to improved integration of the Enterprise Java stack, the \"Contexts and Dependency Injection for the Java EE platform\" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
msgstr "エンタープライズJavaスタックの向上した統合から離れて、Web Beansは最先端のタイプセーフ、ステートフルな依存性注入フレームワークも提供します。これは広い範囲のアプリケーションタイプ(エンタープライズでもそうでなくても)で有効です。これを推進するために、Web BeansはどんなEnterprise Editionの機能であってもJava Standard Edition環境でも独立して実行するためのシンプルな手段を提供します。"
#. Tag: para
@@ -295,7 +295,7 @@ msgstr "開発者の負担軽減のために、Web BeansはWeb Beansマネージ
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Parameters List<String> params;"
+msgid "@Inject @Parameters List<String> params;"
msgstr ""
#. Tag: programlisting
@@ -315,7 +315,7 @@ msgstr "コマンドラインパラメータは @Deployed ManagerContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
+msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
msgstr ""
#. Tag: para
@@ -367,17 +367,17 @@ msgstr "Web Beans SEアプリケーションは以下のメインメソッドを
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "java org.jboss.weld.environment.se.StartMain <args>"
+msgid "java org.jboss.weld.environment.se.StartMain <args>"
msgstr "]]>"
#. Tag: title
#, no-c-format
-msgid "Programatic Bootstrap API"
+msgid "Programmatic Bootstrap API"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
+msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
msgstr ""
#. Tag: programlisting
@@ -403,10 +403,10 @@ msgid ""
"{\n"
"\n"
" /** Provides access to all beans within the application. */\n"
-" public Instance<Object> instance() {...}\n"
+" public Instance<Object> instance() {...}\n"
"\n"
" /** Provides access to all events within the application. */\n"
-" public Event<Object> event() {...}\n"
+" public Event<Object> event() {...}\n"
"\n"
" /** Provides direct access to the BeanManager. */\n"
" public BeanManager getBeanManager() {...}\n"
@@ -416,7 +416,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
+msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
msgstr ""
#. Tag: programlisting
@@ -456,22 +456,22 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
+msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans>\n"
-" <decorators>\n"
-" <decorator>org.jboss.weld.environment.se.threading.RunnableDecorator</decorator>\n"
-" </decorator>\n"
-"</beans>"
+"<beans>\n"
+" <decorators>\n"
+" <class>org.jboss.weld.environment.se.threading.RunnableDecorator</class>\n"
+" </decorator>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situtations where you would otherwise have used ThreadLocal directly, which are typically rare."
+msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situations where you would otherwise have used ThreadLocal directly, which are typically rare."
msgstr ""
#. Tag: title
@@ -481,7 +481,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
+msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ja-JP/events.po b/docs/reference/src/main/docbook/ja-JP/events.po
index 56bc0b4e798..d3f90353d69 100644
--- a/docs/reference/src/main/docbook/ja-JP/events.po
+++ b/docs/reference/src/main/docbook/ja-JP/events.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-04-30 23:50+0900\n"
"Last-Translator: Fusayuki Minamoto \n"
"Language-Team: none\n"
@@ -36,7 +36,7 @@ msgstr "イベントプロデューサはオブザーバから分離されてい
#. Tag: para
#, fuzzy, no-c-format
-msgid "observers can specify a combination of "selectors" to narrow the set of event notifications they will receive, and"
+msgid "observers can specify a combination of \"selectors\" to narrow the set of event notifications they will receive, and"
msgstr "オブザーバは \"セレクタ\"の組み合わせを指定することで、受信するイベント通知の集まりを狭めることが可能です"
#. Tag: para
@@ -46,7 +46,7 @@ msgstr "オブザーバは直ちにに通知を受信するか、あるいは現
#. Tag: para
#, no-c-format
-msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
+msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
msgstr ""
#. Tag: title
@@ -61,7 +61,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
+msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
msgstr ""
#. Tag: programlisting
@@ -104,7 +104,7 @@ msgstr "only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
+msgid "An observer method need not specify any event qualifiers—in this case it is interested in only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
msgstr "オブザーバメソッドはイベントバインディングを指定する必要はありません このケースでは特定のタイプの すべて のイベントに関心があります。もしイベントバインディングを指定するのであれば、イベントバインディングを持つイベントだけに関心があります。"
#. Tag: para
@@ -129,7 +129,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Event<Document> documentEvent;"
+msgid "@Inject @Any Event<Document> documentEvent;"
msgstr " documentEvent]]>"
#. Tag: para
@@ -184,7 +184,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
+msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
msgstr " documentUpdatedEvent]]>"
#. Tag: para
@@ -204,12 +204,12 @@ msgstr "fire() へ渡されるイベントバインディン
#. Tag: para
#, no-c-format
-msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
+msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
+msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
msgstr "(){} );]]>"
#. Tag: para
@@ -224,7 +224,7 @@ msgstr "トランザクション型オブザーバ"
#. Tag: para
#, no-c-format
-msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
+msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
msgstr ""
#. Tag: para
@@ -286,7 +286,7 @@ msgstr "イベントバインディングタイプはイベントプロデュー
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
+msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
msgstr " LoggedInEvent;}}]]>"
#. Tag: para
@@ -298,7 +298,7 @@ msgstr "別の方法では、イベントバインディングタイプのメン
#, fuzzy, no-c-format
msgid ""
"abstract class RoleBinding \n"
-" extends AnnotationLiteral<Role> \n"
+" extends AnnotationLiteral<Role> \n"
" implements Role {}"
msgstr ""
" blogEvent;\n"
"...\n"
@@ -442,12 +442,12 @@ msgid ""
"\n"
" @PersistenceContext EntityManager em;\n"
" \n"
-" List<Product> products;\n"
+" List<Product> products;\n"
"\n"
" @Produces @Catalog \n"
-" List<Product> getCatalog() {\n"
+" List<Product> getCatalog() {\n"
" if (products==null) {\n"
-" products = em.createQuery("select p from Product p where p.deleted = false")\n"
+" products = em.createQuery(\"select p from Product p where p.deleted = false\")\n"
" .getResultList();\n"
" }\n"
" return products;\n"
@@ -489,16 +489,16 @@ msgid ""
"@Stateless\n"
"public class ProductManager {\n"
" @PersistenceContext EntityManager em;\n"
-" @Inject @Any Event<Product> productEvent;\n"
+" @Inject @Any Event<Product> productEvent;\n"
"\n"
" public void delete(Product product) {\n"
" em.delete(product);\n"
-" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
" }\n"
" \n"
" public void persist(Product product) {\n"
" em.persist(product);\n"
-" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
" }\n"
" ...\n"
"}"
diff --git a/docs/reference/src/main/docbook/ja-JP/example.po b/docs/reference/src/main/docbook/ja-JP/example.po
index 5059726ae25..bbf5bb8a46a 100644
--- a/docs/reference/src/main/docbook/ja-JP/example.po
+++ b/docs/reference/src/main/docbook/ja-JP/example.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-06-09 03:51+0900\n"
"Last-Translator: Shinobu NOGAMI \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "JSF Web アプリケーションサンプル"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
+msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
msgstr "完全な例でこの考えを説明しましょう。JSF を 使用するアプリケーションとしてユーザのログイン / ログアウトを実装します。まず最初に、ログインしている間にユーザ名とパスワードを保持しておくための Web Bean を定義するでしょう:"
#. Tag: programlisting
@@ -63,18 +63,18 @@ msgstr "この Web Bean は、以下の JSF フォームのログインプロン
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:form>\n"
-" <h:panelGrid columns="2" rendered="#{!login.loggedIn}">\n"
-" <f:validateBean>\n"
-" <h:outputLabel for="username">Username:</h:outputLabel>\n"
-" <h:inputText id="username" value="#{credentials.username}"/>\n"
-" <h:outputLabel for="password">Password:</h:outputLabel>\n"
-" <h:inputSecret id="password" value="#{credentials.password}"/>\n"
-" </f:validateBean>\n"
-" </h:panelGrid>\n"
-" <h:commandButton value="Login" action="#{login.login}" rendered="#{!login.loggedIn}"/>\n"
-" <h:commandButton value="Logout" action="#{login.logout}" rendered="#{login.loggedIn}"/>\n"
-"</h:form>"
+"<h:form>\n"
+" <h:panelGrid columns=\"2\" rendered=\"#{!login.loggedIn}\">\n"
+" <f:validateBean>\n"
+" <h:outputLabel for=\"username\">Username:</h:outputLabel>\n"
+" <h:inputText id=\"username\" value=\"#{credentials.username}\"/>\n"
+" <h:outputLabel for=\"password\">Password:</h:outputLabel>\n"
+" <h:inputSecret id=\"password\" value=\"#{credentials.password}\"/>\n"
+" </f:validateBean>\n"
+" </h:panelGrid>\n"
+" <h:commandButton value=\"Login\" action=\"#{login.login}\" rendered=\"#{!login.loggedIn}\"/>\n"
+" <h:commandButton value=\"Logout\" action=\"#{login.logout}\" rendered=\"#{login.loggedIn}\"/>\n"
+"</h:form>"
msgstr ""
"\n"
" \n"
@@ -121,7 +121,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
+msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
msgstr ""
#. Tag: para
@@ -141,10 +141,10 @@ msgid ""
" private User user;\n"
" \n"
" public void login() {\n"
-" List<User> results = userDatabase.createQuery(\n"
-" "select u from User u where u.username = :username and u.password = :password")\n"
-" .setParameter("username", credentials.getUsername())\n"
-" .setParameter("password", credentials.getPassword())\n"
+" List<User> results = userDatabase.createQuery(\n"
+" \"select u from User u where u.username = :username and u.password = :password\")\n"
+" .setParameter(\"username\", credentials.getUsername())\n"
+" .setParameter(\"password\", credentials.getPassword())\n"
" .getResultList();\n"
" \n"
" if (!results.isEmpty()) {\n"
@@ -290,14 +290,14 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:panelGroup rendered="#{login.loggedIn}">\n"
+"<h:panelGroup rendered=\"#{login.loggedIn}\">\n"
" signed in as #{currentUser.username}\n"
-"</h:panelGroup>"
+"</h:panelGroup>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
+msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
msgstr "うまくいけば、このサンプルから Web Bean プログラミングモデルの感触をつかむことができます。次の章では、 Web Beans の依存性注入 (dependency injection) をより深く説明します。"
#~ msgid "Of course, @LoggedIn is a binding annotation:"
diff --git a/docs/reference/src/main/docbook/ja-JP/extend.po b/docs/reference/src/main/docbook/ja-JP/extend.po
index 7a6bc7cf56a..90f79998556 100644
--- a/docs/reference/src/main/docbook/ja-JP/extend.po
+++ b/docs/reference/src/main/docbook/ja-JP/extend.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-04-27 12:26+0900\n"
"Last-Translator: wadahiro \n"
"Language-Team: none\n"
@@ -76,7 +76,7 @@ msgstr "Beanクラス"
#. Tag: para
#, no-c-format
-msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
+msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
msgstr ""
#. Tag: programlisting
@@ -164,15 +164,15 @@ msgid ""
"class MyExtension implements Extension {\n"
" \n"
" void beforeBeanDiscovery(@Observes BeforeBeanDiscovery bbd) {\n"
-" Logger.global.debug("beginning the scanning process");\n"
+" Logger.global.debug(\"beginning the scanning process\");\n"
" }\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
-" Logger.global.debug("scanning type: " + pat.getAnnotatedType().getJavaClass().getName());\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" Logger.global.debug(\"scanning type: \" + pat.getAnnotatedType().getJavaClass().getName());\n"
" } \n"
"\n"
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd) {\n"
-" Logger.global.debug("finished the scanning process");\n"
+" Logger.global.debug(\"finished the scanning process\");\n"
" }\n"
" \n"
"}"
@@ -180,7 +180,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
+msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
msgstr ""
#. Tag: programlisting
@@ -188,7 +188,7 @@ msgstr ""
msgid ""
"class MyExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" //tell the container to ignore the type if it is annotated @Ignore\n"
" if ( pat.getAnnotatedType().isAnnotionPresent(Ignore.class) ) pat.veto(); \n"
" } \n"
@@ -203,7 +203,7 @@ msgstr "Web Beansを拡張するための中枢部はManager
#. Tag: programlisting
#, no-c-format
-msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
+msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
msgstr ""
#. Tag: title
@@ -220,31 +220,31 @@ msgstr "Managerインタフェースで、プログラミン
#, no-c-format
msgid ""
"public interface BeanManager {\n"
-" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
-" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
-" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
-" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
-" public Set<Bean<?>> getBeans(String name);\n"
-" public Bean<?> getPassivationCapableBean(String id);\n"
-" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
+" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
+" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
+" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
+" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
+" public Set<Bean<?>> getBeans(String name);\n"
+" public Bean<?> getPassivationCapableBean(String id);\n"
+" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
" public void validate(InjectionPoint injectionPoint);\n"
" public void fireEvent(Object event, Annotation... qualifiers);\n"
-" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
-" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
-" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
-" public boolean isScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
-" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
-" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
-" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
-" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
-" public Context getContext(Class<? extends Annotation> scopeType);\n"
+" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
+" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
+" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
+" public boolean isScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
+" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
+" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
+" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
+" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
+" public Context getContext(Class<? extends Annotation> scopeType);\n"
" public ELResolver getELResolver();\n"
" public ExpressionFactory wrapExpressionFactory(ExpressionFactory expressionFactory);\n"
-" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
-" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
+" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
+" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
"}"
msgstr ""
@@ -265,7 +265,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's study some of the interfaces exposed by the BeanManager."
+msgid "Let's study some of the interfaces exposed by the BeanManager."
msgstr "Web Beansを拡張するための中枢部はManagerオブジェクトです。"
#. Tag: title
@@ -280,21 +280,21 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to instatiate the object itself, and so only method and field injection will be supported."
+msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to insntatiate the object itself, and so only method and field injection will be supported."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"//get the BeanManager from JNDI\n"
-"BeanManager beanManager = (BeanManager) new InitialContext().lookup("java:comp/BeanManager");\n"
+"BeanManager beanManager = (BeanManager) new InitialContext().lookup(\"java:comp/BeanManager\");\n"
"\n"
"//CDI uses an AnnotatedType object to read the annotations of a class\n"
-"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
+"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
"\n"
"//The extension uses an InjectionTarget to delegate instantiation, dependency injection \n"
"//and lifecycle callbacks to the CDI container\n"
-"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
+"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
"\n"
"//each instance needs its own CDI CreationalContext\n"
"CreationalContext ctx = beanManager.createCreationalContext(null);\n"
@@ -324,33 +324,33 @@ msgstr "抽象クラスであるBeanのインスタンスはW
#. Tag: para
#, no-c-format
-msgid "The Bean interface exposes all the interesting things we dicussed in ."
+msgid "The Bean interface exposes all the interesting things we discussed in ."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"public interface Bean<T> extends Contextual<T> {\n"
-" public Set<Type> getTypes();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Class<? extends Annotation> getScope();\n"
+"public interface Bean<T> extends Contextual<T> {\n"
+" public Set<Type> getTypes();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Class<? extends Annotation> getScope();\n"
" public String getName();\n"
-" public Set<Class<? extends Annotation>> getStereotypes();\n"
-" public Class<?> getBeanClass();\n"
+" public Set<Class<? extends Annotation>> getStereotypes();\n"
+" public Class<?> getBeanClass();\n"
" public boolean isAlternative();\n"
" public boolean isNullable();\n"
-" public Set<InjectionPoint> getInjectionPoints();\n"
+" public Set<InjectionPoint> getInjectionPoints();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's an easy way to find out what beans exist in the application:"
+msgid "There's an easy way to find out what beans exist in the application:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
+msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
msgstr ""
#. Tag: para
@@ -370,7 +370,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
+msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
msgstr ""
#. Tag: programlisting
@@ -381,49 +381,49 @@ msgid ""
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd, BeanManager bm) {\n"
" \n"
" //use this to read annotations of the class\n"
-" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
+" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
"\n"
" //use this to instantiate the class and inject dependencies\n"
-" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
+" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
"\n"
-" abd.addBean( new Bean<SecurityManager>() {\n"
+" abd.addBean( new Bean<SecurityManager>() {\n"
"\n"
" @Override\n"
-" public Class<?> getBeanClass() {\n"
+" public Class<?> getBeanClass() {\n"
" return SecurityManager.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
" public String getName() {\n"
-" return "securityManager";\n"
+" return \"securityManager\";\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getQualifiers() {\n"
-" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
-" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
-" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
+" public Set<Annotation> getQualifiers() {\n"
+" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
+" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
+" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
" return qualifiers;\n"
" }\n"
"\n"
" @Override\n"
-" public Class<? extends Annotation> getScope() {\n"
+" public Class<? extends Annotation> getScope() {\n"
" return SessionScoped.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Class<? extends Annotation>> getStereotypes() {\n"
+" public Set<Class<? extends Annotation>> getStereotypes() {\n"
" return Collections.emptySet();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypes() {\n"
-" Set<Type> types = new HashSet<Type>();\n"
+" public Set<Type> getTypes() {\n"
+" Set<Type> types = new HashSet<Type>();\n"
" types.add(SecurityManager.class);\n"
" types.add(Object.class);\n"
" return types;\n"
@@ -440,7 +440,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
+" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
" SecurityManager instance = it.produce(ctx);\n"
" it.inject(instance, ctx);\n"
" it.postConstruct(instance);\n"
@@ -449,7 +449,7 @@ msgid ""
"\n"
" @Override\n"
" public void destroy(SecurityManager instance, \n"
-" CreationalContext<SecurityManager> ctx) {\n"
+" CreationalContext<SecurityManager> ctx) {\n"
" it.preDestroy(instance);\n"
" it.dispose(instance);\n"
" ctx.release();\n"
@@ -478,7 +478,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
+msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
msgstr ""
#. Tag: programlisting
@@ -486,38 +486,38 @@ msgstr ""
msgid ""
"public class QualifiedNameExtension implements Extension {\n"
"\n"
-" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
+" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
"\n"
" //wrap this to override the annotations of the class\n"
-" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
+" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
" \n"
-" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
+" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
"\n"
" @Override\n"
-" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
+" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
" return at.getConstructors();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedField<? super X>> getFields() {\n"
+" public Set<AnnotatedField<? super X>> getFields() {\n"
" return at.getFields();\n"
" }\n"
"\n"
" @Override\n"
-" public Class<X> getJavaClass() {\n"
+" public Class<X> getJavaClass() {\n"
" return at.getJavaClass();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
+" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
" return at.getMethods();\n"
" }\n"
"\n"
" @Override\n"
-" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
+" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
" if ( Named.class.equals(annType) ) {\n"
" class NamedLiteral \n"
-" extends AnnotationLiteral<Named> \n"
+" extends AnnotationLiteral<Named> \n"
" implements Named {\n"
" @Override\n"
" public String value() {\n"
@@ -526,7 +526,7 @@ msgid ""
" final String qualifiedName;\n"
" if ( pkg.isAnnotationPresent(Named.class) ) {\n"
" qualifiedName = pkg.getAnnotation(Named.class).value() \n"
-" + '.' + unqualifiedName;\n"
+" + '.' + unqualifiedName;\n"
" }\n"
" else {\n"
" qualifiedName = unqualifiedName;\n"
@@ -542,7 +542,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getAnnotations() {\n"
+" public Set<Annotation> getAnnotations() {\n"
" return at.getAnnotations();\n"
" }\n"
"\n"
@@ -552,12 +552,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypeClosure() {\n"
+" public Set<Type> getTypeClosure() {\n"
" return at.getTypeClosure();\n"
" }\n"
"\n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
" return at.isAnnotationPresent(annType);\n"
" }\n"
" \n"
@@ -571,7 +571,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
+msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
msgstr ""
#. Tag: programlisting
@@ -579,17 +579,17 @@ msgstr ""
msgid ""
"class ServiceAlternativeExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" \n"
-" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
+" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
" \n"
" if ( Service.class.isAssignableFrom( type.getJavaClass() ) ) {\n"
" \n"
" //if the class implements Service, make it an @Alternative\n"
-" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
+" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
" \n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
" return annotationType.equals(Alternative.class) ? \n"
" true : type.isAnnotationPresent(annotationType);\n"
" }\n"
@@ -622,7 +622,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
+msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
msgstr ""
#. Tag: programlisting
@@ -642,25 +642,25 @@ msgstr ""
msgid ""
"public class ConfigExtension implements Extension {\n"
"\n"
-"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
+"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
"\t\t\n"
"\t\t//wrap this to intercept the component lifecycle\n"
-"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
+"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
"\t \n"
-" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
+" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
" \n"
" //use this to read annotations of the class and its members\n"
-" AnnotatedType<X> at = pit.getAnnotatedType();\n"
+" AnnotatedType<X> at = pit.getAnnotatedType();\n"
" \n"
" //read the properties file\n"
-" String propsFileName = at.getClass().getSimpleName() + ".properties";\n"
+" String propsFileName = at.getClass().getSimpleName() + \".properties\";\n"
" InputStream stream = at.getJavaClass().getResourceAsStream(propsFileName);\n"
" if (stream!=null) {\n"
" \n"
" try {\n"
" Properties props = new Properties();\n"
" props.load(stream);\n"
-" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
+" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
" String fieldName = property.getKey().toString();\n"
" Object value = property.getValue();\n"
" try {\n"
@@ -672,7 +672,7 @@ msgid ""
" else {\n"
" //TODO: do type conversion automatically\n"
" pit.addDefinitionError( new InjectionException(\n"
-" "field is not of type String: " + field ) );\n"
+" \"field is not of type String: \" + field ) );\n"
" }\n"
" }\n"
" catch (NoSuchFieldException nsfe) {\n"
@@ -688,14 +688,14 @@ msgid ""
" }\n"
" }\n"
" \n"
-" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
+" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
"\n"
" @Override\n"
-" public void inject(X instance, CreationalContext<X> ctx) {\n"
+" public void inject(X instance, CreationalContext<X> ctx) {\n"
" it.inject(instance, ctx);\n"
" \n"
" //set the values onto the new instance of the component\n"
-" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
+" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
" try {\n"
" configuredValue.getKey().set(instance, configuredValue.getValue());\n"
" }\n"
@@ -721,12 +721,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
-" public X produce(CreationalContext<X> ctx) {\n"
+" public X produce(CreationalContext<X> ctx) {\n"
" return it.produce(ctx);\n"
" }\n"
" \n"
@@ -741,7 +741,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
+msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
msgstr ""
#. Tag: title
@@ -758,9 +758,9 @@ msgstr "ContextインタフェースはWeb Beansへの新し
#, fuzzy, no-c-format
msgid ""
"public interface Context {\n"
-" public Class<? extends Annotation> getScope();\n"
-" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
-" public <T> T get(Contextual<T> contextual);\n"
+" public Class<? extends Annotation> getScope();\n"
+" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
+" public <T> T get(Contextual<T> contextual);\n"
" boolean isActive();\n"
"}"
msgstr ""
diff --git a/docs/reference/src/main/docbook/ja-JP/gettingstarted.po b/docs/reference/src/main/docbook/ja-JP/gettingstarted.po
index de430bc05a3..4ab2ea47127 100644
--- a/docs/reference/src/main/docbook/ja-JP/gettingstarted.po
+++ b/docs/reference/src/main/docbook/ja-JP/gettingstarted.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml \n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-19 20:26+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, Glassfish 3.0 or any compliant Java EE 6 container."
+msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, GlassFish 3.0 or any compliant Java EE 6 container."
msgstr ""
#. Tag: para
@@ -36,7 +36,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To run the examples with the provided build scripts, you'll need the following:"
+msgid "To run the examples with the provided build scripts, you'll need the following:"
msgstr ""
#. Tag: para
@@ -81,12 +81,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
+msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
+msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
msgstr ""
#. Tag: para
@@ -96,7 +96,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
+msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
msgstr ""
#. Tag: title
@@ -106,19 +106,19 @@ msgstr "JBoss AS 5 の使用"
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
+msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
+msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> unzip jboss-6.0.*.zip\n"
-"$> mv jboss-6.0.*/ jboss-as-6.0"
+"$> unzip jboss-6.0.*.zip\n"
+"$> mv jboss-6.0.*/ jboss-as-6.0"
msgstr ""
#. Tag: para
@@ -133,7 +133,7 @@ msgstr "jboss.home=/Applications/jboss-5.0.1.GA"
#. Tag: para
#, fuzzy, no-c-format
-msgid "You're now ready to deploy your first example!"
+msgid "You're now ready to deploy your first example!"
msgstr "これで、最初のサンプルをデプロイする用意ができました。"
#. Tag: para
@@ -144,22 +144,22 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant deploy"
msgstr ""
"$ cd examples/numberguess\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
+msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/jboss-as-6.0\n"
-"$> ./bin/run.sh"
+"$> cd /path/to/jboss-as-6.0\n"
+"$> ./bin/run.sh"
msgstr "$ /Application/jboss-5.0.0.GA/bin/run.sh"
#. Tag: para
@@ -168,11 +168,11 @@ msgid "a Windows command window:"
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
-"$> run"
-msgstr ""
+"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
+"$> run"
+msgstr "$ /Application/jboss-5.0.0.GA/bin/run.sh"
#. Tag: para
#, no-c-format
@@ -227,20 +227,20 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/translator\n"
-"$> ant deploy"
+"$> cd examples/jsf/translator\n"
+"$> ant deploy"
msgstr ""
"$ cd examples/translator\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
+msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
+msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
msgstr "ここでは、コンテキストパスを親切なurl (http://localhost:8080/webbeans-translator) に設定します。"
#. Tag: title
@@ -250,41 +250,43 @@ msgstr "GlassFish の使用"
#. Tag: para
#, no-c-format
-msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
+msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
+msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> chmod 755 glassfish-v3-unix.sh\n"
-"$> ./glassfish-v3-unix.sh"
+"$> chmod 755 glassfish-v3-unix.sh\n"
+"$> ./glassfish-v3-unix.sh"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
+msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
+msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
-"$> ant package"
+"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
+"$> ant package"
msgstr ""
+"$ cd examples/numberguess\n"
+"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
+msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
msgstr ""
#. Tag: para
@@ -294,12 +296,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin start-domain domain1"
+msgid "$> asadmin start-domain domain1"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on "Applications", then click on the "Deploy..." button under the heading "Applications" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
+msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on \"Applications\", then click on the \"Deploy...\" button under the heading \"Applications\" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
msgstr ""
#. Tag: para
@@ -309,7 +311,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin deploy target/weld-numberguess.war"
+msgid "$> asadmin deploy target/weld-numberguess.war"
msgstr ""
#. Tag: para
@@ -329,24 +331,24 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
+msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
+msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
msgstr "Tomcat 6.0.18 以降を tomcat.apache.org からダウンロードして展開する必要があります。例:"
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "$> unzip apache-tomcat-6.0.18.zip"
+msgid "$> unzip apache-tomcat-6.0.18.zip"
msgstr ""
""
#. Tag: para
#, no-c-format
-msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
+msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
msgstr ""
#. Tag: title
@@ -356,7 +358,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
+msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
msgstr ""
#. Tag: programlisting
@@ -366,7 +368,7 @@ msgstr "tomcat.home=/Applications/apache-tomcat-6.0.18"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now you're ready to deploy the numberguess example to Tomcat!"
+msgid "Now you're ready to deploy the numberguess example to Tomcat!"
msgstr "Tomcat への numberguess サンプルのデプロイ:"
#. Tag: para
@@ -377,15 +379,15 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant tomcat.deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant tomcat.deploy"
msgstr ""
"$ cd examples/numberguess\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with "tomcat."."
+msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with \"tomcat.\"."
msgstr ""
#. Tag: para
@@ -410,21 +412,21 @@ msgstr "ant undeploy - サーバからサンプルを削除
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
+msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/apache-tomcat-6\n"
-"$> ./bin/start.sh"
+"$> cd /path/to/apache-tomcat-6\n"
+"$> ./bin/start.sh"
msgstr "$ /Applications/apache-tomcat-6.0.18/bin/startup.sh"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
-"$> start"
+"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
+"$> start"
msgstr ""
""
@@ -441,12 +443,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
+msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
+msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
msgstr ""
#. Tag: para
@@ -456,7 +458,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<user username="admin" password="" roles="manager"/>"
+msgid "<user username=\"admin\" password=\"\" roles=\"manager\"/>"
msgstr ""
#. Tag: para
@@ -466,7 +468,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
+msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
msgstr ""
#. Tag: para
@@ -476,7 +478,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn tomcat:redeploy -Ptomcat"
+msgid "$> mvn tomcat:redeploy -Ptomcat"
msgstr ""
#. Tag: para
@@ -491,7 +493,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace tomcat:run -Ptomcat"
+msgid "$> mvn war:inplace tomcat:run -Ptomcat"
msgstr ""
#. Tag: para
@@ -501,12 +503,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Ptomcat"
+msgid "$> mvn compile war:inplace -Ptomcat"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
+msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
msgstr ""
#. Tag: title
@@ -521,12 +523,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
+msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
+msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
msgstr ""
#. Tag: para
@@ -537,8 +539,8 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> mvn war:inplace jetty:run -Pjetty"
+"$> cd examples/jsf/numberguess\n"
+"$> mvn war:inplace jetty:run -Pjetty"
msgstr ""
""
@@ -555,7 +557,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Pjetty"
+msgid "$> mvn compile war:inplace -Pjetty"
msgstr ""
#. Tag: para
@@ -565,7 +567,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclispe[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
+msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclipse[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
msgstr ""
#. Tag: para
@@ -575,7 +577,7 @@ msgstr "Eclipse プロジェクトの作成"
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
+msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
msgstr ""
#. Tag: para
@@ -585,12 +587,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace -Pjetty-ide"
+msgid "$> mvn war:inplace -Pjetty-ide"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using "Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
+msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using \"Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ja-JP/injection.po b/docs/reference/src/main/docbook/ja-JP/injection.po
index 1c32b88d0f8..3a8f6cab20e 100644
--- a/docs/reference/src/main/docbook/ja-JP/injection.po
+++ b/docs/reference/src/main/docbook/ja-JP/injection.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-06-02 01:32+0900\n"
"Last-Translator: Daisuke Sano \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "依存性注入"
#. Tag: para
#, no-c-format
-msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
+msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
msgstr ""
#. Tag: title
@@ -146,7 +146,7 @@ msgstr "次に、Web Beanマネージャは、Web Beanの、注入すべきす
#. Tag: para
#, fuzzy, no-c-format
-msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
+msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
msgstr "次に、Web Beanマネージャは、Web Beanの、すべての初期化メソッドを実行する"
#. Tag: para
@@ -182,7 +182,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
+msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
msgstr ""
#. Tag: title
@@ -192,7 +192,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
+msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
msgstr "Web Beansの仕様では、タイプセーフ解決アルゴリズムが定義されており、Web Beanマネージャは、ある注入箇所への注入を行う際、これにのっとって、注入すべきWeb Beanを特定します。このアルゴリズムは最初は複雑に感じますが、一度理解してしまえば、とても直観的なものです。タイプセーフ解決アルゴリズムは、システムの初期化時に使われます。これは、もしWeb Beanの依存性が充たされない場合には、マネージャがUnsatisfiedDependencyExceptionやAmbiguousDependencyExceptionをスローすることによって、即座にそれをユーザに通知することを意味します。"
#. Tag: para
@@ -217,12 +217,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
+msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
+msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
msgstr ""
#. Tag: title
@@ -383,7 +383,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you may be thinking, "What's the different between using a qualifier and just specifying the exact implementation class you want?" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alterative implementations of @Asynchronous PaymentProcessor!"
+msgid "Now, you may be thinking, \"What's the different between using a qualifier and just specifying the exact implementation class you want?\" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alternative implementations of @Asynchronous PaymentProcessor!"
msgstr ""
#. Tag: title
@@ -393,7 +393,7 @@ msgstr "シンプルWeb Beanは@PostConstructと@Pre
#. Tag: para
#, no-c-format
-msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to decare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
+msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to declare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
msgstr ""
#. Tag: para
@@ -405,7 +405,7 @@ msgstr ""
#, no-c-format
msgid ""
"@Inject \n"
-"void initServices(@Any Instance<Service> services) { \n"
+"void initServices(@Any Instance<Service> services) { \n"
" for (Service service: services) {\n"
" service.init();\n"
" }\n"
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then we select one of the possible member values when appling the qualifier:"
+msgid "Then we select one of the possible member values when applying the qualifier:"
msgstr ""
#. Tag: programlisting
@@ -462,7 +462,7 @@ msgid ""
"@Target({METHOD, FIELD, PARAMETER, TYPE})\n"
"public @interface PayBy {\n"
" PaymentMethod value();\n"
-" @Nonbinding String comment() default "";\n"
+" @Nonbinding String comment() default \"\";\n"
"}"
msgstr ""
"this FAQ for step-by-step instructions for how to resolve an ambigous resolution exception between a raw bean type and a producer method that returns the same bean type."
+msgid "See this FAQ for step-by-step instructions for how to resolve an ambiguous resolution exception between a raw bean type and a producer method that returns the same bean type."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Just remember: "There can be only one.""
+msgid "Just remember: \"There can be only one.\""
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
+msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
+msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
msgstr "Web Beansにおける依存性注入を行う際に気をつけるべきことが、もう少しあります。"
#. Tag: title
@@ -645,7 +645,7 @@ msgstr "注入されたWeb Beanのクライアントは、通常、Web Beanイ
#. Tag: para
#, fuzzy, no-c-format
-msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
+msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
msgstr "アプリケーションスコープに結び付けられたWeb Beanが、リクエストスコープに結び付けられたWeb Beanに対する直接的な参照を持っている場合を想像してみてください。アプリケーションスコープのWeb Beanは、たくさんの異なるリクエスト間で共有されます。しかしながら、それぞれのリクエストは、それぞれ異なったリクエストスコープのWeb Beanインスタンスを参照するべきなのです。"
#. Tag: para
@@ -670,7 +670,7 @@ msgstr "次に挙げるJava型はWeb Beanマネージャがプロキシ化する
#. Tag: para
#, fuzzy, no-c-format
-msgid "classes which don't have a non-private constructor with no parameters, and"
+msgid "classes which don't have a non-private constructor with no parameters, and"
msgstr "プライベートでなく、引数を持たないコンストラクタを持たないクラス"
#. Tag: para
@@ -685,7 +685,7 @@ msgstr "配列とプリミティブ型"
#. Tag: para
#, no-c-format
-msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
+msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
msgstr ""
#. Tag: para
@@ -695,7 +695,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "change the type of the injection point to Instance<X>,"
+msgid "change the type of the injection point to Instance<X>,"
msgstr ""
#. Tag: para
@@ -725,7 +725,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But we didn't get around to implementing this yet."
+msgid "But we didn't get around to implementing this yet."
msgstr ""
#. Tag: title
@@ -760,7 +760,7 @@ msgstr "アプリケーションは注入によって、Manager"
#. Tag: para
@@ -795,7 +795,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -810,19 +810,19 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, we need to obtain an instance of our qualifier type. Since annotatons are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
+msgid "Next, we need to obtain an instance of our qualifier type. Since annotations are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"abstract class AsynchronousQualifier\n"
-"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
+"class AsynchronousQualifier\n"
+"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
msgstr ""
" \n"
@@ -837,14 +837,14 @@ msgstr ""
#, fuzzy, no-c-format
msgid ""
"PaymentProcessor p = paymentProcessorSource\n"
-" .select(new AnnotationLiteral<Asynchronous>() {});"
+" .select(new AnnotationLiteral<Asynchronous>() {});"
msgstr ""
"(){});]]>"
#. Tag: para
#, no-c-format
-msgid "We can't use an anonymous class to implement a qualifier type with members."
+msgid "However, we can't use an anonymous class to implement a qualifier type with members."
msgstr ""
#. Tag: para
@@ -892,7 +892,7 @@ msgstr "@Dependentスコープを持ったWeb Beanは、"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
+msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
msgstr "納得できませんか?もう一つの例を見てみましょう。HTTPパラメタを注入するためには、バインディングタイプを定義する必要があります。"
#. Tag: programlisting
@@ -964,8 +964,8 @@ msgstr "このバインディングタイプを注入箇所において、次の
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@HttpParam("username") String username;\n"
-"@HttpParam("password") String password;"
+"@HttpParam(\"username\") String username;\n"
+"@HttpParam(\"password\") String password;"
msgstr ""
""
@@ -980,7 +980,7 @@ msgstr "次のプロデューサメソッドが動作します。"
msgid ""
"class HttpParams\n"
"\n"
-" @Produces @HttpParam("")\n"
+" @Produces @HttpParam(\"\")\n"
" String getParamValue(InjectionPoint ip) {\n"
" ServletRequest request = (ServletRequest) FacesContext.getCurrentInstance().getExternalContext().getRequest();\n"
" return request.getParameter(ip.getAnnotated().getAnnotation(HttpParam.class).value());\n"
@@ -999,7 +999,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own prodcuer for the request and have it injected as a method parameter."
+msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own producer for the request and have it injected as a method parameter."
msgstr ""
#. Tag: para
@@ -1017,8 +1017,8 @@ msgstr "Web BeanマネージャはInjectionPointインタフ
msgid ""
"public interface InjectionPoint { \n"
" public Type getType();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Bean<?> getBean();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Bean<?> getBean();\n"
" public Member getMember();\n"
" public Annotated getAnnotated();\n"
" public boolean isDelegate();\n"
diff --git a/docs/reference/src/main/docbook/ja-JP/interceptors.po b/docs/reference/src/main/docbook/ja-JP/interceptors.po
index 9fbf0b503d7..22df2759996 100644
--- a/docs/reference/src/main/docbook/ja-JP/interceptors.po
+++ b/docs/reference/src/main/docbook/ja-JP/interceptors.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-04-30 23:14+0900\n"
"Last-Translator: Fusayuki Minamoto \n"
"Language-Team: none\n"
@@ -107,7 +107,7 @@ msgstr "インタセプタバインディング"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
+msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
msgstr "Web Beansをトランザクション型として宣言したいと仮定します。最初に必要なことは、次のような、興味のあるWeb Beansを正確に指定するための インタセプタバインディングアノテーション です。"
#. Tag: programlisting
@@ -160,7 +160,7 @@ msgstr "インタセプタの実装"
#. Tag: para
#, fuzzy, no-c-format
-msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
+msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
msgstr "それは素晴らしいことではありますが、どこかでこのトランザクション管理アスペクトを提供するインタセプタを実際に実装する必要があります。必要なのは、標準的なEJBインタセプタを作成し、それに @Interceptor と @Transactional のアノテーションを付加するだけです。"
#. Tag: programlisting
@@ -222,16 +222,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -262,17 +262,17 @@ msgstr "たとえば、セキュリティインタセプタが Transact
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -375,7 +375,7 @@ msgstr "通常、複数のインタセプタをWeb Beanに結びつけるため
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Secure(rolesAllowed="admin") @Transactional\n"
+"@Secure(rolesAllowed=\"admin\") @Transactional\n"
"public class ShoppingCart { ... }"
msgstr ""
"meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
+msgid "Well, fortunately, CDI works around this missing feature of Java. We may annotate one interceptor binding type with other interceptor binding types (termed a meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
msgstr "幸い、Web BeansはJavaのこの不足機能を補います。あるインタセプタバインディングタイプを他の複数のバインディングタイプにアノテーションとして付加することが許されます。このインタセプタバインディングは推移的です。つまり、最初のインタセプタバインディングを持つ任意のWeb Beanはメタアノテーションとして宣言されたインタセプタバインディングを継承します。"
#. Tag: programlisting
@@ -530,7 +530,7 @@ msgstr "インタセプタはデプロイ時に簡単に無効に設定できな
#. Tag: para
#, fuzzy, 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."
+msgid "the interceptor ordering is non-global — it is determined by the order in which interceptors are listed at the class level."
msgstr "インタセプタの順番はグローバルではない。つまり、クラスレベルでリストされたインタセプタの順番によって決定される"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ja-JP/intro.po b/docs/reference/src/main/docbook/ja-JP/intro.po
index 4293b068dcc..e51727bf999 100644
--- a/docs/reference/src/main/docbook/ja-JP/intro.po
+++ b/docs/reference/src/main/docbook/ja-JP/intro.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-06-09 03:50+0900\n"
"Last-Translator: Shinobu NOGAMI \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
+msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
msgstr "あなたは、すでに最初の Web Bean を書き始めることに夢中ですか。あるいは、たぶん Web Beans 仕様によって、どのような種類のフープを跳ぶことができるのかを不思議に思って疑い深くなっているのかもしれません。朗報なことは、すでにあなたはおそらく数百、もしかすると数千の Web Beans を書いて使用しているかもしれないということです。あなたは最初の書いた Web Bean を思い出すことさえできないかもしれません。"
#. Tag: title
@@ -36,27 +36,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Prior to Java EE 6, there was no clear definition of the term "bean" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications "beans" for years. There were even a couple of different kinds of things called "beans" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a "bean". What we've been missing is a common definition."
+msgid "Prior to Java EE 6, there was no clear definition of the term \"bean\" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications \"beans\" for years. There were even a couple of different kinds of things called \"beans\" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a \"bean\". What we've been missing is a common definition."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
+msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
+msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
+msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now let's see how to create your first bean that actually uses CDI."
+msgid "Now let's see how to create your first bean that actually uses CDI."
msgstr ""
#. Tag: title
@@ -66,14 +66,14 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
+msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
msgstr "様々なアプリケーションで何年間も使っている2つの既存の Java クラスがあると仮定します。1つ目のクラスは、文のリストへ文字列に構文解析します:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
"public class SentenceParser {\n"
-" public List<String> parse(String text) { ... }\n"
+" public List<String> parse(String text) { ... }\n"
"}"
msgstr ""
"TextTranslator はパ
#. Tag: para
#, fuzzy, no-c-format
-msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
+msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
msgstr "あなたが推測しているように、 @Initializer ノテーションは依存性注入と関係があります。@Initializer は、Web Bean のコンストラクタあるいはメソッドに適用することができ、Web Bean をインスタンス化するときに Web Bean マネージャにそのコンストラクタあるいはメソッドを呼ぶ出すように伝えます。Web Beanマネージャは、コンストラクタあるいはメソッドのパラメータに他の Web Beans を注入します。"
#. Tag: para
@@ -181,7 +181,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
+msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
msgstr ""
#. Tag: programlisting
@@ -220,7 +220,7 @@ msgstr "ここで Translator はローカルインターフ
#. Tag: para
#, no-c-format
-msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
+msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
msgstr ""
#. Tag: para
@@ -231,7 +231,7 @@ msgstr "Web Bean、サーブレットあるいは EJB へ注入することに
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
+"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
"...\n"
"public void translate() {\n"
" textTranslatorInstance.get().translate(inputText);\n"
@@ -244,17 +244,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
+msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
+msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
msgstr "システムの初期化時に、Web Bean マネージャはそれぞれのインジェクションポイントの条件を満たすまさに1つの Web Bean が存在することを検証しなければなりません。サンプルで、もし利用可能な Translator の実装がなければ、あるいは SentenceTranslator EJB がデプロイされていなければ、Web Bean マネージャーは、UnsatisfiedDependencyException をスローします。もし1つ以上の Translator の実装が利用可能であれば、Web Beanマネージャは、AmbiguousDependencyException をスローします。"
#. Tag: para
#, no-c-format
-msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
+msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
msgstr ""
#~ msgid "Getting started with Web Beans"
diff --git a/docs/reference/src/main/docbook/ja-JP/next.po b/docs/reference/src/main/docbook/ja-JP/next.po
index 4982d419a2b..353a578488e 100644
--- a/docs/reference/src/main/docbook/ja-JP/next.po
+++ b/docs/reference/src/main/docbook/ja-JP/next.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-04-19 02:20+0900\n"
"Last-Translator: wadahiro \n"
"Language-Team: none\n"
@@ -21,13 +21,13 @@ msgstr "次のステップ"
#. Tag: para
#, no-c-format
-msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
+msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
msgstr ""
# substantiallyってどう訳す
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
+msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
msgstr "Web Beansの参照実装は、http://seamframework.org/WebBeansで開発されています。RI開発チームとWeb Beansのスペックリードはhttp://in.relation.toでブログを書いています。この記事は、大体はそこで書かかれた一連のブログエントリーに基づいています。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ja-JP/part1.po b/docs/reference/src/main/docbook/ja-JP/part1.po
index 8e0e6a0fe97..007a9615a0c 100644
--- a/docs/reference/src/main/docbook/ja-JP/part1.po
+++ b/docs/reference/src/main/docbook/ja-JP/part1.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml \n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-19 20:26+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -126,7 +126,7 @@ msgstr "明示的に破棄する必要がありますか?"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Where should I keep the reference to it when I'm not currently using it?"
+msgid "Where should I keep the reference to it when I'm not currently using it?"
msgstr "直接的に使用していないときに、それへのリファレンスはどこに保持すべきですか?"
#. Tag: para
@@ -141,7 +141,7 @@ msgstr "どのようにこのオブジェクトを他のオブジェクトとの
#. Tag: para
#, no-c-format
-msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
+msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
msgstr ""
#. Tag: para
@@ -171,12 +171,12 @@ msgstr "デコレータ (decorator) ビジネス関心事
#. Tag: para
#, fuzzy, no-c-format
-msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
+msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
msgstr "最も重要なことは、これらすべての機能を Web Beans は タイプセーフ (typesafe) な方法で提供することです。Web Beans は、どのオブジェクトが共同して動作するのに適合しているのかを決定するために、文字列 (String) ベースの識別子を一切使用しません。さらに、オプションとしては残っていますが、XML ファイルもほとんど使用されません。その代わりに Web Beans は、既存の Java オブジェクトモデルで利用可能なタイプ情報と、バインディングアノテーション (binding annotation) と呼ばれる新しいパターンを一緒に使用します。これにより、Web Beans とその依存関係にあるもの、インタセプタ、デコレータ、イベント消費者とが結び付けられます。"
#. Tag: para
#, no-c-format
-msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
+msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
msgstr ""
#. Tag: para
@@ -186,7 +186,7 @@ msgstr "さらに Web Beans は、他との連携の際に必要となるイン
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
+msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
msgstr "Web Beans は、Seam や Guice、Spring を含む多くの現存する Java フレームワークから影響を受けました。しかし、Web Beans はそれ自身とても特徴的な性質を持っています: Seam よりもタイプセーフであり、Spring よりもステートフルであって XML セントリックではなく、Guice よりも多くの Web アプリケーションとエンタープライズアプリケーション向けの機能があります。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ja-JP/part3.po b/docs/reference/src/main/docbook/ja-JP/part3.po
index 7b1076cd2a1..2000d940720 100644
--- a/docs/reference/src/main/docbook/ja-JP/part3.po
+++ b/docs/reference/src/main/docbook/ja-JP/part3.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-07-02 12:31+0900\n"
"Last-Translator: minamoto \n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
+msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
msgstr ""
#. Tag: para
@@ -71,7 +71,7 @@ msgstr "Web Beans における第二のテーマは、 強い型付け
#. Tag: para
#, fuzzy, no-c-format
-msgid "You don't see string-based identifiers in CDI 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!"
+msgid "You don't see string-based identifiers in CDI 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
@@ -141,7 +141,7 @@ msgstr "Web Beans ステレオタイプ は、一歩先
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
+msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
msgstr "現在、もう既に Web Beans のいくつかの先進機能に会う準備が整っています。これらの特徴がコードを妥当性を検査するのがより簡単で、より理解できるようにするために存在することを覚えておいてください。ほとんどの場合、決して実際はこれらの機能を使う 必要はありません 、しかし、賢明にそれらを使用するならば、それらの力を理解必要があります。"
#~ msgid "Even Web Beans XML metadata is strongly typed! There's no compiler for XML, so Web Beans takes advantage of XML schemas to validate the Java types and attributes that appear in XML. This approach turns out to make the XML more literate, just like annotations made our Java code more literate."
diff --git a/docs/reference/src/main/docbook/ja-JP/part4.po b/docs/reference/src/main/docbook/ja-JP/part4.po
index 0f3f7be8ea4..34b564f3485 100644
--- a/docs/reference/src/main/docbook/ja-JP/part4.po
+++ b/docs/reference/src/main/docbook/ja-JP/part4.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-04-25 00:28+0900\n"
"Last-Translator: tagawaman \n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
+msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
msgstr ""
#. Tag: para
@@ -26,7 +26,7 @@ msgstr "我々は既に、Web BeansがどのようにしてEJBとJSFの統合を
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
+msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
msgstr "我々は、Web Beansを使うアプリケーションで、Java EEプラットフォームを最大限に活用する方法を、今まさに知ろうとしています。我々はまた、Web Beansへ持ち運び可能な拡張機能のサポートを提供するサービス プロバイダ インタフェース(SPI)のセットを簡単に得ることができます。あなたがこれらのSPIを直接使う事は一切ないかも知れません。しかし、もしあなたが必要とするならば、これらSPIが存在するという事を知っておくと良いでしょう。最も重要な事は、あなたがサードパーティの拡張機能を使う時にはいつも、あなたは間接的にSPIを、あなたのいいように使うであろうという事なのです。"
#~ msgid "The third theme of Web Beans is integration. Web Beans was designed to work in concert with other technologies, helping the application developer fit the other technologies together. Web Beans is an open technology. It forms a part of the Java EE ecosystem, and is itself the foundation for a new ecosystem of portable extensions and integration with existing frameworks and technologies."
diff --git a/docs/reference/src/main/docbook/ja-JP/part5.po b/docs/reference/src/main/docbook/ja-JP/part5.po
index d17f5df3b68..1a4e43f1363 100644
--- a/docs/reference/src/main/docbook/ja-JP/part5.po
+++ b/docs/reference/src/main/docbook/ja-JP/part5.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-05-03 06:31+0900\n"
"Last-Translator: TANABE Junnichi \n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and Glassfish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
+msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and GlassFish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
msgstr "Web BeansはJSR-299の参照実装で、Java Enterprise EditionアプリケーションにJSR-299サービスを提供するためにJBoss ASとGlassfishにより利用されています。Web Beansはまた、JSR-299仕様により定義された環境とAPIを飛び超え、(TomcatのようなサーブレットコンテナやJava SEのような)多くの他環境と(loggingやJSR-299のXMLディプロイメントデスクリプタの為のXSD生成のような)追加のAPIとモジュールに対するサポートを提供します。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ja-JP/producermethods.po b/docs/reference/src/main/docbook/ja-JP/producermethods.po
index e24bfa0bebc..339c4d6214d 100644
--- a/docs/reference/src/main/docbook/ja-JP/producermethods.po
+++ b/docs/reference/src/main/docbook/ja-JP/producermethods.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-06-23 23:39+0900\n"
"Last-Translator: TANABE Junnichi \n"
"Language-Team: none\n"
@@ -22,7 +22,7 @@ msgstr "プロデューサメソッド"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
+msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
msgstr "Web Beanマネージャがアプリケーションの代わりにオブジェクトのインスタンス化に対して責務を負うときいくらかの発生する制限をプロデューサメソッドは、克服してくれます。それらはWeb BeansでないオブジェクトをWeb Beans環境に統合する最も簡単な方法でもあります。(我々はで2番目のアプローチを見ることになるでしょう。)"
#. Tag: para
@@ -77,7 +77,7 @@ msgstr "実行時にAPIタイプの実装を変える。"
#. Tag: para
#, fuzzy, no-c-format
-msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
+msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
msgstr "特に、プロデューサメソッドによってWeb Beanを利用した実行時ポリモフィズムを利用できるようになります。見てきたように、デプロイメントタイプはデプロイメントの多態性の問題に対するパワフルなソリューションです。しかし、一旦そのシステムがデプロイされると、そのWeb Beanの実装は固定されてしまいます。プロデューサメソッドにはそのような制限はありません。"
#. Tag: programlisting
@@ -162,7 +162,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
+msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
msgstr "今度プロデューサメソッドが呼び出されると、戻されたPaymentStrategyはセッションコンテキストに属することになります。プロデューサメソッドが同じセッションで再び呼び出されることは無いでしょう。"
#. Tag: para
@@ -177,12 +177,12 @@ msgstr "プロデューサメソッドへのインジェクション"
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
+msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
msgstr "上のコードには1つの潜在的な問題があります。CreditCardPaymentStrategyの実装はJavaのnew演算子を使ってインスタンス化されています。アプリケーションにより直接インスタンス化されたオブジェクトは依存性注入の恩恵を受けることができず、インターセプタを持ちません。"
#. Tag: para
#, fuzzy, no-c-format
-msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
+msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
msgstr "これが望むことでないのであれば、私たちはWeb Beanインスタンスを取得するためにプロデューサメソッドに依存性注入することができます。"
#. Tag: programlisting
@@ -214,12 +214,12 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of "promoting" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left "hanging" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
+msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of \"promoting\" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left \"hanging\" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
msgstr "待って!もしCreditCardPaymentStrategyがリクエストスコープのWeb Beanだとしたら?その場合、プロデューサメソッドは現在のリクエストスコープをセッションスコープに\"プロモート\"する効果を持ちます。これはほぼ確実なバグ!リクエストスコープのオブジェクトはセッションが終わる前にWeb Beanマジェージャによって破棄されることになるでしょうが、オブジェクトのリファレンスはセッションスコープに\"ぶら下がった\"ままになるでしょう。このエラーはWeb Beanマジェージャには検知されないでしょうから、Web Beanインスタンスをプロデューサメソッドから戻すときには気をつけてください。"
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
+msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
msgstr "私たちがこのバグを解決する方法が少なくとも3つあります。私たちはCreditCardPaymentStrategyを実装したスコープを変えることができますが、これはWeb Beanの他のクライアントに影響を与えるでしょう。より良い選択肢はプロデューサメソッドのスコープを@Dependentか@RequestScopedに変えることでしょう。"
#. Tag: para
@@ -266,7 +266,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
+msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
msgstr "今度は、CreditCardPaymentStrategyの新たな依存インスタンスが作成され、プロデューサメソッドに渡され、プロデューサメソッドにより戻され、そして最終的にセッションコンテキストに属することになります。そのセッションの最後でPreferencesオブジェクトが破棄されるまで依存オブジェクトは破棄されることは無いでしょう。"
#. Tag: title
diff --git a/docs/reference/src/main/docbook/ja-JP/resources.po b/docs/reference/src/main/docbook/ja-JP/resources.po
index 58477d7553e..195d360eccc 100644
--- a/docs/reference/src/main/docbook/ja-JP/resources.po
+++ b/docs/reference/src/main/docbook/ja-JP/resources.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a nonportable "mapped name"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
+msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a non-portable \"mapped name\"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
msgstr ""
#. Tag: para
@@ -72,35 +72,35 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @WebServiceRef(lookup="java:app/service/Catalog")\n"
+"@Produces @WebServiceRef(lookup=\"java:app/service/Catalog\")\n"
"Catalog catalog;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @Resource(lookup="java:global/env/jdbc/CustomerDatasource") \n"
+"@Produces @Resource(lookup=\"java:global/env/jdbc/CustomerDatasource\") \n"
"@CustomerDatabase Datasource customerDatabase;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceContext(unitName="CustomerDatabase")\n"
+"@Produces @PersistenceContext(unitName=\"CustomerDatabase\")\n"
"@CustomerDatabase EntityManager customerDatabasePersistenceContext;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceUnit(unitName="CustomerDatabase") \n"
+"@Produces @PersistenceUnit(unitName=\"CustomerDatabase\") \n"
"@CustomerDatabase EntityManagerFactory customerDatabasePersistenceUnit;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @EJB(ejbLink="../their.jar#PaymentService") \n"
+"@Produces @EJB(ejbLink=\"../their.jar#PaymentService\") \n"
"PaymentService paymentService;"
msgstr ""
@@ -126,7 +126,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
+msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
msgstr ""
#. Tag: title
@@ -171,7 +171,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
+msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
msgstr ""
#. Tag: programlisting
@@ -186,7 +186,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@PersistenceContext(unitName="CustomerDatabase") EntityManager"
+msgid "@PersistenceContext(unitName=\"CustomerDatabase\") EntityManager"
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ja-JP/ri-spi.po b/docs/reference/src/main/docbook/ja-JP/ri-spi.po
index cbe204f057f..0bed40b238c 100644
--- a/docs/reference/src/main/docbook/ja-JP/ri-spi.po
+++ b/docs/reference/src/main/docbook/ja-JP/ri-spi.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-05-18 01:40+0900\n"
"Last-Translator: wadahiro \n"
"Language-Team: none\n"
@@ -31,7 +31,7 @@ msgstr "リソースサービス"
#. Tag: para
#, no-c-format
-msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the "Weld: Servlets" extension will be sufficient, and will work in any container supporting the Servlet API."
+msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the \"Weld: Servlets\" extension will be sufficient, and will work in any container supporting the Servlet API."
msgstr ""
#. Tag: para
@@ -56,7 +56,7 @@ msgstr "SPIのすべてのインタフェースがデコレータパターンを
#. Tag: para
#, fuzzy, no-c-format
-msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
+msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
msgstr "ブートストラップは複数の環境をサポートします。環境はEnvironmentインタフェースの実装によって定義されます。多くの標準環境がEnvironments列挙で組み込まれています。環境によっては異なるサービスを要求します(たとえば、サーブレットはトランザクション、EJBまたはJPAサービスを必須としません)。デフォルトではEE環境が想定されますが、bootstrap.setEnvironment()を呼ぶことで環境を設定できます。"
#. Tag: para
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
+msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
msgstr ""
#. Tag: para
@@ -96,7 +96,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
+msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
msgstr ""
#. Tag: para
@@ -106,12 +106,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
+msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
+msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
msgstr ""
#. Tag: para
@@ -126,7 +126,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
+msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
msgstr ""
#. Tag: para
@@ -156,7 +156,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
+msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
msgstr ""
#. Tag: para
@@ -196,7 +196,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
+msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
msgstr ""
#. Tag: title
@@ -211,7 +211,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
+msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
msgstr "(よくセッションBeanを背後とする)ローカルEJBを解決するとき、EJB参照を囲んだラッパー(SessionObjectReference)を返します。このラッパーのおかげで、Web Beansは特定のビジネスインタフェースを実装する参照を要求することができます。SFSBの場合は、コンテナからEJBの削除を要求することができます。"
#. Tag: para
@@ -276,7 +276,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); intercepter will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
+msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); interceptor will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
msgstr ""
#. Tag: para
@@ -351,7 +351,7 @@ msgstr "アプリケーションコンテキスト"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
+msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
msgstr "Web Beansは、アプリケーションサーバーかその他のコンテナが、アプリケーションコンテキストのための保存領域を提供することを想定しています。org.jboss.webbeans.context.api.BeanStoreは、アプリケーションスコープの保存領域を提供するように実装される必要があります。"
#. Tag: title
@@ -366,7 +366,7 @@ msgstr "org.jboss.webbeans.bootstrap.api.Bootstrapインタ
#. Tag: para
#, fuzzy, no-c-format
-msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programtically, or built in). Bean validation will validate all beans."
+msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programmatically, or built in). Bean validation will validate all beans."
msgstr "ブートストラップは、初期化と起動とシャットダウンのフェーズに分かれます。初期化はマネージャを生成し、標準の(仕様で定義された)コンテキストを追加するでしょう。ブートストラップはEJB、クラスおよびXMLを探索します。アノテーションにより定義されたBeansを追加します。また、XMLで定義されたBeansを追加します。そして、すべてのBeansの妥当性確認を行います。"
#. Tag: para
@@ -426,7 +426,7 @@ msgstr "クラスローダの分離"
#. Tag: para
#, fuzzy, no-c-format
-msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuation, classloader isolation for each CDI application."
+msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuration, classloader isolation for each CDI application."
msgstr "Web Beans RIを複数のアプリケーションのデプロイをサポートする環境に統合しているなら、それぞれのWeb Beansアプリケーションのクラスローダの分離を、自動的またはユーザによる設定によって有効とする必要があります。"
#. Tag: term
@@ -441,7 +441,7 @@ msgstr "Web Beansをサーブレット環境と統合しているなら、自動
#. Tag: para
#, no-c-format
-msgid "You must ensure that that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
+msgid "You must ensure that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
msgstr ""
#. Tag: term
@@ -582,7 +582,7 @@ msgid ""
"InjectionTarget it = weldBeanManager.fireProcessInjectionTarget(clazz);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
+"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
"\n"
"// Produce the instance, performing any constructor injection required\n"
"Object instance = it.produce();\n"
@@ -616,16 +616,16 @@ msgstr ""
msgid ""
"// Obtain the EjbDescriptor for the EJB\n"
"// You may choose to use this utility method to get the descriptor\n"
-"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
+"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
"\n"
"// Get an the Bean object\n"
-"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
+"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
"\n"
"// Create the injection target\n"
"InjectionTarget it = deploymentBeanManager.createInjectionTarget(ejbDescriptor);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
+"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
"\n"
"// Perform injection and call initializers\n"
"it.inject(instance, cc);\n"
diff --git a/docs/reference/src/main/docbook/ja-JP/scopescontexts.po b/docs/reference/src/main/docbook/ja-JP/scopescontexts.po
index c7cca1c4884..2ef01599246 100644
--- a/docs/reference/src/main/docbook/ja-JP/scopescontexts.po
+++ b/docs/reference/src/main/docbook/ja-JP/scopescontexts.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-06-04 00:47+0900\n"
"Last-Translator: Daisuke Sano \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "スコープとコンテキスト"
#. Tag: para
#, fuzzy, no-c-format
-msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
+msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
msgstr "これまでもスコープタイプアノテーションに関するいくつかの例を見てきました。Web Beanのスコープは、Web Beanインスタンスのライフサイクルを定めるものです。また、どのクライアントがどのWeb Beanインスタンスを参照するかを定めるものでもあります。Web Beansの仕様では、スコープは以下のことを定めます。"
#. Tag: para
@@ -46,7 +46,7 @@ msgstr "例えば、セッションスコープを持ったWeb Beanである@Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
+msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
msgstr ""
#. Tag: title
@@ -56,7 +56,7 @@ msgstr "スコープタイプ"
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
+msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
msgstr "Web Beansでは、拡張コンテキストモデルという特徴をもっており、新たなスコープタイプアノテーションを作成することによって、新たなスコープを定義することが可能になっています。"
#. Tag: programlisting
@@ -74,7 +74,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
+msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
msgstr "もちろんこれは、新たなスコープを定義する作業の内のごく簡単な一部分であり、スコープタイプを使うためには、さらにそのスコープを実装するコンテキストオブジェクトを定義する必要があります。コンテキストを実装するのは通常とても技術のいる作業であり、フレームワークを開発する目的でのみ行われます。"
#. Tag: para
@@ -93,7 +93,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Usually, you'll use one of CDI's built-in scopes."
+msgid "Usually, you'll use one of CDI's built-in scopes."
msgstr "通常、Web Beansの組み込みスコープの中の一つを使います。"
#. Tag: title
@@ -193,7 +193,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
+msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
msgstr "四つの組み込みスコープの内の三つはJava EE開発者にとっては極めて身近なものであるはずですので、ここではそれらの議論を行う時間を省くことにします。しかしながら、残りの一つは新たなスコープです。"
#. Tag: title
@@ -218,7 +218,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
+msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
msgstr "一つの対話は、一つのタスク、ユーザー視点での作業の単位を表現します。対話コンテキストは、ユーザーが今行っている作業に関連する状態を保持します。もし、ユーザーが複数の作業を同時に行っている場合は、対話も複数になります。"
#. Tag: para
@@ -341,25 +341,25 @@ msgstr "ゆえに、次のリンクは対話を伝播します。"
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "<a href="/addProduct.jsp?cid=#{conversation.id}">Add Product</a>"
+msgid "<a href=\"/addProduct.jsp?cid=#{conversation.id}\">Add Product</a>"
msgstr "Add Product]]>"
#. Tag: para
#, no-c-format
-msgid "It's probably better to use one of the link components in JSF 2:"
+msgid "It's probably better to use one of the link components in JSF 2:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:link outcome="/addProduct.xhtml" value="Add Product">\n"
-" <f:param name="cid" value="#{javax.enterprise.context.conversation.id}"/>\n"
-"</h:link>"
+"<h:link outcome=\"/addProduct.xhtml\" value=\"Add Product\">\n"
+" <f:param name=\"cid\" value=\"#{javax.enterprise.context.conversation.id}\"/>\n"
+"</h:link>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a "flash" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
+msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a \"flash\" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
msgstr "またWeb Beanマネージャは、対話が長期対話として導入されていないとしても、あらゆるリダイレクトをまたがって対話を伝播させる必要があります。これは、よくあるPOST-then-redirectパターンの実装をとても簡単なものにし、Ruby on Railsの\"flash\"オブジェクトのような貧弱なアーキテクチャに頼る必要がありません。このようなケースで、Web Beanマネージャは自動的にリダイレクトURLにリクエストパラメタを付加します。"
#. Tag: title
@@ -369,7 +369,7 @@ msgstr "対話のタイムアウト"
#. Tag: para
#, fuzzy, no-c-format
-msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
+msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
msgstr "Web Beanマネージャは、対話とそこに保持されたすべての状態を、リソースを保つ目的で破棄することを許されています。Web Beansの仕様で必須というわけではありませんが、Web Beanマネージャの通常の実装では、これをある種のタイムアウトに基づいて行うようになっています。タイムアウトは、対話が破棄されるまでに使用されない期間となります。"
#. Tag: para
@@ -399,12 +399,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can guess what "singleton" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
+msgid "You can guess what \"singleton\" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
+msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
msgstr ""
#. Tag: para
@@ -424,7 +424,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
+msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
msgstr ""
#. Tag: para
@@ -464,12 +464,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
+msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
+msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
msgstr ""
#. Tag: para
@@ -538,7 +538,7 @@ msgstr "calculatorフィールドには対話スコープを
#. Tag: para
#, fuzzy, no-c-format
-msgid "This feature is particularly useful with producer methods, as we'll see in the next chapter."
+msgid "This feature is particularly useful with producer methods, as we'll see in ."
msgstr "この機能は、特に次章で説明するプロデューサメソッドにおいて効果を発揮します。"
#~ msgid "@RequestScoped"
diff --git a/docs/reference/src/main/docbook/ja-JP/specialization.po b/docs/reference/src/main/docbook/ja-JP/specialization.po
index 822c1760b72..bec5e3fb4bc 100644
--- a/docs/reference/src/main/docbook/ja-JP/specialization.po
+++ b/docs/reference/src/main/docbook/ja-JP/specialization.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-06-09 19:23+0900\n"
"Last-Translator: Keita Higashi \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
+msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
msgstr ""
#. Tag: para
@@ -41,12 +41,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
+msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
+msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
msgstr ""
#. Tag: title
@@ -75,7 +75,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
+msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
msgstr "しかし、ステージング環境で、異なる Web Bean で PaymentProcessor のその実装にオーバーライドします。"
#. Tag: programlisting
@@ -115,12 +115,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
+msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
+msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
msgstr ""
#. Tag: programlisting
@@ -161,16 +161,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <alternatives>\n"
-" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
-" </alternatives>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <alternatives>\n"
+" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
+" </alternatives>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
+msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
msgstr ""
#. Tag: para
@@ -255,7 +255,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
+msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ja-JP/stereotypes.po b/docs/reference/src/main/docbook/ja-JP/stereotypes.po
index b39595b53d6..8bddcb0c333 100644
--- a/docs/reference/src/main/docbook/ja-JP/stereotypes.po
+++ b/docs/reference/src/main/docbook/ja-JP/stereotypes.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-05-21 20:05+0900\n"
"Last-Translator: Keita Higashi \n"
"Language-Team: none\n"
@@ -99,7 +99,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
+msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
msgstr ""
#. Tag: title
@@ -142,7 +142,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
+msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
msgstr ""
#. Tag: title
@@ -262,12 +262,12 @@ msgstr "ステレオタイプ"
#. Tag: para
#, no-c-format
-msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
+msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
+msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
msgstr ""
#. Tag: programlisting
@@ -294,7 +294,7 @@ msgstr "標準ステレオタイプ"
#. Tag: para
#, fuzzy, no-c-format
-msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
+msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
msgstr "Web Beans 仕様によって定義される @Interceptor と @Decorator の二つの標準ステレオタイプをすでに経験しました。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ja-JP/weldexamples.po b/docs/reference/src/main/docbook/ja-JP/weldexamples.po
index 2b0162d586e..b6652a22ad1 100644
--- a/docs/reference/src/main/docbook/ja-JP/weldexamples.po
+++ b/docs/reference/src/main/docbook/ja-JP/weldexamples.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
+msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
msgstr ""
#. Tag: title
@@ -31,75 +31,75 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
+msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
+msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
+msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<faces-config version="2.0"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<faces-config version=\"2.0\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd">\n"
-"</faces-config>"
+" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd\">\n"
+"</faces-config>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
+msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, there's the familiar web.xml:"
+msgid "Finally, there's the familiar web.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<web-app version="2.5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<web-app version=\"2.5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd\">\n"
" \n"
-" <display-name>weld-jsf-numberguess-war</display-name>\n"
-" <description>Weld JSF numberguess example (war)</description>\n"
+" <display-name>weld-jsf-numberguess-war</display-name>\n"
+" <description>Weld JSF numberguess example (war)</description>\n"
"\n"
-" <servlet>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
-" <load-on-startup>1</load-on-startup>\n"
-" </servlet>\n"
+" <servlet>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
+" <load-on-startup>1</load-on-startup>\n"
+" </servlet>\n"
"\n"
-" <servlet-mapping>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <url-pattern>*.jsf</url-pattern>\n"
-" </servlet-mapping>\n"
+" <servlet-mapping>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <url-pattern>*.jsf</url-pattern>\n"
+" </servlet-mapping>\n"
" \n"
-" <context-param>\n"
-" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
-" <param-value>.xhtml</param-value>\n"
-" </context-param>\n"
+" <context-param>\n"
+" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
+" <param-value>.xhtml</param-value>\n"
+" </context-param>\n"
"\n"
-" <session-config>\n"
-" <session-timeout>10</session-timeout>\n"
-" </session-config>\n"
+" <session-config>\n"
+" <session-timeout>10</session-timeout>\n"
+" </session-config>\n"
"\n"
-"</web-app>"
+"</web-app>"
msgstr ""
#. Tag: para
@@ -129,51 +129,51 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
+msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"\n"
-" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">\n"
-"<html xmlns="http://www.w3.org/1999/xhtml"\n"
-" xmlns:ui="http://java.sun.com/jsf/facelets"\n"
-" xmlns:h="http://java.sun.com/jsf/html"\n"
-" xmlns:f="http://java.sun.com/jsf/core">\n"
+"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
+" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n"
+"<html xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" xmlns:ui=\"http://java.sun.com/jsf/facelets\"\n"
+" xmlns:h=\"http://java.sun.com/jsf/html\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\">\n"
"\n"
-" <ui:composition template="/template.xhtml">\n"
-" <ui:define name="content">\n"
-" <h1>Guess a number...</h1>\n"
-" <h:form id="numberGuess">\n"
-" <div style="color: red">\n"
-" <h:messages id="messages" globalOnly="false"/>\n"
-" <h:outputText id="Higher" value="Higher!"\n"
-" rendered="#{game.number gt game.guess and game.guess ne 0}"/>\n"
-" <h:outputText id="Lower" value="Lower!"\n"
-" rendered="#{game.number lt game.guess and game.guess ne 0}"/>\n"
-" </div>\n"
+" <ui:composition template=\"/template.xhtml\">\n"
+" <ui:define name=\"content\">\n"
+" <h1>Guess a number...</h1>\n"
+" <h:form id=\"numberGuess\">\n"
+" <div style=\"color: red\">\n"
+" <h:messages id=\"messages\" globalOnly=\"false\"/>\n"
+" <h:outputText id=\"Higher\" value=\"Higher!\"\n"
+" rendered=\"#{game.number gt game.guess and game.guess ne 0}\"/>\n"
+" <h:outputText id=\"Lower\" value=\"Lower!\"\n"
+" rendered=\"#{game.number lt game.guess and game.guess ne 0}\"/>\n"
+" </div>\n"
" \n"
-" <div>\n"
-" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
+" <div>\n"
+" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
" You have #{game.remainingGuesses} guesses remaining.\n"
-" </div>\n"
+" </div>\n"
" \n"
-" <div>\n"
+" <div>\n"
" Your guess: \n"
-" <h:inputText id="inputGuess" value="#{game.guess}"\n"
-" size="3" required="true" disabled="#{game.number eq game.guess}"\n"
-" validator="#{game.validateNumberRange}"/>\n"
-" <h:commandButton id="guessButton" value="Guess" \n"
-" action="#{game.check}" disabled="#{game.number eq game.guess}"/>\n"
-" </div>\n"
-" <div>\n"
-" <h:commandButton id="restartButton" value="Reset" action="#{game.reset}" immediate="true"/>\n"
-" </div>\n"
-" </h:form>\n"
-" </ui:define>\n"
-" </ui:composition>\n"
-"</html>"
+" <h:inputText id=\"inputGuess\" value=\"#{game.guess}\"\n"
+" size=\"3\" required=\"true\" disabled=\"#{game.number eq game.guess}\"\n"
+" validator=\"#{game.validateNumberRange}\"/>\n"
+" <h:commandButton id=\"guessButton\" value=\"Guess\" \n"
+" action=\"#{game.check}\" disabled=\"#{game.number eq game.guess}\"/>\n"
+" </div>\n"
+" <div>\n"
+" <h:commandButton id=\"restartButton\" value=\"Reset\" action=\"#{game.reset}\" immediate=\"true\"/>\n"
+" </div>\n"
+" </h:form>\n"
+" </ui:define>\n"
+" </ui:composition>\n"
+"</html>"
msgstr ""
#. Tag: para
@@ -183,7 +183,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are a number of messages which can be sent to the user, "Higher!", "Lower!" and "Correct!""
+msgid "There are a number of messages which can be sent to the user, \"Higher!\", \"Lower!\" and \"Correct!\""
msgstr ""
#. Tag: para
@@ -198,7 +198,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
+msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
msgstr ""
#. Tag: para
@@ -266,7 +266,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Generator is application scoped, so we don't get a different random each time."
+msgid "The Generator is application scoped, so we don't get a different random each time."
msgstr ""
#. Tag: para
@@ -276,12 +276,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
+msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
+msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
msgstr ""
#. Tag: programlisting
@@ -298,19 +298,19 @@ msgid ""
" private int remainingGuesses;\n"
"\n"
" @Inject @MaxNumber private int maxNumber;\n"
-" @Inject @Random Instance<Integer> randomNumber;\n"
+" @Inject @Random Instance<Integer> randomNumber;\n"
" \n"
" public Game() {}\n"
" \n"
" public void check() {\n"
-" if (guess > number) {\n"
+" if (guess > number) {\n"
" biggest = guess - 1;\n"
" }\n"
-" else if (guess < number) {\n"
+" else if (guess < number) {\n"
" smallest = guess + 1;\n"
" }\n"
" else if (guess == number) {\n"
-" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage("Correct!"));\n"
+" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage(\"Correct!\"));\n"
" }\n"
" remainingGuesses--;\n"
" }\n"
@@ -325,18 +325,18 @@ msgid ""
" }\n"
" \n"
" public void validateNumberRange(FacesContext context, UIComponent toValidate, Object value) {\n"
-" if (remainingGuesses <= 0) {\n"
-" FacesMessage message = new FacesMessage("No guesses left!");\n"
+" if (remainingGuesses <= 0) {\n"
+" FacesMessage message = new FacesMessage(\"No guesses left!\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" ((UIInput) toValidate).setValid(false);\n"
" return;\n"
" }\n"
" int input = (Integer) value;\n"
"\n"
-" if (input < smallest || input > biggest) {\n"
+" if (input < smallest || input > biggest) {\n"
" ((UIInput) toValidate).setValid(false);\n"
"\n"
-" FacesMessage message = new FacesMessage("Invalid guess");\n"
+" FacesMessage message = new FacesMessage(\"Invalid guess\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" }\n"
" }\n"
@@ -385,20 +385,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
+msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
+msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
msgstr ""
#. Tag: title
@@ -418,17 +418,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin ."
+msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects . Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
+msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects. Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This will create a project in your workspace called weld-se-numberguess ."
+msgid "This will create a project in your workspace called weld-se-numberguess."
msgstr ""
#. Tag: para
@@ -438,7 +438,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to get the example running!"
+msgid "It's time to get the example running!"
msgstr ""
#. Tag: title
@@ -448,12 +448,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
+msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right click on the project, and choose Run As -> Run As Application:"
+msgid "Right click on the project, and choose Run As -> Run As Application:"
msgstr ""
#. Tag: para
@@ -503,7 +503,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's have a look at the significant code and configuration files that make up this example."
+msgid "Let's have a look at the significant code and configuration files that make up this example."
msgstr ""
#. Tag: para
@@ -513,7 +513,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
+msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
msgstr ""
#. Tag: programlisting
@@ -558,7 +558,7 @@ msgid ""
"\n"
" public boolean isGameLost()\n"
" {\n"
-" return guess != number && remainingGuesses <= 0;\n"
+" return guess != number && remainingGuesses <= 0;\n"
" }\n"
"\n"
" public boolean check()\n"
@@ -567,12 +567,12 @@ msgid ""
"\n"
" if (checkNewNumberRangeIsValid())\n"
" {\n"
-" if (guess > number)\n"
+" if (guess > number)\n"
" {\n"
" biggest = guess - 1;\n"
" }\n"
"\n"
-" if (guess < number)\n"
+" if (guess < number)\n"
" {\n"
" smallest = guess + 1;\n"
" }\n"
@@ -590,7 +590,7 @@ msgid ""
"\n"
" private boolean checkNewNumberRangeIsValid()\n"
" {\n"
-" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
+" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
" }\n"
"\n"
" @PostConstruct\n"
@@ -607,12 +607,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
+msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
+msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
msgstr ""
#. Tag: para
@@ -642,12 +642,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
+msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
+msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
msgstr ""
#. Tag: programlisting
@@ -660,11 +660,11 @@ msgid ""
"\n"
" public String getChallengeMessage()\n"
" {\n"
-" StringBuilder challengeMsg = new StringBuilder("I'm thinking of a number between ");\n"
+" StringBuilder challengeMsg = new StringBuilder(\"I'm thinking of a number between \");\n"
" challengeMsg.append(game.getSmallest());\n"
-" challengeMsg.append(" and ");\n"
+" challengeMsg.append(\" and \");\n"
" challengeMsg.append(game.getBiggest());\n"
-" challengeMsg.append(". Can you guess what it is?");\n"
+" challengeMsg.append(\". Can you guess what it is?\");\n"
"\n"
" return challengeMsg.toString();\n"
" }\n"
@@ -673,34 +673,34 @@ msgid ""
" {\n"
" if (game.isGameWon())\n"
" {\n"
-" return "You guessed it! The number was " + game.getNumber();\n"
+" return \"You guessed it! The number was \" + game.getNumber();\n"
" }\n"
" else if (game.isGameLost())\n"
" {\n"
-" return "You are fail! The number was " + game.getNumber();\n"
+" return \"You are fail! The number was \" + game.getNumber();\n"
" }\n"
" else if (!game.isValidNumberRange())\n"
" {\n"
-" return "Invalid number range!";\n"
+" return \"Invalid number range!\";\n"
" }\n"
" else if (game.getRemainingGuesses() == Game.MAX_NUM_GUESSES)\n"
" {\n"
-" return "What is your first guess?";\n"
+" return \"What is your first guess?\";\n"
" }\n"
" else\n"
" {\n"
" String direction = null;\n"
"\n"
-" if (game.getGuess() < game.getNumber())\n"
+" if (game.getGuess() < game.getNumber())\n"
" {\n"
-" direction = "Higher";\n"
+" direction = \"Higher\";\n"
" }\n"
" else\n"
" {\n"
-" direction = "Lower";\n"
+" direction = \"Lower\";\n"
" }\n"
"\n"
-" return direction + "! You have " + game.getRemainingGuesses() + " guesses left.";\n"
+" return direction + \"! You have \" + game.getRemainingGuesses() + \" guesses left.\";\n"
" }\n"
" }\n"
"}"
@@ -713,7 +713,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
+msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
msgstr ""
#. Tag: para
@@ -783,7 +783,7 @@ msgid ""
" private void refreshUI() {\n"
" mainLabel.setText( msgGenerator.getChallengeMessage() );\n"
" messageLabel.setText( msgGenerator.getResultMessage() );\n"
-" guessText.setText( "" );\n"
+" guessText.setText( \"\" );\n"
" guessesLeftBar.setValue( game.getRemainingGuesses() );\n"
" guessText.requestFocus();\n"
" }\n"
@@ -818,7 +818,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
+msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
msgstr ""
#. Tag: para
@@ -828,7 +828,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Calls game.check() to validate and perform one 'turn' of the game"
+msgid "Calls game.check() to validate and perform one 'turn' of the game"
msgstr ""
#. Tag: para
@@ -853,7 +853,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
+msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
msgstr ""
#. Tag: para
@@ -863,25 +863,25 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
+msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<plugin>\n"
-" <groupId>org.apache.maven.plugins</groupId>\n"
-" <artifactId>maven-ear-plugin</artifactId>\n"
-" <configuration>\n"
-" <modules>\n"
-" <webModule>\n"
-" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
-" <artifactId>weld-jsf-translator-war</artifactId>\n"
-" <contextRoot>/weld-translator</contextRoot>\n"
-" </webModule>\n"
-" </modules>\n"
-" </configuration>\n"
-"</plugin>"
+"<plugin>\n"
+" <groupId>org.apache.maven.plugins</groupId>\n"
+" <artifactId>maven-ear-plugin</artifactId>\n"
+" <configuration>\n"
+" <modules>\n"
+" <webModule>\n"
+" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
+" <artifactId>weld-jsf-translator-war</artifactId>\n"
+" <contextRoot>/weld-translator</contextRoot>\n"
+" </webModule>\n"
+" </modules>\n"
+" </configuration>\n"
+"</plugin>"
msgstr ""
#. Tag: para
@@ -891,72 +891,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
+msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<application version="5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<application version=\"5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/application_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/application_5.xsd\">\n"
"\n"
-" <display-name>weld-jsf-translator-ear</display-name>\n"
-" <description>The Weld JSF translator example (ear)</description>\n"
+" <display-name>weld-jsf-translator-ear</display-name>\n"
+" <description>The Weld JSF translator example (ear)</description>\n"
" \n"
-" <module>\n"
-" <web>\n"
-" <web-uri>weld-translator.war</web-uri>\n"
-" <context-root>/weld-translator</context-root>\n"
-" </web>\n"
-" </module>\n"
-" <module>\n"
-" <ejb>weld-translator.jar</ejb>\n"
-" </module>\n"
-"</application>"
+" <module>\n"
+" <web>\n"
+" <web-uri>weld-translator.war</web-uri>\n"
+" <context-root>/weld-translator</context-root>\n"
+" </web>\n"
+" </module>\n"
+" <module>\n"
+" <ejb>weld-translator.jar</ejb>\n"
+" </module>\n"
+"</application>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
+msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (ommitted here for brevity):"
+msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (omitted here for brevity):"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:form id="translator">\n"
+"<h:form id=\"translator\">\n"
"\n"
-" <table>\n"
-" <tr align="center" style="font-weight: bold">\n"
-" <td>\n"
+" <table>\n"
+" <tr align=\"center\" style=\"font-weight: bold\">\n"
+" <td>\n"
" Your text\n"
-" </td>\n"
-" <td>\n"
+" </td>\n"
+" <td>\n"
" Translation\n"
-" </td>\n"
-" </tr>\n"
-" <tr>\n"
-" <td>\n"
-" <h:inputTextarea id="text" value="#{translator.text}" required="true" rows="5" cols="80"/>\n"
-" </td>\n"
-" <td>\n"
-" <h:outputText value="#{translator.translatedText}"/>\n"
-" </td>\n"
-" </tr>\n"
-" </table>\n"
-" <div>\n"
-" <h:commandButton id="button" value="Translate" action="#{translator.translate}"/>\n"
-" </div>\n"
+" </td>\n"
+" </tr>\n"
+" <tr>\n"
+" <td>\n"
+" <h:inputTextarea id=\"text\" value=\"#{translator.text}\" required=\"true\" rows=\"5\" cols=\"80\"/>\n"
+" </td>\n"
+" <td>\n"
+" <h:outputText value=\"#{translator.translatedText}\"/>\n"
+" </td>\n"
+" </tr>\n"
+" </table>\n"
+" <div>\n"
+" <h:commandButton id=\"button\" value=\"Translate\" action=\"#{translator.translate}\"/>\n"
+" </div>\n"
" \n"
-"</h:form>"
+"</h:form>"
msgstr ""
#. Tag: para
@@ -966,12 +966,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
+msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
+msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
msgstr ""
#. Tag: para
@@ -995,7 +995,7 @@ msgid ""
" public String translate(String text) { \n"
" StringBuilder sb = new StringBuilder(); \n"
" for (String sentence: sentenceParser.parse(text)) { \n"
-" sb.append(translator.translate(sentence)).append(". "); \n"
+" sb.append(translator.translate(sentence)).append(\". \"); \n"
" } \n"
" return sb.toString().trim(); \n"
" }\n"
@@ -1005,7 +1005,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
+msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
msgstr ""
#. Tag: programlisting
@@ -1015,7 +1015,7 @@ msgid ""
"public class SentenceTranslator implements Translator { \n"
"\n"
" public String translate(String sentence) { \n"
-" return "Lorem ipsum dolor sit amet"; \n"
+" return \"Lorem ipsum dolor sit amet\"; \n"
" }\n"
"\n"
"}"
@@ -1031,7 +1031,7 @@ msgstr ""
msgid ""
"@Stateful\n"
"@RequestScoped\n"
-"@Named("translator")\n"
+"@Named(\"translator\")\n"
"public class TranslatorControllerBean implements TranslatorController {\n"
"\n"
" @Inject private TextTranslator translator;\n"
diff --git a/docs/reference/src/main/docbook/ko-KR/Weld_-_JSR-299_Reference_Implementation.po b/docs/reference/src/main/docbook/ko-KR/Weld_-_JSR-299_Reference_Implementation.po
new file mode 100644
index 00000000000..f4baccac014
--- /dev/null
+++ b/docs/reference/src/main/docbook/ko-KR/Weld_-_JSR-299_Reference_Implementation.po
@@ -0,0 +1,59 @@
+#
+# AUTHOR , YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "A note about naming and nomenclature"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Shortly before the final draft of JSR-299 was submitted, the specification changed its name from \"Web Beans\" to \"Java Contexts and Dependency Injection for the Java EE platform\", abbreviated CDI. For a brief period after the renaming, the reference implementation adopted the name \"Web Beans\". However, this ended up causing more confusion than it solved and Red Hat decided to change the name of the reference implementation to \"Weld\". You may still find other documentation, blogs, forum posts, etc. that use the old nomenclature. Please update any references you can. The naming game is over."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You'll also find that some of the functionality that once existed in the specification is now missing, such as defining beans in XML. These features will be available as portable extensions for CDI in the Weld project, and perhaps other implementations."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this reference guide was started while changes were still being made to the specification. We've done our best to update it for accuracy. If you discover a conflict between what is written in this guide and the specification, the specification is the authority—assume it is correct. If you believe you have found an error in the specification, please report it to the JSR-299 EG."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Beans"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Start with Weld, the CDI Reference Implementation"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Loose coupling with strong typing"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "CDI and the Java EE ecosystem"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Weld Reference Guide"
+msgstr ""
+
diff --git a/docs/reference/src/main/docbook/ko-KR/beans.po b/docs/reference/src/main/docbook/ko-KR/beans.po
index f6af3166973..e871e32177a 100644
--- a/docs/reference/src/main/docbook/ko-KR/beans.po
+++ b/docs/reference/src/main/docbook/ko-KR/beans.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
+msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
msgstr ""
#. Tag: para
@@ -56,7 +56,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
+msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
msgstr ""
#. Tag: para
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
+msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
msgstr ""
#. Tag: title
@@ -131,7 +131,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's see what all this new terminology means."
+msgid "Let's see what all this new terminology means."
msgstr ""
#. Tag: title
@@ -141,7 +141,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a "contract" that must be satisfied by the bean to be injected. The contract is:"
+msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a \"contract\" that must be satisfied by the bean to be injected. The contract is:"
msgstr ""
#. Tag: para
@@ -164,14 +164,14 @@ msgstr ""
msgid ""
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
+msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
msgstr ""
#. Tag: para
@@ -192,12 +192,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
+msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
+msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
msgstr ""
#. Tag: programlisting
@@ -206,19 +206,19 @@ msgid ""
"@Typed(Shop.class)\n"
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of "quality" using a qualifier."
+msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of \"quality\" using a qualifier."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
+msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
msgstr ""
#. Tag: programlisting
@@ -232,12 +232,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
+msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
+msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
msgstr ""
#. Tag: para
@@ -252,12 +252,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
+msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
msgstr ""
#. Tag: para
@@ -275,12 +270,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If a bean does not explicitly specify a qualifier, it has the default qualifier, @Default."
+msgid "If a bean or an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
+msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
msgstr ""
#. Tag: title
@@ -312,7 +307,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
+msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
msgstr ""
#. Tag: para
@@ -322,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk more about scopes in ."
+msgid "We'll talk more about scopes in ."
msgstr ""
#. Tag: title
@@ -343,7 +338,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"public @SessionScoped @Named("cart")\n"
+"public @SessionScoped @Named(\"cart\")\n"
"class ShoppingCart implements Serializable { ... }"
msgstr ""
@@ -355,9 +350,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:dataTable value="#{cart.lineItems}" var="item">\n"
+"<h:dataTable value=\"#{cart.lineItems}\" var=\"item\">\n"
" ...\n"
-"</h:dataTable>"
+"</h:dataTable>"
msgstr ""
#. Tag: para
@@ -389,7 +384,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
+msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
msgstr ""
#. Tag: programlisting
@@ -416,12 +411,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
+msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
+msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
msgstr ""
#. Tag: para
@@ -470,17 +465,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
+msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
+msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
+msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
msgstr ""
#. Tag: title
@@ -490,7 +485,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
+msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
msgstr ""
#. Tag: title
@@ -500,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
+msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
msgstr ""
#. Tag: para
@@ -525,7 +520,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It has an appropriate constructor—either:"
+msgid "It has an appropriate constructor—either:"
msgstr ""
#. Tag: para
@@ -540,7 +535,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
+msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
msgstr ""
#. Tag: para
@@ -585,12 +580,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
+msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
+msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
msgstr ""
#. Tag: para
@@ -625,7 +620,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
+msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
msgstr ""
#. Tag: para
@@ -640,17 +635,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
+msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
+msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're "heavyweight". It's nothing more than superstition to think that something is "heavier" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like "heavyweight"."
+msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're \"heavyweight\". It's nothing more than superstition to think that something is \"heavier\" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like \"heavyweight\"."
msgstr ""
#. Tag: title
@@ -690,7 +685,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
+msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
msgstr ""
#. Tag: programlisting
@@ -705,7 +700,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<p>Your raffle number is #{randomNumber}.</p>"
+msgid "<p>Your raffle number is #{randomNumber}.</p>"
msgstr ""
#. Tag: para
@@ -746,14 +741,14 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces Set<Roles> getRoles(User user) {\n"
+"@Produces Set<Roles> getRoles(User user) {\n"
" return user.getRoles();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk much more about producer methods in ."
+msgid "We'll talk much more about producer methods in ."
msgstr ""
#. Tag: title
@@ -763,7 +758,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
+msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
msgstr ""
#. Tag: programlisting
@@ -771,7 +766,7 @@ msgstr ""
msgid ""
"public class Shop {\n"
" @Produces PaymentProcessor paymentProcessor = ....;\n"
-" @Produces @Catalog List<Product> products = ....;\n"
+" @Produces @Catalog List<Product> products = ....;\n"
"}"
msgstr ""
@@ -782,5 +777,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
+msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
msgstr ""
diff --git a/docs/reference/src/main/docbook/ko-KR/configure.po b/docs/reference/src/main/docbook/ko-KR/configure.po
index eeba87f0a16..01ef2ccd8ab 100644
--- a/docs/reference/src/main/docbook/ko-KR/configure.po
+++ b/docs/reference/src/main/docbook/ko-KR/configure.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -30,50 +30,50 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
+msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<?xml version="1.0" encoding="UTF-8"?>\n"
-"<beans xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \n"
-" xmlns:weld="http://jboss.org/schema/weld/beans" \n"
-" xsi:schemaLocation="\n"
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<beans xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" \n"
+" xmlns:weld=\"http://jboss.org/schema/weld/beans\" \n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee http://docs.jboss.org/cdi/beans_1_0.xsd\n"
-" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">\n"
+" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd\">\n"
" \n"
-" <weld:scan>\n"
+" <weld:scan>\n"
" \n"
-" <!-- Don't deploy the classes for the swing app! -->\n"
-" <weld:exclude name="com.acme.swing.**" />\n"
+" <!-- Don't deploy the classes for the swing app! -->\n"
+" <weld:exclude name=\"com.acme.swing.**\" />\n"
" \n"
-" <!-- Don't include GWT support if GWT is not installed -->\n"
-" <weld:exclude name="com.acme.gwt.**">\n"
-" <weld:if-class-available name="!com.google.GWT"/>\n"
-" </weld:exclude>\n"
+" <!-- Don't include GWT support if GWT is not installed -->\n"
+" <weld:exclude name=\"com.acme.gwt.**\">\n"
+" <weld:if-class-available name=\"!com.google.GWT\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
+" <!--\n"
" Exclude classes which end in Blether if the system property verbosity is set to low\n"
" i.e.\n"
" java ... -Dverbosity=low \n"
-" --> \n"
-" <weld:exclude pattern="^(.*)Blether$">\n"
-" <weld:if-system-property name="verbosity" value="low"/>\n"
-" </weld:exclude>\n"
+" --> \n"
+" <weld:exclude pattern=\"^(.*)Blether$\">\n"
+" <weld:if-system-property name=\"verbosity\" value=\"low\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
-" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
+" <!--\n"
+" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
" property is not set\n"
-" -->\n"
-" <weld:exclude name="com.acme.jsf.**">\n"
-" <weld:if-class-available name="org.apahce.wicket.Wicket"/>\n"
-" <weld:if-system-property name="!viewlayer"/>\n"
-" </weld:exclude>\n"
-" </weld:scan>\n"
+" -->\n"
+" <weld:exclude name=\"com.acme.jsf.**\">\n"
+" <weld:if-class-available name=\"org.apahce.wicket.Wicket\"/>\n"
+" <weld:if-system-property name=\"!viewlayer\"/>\n"
+" </weld:exclude>\n"
+" </weld:scan>\n"
" \n"
-"</beans>"
+"</beans>"
msgstr ""
#. Tag: para
@@ -83,7 +83,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
+msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
msgstr ""
#. Tag: para
@@ -93,12 +93,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
+msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
+msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
msgstr ""
#. Tag: para
@@ -113,5 +113,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
+msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
msgstr ""
diff --git a/docs/reference/src/main/docbook/ko-KR/contexts.po b/docs/reference/src/main/docbook/ko-KR/contexts.po
index 998addb61d4..6503057daf1 100644
--- a/docs/reference/src/main/docbook/ko-KR/contexts.po
+++ b/docs/reference/src/main/docbook/ko-KR/contexts.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,17 +25,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld allows you to easiy manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivaed (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
+msgid "Weld allows you to easily manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivated (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and discociating the data store after calling activate."
+msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and dissociating the data store after calling activate."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld automatically controls context lifecycle in many scenarios such as Http Requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
+msgid "Weld automatically controls context lifecycle in many scenarios such as HTTP requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
msgstr ""
#. Tag: para
@@ -145,7 +145,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
+msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
msgstr ""
#. Tag: entry
@@ -245,12 +245,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implmentations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
+msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implementations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
+msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
msgstr ""
#. Tag: programlisting
@@ -263,14 +263,14 @@ msgid ""
" ...\n"
" \n"
" /* Start the request, providing a data store which will last the lifetime of the request */\n"
-" public void startRequest(Map<String, Object> requestDataStore) {\n"
+" public void startRequest(Map<String, Object> requestDataStore) {\n"
" // Associate the store with the context and acticate the context\n"
" requestContext.associate(requestDataStore);\n"
" requestContext.activate();\n"
" }\n"
" \n"
" /* End the request, providing the same data store as was used to start the request */\n"
-" public void endRequest(Map<String, Object> requestDataStore) {\n"
+" public void endRequest(Map<String, Object> requestDataStore) {\n"
" try {\n"
" /* Invalidate the request (all bean instances will be scheduled for destruction) */\n"
" requestContext.invalidate();\n"
@@ -290,7 +290,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's session contexts are "lazy" and don't require a session to actually exist until a bean instance must be written."
+msgid "Weld's session contexts are \"lazy\" and don't require a session to actually exist until a bean instance must be written."
msgstr ""
#. Tag: para
@@ -308,16 +308,16 @@ msgid ""
" /* Start a transient conversation */\n"
" /* Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */\n"
-" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" resumeOrStartConversation(requestDataStore, sessionDataStore, null);\n"
" }\n"
"\n"
" /* Start a transient conversation (if cid is null) or resume a non-transient */\n"
" /* conversation. Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */ \n"
-" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore, \n"
+" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore, \n"
" String cid) {\n"
" /* Associate the stores with the context and acticate the context */\n"
" * BoundRequest just wraps the two datastores */\n"
@@ -329,8 +329,8 @@ msgid ""
" /* End the conversations, providing the same data store as was used to start */\n"
" /* the request. Any transient conversations will be destroyed, any newly-promoted */\n"
" /* conversations will be placed into the session */\n"
-" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" try {\n"
" /* Invalidate the conversation (all transient conversations will be scheduled for destruction) */\n"
" conversationContext.invalidate();\n"
@@ -345,15 +345,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the containber), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
+msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the container), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the abilty to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
+msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the ability to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's conversations are not assigned ids until they become non-transient."
+msgid "Weld's conversations are not assigned ids until they become non-transient."
msgstr ""
diff --git a/docs/reference/src/main/docbook/ko-KR/decorators.po b/docs/reference/src/main/docbook/ko-KR/decorators.po
index 0abbb8f0834..4a4420a4a10 100644
--- a/docs/reference/src/main/docbook/ko-KR/decorators.po
+++ b/docs/reference/src/main/docbook/ko-KR/decorators.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: decorators\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-23 11:19+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -32,12 +32,12 @@ msgstr "데코레이터 "
#. Tag: para
#, fuzzy, no-c-format
-msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
+msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
msgstr "인터셉터는 유형 시스템에 직교 되어 있는 문제를 분리하고 캡쳐하는 강력한 방법입니다. 인터셉터는 모든 Java 유형 호출을 차단할 수 있습니다. 이는 트랜젝션 관리 및 보안과 같은 기술적 문제를 해결하는데 유용합니다. 하지만, 본래 인터셉터는 차단한 이벤트의 실제적 시멘틱을 인식하지 않습니다. 따라서, 인터셉터는 비지니스 관련 문제를 분리하기 위한 도구로는 적합하지 않습니다. "
#. Tag: para
#, fuzzy, no-c-format
-msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
+msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
msgstr "역으로 기능하는 것이 데코레이터입니다. 데코레이터는 특정 Java 인터페이스에 대해서만 호출을 차단하며, 인터페이스에 부착된 모든 시멘틱을 인식합니다. 이는 일부 비지니스 문제를 모델화하기 위해 데코레이터를 완벽한 도구로 만듭니다. 또한 데코레이터는 인터셉터의 일반적 기능을 갖지 않습니다. 데코레이터는 여러 이질적 유형을 초월하는 기술적 문제를 해결할 수 없습니다. "
#. Tag: para
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
+msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
msgstr "기타 다른 심플 Web Beans와 다르게, 데코레이터는 추상클래스일 수 도 있습니다. 데코레이터된 인터페이스의 특정 방식에 대해 데코레이터가 특별히 해야할 것이 없을 경우, 이 방식을 구현하실 필요가 없습니다. "
#. Tag: para
@@ -219,14 +219,14 @@ msgid ""
" \n"
" public void withdraw(BigDecimal amount) {\n"
" account.withdraw(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedWithdrawl(amount) );\n"
" }\n"
" }\n"
" \n"
" public void deposit(BigDecimal amount);\n"
" account.deposit(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedDeposit(amount) );\n"
" }\n"
" }\n"
@@ -269,21 +269,21 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <decorators>\n"
-" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
-" </decorators>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <decorators>\n"
+" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
+" </decorators>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
+msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
msgstr "이러한 명시 사항은 데코레이터에 대해 <Interceptors> 명시가 인터셉터에 대해 실행하는 것과 동일한 목적을 실행합니다: "
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ko-KR/ee.po b/docs/reference/src/main/docbook/ko-KR/ee.po
index 098d5606831..b316a428e8e 100644
--- a/docs/reference/src/main/docbook/ko-KR/ee.po
+++ b/docs/reference/src/main/docbook/ko-KR/ee.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: ee\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-15 02:17+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -64,7 +64,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
+msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
msgstr ""
#. Tag: para
@@ -89,7 +89,7 @@ msgstr "Java EE 리소스를 Web Bean으로 삽입 "
#. Tag: para
#, fuzzy, no-c-format
-msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
+msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
msgstr "모든 엔터프라이즈 Web Beans는 @Resource, @EJB, @PersistenceContext를 사용하여 Java EE 의존성 삽입의 장점을 취할 수 있습니다. 이미 이에 대한 몇몇 예를 살펴보았습니다: "
#. Tag: programlisting
@@ -148,7 +148,7 @@ msgstr "Servlet에서 Web Bean 호출 "
#. Tag: para
#, fuzzy, no-c-format
-msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
+msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
msgstr "Java EE 6에 있는 Servlet에서 Web Bean을 사용하기가 쉽습니다. Web Beans 영역 또는 초기화 방식 삽입을 사용하여 Web Bean을 삽입합니다. "
#. Tag: programlisting
@@ -161,14 +161,14 @@ msgid ""
" @Override\n"
" public void service(HttpServletRequest request, HttpServletResponse response)\n"
" throws ServletException, IOException {\n"
-" credentials.setUsername(request.getParameter("username")):\n"
-" credentials.setPassword(request.getParameter("password")):\n"
+" credentials.setUsername(request.getParameter(\"username\")):\n"
+" credentials.setPassword(request.getParameter(\"password\")):\n"
" login.login();\n"
" if ( login.isLoggedIn() ) {\n"
-" response.sendRedirect("/home.jsp");\n"
+" response.sendRedirect(\"/home.jsp\");\n"
" }\n"
" else {\n"
-" response.sendRedirect("/loginError.jsp");\n"
+" response.sendRedirect(\"/loginError.jsp\");\n"
" }\n"
" }\n"
" \n"
@@ -207,7 +207,7 @@ msgstr "Message-Driven Bean에서 Web Bean 호출 "
#. Tag: para
#, no-c-format
-msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
+msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
msgstr ""
#. Tag: para
@@ -269,10 +269,10 @@ msgstr ""
#, no-c-format
msgid ""
"public class OrderResources {\n"
-" @Resource(name="jms/ConnectionFactory")\n"
+" @Resource(name=\"jms/ConnectionFactory\")\n"
" private ConnectionFactory connectionFactory;\n"
" \n"
-" @Resource(name="jms/OrderQueue")\n"
+" @Resource(name=\"jms/OrderQueue\")\n"
" private Queue orderQueue;\n"
" \n"
" @Produces @OrderConnection\n"
@@ -323,7 +323,7 @@ msgid ""
"\n"
"public void sendMessage() {\n"
" MapMessage msg = orderSession.createMapMessage();\n"
-" msg.setLong("orderId", order.getId());\n"
+" msg.setLong(\"orderId\", order.getId());\n"
" ...\n"
" producer.send(msg);\n"
"}"
@@ -349,7 +349,7 @@ msgstr "패키징 및 배포 "
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a "bean archive". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
+msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a \"bean archive\". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
msgstr "Web Beans는 특정 배포 아카이브를 지정하지 않습니다. JAR, EJB-JAR 또는 WAR에 있는 Web Beans 애플리케이션 classpath에 있는 배포 위치를 패키지화할 수 있습니다. 하지만 Web Beans이 있는 각각의 아카이브에는 META-INF 또는 WEB-INF 디렉토리에 있는 web-beans.xml라는 파일이 들어 있어야 합니다. 파일은 비어 있을 수 도 있습니다. web-beans.xml 파일이 없는 아카이브에 배포된 Web Beans는 애플리케이션에서 사용할 수 없습니다. "
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ko-KR/environments.po b/docs/reference/src/main/docbook/ko-KR/environments.po
index af15132282a..dcf89138168 100644
--- a/docs/reference/src/main/docbook/ko-KR/environments.po
+++ b/docs/reference/src/main/docbook/ko-KR/environments.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-28 17:09+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -56,12 +56,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
+msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an "uber-jar", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
+msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an \"uber-jar\", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
msgstr ""
#. Tag: para
@@ -72,9 +72,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
#. Tag: title
@@ -84,18 +84,18 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
+msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<Context>\n"
-" <Resource name="BeanManager" \n"
-" auth="Container"\n"
-" type="javax.enterprise.inject.spi.BeanManager"\n"
-" factory="org.jboss.weld.resources.ManagerObjectFactory"/>\n"
-"</Context>"
+"<Context>\n"
+" <Resource name=\"BeanManager\" \n"
+" auth=\"Container\"\n"
+" type=\"javax.enterprise.inject.spi.BeanManager\"\n"
+" factory=\"org.jboss.weld.resources.ManagerObjectFactory\"/>\n"
+"</Context>"
msgstr ""
#. Tag: para
@@ -106,12 +106,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<resource-env-ref>\n"
-" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
-" <resource-env-ref-type>\n"
+"<resource-env-ref>\n"
+" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
+" <resource-env-ref-type>\n"
" javax.enterprise.inject.spi.BeanManager\n"
-" </resource-env-ref-type>\n"
-"</resource-env-ref>"
+" </resource-env-ref-type>\n"
+"</resource-env-ref>"
msgstr ""
#. Tag: para
@@ -131,27 +131,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
+msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.mortbay.jetty.plus.naming.Resource">\n"
-" <Arg><Ref id="webAppCtx"/></Arg> \n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.mortbay.jetty.plus.naming.Resource\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg> \n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure>"
msgstr ""
#. Tag: para
@@ -162,22 +162,22 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://www.eclipse.org/jetty/configure.dtd">\n"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://www.eclipse.org/jetty/configure.dtd\">\n"
"\n"
-"<Configure id="webAppCtx" class="org.eclipse.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.eclipse.jetty.plus.jndi.Resource">\n"
-" <Arg> <Ref id="webAppCtx"/> </Arg>\n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure> "
+"<Configure id=\"webAppCtx\" class=\"org.eclipse.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.eclipse.jetty.plus.jndi.Resource\">\n"
+" <Arg> <Ref id=\"webAppCtx\"/> </Arg>\n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure> "
msgstr ""
#. Tag: para
@@ -187,7 +187,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
+msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
msgstr ""
#. Tag: para
@@ -197,19 +197,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file META-INF/jetty-web.xml with the following content to your war:"
+msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file WEB-INF/jetty-web.xml with the following content to your war:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <Call class="org.jboss.weld.environment.jetty.WeldServletHandler" name="process">\n"
-" <Arg><Ref id="webAppCtx"/></Arg>\n"
-" </Call>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <Call class=\"org.jboss.weld.environment.jetty.WeldServletHandler\" name=\"process\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg>\n"
+" </Call>\n"
+"</Configure>"
msgstr ""
#. Tag: title
@@ -219,7 +219,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In addition to improved integration of the Enterprise Java stack, the "Contexts and Dependency Injection for the Java EE platform" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
+msgid "In addition to improved integration of the Enterprise Java stack, the \"Contexts and Dependency Injection for the Java EE platform\" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
msgstr ""
#. Tag: para
@@ -279,7 +279,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Parameters List<String> params;"
+msgid "@Inject @Parameters List<String> params;"
msgstr ""
#. Tag: programlisting
@@ -299,7 +299,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example of a simple CDI SE application:"
+msgid "Here's an example of a simple CDI SE application:"
msgstr ""
#. Tag: programlisting
@@ -308,8 +308,8 @@ msgid ""
"@Singleton\n"
"public class HelloWorld\n"
"{\n"
-" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
-" System.out.println("Hello " + parameters.get(0));\n"
+" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
+" System.out.println(\"Hello \" + parameters.get(0));\n"
" }\n"
"}"
msgstr ""
@@ -331,7 +331,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
+msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
msgstr ""
#. Tag: para
@@ -341,17 +341,17 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "java org.jboss.weld.environment.se.StartMain <args>"
+msgid "java org.jboss.weld.environment.se.StartMain <args>"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Programatic Bootstrap API"
+msgid "Programmatic Bootstrap API"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
+msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
msgstr ""
#. Tag: programlisting
@@ -377,10 +377,10 @@ msgid ""
"{\n"
"\n"
" /** Provides access to all beans within the application. */\n"
-" public Instance<Object> instance() {...}\n"
+" public Instance<Object> instance() {...}\n"
"\n"
" /** Provides access to all events within the application. */\n"
-" public Event<Object> event() {...}\n"
+" public Event<Object> event() {...}\n"
"\n"
" /** Provides direct access to the BeanManager. */\n"
" public BeanManager getBeanManager() {...}\n"
@@ -390,7 +390,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
+msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
msgstr ""
#. Tag: programlisting
@@ -430,22 +430,22 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
+msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans>\n"
-" <decorators>\n"
-" <decorator>org.jboss.weld.environment.se.threading.RunnableDecorator</decorator>\n"
-" </decorator>\n"
-"</beans>"
+"<beans>\n"
+" <decorators>\n"
+" <class>org.jboss.weld.environment.se.threading.RunnableDecorator</class>\n"
+" </decorator>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situtations where you would otherwise have used ThreadLocal directly, which are typically rare."
+msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situations where you would otherwise have used ThreadLocal directly, which are typically rare."
msgstr ""
#. Tag: title
@@ -455,7 +455,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
+msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ko-KR/events.po b/docs/reference/src/main/docbook/ko-KR/events.po
index 6ef7ba2e4c4..07afbd989c7 100644
--- a/docs/reference/src/main/docbook/ko-KR/events.po
+++ b/docs/reference/src/main/docbook/ko-KR/events.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: events\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-23 11:16+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -52,7 +52,7 @@ msgstr "이벤트 생산자만 옵저버에서 연결 해제되는 것이 아니
#. Tag: para
#, fuzzy, no-c-format
-msgid "observers can specify a combination of "selectors" to narrow the set of event notifications they will receive, and"
+msgid "observers can specify a combination of \"selectors\" to narrow the set of event notifications they will receive, and"
msgstr "옵저버는 \"선택자\" 조합을 지정하여 이벤트 통지 모음의 범위를 좁힙니다. "
#. Tag: para
@@ -62,7 +62,7 @@ msgstr "옵저버는 바로 통지하거나 또는 현재 트랜젝션이 끝날
#. Tag: para
#, no-c-format
-msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
+msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
msgstr ""
#. Tag: title
@@ -77,7 +77,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
+msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
msgstr ""
#. Tag: programlisting
@@ -120,7 +120,7 @@ msgstr "only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
+msgid "An observer method need not specify any event qualifiers—in this case it is interested in only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
msgstr "옵저버 방식은 어떤 이벤트 바인딩도 지정할 필요가 없습니다 이러한 경우 특정 유형의 모든 이벤트에 관심을 갖게 됩니다. 이벤트 바인딩을 지정하지 않을 경우, 이러한 이벤트 바인딩이 있는 이벤트에만 관심을 갖게 됩니다. "
#. Tag: para
@@ -145,7 +145,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Event<Document> documentEvent;"
+msgid "@Inject @Any Event<Document> documentEvent;"
msgstr " documentEvent]]>"
#. Tag: para
@@ -200,7 +200,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
+msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
msgstr " documentUpdatedEvent]]>"
#. Tag: para
@@ -220,12 +220,12 @@ msgstr "이는 fire()에 전달된 이벤트 바인딩에 대
#. Tag: para
#, no-c-format
-msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
+msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
+msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
msgstr "(){} );]]>"
#. Tag: para
@@ -240,7 +240,7 @@ msgstr "트랜잭션 옵저버 "
#. Tag: para
#, no-c-format
-msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
+msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
msgstr ""
#. Tag: para
@@ -302,7 +302,7 @@ msgstr "이벤트 바인딩 유형 멤버는 이벤트 통지 삽입 지점에
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
+msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
msgstr " LoggedInEvent;}}]]>"
#. Tag: para
@@ -314,7 +314,7 @@ msgstr "다른 방법으로, 이벤트 바인딩 유형 멤버 값은 이벤트
#, fuzzy, no-c-format
msgid ""
"abstract class RoleBinding \n"
-" extends AnnotationLiteral<Role> \n"
+" extends AnnotationLiteral<Role> \n"
" implements Role {}"
msgstr ""
" blogEvent;\n"
"...\n"
@@ -458,12 +458,12 @@ msgid ""
"\n"
" @PersistenceContext EntityManager em;\n"
" \n"
-" List<Product> products;\n"
+" List<Product> products;\n"
"\n"
" @Produces @Catalog \n"
-" List<Product> getCatalog() {\n"
+" List<Product> getCatalog() {\n"
" if (products==null) {\n"
-" products = em.createQuery("select p from Product p where p.deleted = false")\n"
+" products = em.createQuery(\"select p from Product p where p.deleted = false\")\n"
" .getResultList();\n"
" }\n"
" return products;\n"
@@ -505,16 +505,16 @@ msgid ""
"@Stateless\n"
"public class ProductManager {\n"
" @PersistenceContext EntityManager em;\n"
-" @Inject @Any Event<Product> productEvent;\n"
+" @Inject @Any Event<Product> productEvent;\n"
"\n"
" public void delete(Product product) {\n"
" em.delete(product);\n"
-" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
" }\n"
" \n"
" public void persist(Product product) {\n"
" em.persist(product);\n"
-" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
" }\n"
" ...\n"
"}"
diff --git a/docs/reference/src/main/docbook/ko-KR/example.po b/docs/reference/src/main/docbook/ko-KR/example.po
index 0f3ec79d141..3522adf4115 100644
--- a/docs/reference/src/main/docbook/ko-KR/example.po
+++ b/docs/reference/src/main/docbook/ko-KR/example.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: example\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-14 15:00+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -30,7 +30,7 @@ msgstr "JSF 웹 애플리케이션 예 "
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
+msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
msgstr "이러한 웹 애플리케이션의 예를 살펴봅시다. JSF를 사용하는 애플리케이션의 사용자 로그인/로그아웃을 구현할 것입니다. 먼저, 로그인시 입력한 사용자 이름 및 암호를 보유하기 위해 Web Bean을 정의합니다: "
#. Tag: programlisting
@@ -72,18 +72,18 @@ msgstr "Web Bean은 다음과 같은 JSF 형식에서 로그인 프롬프트로
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:form>\n"
-" <h:panelGrid columns="2" rendered="#{!login.loggedIn}">\n"
-" <f:validateBean>\n"
-" <h:outputLabel for="username">Username:</h:outputLabel>\n"
-" <h:inputText id="username" value="#{credentials.username}"/>\n"
-" <h:outputLabel for="password">Password:</h:outputLabel>\n"
-" <h:inputSecret id="password" value="#{credentials.password}"/>\n"
-" </f:validateBean>\n"
-" </h:panelGrid>\n"
-" <h:commandButton value="Login" action="#{login.login}" rendered="#{!login.loggedIn}"/>\n"
-" <h:commandButton value="Logout" action="#{login.logout}" rendered="#{login.loggedIn}"/>\n"
-"</h:form>"
+"<h:form>\n"
+" <h:panelGrid columns=\"2\" rendered=\"#{!login.loggedIn}\">\n"
+" <f:validateBean>\n"
+" <h:outputLabel for=\"username\">Username:</h:outputLabel>\n"
+" <h:inputText id=\"username\" value=\"#{credentials.username}\"/>\n"
+" <h:outputLabel for=\"password\">Password:</h:outputLabel>\n"
+" <h:inputSecret id=\"password\" value=\"#{credentials.password}\"/>\n"
+" </f:validateBean>\n"
+" </h:panelGrid>\n"
+" <h:commandButton value=\"Login\" action=\"#{login.login}\" rendered=\"#{!login.loggedIn}\"/>\n"
+" <h:commandButton value=\"Logout\" action=\"#{login.logout}\" rendered=\"#{login.loggedIn}\"/>\n"
+"</h:form>"
msgstr ""
"\n"
" \n"
@@ -130,7 +130,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
+msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
msgstr ""
#. Tag: para
@@ -150,10 +150,10 @@ msgid ""
" private User user;\n"
" \n"
" public void login() {\n"
-" List<User> results = userDatabase.createQuery(\n"
-" "select u from User u where u.username = :username and u.password = :password")\n"
-" .setParameter("username", credentials.getUsername())\n"
-" .setParameter("password", credentials.getPassword())\n"
+" List<User> results = userDatabase.createQuery(\n"
+" \"select u from User u where u.username = :username and u.password = :password\")\n"
+" .setParameter(\"username\", credentials.getUsername())\n"
+" .setParameter(\"password\", credentials.getPassword())\n"
" .getResultList();\n"
" \n"
" if (!results.isEmpty()) {\n"
@@ -299,14 +299,14 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:panelGroup rendered="#{login.loggedIn}">\n"
+"<h:panelGroup rendered=\"#{login.loggedIn}\">\n"
" signed in as #{currentUser.username}\n"
-"</h:panelGroup>"
+"</h:panelGroup>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
+msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
msgstr "이러한 예가 Web Bean 프로그래밍 모델의 맛을 보는 계기가 되었으면 합니다. 다음 부분에서는 Web Beans 의존성 삽입에 대해 자세히 살펴보겠습니다. "
#~ msgid "Of course, @LoggedIn is a binding annotation:"
diff --git a/docs/reference/src/main/docbook/ko-KR/extend.po b/docs/reference/src/main/docbook/ko-KR/extend.po
index 20f9253a9e1..df08edc6743 100644
--- a/docs/reference/src/main/docbook/ko-KR/extend.po
+++ b/docs/reference/src/main/docbook/ko-KR/extend.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: extend\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-23 11:05+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -86,7 +86,7 @@ msgstr "Bean 클래스 "
#. Tag: para
#, no-c-format
-msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
+msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
msgstr ""
#. Tag: programlisting
@@ -174,15 +174,15 @@ msgid ""
"class MyExtension implements Extension {\n"
" \n"
" void beforeBeanDiscovery(@Observes BeforeBeanDiscovery bbd) {\n"
-" Logger.global.debug("beginning the scanning process");\n"
+" Logger.global.debug(\"beginning the scanning process\");\n"
" }\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
-" Logger.global.debug("scanning type: " + pat.getAnnotatedType().getJavaClass().getName());\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" Logger.global.debug(\"scanning type: \" + pat.getAnnotatedType().getJavaClass().getName());\n"
" } \n"
"\n"
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd) {\n"
-" Logger.global.debug("finished the scanning process");\n"
+" Logger.global.debug(\"finished the scanning process\");\n"
" }\n"
" \n"
"}"
@@ -190,7 +190,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
+msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
msgstr ""
#. Tag: programlisting
@@ -198,7 +198,7 @@ msgstr ""
msgid ""
"class MyExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" //tell the container to ignore the type if it is annotated @Ignore\n"
" if ( pat.getAnnotatedType().isAnnotionPresent(Ignore.class) ) pat.veto(); \n"
" } \n"
@@ -213,7 +213,7 @@ msgstr "Web Beans 확장의 중심은 Manager 객체입니다
#. Tag: programlisting
#, no-c-format
-msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
+msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
msgstr ""
#. Tag: title
@@ -230,31 +230,31 @@ msgstr "Manager 인터페이스는 Web Beans, 인터셉터,
#, no-c-format
msgid ""
"public interface BeanManager {\n"
-" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
-" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
-" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
-" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
-" public Set<Bean<?>> getBeans(String name);\n"
-" public Bean<?> getPassivationCapableBean(String id);\n"
-" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
+" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
+" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
+" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
+" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
+" public Set<Bean<?>> getBeans(String name);\n"
+" public Bean<?> getPassivationCapableBean(String id);\n"
+" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
" public void validate(InjectionPoint injectionPoint);\n"
" public void fireEvent(Object event, Annotation... qualifiers);\n"
-" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
-" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
-" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
-" public boolean isScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
-" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
-" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
-" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
-" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
-" public Context getContext(Class<? extends Annotation> scopeType);\n"
+" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
+" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
+" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
+" public boolean isScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
+" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
+" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
+" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
+" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
+" public Context getContext(Class<? extends Annotation> scopeType);\n"
" public ELResolver getELResolver();\n"
" public ExpressionFactory wrapExpressionFactory(ExpressionFactory expressionFactory);\n"
-" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
-" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
+" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
+" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
"}"
msgstr ""
@@ -275,7 +275,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's study some of the interfaces exposed by the BeanManager."
+msgid "Let's study some of the interfaces exposed by the BeanManager."
msgstr "Web Beans 확장의 중심은 Manager 객체입니다. "
#. Tag: title
@@ -290,21 +290,21 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to instatiate the object itself, and so only method and field injection will be supported."
+msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to insntatiate the object itself, and so only method and field injection will be supported."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"//get the BeanManager from JNDI\n"
-"BeanManager beanManager = (BeanManager) new InitialContext().lookup("java:comp/BeanManager");\n"
+"BeanManager beanManager = (BeanManager) new InitialContext().lookup(\"java:comp/BeanManager\");\n"
"\n"
"//CDI uses an AnnotatedType object to read the annotations of a class\n"
-"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
+"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
"\n"
"//The extension uses an InjectionTarget to delegate instantiation, dependency injection \n"
"//and lifecycle callbacks to the CDI container\n"
-"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
+"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
"\n"
"//each instance needs its own CDI CreationalContext\n"
"CreationalContext ctx = beanManager.createCreationalContext(null);\n"
@@ -334,33 +334,33 @@ msgstr "Bean 추상 클래스의 인스턴스는 Web Beans를
#. Tag: para
#, no-c-format
-msgid "The Bean interface exposes all the interesting things we dicussed in ."
+msgid "The Bean interface exposes all the interesting things we discussed in ."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"public interface Bean<T> extends Contextual<T> {\n"
-" public Set<Type> getTypes();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Class<? extends Annotation> getScope();\n"
+"public interface Bean<T> extends Contextual<T> {\n"
+" public Set<Type> getTypes();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Class<? extends Annotation> getScope();\n"
" public String getName();\n"
-" public Set<Class<? extends Annotation>> getStereotypes();\n"
-" public Class<?> getBeanClass();\n"
+" public Set<Class<? extends Annotation>> getStereotypes();\n"
+" public Class<?> getBeanClass();\n"
" public boolean isAlternative();\n"
" public boolean isNullable();\n"
-" public Set<InjectionPoint> getInjectionPoints();\n"
+" public Set<InjectionPoint> getInjectionPoints();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's an easy way to find out what beans exist in the application:"
+msgid "There's an easy way to find out what beans exist in the application:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
+msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
msgstr ""
#. Tag: para
@@ -380,7 +380,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
+msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
msgstr ""
#. Tag: programlisting
@@ -391,49 +391,49 @@ msgid ""
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd, BeanManager bm) {\n"
" \n"
" //use this to read annotations of the class\n"
-" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
+" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
"\n"
" //use this to instantiate the class and inject dependencies\n"
-" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
+" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
"\n"
-" abd.addBean( new Bean<SecurityManager>() {\n"
+" abd.addBean( new Bean<SecurityManager>() {\n"
"\n"
" @Override\n"
-" public Class<?> getBeanClass() {\n"
+" public Class<?> getBeanClass() {\n"
" return SecurityManager.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
" public String getName() {\n"
-" return "securityManager";\n"
+" return \"securityManager\";\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getQualifiers() {\n"
-" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
-" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
-" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
+" public Set<Annotation> getQualifiers() {\n"
+" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
+" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
+" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
" return qualifiers;\n"
" }\n"
"\n"
" @Override\n"
-" public Class<? extends Annotation> getScope() {\n"
+" public Class<? extends Annotation> getScope() {\n"
" return SessionScoped.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Class<? extends Annotation>> getStereotypes() {\n"
+" public Set<Class<? extends Annotation>> getStereotypes() {\n"
" return Collections.emptySet();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypes() {\n"
-" Set<Type> types = new HashSet<Type>();\n"
+" public Set<Type> getTypes() {\n"
+" Set<Type> types = new HashSet<Type>();\n"
" types.add(SecurityManager.class);\n"
" types.add(Object.class);\n"
" return types;\n"
@@ -450,7 +450,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
+" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
" SecurityManager instance = it.produce(ctx);\n"
" it.inject(instance, ctx);\n"
" it.postConstruct(instance);\n"
@@ -459,7 +459,7 @@ msgid ""
"\n"
" @Override\n"
" public void destroy(SecurityManager instance, \n"
-" CreationalContext<SecurityManager> ctx) {\n"
+" CreationalContext<SecurityManager> ctx) {\n"
" it.preDestroy(instance);\n"
" it.dispose(instance);\n"
" ctx.release();\n"
@@ -488,7 +488,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
+msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
msgstr ""
#. Tag: programlisting
@@ -496,38 +496,38 @@ msgstr ""
msgid ""
"public class QualifiedNameExtension implements Extension {\n"
"\n"
-" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
+" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
"\n"
" //wrap this to override the annotations of the class\n"
-" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
+" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
" \n"
-" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
+" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
"\n"
" @Override\n"
-" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
+" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
" return at.getConstructors();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedField<? super X>> getFields() {\n"
+" public Set<AnnotatedField<? super X>> getFields() {\n"
" return at.getFields();\n"
" }\n"
"\n"
" @Override\n"
-" public Class<X> getJavaClass() {\n"
+" public Class<X> getJavaClass() {\n"
" return at.getJavaClass();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
+" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
" return at.getMethods();\n"
" }\n"
"\n"
" @Override\n"
-" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
+" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
" if ( Named.class.equals(annType) ) {\n"
" class NamedLiteral \n"
-" extends AnnotationLiteral<Named> \n"
+" extends AnnotationLiteral<Named> \n"
" implements Named {\n"
" @Override\n"
" public String value() {\n"
@@ -536,7 +536,7 @@ msgid ""
" final String qualifiedName;\n"
" if ( pkg.isAnnotationPresent(Named.class) ) {\n"
" qualifiedName = pkg.getAnnotation(Named.class).value() \n"
-" + '.' + unqualifiedName;\n"
+" + '.' + unqualifiedName;\n"
" }\n"
" else {\n"
" qualifiedName = unqualifiedName;\n"
@@ -552,7 +552,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getAnnotations() {\n"
+" public Set<Annotation> getAnnotations() {\n"
" return at.getAnnotations();\n"
" }\n"
"\n"
@@ -562,12 +562,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypeClosure() {\n"
+" public Set<Type> getTypeClosure() {\n"
" return at.getTypeClosure();\n"
" }\n"
"\n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
" return at.isAnnotationPresent(annType);\n"
" }\n"
" \n"
@@ -581,7 +581,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
+msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
msgstr ""
#. Tag: programlisting
@@ -589,17 +589,17 @@ msgstr ""
msgid ""
"class ServiceAlternativeExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" \n"
-" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
+" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
" \n"
" if ( Service.class.isAssignableFrom( type.getJavaClass() ) ) {\n"
" \n"
" //if the class implements Service, make it an @Alternative\n"
-" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
+" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
" \n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
" return annotationType.equals(Alternative.class) ? \n"
" true : type.isAnnotationPresent(annotationType);\n"
" }\n"
@@ -632,7 +632,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
+msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
msgstr ""
#. Tag: programlisting
@@ -652,25 +652,25 @@ msgstr ""
msgid ""
"public class ConfigExtension implements Extension {\n"
"\n"
-"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
+"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
"\t\t\n"
"\t\t//wrap this to intercept the component lifecycle\n"
-"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
+"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
"\t \n"
-" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
+" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
" \n"
" //use this to read annotations of the class and its members\n"
-" AnnotatedType<X> at = pit.getAnnotatedType();\n"
+" AnnotatedType<X> at = pit.getAnnotatedType();\n"
" \n"
" //read the properties file\n"
-" String propsFileName = at.getClass().getSimpleName() + ".properties";\n"
+" String propsFileName = at.getClass().getSimpleName() + \".properties\";\n"
" InputStream stream = at.getJavaClass().getResourceAsStream(propsFileName);\n"
" if (stream!=null) {\n"
" \n"
" try {\n"
" Properties props = new Properties();\n"
" props.load(stream);\n"
-" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
+" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
" String fieldName = property.getKey().toString();\n"
" Object value = property.getValue();\n"
" try {\n"
@@ -682,7 +682,7 @@ msgid ""
" else {\n"
" //TODO: do type conversion automatically\n"
" pit.addDefinitionError( new InjectionException(\n"
-" "field is not of type String: " + field ) );\n"
+" \"field is not of type String: \" + field ) );\n"
" }\n"
" }\n"
" catch (NoSuchFieldException nsfe) {\n"
@@ -698,14 +698,14 @@ msgid ""
" }\n"
" }\n"
" \n"
-" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
+" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
"\n"
" @Override\n"
-" public void inject(X instance, CreationalContext<X> ctx) {\n"
+" public void inject(X instance, CreationalContext<X> ctx) {\n"
" it.inject(instance, ctx);\n"
" \n"
" //set the values onto the new instance of the component\n"
-" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
+" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
" try {\n"
" configuredValue.getKey().set(instance, configuredValue.getValue());\n"
" }\n"
@@ -731,12 +731,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
-" public X produce(CreationalContext<X> ctx) {\n"
+" public X produce(CreationalContext<X> ctx) {\n"
" return it.produce(ctx);\n"
" }\n"
" \n"
@@ -751,7 +751,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
+msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
msgstr ""
#. Tag: title
@@ -768,9 +768,9 @@ msgstr "Context 인터페이스는 Web Beans에 새로운 범
#, fuzzy, no-c-format
msgid ""
"public interface Context {\n"
-" public Class<? extends Annotation> getScope();\n"
-" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
-" public <T> T get(Contextual<T> contextual);\n"
+" public Class<? extends Annotation> getScope();\n"
+" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
+" public <T> T get(Contextual<T> contextual);\n"
" boolean isActive();\n"
"}"
msgstr ""
diff --git a/docs/reference/src/main/docbook/ko-KR/gettingstarted.po b/docs/reference/src/main/docbook/ko-KR/gettingstarted.po
index 426f88f02d4..cf56dce66d2 100644
--- a/docs/reference/src/main/docbook/ko-KR/gettingstarted.po
+++ b/docs/reference/src/main/docbook/ko-KR/gettingstarted.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: ri\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-23 11:14+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -33,7 +33,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, Glassfish 3.0 or any compliant Java EE 6 container."
+msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, GlassFish 3.0 or any compliant Java EE 6 container."
msgstr ""
#. Tag: para
@@ -48,7 +48,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To run the examples with the provided build scripts, you'll need the following:"
+msgid "To run the examples with the provided build scripts, you'll need the following:"
msgstr ""
#. Tag: para
@@ -93,12 +93,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
+msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
+msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
msgstr ""
#. Tag: para
@@ -108,7 +108,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
+msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
msgstr ""
#. Tag: title
@@ -118,19 +118,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
+msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
+msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> unzip jboss-6.0.*.zip\n"
-"$> mv jboss-6.0.*/ jboss-as-6.0"
+"$> unzip jboss-6.0.*.zip\n"
+"$> mv jboss-6.0.*/ jboss-as-6.0"
msgstr ""
#. Tag: para
@@ -145,7 +145,7 @@ msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
#, fuzzy, no-c-format
-msgid "You're now ready to deploy your first example!"
+msgid "You're now ready to deploy your first example!"
msgstr "이제, 첫번째 예제를 배치할 준비가 되었습니다! "
#. Tag: para
@@ -156,22 +156,22 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant deploy"
msgstr ""
"$ cd examples/numberguess\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
+msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/jboss-as-6.0\n"
-"$> ./bin/run.sh"
+"$> cd /path/to/jboss-as-6.0\n"
+"$> ./bin/run.sh"
msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
@@ -180,11 +180,11 @@ msgid "a Windows command window:"
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
-"$> run"
-msgstr ""
+"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
+"$> run"
+msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
#, no-c-format
@@ -239,20 +239,20 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/translator\n"
-"$> ant deploy"
+"$> cd examples/jsf/translator\n"
+"$> ant deploy"
msgstr ""
"$ cd examples/translator\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
+msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
+msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
msgstr "url (http://localhost:8080/webbeans-translator)을 제공하는 컨텍스트 경로를 설정합니다. "
#. Tag: title
@@ -262,41 +262,43 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
+msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
+msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> chmod 755 glassfish-v3-unix.sh\n"
-"$> ./glassfish-v3-unix.sh"
+"$> chmod 755 glassfish-v3-unix.sh\n"
+"$> ./glassfish-v3-unix.sh"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
+msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
+msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
-"$> ant package"
+"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
+"$> ant package"
msgstr ""
+"$ cd examples/numberguess\n"
+"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
+msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
msgstr ""
#. Tag: para
@@ -306,12 +308,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin start-domain domain1"
+msgid "$> asadmin start-domain domain1"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on "Applications", then click on the "Deploy..." button under the heading "Applications" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
+msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on \"Applications\", then click on the \"Deploy...\" button under the heading \"Applications\" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
msgstr ""
#. Tag: para
@@ -321,7 +323,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin deploy target/weld-numberguess.war"
+msgid "$> asadmin deploy target/weld-numberguess.war"
msgstr ""
#. Tag: para
@@ -341,24 +343,24 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
+msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
+msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
msgstr "다음으로 seamframework.org에서 Web Beans RI를 다운로드하여 압축 풀기를 합니다. 예: "
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "$> unzip apache-tomcat-6.0.18.zip"
+msgid "$> unzip apache-tomcat-6.0.18.zip"
msgstr ""
""
#. Tag: para
#, no-c-format
-msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
+msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
msgstr ""
#. Tag: title
@@ -368,7 +370,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
+msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
msgstr ""
#. Tag: programlisting
@@ -378,7 +380,7 @@ msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now you're ready to deploy the numberguess example to Tomcat!"
+msgid "Now you're ready to deploy the numberguess example to Tomcat!"
msgstr "numberguess 예제를 배치하려면: "
#. Tag: para
@@ -389,15 +391,15 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant tomcat.deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant tomcat.deploy"
msgstr ""
"$ cd examples/numberguess\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with "tomcat."."
+msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with \"tomcat.\"."
msgstr ""
#. Tag: para
@@ -422,21 +424,21 @@ msgstr "ant undeploy - 서버에서 예제를 제거합니다
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
+msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/apache-tomcat-6\n"
-"$> ./bin/start.sh"
+"$> cd /path/to/apache-tomcat-6\n"
+"$> ./bin/start.sh"
msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
-"$> start"
+"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
+"$> start"
msgstr ""
""
@@ -453,12 +455,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
+msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
+msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
msgstr ""
#. Tag: para
@@ -468,7 +470,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<user username="admin" password="" roles="manager"/>"
+msgid "<user username=\"admin\" password=\"\" roles=\"manager\"/>"
msgstr ""
#. Tag: para
@@ -478,7 +480,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
+msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
msgstr ""
#. Tag: para
@@ -488,7 +490,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn tomcat:redeploy -Ptomcat"
+msgid "$> mvn tomcat:redeploy -Ptomcat"
msgstr ""
#. Tag: para
@@ -503,7 +505,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace tomcat:run -Ptomcat"
+msgid "$> mvn war:inplace tomcat:run -Ptomcat"
msgstr ""
#. Tag: para
@@ -513,12 +515,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Ptomcat"
+msgid "$> mvn compile war:inplace -Ptomcat"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
+msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
msgstr ""
#. Tag: title
@@ -533,12 +535,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
+msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
+msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
msgstr ""
#. Tag: para
@@ -547,11 +549,13 @@ msgid "To run the weld-numberguess example on Jetty, switch t
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> mvn war:inplace jetty:run -Pjetty"
+"$> cd examples/jsf/numberguess\n"
+"$> mvn war:inplace jetty:run -Pjetty"
msgstr ""
+"$ cd examples/numberguess\n"
+"ant deploy"
#. Tag: para
#, no-c-format
@@ -565,7 +569,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Pjetty"
+msgid "$> mvn compile war:inplace -Pjetty"
msgstr ""
#. Tag: para
@@ -575,7 +579,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclispe[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
+msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclipse[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
msgstr ""
#. Tag: para
@@ -585,7 +589,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
+msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
msgstr ""
#. Tag: para
@@ -595,12 +599,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace -Pjetty-ide"
+msgid "$> mvn war:inplace -Pjetty-ide"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using "Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
+msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using \"Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ko-KR/injection.po b/docs/reference/src/main/docbook/ko-KR/injection.po
index 1ab27c922f7..30424eff8c0 100644
--- a/docs/reference/src/main/docbook/ko-KR/injection.po
+++ b/docs/reference/src/main/docbook/ko-KR/injection.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: injection\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-23 17:37+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -40,7 +40,7 @@ msgstr "의존성 삽입 "
#. Tag: para
#, no-c-format
-msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
+msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
msgstr ""
#. Tag: title
@@ -165,7 +165,7 @@ msgstr "다음으로, Web Bean 관리자는 Web Bean의 삽입된 모든 영역
#. Tag: para
#, fuzzy, no-c-format
-msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
+msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
msgstr "그 후, Web Bean 관리자는 Web Bean의 모든 초기화 방식을 호출합니다. "
#. Tag: para
@@ -201,7 +201,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
+msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
msgstr ""
#. Tag: title
@@ -211,7 +211,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
+msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
msgstr "Web Beans 사양은 타입 안정적 해상도 알고리즘이라는 절차를 정의하여, Web Bean 관리자가 삽입 지점에 삽입하기 위해 Web Bean을 인식할 때 이를 따르게 됩니다. 이러한 알고르짐은 처음에는 복잡하게 보이지만, 일단 이를 이해하면, 이는 다소 직관적입니다. 타입 안정적 해상도는 시스템 초기화시에 실행되어, 관리자는 사용자에 과한 정보를 즉각적으로 알게되며 Web Bean의 의존성에 만족하지 않을 경우, UnsatisfiedDependencyException 또는 AmbiguousDependencyException을 넘기게 됩니다. "
#. Tag: para
@@ -236,12 +236,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
+msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
+msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
msgstr ""
#. Tag: title
@@ -402,7 +402,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you may be thinking, "What's the different between using a qualifier and just specifying the exact implementation class you want?" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alterative implementations of @Asynchronous PaymentProcessor!"
+msgid "Now, you may be thinking, \"What's the different between using a qualifier and just specifying the exact implementation class you want?\" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alternative implementations of @Asynchronous PaymentProcessor!"
msgstr ""
#. Tag: title
@@ -412,7 +412,7 @@ msgstr "심플 Web Beans는 @PostConstruct 및 @PreD
#. Tag: para
#, no-c-format
-msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to decare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
+msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to declare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
msgstr ""
#. Tag: para
@@ -424,7 +424,7 @@ msgstr ""
#, no-c-format
msgid ""
"@Inject \n"
-"void initServices(@Any Instance<Service> services) { \n"
+"void initServices(@Any Instance<Service> services) { \n"
" for (Service service: services) {\n"
" service.init();\n"
" }\n"
@@ -460,7 +460,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then we select one of the possible member values when appling the qualifier:"
+msgid "Then we select one of the possible member values when applying the qualifier:"
msgstr ""
#. Tag: programlisting
@@ -481,7 +481,7 @@ msgid ""
"@Target({METHOD, FIELD, PARAMETER, TYPE})\n"
"public @interface PayBy {\n"
" PaymentMethod value();\n"
-" @Nonbinding String comment() default "";\n"
+" @Nonbinding String comment() default \"\";\n"
"}"
msgstr ""
"this FAQ for step-by-step instructions for how to resolve an ambigous resolution exception between a raw bean type and a producer method that returns the same bean type."
+msgid "See this FAQ for step-by-step instructions for how to resolve an ambiguous resolution exception between a raw bean type and a producer method that returns the same bean type."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Just remember: "There can be only one.""
+msgid "Just remember: \"There can be only one.\""
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
+msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
+msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
msgstr "Web Beans에서 의존성 삽입을 사용할 때 유의하셔야 할 사항이 한 가지 더 있습니다. "
#. Tag: title
@@ -664,7 +664,7 @@ msgstr "삽입된 Web Bean 클라이언트는 Web Bean 인스턴스에 직접적
#. Tag: para
#, fuzzy, no-c-format
-msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
+msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
msgstr "요청 범위로 바운딩된 Web Bean으로의 직접 참조를 보유하고 있는 애플리케이션 범위에 바운딩된 Web Bean을 가정해 봅시다. 애플리케이션 범위에 바운딩된 Web Bean은 다른 많은 요청 사이에서 공유됩니다. 하지만, 각각의 요청은 요청 범위로 바운딩된 Web Bean의 다른 인스턴스를 확인해야 합니다! "
#. Tag: para
@@ -689,7 +689,7 @@ msgstr "다음과 같은 Java 유형은 Web Bean 관리자에 의해 프록시
#. Tag: para
#, fuzzy, no-c-format
-msgid "classes which don't have a non-private constructor with no parameters, and"
+msgid "classes which don't have a non-private constructor with no parameters, and"
msgstr "매개 변수 없는 비전용 생성자를 갖지 않는 클래스, "
#. Tag: para
@@ -704,7 +704,7 @@ msgstr "배열 및 기본 유형 "
#. Tag: para
#, no-c-format
-msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
+msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
msgstr ""
#. Tag: para
@@ -714,7 +714,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "change the type of the injection point to Instance<X>,"
+msgid "change the type of the injection point to Instance<X>,"
msgstr ""
#. Tag: para
@@ -744,7 +744,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But we didn't get around to implementing this yet."
+msgid "But we didn't get around to implementing this yet."
msgstr ""
#. Tag: title
@@ -779,7 +779,7 @@ msgstr "애플리케이션은 삽입에 의해 Manager 인터
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -814,7 +814,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -829,19 +829,19 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, we need to obtain an instance of our qualifier type. Since annotatons are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
+msgid "Next, we need to obtain an instance of our qualifier type. Since annotations are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
"abstract class AsynchronousQualifier\n"
-"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
+"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
msgstr ""
" \n"
@@ -856,14 +856,14 @@ msgstr ""
#, fuzzy, no-c-format
msgid ""
"PaymentProcessor p = paymentProcessorSource\n"
-" .select(new AnnotationLiteral<Asynchronous>() {});"
+" .select(new AnnotationLiteral<Asynchronous>() {});"
msgstr ""
"(){});]]>"
#. Tag: para
#, no-c-format
-msgid "We can't use an anonymous class to implement a qualifier type with members."
+msgid "However, we can't use an anonymous class to implement a qualifier type with members."
msgstr ""
#. Tag: para
@@ -911,7 +911,7 @@ msgstr "@Dependent 범위와 함께 Web Bean은 Inje
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
+msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
msgstr "다음 예를 살펴봅시다. 다음과 같은 코드는 프로그램을 리팩토링하기에 취약하고 장황합니다: "
#. Tag: programlisting
@@ -955,7 +955,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
+msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
msgstr "확신하시지 않습니까? 그러시다면 여기에 두 번째 예제가 있습니다. HTTP 매개 변수를 삽입하려면, 바인딩 유형을 정의해야 합니다: "
#. Tag: programlisting
@@ -983,8 +983,8 @@ msgstr "다음과 같이 삽입 지점에서 이러한 바인딩 유형을 사
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@HttpParam("username") String username;\n"
-"@HttpParam("password") String password;"
+"@HttpParam(\"username\") String username;\n"
+"@HttpParam(\"password\") String password;"
msgstr ""
""
@@ -999,7 +999,7 @@ msgstr "다음의 생산자 방식은 다음과 같이 작업합니다: "
msgid ""
"class HttpParams\n"
"\n"
-" @Produces @HttpParam("")\n"
+" @Produces @HttpParam(\"\")\n"
" String getParamValue(InjectionPoint ip) {\n"
" ServletRequest request = (ServletRequest) FacesContext.getCurrentInstance().getExternalContext().getRequest();\n"
" return request.getParameter(ip.getAnnotated().getAnnotation(HttpParam.class).value());\n"
@@ -1018,7 +1018,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own prodcuer for the request and have it injected as a method parameter."
+msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own producer for the request and have it injected as a method parameter."
msgstr ""
#. Tag: para
@@ -1036,8 +1036,8 @@ msgstr "Web Bean 관리자는 InjectionPoint 인터페이스
msgid ""
"public interface InjectionPoint { \n"
" public Type getType();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Bean<?> getBean();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Bean<?> getBean();\n"
" public Member getMember();\n"
" public Annotated getAnnotated();\n"
" public boolean isDelegate();\n"
diff --git a/docs/reference/src/main/docbook/ko-KR/interceptors.po b/docs/reference/src/main/docbook/ko-KR/interceptors.po
index 29ff5f4e805..7288b979ea8 100644
--- a/docs/reference/src/main/docbook/ko-KR/interceptors.po
+++ b/docs/reference/src/main/docbook/ko-KR/interceptors.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: interceptors\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-23 11:10+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -116,7 +116,7 @@ msgstr "인터셉터 바인딩 "
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
+msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
msgstr "Web Beans의 일부는 트랜젝션할 수 있음을 명시하고자 한다고 가정합니다. 처음으로 해야할 것은 어떤 Web Beans에 관심이 있는 지를 지정하기 위해 인터셉터 바인딩 어노테이션을 합니다: "
#. Tag: programlisting
@@ -169,7 +169,7 @@ msgstr "인터셉터 구현 "
#. Tag: para
#, fuzzy, no-c-format
-msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
+msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
msgstr "행을 따라 어딘가에 이러한 트랜젝션 관리 측면을 제공하기 위해 실제적으로 인터셉터를 구현해야 합니다. 해야 할 작업은 표준 EJB 인터셉터를 생성하고 이를 @Interceptor 및 @Transactional로 어노테이션하는 것입니다. "
#. Tag: programlisting
@@ -231,16 +231,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -271,17 +271,17 @@ msgstr "예를 들어, TransactionInterceptor 이전에 보
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -384,7 +384,7 @@ msgstr "일반적으로 여러개의 인터셉터를 Web Bean에 바인딩하기
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Secure(rolesAllowed="admin") @Transactional\n"
+"@Secure(rolesAllowed=\"admin\") @Transactional\n"
"public class ShoppingCart { ... }"
msgstr ""
"meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
+msgid "Well, fortunately, CDI works around this missing feature of Java. We may annotate one interceptor binding type with other interceptor binding types (termed a meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
msgstr "다행히도 Web Beans는 이러한 생략된 Java의 기능을 해결하여 하나의 인터셉터 바인딩 유형을 다른 인터셉터 바인딩 유형과 어노테이션할 수 있습니다. 인터셉터 바인딩은 트렌젝션 가능하여 첫번째 인터셉터 바인딩이 있는 Web Bean은 메타 어노테이션으로 명시된 인터셉터 바인딩을 상속할 수 있습니다. "
#. Tag: programlisting
@@ -539,7 +539,7 @@ msgstr "인터셉터는 배치시 쉽게 비활성화할 수 없습니다, "
#. Tag: para
#, fuzzy, 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."
+msgid "the interceptor ordering is non-global — it is determined by the order in which interceptors are listed at the class level."
msgstr "인터셉터 순서는 비전역적입니다 이는 클래스 레벨로 열거된 인터셉터 순서에 의해 결정됩니다. "
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ko-KR/intro.po b/docs/reference/src/main/docbook/ko-KR/intro.po
index 1d85d8b0e8c..0b04af5ec13 100644
--- a/docs/reference/src/main/docbook/ko-KR/intro.po
+++ b/docs/reference/src/main/docbook/ko-KR/intro.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: intro\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-29 14:49+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -38,7 +38,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
+msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
msgstr "첫 번째 Web Bean 작성을 시작해 보시겠습니까? 혹은 어떤 종류의 Web Beans 사양을 통해 도약하게 될 지를 의아해 하거나 의심하고 계실 수 도 있겠군요! 한 가지 좋은 정보는 여러분은 이미 수백개의 혹은 수천개의 Web Beans을 이미 작성 및 사용하고 계셨다는 것입니다. 아마 여러분은 처음으로 작성하신 Web Beans를 기억하지 못하고 계실 수 도 있습니다. "
#. Tag: title
@@ -53,27 +53,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Prior to Java EE 6, there was no clear definition of the term "bean" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications "beans" for years. There were even a couple of different kinds of things called "beans" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a "bean". What we've been missing is a common definition."
+msgid "Prior to Java EE 6, there was no clear definition of the term \"bean\" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications \"beans\" for years. There were even a couple of different kinds of things called \"beans\" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a \"bean\". What we've been missing is a common definition."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
+msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
+msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
+msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now let's see how to create your first bean that actually uses CDI."
+msgid "Now let's see how to create your first bean that actually uses CDI."
msgstr ""
#. Tag: title
@@ -83,14 +83,14 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
+msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
msgstr "다양한 애플리케이션에서 오랫동안 사용해 온 두 개의 Java 클래스를 갖고 있다고 가정합시다. 첫 번째 클래스는 문자열을 문장 목록으로 구문 분석합니다: "
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
"public class SentenceParser {\n"
-" public List<String> parse(String text) { ... }\n"
+" public List<String> parse(String text) { ... }\n"
"}"
msgstr ""
"TextTranslator@Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
+msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
msgstr "예상하셨듯이, @Initializer 어노테이션은 의존성 삽입을 사용하여 실행하기 위한 무엇인가를 갖고 있습니다! @Initializer는 생성자 또는 Web Bean 방식에 적용될 수 있으며, Web Bean을 인스턴스화할 때 Web Bean 관리자에게 생성자 또는 Web Bean 방식을 호출할 것을 지시합니다. Web Bean 관리자는 기타 다른 Web Beans를 생성자 또는 방식의 매개 변수에 삽입하게 됩니다. "
#. Tag: para
@@ -198,7 +198,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
+msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
msgstr ""
#. Tag: programlisting
@@ -237,7 +237,7 @@ msgstr "여기서 Translator는 로컬 인터페이스입니
#. Tag: para
#, no-c-format
-msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
+msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
msgstr ""
#. Tag: para
@@ -248,7 +248,7 @@ msgstr "인스턴스를 Web Bean, Servlet 또는 EJB로 삽입하여 Te
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
+"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
"...\n"
"public void translate() {\n"
" textTranslatorInstance.get().translate(inputText);\n"
@@ -261,17 +261,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
+msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
+msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
msgstr "시스템 초기화시 Web Bean 관리자는 각각의 삽입 지점을 만족시키는 하나의 Web Bean이 존재하도록 이를 유효화해야 합니다. 예에서 사용 가능한 Translator 구현이 없을 경우 SentenceTranslator EJB가 배치되지 않는 다면 Web Bean 관리자는 UnsatisfiedDependencyException을 넘기게 됩니다. 하나 이상의 Translator를 구현할 수 있을 경우, Web Bean 관리자는 AmbiguousDependencyException을 넘기게 됩니다. "
#. Tag: para
#, no-c-format
-msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
+msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
msgstr ""
#~ msgid "Getting started with Web Beans"
diff --git a/docs/reference/src/main/docbook/ko-KR/next.po b/docs/reference/src/main/docbook/ko-KR/next.po
index fcd895e749b..da2a324ef25 100644
--- a/docs/reference/src/main/docbook/ko-KR/next.po
+++ b/docs/reference/src/main/docbook/ko-KR/next.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: next\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-09 11:31+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -26,12 +26,12 @@ msgstr "다음 단계 "
#. Tag: para
#, no-c-format
-msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
+msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
+msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
msgstr "Web Beans Reference 구현은 http://seamframework.org/WebBeans에서 개발되고 있습니다. RI 개발팀 및 Web Beans 사양은 http://in.relation.to에 있는 블로그에 있습니다. 이러한 문서는 실질적으로 블로그에 게시된 기사의 시리즈를 기반으로 합니다. "
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ko-KR/part1.po b/docs/reference/src/main/docbook/ko-KR/part1.po
index 7b53c2ea616..eb332871f31 100644
--- a/docs/reference/src/main/docbook/ko-KR/part1.po
+++ b/docs/reference/src/main/docbook/ko-KR/part1.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: part1\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-27 10:42+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -135,7 +135,7 @@ msgstr "이를 명시적으로 삭제해야 합니까? "
#. Tag: para
#, fuzzy, no-c-format
-msgid "Where should I keep the reference to it when I'm not currently using it?"
+msgid "Where should I keep the reference to it when I'm not currently using it?"
msgstr "직접 사용하지 않을 경우 참조 사항을 어디에 보관해야 합니까? "
#. Tag: para
@@ -150,7 +150,7 @@ msgstr "어떻게 하면 다른 개체 사이에서 이러한 개체를 공유
#. Tag: para
#, no-c-format
-msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
+msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
msgstr ""
#. Tag: para
@@ -180,12 +180,12 @@ msgstr "데코레이터는 비지니스 문제를 구분하
#. Tag: para
#, fuzzy, no-c-format
-msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
+msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
msgstr "가장 중요하게 Web Beans는 이러한 모든 기능을 타입 안정적 (typesafe) 방식으로 제공합니다. Web Beans는 협력적 객체를 갖추기 위한 방법을 결정하기 위해 문자열 기반의 식별자를 사용하지 않습니다. XML은 옵션으로 남아있어도 거의 사용되지 않습니다. 대신 Web Beans는 바인딩 어노테이션 (binding annotations)이라는 새로운 패턴과 함께 Java 객체 모델에서 이미 사용 가능한 타이핑 정보를 사용하여 Web Beans 및 Web Beans의 의존성, 인터셉터, 데코레이터 및 이벤트 소비자를 함께 묶습니다. "
#. Tag: para
#, no-c-format
-msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
+msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr "Web Beans는 통합 지점을 제공하여 차후 Java EE 사양이나
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
+msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
msgstr "Web Beans는 Seam, Guice, Spring을 포함하여 다수의 기존 Java 프레임워크에 의해 영향을 받았지만 Web Beans은 자체적으로 다음과 같은 고유한 기능을 소유하고 있습니다: Seam 보다 더 타입 안정적, 보다 더 상태 기반적, Spring 보다 덜 XML-중심, Guice 보다 더 웹 및 엔터프라이즈-애플리케이션 사용 가능 "
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ko-KR/part3.po b/docs/reference/src/main/docbook/ko-KR/part3.po
index 37ae05eef5d..1bff20df720 100644
--- a/docs/reference/src/main/docbook/ko-KR/part3.po
+++ b/docs/reference/src/main/docbook/ko-KR/part3.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: part3\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-23 11:11+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
+msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
msgstr ""
#. Tag: para
@@ -76,7 +76,7 @@ msgstr "Web Beans의 두번째 주요 기능은 강한 타이핑 (stro
#. Tag: para
#, fuzzy, no-c-format
-msgid "You don't see string-based identifiers in CDI 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!"
+msgid "You don't see string-based identifiers in CDI 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
@@ -146,7 +146,7 @@ msgstr "Web Beans의 전형적인 역할은 이러한 기
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
+msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
msgstr "이제 Web Beans의 보다 고급 기능에 대해 알아볼 준비가 되었습니다. 이러한 기능은 코드를 보다 쉽게 유효화하고 이해 가능하게 하기 위해 존재하는 것임을 명심하시기 바랍니다. 대부분 이러한 기능을 사용할 필요가 없지만 이를 보다 효과적으로 사용할 경우, 이러한 기능에 감사하게 될 것입니다. "
#~ msgid "Even Web Beans XML metadata is strongly typed! There's no compiler for XML, so Web Beans takes advantage of XML schemas to validate the Java types and attributes that appear in XML. This approach turns out to make the XML more literate, just like annotations made our Java code more literate."
diff --git a/docs/reference/src/main/docbook/ko-KR/part4.po b/docs/reference/src/main/docbook/ko-KR/part4.po
index f5184a0dd43..76234d2f1ea 100644
--- a/docs/reference/src/main/docbook/ko-KR/part4.po
+++ b/docs/reference/src/main/docbook/ko-KR/part4.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: part4\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-13 16:06+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
+msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
msgstr ""
#. Tag: para
@@ -31,7 +31,7 @@ msgstr "EJB가 JSF 페이지에 직접 바운딩되게 하여 Web Beans이 어
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
+msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
msgstr "Web Beans을 사용하는 애플리케이션에서 Java EE 플랫폼의 장점을 최대한으로 활용하는 방법에 대해 살펴보겠습니다. 또한 Web Beans에 휴대용 확장을 지원하기 위해 제공되는 SPI 설정에 대해서도 간략하게 살펴보겠습니다. 이러한 SPI 기능을 직접 사용할 필요가 없을 수 도 있지만, 만약 필요할 경우 이러한 기능한 기능이 있다는 것을 알아두시면 좋습니다. 가장 중요하게 제삼자 확장 기능을 사용할 때 마다 이러한 기능의 장점을 간접적으로 활용할 수 있습니다. "
#~ msgid "The third theme of Web Beans is integration. Web Beans was designed to work in concert with other technologies, helping the application developer fit the other technologies together. Web Beans is an open technology. It forms a part of the Java EE ecosystem, and is itself the foundation for a new ecosystem of portable extensions and integration with existing frameworks and technologies."
diff --git a/docs/reference/src/main/docbook/ko-KR/part5.po b/docs/reference/src/main/docbook/ko-KR/part5.po
index 9071616d04f..c00e43d73e2 100644
--- a/docs/reference/src/main/docbook/ko-KR/part5.po
+++ b/docs/reference/src/main/docbook/ko-KR/part5.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-28 17:09+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and Glassfish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
+msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and GlassFish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ko-KR/producermethods.po b/docs/reference/src/main/docbook/ko-KR/producermethods.po
index 1633faa4666..44dbe2b61d8 100644
--- a/docs/reference/src/main/docbook/ko-KR/producermethods.po
+++ b/docs/reference/src/main/docbook/ko-KR/producermethods.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: producermethods\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-23 11:12+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -28,7 +28,7 @@ msgstr "생산자 방식 "
#. Tag: para
#, fuzzy, no-c-format
-msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
+msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
msgstr "생산자 방식은 Web Bean 관리자가 애플리케이션 대신 인스턴스 객체에 응답할 때 발생할 수 있는 특정한 한계를 극복할 수 있게 합니다. Web Beans이 아닌 객체를 Web Beans 환경으로 통합하기 위한 가장 쉬운 방법이 있습니다. (에서 두번째 방법에 대해 살펴보겠습니다.) "
#. Tag: para
@@ -83,7 +83,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
+msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
msgstr ""
#. Tag: programlisting
@@ -165,7 +165,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
+msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
msgstr "이제 생산자 방식이 호출되면, 반환된 PaymentStrategy는 세션 컨텍스트로 바운드됩니다. 동일한 세션에서 생산자 방식은 다시 호출되지 않습니다. "
#. Tag: para
@@ -180,12 +180,12 @@ msgstr "생산자 방식으로 삽입 "
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
+msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
msgstr "위의 코드에 한 가지 문제가 있을 수 있습니다. CreditCardPaymentStrategy 구현은 Java new 연산자를 사용하여 인스턴스화됩니다. 애플리케이션에 의해 직접 인스턴스화된 객체는 의존성 삽입의 장점을 취할 수 없으며 인터셉터를 갖지 못합니다. "
#. Tag: para
#, fuzzy, no-c-format
-msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
+msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
msgstr "이러한 방식을 원하지 않을 경우, 의존성 삽입을 생산자 방식으로 사용하여 Web Bean 인스턴스를 획득할 수 있습니다: "
#. Tag: programlisting
@@ -217,12 +217,12 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of "promoting" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left "hanging" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
+msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of \"promoting\" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left \"hanging\" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
msgstr "CreditCardPaymentStrategy가 요청 범위 Web Bean이면 어떻게 합니까? 이럴 경우 생산자 방식은 현재 요청 범위 임스턴스를 세선 범위로 \"활성화되게\" 됩니다. 이는 버그입니다! 요청 범위 객체는 세션이 종료되기 전 Web Bean 관리자에 의해 삭제되지만, 객체에 대한 참조는 세션 범위에 \"남아 있게\" 됩니다. 이러한 오류는 Web Bean 관리자에 의해 검출되지 않으므로 생산자 방식에 Web Bean 인스턴스를 반환할 경우 각별히 주의하시기 바랍니다! "
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
+msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
msgstr "이러한 버그를 해결할 수 있는 세 가지 방법이 있습니다. CreditCardPaymentStrategy 구현 범위를 변경할 수 있지만, Web Bean의 클라이언트에 영향을 미칠 수 있습니다. 보다 나은 방법으로 생산자 방식의 범위를 @Dependent 또는 @RequestScoped로 변경하는 것입니다. "
#. Tag: para
@@ -269,7 +269,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
+msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
msgstr "CreditCardPaymentStrategy의 새로운 의존성 인스턴스가 생성되면, 생산자 방식으로 전달하고, 생산자 방식에 의해 반환된 후, 마지막으로 세션 컨텍스트로 바운딩됩니다. 의존성 객체는 세션 마지막에 Preferences 객체가 삭제될 때 까지 삭제되지 않습니다. "
#. Tag: title
diff --git a/docs/reference/src/main/docbook/ko-KR/resources.po b/docs/reference/src/main/docbook/ko-KR/resources.po
index 1b1776f962f..cc8aa1313ef 100644
--- a/docs/reference/src/main/docbook/ko-KR/resources.po
+++ b/docs/reference/src/main/docbook/ko-KR/resources.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a nonportable "mapped name"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
+msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a non-portable \"mapped name\"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
msgstr ""
#. Tag: para
@@ -72,35 +72,35 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @WebServiceRef(lookup="java:app/service/Catalog")\n"
+"@Produces @WebServiceRef(lookup=\"java:app/service/Catalog\")\n"
"Catalog catalog;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @Resource(lookup="java:global/env/jdbc/CustomerDatasource") \n"
+"@Produces @Resource(lookup=\"java:global/env/jdbc/CustomerDatasource\") \n"
"@CustomerDatabase Datasource customerDatabase;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceContext(unitName="CustomerDatabase")\n"
+"@Produces @PersistenceContext(unitName=\"CustomerDatabase\")\n"
"@CustomerDatabase EntityManager customerDatabasePersistenceContext;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceUnit(unitName="CustomerDatabase") \n"
+"@Produces @PersistenceUnit(unitName=\"CustomerDatabase\") \n"
"@CustomerDatabase EntityManagerFactory customerDatabasePersistenceUnit;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @EJB(ejbLink="../their.jar#PaymentService") \n"
+"@Produces @EJB(ejbLink=\"../their.jar#PaymentService\") \n"
"PaymentService paymentService;"
msgstr ""
@@ -126,7 +126,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
+msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
msgstr ""
#. Tag: title
@@ -171,7 +171,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
+msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
msgstr ""
#. Tag: programlisting
@@ -186,7 +186,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@PersistenceContext(unitName="CustomerDatabase") EntityManager"
+msgid "@PersistenceContext(unitName=\"CustomerDatabase\") EntityManager"
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ko-KR/ri-spi.po b/docs/reference/src/main/docbook/ko-KR/ri-spi.po
index f9ecb941fae..1da641fae25 100644
--- a/docs/reference/src/main/docbook/ko-KR/ri-spi.po
+++ b/docs/reference/src/main/docbook/ko-KR/ri-spi.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: ri-spi\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-19 13:32+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -43,7 +43,7 @@ msgstr "리소스 불러오기 "
#. Tag: para
#, no-c-format
-msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the "Weld: Servlets" extension will be sufficient, and will work in any container supporting the Servlet API."
+msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the \"Weld: Servlets\" extension will be sufficient, and will work in any container supporting the Servlet API."
msgstr ""
#. Tag: para
@@ -68,7 +68,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
+msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
msgstr ""
#. Tag: para
@@ -88,7 +88,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
+msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
msgstr ""
#. Tag: para
@@ -108,7 +108,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
+msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
msgstr ""
#. Tag: para
@@ -118,12 +118,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
+msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
+msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
msgstr ""
#. Tag: para
@@ -138,7 +138,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
+msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
msgstr ""
#. Tag: para
@@ -168,7 +168,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
+msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
msgstr ""
#. Tag: para
@@ -208,7 +208,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
+msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
msgstr ""
#. Tag: title
@@ -223,7 +223,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
+msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
msgstr ""
#. Tag: para
@@ -288,7 +288,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); intercepter will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
+msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); interceptor will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
msgstr ""
#. Tag: para
@@ -363,7 +363,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
+msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
msgstr ""
#. Tag: title
@@ -378,7 +378,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programtically, or built in). Bean validation will validate all beans."
+msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programmatically, or built in). Bean validation will validate all beans."
msgstr ""
#. Tag: para
@@ -438,7 +438,7 @@ msgstr "Classloader 분리 "
#. Tag: para
#, fuzzy, no-c-format
-msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuation, classloader isolation for each CDI application."
+msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuration, classloader isolation for each CDI application."
msgstr "Web Beans RI를 다수의 애플리케이션의 운용을 지원하는 환경으로 통합할 경우, 각각의 Web Beans 애플리케이션에 대한 클래스로더 분리를 자동으로 또는 사용자 설정을 통해 반드시 활성화해야 합니다. "
#. Tag: term
@@ -453,7 +453,7 @@ msgstr "Web Beans를 Servlet 환경으로 통합할 경우, Servlet을 사용하
#. Tag: para
#, no-c-format
-msgid "You must ensure that that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
+msgid "You must ensure that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
msgstr ""
#. Tag: term
@@ -594,7 +594,7 @@ msgid ""
"InjectionTarget it = weldBeanManager.fireProcessInjectionTarget(clazz);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
+"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
"\n"
"// Produce the instance, performing any constructor injection required\n"
"Object instance = it.produce();\n"
@@ -628,16 +628,16 @@ msgstr ""
msgid ""
"// Obtain the EjbDescriptor for the EJB\n"
"// You may choose to use this utility method to get the descriptor\n"
-"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
+"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
"\n"
"// Get an the Bean object\n"
-"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
+"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
"\n"
"// Create the injection target\n"
"InjectionTarget it = deploymentBeanManager.createInjectionTarget(ejbDescriptor);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
+"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
"\n"
"// Perform injection and call initializers\n"
"it.inject(instance, cc);\n"
diff --git a/docs/reference/src/main/docbook/ko-KR/scopescontexts.po b/docs/reference/src/main/docbook/ko-KR/scopescontexts.po
index 20c10b5cb26..da79a43d37f 100644
--- a/docs/reference/src/main/docbook/ko-KR/scopescontexts.po
+++ b/docs/reference/src/main/docbook/ko-KR/scopescontexts.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: scopescontexts\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-22 12:18+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -29,7 +29,7 @@ msgstr "범위 및 컨텍스트 "
#. Tag: para
#, fuzzy, no-c-format
-msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
+msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
msgstr "지금까지 범위 유형 어노테이션의 여러 가지 예를 살펴보았습니다. Web Bean의 범위는 Web Bean 인스턴스의 수명주기를 결정합니다. 또한 범위는 어떤 클라이언트가 어떤 Web Bean 인스턴스를 참조하게 할 지를 결정합니다. Web Beans 사양에 따라 범위는 다음을 결정합니다: "
#. Tag: para
@@ -54,7 +54,7 @@ msgstr "예를 들어, Web Bean 세션 범위가 있을 경우, Current
#. Tag: para
#, no-c-format
-msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
+msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
msgstr ""
#. Tag: title
@@ -64,7 +64,7 @@ msgstr "범위 유형 "
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
+msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
msgstr "Web Beans는 extensible context model을 특징으로 합니다. 새로운 범위 유형 어노테이션을 생성하여 새로운 범위를 정의할 수 있습니다: "
#. Tag: programlisting
@@ -82,7 +82,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
+msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
msgstr "물론 이는 이러한 작업 중 쉬운 부분입니다. 이러한 범위 유형을 유용하게 하려면, 범위를 구현하는 Context 객체를 정의해야 합니다! Context 구현은 아주 기술적인 작업으로, 프레임워크 개발 만을 목적으로 합니다. "
#. Tag: para
@@ -101,7 +101,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Usually, you'll use one of CDI's built-in scopes."
+msgid "Usually, you'll use one of CDI's built-in scopes."
msgstr "주로, Web Beans의 내장된 범위 중 하나를 사용하게 됩니다. "
#. Tag: title
@@ -201,7 +201,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
+msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
msgstr "네 개의 내장된 범위 중 세 개는 모든 Java EE 개발자에게 익숙하므로, 여기서 다루지 않겠습니다. 하지만 이 중 하나의 범위 새로운 것입니다. "
#. Tag: title
@@ -226,7 +226,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
+msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
msgstr "컨버세이션은 사용자 관점에서의 작업 단위, 작업 내용을 나타냅니다. 컨버세이션 컨텍스트는 현재 사용자가 작업하고 있는 것과 관련된 상태를 유지합니다. 사용자가 동시에 여러가지 작업을 실행하고 있을 경우, 여러 개의 컨버세이션이 있게 됩니다. "
#. Tag: para
@@ -349,25 +349,25 @@ msgstr "따라서, 다음과 같은 링크가 컨버세이션을 보급합니다
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "<a href="/addProduct.jsp?cid=#{conversation.id}">Add Product</a>"
+msgid "<a href=\"/addProduct.jsp?cid=#{conversation.id}\">Add Product</a>"
msgstr "Add Product]]>"
#. Tag: para
#, no-c-format
-msgid "It's probably better to use one of the link components in JSF 2:"
+msgid "It's probably better to use one of the link components in JSF 2:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:link outcome="/addProduct.xhtml" value="Add Product">\n"
-" <f:param name="cid" value="#{javax.enterprise.context.conversation.id}"/>\n"
-"</h:link>"
+"<h:link outcome=\"/addProduct.xhtml\" value=\"Add Product\">\n"
+" <f:param name=\"cid\" value=\"#{javax.enterprise.context.conversation.id}\"/>\n"
+"</h:link>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a "flash" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
+msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a \"flash\" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
msgstr "Web Bean 관리자는 컨버세이션이 장기 실행으로 표시되어 있지 않아도, 리다이렉트를 통해 컨버세이션을 보급해야 합니다. 이는 \"플래시\" 객체와 같은 깨지기 쉬운 구조에 의지하지 않고 일반적인 POST-then-redirect 패턴 쉽게 구현하게 합니다. 이러한 경우 Web Bean 관리자는 리다이렉트 URL에 요청 매개 변수를 자동으로 추가합니다. "
#. Tag: title
@@ -377,7 +377,7 @@ msgstr "컨버세이션 시간 초과 "
#. Tag: para
#, fuzzy, no-c-format
-msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
+msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
msgstr "Web Bean 관리자에게는 리소스를 보관하기 위해 컨텍스트에 있는 모든 상태 및 컨버세이션을 삭제할 수 있는 권한이 있습니다. Web Bean 관리자 구현은 주로 시간 초과에 기반하여 이를 실행합니다 이는 Web Beans 사양에 의해 요청되지 않습니다. 시간 초과는 컨버세이션이 삭제된 후 비활성화 기간을 말합니다. "
#. Tag: para
@@ -407,12 +407,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can guess what "singleton" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
+msgid "You can guess what \"singleton\" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
+msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
msgstr ""
#. Tag: para
@@ -432,7 +432,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
+msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
msgstr ""
#. Tag: para
@@ -472,12 +472,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
+msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
+msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
msgstr ""
#. Tag: para
@@ -546,7 +546,7 @@ msgstr "calculator 영역에는 Calculator
#. Tag: para
#, fuzzy, no-c-format
-msgid "This feature is particularly useful with producer methods, as we'll see in the next chapter."
+msgid "This feature is particularly useful with producer methods, as we'll see in ."
msgstr "특히 이러한 기능은 다음 장에서 다루게 될 생산자 방식에서 유용합니다. "
#~ msgid "@RequestScoped"
diff --git a/docs/reference/src/main/docbook/ko-KR/specialization.po b/docs/reference/src/main/docbook/ko-KR/specialization.po
index b0237948c7b..6f7e978c6f2 100644
--- a/docs/reference/src/main/docbook/ko-KR/specialization.po
+++ b/docs/reference/src/main/docbook/ko-KR/specialization.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: specialization\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-23 11:14+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -33,7 +33,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
+msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
msgstr ""
#. Tag: para
@@ -53,12 +53,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
+msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
+msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
msgstr ""
#. Tag: title
@@ -87,7 +87,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
+msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
msgstr "staging 환경에서, 다른 Web Bean을 사용하여 PaymentProcessor 구현을 덮어쓰기 합니다: "
#. Tag: programlisting
@@ -127,12 +127,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
+msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
+msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
msgstr ""
#. Tag: programlisting
@@ -173,16 +173,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <alternatives>\n"
-" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
-" </alternatives>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <alternatives>\n"
+" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
+" </alternatives>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -207,7 +207,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
+msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
msgstr ""
#. Tag: para
@@ -267,7 +267,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
+msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ko-KR/stereotypes.po b/docs/reference/src/main/docbook/ko-KR/stereotypes.po
index 0a286bbbd40..96e35bf720f 100644
--- a/docs/reference/src/main/docbook/ko-KR/stereotypes.po
+++ b/docs/reference/src/main/docbook/ko-KR/stereotypes.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: stereotypes\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-20 15:31+1000\n"
"Last-Translator: Eunju Kim \n"
"Language-Team: Korean \n"
@@ -106,7 +106,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
+msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
msgstr ""
#. Tag: title
@@ -149,7 +149,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
+msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
msgstr ""
#. Tag: title
@@ -269,12 +269,12 @@ msgstr "스테레오타입 (Stereotypes) "
#. Tag: para
#, no-c-format
-msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
+msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
+msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
msgstr ""
#. Tag: programlisting
@@ -301,7 +301,7 @@ msgstr "표준 스테레오타입 "
#. Tag: para
#, fuzzy, no-c-format
-msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
+msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
msgstr "Web Beans 사양에 의해 정의된 두가지 표준 스테레오타입 @Interceptor 및 @Decorator를 살펴보았습니다. "
#. Tag: para
diff --git a/docs/reference/src/main/docbook/ko-KR/weldexamples.po b/docs/reference/src/main/docbook/ko-KR/weldexamples.po
index d06c2098a54..7f110fbda7e 100644
--- a/docs/reference/src/main/docbook/ko-KR/weldexamples.po
+++ b/docs/reference/src/main/docbook/ko-KR/weldexamples.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
+msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
msgstr ""
#. Tag: title
@@ -31,75 +31,75 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
+msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
+msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
+msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<faces-config version="2.0"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<faces-config version=\"2.0\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd">\n"
-"</faces-config>"
+" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd\">\n"
+"</faces-config>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
+msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, there's the familiar web.xml:"
+msgid "Finally, there's the familiar web.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<web-app version="2.5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<web-app version=\"2.5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd\">\n"
" \n"
-" <display-name>weld-jsf-numberguess-war</display-name>\n"
-" <description>Weld JSF numberguess example (war)</description>\n"
+" <display-name>weld-jsf-numberguess-war</display-name>\n"
+" <description>Weld JSF numberguess example (war)</description>\n"
"\n"
-" <servlet>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
-" <load-on-startup>1</load-on-startup>\n"
-" </servlet>\n"
+" <servlet>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
+" <load-on-startup>1</load-on-startup>\n"
+" </servlet>\n"
"\n"
-" <servlet-mapping>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <url-pattern>*.jsf</url-pattern>\n"
-" </servlet-mapping>\n"
+" <servlet-mapping>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <url-pattern>*.jsf</url-pattern>\n"
+" </servlet-mapping>\n"
" \n"
-" <context-param>\n"
-" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
-" <param-value>.xhtml</param-value>\n"
-" </context-param>\n"
+" <context-param>\n"
+" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
+" <param-value>.xhtml</param-value>\n"
+" </context-param>\n"
"\n"
-" <session-config>\n"
-" <session-timeout>10</session-timeout>\n"
-" </session-config>\n"
+" <session-config>\n"
+" <session-timeout>10</session-timeout>\n"
+" </session-config>\n"
"\n"
-"</web-app>"
+"</web-app>"
msgstr ""
#. Tag: para
@@ -129,51 +129,51 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
+msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"\n"
-" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">\n"
-"<html xmlns="http://www.w3.org/1999/xhtml"\n"
-" xmlns:ui="http://java.sun.com/jsf/facelets"\n"
-" xmlns:h="http://java.sun.com/jsf/html"\n"
-" xmlns:f="http://java.sun.com/jsf/core">\n"
+"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
+" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n"
+"<html xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" xmlns:ui=\"http://java.sun.com/jsf/facelets\"\n"
+" xmlns:h=\"http://java.sun.com/jsf/html\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\">\n"
"\n"
-" <ui:composition template="/template.xhtml">\n"
-" <ui:define name="content">\n"
-" <h1>Guess a number...</h1>\n"
-" <h:form id="numberGuess">\n"
-" <div style="color: red">\n"
-" <h:messages id="messages" globalOnly="false"/>\n"
-" <h:outputText id="Higher" value="Higher!"\n"
-" rendered="#{game.number gt game.guess and game.guess ne 0}"/>\n"
-" <h:outputText id="Lower" value="Lower!"\n"
-" rendered="#{game.number lt game.guess and game.guess ne 0}"/>\n"
-" </div>\n"
+" <ui:composition template=\"/template.xhtml\">\n"
+" <ui:define name=\"content\">\n"
+" <h1>Guess a number...</h1>\n"
+" <h:form id=\"numberGuess\">\n"
+" <div style=\"color: red\">\n"
+" <h:messages id=\"messages\" globalOnly=\"false\"/>\n"
+" <h:outputText id=\"Higher\" value=\"Higher!\"\n"
+" rendered=\"#{game.number gt game.guess and game.guess ne 0}\"/>\n"
+" <h:outputText id=\"Lower\" value=\"Lower!\"\n"
+" rendered=\"#{game.number lt game.guess and game.guess ne 0}\"/>\n"
+" </div>\n"
" \n"
-" <div>\n"
-" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
+" <div>\n"
+" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
" You have #{game.remainingGuesses} guesses remaining.\n"
-" </div>\n"
+" </div>\n"
" \n"
-" <div>\n"
+" <div>\n"
" Your guess: \n"
-" <h:inputText id="inputGuess" value="#{game.guess}"\n"
-" size="3" required="true" disabled="#{game.number eq game.guess}"\n"
-" validator="#{game.validateNumberRange}"/>\n"
-" <h:commandButton id="guessButton" value="Guess" \n"
-" action="#{game.check}" disabled="#{game.number eq game.guess}"/>\n"
-" </div>\n"
-" <div>\n"
-" <h:commandButton id="restartButton" value="Reset" action="#{game.reset}" immediate="true"/>\n"
-" </div>\n"
-" </h:form>\n"
-" </ui:define>\n"
-" </ui:composition>\n"
-"</html>"
+" <h:inputText id=\"inputGuess\" value=\"#{game.guess}\"\n"
+" size=\"3\" required=\"true\" disabled=\"#{game.number eq game.guess}\"\n"
+" validator=\"#{game.validateNumberRange}\"/>\n"
+" <h:commandButton id=\"guessButton\" value=\"Guess\" \n"
+" action=\"#{game.check}\" disabled=\"#{game.number eq game.guess}\"/>\n"
+" </div>\n"
+" <div>\n"
+" <h:commandButton id=\"restartButton\" value=\"Reset\" action=\"#{game.reset}\" immediate=\"true\"/>\n"
+" </div>\n"
+" </h:form>\n"
+" </ui:define>\n"
+" </ui:composition>\n"
+"</html>"
msgstr ""
#. Tag: para
@@ -183,7 +183,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are a number of messages which can be sent to the user, "Higher!", "Lower!" and "Correct!""
+msgid "There are a number of messages which can be sent to the user, \"Higher!\", \"Lower!\" and \"Correct!\""
msgstr ""
#. Tag: para
@@ -198,7 +198,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
+msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
msgstr ""
#. Tag: para
@@ -266,7 +266,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Generator is application scoped, so we don't get a different random each time."
+msgid "The Generator is application scoped, so we don't get a different random each time."
msgstr ""
#. Tag: para
@@ -276,12 +276,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
+msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
+msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
msgstr ""
#. Tag: programlisting
@@ -298,19 +298,19 @@ msgid ""
" private int remainingGuesses;\n"
"\n"
" @Inject @MaxNumber private int maxNumber;\n"
-" @Inject @Random Instance<Integer> randomNumber;\n"
+" @Inject @Random Instance<Integer> randomNumber;\n"
" \n"
" public Game() {}\n"
" \n"
" public void check() {\n"
-" if (guess > number) {\n"
+" if (guess > number) {\n"
" biggest = guess - 1;\n"
" }\n"
-" else if (guess < number) {\n"
+" else if (guess < number) {\n"
" smallest = guess + 1;\n"
" }\n"
" else if (guess == number) {\n"
-" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage("Correct!"));\n"
+" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage(\"Correct!\"));\n"
" }\n"
" remainingGuesses--;\n"
" }\n"
@@ -325,18 +325,18 @@ msgid ""
" }\n"
" \n"
" public void validateNumberRange(FacesContext context, UIComponent toValidate, Object value) {\n"
-" if (remainingGuesses <= 0) {\n"
-" FacesMessage message = new FacesMessage("No guesses left!");\n"
+" if (remainingGuesses <= 0) {\n"
+" FacesMessage message = new FacesMessage(\"No guesses left!\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" ((UIInput) toValidate).setValid(false);\n"
" return;\n"
" }\n"
" int input = (Integer) value;\n"
"\n"
-" if (input < smallest || input > biggest) {\n"
+" if (input < smallest || input > biggest) {\n"
" ((UIInput) toValidate).setValid(false);\n"
"\n"
-" FacesMessage message = new FacesMessage("Invalid guess");\n"
+" FacesMessage message = new FacesMessage(\"Invalid guess\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" }\n"
" }\n"
@@ -385,20 +385,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
+msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
+msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
msgstr ""
#. Tag: title
@@ -418,17 +418,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin ."
+msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects . Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
+msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects. Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This will create a project in your workspace called weld-se-numberguess ."
+msgid "This will create a project in your workspace called weld-se-numberguess."
msgstr ""
#. Tag: para
@@ -438,7 +438,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to get the example running!"
+msgid "It's time to get the example running!"
msgstr ""
#. Tag: title
@@ -448,12 +448,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
+msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right click on the project, and choose Run As -> Run As Application:"
+msgid "Right click on the project, and choose Run As -> Run As Application:"
msgstr ""
#. Tag: para
@@ -503,7 +503,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's have a look at the significant code and configuration files that make up this example."
+msgid "Let's have a look at the significant code and configuration files that make up this example."
msgstr ""
#. Tag: para
@@ -513,7 +513,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
+msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
msgstr ""
#. Tag: programlisting
@@ -558,7 +558,7 @@ msgid ""
"\n"
" public boolean isGameLost()\n"
" {\n"
-" return guess != number && remainingGuesses <= 0;\n"
+" return guess != number && remainingGuesses <= 0;\n"
" }\n"
"\n"
" public boolean check()\n"
@@ -567,12 +567,12 @@ msgid ""
"\n"
" if (checkNewNumberRangeIsValid())\n"
" {\n"
-" if (guess > number)\n"
+" if (guess > number)\n"
" {\n"
" biggest = guess - 1;\n"
" }\n"
"\n"
-" if (guess < number)\n"
+" if (guess < number)\n"
" {\n"
" smallest = guess + 1;\n"
" }\n"
@@ -590,7 +590,7 @@ msgid ""
"\n"
" private boolean checkNewNumberRangeIsValid()\n"
" {\n"
-" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
+" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
" }\n"
"\n"
" @PostConstruct\n"
@@ -607,12 +607,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
+msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
+msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
msgstr ""
#. Tag: para
@@ -642,12 +642,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
+msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
+msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
msgstr ""
#. Tag: programlisting
@@ -660,11 +660,11 @@ msgid ""
"\n"
" public String getChallengeMessage()\n"
" {\n"
-" StringBuilder challengeMsg = new StringBuilder("I'm thinking of a number between ");\n"
+" StringBuilder challengeMsg = new StringBuilder(\"I'm thinking of a number between \");\n"
" challengeMsg.append(game.getSmallest());\n"
-" challengeMsg.append(" and ");\n"
+" challengeMsg.append(\" and \");\n"
" challengeMsg.append(game.getBiggest());\n"
-" challengeMsg.append(". Can you guess what it is?");\n"
+" challengeMsg.append(\". Can you guess what it is?\");\n"
"\n"
" return challengeMsg.toString();\n"
" }\n"
@@ -673,34 +673,34 @@ msgid ""
" {\n"
" if (game.isGameWon())\n"
" {\n"
-" return "You guessed it! The number was " + game.getNumber();\n"
+" return \"You guessed it! The number was \" + game.getNumber();\n"
" }\n"
" else if (game.isGameLost())\n"
" {\n"
-" return "You are fail! The number was " + game.getNumber();\n"
+" return \"You are fail! The number was \" + game.getNumber();\n"
" }\n"
" else if (!game.isValidNumberRange())\n"
" {\n"
-" return "Invalid number range!";\n"
+" return \"Invalid number range!\";\n"
" }\n"
" else if (game.getRemainingGuesses() == Game.MAX_NUM_GUESSES)\n"
" {\n"
-" return "What is your first guess?";\n"
+" return \"What is your first guess?\";\n"
" }\n"
" else\n"
" {\n"
" String direction = null;\n"
"\n"
-" if (game.getGuess() < game.getNumber())\n"
+" if (game.getGuess() < game.getNumber())\n"
" {\n"
-" direction = "Higher";\n"
+" direction = \"Higher\";\n"
" }\n"
" else\n"
" {\n"
-" direction = "Lower";\n"
+" direction = \"Lower\";\n"
" }\n"
"\n"
-" return direction + "! You have " + game.getRemainingGuesses() + " guesses left.";\n"
+" return direction + \"! You have \" + game.getRemainingGuesses() + \" guesses left.\";\n"
" }\n"
" }\n"
"}"
@@ -713,7 +713,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
+msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
msgstr ""
#. Tag: para
@@ -783,7 +783,7 @@ msgid ""
" private void refreshUI() {\n"
" mainLabel.setText( msgGenerator.getChallengeMessage() );\n"
" messageLabel.setText( msgGenerator.getResultMessage() );\n"
-" guessText.setText( "" );\n"
+" guessText.setText( \"\" );\n"
" guessesLeftBar.setValue( game.getRemainingGuesses() );\n"
" guessText.requestFocus();\n"
" }\n"
@@ -818,7 +818,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
+msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
msgstr ""
#. Tag: para
@@ -828,7 +828,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Calls game.check() to validate and perform one 'turn' of the game"
+msgid "Calls game.check() to validate and perform one 'turn' of the game"
msgstr ""
#. Tag: para
@@ -853,7 +853,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
+msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
msgstr ""
#. Tag: para
@@ -863,25 +863,25 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
+msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<plugin>\n"
-" <groupId>org.apache.maven.plugins</groupId>\n"
-" <artifactId>maven-ear-plugin</artifactId>\n"
-" <configuration>\n"
-" <modules>\n"
-" <webModule>\n"
-" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
-" <artifactId>weld-jsf-translator-war</artifactId>\n"
-" <contextRoot>/weld-translator</contextRoot>\n"
-" </webModule>\n"
-" </modules>\n"
-" </configuration>\n"
-"</plugin>"
+"<plugin>\n"
+" <groupId>org.apache.maven.plugins</groupId>\n"
+" <artifactId>maven-ear-plugin</artifactId>\n"
+" <configuration>\n"
+" <modules>\n"
+" <webModule>\n"
+" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
+" <artifactId>weld-jsf-translator-war</artifactId>\n"
+" <contextRoot>/weld-translator</contextRoot>\n"
+" </webModule>\n"
+" </modules>\n"
+" </configuration>\n"
+"</plugin>"
msgstr ""
#. Tag: para
@@ -891,72 +891,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
+msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<application version="5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<application version=\"5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/application_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/application_5.xsd\">\n"
"\n"
-" <display-name>weld-jsf-translator-ear</display-name>\n"
-" <description>The Weld JSF translator example (ear)</description>\n"
+" <display-name>weld-jsf-translator-ear</display-name>\n"
+" <description>The Weld JSF translator example (ear)</description>\n"
" \n"
-" <module>\n"
-" <web>\n"
-" <web-uri>weld-translator.war</web-uri>\n"
-" <context-root>/weld-translator</context-root>\n"
-" </web>\n"
-" </module>\n"
-" <module>\n"
-" <ejb>weld-translator.jar</ejb>\n"
-" </module>\n"
-"</application>"
+" <module>\n"
+" <web>\n"
+" <web-uri>weld-translator.war</web-uri>\n"
+" <context-root>/weld-translator</context-root>\n"
+" </web>\n"
+" </module>\n"
+" <module>\n"
+" <ejb>weld-translator.jar</ejb>\n"
+" </module>\n"
+"</application>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
+msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (ommitted here for brevity):"
+msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (omitted here for brevity):"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:form id="translator">\n"
+"<h:form id=\"translator\">\n"
"\n"
-" <table>\n"
-" <tr align="center" style="font-weight: bold">\n"
-" <td>\n"
+" <table>\n"
+" <tr align=\"center\" style=\"font-weight: bold\">\n"
+" <td>\n"
" Your text\n"
-" </td>\n"
-" <td>\n"
+" </td>\n"
+" <td>\n"
" Translation\n"
-" </td>\n"
-" </tr>\n"
-" <tr>\n"
-" <td>\n"
-" <h:inputTextarea id="text" value="#{translator.text}" required="true" rows="5" cols="80"/>\n"
-" </td>\n"
-" <td>\n"
-" <h:outputText value="#{translator.translatedText}"/>\n"
-" </td>\n"
-" </tr>\n"
-" </table>\n"
-" <div>\n"
-" <h:commandButton id="button" value="Translate" action="#{translator.translate}"/>\n"
-" </div>\n"
+" </td>\n"
+" </tr>\n"
+" <tr>\n"
+" <td>\n"
+" <h:inputTextarea id=\"text\" value=\"#{translator.text}\" required=\"true\" rows=\"5\" cols=\"80\"/>\n"
+" </td>\n"
+" <td>\n"
+" <h:outputText value=\"#{translator.translatedText}\"/>\n"
+" </td>\n"
+" </tr>\n"
+" </table>\n"
+" <div>\n"
+" <h:commandButton id=\"button\" value=\"Translate\" action=\"#{translator.translate}\"/>\n"
+" </div>\n"
" \n"
-"</h:form>"
+"</h:form>"
msgstr ""
#. Tag: para
@@ -966,12 +966,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
+msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
+msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
msgstr ""
#. Tag: para
@@ -995,7 +995,7 @@ msgid ""
" public String translate(String text) { \n"
" StringBuilder sb = new StringBuilder(); \n"
" for (String sentence: sentenceParser.parse(text)) { \n"
-" sb.append(translator.translate(sentence)).append(". "); \n"
+" sb.append(translator.translate(sentence)).append(\". \"); \n"
" } \n"
" return sb.toString().trim(); \n"
" }\n"
@@ -1005,7 +1005,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
+msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
msgstr ""
#. Tag: programlisting
@@ -1015,7 +1015,7 @@ msgid ""
"public class SentenceTranslator implements Translator { \n"
"\n"
" public String translate(String sentence) { \n"
-" return "Lorem ipsum dolor sit amet"; \n"
+" return \"Lorem ipsum dolor sit amet\"; \n"
" }\n"
"\n"
"}"
@@ -1031,7 +1031,7 @@ msgstr ""
msgid ""
"@Stateful\n"
"@RequestScoped\n"
-"@Named("translator")\n"
+"@Named(\"translator\")\n"
"public class TranslatorControllerBean implements TranslatorController {\n"
"\n"
" @Inject private TextTranslator translator;\n"
diff --git a/docs/reference/src/main/docbook/pot/Author_Group.pot b/docs/reference/src/main/docbook/pot/Author_Group.pot
index c095366952e..f03e7266050 100644
--- a/docs/reference/src/main/docbook/pot/Author_Group.pot
+++ b/docs/reference/src/main/docbook/pot/Author_Group.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
-"PO-Revision-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/docs/reference/src/main/docbook/pot/Book_Info.pot b/docs/reference/src/main/docbook/pot/Book_Info.pot
index 18bf72002f9..3673d1aacc9 100644
--- a/docs/reference/src/main/docbook/pot/Book_Info.pot
+++ b/docs/reference/src/main/docbook/pot/Book_Info.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
-"PO-Revision-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/docs/reference/src/main/docbook/pot/Weld_-_JSR-299_Reference_Implementation.pot b/docs/reference/src/main/docbook/pot/Weld_-_JSR-299_Reference_Implementation.pot
new file mode 100644
index 00000000000..f4baccac014
--- /dev/null
+++ b/docs/reference/src/main/docbook/pot/Weld_-_JSR-299_Reference_Implementation.pot
@@ -0,0 +1,59 @@
+#
+# AUTHOR , YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "A note about naming and nomenclature"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Shortly before the final draft of JSR-299 was submitted, the specification changed its name from \"Web Beans\" to \"Java Contexts and Dependency Injection for the Java EE platform\", abbreviated CDI. For a brief period after the renaming, the reference implementation adopted the name \"Web Beans\". However, this ended up causing more confusion than it solved and Red Hat decided to change the name of the reference implementation to \"Weld\". You may still find other documentation, blogs, forum posts, etc. that use the old nomenclature. Please update any references you can. The naming game is over."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You'll also find that some of the functionality that once existed in the specification is now missing, such as defining beans in XML. These features will be available as portable extensions for CDI in the Weld project, and perhaps other implementations."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this reference guide was started while changes were still being made to the specification. We've done our best to update it for accuracy. If you discover a conflict between what is written in this guide and the specification, the specification is the authority—assume it is correct. If you believe you have found an error in the specification, please report it to the JSR-299 EG."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Beans"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Start with Weld, the CDI Reference Implementation"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Loose coupling with strong typing"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "CDI and the Java EE ecosystem"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Weld Reference Guide"
+msgstr ""
+
diff --git a/docs/reference/src/main/docbook/pot/beans.pot b/docs/reference/src/main/docbook/pot/beans.pot
index d73870b40ab..4ad5a3068bf 100644
--- a/docs/reference/src/main/docbook/pot/beans.pot
+++ b/docs/reference/src/main/docbook/pot/beans.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
-"PO-Revision-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -24,7 +24,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
+msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
msgstr ""
#. Tag: para
@@ -54,7 +54,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
+msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
msgstr ""
#. Tag: para
@@ -74,7 +74,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
+msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
msgstr ""
#. Tag: title
@@ -129,7 +129,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's see what all this new terminology means."
+msgid "Let's see what all this new terminology means."
msgstr ""
#. Tag: title
@@ -139,7 +139,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a "contract" that must be satisfied by the bean to be injected. The contract is:"
+msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a \"contract\" that must be satisfied by the bean to be injected. The contract is:"
msgstr ""
#. Tag: para
@@ -161,14 +161,14 @@ msgstr ""
#, no-c-format
msgid "public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
+msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
msgstr ""
#. Tag: para
@@ -188,12 +188,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
+msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
+msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
msgstr ""
#. Tag: programlisting
@@ -201,19 +201,19 @@ msgstr ""
msgid "@Typed(Shop.class)\n"
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of "quality" using a qualifier."
+msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of \"quality\" using a qualifier."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
+msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
msgstr ""
#. Tag: programlisting
@@ -226,12 +226,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
+msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
+msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
msgstr ""
#. Tag: para
@@ -246,12 +246,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
+msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
msgstr ""
#. Tag: para
@@ -268,12 +263,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If a bean does not explicitly specify a qualifier, it has the default qualifier, @Default."
+msgid "If a bean or an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
+msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
msgstr ""
#. Tag: title
@@ -304,7 +299,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
+msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
msgstr ""
#. Tag: para
@@ -314,7 +309,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk more about scopes in ."
+msgid "We'll talk more about scopes in ."
msgstr ""
#. Tag: title
@@ -334,7 +329,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "public @SessionScoped @Named("cart")\n"
+msgid "public @SessionScoped @Named(\"cart\")\n"
"class ShoppingCart implements Serializable { ... }"
msgstr ""
@@ -345,9 +340,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<h:dataTable value="#{cart.lineItems}" var="item">\n"
+msgid "<h:dataTable value=\"#{cart.lineItems}\" var=\"item\">\n"
" ...\n"
-"</h:dataTable>"
+"</h:dataTable>"
msgstr ""
#. Tag: para
@@ -378,7 +373,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
+msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
msgstr ""
#. Tag: programlisting
@@ -404,12 +399,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
+msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
+msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
msgstr ""
#. Tag: para
@@ -455,17 +450,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
+msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
+msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
+msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
msgstr ""
#. Tag: title
@@ -475,7 +470,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
+msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
msgstr ""
#. Tag: title
@@ -485,7 +480,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
+msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
msgstr ""
#. Tag: para
@@ -510,7 +505,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It has an appropriate constructor—either:"
+msgid "It has an appropriate constructor—either:"
msgstr ""
#. Tag: para
@@ -525,7 +520,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
+msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
msgstr ""
#. Tag: para
@@ -570,12 +565,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
+msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
+msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
msgstr ""
#. Tag: para
@@ -610,7 +605,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
+msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
msgstr ""
#. Tag: para
@@ -625,17 +620,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
+msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
+msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're "heavyweight". It's nothing more than superstition to think that something is "heavier" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like "heavyweight"."
+msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're \"heavyweight\". It's nothing more than superstition to think that something is \"heavier\" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like \"heavyweight\"."
msgstr ""
#. Tag: title
@@ -674,7 +669,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
+msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
msgstr ""
#. Tag: programlisting
@@ -689,7 +684,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<p>Your raffle number is #{randomNumber}.</p>"
+msgid "<p>Your raffle number is #{randomNumber}.</p>"
msgstr ""
#. Tag: para
@@ -729,14 +724,14 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Produces Set<Roles> getRoles(User user) {\n"
+msgid "@Produces Set<Roles> getRoles(User user) {\n"
" return user.getRoles();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk much more about producer methods in ."
+msgid "We'll talk much more about producer methods in ."
msgstr ""
#. Tag: title
@@ -746,14 +741,14 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
+msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "public class Shop {\n"
" @Produces PaymentProcessor paymentProcessor = ....;\n"
-" @Produces @Catalog List<Product> products = ....;\n"
+" @Produces @Catalog List<Product> products = ....;\n"
"}"
msgstr ""
@@ -764,6 +759,6 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
+msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
msgstr ""
diff --git a/docs/reference/src/main/docbook/pot/configure.pot b/docs/reference/src/main/docbook/pot/configure.pot
index 136af82617d..f2eb9fc7364 100644
--- a/docs/reference/src/main/docbook/pot/configure.pot
+++ b/docs/reference/src/main/docbook/pot/configure.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
-"PO-Revision-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -29,49 +29,49 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
+msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<?xml version="1.0" encoding="UTF-8"?>\n"
-"<beans xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \n"
-" xmlns:weld="http://jboss.org/schema/weld/beans" \n"
-" xsi:schemaLocation="\n"
+msgid "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<beans xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" \n"
+" xmlns:weld=\"http://jboss.org/schema/weld/beans\" \n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee http://docs.jboss.org/cdi/beans_1_0.xsd\n"
-" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">\n"
+" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd\">\n"
" \n"
-" <weld:scan>\n"
+" <weld:scan>\n"
" \n"
-" <!-- Don't deploy the classes for the swing app! -->\n"
-" <weld:exclude name="com.acme.swing.**" />\n"
+" <!-- Don't deploy the classes for the swing app! -->\n"
+" <weld:exclude name=\"com.acme.swing.**\" />\n"
" \n"
-" <!-- Don't include GWT support if GWT is not installed -->\n"
-" <weld:exclude name="com.acme.gwt.**">\n"
-" <weld:if-class-available name="!com.google.GWT"/>\n"
-" </weld:exclude>\n"
+" <!-- Don't include GWT support if GWT is not installed -->\n"
+" <weld:exclude name=\"com.acme.gwt.**\">\n"
+" <weld:if-class-available name=\"!com.google.GWT\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
+" <!--\n"
" Exclude classes which end in Blether if the system property verbosity is set to low\n"
" i.e.\n"
" java ... -Dverbosity=low \n"
-" --> \n"
-" <weld:exclude pattern="^(.*)Blether$">\n"
-" <weld:if-system-property name="verbosity" value="low"/>\n"
-" </weld:exclude>\n"
+" --> \n"
+" <weld:exclude pattern=\"^(.*)Blether$\">\n"
+" <weld:if-system-property name=\"verbosity\" value=\"low\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
-" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
+" <!--\n"
+" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
" property is not set\n"
-" -->\n"
-" <weld:exclude name="com.acme.jsf.**">\n"
-" <weld:if-class-available name="org.apahce.wicket.Wicket"/>\n"
-" <weld:if-system-property name="!viewlayer"/>\n"
-" </weld:exclude>\n"
-" </weld:scan>\n"
+" -->\n"
+" <weld:exclude name=\"com.acme.jsf.**\">\n"
+" <weld:if-class-available name=\"org.apahce.wicket.Wicket\"/>\n"
+" <weld:if-system-property name=\"!viewlayer\"/>\n"
+" </weld:exclude>\n"
+" </weld:scan>\n"
" \n"
-"</beans>"
+"</beans>"
msgstr ""
#. Tag: para
@@ -81,7 +81,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
+msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
msgstr ""
#. Tag: para
@@ -91,12 +91,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
+msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
+msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
msgstr ""
#. Tag: para
@@ -111,6 +111,6 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
+msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
msgstr ""
diff --git a/docs/reference/src/main/docbook/pot/contexts.pot b/docs/reference/src/main/docbook/pot/contexts.pot
index aaf4cc8fd49..b65b9e0d01f 100644
--- a/docs/reference/src/main/docbook/pot/contexts.pot
+++ b/docs/reference/src/main/docbook/pot/contexts.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
-"PO-Revision-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -24,17 +24,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld allows you to easiy manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivaed (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
+msgid "Weld allows you to easily manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivated (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and discociating the data store after calling activate."
+msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and dissociating the data store after calling activate."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld automatically controls context lifecycle in many scenarios such as Http Requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
+msgid "Weld automatically controls context lifecycle in many scenarios such as HTTP requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
msgstr ""
#. Tag: para
@@ -144,7 +144,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
+msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
msgstr ""
#. Tag: entry
@@ -244,12 +244,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implmentations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
+msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implementations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
+msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
msgstr ""
#. Tag: programlisting
@@ -261,14 +261,14 @@ msgid " /* Inject the BoundRequestContext. */\n"
" ...\n"
" \n"
" /* Start the request, providing a data store which will last the lifetime of the request */\n"
-" public void startRequest(Map<String, Object> requestDataStore) {\n"
+" public void startRequest(Map<String, Object> requestDataStore) {\n"
" // Associate the store with the context and acticate the context\n"
" requestContext.associate(requestDataStore);\n"
" requestContext.activate();\n"
" }\n"
" \n"
" /* End the request, providing the same data store as was used to start the request */\n"
-" public void endRequest(Map<String, Object> requestDataStore) {\n"
+" public void endRequest(Map<String, Object> requestDataStore) {\n"
" try {\n"
" /* Invalidate the request (all bean instances will be scheduled for destruction) */\n"
" requestContext.invalidate();\n"
@@ -288,7 +288,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's session contexts are "lazy" and don't require a session to actually exist until a bean instance must be written."
+msgid "Weld's session contexts are \"lazy\" and don't require a session to actually exist until a bean instance must be written."
msgstr ""
#. Tag: para
@@ -305,16 +305,16 @@ msgid " @Inject BoundConversationContext conversationContext;\n"
" /* Start a transient conversation */\n"
" /* Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */\n"
-" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" resumeOrStartConversation(requestDataStore, sessionDataStore, null);\n"
" }\n"
"\n"
" /* Start a transient conversation (if cid is null) or resume a non-transient */\n"
" /* conversation. Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */ \n"
-" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore, \n"
+" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore, \n"
" String cid) {\n"
" /* Associate the stores with the context and acticate the context */\n"
" * BoundRequest just wraps the two datastores */\n"
@@ -326,8 +326,8 @@ msgid " @Inject BoundConversationContext conversationContext;\n"
" /* End the conversations, providing the same data store as was used to start */\n"
" /* the request. Any transient conversations will be destroyed, any newly-promoted */\n"
" /* conversations will be placed into the session */\n"
-" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" try {\n"
" /* Invalidate the conversation (all transient conversations will be scheduled for destruction) */\n"
" conversationContext.invalidate();\n"
@@ -342,16 +342,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the containber), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
+msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the container), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the abilty to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
+msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the ability to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's conversations are not assigned ids until they become non-transient."
+msgid "Weld's conversations are not assigned ids until they become non-transient."
msgstr ""
diff --git a/docs/reference/src/main/docbook/pot/decorators.pot b/docs/reference/src/main/docbook/pot/decorators.pot
index 6a91015fbac..67613948bfe 100644
--- a/docs/reference/src/main/docbook/pot/decorators.pot
+++ b/docs/reference/src/main/docbook/pot/decorators.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
-"PO-Revision-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -19,12 +19,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
+msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
+msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
msgstr ""
#. Tag: para
@@ -87,7 +87,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
+msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
msgstr ""
#. Tag: para
@@ -166,14 +166,14 @@ msgid "@Decorator\n"
" \n"
" public void withdraw(BigDecimal amount) {\n"
" account.withdraw(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedWithdrawl(amount) );\n"
" }\n"
" }\n"
" \n"
" public void deposit(BigDecimal amount);\n"
" account.deposit(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedDeposit(amount) );\n"
" }\n"
" }\n"
@@ -192,21 +192,21 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+msgid "<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <decorators>\n"
-" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
-" </decorators>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <decorators>\n"
+" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
+" </decorators>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
+msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pot/ee.pot b/docs/reference/src/main/docbook/pot/ee.pot
index 6a17af5448e..fed11a8334c 100644
--- a/docs/reference/src/main/docbook/pot/ee.pot
+++ b/docs/reference/src/main/docbook/pot/ee.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
-"PO-Revision-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -54,7 +54,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
+msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
msgstr ""
#. Tag: para
@@ -78,7 +78,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
+msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
msgstr ""
#. Tag: programlisting
@@ -118,7 +118,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
+msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
msgstr ""
#. Tag: programlisting
@@ -130,14 +130,14 @@ msgid "public class Login extends HttpServlet {\n"
" @Override\n"
" public void service(HttpServletRequest request, HttpServletResponse response)\n"
" throws ServletException, IOException {\n"
-" credentials.setUsername(request.getParameter("username")):\n"
-" credentials.setPassword(request.getParameter("password")):\n"
+" credentials.setUsername(request.getParameter(\"username\")):\n"
+" credentials.setPassword(request.getParameter(\"password\")):\n"
" login.login();\n"
" if ( login.isLoggedIn() ) {\n"
-" response.sendRedirect("/home.jsp");\n"
+" response.sendRedirect(\"/home.jsp\");\n"
" }\n"
" else {\n"
-" response.sendRedirect("/loginError.jsp");\n"
+" response.sendRedirect(\"/loginError.jsp\");\n"
" }\n"
" }\n"
" \n"
@@ -156,7 +156,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
+msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
msgstr ""
#. Tag: para
@@ -205,10 +205,10 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "public class OrderResources {\n"
-" @Resource(name="jms/ConnectionFactory")\n"
+" @Resource(name=\"jms/ConnectionFactory\")\n"
" private ConnectionFactory connectionFactory;\n"
" \n"
-" @Resource(name="jms/OrderQueue")\n"
+" @Resource(name=\"jms/OrderQueue\")\n"
" private Queue orderQueue;\n"
" \n"
" @Produces @OrderConnection\n"
@@ -258,7 +258,7 @@ msgid "@Inject Order order;\n"
"\n"
"public void sendMessage() {\n"
" MapMessage msg = orderSession.createMapMessage();\n"
-" msg.setLong("orderId", order.getId());\n"
+" msg.setLong(\"orderId\", order.getId());\n"
" ...\n"
" producer.send(msg);\n"
"}"
@@ -276,7 +276,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a "bean archive". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
+msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a \"bean archive\". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pot/environments.pot b/docs/reference/src/main/docbook/pot/environments.pot
index d6afbb7f6cd..f2c53cee2a0 100644
--- a/docs/reference/src/main/docbook/pot/environments.pot
+++ b/docs/reference/src/main/docbook/pot/environments.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
-"PO-Revision-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -54,12 +54,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
+msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an "uber-jar", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
+msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an \"uber-jar\", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
msgstr ""
#. Tag: para
@@ -69,9 +69,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+msgid "<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
#. Tag: title
@@ -81,17 +81,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
+msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<Context>\n"
-" <Resource name="BeanManager" \n"
-" auth="Container"\n"
-" type="javax.enterprise.inject.spi.BeanManager"\n"
-" factory="org.jboss.weld.resources.ManagerObjectFactory"/>\n"
-"</Context>"
+msgid "<Context>\n"
+" <Resource name=\"BeanManager\" \n"
+" auth=\"Container\"\n"
+" type=\"javax.enterprise.inject.spi.BeanManager\"\n"
+" factory=\"org.jboss.weld.resources.ManagerObjectFactory\"/>\n"
+"</Context>"
msgstr ""
#. Tag: para
@@ -101,12 +101,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<resource-env-ref>\n"
-" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
-" <resource-env-ref-type>\n"
+msgid "<resource-env-ref>\n"
+" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
+" <resource-env-ref-type>\n"
" javax.enterprise.inject.spi.BeanManager\n"
-" </resource-env-ref-type>\n"
-"</resource-env-ref>"
+" </resource-env-ref-type>\n"
+"</resource-env-ref>"
msgstr ""
#. Tag: para
@@ -126,26 +126,26 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
+msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.mortbay.jetty.plus.naming.Resource">\n"
-" <Arg><Ref id="webAppCtx"/></Arg> \n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure>"
+msgid "<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.mortbay.jetty.plus.naming.Resource\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg> \n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure>"
msgstr ""
#. Tag: para
@@ -155,22 +155,22 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://www.eclipse.org/jetty/configure.dtd">\n"
+msgid "<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://www.eclipse.org/jetty/configure.dtd\">\n"
"\n"
-"<Configure id="webAppCtx" class="org.eclipse.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.eclipse.jetty.plus.jndi.Resource">\n"
-" <Arg> <Ref id="webAppCtx"/> </Arg>\n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure> "
+"<Configure id=\"webAppCtx\" class=\"org.eclipse.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.eclipse.jetty.plus.jndi.Resource\">\n"
+" <Arg> <Ref id=\"webAppCtx\"/> </Arg>\n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure> "
msgstr ""
#. Tag: para
@@ -180,7 +180,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
+msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
msgstr ""
#. Tag: para
@@ -190,18 +190,18 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file META-INF/jetty-web.xml with the following content to your war:"
+msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file WEB-INF/jetty-web.xml with the following content to your war:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <Call class="org.jboss.weld.environment.jetty.WeldServletHandler" name="process">\n"
-" <Arg><Ref id="webAppCtx"/></Arg>\n"
-" </Call>\n"
-"</Configure>"
+msgid "<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <Call class=\"org.jboss.weld.environment.jetty.WeldServletHandler\" name=\"process\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg>\n"
+" </Call>\n"
+"</Configure>"
msgstr ""
#. Tag: title
@@ -211,7 +211,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In addition to improved integration of the Enterprise Java stack, the "Contexts and Dependency Injection for the Java EE platform" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
+msgid "In addition to improved integration of the Enterprise Java stack, the \"Contexts and Dependency Injection for the Java EE platform\" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
msgstr ""
#. Tag: para
@@ -271,7 +271,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Parameters List<String> params;"
+msgid "@Inject @Parameters List<String> params;"
msgstr ""
#. Tag: programlisting
@@ -291,7 +291,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example of a simple CDI SE application:"
+msgid "Here's an example of a simple CDI SE application:"
msgstr ""
#. Tag: programlisting
@@ -299,8 +299,8 @@ msgstr ""
msgid "@Singleton\n"
"public class HelloWorld\n"
"{\n"
-" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
-" System.out.println("Hello " + parameters.get(0));\n"
+" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
+" System.out.println(\"Hello \" + parameters.get(0));\n"
" }\n"
"}"
msgstr ""
@@ -322,7 +322,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
+msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
msgstr ""
#. Tag: para
@@ -332,17 +332,17 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "java org.jboss.weld.environment.se.StartMain <args>"
+msgid "java org.jboss.weld.environment.se.StartMain <args>"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Programatic Bootstrap API"
+msgid "Programmatic Bootstrap API"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
+msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
msgstr ""
#. Tag: programlisting
@@ -366,10 +366,10 @@ msgid "public class WeldContainer\n"
"{\n"
"\n"
" /** Provides access to all beans within the application. */\n"
-" public Instance<Object> instance() {...}\n"
+" public Instance<Object> instance() {...}\n"
"\n"
" /** Provides access to all events within the application. */\n"
-" public Event<Object> event() {...}\n"
+" public Event<Object> event() {...}\n"
"\n"
" /** Provides direct access to the BeanManager. */\n"
" public BeanManager getBeanManager() {...}\n"
@@ -379,7 +379,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
+msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
msgstr ""
#. Tag: programlisting
@@ -417,21 +417,21 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
+msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<beans>\n"
-" <decorators>\n"
-" <decorator>org.jboss.weld.environment.se.threading.RunnableDecorator</decorator>\n"
-" </decorator>\n"
-"</beans>"
+msgid "<beans>\n"
+" <decorators>\n"
+" <class>org.jboss.weld.environment.se.threading.RunnableDecorator</class>\n"
+" </decorator>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situtations where you would otherwise have used ThreadLocal directly, which are typically rare."
+msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situations where you would otherwise have used ThreadLocal directly, which are typically rare."
msgstr ""
#. Tag: title
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
+msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pot/events.pot b/docs/reference/src/main/docbook/pot/events.pot
index 60d2958fd37..690a4adb43c 100644
--- a/docs/reference/src/main/docbook/pot/events.pot
+++ b/docs/reference/src/main/docbook/pot/events.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
-"PO-Revision-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -34,7 +34,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "observers can specify a combination of "selectors" to narrow the set of event notifications they will receive, and"
+msgid "observers can specify a combination of \"selectors\" to narrow the set of event notifications they will receive, and"
msgstr ""
#. Tag: para
@@ -44,7 +44,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
+msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
msgstr ""
#. Tag: title
@@ -59,7 +59,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
+msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
msgstr ""
#. Tag: programlisting
@@ -97,7 +97,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "An observer method need not specify any event qualifiers—in this case it is interested in only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
+msgid "An observer method need not specify any event qualifiers—in this case it is interested in only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
msgstr ""
#. Tag: para
@@ -122,7 +122,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Any Event<Document> documentEvent;"
+msgid "@Inject @Any Event<Document> documentEvent;"
msgstr ""
#. Tag: para
@@ -177,7 +177,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
+msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
msgstr ""
#. Tag: para
@@ -197,12 +197,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
+msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
+msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
msgstr ""
#. Tag: para
@@ -217,7 +217,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
+msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
msgstr ""
#. Tag: para
@@ -272,7 +272,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
+msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
msgstr ""
#. Tag: para
@@ -283,7 +283,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "abstract class RoleBinding \n"
-" extends AnnotationLiteral<Role> \n"
+" extends AnnotationLiteral<Role> \n"
" implements Role {}"
msgstr ""
@@ -311,9 +311,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Blog Event<Document> blogEvent;\n"
+msgid "@Inject @Blog Event<Document> blogEvent;\n"
"...\n"
-"if (document.isBlog()) blogEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
+"if (document.isBlog()) blogEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
msgstr ""
#. Tag: para
@@ -418,12 +418,12 @@ msgid "@ApplicationScoped @Singleton\n"
"\n"
" @PersistenceContext EntityManager em;\n"
" \n"
-" List<Product> products;\n"
+" List<Product> products;\n"
"\n"
" @Produces @Catalog \n"
-" List<Product> getCatalog() {\n"
+" List<Product> getCatalog() {\n"
" if (products==null) {\n"
-" products = em.createQuery("select p from Product p where p.deleted = false")\n"
+" products = em.createQuery(\"select p from Product p where p.deleted = false\")\n"
" .getResultList();\n"
" }\n"
" return products;\n"
@@ -447,16 +447,16 @@ msgstr ""
msgid "@Stateless\n"
"public class ProductManager {\n"
" @PersistenceContext EntityManager em;\n"
-" @Inject @Any Event<Product> productEvent;\n"
+" @Inject @Any Event<Product> productEvent;\n"
"\n"
" public void delete(Product product) {\n"
" em.delete(product);\n"
-" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
" }\n"
" \n"
" public void persist(Product product) {\n"
" em.persist(product);\n"
-" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
" }\n"
" ...\n"
"}"
diff --git a/docs/reference/src/main/docbook/pot/example.pot b/docs/reference/src/main/docbook/pot/example.pot
index 6eeb7e7db6f..d29aa66bac7 100644
--- a/docs/reference/src/main/docbook/pot/example.pot
+++ b/docs/reference/src/main/docbook/pot/example.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
-"PO-Revision-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -19,7 +19,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
+msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
msgstr ""
#. Tag: programlisting
@@ -46,18 +46,18 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<h:form>\n"
-" <h:panelGrid columns="2" rendered="#{!login.loggedIn}">\n"
-" <f:validateBean>\n"
-" <h:outputLabel for="username">Username:</h:outputLabel>\n"
-" <h:inputText id="username" value="#{credentials.username}"/>\n"
-" <h:outputLabel for="password">Password:</h:outputLabel>\n"
-" <h:inputSecret id="password" value="#{credentials.password}"/>\n"
-" </f:validateBean>\n"
-" </h:panelGrid>\n"
-" <h:commandButton value="Login" action="#{login.login}" rendered="#{!login.loggedIn}"/>\n"
-" <h:commandButton value="Logout" action="#{login.logout}" rendered="#{login.loggedIn}"/>\n"
-"</h:form>"
+msgid "<h:form>\n"
+" <h:panelGrid columns=\"2\" rendered=\"#{!login.loggedIn}\">\n"
+" <f:validateBean>\n"
+" <h:outputLabel for=\"username\">Username:</h:outputLabel>\n"
+" <h:inputText id=\"username\" value=\"#{credentials.username}\"/>\n"
+" <h:outputLabel for=\"password\">Password:</h:outputLabel>\n"
+" <h:inputSecret id=\"password\" value=\"#{credentials.password}\"/>\n"
+" </f:validateBean>\n"
+" </h:panelGrid>\n"
+" <h:commandButton value=\"Login\" action=\"#{login.login}\" rendered=\"#{!login.loggedIn}\"/>\n"
+" <h:commandButton value=\"Logout\" action=\"#{login.logout}\" rendered=\"#{login.loggedIn}\"/>\n"
+"</h:form>"
msgstr ""
#. Tag: para
@@ -80,7 +80,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
+msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
msgstr ""
#. Tag: para
@@ -99,10 +99,10 @@ msgid "@SessionScoped @Named\n"
" private User user;\n"
" \n"
" public void login() {\n"
-" List<User> results = userDatabase.createQuery(\n"
-" "select u from User u where u.username = :username and u.password = :password")\n"
-" .setParameter("username", credentials.getUsername())\n"
-" .setParameter("password", credentials.getPassword())\n"
+" List<User> results = userDatabase.createQuery(\n"
+" \"select u from User u where u.username = :username and u.password = :password\")\n"
+" .setParameter(\"username\", credentials.getUsername())\n"
+" .setParameter(\"password\", credentials.getPassword())\n"
" .getResultList();\n"
" \n"
" if (!results.isEmpty()) {\n"
@@ -188,13 +188,13 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<h:panelGroup rendered="#{login.loggedIn}">\n"
+msgid "<h:panelGroup rendered=\"#{login.loggedIn}\">\n"
" signed in as #{currentUser.username}\n"
-"</h:panelGroup>"
+"</h:panelGroup>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
+msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
msgstr ""
diff --git a/docs/reference/src/main/docbook/pot/extend.pot b/docs/reference/src/main/docbook/pot/extend.pot
index 38a0aa88507..b19afe2dbed 100644
--- a/docs/reference/src/main/docbook/pot/extend.pot
+++ b/docs/reference/src/main/docbook/pot/extend.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
-"PO-Revision-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -74,7 +74,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
+msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
msgstr ""
#. Tag: programlisting
@@ -160,15 +160,15 @@ msgstr ""
msgid "class MyExtension implements Extension {\n"
" \n"
" void beforeBeanDiscovery(@Observes BeforeBeanDiscovery bbd) {\n"
-" Logger.global.debug("beginning the scanning process");\n"
+" Logger.global.debug(\"beginning the scanning process\");\n"
" }\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
-" Logger.global.debug("scanning type: " + pat.getAnnotatedType().getJavaClass().getName());\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" Logger.global.debug(\"scanning type: \" + pat.getAnnotatedType().getJavaClass().getName());\n"
" } \n"
"\n"
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd) {\n"
-" Logger.global.debug("finished the scanning process");\n"
+" Logger.global.debug(\"finished the scanning process\");\n"
" }\n"
" \n"
"}"
@@ -176,14 +176,14 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
+msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "class MyExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" //tell the container to ignore the type if it is annotated @Ignore\n"
" if ( pat.getAnnotatedType().isAnnotionPresent(Ignore.class) ) pat.veto(); \n"
" } \n"
@@ -198,7 +198,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
+msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
msgstr ""
#. Tag: title
@@ -214,31 +214,31 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "public interface BeanManager {\n"
-" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
-" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
-" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
-" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
-" public Set<Bean<?>> getBeans(String name);\n"
-" public Bean<?> getPassivationCapableBean(String id);\n"
-" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
+" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
+" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
+" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
+" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
+" public Set<Bean<?>> getBeans(String name);\n"
+" public Bean<?> getPassivationCapableBean(String id);\n"
+" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
" public void validate(InjectionPoint injectionPoint);\n"
" public void fireEvent(Object event, Annotation... qualifiers);\n"
-" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
-" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
-" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
-" public boolean isScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
-" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
-" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
-" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
-" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
-" public Context getContext(Class<? extends Annotation> scopeType);\n"
+" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
+" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
+" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
+" public boolean isScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
+" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
+" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
+" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
+" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
+" public Context getContext(Class<? extends Annotation> scopeType);\n"
" public ELResolver getELResolver();\n"
" public ExpressionFactory wrapExpressionFactory(ExpressionFactory expressionFactory);\n"
-" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
-" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
+" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
+" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
"}"
msgstr ""
@@ -259,7 +259,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's study some of the interfaces exposed by the BeanManager."
+msgid "Let's study some of the interfaces exposed by the BeanManager."
msgstr ""
#. Tag: title
@@ -274,20 +274,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to instatiate the object itself, and so only method and field injection will be supported."
+msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to insntatiate the object itself, and so only method and field injection will be supported."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "//get the BeanManager from JNDI\n"
-"BeanManager beanManager = (BeanManager) new InitialContext().lookup("java:comp/BeanManager");\n"
+"BeanManager beanManager = (BeanManager) new InitialContext().lookup(\"java:comp/BeanManager\");\n"
"\n"
"//CDI uses an AnnotatedType object to read the annotations of a class\n"
-"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
+"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
"\n"
"//The extension uses an InjectionTarget to delegate instantiation, dependency injection \n"
"//and lifecycle callbacks to the CDI container\n"
-"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
+"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
"\n"
"//each instance needs its own CDI CreationalContext\n"
"CreationalContext ctx = beanManager.createCreationalContext(null);\n"
@@ -318,32 +318,32 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Bean interface exposes all the interesting things we dicussed in ."
+msgid "The Bean interface exposes all the interesting things we discussed in ."
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "public interface Bean<T> extends Contextual<T> {\n"
-" public Set<Type> getTypes();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Class<? extends Annotation> getScope();\n"
+msgid "public interface Bean<T> extends Contextual<T> {\n"
+" public Set<Type> getTypes();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Class<? extends Annotation> getScope();\n"
" public String getName();\n"
-" public Set<Class<? extends Annotation>> getStereotypes();\n"
-" public Class<?> getBeanClass();\n"
+" public Set<Class<? extends Annotation>> getStereotypes();\n"
+" public Class<?> getBeanClass();\n"
" public boolean isAlternative();\n"
" public boolean isNullable();\n"
-" public Set<InjectionPoint> getInjectionPoints();\n"
+" public Set<InjectionPoint> getInjectionPoints();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's an easy way to find out what beans exist in the application:"
+msgid "There's an easy way to find out what beans exist in the application:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
+msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
msgstr ""
#. Tag: para
@@ -363,7 +363,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
+msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
msgstr ""
#. Tag: programlisting
@@ -373,49 +373,49 @@ msgid "public class SecurityManagerExtension implements Extension {\n"
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd, BeanManager bm) {\n"
" \n"
" //use this to read annotations of the class\n"
-" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
+" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
"\n"
" //use this to instantiate the class and inject dependencies\n"
-" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
+" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
"\n"
-" abd.addBean( new Bean<SecurityManager>() {\n"
+" abd.addBean( new Bean<SecurityManager>() {\n"
"\n"
" @Override\n"
-" public Class<?> getBeanClass() {\n"
+" public Class<?> getBeanClass() {\n"
" return SecurityManager.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
" public String getName() {\n"
-" return "securityManager";\n"
+" return \"securityManager\";\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getQualifiers() {\n"
-" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
-" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
-" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
+" public Set<Annotation> getQualifiers() {\n"
+" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
+" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
+" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
" return qualifiers;\n"
" }\n"
"\n"
" @Override\n"
-" public Class<? extends Annotation> getScope() {\n"
+" public Class<? extends Annotation> getScope() {\n"
" return SessionScoped.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Class<? extends Annotation>> getStereotypes() {\n"
+" public Set<Class<? extends Annotation>> getStereotypes() {\n"
" return Collections.emptySet();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypes() {\n"
-" Set<Type> types = new HashSet<Type>();\n"
+" public Set<Type> getTypes() {\n"
+" Set<Type> types = new HashSet<Type>();\n"
" types.add(SecurityManager.class);\n"
" types.add(Object.class);\n"
" return types;\n"
@@ -432,7 +432,7 @@ msgid "public class SecurityManagerExtension implements Extension {\n"
" }\n"
"\n"
" @Override\n"
-" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
+" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
" SecurityManager instance = it.produce(ctx);\n"
" it.inject(instance, ctx);\n"
" it.postConstruct(instance);\n"
@@ -441,7 +441,7 @@ msgid "public class SecurityManagerExtension implements Extension {\n"
"\n"
" @Override\n"
" public void destroy(SecurityManager instance, \n"
-" CreationalContext<SecurityManager> ctx) {\n"
+" CreationalContext<SecurityManager> ctx) {\n"
" it.preDestroy(instance);\n"
" it.dispose(instance);\n"
" ctx.release();\n"
@@ -470,45 +470,45 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
+msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "public class QualifiedNameExtension implements Extension {\n"
"\n"
-" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
+" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
"\n"
" //wrap this to override the annotations of the class\n"
-" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
+" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
" \n"
-" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
+" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
"\n"
" @Override\n"
-" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
+" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
" return at.getConstructors();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedField<? super X>> getFields() {\n"
+" public Set<AnnotatedField<? super X>> getFields() {\n"
" return at.getFields();\n"
" }\n"
"\n"
" @Override\n"
-" public Class<X> getJavaClass() {\n"
+" public Class<X> getJavaClass() {\n"
" return at.getJavaClass();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
+" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
" return at.getMethods();\n"
" }\n"
"\n"
" @Override\n"
-" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
+" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
" if ( Named.class.equals(annType) ) {\n"
" class NamedLiteral \n"
-" extends AnnotationLiteral<Named> \n"
+" extends AnnotationLiteral<Named> \n"
" implements Named {\n"
" @Override\n"
" public String value() {\n"
@@ -517,7 +517,7 @@ msgid "public class QualifiedNameExtension implements Extension {\n"
" final String qualifiedName;\n"
" if ( pkg.isAnnotationPresent(Named.class) ) {\n"
" qualifiedName = pkg.getAnnotation(Named.class).value() \n"
-" + '.' + unqualifiedName;\n"
+" + '.' + unqualifiedName;\n"
" }\n"
" else {\n"
" qualifiedName = unqualifiedName;\n"
@@ -533,7 +533,7 @@ msgid "public class QualifiedNameExtension implements Extension {\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getAnnotations() {\n"
+" public Set<Annotation> getAnnotations() {\n"
" return at.getAnnotations();\n"
" }\n"
"\n"
@@ -543,12 +543,12 @@ msgid "public class QualifiedNameExtension implements Extension {\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypeClosure() {\n"
+" public Set<Type> getTypeClosure() {\n"
" return at.getTypeClosure();\n"
" }\n"
"\n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
" return at.isAnnotationPresent(annType);\n"
" }\n"
" \n"
@@ -562,24 +562,24 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
+msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "class ServiceAlternativeExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" \n"
-" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
+" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
" \n"
" if ( Service.class.isAssignableFrom( type.getJavaClass() ) ) {\n"
" \n"
" //if the class implements Service, make it an @Alternative\n"
-" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
+" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
" \n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
" return annotationType.equals(Alternative.class) ? \n"
" true : type.isAnnotationPresent(annotationType);\n"
" }\n"
@@ -612,7 +612,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
+msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
msgstr ""
#. Tag: programlisting
@@ -630,25 +630,25 @@ msgstr ""
#, no-c-format
msgid "public class ConfigExtension implements Extension {\n"
"\n"
-" <X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
+" <X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
" \n"
" //wrap this to intercept the component lifecycle\n"
-" final InjectionTarget<X> it = pit.getInjectionTarget();\n"
+" final InjectionTarget<X> it = pit.getInjectionTarget();\n"
" \n"
-" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
+" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
" \n"
" //use this to read annotations of the class and its members\n"
-" AnnotatedType<X> at = pit.getAnnotatedType();\n"
+" AnnotatedType<X> at = pit.getAnnotatedType();\n"
" \n"
" //read the properties file\n"
-" String propsFileName = at.getClass().getSimpleName() + ".properties";\n"
+" String propsFileName = at.getClass().getSimpleName() + \".properties\";\n"
" InputStream stream = at.getJavaClass().getResourceAsStream(propsFileName);\n"
" if (stream!=null) {\n"
" \n"
" try {\n"
" Properties props = new Properties();\n"
" props.load(stream);\n"
-" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
+" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
" String fieldName = property.getKey().toString();\n"
" Object value = property.getValue();\n"
" try {\n"
@@ -660,7 +660,7 @@ msgid "public class ConfigExtension implements Extension {\n"
" else {\n"
" //TODO: do type conversion automatically\n"
" pit.addDefinitionError( new InjectionException(\n"
-" "field is not of type String: " + field ) );\n"
+" \"field is not of type String: \" + field ) );\n"
" }\n"
" }\n"
" catch (NoSuchFieldException nsfe) {\n"
@@ -676,14 +676,14 @@ msgid "public class ConfigExtension implements Extension {\n"
" }\n"
" }\n"
" \n"
-" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
+" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
"\n"
" @Override\n"
-" public void inject(X instance, CreationalContext<X> ctx) {\n"
+" public void inject(X instance, CreationalContext<X> ctx) {\n"
" it.inject(instance, ctx);\n"
" \n"
" //set the values onto the new instance of the component\n"
-" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
+" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
" try {\n"
" configuredValue.getKey().set(instance, configuredValue.getValue());\n"
" }\n"
@@ -709,12 +709,12 @@ msgid "public class ConfigExtension implements Extension {\n"
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
-" public X produce(CreationalContext<X> ctx) {\n"
+" public X produce(CreationalContext<X> ctx) {\n"
" return it.produce(ctx);\n"
" }\n"
" \n"
@@ -729,7 +729,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
+msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
msgstr ""
#. Tag: title
@@ -745,9 +745,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "public interface Context {\n"
-" public Class<? extends Annotation> getScope();\n"
-" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
-" public <T> T get(Contextual<T> contextual);\n"
+" public Class<? extends Annotation> getScope();\n"
+" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
+" public <T> T get(Contextual<T> contextual);\n"
" boolean isActive();\n"
"}"
msgstr ""
diff --git a/docs/reference/src/main/docbook/pot/gettingstarted.pot b/docs/reference/src/main/docbook/pot/gettingstarted.pot
index b1830825b72..91896fb7b4a 100644
--- a/docs/reference/src/main/docbook/pot/gettingstarted.pot
+++ b/docs/reference/src/main/docbook/pot/gettingstarted.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
-"PO-Revision-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -19,7 +19,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, Glassfish 3.0 or any compliant Java EE 6 container."
+msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, GlassFish 3.0 or any compliant Java EE 6 container."
msgstr ""
#. Tag: para
@@ -34,7 +34,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To run the examples with the provided build scripts, you'll need the following:"
+msgid "To run the examples with the provided build scripts, you'll need the following:"
msgstr ""
#. Tag: para
@@ -79,12 +79,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
+msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
+msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
msgstr ""
#. Tag: para
@@ -94,7 +94,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
+msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
msgstr ""
#. Tag: title
@@ -104,18 +104,18 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
+msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
+msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> unzip jboss-6.0.*.zip\n"
-"$> mv jboss-6.0.*/ jboss-as-6.0"
+msgid "$> unzip jboss-6.0.*.zip\n"
+"$> mv jboss-6.0.*/ jboss-as-6.0"
msgstr ""
#. Tag: para
@@ -130,7 +130,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You're now ready to deploy your first example!"
+msgid "You're now ready to deploy your first example!"
msgstr ""
#. Tag: para
@@ -140,19 +140,19 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> cd examples/jsf/numberguess\n"
-"$> ant deploy"
+msgid "$> cd examples/jsf/numberguess\n"
+"$> ant deploy"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
+msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> cd /path/to/jboss-as-6.0\n"
-"$> ./bin/run.sh"
+msgid "$> cd /path/to/jboss-as-6.0\n"
+"$> ./bin/run.sh"
msgstr ""
#. Tag: para
@@ -162,8 +162,8 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
-"$> run"
+msgid "$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
+"$> run"
msgstr ""
#. Tag: para
@@ -218,18 +218,18 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> cd examples/jsf/translator\n"
-"$> ant deploy"
+msgid "$> cd examples/jsf/translator\n"
+"$> ant deploy"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
+msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
+msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
msgstr ""
#. Tag: title
@@ -239,39 +239,39 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
+msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
+msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> chmod 755 glassfish-v3-unix.sh\n"
-"$> ./glassfish-v3-unix.sh"
+msgid "$> chmod 755 glassfish-v3-unix.sh\n"
+"$> ./glassfish-v3-unix.sh"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
+msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
+msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
-"$> ant package"
+msgid "$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
+"$> ant package"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
+msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
msgstr ""
#. Tag: para
@@ -281,12 +281,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin start-domain domain1"
+msgid "$> asadmin start-domain domain1"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on "Applications", then click on the "Deploy..." button under the heading "Applications" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
+msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on \"Applications\", then click on the \"Deploy...\" button under the heading \"Applications\" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
msgstr ""
#. Tag: para
@@ -296,7 +296,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin deploy target/weld-numberguess.war"
+msgid "$> asadmin deploy target/weld-numberguess.war"
msgstr ""
#. Tag: para
@@ -316,22 +316,22 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
+msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
+msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> unzip apache-tomcat-6.0.18.zip"
+msgid "$> unzip apache-tomcat-6.0.18.zip"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
+msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
msgstr ""
#. Tag: title
@@ -341,7 +341,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
+msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
msgstr ""
#. Tag: programlisting
@@ -351,7 +351,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now you're ready to deploy the numberguess example to Tomcat!"
+msgid "Now you're ready to deploy the numberguess example to Tomcat!"
msgstr ""
#. Tag: para
@@ -361,13 +361,13 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> cd examples/jsf/numberguess\n"
-"$> ant tomcat.deploy"
+msgid "$> cd examples/jsf/numberguess\n"
+"$> ant tomcat.deploy"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with "tomcat."."
+msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with \"tomcat.\"."
msgstr ""
#. Tag: para
@@ -392,19 +392,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
+msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> cd /path/to/apache-tomcat-6\n"
-"$> ./bin/start.sh"
+msgid "$> cd /path/to/apache-tomcat-6\n"
+"$> ./bin/start.sh"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
-"$> start"
+msgid "$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
+"$> start"
msgstr ""
#. Tag: para
@@ -419,12 +419,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
+msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
+msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
msgstr ""
#. Tag: para
@@ -434,7 +434,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<user username="admin" password="" roles="manager"/>"
+msgid "<user username=\"admin\" password=\"\" roles=\"manager\"/>"
msgstr ""
#. Tag: para
@@ -444,7 +444,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
+msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
msgstr ""
#. Tag: para
@@ -454,7 +454,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn tomcat:redeploy -Ptomcat"
+msgid "$> mvn tomcat:redeploy -Ptomcat"
msgstr ""
#. Tag: para
@@ -469,7 +469,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace tomcat:run -Ptomcat"
+msgid "$> mvn war:inplace tomcat:run -Ptomcat"
msgstr ""
#. Tag: para
@@ -479,12 +479,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Ptomcat"
+msgid "$> mvn compile war:inplace -Ptomcat"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
+msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
msgstr ""
#. Tag: title
@@ -499,12 +499,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
+msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
+msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
msgstr ""
#. Tag: para
@@ -514,8 +514,8 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> cd examples/jsf/numberguess\n"
-"$> mvn war:inplace jetty:run -Pjetty"
+msgid "$> cd examples/jsf/numberguess\n"
+"$> mvn war:inplace jetty:run -Pjetty"
msgstr ""
#. Tag: para
@@ -530,7 +530,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Pjetty"
+msgid "$> mvn compile war:inplace -Pjetty"
msgstr ""
#. Tag: para
@@ -540,7 +540,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclispe[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
+msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclipse[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
msgstr ""
#. Tag: para
@@ -550,7 +550,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
+msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
msgstr ""
#. Tag: para
@@ -560,12 +560,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace -Pjetty-ide"
+msgid "$> mvn war:inplace -Pjetty-ide"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using "Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
+msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using \"Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pot/injection.pot b/docs/reference/src/main/docbook/pot/injection.pot
index bdad763fd03..7b2af4d633b 100644
--- a/docs/reference/src/main/docbook/pot/injection.pot
+++ b/docs/reference/src/main/docbook/pot/injection.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
-"PO-Revision-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -19,7 +19,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
+msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
msgstr ""
#. Tag: title
@@ -116,7 +116,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
+msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
msgstr ""
#. Tag: para
@@ -148,7 +148,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
+msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
msgstr ""
#. Tag: title
@@ -158,7 +158,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
+msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
msgstr ""
#. Tag: para
@@ -183,12 +183,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
+msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
+msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
msgstr ""
#. Tag: title
@@ -305,7 +305,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you may be thinking, "What's the different between using a qualifier and just specifying the exact implementation class you want?" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alterative implementations of @Asynchronous PaymentProcessor!"
+msgid "Now, you may be thinking, \"What's the different between using a qualifier and just specifying the exact implementation class you want?\" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alternative implementations of @Asynchronous PaymentProcessor!"
msgstr ""
#. Tag: title
@@ -315,7 +315,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to decare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
+msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to declare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
msgstr ""
#. Tag: para
@@ -326,7 +326,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "@Inject \n"
-"void initServices(@Any Instance<Service> services) { \n"
+"void initServices(@Any Instance<Service> services) { \n"
" for (Service service: services) {\n"
" service.init();\n"
" }\n"
@@ -355,7 +355,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then we select one of the possible member values when appling the qualifier:"
+msgid "Then we select one of the possible member values when applying the qualifier:"
msgstr ""
#. Tag: programlisting
@@ -375,7 +375,7 @@ msgid "@Qualifier\n"
"@Target({METHOD, FIELD, PARAMETER, TYPE})\n"
"public @interface PayBy {\n"
" PaymentMethod value();\n"
-" @Nonbinding String comment() default "";\n"
+" @Nonbinding String comment() default \"\";\n"
"}"
msgstr ""
@@ -432,21 +432,21 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+msgid "<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <alternatives>\n"
-" <class>org.mycompany.mock.MockPaymentProcessor</class>\n"
-" </alternatives>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <alternatives>\n"
+" <class>org.mycompany.mock.MockPaymentProcessor</class>\n"
+" </alternatives>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "When an ambiguous dependency exists at an injection point, the container attempts to resolve the ambiguity by looking for an enabled alternative among the beans that could be injected. If there is exactly one enabled alternative, that's the bean that will be injected."
+msgid "When an ambiguous dependency exists at an injection point, the container attempts to resolve the ambiguity by looking for an enabled alternative among the beans that could be injected. If there is exactly one enabled alternative, that's the bean that will be injected."
msgstr ""
#. Tag: title
@@ -461,7 +461,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "During the course of your development, you're going to encounter this situation. Let's learn how to resolve it."
+msgid "During the course of your development, you're going to encounter this situation. Let's learn how to resolve it."
msgstr ""
#. Tag: para
@@ -511,22 +511,22 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "See this FAQ for step-by-step instructions for how to resolve an ambigous resolution exception between a raw bean type and a producer method that returns the same bean type."
+msgid "See this FAQ for step-by-step instructions for how to resolve an ambiguous resolution exception between a raw bean type and a producer method that returns the same bean type."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Just remember: "There can be only one.""
+msgid "Just remember: \"There can be only one.\""
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
+msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
+msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
msgstr ""
#. Tag: title
@@ -541,7 +541,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
+msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
msgstr ""
#. Tag: para
@@ -566,7 +566,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "classes which don't have a non-private constructor with no parameters, and"
+msgid "classes which don't have a non-private constructor with no parameters, and"
msgstr ""
#. Tag: para
@@ -581,7 +581,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
+msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
msgstr ""
#. Tag: para
@@ -591,7 +591,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "change the type of the injection point to Instance<X>,"
+msgid "change the type of the injection point to Instance<X>,"
msgstr ""
#. Tag: para
@@ -621,7 +621,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But we didn't get around to implementing this yet."
+msgid "But we didn't get around to implementing this yet."
msgstr ""
#. Tag: title
@@ -656,7 +656,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -691,7 +691,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -706,18 +706,18 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, we need to obtain an instance of our qualifier type. Since annotatons are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
+msgid "Next, we need to obtain an instance of our qualifier type. Since annotations are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "abstract class AsynchronousQualifier\n"
-"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
+msgid "class AsynchronousQualifier\n"
+"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
msgstr ""
#. Tag: para
@@ -728,12 +728,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "PaymentProcessor p = paymentProcessorSource\n"
-" .select(new AnnotationLiteral<Asynchronous>() {});"
+" .select(new AnnotationLiteral<Asynchronous>() {});"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We can't use an anonymous class to implement a qualifier type with members."
+msgid "However, we can't use an anonymous class to implement a qualifier type with members."
msgstr ""
#. Tag: para
@@ -780,7 +780,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
+msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
msgstr ""
#. Tag: programlisting
@@ -816,7 +816,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
+msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
msgstr ""
#. Tag: programlisting
@@ -836,8 +836,8 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@HttpParam("username") String username;\n"
-"@HttpParam("password") String password;"
+msgid "@HttpParam(\"username\") String username;\n"
+"@HttpParam(\"password\") String password;"
msgstr ""
#. Tag: para
@@ -849,7 +849,7 @@ msgstr ""
#, no-c-format
msgid "class HttpParams\n"
"\n"
-" @Produces @HttpParam("")\n"
+" @Produces @HttpParam(\"\")\n"
" String getParamValue(InjectionPoint ip) {\n"
" ServletRequest request = (ServletRequest) FacesContext.getCurrentInstance().getExternalContext().getRequest();\n"
" return request.getParameter(ip.getAnnotated().getAnnotation(HttpParam.class).value());\n"
@@ -860,7 +860,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own prodcuer for the request and have it injected as a method parameter."
+msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own producer for the request and have it injected as a method parameter."
msgstr ""
#. Tag: para
@@ -877,8 +877,8 @@ msgstr ""
#, no-c-format
msgid "public interface InjectionPoint { \n"
" public Type getType();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Bean<?> getBean();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Bean<?> getBean();\n"
" public Member getMember();\n"
" public Annotated getAnnotated();\n"
" public boolean isDelegate();\n"
diff --git a/docs/reference/src/main/docbook/pot/interceptors.pot b/docs/reference/src/main/docbook/pot/interceptors.pot
index d27964c98fc..04f895dd08f 100644
--- a/docs/reference/src/main/docbook/pot/interceptors.pot
+++ b/docs/reference/src/main/docbook/pot/interceptors.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
-"PO-Revision-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -93,7 +93,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
+msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
msgstr ""
#. Tag: programlisting
@@ -134,7 +134,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
+msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
msgstr ""
#. Tag: programlisting
@@ -181,16 +181,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+msgid "<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -220,17 +220,17 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+msgid "<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -310,7 +310,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Secure(rolesAllowed="admin") @Transactional\n"
+msgid "@Secure(rolesAllowed=\"admin\") @Transactional\n"
"public class ShoppingCart { ... }"
msgstr ""
@@ -378,7 +378,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Well, fortunately, CDI works around this missing feature of Java. We may annotate one interceptor binding type with other interceptor binding types (termed a meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
+msgid "Well, fortunately, CDI works around this missing feature of Java. We may annotate one interceptor binding type with other interceptor binding types (termed a meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
msgstr ""
#. Tag: programlisting
@@ -430,7 +430,7 @@ msgstr ""
#. Tag: para
#, 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."
+msgid "the interceptor ordering is non-global — it is determined by the order in which interceptors are listed at the class level."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pot/intro.pot b/docs/reference/src/main/docbook/pot/intro.pot
index 7497b06453c..2d8990acdbf 100644
--- a/docs/reference/src/main/docbook/pot/intro.pot
+++ b/docs/reference/src/main/docbook/pot/intro.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
-"PO-Revision-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -19,7 +19,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
+msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
msgstr ""
#. Tag: title
@@ -34,27 +34,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Prior to Java EE 6, there was no clear definition of the term "bean" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications "beans" for years. There were even a couple of different kinds of things called "beans" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a "bean". What we've been missing is a common definition."
+msgid "Prior to Java EE 6, there was no clear definition of the term \"bean\" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications \"beans\" for years. There were even a couple of different kinds of things called \"beans\" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a \"bean\". What we've been missing is a common definition."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
+msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
+msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
+msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now let's see how to create your first bean that actually uses CDI."
+msgid "Now let's see how to create your first bean that actually uses CDI."
msgstr ""
#. Tag: title
@@ -64,13 +64,13 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
+msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "public class SentenceParser {\n"
-" public List<String> parse(String text) { ... }\n"
+" public List<String> parse(String text) { ... }\n"
"}"
msgstr ""
@@ -102,7 +102,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unfortunately, we don't have a class that translates whole text documents. So let's write a bean for this job:"
+msgid "Unfortunately, we don't have a class that translates whole text documents. So let's write a bean for this job:"
msgstr ""
#. Tag: programlisting
@@ -134,7 +134,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
+msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
msgstr ""
#. Tag: para
@@ -144,7 +144,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
+msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
msgstr ""
#. Tag: programlisting
@@ -182,7 +182,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
+msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
msgstr ""
#. Tag: para
@@ -192,7 +192,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject Instance<TextTranslator> textTranslatorInstance;\n"
+msgid "@Inject Instance<TextTranslator> textTranslatorInstance;\n"
"...\n"
"public void translate() {\n"
" textTranslatorInstance.get().translate(inputText);\n"
@@ -201,16 +201,16 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
+msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
+msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
+msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
msgstr ""
diff --git a/docs/reference/src/main/docbook/pot/next.pot b/docs/reference/src/main/docbook/pot/next.pot
index 2ee7aab56fc..df50fc5a739 100644
--- a/docs/reference/src/main/docbook/pot/next.pot
+++ b/docs/reference/src/main/docbook/pot/next.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
-"PO-Revision-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -19,12 +19,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
+msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
+msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pot/part1.pot b/docs/reference/src/main/docbook/pot/part1.pot
index ab71de16f27..4e14e398ab8 100644
--- a/docs/reference/src/main/docbook/pot/part1.pot
+++ b/docs/reference/src/main/docbook/pot/part1.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
-"PO-Revision-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -124,7 +124,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Where should I keep the reference to it when I'm not currently using it?"
+msgid "Where should I keep the reference to it when I'm not currently using it?"
msgstr ""
#. Tag: para
@@ -139,7 +139,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
+msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
msgstr ""
#. Tag: para
@@ -169,12 +169,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
+msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
+msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
msgstr ""
#. Tag: para
@@ -184,7 +184,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
+msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pot/part2.pot b/docs/reference/src/main/docbook/pot/part2.pot
index e89a6feea58..3e532e4fdfb 100644
--- a/docs/reference/src/main/docbook/pot/part2.pot
+++ b/docs/reference/src/main/docbook/pot/part2.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
-"PO-Revision-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
diff --git a/docs/reference/src/main/docbook/pot/part3.pot b/docs/reference/src/main/docbook/pot/part3.pot
index 462ab16bcd0..6d2aa55ccc5 100644
--- a/docs/reference/src/main/docbook/pot/part3.pot
+++ b/docs/reference/src/main/docbook/pot/part3.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
-"PO-Revision-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -14,7 +14,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
+msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
msgstr ""
#. Tag: para
@@ -69,7 +69,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You don't see string-based identifiers in CDI 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!"
+msgid "You don't see string-based identifiers in CDI 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 ""
#. Tag: para
@@ -139,6 +139,6 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
+msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
msgstr ""
diff --git a/docs/reference/src/main/docbook/pot/part4.pot b/docs/reference/src/main/docbook/pot/part4.pot
index e5b5a5371c5..8b64b7215db 100644
--- a/docs/reference/src/main/docbook/pot/part4.pot
+++ b/docs/reference/src/main/docbook/pot/part4.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
-"PO-Revision-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -14,7 +14,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
+msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
msgstr ""
#. Tag: para
@@ -24,6 +24,6 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
+msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
msgstr ""
diff --git a/docs/reference/src/main/docbook/pot/part5.pot b/docs/reference/src/main/docbook/pot/part5.pot
index 28b643e2c31..3a3f2e3f430 100644
--- a/docs/reference/src/main/docbook/pot/part5.pot
+++ b/docs/reference/src/main/docbook/pot/part5.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
-"PO-Revision-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -14,7 +14,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and Glassfish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
+msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and GlassFish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pot/producermethods.pot b/docs/reference/src/main/docbook/pot/producermethods.pot
index 3884336b9ba..accc124f349 100644
--- a/docs/reference/src/main/docbook/pot/producermethods.pot
+++ b/docs/reference/src/main/docbook/pot/producermethods.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
-"PO-Revision-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -19,7 +19,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
+msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
msgstr ""
#. Tag: para
@@ -74,7 +74,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
+msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
msgstr ""
#. Tag: programlisting
@@ -135,7 +135,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
+msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
msgstr ""
#. Tag: para
@@ -150,12 +150,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
+msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
+msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
msgstr ""
#. Tag: programlisting
@@ -175,12 +175,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of "promoting" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left "hanging" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
+msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of \"promoting\" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left \"hanging\" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
+msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
msgstr ""
#. Tag: para
@@ -215,7 +215,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
+msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
msgstr ""
#. Tag: title
diff --git a/docs/reference/src/main/docbook/pot/resources.pot b/docs/reference/src/main/docbook/pot/resources.pot
index 8fda2fa57fc..79e562e1366 100644
--- a/docs/reference/src/main/docbook/pot/resources.pot
+++ b/docs/reference/src/main/docbook/pot/resources.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
-"PO-Revision-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -24,7 +24,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a nonportable "mapped name"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
+msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a non-portable \"mapped name\"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
msgstr ""
#. Tag: para
@@ -69,31 +69,31 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Produces @WebServiceRef(lookup="java:app/service/Catalog")\n"
+msgid "@Produces @WebServiceRef(lookup=\"java:app/service/Catalog\")\n"
"Catalog catalog;"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Produces @Resource(lookup="java:global/env/jdbc/CustomerDatasource") \n"
+msgid "@Produces @Resource(lookup=\"java:global/env/jdbc/CustomerDatasource\") \n"
"@CustomerDatabase Datasource customerDatabase;"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Produces @PersistenceContext(unitName="CustomerDatabase")\n"
+msgid "@Produces @PersistenceContext(unitName=\"CustomerDatabase\")\n"
"@CustomerDatabase EntityManager customerDatabasePersistenceContext;"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Produces @PersistenceUnit(unitName="CustomerDatabase") \n"
+msgid "@Produces @PersistenceUnit(unitName=\"CustomerDatabase\") \n"
"@CustomerDatabase EntityManagerFactory customerDatabasePersistenceUnit;"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Produces @EJB(ejbLink="../their.jar#PaymentService") \n"
+msgid "@Produces @EJB(ejbLink=\"../their.jar#PaymentService\") \n"
"PaymentService paymentService;"
msgstr ""
@@ -119,7 +119,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
+msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
msgstr ""
#. Tag: title
@@ -164,7 +164,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
+msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
msgstr ""
#. Tag: programlisting
@@ -179,7 +179,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@PersistenceContext(unitName="CustomerDatabase") EntityManager"
+msgid "@PersistenceContext(unitName=\"CustomerDatabase\") EntityManager"
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pot/ri-spi.pot b/docs/reference/src/main/docbook/pot/ri-spi.pot
index 78d6ab201f1..4df2cdc582e 100644
--- a/docs/reference/src/main/docbook/pot/ri-spi.pot
+++ b/docs/reference/src/main/docbook/pot/ri-spi.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
-"PO-Revision-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -29,7 +29,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the "Weld: Servlets" extension will be sufficient, and will work in any container supporting the Servlet API."
+msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the \"Weld: Servlets\" extension will be sufficient, and will work in any container supporting the Servlet API."
msgstr ""
#. Tag: para
@@ -54,7 +54,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
+msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
msgstr ""
#. Tag: para
@@ -74,7 +74,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
+msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
msgstr ""
#. Tag: para
@@ -94,7 +94,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
+msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
msgstr ""
#. Tag: para
@@ -104,12 +104,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
+msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
+msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
msgstr ""
#. Tag: para
@@ -124,7 +124,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
+msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
msgstr ""
#. Tag: para
@@ -154,7 +154,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
+msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
msgstr ""
#. Tag: para
@@ -194,7 +194,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
+msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
msgstr ""
#. Tag: title
@@ -209,7 +209,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
+msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
msgstr ""
#. Tag: para
@@ -274,7 +274,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); intercepter will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
+msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); interceptor will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
msgstr ""
#. Tag: para
@@ -349,7 +349,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
+msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
msgstr ""
#. Tag: title
@@ -364,7 +364,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programtically, or built in). Bean validation will validate all beans."
+msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programmatically, or built in). Bean validation will validate all beans."
msgstr ""
#. Tag: para
@@ -424,7 +424,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuation, classloader isolation for each CDI application."
+msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuration, classloader isolation for each CDI application."
msgstr ""
#. Tag: term
@@ -439,7 +439,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You must ensure that that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
+msgid "You must ensure that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
msgstr ""
#. Tag: term
@@ -579,7 +579,7 @@ msgid "// Fire ProcessInjectionTarget, returning the InjectionTarget\n"
"InjectionTarget it = weldBeanManager.fireProcessInjectionTarget(clazz);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
+"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
"\n"
"// Produce the instance, performing any constructor injection required\n"
"Object instance = it.produce();\n"
@@ -612,16 +612,16 @@ msgstr ""
#, no-c-format
msgid "// Obtain the EjbDescriptor for the EJB\n"
"// You may choose to use this utility method to get the descriptor\n"
-"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
+"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
"\n"
"// Get an the Bean object\n"
-"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
+"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
"\n"
"// Create the injection target\n"
"InjectionTarget it = deploymentBeanManager.createInjectionTarget(ejbDescriptor);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
+"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
"\n"
"// Perform injection and call initializers\n"
"it.inject(instance, cc);\n"
diff --git a/docs/reference/src/main/docbook/pot/scopescontexts.pot b/docs/reference/src/main/docbook/pot/scopescontexts.pot
index 5bd788f68bc..724c7090ae9 100644
--- a/docs/reference/src/main/docbook/pot/scopescontexts.pot
+++ b/docs/reference/src/main/docbook/pot/scopescontexts.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
-"PO-Revision-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -19,7 +19,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
+msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
msgstr ""
#. Tag: para
@@ -44,7 +44,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
+msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
msgstr ""
#. Tag: title
@@ -54,7 +54,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
+msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
msgstr ""
#. Tag: programlisting
@@ -67,7 +67,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
+msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
msgstr ""
#. Tag: para
@@ -83,7 +83,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Usually, you'll use one of CDI's built-in scopes."
+msgid "Usually, you'll use one of CDI's built-in scopes."
msgstr ""
#. Tag: title
@@ -183,7 +183,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
+msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
msgstr ""
#. Tag: title
@@ -208,7 +208,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
+msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
msgstr ""
#. Tag: para
@@ -300,24 +300,24 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<a href="/addProduct.jsp?cid=#{conversation.id}">Add Product</a>"
+msgid "<a href=\"/addProduct.jsp?cid=#{conversation.id}\">Add Product</a>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's probably better to use one of the link components in JSF 2:"
+msgid "It's probably better to use one of the link components in JSF 2:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<h:link outcome="/addProduct.xhtml" value="Add Product">\n"
-" <f:param name="cid" value="#{javax.enterprise.context.conversation.id}"/>\n"
-"</h:link>"
+msgid "<h:link outcome=\"/addProduct.xhtml\" value=\"Add Product\">\n"
+" <f:param name=\"cid\" value=\"#{javax.enterprise.context.conversation.id}\"/>\n"
+"</h:link>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a "flash" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
+msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a \"flash\" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
msgstr ""
#. Tag: title
@@ -327,7 +327,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
+msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
msgstr ""
#. Tag: para
@@ -357,12 +357,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can guess what "singleton" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
+msgid "You can guess what \"singleton\" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
+msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
msgstr ""
#. Tag: para
@@ -382,7 +382,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
+msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
msgstr ""
#. Tag: para
@@ -422,12 +422,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
+msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
+msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
msgstr ""
#. Tag: para
@@ -486,6 +486,6 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This feature is particularly useful with producer methods, as we'll see in the next chapter."
+msgid "This feature is particularly useful with producer methods, as we'll see in ."
msgstr ""
diff --git a/docs/reference/src/main/docbook/pot/specialization.pot b/docs/reference/src/main/docbook/pot/specialization.pot
index 2e2decb92f6..9efd025dd5a 100644
--- a/docs/reference/src/main/docbook/pot/specialization.pot
+++ b/docs/reference/src/main/docbook/pot/specialization.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
-"PO-Revision-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -19,7 +19,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
+msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
msgstr ""
#. Tag: para
@@ -39,12 +39,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
+msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
+msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
msgstr ""
#. Tag: title
@@ -67,7 +67,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
+msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
msgstr ""
#. Tag: programlisting
@@ -95,12 +95,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
+msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
+msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
msgstr ""
#. Tag: programlisting
@@ -133,16 +133,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+msgid "<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <alternatives>\n"
-" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
-" </alternatives>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <alternatives>\n"
+" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
+" </alternatives>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -167,7 +167,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
+msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
msgstr ""
#. Tag: para
@@ -221,7 +221,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
+msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pot/stereotypes.pot b/docs/reference/src/main/docbook/pot/stereotypes.pot
index 89e2aa08c67..73347c5303b 100644
--- a/docs/reference/src/main/docbook/pot/stereotypes.pot
+++ b/docs/reference/src/main/docbook/pot/stereotypes.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
-"PO-Revision-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -89,7 +89,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
+msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
msgstr ""
#. Tag: title
@@ -124,7 +124,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
+msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
msgstr ""
#. Tag: title
@@ -217,12 +217,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
+msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
+msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
msgstr ""
#. Tag: programlisting
@@ -242,7 +242,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
+msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pot/weldexamples.pot b/docs/reference/src/main/docbook/pot/weldexamples.pot
index c4d5eb0dd03..182ced0d370 100644
--- a/docs/reference/src/main/docbook/pot/weldexamples.pot
+++ b/docs/reference/src/main/docbook/pot/weldexamples.pot
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
-"PO-Revision-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
@@ -19,7 +19,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
+msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
msgstr ""
#. Tag: title
@@ -29,73 +29,73 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
+msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
+msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
+msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<faces-config version="2.0"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+msgid "<faces-config version=\"2.0\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd">\n"
-"</faces-config>"
+" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd\">\n"
+"</faces-config>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
+msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, there's the familiar web.xml:"
+msgid "Finally, there's the familiar web.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<web-app version="2.5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+msgid "<web-app version=\"2.5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd\">\n"
" \n"
-" <display-name>weld-jsf-numberguess-war</display-name>\n"
-" <description>Weld JSF numberguess example (war)</description>\n"
+" <display-name>weld-jsf-numberguess-war</display-name>\n"
+" <description>Weld JSF numberguess example (war)</description>\n"
"\n"
-" <servlet>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
-" <load-on-startup>1</load-on-startup>\n"
-" </servlet>\n"
+" <servlet>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
+" <load-on-startup>1</load-on-startup>\n"
+" </servlet>\n"
"\n"
-" <servlet-mapping>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <url-pattern>*.jsf</url-pattern>\n"
-" </servlet-mapping>\n"
+" <servlet-mapping>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <url-pattern>*.jsf</url-pattern>\n"
+" </servlet-mapping>\n"
" \n"
-" <context-param>\n"
-" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
-" <param-value>.xhtml</param-value>\n"
-" </context-param>\n"
+" <context-param>\n"
+" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
+" <param-value>.xhtml</param-value>\n"
+" </context-param>\n"
"\n"
-" <session-config>\n"
-" <session-timeout>10</session-timeout>\n"
-" </session-config>\n"
+" <session-config>\n"
+" <session-timeout>10</session-timeout>\n"
+" </session-config>\n"
"\n"
-"</web-app>"
+"</web-app>"
msgstr ""
#. Tag: para
@@ -125,50 +125,50 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
+msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"\n"
-" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">\n"
-"<html xmlns="http://www.w3.org/1999/xhtml"\n"
-" xmlns:ui="http://java.sun.com/jsf/facelets"\n"
-" xmlns:h="http://java.sun.com/jsf/html"\n"
-" xmlns:f="http://java.sun.com/jsf/core">\n"
+msgid "<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
+" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n"
+"<html xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" xmlns:ui=\"http://java.sun.com/jsf/facelets\"\n"
+" xmlns:h=\"http://java.sun.com/jsf/html\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\">\n"
"\n"
-" <ui:composition template="/template.xhtml">\n"
-" <ui:define name="content">\n"
-" <h1>Guess a number...</h1>\n"
-" <h:form id="numberGuess">\n"
-" <div style="color: red">\n"
-" <h:messages id="messages" globalOnly="false"/>\n"
-" <h:outputText id="Higher" value="Higher!"\n"
-" rendered="#{game.number gt game.guess and game.guess ne 0}"/>\n"
-" <h:outputText id="Lower" value="Lower!"\n"
-" rendered="#{game.number lt game.guess and game.guess ne 0}"/>\n"
-" </div>\n"
+" <ui:composition template=\"/template.xhtml\">\n"
+" <ui:define name=\"content\">\n"
+" <h1>Guess a number...</h1>\n"
+" <h:form id=\"numberGuess\">\n"
+" <div style=\"color: red\">\n"
+" <h:messages id=\"messages\" globalOnly=\"false\"/>\n"
+" <h:outputText id=\"Higher\" value=\"Higher!\"\n"
+" rendered=\"#{game.number gt game.guess and game.guess ne 0}\"/>\n"
+" <h:outputText id=\"Lower\" value=\"Lower!\"\n"
+" rendered=\"#{game.number lt game.guess and game.guess ne 0}\"/>\n"
+" </div>\n"
" \n"
-" <div>\n"
-" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
+" <div>\n"
+" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
" You have #{game.remainingGuesses} guesses remaining.\n"
-" </div>\n"
+" </div>\n"
" \n"
-" <div>\n"
+" <div>\n"
" Your guess: \n"
-" <h:inputText id="inputGuess" value="#{game.guess}"\n"
-" size="3" required="true" disabled="#{game.number eq game.guess}"\n"
-" validator="#{game.validateNumberRange}"/>\n"
-" <h:commandButton id="guessButton" value="Guess" \n"
-" action="#{game.check}" disabled="#{game.number eq game.guess}"/>\n"
-" </div>\n"
-" <div>\n"
-" <h:commandButton id="restartButton" value="Reset" action="#{game.reset}" immediate="true"/>\n"
-" </div>\n"
-" </h:form>\n"
-" </ui:define>\n"
-" </ui:composition>\n"
-"</html>"
+" <h:inputText id=\"inputGuess\" value=\"#{game.guess}\"\n"
+" size=\"3\" required=\"true\" disabled=\"#{game.number eq game.guess}\"\n"
+" validator=\"#{game.validateNumberRange}\"/>\n"
+" <h:commandButton id=\"guessButton\" value=\"Guess\" \n"
+" action=\"#{game.check}\" disabled=\"#{game.number eq game.guess}\"/>\n"
+" </div>\n"
+" <div>\n"
+" <h:commandButton id=\"restartButton\" value=\"Reset\" action=\"#{game.reset}\" immediate=\"true\"/>\n"
+" </div>\n"
+" </h:form>\n"
+" </ui:define>\n"
+" </ui:composition>\n"
+"</html>"
msgstr ""
#. Tag: para
@@ -178,7 +178,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are a number of messages which can be sent to the user, "Higher!", "Lower!" and "Correct!""
+msgid "There are a number of messages which can be sent to the user, \"Higher!\", \"Lower!\" and \"Correct!\""
msgstr ""
#. Tag: para
@@ -193,7 +193,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
+msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
msgstr ""
#. Tag: para
@@ -259,7 +259,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Generator is application scoped, so we don't get a different random each time."
+msgid "The Generator is application scoped, so we don't get a different random each time."
msgstr ""
#. Tag: para
@@ -269,12 +269,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
+msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
+msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
msgstr ""
#. Tag: programlisting
@@ -290,19 +290,19 @@ msgid "@Named\n"
" private int remainingGuesses;\n"
"\n"
" @Inject @MaxNumber private int maxNumber;\n"
-" @Inject @Random Instance<Integer> randomNumber;\n"
+" @Inject @Random Instance<Integer> randomNumber;\n"
" \n"
" public Game() {}\n"
" \n"
" public void check() {\n"
-" if (guess > number) {\n"
+" if (guess > number) {\n"
" biggest = guess - 1;\n"
" }\n"
-" else if (guess < number) {\n"
+" else if (guess < number) {\n"
" smallest = guess + 1;\n"
" }\n"
" else if (guess == number) {\n"
-" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage("Correct!"));\n"
+" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage(\"Correct!\"));\n"
" }\n"
" remainingGuesses--;\n"
" }\n"
@@ -317,18 +317,18 @@ msgid "@Named\n"
" }\n"
" \n"
" public void validateNumberRange(FacesContext context, UIComponent toValidate, Object value) {\n"
-" if (remainingGuesses <= 0) {\n"
-" FacesMessage message = new FacesMessage("No guesses left!");\n"
+" if (remainingGuesses <= 0) {\n"
+" FacesMessage message = new FacesMessage(\"No guesses left!\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" ((UIInput) toValidate).setValid(false);\n"
" return;\n"
" }\n"
" int input = (Integer) value;\n"
"\n"
-" if (input < smallest || input > biggest) {\n"
+" if (input < smallest || input > biggest) {\n"
" ((UIInput) toValidate).setValid(false);\n"
"\n"
-" FacesMessage message = new FacesMessage("Invalid guess");\n"
+" FacesMessage message = new FacesMessage(\"Invalid guess\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" }\n"
" }\n"
@@ -377,19 +377,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
+msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+msgid "<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
+msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
msgstr ""
#. Tag: title
@@ -409,17 +409,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin ."
+msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects . Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
+msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects. Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This will create a project in your workspace called weld-se-numberguess ."
+msgid "This will create a project in your workspace called weld-se-numberguess."
msgstr ""
#. Tag: para
@@ -429,7 +429,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to get the example running!"
+msgid "It's time to get the example running!"
msgstr ""
#. Tag: title
@@ -439,12 +439,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
+msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right click on the project, and choose Run As -> Run As Application:"
+msgid "Right click on the project, and choose Run As -> Run As Application:"
msgstr ""
#. Tag: para
@@ -494,7 +494,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's have a look at the significant code and configuration files that make up this example."
+msgid "Let's have a look at the significant code and configuration files that make up this example."
msgstr ""
#. Tag: para
@@ -504,7 +504,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
+msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
msgstr ""
#. Tag: programlisting
@@ -548,7 +548,7 @@ msgid "@ApplicationScoped\n"
"\n"
" public boolean isGameLost()\n"
" {\n"
-" return guess != number && remainingGuesses <= 0;\n"
+" return guess != number && remainingGuesses <= 0;\n"
" }\n"
"\n"
" public boolean check()\n"
@@ -557,12 +557,12 @@ msgid "@ApplicationScoped\n"
"\n"
" if (checkNewNumberRangeIsValid())\n"
" {\n"
-" if (guess > number)\n"
+" if (guess > number)\n"
" {\n"
" biggest = guess - 1;\n"
" }\n"
"\n"
-" if (guess < number)\n"
+" if (guess < number)\n"
" {\n"
" smallest = guess + 1;\n"
" }\n"
@@ -580,7 +580,7 @@ msgid "@ApplicationScoped\n"
"\n"
" private boolean checkNewNumberRangeIsValid()\n"
" {\n"
-" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
+" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
" }\n"
"\n"
" @PostConstruct\n"
@@ -597,12 +597,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
+msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
+msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
msgstr ""
#. Tag: para
@@ -632,12 +632,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
+msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
+msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
msgstr ""
#. Tag: programlisting
@@ -649,11 +649,11 @@ msgid "public class MessageGenerator\n"
"\n"
" public String getChallengeMessage()\n"
" {\n"
-" StringBuilder challengeMsg = new StringBuilder("I'm thinking of a number between ");\n"
+" StringBuilder challengeMsg = new StringBuilder(\"I'm thinking of a number between \");\n"
" challengeMsg.append(game.getSmallest());\n"
-" challengeMsg.append(" and ");\n"
+" challengeMsg.append(\" and \");\n"
" challengeMsg.append(game.getBiggest());\n"
-" challengeMsg.append(". Can you guess what it is?");\n"
+" challengeMsg.append(\". Can you guess what it is?\");\n"
"\n"
" return challengeMsg.toString();\n"
" }\n"
@@ -662,34 +662,34 @@ msgid "public class MessageGenerator\n"
" {\n"
" if (game.isGameWon())\n"
" {\n"
-" return "You guessed it! The number was " + game.getNumber();\n"
+" return \"You guessed it! The number was \" + game.getNumber();\n"
" }\n"
" else if (game.isGameLost())\n"
" {\n"
-" return "You are fail! The number was " + game.getNumber();\n"
+" return \"You are fail! The number was \" + game.getNumber();\n"
" }\n"
" else if (!game.isValidNumberRange())\n"
" {\n"
-" return "Invalid number range!";\n"
+" return \"Invalid number range!\";\n"
" }\n"
" else if (game.getRemainingGuesses() == Game.MAX_NUM_GUESSES)\n"
" {\n"
-" return "What is your first guess?";\n"
+" return \"What is your first guess?\";\n"
" }\n"
" else\n"
" {\n"
" String direction = null;\n"
"\n"
-" if (game.getGuess() < game.getNumber())\n"
+" if (game.getGuess() < game.getNumber())\n"
" {\n"
-" direction = "Higher";\n"
+" direction = \"Higher\";\n"
" }\n"
" else\n"
" {\n"
-" direction = "Lower";\n"
+" direction = \"Lower\";\n"
" }\n"
"\n"
-" return direction + "! You have " + game.getRemainingGuesses() + " guesses left.";\n"
+" return direction + \"! You have \" + game.getRemainingGuesses() + \" guesses left.\";\n"
" }\n"
" }\n"
"}"
@@ -702,7 +702,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
+msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
msgstr ""
#. Tag: para
@@ -771,7 +771,7 @@ msgid "public class NumberGuessFrame extends javax.swing.JFrame\n"
" private void refreshUI() {\n"
" mainLabel.setText( msgGenerator.getChallengeMessage() );\n"
" messageLabel.setText( msgGenerator.getResultMessage() );\n"
-" guessText.setText( "" );\n"
+" guessText.setText( \"\" );\n"
" guessesLeftBar.setValue( game.getRemainingGuesses() );\n"
" guessText.requestFocus();\n"
" }\n"
@@ -806,7 +806,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
+msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
msgstr ""
#. Tag: para
@@ -816,7 +816,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Calls game.check() to validate and perform one 'turn' of the game"
+msgid "Calls game.check() to validate and perform one 'turn' of the game"
msgstr ""
#. Tag: para
@@ -841,7 +841,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
+msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
msgstr ""
#. Tag: para
@@ -851,24 +851,24 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
+msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<plugin>\n"
-" <groupId>org.apache.maven.plugins</groupId>\n"
-" <artifactId>maven-ear-plugin</artifactId>\n"
-" <configuration>\n"
-" <modules>\n"
-" <webModule>\n"
-" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
-" <artifactId>weld-jsf-translator-war</artifactId>\n"
-" <contextRoot>/weld-translator</contextRoot>\n"
-" </webModule>\n"
-" </modules>\n"
-" </configuration>\n"
-"</plugin>"
+msgid "<plugin>\n"
+" <groupId>org.apache.maven.plugins</groupId>\n"
+" <artifactId>maven-ear-plugin</artifactId>\n"
+" <configuration>\n"
+" <modules>\n"
+" <webModule>\n"
+" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
+" <artifactId>weld-jsf-translator-war</artifactId>\n"
+" <contextRoot>/weld-translator</contextRoot>\n"
+" </webModule>\n"
+" </modules>\n"
+" </configuration>\n"
+"</plugin>"
msgstr ""
#. Tag: para
@@ -878,70 +878,70 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
+msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<application version="5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+msgid "<application version=\"5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/application_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/application_5.xsd\">\n"
"\n"
-" <display-name>weld-jsf-translator-ear</display-name>\n"
-" <description>The Weld JSF translator example (ear)</description>\n"
+" <display-name>weld-jsf-translator-ear</display-name>\n"
+" <description>The Weld JSF translator example (ear)</description>\n"
" \n"
-" <module>\n"
-" <web>\n"
-" <web-uri>weld-translator.war</web-uri>\n"
-" <context-root>/weld-translator</context-root>\n"
-" </web>\n"
-" </module>\n"
-" <module>\n"
-" <ejb>weld-translator.jar</ejb>\n"
-" </module>\n"
-"</application>"
+" <module>\n"
+" <web>\n"
+" <web-uri>weld-translator.war</web-uri>\n"
+" <context-root>/weld-translator</context-root>\n"
+" </web>\n"
+" </module>\n"
+" <module>\n"
+" <ejb>weld-translator.jar</ejb>\n"
+" </module>\n"
+"</application>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
+msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (ommitted here for brevity):"
+msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (omitted here for brevity):"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<h:form id="translator">\n"
+msgid "<h:form id=\"translator\">\n"
"\n"
-" <table>\n"
-" <tr align="center" style="font-weight: bold">\n"
-" <td>\n"
+" <table>\n"
+" <tr align=\"center\" style=\"font-weight: bold\">\n"
+" <td>\n"
" Your text\n"
-" </td>\n"
-" <td>\n"
+" </td>\n"
+" <td>\n"
" Translation\n"
-" </td>\n"
-" </tr>\n"
-" <tr>\n"
-" <td>\n"
-" <h:inputTextarea id="text" value="#{translator.text}" required="true" rows="5" cols="80"/>\n"
-" </td>\n"
-" <td>\n"
-" <h:outputText value="#{translator.translatedText}"/>\n"
-" </td>\n"
-" </tr>\n"
-" </table>\n"
-" <div>\n"
-" <h:commandButton id="button" value="Translate" action="#{translator.translate}"/>\n"
-" </div>\n"
+" </td>\n"
+" </tr>\n"
+" <tr>\n"
+" <td>\n"
+" <h:inputTextarea id=\"text\" value=\"#{translator.text}\" required=\"true\" rows=\"5\" cols=\"80\"/>\n"
+" </td>\n"
+" <td>\n"
+" <h:outputText value=\"#{translator.translatedText}\"/>\n"
+" </td>\n"
+" </tr>\n"
+" </table>\n"
+" <div>\n"
+" <h:commandButton id=\"button\" value=\"Translate\" action=\"#{translator.translate}\"/>\n"
+" </div>\n"
" \n"
-"</h:form>"
+"</h:form>"
msgstr ""
#. Tag: para
@@ -951,12 +951,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
+msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
+msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
msgstr ""
#. Tag: para
@@ -979,7 +979,7 @@ msgid "public class TextTranslator implements Serializable { \n"
" public String translate(String text) { \n"
" StringBuilder sb = new StringBuilder(); \n"
" for (String sentence: sentenceParser.parse(text)) { \n"
-" sb.append(translator.translate(sentence)).append(". "); \n"
+" sb.append(translator.translate(sentence)).append(\". \"); \n"
" } \n"
" return sb.toString().trim(); \n"
" }\n"
@@ -989,7 +989,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
+msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
msgstr ""
#. Tag: programlisting
@@ -998,7 +998,7 @@ msgid "@Stateless\n"
"public class SentenceTranslator implements Translator { \n"
"\n"
" public String translate(String sentence) { \n"
-" return "Lorem ipsum dolor sit amet"; \n"
+" return \"Lorem ipsum dolor sit amet\"; \n"
" }\n"
"\n"
"}"
@@ -1013,7 +1013,7 @@ msgstr ""
#, no-c-format
msgid "@Stateful\n"
"@RequestScoped\n"
-"@Named("translator")\n"
+"@Named(\"translator\")\n"
"public class TranslatorControllerBean implements TranslatorController {\n"
"\n"
" @Inject private TextTranslator translator;\n"
diff --git a/docs/reference/src/main/docbook/pt-BR/Weld_-_JSR-299_Reference_Implementation.po b/docs/reference/src/main/docbook/pt-BR/Weld_-_JSR-299_Reference_Implementation.po
new file mode 100644
index 00000000000..f4baccac014
--- /dev/null
+++ b/docs/reference/src/main/docbook/pt-BR/Weld_-_JSR-299_Reference_Implementation.po
@@ -0,0 +1,59 @@
+#
+# AUTHOR , YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "A note about naming and nomenclature"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Shortly before the final draft of JSR-299 was submitted, the specification changed its name from \"Web Beans\" to \"Java Contexts and Dependency Injection for the Java EE platform\", abbreviated CDI. For a brief period after the renaming, the reference implementation adopted the name \"Web Beans\". However, this ended up causing more confusion than it solved and Red Hat decided to change the name of the reference implementation to \"Weld\". You may still find other documentation, blogs, forum posts, etc. that use the old nomenclature. Please update any references you can. The naming game is over."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You'll also find that some of the functionality that once existed in the specification is now missing, such as defining beans in XML. These features will be available as portable extensions for CDI in the Weld project, and perhaps other implementations."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this reference guide was started while changes were still being made to the specification. We've done our best to update it for accuracy. If you discover a conflict between what is written in this guide and the specification, the specification is the authority—assume it is correct. If you believe you have found an error in the specification, please report it to the JSR-299 EG."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Beans"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Start with Weld, the CDI Reference Implementation"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Loose coupling with strong typing"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "CDI and the Java EE ecosystem"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Weld Reference Guide"
+msgstr ""
+
diff --git a/docs/reference/src/main/docbook/pt-BR/beans.po b/docs/reference/src/main/docbook/pt-BR/beans.po
index cad02afd776..446bbf5e763 100644
--- a/docs/reference/src/main/docbook/pt-BR/beans.po
+++ b/docs/reference/src/main/docbook/pt-BR/beans.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-04-14 15:37-0300\n"
"Last-Translator: Bruno Leonardo Gonçalves \n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr "Um bean é usualmente uma classe de aplicação que contém lógica de n
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
+msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
msgstr "Vamos voltar um segundo. O que realmente significa ser contextual? Uma vez que os beans podem ser stateful, é importante saber qual instância do bean eu tenho. Ao contrário de um modelo de componentes stateless (por exemplo, stateless session beans) ou um modelo de componentes singleton (como servlets, ou singleton beans), diferentes clientes de um bean vêem o bean em diferentes estados. O estado visível ao cliente depende de para qual instância do bean o cliente tem uma referência."
#. Tag: para
@@ -56,7 +56,7 @@ msgstr "Os clientes (por exemplo, outros beans) executados no mesmo contexto ver
#. Tag: para
#, fuzzy, no-c-format
-msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
+msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
msgstr "Uma grande vantagem do modelo contextual é que ele permite que stateful beans sejam tratados como serviços! O cliente não precisa se preocupar com o gerenciamento do ciclo de vida do bean que ele está usando, nem mesmo precisam saber o que é ciclo de vida. Os beans interagem passando mensagens, e as implementações do bean definem o ciclo de vida de seu próprio estado. Os beans são de baixo acoplamento porque:"
#. Tag: para
@@ -76,7 +76,7 @@ msgstr "Podemos substituir um bean por outro bean diferente que implementa a mes
#. Tag: para
#, fuzzy, no-c-format
-msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
+msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
msgstr "Note que nem todos os clientes de um bean são eles próprios também beans. Outros objetos como servlets ou message-driven beans—que são por natureza objetos não injetáveis e não contextuais—podem também obter referências para beans por meio de injeção."
#. Tag: title
@@ -131,7 +131,7 @@ msgstr "Além disso, um bean pode ou não pode ser um bean alternativo."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's see what all this new terminology means."
+msgid "Let's see what all this new terminology means."
msgstr "Vamos ver o que toda esta nova terminologia significa."
#. Tag: title
@@ -141,7 +141,7 @@ msgstr "Tipos e qualificadores de bean e injeção de dependência"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a "contract" that must be satisfied by the bean to be injected. The contract is:"
+msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a \"contract\" that must be satisfied by the bean to be injected. The contract is:"
msgstr "Beans usualmente adquirem referências para outros beans por meio de injeção de dependência. Qualquer atributo injetado especifica um \"contrato\" que deve ser satisfeito pelo bean para ser injetado. O contrato é:"
#. Tag: para
@@ -164,7 +164,7 @@ msgstr "Um tipo de bean é uma classe ou interface definida pelo usuário; um ti
msgid ""
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
@@ -176,7 +176,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
+msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
msgstr "Os tipos de bean são BookShop, Business e Shop<Book>, bem como o tipo implícito java.lang.Object. (Observe que um tipo parametrizado é um tipo de bean válido)."
#. Tag: para
@@ -203,12 +203,12 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
+msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
msgstr "Os tipos de bean de um session bean incluem suas interfaces locais e a classe de visão local do bean (se houver). As interfaces remotas do EJB não são consideradas tipos de bean de um session bean. Você não pode injetar um EJB usando sua interface remota, a menos que você defina um recurso, o qual vamos abordar no ."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
+msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
msgstr "Os tipos do bean podem ser limitados a um conjunto explícito, anotando o bean com a anotação @Typed e listando as classes que devem ser os tipos do bean. Por exemplo, os tipos de bean desde bean foram restritos a Shop<Book>, juntamente com java.lang.Object:"
#. Tag: programlisting
@@ -217,7 +217,7 @@ msgid ""
"@Typed(Shop.class)\n"
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
@@ -230,12 +230,12 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of "quality" using a qualifier."
+msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of \"quality\" using a qualifier."
msgstr "Algumas vezes um tipo de bean sozinho não fornece informação suficiente para o contêiner saber qual bean injetar. Por exemplo, suponha que temos duas implementações da interface PaymentProcessor: CreditCardPaymentProcessor e DebitPaymentProcessor. Injetar em um campo do tipo PaymentProcessor introduz uma condição ambígua. Nestes casos, o cliente deve especificar algum qualidade adicional da implementação que ele está interessado. Modelamos esta categoria de \"qualidade\" usando um qualificador."
#. Tag: para
#, fuzzy, no-c-format
-msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
+msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
msgstr "Um qualificador é uma anotação definida pelo usuário que é ela própria anotada com @Qualifer. Uma anotação de qualificador é uma extensão do sitema de tipos. Ela nos permite desambiguar um tipo sem ter que recorrer a nomes baseados em strings. Aqui está um exemplo de uma anotação de qualificador:"
#. Tag: programlisting
@@ -253,12 +253,12 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
+msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
msgstr "Você pode não estar acostumado a ver a definição de uma anotação. Na verdade, essa poderia ser a primeira vez que você encontrou uma. Com CDI, definições de anotação se tornará um artefato familiar conforme você for criando-os de vez em quando."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
+msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
msgstr "Preste atenção nos nomes das anotações embutidas em CDI e EJB. Você perceberá que elas são muitas vezes adjetivos. Nós encorajamos você a seguir esta convenção ao criar suas próprias anotações, uma vez que elas servem para descrever os comportamentos e papéis da classe."
#. Tag: para
@@ -271,14 +271,9 @@ msgstr "Agora que temos definido uma anotação de qualificador, podemos utiliz
msgid "@Inject @CreditCard PaymentProcessor paymentProcessor"
msgstr ""
-#. Tag: para
-#, no-c-format
-msgid "If an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
-msgstr "Se um ponto de injeção não define explicitamente um qualificador, ele terá o qualificador padrão, @Default."
-
#. Tag: para
#, fuzzy, no-c-format
-msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
+msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
msgstr "Para cada ponto de injeção, o contêiner pesquisa por um bean que satisfaça o contrato, um que tenha o tipo de bean e todos os qualificadores. Se ele encontrar exatamente um bean, ele injeta uma instância deste bean. Se ele não encontrar, ele reporta um erro ao usuário."
#. Tag: para
@@ -298,13 +293,13 @@ msgstr ""
" implements PaymentProcessor { ... }]]>"
#. Tag: para
-#, no-c-format
-msgid "If a bean does not explicitly specify a qualifier, it has the default qualifier, @Default."
-msgstr "Se um bean não define explicitamente um qualificador, ele terá o qualificador padrão, @Default."
+#, fuzzy, no-c-format
+msgid "If a bean or an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
+msgstr "Se um ponto de injeção não define explicitamente um qualificador, ele terá o qualificador padrão, @Default."
#. Tag: para
#, fuzzy, no-c-format
-msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
+msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
msgstr "Esse não é bem o fim da história. CDI também define uma simples regra de resolução que ajuda o contêiner decidir o que fazer se houver mais de um bean que satisfaz um contrato específico. Vamos entrar em mais detalhes no ."
#. Tag: title
@@ -338,7 +333,7 @@ msgstr "Uma instância de um bean com escopo de sessão está vinculada à sess
#. Tag: para
#, fuzzy, no-c-format
-msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
+msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
msgstr "Mantenha em mente que uma vez que um bean está vinculado a um contexto, ele permanece neste contexto até que o contexto seja destruído. Não existe modo algum para remover manualmente um bean daquele contexto. Se você não quer que o bean fique na sessão indefinitivamente, considere o uso de um outro escopo com um tempo de vida mais curto, como os escopos de solicitação e conversação."
#. Tag: para
@@ -348,7 +343,7 @@ msgstr "Se um escopo não está explicitamente especificado, então o bean perte
#. Tag: para
#, fuzzy, no-c-format
-msgid "We'll talk more about scopes in ."
+msgid "We'll talk more about scopes in ."
msgstr "Nós falaremos mais sobre escopos no ."
#. Tag: title
@@ -369,10 +364,10 @@ msgstr "O nome EL é especificado usando a anotação @Named,
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"public @SessionScoped @Named("cart")\n"
+"public @SessionScoped @Named(\"cart\")\n"
"class ShoppingCart implements Serializable { ... }"
msgstr ""
-""
#. Tag: para
@@ -383,9 +378,9 @@ msgstr "Agora podemos facilmente usar o bean em qualquer página JSF ou JSP:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:dataTable value="#{cart.lineItems}" var="item">\n"
+"<h:dataTable value=\"#{cart.lineItems}\" var=\"item\">\n"
" ...\n"
-"</h:dataTable>"
+"</h:dataTable>"
msgstr ""
"\n"
" ...\n"
@@ -422,7 +417,7 @@ msgstr "Alternativos"
#. Tag: para
#, fuzzy, no-c-format
-msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
+msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
msgstr "Nós já vimos como os qualificadores nos permite escolher entre múltiplas implementações de uma interface durante o desenvolvimento. Mas algumas vezes temos uma interface (ou outro tipo de bean), cuja implementação varia dependendo do ambiente de implantação. Por exemplo, podemos querer usar uma implementação de imitação em um ambiente de teste. Uma alternativa seria declarar a classe de bean com a anotação @Alternative."
#. Tag: programlisting
@@ -451,12 +446,12 @@ msgstr "Tipos para vinculação de interceptador"
#. Tag: para
#, fuzzy, no-c-format
-msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
+msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
msgstr "Você pode estar familiarizado com o uso de interceptadores em EJB 3.0. Em Java EE 6, esta funcionalidade foi generalizada para trabalhar com outros beans gerenciados. Está bem, você não precisa tornar seu bean um EJB apenas para interceptar seus métodos. (Berro). Então, o que CDI tem a oferecer além disso? Bem, bastante realmente. Vamos dar algumas explicações."
#. Tag: para
#, fuzzy, no-c-format
-msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
+msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
msgstr "A maneira em que interceptadores foram definidos em Java EE 5 não foi muito intuitivo. Era necessário especificar a implementação do interceptador diretamente na implementação do EJB, seja pela anotação @Interceptors ou no descritor XML. Você pode muito bem apenas colocar o código do interceptador dentro da implementação! Em segundo lugar, a ordem na qual os interceptadores são aplicados é obtida a partir da ordem na qual eles são declarados na anotação ou no descritor XML. Talvez isto não seja tão ruim se você está aplicando os interceptadores a um único bean. Mas, se você está aplicando eles repetidamente, então há uma boa chance de você definir por descuido uma ordem diferente para diferentes beans. Agora isso é um problema."
#. Tag: para
@@ -514,17 +509,17 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
+msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
msgstr "Observe que ShoppingCart e TransactionInterceptor não sabem nada sobre o outro."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
+msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
msgstr "Interceptadores são específicos de implantação. (Não precisamos de um TransactionInterceptor em nossos testes de unidade!) Por padrão, um interceptador está disabilitado. Podemos habilitar um interceptador usando o descritor de implantação CDI META-INF/beans.xml do jar ou módulo Java EE. Este descritor também é onde especificamos a ordem dos interceptadores."
#. Tag: para
#, fuzzy, no-c-format
-msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
+msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
msgstr "Discutiremos sobre interceptadores, e seus primos decoradores, no e ."
#. Tag: title
@@ -534,7 +529,7 @@ msgstr "Quais categorias de classes são beans?"
#. Tag: para
#, fuzzy, no-c-format
-msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
+msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
msgstr "Nós já vimos dois tipos de beans: JavaBeans e EJB session beans. Esta é toda a história? Na verdade, é apenas o começo. Vamos explorar as várias categorias de beans que implementações CDI devem suportar sem modificações."
#. Tag: title
@@ -544,7 +539,7 @@ msgstr "Managed beans"
#. Tag: para
#, fuzzy, no-c-format
-msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
+msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
msgstr "Um managed bean é uma classe Java. O ciclo de vida básico e a semântica de um managed bean são definidos pelo especificação de Managed Beans. Você pode explicitamente declarar um managed bean anotando a classe do bean com @ManagedBean, mas em CDI você não precisa disto. De acordo com a especificação, o contêiner CDI trata qualquer classe que satisfaz as seguintes condições como um managed bean:"
#. Tag: para
@@ -569,7 +564,7 @@ msgstr "Ela não implementa javax.enterprise.inject.spi.Extension@Inject."
#. Tag: para
#, fuzzy, no-c-format
-msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
+msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
msgstr "De acordo com esta definição, entidades JPA são tecnicamente managed beans. No entanto, as entidades possuem ciclo de vida, estado e modelo de identidade próprios e especiais, e são usualmente instanciadas por JPA ou utilizando new. Portanto, não recomendamos injetar uma classe de entidade diretamente. Recomendamos especialmente não atribuir um escopo que não seja @Dependent em uma classe de entidade, uma vez que JPA não é capaz de persistir proxies injetados por CDI."
#. Tag: para
@@ -629,12 +624,12 @@ msgstr "O conjunto irrestrito de tipos de bean para um session bean contém toda
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
+msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
msgstr "Não existe razão alguma para declarar explicitamente o escopo de um stateless session bean ou singleton session bean. O contêiner EJB controla o ciclo de vida destes beans, de acordo com a semântica da declaração @Stateless ou @Singleton. Por outro lado, um stateful session bean pode possuir qualquer escopo."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
+msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
msgstr "Stateful session beans podem definir um método de remoção, anotado com @Remove, que é utilizado pela aplicação para indicar que uma instância deve ser destruída. No entato, para uma instância contextual do bean—uma instância sob o controle de CDI—este método só pode ser chamado pela aplicação se o bean possuir o escopo @Dependent. Para beans com outros escopos, a aplicação deve deixar o contêiner destruir o bean."
#. Tag: para
@@ -669,7 +664,7 @@ msgstr "temporizadores e métodos assíncronos."
#. Tag: para
#, fuzzy, no-c-format
-msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
+msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
msgstr "Quando não precisamos de nenhuma dessas coisas, um managed bean comum servirá muito bem."
#. Tag: para
@@ -684,17 +679,17 @@ msgstr "Os beans que mantêm referências a recursos muito pesados, ou tiram mui
#. Tag: para
#, fuzzy, no-c-format
-msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
+msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
msgstr "Finalmente, normalmente é óbvio quando gerenciamento de transação a nível de método, segurança a nível de método, temporizadores, métodos remotos ou métodos assíncronos são utilizados."
#. Tag: para
#, fuzzy, no-c-format
-msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
+msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
msgstr "O ponto que estamos tentando determinar é: usar um session bean quando você precisar dos serviços que ele oferece, não apenas porque você quer usar injeção de dependência, gerenciamento de ciclo de vida, ou interceptadores. Java EE 6 fornece um modelo de programação graduado. É normalmente fácil iniciar com um managed bean habitual e, posteriormente, transformá-lo em um EJB apenas adicionando uma das seguintes anotações: @Stateless, @Stateful ou @Singleton."
#. Tag: para
#, fuzzy, no-c-format
-msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're "heavyweight". It's nothing more than superstition to think that something is "heavier" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like "heavyweight"."
+msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're \"heavyweight\". It's nothing more than superstition to think that something is \"heavier\" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like \"heavyweight\"."
msgstr "Por outro lado, não tenha medo de usar session beans apenas porque você ouviu seus amigos dizer que eles são \"pesados\". Não é nada mais do que superstição pensar que alguma coisa é \"mais pesada\" apenas porque é hospedada nativamente dentro do contêiner Java EE, em vez de um contêiner proprietário de beans ou um framework de injeção de dependência que executa como uma camada adicional de ofuscação. E como um princípio geral, você deve desconfiar de pessoas que usam uma terminologia vagamente definida, como \"pesado\"."
#. Tag: title
@@ -744,7 +739,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
+msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
msgstr "Não podemos escrever uma classe de bean que é ela própria um número aleatório. Mas podemos certamente escrever um método que retorna um número aleatório. Ao tornar o método um método produtor, permitimos que o valor de retorno do método—neste caso um Integer—seja injetado. Podemos até mesmo especificar um qualificador—neste caso @Random, um escopo—que neste caso é por padrão @Dependent, e um nome EL—que neste caso é por padrão randomNumber de acordo com a convenção JavaBeans para nome de propriedades. Agora podemos obter um número aleatório em qualquer lugar:"
#. Tag: programlisting
@@ -759,7 +754,7 @@ msgstr "Até mesmo em uma expressão Unified EL:"
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "<p>Your raffle number is #{randomNumber}.</p>"
+msgid "<p>Your raffle number is #{randomNumber}.</p>"
msgstr "Your raffle number is #{randomNumber}.]]>"
#. Tag: para
@@ -800,7 +795,7 @@ msgstr "Se o método produtor possuir parâmetros, o contêiner buscará por um
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Produces Set<Roles> getRoles(User user) {\n"
+"@Produces Set<Roles> getRoles(User user) {\n"
" return user.getRoles();\n"
"}"
msgstr ""
@@ -810,7 +805,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "We'll talk much more about producer methods in ."
+msgid "We'll talk much more about producer methods in ."
msgstr "Falaremos mais sobre métodos produtores no ."
#. Tag: title
@@ -820,7 +815,7 @@ msgstr "Campos produtores"
#. Tag: para
#, fuzzy, no-c-format
-msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
+msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
msgstr "Um campo produtor é uma alternativa mais simples para um método produtor. Um campo produtor é declarado ao anotar um campo de uma classe de bean com a anotação @Produces—a mesma anotação usada pelos métodos produtores."
#. Tag: programlisting
@@ -828,7 +823,7 @@ msgstr "Um campo produtor é uma alternativa mais simples p
msgid ""
"public class Shop {\n"
" @Produces PaymentProcessor paymentProcessor = ....;\n"
-" @Produces @Catalog List<Product> products = ....;\n"
+" @Produces @Catalog List<Product> products = ....;\n"
"}"
msgstr ""
". Because we can't wait to get to work on some examples."
+msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
msgstr "Um campo produtor é realmente apenas um atalho que nos permite evitar escrever um método getter sem utilidade. No entanto, além da conveniência, campos produtores servem um propósito específico como um adaptador para injeção no ambiente de componentes Java EE, mas para aprender mais sobre isto, você terá que aguardar até o . Porque não podemos esperar para começar a trabalhar em alguns exemplos."
+
+#~ msgid "If a bean does not explicitly specify a qualifier, it has the default qualifier, @Default."
+#~ msgstr "Se um bean não define explicitamente um qualificador, ele terá o qualificador padrão, @Default."
+
+#, fuzzy
+#~ msgid ""
+#~ "public @SessionScoped @Named("cart")\n"
+#~ "class ShoppingCart implements Serializable { ... }"
+#~ msgstr ""
+#~ ""
diff --git a/docs/reference/src/main/docbook/pt-BR/configure.po b/docs/reference/src/main/docbook/pt-BR/configure.po
index 1335db29b7d..b30e0049636 100644
--- a/docs/reference/src/main/docbook/pt-BR/configure.po
+++ b/docs/reference/src/main/docbook/pt-BR/configure.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:05:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -30,50 +30,50 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
+msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<?xml version="1.0" encoding="UTF-8"?>\n"
-"<beans xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \n"
-" xmlns:weld="http://jboss.org/schema/weld/beans" \n"
-" xsi:schemaLocation="\n"
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<beans xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" \n"
+" xmlns:weld=\"http://jboss.org/schema/weld/beans\" \n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee http://docs.jboss.org/cdi/beans_1_0.xsd\n"
-" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">\n"
+" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd\">\n"
" \n"
-" <weld:scan>\n"
+" <weld:scan>\n"
" \n"
-" <!-- Don't deploy the classes for the swing app! -->\n"
-" <weld:exclude name="com.acme.swing.**" />\n"
+" <!-- Don't deploy the classes for the swing app! -->\n"
+" <weld:exclude name=\"com.acme.swing.**\" />\n"
" \n"
-" <!-- Don't include GWT support if GWT is not installed -->\n"
-" <weld:exclude name="com.acme.gwt.**">\n"
-" <weld:if-class-available name="!com.google.GWT"/>\n"
-" </weld:exclude>\n"
+" <!-- Don't include GWT support if GWT is not installed -->\n"
+" <weld:exclude name=\"com.acme.gwt.**\">\n"
+" <weld:if-class-available name=\"!com.google.GWT\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
+" <!--\n"
" Exclude classes which end in Blether if the system property verbosity is set to low\n"
" i.e.\n"
" java ... -Dverbosity=low \n"
-" --> \n"
-" <weld:exclude pattern="^(.*)Blether$">\n"
-" <weld:if-system-property name="verbosity" value="low"/>\n"
-" </weld:exclude>\n"
+" --> \n"
+" <weld:exclude pattern=\"^(.*)Blether$\">\n"
+" <weld:if-system-property name=\"verbosity\" value=\"low\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
-" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
+" <!--\n"
+" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
" property is not set\n"
-" -->\n"
-" <weld:exclude name="com.acme.jsf.**">\n"
-" <weld:if-class-available name="org.apahce.wicket.Wicket"/>\n"
-" <weld:if-system-property name="!viewlayer"/>\n"
-" </weld:exclude>\n"
-" </weld:scan>\n"
+" -->\n"
+" <weld:exclude name=\"com.acme.jsf.**\">\n"
+" <weld:if-class-available name=\"org.apahce.wicket.Wicket\"/>\n"
+" <weld:if-system-property name=\"!viewlayer\"/>\n"
+" </weld:exclude>\n"
+" </weld:scan>\n"
" \n"
-"</beans>"
+"</beans>"
msgstr ""
#. Tag: para
@@ -83,7 +83,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
+msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
msgstr ""
#. Tag: para
@@ -93,12 +93,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
+msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
+msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
msgstr ""
#. Tag: para
@@ -113,5 +113,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
+msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
msgstr ""
diff --git a/docs/reference/src/main/docbook/pt-BR/contexts.po b/docs/reference/src/main/docbook/pt-BR/contexts.po
index 5e20509e1a6..383877e9fc9 100644
--- a/docs/reference/src/main/docbook/pt-BR/contexts.po
+++ b/docs/reference/src/main/docbook/pt-BR/contexts.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:05:00\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,17 +25,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld allows you to easiy manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivaed (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
+msgid "Weld allows you to easily manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivated (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and discociating the data store after calling activate."
+msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and dissociating the data store after calling activate."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld automatically controls context lifecycle in many scenarios such as Http Requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
+msgid "Weld automatically controls context lifecycle in many scenarios such as HTTP requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
msgstr ""
#. Tag: para
@@ -145,7 +145,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
+msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
msgstr ""
#. Tag: entry
@@ -245,12 +245,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implmentations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
+msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implementations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
+msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
msgstr ""
#. Tag: programlisting
@@ -263,14 +263,14 @@ msgid ""
" ...\n"
" \n"
" /* Start the request, providing a data store which will last the lifetime of the request */\n"
-" public void startRequest(Map<String, Object> requestDataStore) {\n"
+" public void startRequest(Map<String, Object> requestDataStore) {\n"
" // Associate the store with the context and acticate the context\n"
" requestContext.associate(requestDataStore);\n"
" requestContext.activate();\n"
" }\n"
" \n"
" /* End the request, providing the same data store as was used to start the request */\n"
-" public void endRequest(Map<String, Object> requestDataStore) {\n"
+" public void endRequest(Map<String, Object> requestDataStore) {\n"
" try {\n"
" /* Invalidate the request (all bean instances will be scheduled for destruction) */\n"
" requestContext.invalidate();\n"
@@ -290,7 +290,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's session contexts are "lazy" and don't require a session to actually exist until a bean instance must be written."
+msgid "Weld's session contexts are \"lazy\" and don't require a session to actually exist until a bean instance must be written."
msgstr ""
#. Tag: para
@@ -308,16 +308,16 @@ msgid ""
" /* Start a transient conversation */\n"
" /* Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */\n"
-" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" resumeOrStartConversation(requestDataStore, sessionDataStore, null);\n"
" }\n"
"\n"
" /* Start a transient conversation (if cid is null) or resume a non-transient */\n"
" /* conversation. Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */ \n"
-" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore, \n"
+" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore, \n"
" String cid) {\n"
" /* Associate the stores with the context and acticate the context */\n"
" * BoundRequest just wraps the two datastores */\n"
@@ -329,8 +329,8 @@ msgid ""
" /* End the conversations, providing the same data store as was used to start */\n"
" /* the request. Any transient conversations will be destroyed, any newly-promoted */\n"
" /* conversations will be placed into the session */\n"
-" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" try {\n"
" /* Invalidate the conversation (all transient conversations will be scheduled for destruction) */\n"
" conversationContext.invalidate();\n"
@@ -345,15 +345,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the containber), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
+msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the container), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the abilty to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
+msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the ability to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's conversations are not assigned ids until they become non-transient."
+msgid "Weld's conversations are not assigned ids until they become non-transient."
msgstr ""
diff --git a/docs/reference/src/main/docbook/pt-BR/decorators.po b/docs/reference/src/main/docbook/pt-BR/decorators.po
index eb623579464..fa8b99cd975 100644
--- a/docs/reference/src/main/docbook/pt-BR/decorators.po
+++ b/docs/reference/src/main/docbook/pt-BR/decorators.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-21 01:34-0300\n"
"Last-Translator: Bruno Leonardo Gonçalves \n"
"Language-Team: none\n"
@@ -21,12 +21,12 @@ msgstr "Decoradores"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
+msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
msgstr "Interceptadores são um meio poderoso para capturar e separar preocupações ortogonais na aplicação (e sistema de tipos). Qualquer interceptador é capaz de interceptar invocações de qualquer tipo Java. Isso os torna ideais para resolver questões técnicas, tais como gerenciamento de transação, segurança e registro de chamadas. No entanto, por natureza, interceptadores desconhecem a real semântica dos eventos que interceptam. Assim, interceptadores não são um instrumento adequado para a separação de questões relacionadas a negócios."
#. Tag: para
#, fuzzy, no-c-format
-msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
+msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
msgstr "O contrário é verdadeiro para decoradores. Um decorador intercepta invocações apenas para uma determinada interface Java e, portanto, é ciente de toda a semântica que acompanha esta interface. Visto que decoradores implementam diretamente operações com regras de negócios, isto torna eles uma ferramenta perfeita para modelar alguns tipos de questões de negócios. Isto também significa que um decorador não tem a generalidade de um interceptador. Decoradores não são capazes de resolver questões técnicas que atravessam muitos tipos diferentes. Interceptadores e decoradores, ambora similares em muitos aspectos, são complementares. Vamos ver alguns casos onde decoradores são bem convenientes."
#. Tag: para
@@ -118,7 +118,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
+msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
msgstr "Ao contrário de outros beans, um decorador pode ser uma classe abstrata. Portanto, se não há nada de especial que o decorador precise fazer para um determinado método da interface decorada, você não precisa implementar esse método."
#. Tag: para
@@ -205,14 +205,14 @@ msgid ""
" \n"
" public void withdraw(BigDecimal amount) {\n"
" account.withdraw(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedWithdrawl(amount) );\n"
" }\n"
" }\n"
" \n"
" public void deposit(BigDecimal amount);\n"
" account.deposit(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedDeposit(amount) );\n"
" }\n"
" }\n"
@@ -253,16 +253,16 @@ msgstr "Por padrão, todos decoradores estão desabilitados. Nós precisamos <interceptors> declaration serves for interceptors:"
+msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
msgstr "Essa declaração tem o mesmo propósito para decoradores que a declaração <interceptors> tem para os interceptadores:"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pt-BR/ee.po b/docs/reference/src/main/docbook/pt-BR/ee.po
index d176218c9a5..43cbc1c2b4d 100644
--- a/docs/reference/src/main/docbook/pt-BR/ee.po
+++ b/docs/reference/src/main/docbook/pt-BR/ee.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-12-19 18:11-0300\n"
"Last-Translator: João Paulo Viragine \n"
"Language-Team: none\n"
@@ -56,7 +56,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
+msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
msgstr ""
#. Tag: para
@@ -81,7 +81,7 @@ msgstr "Injetando recursos Java EE em um bean"
#. Tag: para
#, fuzzy, no-c-format
-msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
+msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
msgstr "Todos Web Beans, simples e corporativos (enterprise Web Beans), podem usufruir da injeção de dependência do Java EE utilizando @Resource, @EJB e @PersistenceContext. Nós já vimos vários exemplos disso, embora não demos muita ênfase até o momento:"
#. Tag: programlisting
@@ -135,7 +135,7 @@ msgstr "Invocando um Web Bean a partir de um Servlet"
#. Tag: para
#, fuzzy, no-c-format
-msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
+msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
msgstr "É fácil utilizar um Web Bean a partir de um Servlet em Java EE : basta injetar o Web Bean usando a injeção de atributos ou de método de inicialização de Web Beans."
#. Tag: programlisting
@@ -148,14 +148,14 @@ msgid ""
" @Override\n"
" public void service(HttpServletRequest request, HttpServletResponse response)\n"
" throws ServletException, IOException {\n"
-" credentials.setUsername(request.getParameter("username")):\n"
-" credentials.setPassword(request.getParameter("password")):\n"
+" credentials.setUsername(request.getParameter(\"username\")):\n"
+" credentials.setPassword(request.getParameter(\"password\")):\n"
" login.login();\n"
" if ( login.isLoggedIn() ) {\n"
-" response.sendRedirect("/home.jsp");\n"
+" response.sendRedirect(\"/home.jsp\");\n"
" }\n"
" else {\n"
-" response.sendRedirect("/loginError.jsp");\n"
+" response.sendRedirect(\"/loginError.jsp\");\n"
" }\n"
" }\n"
" \n"
@@ -193,7 +193,7 @@ msgstr "Invocando um Web Bean de um Message-Driven Bean"
#. Tag: para
#, no-c-format
-msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
+msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
msgstr ""
#. Tag: para
@@ -253,10 +253,10 @@ msgstr ""
#, fuzzy, no-c-format
msgid ""
"public class OrderResources {\n"
-" @Resource(name="jms/ConnectionFactory")\n"
+" @Resource(name=\"jms/ConnectionFactory\")\n"
" private ConnectionFactory connectionFactory;\n"
" \n"
-" @Resource(name="jms/OrderQueue")\n"
+" @Resource(name=\"jms/OrderQueue\")\n"
" private Queue orderQueue;\n"
" \n"
" @Produces @OrderConnection\n"
@@ -346,7 +346,7 @@ msgid ""
"\n"
"public void sendMessage() {\n"
" MapMessage msg = orderSession.createMapMessage();\n"
-" msg.setLong("orderId", order.getId());\n"
+" msg.setLong(\"orderId\", order.getId());\n"
" ...\n"
" producer.send(msg);\n"
"}"
@@ -374,7 +374,7 @@ msgstr "Empacotamento e implantação"
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a "bean archive". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
+msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a \"bean archive\". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
msgstr "A Web Beans não define nenhum tipo especial de pacote de implantação. Você pode empacotar Web Beans em JARs, EJB-JARs ou WARs qualquer localização de implantação do classpath da aplicação. Entretanto, cada arquivo ( JARs, EJB-JARs ou WARs) que contém Web Beans deve incluir um arquivo chamado web-beans.xml no diretório META-INF ou no diretório WEB-INF. O arquivo pode ser vazio. Os Web Beans implantados em pacotes que não possuem o arquivo web-beans.xml não estarão disponíveis para uso na aplicação."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pt-BR/environments.po b/docs/reference/src/main/docbook/pt-BR/environments.po
index d16b80c4dc8..fe64bd0ab38 100644
--- a/docs/reference/src/main/docbook/pt-BR/environments.po
+++ b/docs/reference/src/main/docbook/pt-BR/environments.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-12-19 18:10-0300\n"
"Last-Translator: João Paulo Viragine \n"
"Language-Team: none\n"
@@ -56,12 +56,12 @@ msgstr "A Web Beans pode ser utilizada em qualquer Servlet container como o Tomc
#. Tag: para
#, fuzzy, no-c-format
-msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
+msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
msgstr "A Web Beans não suporta a implantação de session beans, injeção utilizando @EJB, @Resource, ou @PersistenceContext, ou eventos transacionais no Tomcat."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an "uber-jar", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
+msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an \"uber-jar\", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
msgstr "A Web Beans deveria ser utilizada como uma bibilioteca de aplicação web no Tomcat. Você deve colocar o webbeans-tomcat.jar em WEB-INF/lib. webbeans-tomcat.jar é um \"hiper-jar\", disponível para a sua conveniência. Em vez disso, você pode utilizar os componentes do jars:"
#. Tag: para
@@ -72,9 +72,9 @@ msgstr "Você também precisa especificar explicitamente o Tomcat servlet listen
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
"\n"
" org.jboss.weld.environment.servlet.Listener\n"
@@ -87,18 +87,18 @@ msgstr "Tomcat"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
+msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
msgstr "O Tomcat tem um JNDI apenas de leitura. Assim, a Web Beans não pode vincular automaticamente o Manager. Para vincular o Manager no JNDI, você deve adicionar o seguinte ao seu META-INF/context.xml:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<Context>\n"
-" <Resource name="BeanManager" \n"
-" auth="Container"\n"
-" type="javax.enterprise.inject.spi.BeanManager"\n"
-" factory="org.jboss.weld.resources.ManagerObjectFactory"/>\n"
-"</Context>"
+"<Context>\n"
+" <Resource name=\"BeanManager\" \n"
+" auth=\"Container\"\n"
+" type=\"javax.enterprise.inject.spi.BeanManager\"\n"
+" factory=\"org.jboss.weld.resources.ManagerObjectFactory\"/>\n"
+"</Context>"
msgstr ""
"\n"
" \n"
" BeanManager\n"
@@ -146,27 +146,27 @@ msgstr "Jetty"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
+msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
msgstr "O Tomcat tem um JNDI apenas de leitura. Assim, a Web Beans não pode vincular automaticamente o Manager. Para vincular o Manager no JNDI, você deve adicionar o seguinte ao seu META-INF/context.xml:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.mortbay.jetty.plus.naming.Resource">\n"
-" <Arg><Ref id="webAppCtx"/></Arg> \n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.mortbay.jetty.plus.naming.Resource\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg> \n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure>"
msgstr ""
"\n"
@@ -192,22 +192,22 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://www.eclipse.org/jetty/configure.dtd">\n"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://www.eclipse.org/jetty/configure.dtd\">\n"
"\n"
-"<Configure id="webAppCtx" class="org.eclipse.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.eclipse.jetty.plus.jndi.Resource">\n"
-" <Arg> <Ref id="webAppCtx"/> </Arg>\n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure> "
+"<Configure id=\"webAppCtx\" class=\"org.eclipse.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.eclipse.jetty.plus.jndi.Resource\">\n"
+" <Arg> <Ref id=\"webAppCtx\"/> </Arg>\n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure> "
msgstr ""
"\n"
@@ -232,7 +232,7 @@ msgstr "e torná-lo disponível para a sua implantação, acrescentando-o ao
javax.naming.spi.ObjectFactory
like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
+msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
msgstr ""
#. Tag: para
@@ -242,19 +242,19 @@ msgstr "O Tomcat não só permite a você vincular as entradas para jav
#. Tag: para
#, no-c-format
-msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file META-INF/jetty-web.xml with the following content to your war:"
+msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file WEB-INF/jetty-web.xml with the following content to your war:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <Call class="org.jboss.weld.environment.jetty.WeldServletHandler" name="process">\n"
-" <Arg><Ref id="webAppCtx"/></Arg>\n"
-" </Call>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <Call class=\"org.jboss.weld.environment.jetty.WeldServletHandler\" name=\"process\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg>\n"
+" </Call>\n"
+"</Configure>"
msgstr ""
#. Tag: title
@@ -264,7 +264,7 @@ msgstr "Java SE"
#. Tag: para
#, no-c-format
-msgid "In addition to improved integration of the Enterprise Java stack, the "Contexts and Dependency Injection for the Java EE platform" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
+msgid "In addition to improved integration of the Enterprise Java stack, the \"Contexts and Dependency Injection for the Java EE platform\" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
msgstr ""
#. Tag: para
@@ -324,7 +324,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Parameters List<String> params;"
+msgid "@Inject @Parameters List<String> params;"
msgstr ""
#. Tag: programlisting
@@ -344,7 +344,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Here's an example of a simple CDI SE application:"
+msgid "Here's an example of a simple CDI SE application:"
msgstr "Aqui está um exemplo de uma simples aplicação Web Beans SE:"
#. Tag: programlisting
@@ -353,8 +353,8 @@ msgid ""
"@Singleton\n"
"public class HelloWorld\n"
"{\n"
-" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
-" System.out.println("Hello " + parameters.get(0));\n"
+" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
+" System.out.println(\"Hello \" + parameters.get(0));\n"
" }\n"
"}"
msgstr ""
@@ -385,7 +385,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
+msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
msgstr ""
#. Tag: para
@@ -395,17 +395,17 @@ msgstr "Aplicações Web Beans SE são iniciadas executando o seguinte método p
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "java org.jboss.weld.environment.se.StartMain <args>"
+msgid "java org.jboss.weld.environment.se.StartMain <args>"
msgstr "]]>"
#. Tag: title
#, no-c-format
-msgid "Programatic Bootstrap API"
+msgid "Programmatic Bootstrap API"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
+msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
msgstr ""
#. Tag: programlisting
@@ -431,10 +431,10 @@ msgid ""
"{\n"
"\n"
" /** Provides access to all beans within the application. */\n"
-" public Instance<Object> instance() {...}\n"
+" public Instance<Object> instance() {...}\n"
"\n"
" /** Provides access to all events within the application. */\n"
-" public Event<Object> event() {...}\n"
+" public Event<Object> event() {...}\n"
"\n"
" /** Provides direct access to the BeanManager. */\n"
" public BeanManager getBeanManager() {...}\n"
@@ -444,7 +444,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
+msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
msgstr ""
#. Tag: programlisting
@@ -484,22 +484,22 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
+msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans>\n"
-" <decorators>\n"
-" <decorator>org.jboss.weld.environment.se.threading.RunnableDecorator</decorator>\n"
-" </decorator>\n"
-"</beans>"
+"<beans>\n"
+" <decorators>\n"
+" <class>org.jboss.weld.environment.se.threading.RunnableDecorator</class>\n"
+" </decorator>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situtations where you would otherwise have used ThreadLocal directly, which are typically rare."
+msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situations where you would otherwise have used ThreadLocal directly, which are typically rare."
msgstr ""
#. Tag: title
@@ -509,7 +509,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
+msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pt-BR/events.po b/docs/reference/src/main/docbook/pt-BR/events.po
index bb5ade69bfa..8beed27213e 100644
--- a/docs/reference/src/main/docbook/pt-BR/events.po
+++ b/docs/reference/src/main/docbook/pt-BR/events.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-12-19 18:11-0300\n"
"Last-Translator: João Paulo Viragine \n"
"Language-Team: none\n"
@@ -36,7 +36,7 @@ msgstr "não só os produtores são desacoplados dos observadores; os observador
#. Tag: para
#, fuzzy, no-c-format
-msgid "observers can specify a combination of "selectors" to narrow the set of event notifications they will receive, and"
+msgid "observers can specify a combination of \"selectors\" to narrow the set of event notifications they will receive, and"
msgstr "os observadores podem especificar uma combinação de \"seletores\" para reduzir o conjunto de eventos que irão receber notificações, e"
#. Tag: para
@@ -46,7 +46,7 @@ msgstr "os observadores podem ser notificados imediatamente ou podem especificar
#. Tag: para
#, no-c-format
-msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
+msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
msgstr ""
#. Tag: title
@@ -61,7 +61,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
+msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
msgstr ""
#. Tag: programlisting
@@ -104,7 +104,7 @@ msgstr "only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
+msgid "An observer method need not specify any event qualifiers—in this case it is interested in only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
msgstr "Um método observador não necessita especificar nenhum binding de evento nesse caso, ele está interessado em todos os eventos de um determinado tipo. Se ele especificar o bindings de evento, ele estará apenas interessado em eventos que também têm esses bindings de evento."
#. Tag: para
@@ -129,7 +129,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Event<Document> documentEvent;"
+msgid "@Inject @Any Event<Document> documentEvent;"
msgstr " documentEvent;]]>"
#. Tag: para
@@ -184,7 +184,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
+msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
msgstr " documentUpdatedEvent;]]>"
#. Tag: para
@@ -204,12 +204,12 @@ msgstr "não especifique nenhum binding de evento exceto pa
#. Tag: para
#, no-c-format
-msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
+msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
+msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
msgstr "(){}).fire(document);]]>"
#. Tag: para
@@ -224,7 +224,7 @@ msgstr "Observadores transacionais"
#. Tag: para
#, no-c-format
-msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
+msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
msgstr ""
#. Tag: para
@@ -286,7 +286,7 @@ msgstr "Membros de tipo de binding de evento podem ser especificados estaticamen
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
+msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
msgstr " loggedInEvent;]]>"
#. Tag: para
@@ -298,7 +298,7 @@ msgstr "Alternativamente, o valor do membro do tipo de binding de evento pode se
#, fuzzy, no-c-format
msgid ""
"abstract class RoleBinding \n"
-" extends AnnotationLiteral<Role> \n"
+" extends AnnotationLiteral<Role> \n"
" implements Role {}"
msgstr ""
" blogEvent;\n"
"...\n"
@@ -445,12 +445,12 @@ msgid ""
"\n"
" @PersistenceContext EntityManager em;\n"
" \n"
-" List<Product> products;\n"
+" List<Product> products;\n"
"\n"
" @Produces @Catalog \n"
-" List<Product> getCatalog() {\n"
+" List<Product> getCatalog() {\n"
" if (products==null) {\n"
-" products = em.createQuery("select p from Product p where p.deleted = false")\n"
+" products = em.createQuery(\"select p from Product p where p.deleted = false\")\n"
" .getResultList();\n"
" }\n"
" return products;\n"
@@ -492,16 +492,16 @@ msgid ""
"@Stateless\n"
"public class ProductManager {\n"
" @PersistenceContext EntityManager em;\n"
-" @Inject @Any Event<Product> productEvent;\n"
+" @Inject @Any Event<Product> productEvent;\n"
"\n"
" public void delete(Product product) {\n"
" em.delete(product);\n"
-" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
" }\n"
" \n"
" public void persist(Product product) {\n"
" em.persist(product);\n"
-" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
" }\n"
" ...\n"
"}"
diff --git a/docs/reference/src/main/docbook/pt-BR/example.po b/docs/reference/src/main/docbook/pt-BR/example.po
index 176fec925c0..c49e0cd500c 100644
--- a/docs/reference/src/main/docbook/pt-BR/example.po
+++ b/docs/reference/src/main/docbook/pt-BR/example.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-01-15 10:27-0300\n"
"Last-Translator: Bruno Leonardo Gonçalves \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "Exemplo de aplicação web JSF "
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
+msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
msgstr "Vamos ilustrar essas ideias com um exemplo completo. Nós implementaremos um login/logout de usuário de uma aplicação que utiliza JSF. Primeiro, definiremos um bean com escopo de solicitação para manter o nome do usuário (username) e a senha (password) fornecidos durante o login, com as restrições definidas utilizando anotações da especificação Beans Validation:"
#. Tag: programlisting
@@ -63,18 +63,18 @@ msgstr "Esse bean é vinculado ao prompt de login no seguinte formulário JSF:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:form>\n"
-" <h:panelGrid columns="2" rendered="#{!login.loggedIn}">\n"
-" <f:validateBean>\n"
-" <h:outputLabel for="username">Username:</h:outputLabel>\n"
-" <h:inputText id="username" value="#{credentials.username}"/>\n"
-" <h:outputLabel for="password">Password:</h:outputLabel>\n"
-" <h:inputSecret id="password" value="#{credentials.password}"/>\n"
-" </f:validateBean>\n"
-" </h:panelGrid>\n"
-" <h:commandButton value="Login" action="#{login.login}" rendered="#{!login.loggedIn}"/>\n"
-" <h:commandButton value="Logout" action="#{login.logout}" rendered="#{login.loggedIn}"/>\n"
-"</h:form>"
+"<h:form>\n"
+" <h:panelGrid columns=\"2\" rendered=\"#{!login.loggedIn}\">\n"
+" <f:validateBean>\n"
+" <h:outputLabel for=\"username\">Username:</h:outputLabel>\n"
+" <h:inputText id=\"username\" value=\"#{credentials.username}\"/>\n"
+" <h:outputLabel for=\"password\">Password:</h:outputLabel>\n"
+" <h:inputSecret id=\"password\" value=\"#{credentials.password}\"/>\n"
+" </f:validateBean>\n"
+" </h:panelGrid>\n"
+" <h:commandButton value=\"Login\" action=\"#{login.login}\" rendered=\"#{!login.loggedIn}\"/>\n"
+" <h:commandButton value=\"Logout\" action=\"#{login.logout}\" rendered=\"#{login.loggedIn}\"/>\n"
+"</h:form>"
msgstr ""
"\n"
" \n"
@@ -119,7 +119,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
+msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
msgstr "(Observe que também vamos precisar de um arquivo persistence.xml para configurar a unidade de persistência JPA contendo a entidade User.)"
#. Tag: para
@@ -139,10 +139,10 @@ msgid ""
" private User user;\n"
" \n"
" public void login() {\n"
-" List<User> results = userDatabase.createQuery(\n"
-" "select u from User u where u.username = :username and u.password = :password")\n"
-" .setParameter("username", credentials.getUsername())\n"
-" .setParameter("password", credentials.getPassword())\n"
+" List<User> results = userDatabase.createQuery(\n"
+" \"select u from User u where u.username = :username and u.password = :password\")\n"
+" .setParameter(\"username\", credentials.getUsername())\n"
+" .setParameter(\"password\", credentials.getPassword())\n"
" .getResultList();\n"
" \n"
" if (!results.isEmpty()) {\n"
@@ -291,9 +291,9 @@ msgstr "Ou podemos referenciar o usuário atual em uma visão JSF:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:panelGroup rendered="#{login.loggedIn}">\n"
+"<h:panelGroup rendered=\"#{login.loggedIn}\">\n"
" signed in as #{currentUser.username}\n"
-"</h:panelGroup>"
+"</h:panelGroup>"
msgstr ""
"\n"
" signed in as #{currentUser.username}\n"
@@ -301,5 +301,5 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
+msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
msgstr "Esperamos que este exemplo tenha dado um gostinho do modelo de programação em CDI. No capítulo seguinte, exploraremos a injeção de dependência com maior profundidade."
diff --git a/docs/reference/src/main/docbook/pt-BR/extend.po b/docs/reference/src/main/docbook/pt-BR/extend.po
index e66356415ff..3df9bc00c43 100644
--- a/docs/reference/src/main/docbook/pt-BR/extend.po
+++ b/docs/reference/src/main/docbook/pt-BR/extend.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-12-19 18:03-0300\n"
"Last-Translator: João Paulo Viragine \n"
"Language-Team: none\n"
@@ -76,7 +76,7 @@ msgstr "A classe Bean "
#. Tag: para
#, no-c-format
-msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
+msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
msgstr ""
#. Tag: programlisting
@@ -164,15 +164,15 @@ msgid ""
"class MyExtension implements Extension {\n"
" \n"
" void beforeBeanDiscovery(@Observes BeforeBeanDiscovery bbd) {\n"
-" Logger.global.debug("beginning the scanning process");\n"
+" Logger.global.debug(\"beginning the scanning process\");\n"
" }\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
-" Logger.global.debug("scanning type: " + pat.getAnnotatedType().getJavaClass().getName());\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" Logger.global.debug(\"scanning type: \" + pat.getAnnotatedType().getJavaClass().getName());\n"
" } \n"
"\n"
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd) {\n"
-" Logger.global.debug("finished the scanning process");\n"
+" Logger.global.debug(\"finished the scanning process\");\n"
" }\n"
" \n"
"}"
@@ -180,7 +180,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
+msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
msgstr ""
#. Tag: programlisting
@@ -188,7 +188,7 @@ msgstr ""
msgid ""
"class MyExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" //tell the container to ignore the type if it is annotated @Ignore\n"
" if ( pat.getAnnotatedType().isAnnotionPresent(Ignore.class) ) pat.veto(); \n"
" } \n"
@@ -203,7 +203,7 @@ msgstr "O nervo central para estender a Web Beans é o objeto Manager
#. Tag: programlisting
#, no-c-format
-msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
+msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
msgstr ""
#. Tag: title
@@ -220,31 +220,31 @@ msgstr "A interface Manager permite, programaticamente, regis
#, fuzzy, no-c-format
msgid ""
"public interface BeanManager {\n"
-" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
-" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
-" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
-" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
-" public Set<Bean<?>> getBeans(String name);\n"
-" public Bean<?> getPassivationCapableBean(String id);\n"
-" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
+" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
+" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
+" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
+" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
+" public Set<Bean<?>> getBeans(String name);\n"
+" public Bean<?> getPassivationCapableBean(String id);\n"
+" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
" public void validate(InjectionPoint injectionPoint);\n"
" public void fireEvent(Object event, Annotation... qualifiers);\n"
-" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
-" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
-" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
-" public boolean isScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
-" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
-" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
-" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
-" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
-" public Context getContext(Class<? extends Annotation> scopeType);\n"
+" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
+" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
+" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
+" public boolean isScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
+" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
+" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
+" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
+" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
+" public Context getContext(Class<? extends Annotation> scopeType);\n"
" public ELResolver getELResolver();\n"
" public ExpressionFactory wrapExpressionFactory(ExpressionFactory expressionFactory);\n"
-" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
-" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
+" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
+" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
"}"
msgstr ""
"BeanManager."
+msgid "Let's study some of the interfaces exposed by the BeanManager."
msgstr "O nervo central para estender a Web Beans é o objeto Manager."
#. Tag: title
@@ -308,21 +308,21 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to instatiate the object itself, and so only method and field injection will be supported."
+msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to insntatiate the object itself, and so only method and field injection will be supported."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"//get the BeanManager from JNDI\n"
-"BeanManager beanManager = (BeanManager) new InitialContext().lookup("java:comp/BeanManager");\n"
+"BeanManager beanManager = (BeanManager) new InitialContext().lookup(\"java:comp/BeanManager\");\n"
"\n"
"//CDI uses an AnnotatedType object to read the annotations of a class\n"
-"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
+"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
"\n"
"//The extension uses an InjectionTarget to delegate instantiation, dependency injection \n"
"//and lifecycle callbacks to the CDI container\n"
-"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
+"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
"\n"
"//each instance needs its own CDI CreationalContext\n"
"CreationalContext ctx = beanManager.createCreationalContext(null);\n"
@@ -352,22 +352,22 @@ msgstr "Instâncias da classe abstrata Bean representam Web B
#. Tag: para
#, no-c-format
-msgid "The Bean interface exposes all the interesting things we dicussed in ."
+msgid "The Bean interface exposes all the interesting things we discussed in ."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"public interface Bean<T> extends Contextual<T> {\n"
-" public Set<Type> getTypes();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Class<? extends Annotation> getScope();\n"
+"public interface Bean<T> extends Contextual<T> {\n"
+" public Set<Type> getTypes();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Class<? extends Annotation> getScope();\n"
" public String getName();\n"
-" public Set<Class<? extends Annotation>> getStereotypes();\n"
-" public Class<?> getBeanClass();\n"
+" public Set<Class<? extends Annotation>> getStereotypes();\n"
+" public Class<?> getBeanClass();\n"
" public boolean isAlternative();\n"
" public boolean isNullable();\n"
-" public Set<InjectionPoint> getInjectionPoints();\n"
+" public Set<InjectionPoint> getInjectionPoints();\n"
"}"
msgstr ""
" extends Contextual {\n"
@@ -384,12 +384,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's an easy way to find out what beans exist in the application:"
+msgid "There's an easy way to find out what beans exist in the application:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
+msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
msgstr ""
#. Tag: para
@@ -409,7 +409,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
+msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
msgstr ""
#. Tag: programlisting
@@ -420,49 +420,49 @@ msgid ""
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd, BeanManager bm) {\n"
" \n"
" //use this to read annotations of the class\n"
-" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
+" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
"\n"
" //use this to instantiate the class and inject dependencies\n"
-" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
+" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
"\n"
-" abd.addBean( new Bean<SecurityManager>() {\n"
+" abd.addBean( new Bean<SecurityManager>() {\n"
"\n"
" @Override\n"
-" public Class<?> getBeanClass() {\n"
+" public Class<?> getBeanClass() {\n"
" return SecurityManager.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
" public String getName() {\n"
-" return "securityManager";\n"
+" return \"securityManager\";\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getQualifiers() {\n"
-" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
-" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
-" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
+" public Set<Annotation> getQualifiers() {\n"
+" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
+" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
+" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
" return qualifiers;\n"
" }\n"
"\n"
" @Override\n"
-" public Class<? extends Annotation> getScope() {\n"
+" public Class<? extends Annotation> getScope() {\n"
" return SessionScoped.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Class<? extends Annotation>> getStereotypes() {\n"
+" public Set<Class<? extends Annotation>> getStereotypes() {\n"
" return Collections.emptySet();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypes() {\n"
-" Set<Type> types = new HashSet<Type>();\n"
+" public Set<Type> getTypes() {\n"
+" Set<Type> types = new HashSet<Type>();\n"
" types.add(SecurityManager.class);\n"
" types.add(Object.class);\n"
" return types;\n"
@@ -479,7 +479,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
+" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
" SecurityManager instance = it.produce(ctx);\n"
" it.inject(instance, ctx);\n"
" it.postConstruct(instance);\n"
@@ -488,7 +488,7 @@ msgid ""
"\n"
" @Override\n"
" public void destroy(SecurityManager instance, \n"
-" CreationalContext<SecurityManager> ctx) {\n"
+" CreationalContext<SecurityManager> ctx) {\n"
" it.preDestroy(instance);\n"
" it.dispose(instance);\n"
" ctx.release();\n"
@@ -517,7 +517,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
+msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
msgstr ""
#. Tag: programlisting
@@ -525,38 +525,38 @@ msgstr ""
msgid ""
"public class QualifiedNameExtension implements Extension {\n"
"\n"
-" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
+" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
"\n"
" //wrap this to override the annotations of the class\n"
-" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
+" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
" \n"
-" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
+" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
"\n"
" @Override\n"
-" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
+" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
" return at.getConstructors();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedField<? super X>> getFields() {\n"
+" public Set<AnnotatedField<? super X>> getFields() {\n"
" return at.getFields();\n"
" }\n"
"\n"
" @Override\n"
-" public Class<X> getJavaClass() {\n"
+" public Class<X> getJavaClass() {\n"
" return at.getJavaClass();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
+" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
" return at.getMethods();\n"
" }\n"
"\n"
" @Override\n"
-" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
+" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
" if ( Named.class.equals(annType) ) {\n"
" class NamedLiteral \n"
-" extends AnnotationLiteral<Named> \n"
+" extends AnnotationLiteral<Named> \n"
" implements Named {\n"
" @Override\n"
" public String value() {\n"
@@ -565,7 +565,7 @@ msgid ""
" final String qualifiedName;\n"
" if ( pkg.isAnnotationPresent(Named.class) ) {\n"
" qualifiedName = pkg.getAnnotation(Named.class).value() \n"
-" + '.' + unqualifiedName;\n"
+" + '.' + unqualifiedName;\n"
" }\n"
" else {\n"
" qualifiedName = unqualifiedName;\n"
@@ -581,7 +581,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getAnnotations() {\n"
+" public Set<Annotation> getAnnotations() {\n"
" return at.getAnnotations();\n"
" }\n"
"\n"
@@ -591,12 +591,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypeClosure() {\n"
+" public Set<Type> getTypeClosure() {\n"
" return at.getTypeClosure();\n"
" }\n"
"\n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
" return at.isAnnotationPresent(annType);\n"
" }\n"
" \n"
@@ -610,7 +610,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
+msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
msgstr ""
#. Tag: programlisting
@@ -618,17 +618,17 @@ msgstr ""
msgid ""
"class ServiceAlternativeExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" \n"
-" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
+" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
" \n"
" if ( Service.class.isAssignableFrom( type.getJavaClass() ) ) {\n"
" \n"
" //if the class implements Service, make it an @Alternative\n"
-" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
+" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
" \n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
" return annotationType.equals(Alternative.class) ? \n"
" true : type.isAnnotationPresent(annotationType);\n"
" }\n"
@@ -661,7 +661,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
+msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
msgstr ""
#. Tag: programlisting
@@ -681,25 +681,25 @@ msgstr ""
msgid ""
"public class ConfigExtension implements Extension {\n"
"\n"
-"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
+"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
"\t\t\n"
"\t\t//wrap this to intercept the component lifecycle\n"
-"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
+"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
"\t \n"
-" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
+" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
" \n"
" //use this to read annotations of the class and its members\n"
-" AnnotatedType<X> at = pit.getAnnotatedType();\n"
+" AnnotatedType<X> at = pit.getAnnotatedType();\n"
" \n"
" //read the properties file\n"
-" String propsFileName = at.getClass().getSimpleName() + ".properties";\n"
+" String propsFileName = at.getClass().getSimpleName() + \".properties\";\n"
" InputStream stream = at.getJavaClass().getResourceAsStream(propsFileName);\n"
" if (stream!=null) {\n"
" \n"
" try {\n"
" Properties props = new Properties();\n"
" props.load(stream);\n"
-" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
+" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
" String fieldName = property.getKey().toString();\n"
" Object value = property.getValue();\n"
" try {\n"
@@ -711,7 +711,7 @@ msgid ""
" else {\n"
" //TODO: do type conversion automatically\n"
" pit.addDefinitionError( new InjectionException(\n"
-" "field is not of type String: " + field ) );\n"
+" \"field is not of type String: \" + field ) );\n"
" }\n"
" }\n"
" catch (NoSuchFieldException nsfe) {\n"
@@ -727,14 +727,14 @@ msgid ""
" }\n"
" }\n"
" \n"
-" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
+" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
"\n"
" @Override\n"
-" public void inject(X instance, CreationalContext<X> ctx) {\n"
+" public void inject(X instance, CreationalContext<X> ctx) {\n"
" it.inject(instance, ctx);\n"
" \n"
" //set the values onto the new instance of the component\n"
-" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
+" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
" try {\n"
" configuredValue.getKey().set(instance, configuredValue.getValue());\n"
" }\n"
@@ -760,12 +760,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
-" public X produce(CreationalContext<X> ctx) {\n"
+" public X produce(CreationalContext<X> ctx) {\n"
" return it.produce(ctx);\n"
" }\n"
" \n"
@@ -780,7 +780,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
+msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
msgstr ""
#. Tag: title
@@ -797,9 +797,9 @@ msgstr "A interface Context suporta a adição de novos escop
#, fuzzy, no-c-format
msgid ""
"public interface Context {\n"
-" public Class<? extends Annotation> getScope();\n"
-" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
-" public <T> T get(Contextual<T> contextual);\n"
+" public Class<? extends Annotation> getScope();\n"
+" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
+" public <T> T get(Contextual<T> contextual);\n"
" boolean isActive();\n"
"}"
msgstr ""
diff --git a/docs/reference/src/main/docbook/pt-BR/gettingstarted.po b/docs/reference/src/main/docbook/pt-BR/gettingstarted.po
index 9ab0d99ce43..3c9f2594560 100644
--- a/docs/reference/src/main/docbook/pt-BR/gettingstarted.po
+++ b/docs/reference/src/main/docbook/pt-BR/gettingstarted.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-21 01:13-0300\n"
"Last-Translator: Bruno Leonardo Gonçalves \n"
"Language-Team: none\n"
@@ -20,8 +20,8 @@ msgid "Getting started with Weld"
msgstr "Iniciando com o Weld"
#. Tag: para
-#, no-c-format
-msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, Glassfish 3.0 or any compliant Java EE 6 container."
+#, fuzzy, no-c-format
+msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, GlassFish 3.0 or any compliant Java EE 6 container."
msgstr "O Weld vem com vários exemplos. Nós recomendamos que você inicie com examples/jsf/numberguess e examples/jsf/translator. O numberguess é um exemplo web (war) contendo somente managed beans não-transacionais. Este exemplo pode ser executado em uma ampla variedade de servidores, incluindo JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, e qualquer contêiner Java EE 6 compatível. O translator é um exemplo corporativo (ear) que contém sessions beans. Este exemplo deve executar no JBoss AS 6.0, GlassFish 3.0 ou qualquer contêiner Java EE 6 compatível."
#. Tag: para
@@ -36,7 +36,7 @@ msgstr "Pré-requisitos"
#. Tag: para
#, fuzzy, no-c-format
-msgid "To run the examples with the provided build scripts, you'll need the following:"
+msgid "To run the examples with the provided build scripts, you'll need the following:"
msgstr "Para executar os exemplos com os scripts de construção fornecidos, você precisará dos seguintes itens:"
#. Tag: para
@@ -81,12 +81,12 @@ msgstr "(opcionalmente) Maven 2.x, para executar os exemplos em um contêiner se
#. Tag: para
#, fuzzy, no-c-format
-msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
+msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
msgstr "Você precisará de uma instalação completa do Ant 1.7.0. Algumas distribuições Linux fornecem apenas uma instalação parcial do Ant que faz com que a construção falhe. Se você tiver problemas, verifique se ant-nodeps.jar está no classpath."
#. Tag: para
#, fuzzy, no-c-format
-msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
+msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
msgstr "Nas próximas seções, você usará o comando do Ant (ant) para invocar o script de construção do Ant em cada exemplo para compilar, montar e implantar o exemplo no JBoss AS e, para o exemplo war, no Apache Tomcat. Você também pode implantar o artefato produzido (war ou ear) em qualquer outro contêiner que suporte Java EE 6, como o GlassFish 3."
#. Tag: para
@@ -96,7 +96,7 @@ msgstr "Se você tem o Maven instalado, você pode usar o comando do Maven (JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
+msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
msgstr "Para implantar os exemplos no JBoss AS, você precisará do JBoss AS 6.0.0 ou acima. Se uma versão da linha JBoss AS 6.0 ainda não estiver disponível, você pode baixar um nightly snapshot. A razão do JBoss AS 6.0.0 ou acima ser requerido é porque esta é a primeira versão que possui suporte embutido a CDI e Bean Validation, tornando-o próximo suficiente a Java EE 6 para executar os exemplos. A boa notícia é que não existem modificações adicionais que você tenha que fazer no servidor. Está pronto para funcionar!"
#. Tag: para
#, fuzzy, no-c-format
-msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
+msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
msgstr "Depois de ter baixado o JBoss AS, extrai-o. (Recomendamos renomear a pasta para incluir o qualificador as, assim fica claro que é o servidor de aplicação). Você pode mover a pasta extraída para qualquer lugar que você queira. Seja qual for o local, este é o que chamaremos de diretório de instalação do JBoss AS, ou JBOSS_HOME."
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> unzip jboss-6.0.*.zip\n"
-"$> mv jboss-6.0.*/ jboss-as-6.0"
+"$> unzip jboss-6.0.*.zip\n"
+"$> mv jboss-6.0.*/ jboss-as-6.0"
msgstr ""
#. Tag: para
@@ -133,7 +133,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "You're now ready to deploy your first example!"
+msgid "You're now ready to deploy your first example!"
msgstr "Agora você está pronto para implantar seu primeiro exemplo!"
#. Tag: para
@@ -144,22 +144,22 @@ msgstr "Vá para o diretório examples/jsf/numberguess e exec
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant deploy"
msgstr ""
" cd examples/jsf/numberguess\n"
"$> ant deploy]]>"
#. Tag: para
#, fuzzy, no-c-format
-msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
+msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
msgstr "Se você já não estiver, inicie o JBoss AS. Você pode também iniciar o JBoss AS a partir de um shell Linux:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/jboss-as-6.0\n"
-"$> ./bin/run.sh"
+"$> cd /path/to/jboss-as-6.0\n"
+"$> ./bin/run.sh"
msgstr ""
" cd /path/to/jboss-as-5.2\n"
"$> ./bin/run.sh]]>"
@@ -172,8 +172,8 @@ msgstr "uma janela de comandos do Windows:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
-"$> run"
+"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
+"$> run"
msgstr ""
" cd c:\\path\\to\\jboss-as-5.2\\bin\n"
"$> run]]>"
@@ -231,20 +231,20 @@ msgstr "O segundo exemplo de partida, weld-translator, traduz
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/translator\n"
-"$> ant deploy"
+"$> cd examples/jsf/translator\n"
+"$> ant deploy"
msgstr ""
" cd examples/jsf/translator\n"
"$> ant deploy]]>"
#. Tag: para
#, fuzzy, no-c-format
-msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
+msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
msgstr "O tradutor utiliza session beans, os quais estão empacotados em um módulo EJB dentro de um ear. Java EE 6 permitirá que session beans sejam implantados em módulos war, mas isto é um tópico para um capítulo posterior."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
+msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
msgstr "Novamente, aguarde uns poucos segundos para a aplicação ser implantada (se você está realmente entediado, leia as mensagens de log), e visite http://localhost:8080/weld-translator para começar a pseudo-tradução."
#. Tag: title
@@ -254,45 +254,45 @@ msgstr "Implantando no GlassFish"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
+msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
msgstr "Implantar no GlassFish deve ser fácil e familiar, certo? Afinal, é a implementação de referência da Java EE 6 e Weld é a implementação de referência da JSR-299, o que significa que o Weld vem integrado ao GlassFish. Então, sim, é tudo muito fácil e familiar."
#. Tag: para
#, fuzzy, no-c-format
-msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
+msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
msgstr "Para implantar os exemplos no GlassFish, você precisará o versão final do GlassFish V3. Selecione a versão que termina com -unix.sh ou -windows.exe de acordo com sua plataforma. Após a conclusão do download, execute o instalador. Em Linux/Unix, primeiramente, você precisará tornar o script executável."
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> chmod 755 glassfish-v3-unix.sh\n"
-"$> ./glassfish-v3-unix.sh"
+"$> chmod 755 glassfish-v3-unix.sh\n"
+"$> ./glassfish-v3-unix.sh"
msgstr ""
" chmod 755 glassfish-v3-b69-unix.sh\n"
"$> ./glassfish-v3-b69-unix.sh]]>"
#. Tag: para
#, fuzzy, no-c-format
-msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
+msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
msgstr "No Windows você pode simplesmente clicar sobre o executável. Siga as instruções no instalador. Ele criará um único domínio nomeado como domain1. Você usará este domínio para implantar os exemplos. Nós recomendamos que você escolha 7070 como a porta HTTP principal para evitar conflitos com uma instância em execução do JBoss AS (ou Apache Tomcat)."
#. Tag: para
#, fuzzy, no-c-format
-msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
+msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
msgstr "Se você tiver implantado um dos exemplos de partida, weld-numberguess ou weld-translator, no JBoss AS, então você já possui o artefato implantável que necessita. Se não, mude para qualquer um dos dois diretórios e mande construí-lo."
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
-"$> ant package"
+"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
+"$> ant package"
msgstr ""
" cd examples/jsf/numberguess (or examples/jsf/translator)\n"
"$> ant package]]>"
#. Tag: para
#, fuzzy, no-c-format
-msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
+msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
msgstr "O artefato implantável para o exemplo weld-numberguess, com o nome weld-numberguess.war, é criado no diretório target do exemplo. O arquivo para o exemplo weld-translator, com o nome weld-translator.ear, é criado no diretório ear/target do exemplo. Tudo que você precisa fazer agora é implantá-lo no GlassFish."
#. Tag: para
@@ -302,12 +302,12 @@ msgstr "Um modo para implantar aplicações no GlassFish é utilizando o asadmin start-domain domain1]]>"
#. Tag: para
#, fuzzy, no-c-format
-msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on "Applications", then click on the "Deploy..." button under the heading "Applications" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
+msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on \"Applications\", then click on the \"Deploy...\" button under the heading \"Applications\" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
msgstr "Após uns poucos segundos você pode visitar o Admin Console no navegador através da URL http://localhost:4848. Na árvore do lado esquerdo da página, clique em \"Aplicações\", depois no botão \"Implantar...\" abaixo do título \"Aplicações\" e selecione o artefato implantável para qualquer um dos dois exemplos. O implantador deve reconhecer que você selecionou um artefato Java EE e permite que você o inicie. Você pode ver os exemplos rodando em http://localhost:7070/weld-numberguess ou http://localhost:7070/weld-translator, dependendo de qual exemplo você implantou."
#. Tag: para
@@ -317,7 +317,7 @@ msgstr "Alternativamente, você pode implantar a aplicação no GlassFish utiliz
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin deploy target/weld-numberguess.war"
+msgid "$> asadmin deploy target/weld-numberguess.war"
msgstr ""
#. Tag: para
@@ -337,22 +337,22 @@ msgstr "Os contêineres servlet não são requeridos para suportar serviços Jav
#. Tag: para
#, fuzzy, no-c-format
-msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
+msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
msgstr "O Weld vem com um servlet listener que inicializa o ambiente CDI, registra o BeanManager no JNDI e oferece injeção dentro de servlets. Basicamente, ele simula um pouco do trabalho realizado pelo contêiner Java EE. (Mas você não terá funcionalidades corporativas como session beans e transações gerenciadas pelo contêiner.)"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
+msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
msgstr "Vamos colocar a extensão servlet do Weld para rodar no Apache Tomcat. Primeiro você precisará baixar o Tomcat 6.0.18 ou posterior em tomcat.apache.org, e o descompactar."
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "$> unzip apache-tomcat-6.0.18.zip"
+msgid "$> unzip apache-tomcat-6.0.18.zip"
msgstr " unzip apache-tomcat-6.0.18.zip]]>"
#. Tag: para
#, fuzzy, no-c-format
-msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
+msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
msgstr "Você possui duas opções para implantar a aplicação no Tomcat. Você pode implantá-la publicando o artefato no diretório de implantação automática usando o Ant ou você pode implantar no servidor via HTTP usando um plugin do Maven. A abordagem do Ant não requer que você tenha o Maven instalado, por isso começaremos por aí. Se você quer usar o Maven, você pode simplesmente pular esta seção."
#. Tag: title
@@ -362,7 +362,7 @@ msgstr "Implantando com o Ant"
#. Tag: para
#, fuzzy, no-c-format
-msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
+msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
msgstr "Para que o Ant coloque o artefato no diretório de implantação automática do Tomcat, ele precisa saber onde a instalação do Tomcat está localizada. Novamente, precisamos definir uma propriedade no arquivo local.build.properties dentro do diretório de exemplos do Weld obtido. Se você ainda não tiver criado este arquivo, faça isso agora. Em seguida, atribua o caminho de sua instalação do Tomcat na propriedade tomcat.home."
#. Tag: programlisting
@@ -372,7 +372,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now you're ready to deploy the numberguess example to Tomcat!"
+msgid "Now you're ready to deploy the numberguess example to Tomcat!"
msgstr "Agora você está pronto para implantar o exemplo numberguess no Tomcat!"
#. Tag: para
@@ -383,15 +383,15 @@ msgstr "Mude para o diretório examples/jsf/numberguess novam
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant tomcat.deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant tomcat.deploy"
msgstr ""
" cd examples/jsf/numberguess\n"
"$> ant tomcat.deploy]]>"
#. Tag: para
#, fuzzy, no-c-format
-msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with "tomcat."."
+msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with \"tomcat.\"."
msgstr "O script de contrução do Ant inclui alvos adicionais para o Tomcat implantar e desimplantar o arquivo no formato explodido ou empacotado. Eles possuem os mesmos nomes usados nos alvos do JBoss AS, prefixados com \"tomcat.\"."
#. Tag: para
@@ -416,14 +416,14 @@ msgstr "ant tomcat.undeploy - remove o exemplo do Tomcat"
#. Tag: para
#, fuzzy, no-c-format
-msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
+msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
msgstr "Se você já não estiver, inicie o Tomcat. Você pode também iniciar o Tomcat a partir de um shell Linux:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/apache-tomcat-6\n"
-"$> ./bin/start.sh"
+"$> cd /path/to/apache-tomcat-6\n"
+"$> ./bin/start.sh"
msgstr ""
" cd /path/to/apache-tomcat-6\n"
"$> ./bin/start.sh]]>"
@@ -431,8 +431,8 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
-"$> start"
+"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
+"$> start"
msgstr ""
" cd c:\\path\\to\\apache-tomcat-6\\bin\n"
"$> start]]>"
@@ -449,12 +449,12 @@ msgstr "Implantando com o Maven"
#. Tag: para
#, fuzzy, no-c-format
-msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
+msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
msgstr "Você também pode implantar a aplicação no Tomcat usando o Maven. Esta seção é um pouco mais avançada, portanto pule-a, a não ser que você esteja ansioso para usar o Maven nativamente. Claro, primeiro você precisará ter certeza que possui o Maven instalado em seu caminho, similar à forma que você configurou o Ant."
#. Tag: para
#, fuzzy, no-c-format
-msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
+msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
msgstr "O plugin do Maven comunica com o Tomcat via HTTP, de modo que não importa onde você instalou o Tomcat. No entanto, a configuração do plugin assume que você está rodando o Tomcat com sua configuração padrão, como localhost e na porta 8080. O arquivo readme.txt no diretório do exemplo possui informações sobre como modificar as configurações do Maven para acomodar uma configuração diferente."
#. Tag: para
@@ -463,9 +463,9 @@ msgid "To allow Maven to communicate with Tomcat over HTTP, edit the co
msgstr "Para permitir que o Maven comunique com o Tomcat via HTTP, edite o arquivo conf/tomcat-users.xml em sua instalação do Tomcat e adicione a seguinte linha:"
#. Tag: programlisting
-#, no-c-format
-msgid "<user username="admin" password="" roles="manager"/>"
-msgstr ""
+#, fuzzy, no-c-format
+msgid "<user username=\"admin\" password=\"\" roles=\"manager\"/>"
+msgstr "]]>"
#. Tag: para
#, no-c-format
@@ -474,7 +474,7 @@ msgstr "Reinicie o Tomcat. Agora você pode implantar a aplicação no Tomcat co
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
+msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
msgstr " mvn compile war:exploded tomcat:exploded -Ptomcat]]>"
#. Tag: para
@@ -484,7 +484,7 @@ msgstr "Uma vez que a aplicação está implantada, você pode reimplantá-la us
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "$> mvn tomcat:redeploy -Ptomcat"
+msgid "$> mvn tomcat:redeploy -Ptomcat"
msgstr " mvn tomcat:redeploy -Ptomcat]]>"
#. Tag: para
@@ -499,7 +499,7 @@ msgstr "Ao invés de enviar o contêiner para uma instalação standalone do Tom
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "$> mvn war:inplace tomcat:run -Ptomcat"
+msgid "$> mvn war:inplace tomcat:run -Ptomcat"
msgstr " mvn war:inplace tomcat:run -Ptomcat]]>"
#. Tag: para
@@ -509,12 +509,12 @@ msgstr "A vantagem de utilizar o servidor embutido é que as mudanças nos ativo
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "$> mvn compile war:inplace -Ptomcat"
+msgid "$> mvn compile war:inplace -Ptomcat"
msgstr " mvn compile war:inplace -Ptomcat]]>"
#. Tag: para
#, fuzzy, no-c-format
-msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
+msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
msgstr "Existem muitos outros goals do Maven que você pode usar se estiver dissecando o exemplo, o qual está documentado no arquivo readme.txt do exemplo."
#. Tag: title
@@ -529,12 +529,12 @@ msgstr "O suporte ao Jetty nos exemplos é uma adição mais recente. Já que o
#. Tag: para
#, fuzzy, no-c-format
-msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
+msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
msgstr "Se você leu toda a seção do Tomcat até o fim, então você está pronto para seguir. A execução do Maven assemelha-se à implantação embutida do Tomcat. Se não, não fique preocupado. Nós ainda iremos abordar tudo que você precisa saber novamente nesta seção."
#. Tag: para
#, fuzzy, no-c-format
-msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
+msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
msgstr "O Maven POM (pom.xml) inclui um profile nomeado jetty que ativa o plugin Maven Jetty, que você pode usar para iniciar o Jetty no modo embutido e implantar a aplicação devidamente. Você não precisa de mais nada instalado, exceto ter o comando do Maven (mvn) em seu caminho. O restante será baixado da internet quando a construção for executada."
#. Tag: para
@@ -545,8 +545,8 @@ msgstr "Para rodar o exemplo weld-numberguess no Jetty, vá p
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> mvn war:inplace jetty:run -Pjetty"
+"$> cd examples/jsf/numberguess\n"
+"$> mvn war:inplace jetty:run -Pjetty"
msgstr ""
" cd examples/jsf/numberguess\n"
"$> mvn war:inplace jetty:run -Pjetty]]>"
@@ -563,7 +563,7 @@ msgstr "Qualquer mudança nos recursos em src/main/webapp ent
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "$> mvn compile war:inplace -Pjetty"
+msgid "$> mvn compile war:inplace -Pjetty"
msgstr " mvn compile war:inplace -Pjetty]]>"
#. Tag: para
@@ -572,8 +572,8 @@ msgid "The war:inplace goal copies the compiled classes and j
msgstr "O goal war:inplace copia as classes e jars compilados dentro de src/main/webapp, nos diretórios WEB-INF/classes e WEB-INF/lib, respectivamente, misturando arquivos fontes e compilados. No entanto, o build resolve estes arquivos temporários excluindo-os do war empacotado ou limpando-os durante a fase clean do Maven."
#. Tag: para
-#, no-c-format
-msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclispe[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
+#, fuzzy, no-c-format
+msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclipse[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
msgstr "Você tem duas opções se quiser rodar o exemplo no Jetty a partir da IDE. Você pode instalar o plugin m2eclispe e executar os goals como descrito acima. Sua outra opção é iniciar o contêiner Jetty a partir de uma aplicação Java."
#. Tag: para
@@ -583,7 +583,7 @@ msgstr "Primeiro, inicialize o projeto Eclipse:"
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
+msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
msgstr " mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide]]>"
#. Tag: para
@@ -593,12 +593,12 @@ msgstr "Em seguida, monte todos os recursos necessários em src/main/we
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "$> mvn war:inplace -Pjetty-ide"
+msgid "$> mvn war:inplace -Pjetty-ide"
msgstr " mvn war:inplace -Pjetty-ide]]>"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using "Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
+msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using \"Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
msgstr "Agora você está pronto para rodar o servidor no Eclipse. Importe o projeto para seu workspace do Eclipse usando \"Import Existing Project into Workspace\". Então, encontre a start class em src/jetty/java e execute seu método main como uma Java Application. O Jetty será executado. Você pode ver a aplicação através da seguinte URL: http://localhost:8080. Preste atenção especial na porta presente na URL e a ausência de um caminho de contexto à direita."
#. Tag: para
@@ -609,9 +609,6 @@ msgstr "Agora que você possui as aplicações de partida implantadas no servido
#~ msgid "JBoss AS 5.2.0 (currently only nightly builds of JBoss AS 5.2.0.Beta1 are available),"
#~ msgstr "JBoss AS 5.2.0 (atualmente somente construções noturnas do JBoss AS 5.2.0.Beta1 estão disponíveis),"
-#~ msgid "]]>"
-#~ msgstr "]]>"
-
#~ msgid "Getting started with Web Beans, the Reference Implementation of JSR-299"
#~ msgstr "Web Beans, a Implementação de Referência da JSR-299"
diff --git a/docs/reference/src/main/docbook/pt-BR/injection.po b/docs/reference/src/main/docbook/pt-BR/injection.po
index acde21bbfb4..502945390bc 100644
--- a/docs/reference/src/main/docbook/pt-BR/injection.po
+++ b/docs/reference/src/main/docbook/pt-BR/injection.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-04-14 17:23-0300\n"
"Last-Translator: Bruno Leonardo Gonçalves \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "Injeção e pesquisa programática de dependências"
#. Tag: para
#, fuzzy, no-c-format
-msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
+msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
msgstr "Uma das características mais significativas do CDI—certamente a mais reconhecida—é injeção de dependência; desculpe-me, injeção de dependência com typesafe."
#. Tag: title
@@ -146,7 +146,7 @@ msgstr "Em seguida, o contêiner inicializa os valores de todos os campos injeta
#. Tag: para
#, fuzzy, no-c-format
-msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
+msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
msgstr "Em seguida, o contêiner chama todos os métodos inicializadores do bean (a ordem de chamada não é portável, não confie nela)."
#. Tag: para
@@ -182,7 +182,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
+msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
msgstr "Este é um caso onde a anotação @Injectnão é necessária no ponto de injeção. O mesmo é verdade para métodos observadores (os quais encontraremos no ) e métodos destruidores."
#. Tag: title
@@ -192,7 +192,7 @@ msgstr "Como as injeções são obtidas"
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
+msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
msgstr "A especificação CDI define um procedimento, chamado de resolução segura de tipos, que o contêiner segue ao indentificar o bean a ser injetado em um ponto de injeção. Este algoritmo parece complexo no início, mas uma vez quq você o entende, é realmente muito intuitivo. A resolução segura de tipos é realizada durante a inicialização do sistema, o que significa que o contêiner informará ao desenvolvedor imediatamente se alguma das dependências de um bean não puder ser satisfeita."
#. Tag: para
@@ -217,12 +217,12 @@ msgstr "permitir que os beans sejam isolados dentro de módulos separados."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
+msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
msgstr "Obviamente, se você possui exatamente um bean de um dado tipo, e um ponto de injeção com este mesmo tipo, então o bean A irá para onde pedir um A. Este é o cenário mais simples possível. Quando você começar sua aplicação, você terá provavelmente vários desses."
#. Tag: para
#, fuzzy, no-c-format
-msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
+msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
msgstr "Mas então, as coisas começam a ficar complicadas. Vamos explorar como o contêiner determina qual bean injetar em casos mais avançados. Nós iniciaremos dando um olhar mais atento em qualificadores."
#. Tag: title
@@ -382,7 +382,7 @@ msgstr "Se um campo injetado ou um parâmetro de um construtor de bean ou métod
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now, you may be thinking, "What's the different between using a qualifier and just specifying the exact implementation class you want?" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alterative implementations of @Asynchronous PaymentProcessor!"
+msgid "Now, you may be thinking, \"What's the different between using a qualifier and just specifying the exact implementation class you want?\" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alternative implementations of @Asynchronous PaymentProcessor!"
msgstr "Agora, você pode estar pensando, \"Qual a diferença entre usar um qualificador e apenas especificar a exata classe de implementação que você deseja?\" É importante entender que um qualificador é como uma extensão da interface. Ele não cria uma dependência direta para qualquer implementação em particular. Podem existir várias implementações alternativas de @Asynchronous PaymentProcessor!"
#. Tag: title
@@ -392,7 +392,7 @@ msgstr "Os qualificadores embutidos @Default e @Any<
#. Tag: para
#, fuzzy, no-c-format
-msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to decare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
+msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to declare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
msgstr "Sempre que um bean ou ponto de injeção não declara explicitamente um qualificador, o contêiner assume o qualificador @Default. Em algum momento, você precisará declarar um ponto de injeção sem especificar um qualificador. Existe um qualificador para isso também. Todos os beans possuem o qualificador @Any. Portanto, ao especificar explicitamente @Any em um ponto de injeção, você suprime o qualificador padrão, sem restringir os beans que são elegíveis para injeção."
#. Tag: para
@@ -404,7 +404,7 @@ msgstr "Isto é especialmente útil se você quiser iterar sobre todos os beans
#, fuzzy, no-c-format
msgid ""
"@Inject \n"
-"void initServices(@Any Instance<Service> services) { \n"
+"void initServices(@Any Instance<Service> services) { \n"
" for (Service service: services) {\n"
" service.init();\n"
" }\n"
@@ -445,8 +445,8 @@ msgstr ""
"}]]>"
#. Tag: para
-#, no-c-format
-msgid "Then we select one of the possible member values when appling the qualifier:"
+#, fuzzy, no-c-format
+msgid "Then we select one of the possible member values when applying the qualifier:"
msgstr "Então selecionamos um dos possíveis valores do membro ao aplicar o qualificador:"
#. Tag: programlisting
@@ -467,7 +467,7 @@ msgid ""
"@Target({METHOD, FIELD, PARAMETER, TYPE})\n"
"public @interface PayBy {\n"
" PaymentMethod value();\n"
-" @Nonbinding String comment() default "";\n"
+" @Nonbinding String comment() default \"\";\n"
"}"
msgstr ""
"@Alternative estão desabil
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <alternatives>\n"
-" <class>org.mycompany.mock.MockPaymentProcessor</class>\n"
-" </alternatives>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <alternatives>\n"
+" <class>org.mycompany.mock.MockPaymentProcessor</class>\n"
+" </alternatives>\n"
+"</beans>"
msgstr ""
"@Alternative beans that are trying
msgstr "desabilite um dos beans @Alternative que estão tentando ocupar o mesmo espaço, usando beans.xml."
#. Tag: para
-#, no-c-format
-msgid "See this FAQ for step-by-step instructions for how to resolve an ambigous resolution exception between a raw bean type and a producer method that returns the same bean type."
+#, fuzzy, no-c-format
+msgid "See this FAQ for step-by-step instructions for how to resolve an ambiguous resolution exception between a raw bean type and a producer method that returns the same bean type."
msgstr "Veja este FAQ para instruções passo-a-passo de como resolver uma exceção de resolução ambígua entre um tipo de bean e um método produtor que retorna o mesmo tipo de bean."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Just remember: "There can be only one.""
+msgid "Just remember: \"There can be only one.\""
msgstr "Apenas lembre-se: \"Só pode haver um.\""
#. Tag: para
#, fuzzy, no-c-format
-msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
+msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
msgstr "Por outro lado, se você realmente tem um ponto de injeção opcional ou multivalorado, você deveria mudar o tipo de seu ponto de injeção para Instance, como veremos na ."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
+msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
msgstr "Agora há mais uma questão que você precisa estar ciente quando usar o serviço de injeção de dependência."
#. Tag: title
@@ -661,7 +661,7 @@ msgstr "Os clientes de um bean injetado não costumam manter uma referência dir
#. Tag: para
#, fuzzy, no-c-format
-msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
+msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
msgstr "Imagine que um bean vinculado ao escopo da aplicação mantenha uma referência direta para um bean vinculado ao escopo da solicitação. O bean com escopo de aplicação é compatilhado entre várias solicitações diferentes. No entanto, cada solicitação deverá ver uma instância diferente do bean com escopo de solicitação—a atual!"
#. Tag: para
@@ -686,7 +686,7 @@ msgstr "Os seguintes tipos Java não podem ser \"proxied\" pelo contêiner:"
#. Tag: para
#, fuzzy, no-c-format
-msgid "classes which don't have a non-private constructor with no parameters, and"
+msgid "classes which don't have a non-private constructor with no parameters, and"
msgstr "classes que não possuem um construtor não privado sem parâmetros, e"
#. Tag: para
@@ -701,7 +701,7 @@ msgstr "arrays e tipos primitivos."
#. Tag: para
#, fuzzy, no-c-format
-msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
+msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
msgstr "Geralmente é muito fácil de corrigir um problema de dependência com proxies. Se um ponto de injeção do tipo X resulta em uma dependência que não pode ser feito um proxy, simplesmente:"
#. Tag: para
@@ -711,7 +711,7 @@ msgstr "adicione um construtor sem parâmetros em X,"
#. Tag: para
#, fuzzy, no-c-format
-msgid "change the type of the injection point to Instance<X>,"
+msgid "change the type of the injection point to Instance<X>,"
msgstr "modifique o tipo do ponto de injeção para Instance<X>,"
#. Tag: para
@@ -741,7 +741,7 @@ msgstr "IBM, JRockit: ReflectionFactory.newConstructorForSerialization(
#. Tag: para
#, fuzzy, no-c-format
-msgid "But we didn't get around to implementing this yet."
+msgid "But we didn't get around to implementing this yet."
msgstr "Mas não somos obrigados a implementar isto ainda."
#. Tag: title
@@ -776,7 +776,7 @@ msgstr "Nestas situações, a aplicação pode obter uma instância da interface
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
msgstr " paymentProcessorSource;]]>"
#. Tag: para
@@ -811,7 +811,7 @@ msgstr "Especificar os qualificadores no ponto de injeção é muito, muito mais
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
msgstr " paymentProcessorSource;]]>"
#. Tag: para
@@ -826,21 +826,21 @@ msgstr "Alternativamente, podemos especificar o qualificador dinamicamente. Prim
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
msgstr " paymentProcessorSource;]]>"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Next, we need to obtain an instance of our qualifier type. Since annotatons are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
+msgid "Next, we need to obtain an instance of our qualifier type. Since annotations are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
msgstr "Em seguida, precisamos obter uma instância de nosso tipo de qualificador. Uma vez que anotações são interfaces, não podemos apenas escrever new Asynchronous(). Também é bastante tedioso criar uma implementação concreta de um tipo de anotação a partir do zero. Em vez disso, o CDI nos permite obter uma instância do qualificador criando uma subclasse da classe auxiliar AnnotationLiteral."
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"abstract class AsynchronousQualifier\n"
-"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
+"class AsynchronousQualifier\n"
+"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
msgstr ""
-" implements Asynchronous {}]]>"
#. Tag: para
@@ -852,14 +852,14 @@ msgstr "E alguns casos, podemos utilizar uma classe anônima:"
#, fuzzy, no-c-format
msgid ""
"PaymentProcessor p = paymentProcessorSource\n"
-" .select(new AnnotationLiteral<Asynchronous>() {});"
+" .select(new AnnotationLiteral<Asynchronous>() {});"
msgstr ""
"() {});]]>"
#. Tag: para
#, fuzzy, no-c-format
-msgid "We can't use an anonymous class to implement a qualifier type with members."
+msgid "However, we can't use an anonymous class to implement a qualifier type with members."
msgstr "Não podemos utilizar uma classe anônima para implementar um tipo de qualificador com membros."
#. Tag: para
@@ -910,7 +910,7 @@ msgstr "Um bean com escopo @Dependent pode injetar uma instâ
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
+msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
msgstr "Vejamos um exemplo. O seguinte código é prolixo e vulnerável a problemas de refatoração:"
#. Tag: programlisting
@@ -954,7 +954,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
+msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
msgstr "Não está convencido? Então aqui está um segundo exemplo. Para injetar parâmetros HTTP, precisamos definir um tipo de qualificador:"
#. Tag: programlisting
@@ -982,8 +982,8 @@ msgstr "Gostaríamos de usar este tipo de qualificador em pontos de injeção do
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@HttpParam("username") String username;\n"
-"@HttpParam("password") String password;"
+"@HttpParam(\"username\") String username;\n"
+"@HttpParam(\"password\") String password;"
msgstr ""
""
@@ -998,7 +998,7 @@ msgstr "O seguinte método produtor faz o trabalho:"
msgid ""
"class HttpParams\n"
"\n"
-" @Produces @HttpParam("")\n"
+" @Produces @HttpParam(\"\")\n"
" String getParamValue(InjectionPoint ip) {\n"
" ServletRequest request = (ServletRequest) FacesContext.getCurrentInstance().getExternalContext().getRequest();\n"
" return request.getParameter(ip.getAnnotated().getAnnotation(HttpParam.class).value());\n"
@@ -1016,8 +1016,8 @@ msgstr ""
"}]]>"
#. Tag: para
-#, no-c-format
-msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own prodcuer for the request and have it injected as a method parameter."
+#, fuzzy, no-c-format
+msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own producer for the request and have it injected as a method parameter."
msgstr "Observe que a aquisição da solicitação neste exemplo é centrada em JSF. Para uma solução mais genérica você pode escrever seu próprio produtor para a solicitação e a injetar como um parâmetro do método."
#. Tag: para
@@ -1035,8 +1035,8 @@ msgstr "O contêiner fornece um bean embutido que implementa a interface \n"
"Language-Team: none\n"
@@ -110,7 +110,7 @@ msgstr "Bindings de interceptadores"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
+msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
msgstr "Suponha que queremos declarar que algum de nossos beans são transacionais. A primeira coisa de que precisamos é um tipo vinculador de interceptador para especificar exatamente em quais beans estamos interessados:"
#. Tag: programlisting
@@ -163,7 +163,7 @@ msgstr "Implementando interceptadores (interceptors)"
#. Tag: para
#, fuzzy, no-c-format
-msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
+msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
msgstr "Isto é ótimo, mas em algum momento teremos que implementar o interceptador que fornece este aspecto de gerenciamento transacional. Tudo que precisamos fazer é criar um interceptador normal, e anotá-lo com @Interceptor e @Transactional."
#. Tag: programlisting
@@ -227,16 +227,16 @@ msgstr "Por padrão, todos os interceptadores estão desabilitados. Nós precisa
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
"meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
+msgid "Well, fortunately, CDI works around this missing feature of Java. We may annotate one interceptor binding type with other interceptor binding types (termed a meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
msgstr "Bem, felizmente, CDI contorna a falta desta funcionalidade em Java. Podemos anotar um tipo vinculador com outros tipos vinculadores de interceptadores (denominado como uma meta-anotação). As vinculações de interceptadores são transitivos — qualquer bean com o primeiro vínculo a um interceptador herda os vínculos a interceptadores declarados como meta-anotações."
#. Tag: programlisting
@@ -557,7 +557,7 @@ msgstr "os interceptadores podem não ser facilmente disabilitados em tempo de i
#. Tag: para
#, fuzzy, 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."
+msgid "the interceptor ordering is non-global — it is determined by the order in which interceptors are listed at the class level."
msgstr "a ordem dos interceptadores não é global — ela é determinada pela ordem em que os interceptadores são listados a nível de classe."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pt-BR/intro.po b/docs/reference/src/main/docbook/pt-BR/intro.po
index cb51ed9ec9a..0067238a596 100644
--- a/docs/reference/src/main/docbook/pt-BR/intro.po
+++ b/docs/reference/src/main/docbook/pt-BR/intro.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-04-14 14:18-0300\n"
"Last-Translator: Bruno Leonardo Gonçalves \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "Introdução"
#. Tag: para
#, fuzzy, no-c-format
-msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
+msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
msgstr "Então você está interessado em começar a escrever seu primeiro bean? Ou talvez você seja cético, imaginando que tipos de argolas a especificação CDI fará com que você atravesse! A boa notícia é que você provavelmente já escreveu e utilizou centenas, talvez milhares de beans. CDI apenas facilita a realmente utilizá-los para construir uma aplicação!"
#. Tag: title
@@ -36,27 +36,27 @@ msgstr "Um bean é exatamente o que você pensa que é. Só que agora ele tem um
#. Tag: para
#, fuzzy, no-c-format
-msgid "Prior to Java EE 6, there was no clear definition of the term "bean" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications "beans" for years. There were even a couple of different kinds of things called "beans" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a "bean". What we've been missing is a common definition."
+msgid "Prior to Java EE 6, there was no clear definition of the term \"bean\" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications \"beans\" for years. There were even a couple of different kinds of things called \"beans\" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a \"bean\". What we've been missing is a common definition."
msgstr "Antes do Java EE 6, não havia uma definição clara do termo \"bean\" na plataforma Java EE. Claro, nós fomos chamando as classes Java usadas em aplicações web e corporativas de \"beans\" por anos. Houveram até um tanto de diferentes tipos de coisas chamados de \"bean\" em especificações EE, incluindo os beans do EJB e os managed beans do JSF. Entretanto, outros frameworks de terceiros como Spring e Seam introduziram suas próprias ideias do que significava ser um \"bean\". O que está faltando é uma definição comum."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
+msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
msgstr "Java EE 6, finalmente, estabelece que a definição comum está na especificação de Managed Beans. Managed Beans são definidos como objetos gerenciados pelo contêiner com mínimas restrições de programação, também conhecidos pelo acrônimo POJO (Plain Old Java Object). Eles suportam um pequeno conjunto de serviços básicos, como injeção de recurso, callbacks e interceptadores do ciclo de vida. Especificações complementares, tais como EJB e CDI, se estabelecem sobre este modelo básico. Porém, afinal, existe um conceito uniforme de um bean e um modelo de componente enxuto que está alinhado através da plataforma Java EE."
#. Tag: para
#, fuzzy, no-c-format
-msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
+msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
msgstr "Com pouquíssimas exceções, quase toda classe Java concreta que possui um construtor com nenhum parâmetro (ou um construtor designado com a anotação @Inject) é um bean. Isso inclui qualquer JavaBean e qualquer EJB session bean. Se você já possui alguns JavaBeans ou session beans, eles já são beans—você não vai precisar de qualquer metadado especial adicional. Há apenas uma pequena coisa que você precisa fazer antes de começar a injetá-los dentro das coisas: você precisa colocá-los em um arquivo (um jar ou um módulo Java EE, como um war ou um jar EJB) que contém um arquivo indicador especial: META-INF/beans.xml."
#. Tag: para
#, fuzzy, no-c-format
-msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
+msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
msgstr "Os JavaBeans e EJBs que você tem escrito todo dia, até agora, não foram capazes de tirar proveito dos novos serviços definidos pela especificação CDI. Mas você será capaz de usar cada um deles com CDI—permitindo que o contêiner crie e destrua instâncias de seus beans e associando-os a um contexto designado, injetando-os dentro de outros beans, usando-os em expressões EL, especializando-os com anotações qualificadoras, até adicionando interceptadores e decoradores para eles—sem modificar seu código existente. No máximo, você precisará adicionar algumas anotações."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now let's see how to create your first bean that actually uses CDI."
+msgid "Now let's see how to create your first bean that actually uses CDI."
msgstr "Agora vamos ver como criar seu primeiro bean que realmente utiliza CDI."
#. Tag: title
@@ -66,14 +66,14 @@ msgstr "Arregaçando as mangas"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
+msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
msgstr "Suponha que temos duas classes Java existentes, que estamos utilizando durante anos em várias aplicações. A primeira classe divide uma string em uma lista de sentenças:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
"public class SentenceParser {\n"
-" public List<String> parse(String text) { ... }\n"
+" public List<String> parse(String text) { ... }\n"
"}"
msgstr ""
"TextTranslator não tem um construtor sem
#. Tag: para
#, fuzzy, no-c-format
-msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
+msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
msgstr "Como você imaginou, a anotação @Inject tem algo a ver com injeção de dependencia! @Inject pode ser aplicada a um construtor ou a um método de um bean, e diz ao contêiner para chamar este construtor ou este método ao instanciar o bean. O contêiner injetará outros beans nos parâmetros do construtor ou do método."
#. Tag: para
@@ -179,7 +179,7 @@ msgstr "Podemos obter uma instância de TextTranslator injeta
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
+msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
msgstr "Vamos criar um bean controlador de UI que utiliza injeção em campo para obter uma instância de TextTranslator, traduzindo o texto digitado por um usuário:"
#. Tag: programlisting
@@ -242,7 +242,7 @@ msgstr "Injeção de uma instância de TextTranslator em um c
#. Tag: para
#, fuzzy, no-c-format
-msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
+msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
msgstr "Observe que o bean controlador tem escopo de solicitação e é nomeado. Uma vez que esta combinação é tão comum em aplicações web uma anotação embutida para isto em CDI, que poderíamos ter utilizada como um atalho. Quando a anotação (estereótipo) @Model é declarada sobre uma classe, cria-se um bean com escopo de solicitação e nomeado."
#. Tag: para
@@ -253,7 +253,7 @@ msgstr "Alternativamente, podemos obter e injetar uma instância de Tex
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
+"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
"...\n"
"public void translate() {\n"
" textTranslatorInstance.get().translate(inputText);\n"
@@ -267,15 +267,15 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
+msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
msgstr "Repare que não é necessário criar um método getter ou setter para injetar um bean dentro de outro. CDI pode acessar um campo injetado diretamente (mesmo se ele for privado!), que algumas vezes ajuda a eliminar algum código supérfluo. O nome do campo é arbitrário. É o tipo do campo que determina o que é injetado."
#. Tag: para
#, fuzzy, no-c-format
-msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
+msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
msgstr "Durante a inicialização do sistema, o contêiner deve validar que existe exatamente um bean que satisfaça cada ponto de injeção. Em nosso exemplo, se nenhuma implementação de Translator está disponível—se o EJB SentenceTranslator não foi implantado—o contêiner iria nos informar sobre uma dependência não satisfeita. Se mais de uma implementação de Translator estivessem disponíveis, o contêiner iria nos informar sobre a dependência ambígua."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
+msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
msgstr "Antes de aprofundarmos nos detalhes, vamos fazer uma pausa e examinar a anatomia de um bean. Que aspectos do bean são significantes e o que lhe confere sua identidade? Em vez de apenas dar exemplos de beans, vamos definir o que torna algo um bean."
diff --git a/docs/reference/src/main/docbook/pt-BR/next.po b/docs/reference/src/main/docbook/pt-BR/next.po
index 25eee9aa120..7dab130cefa 100644
--- a/docs/reference/src/main/docbook/pt-BR/next.po
+++ b/docs/reference/src/main/docbook/pt-BR/next.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-12-19 17:59-0300\n"
"Last-Translator: João Paulo Viragine \n"
"Language-Team: none\n"
@@ -21,12 +21,12 @@ msgstr "Próximos passos"
#. Tag: para
#, no-c-format
-msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
+msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
+msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
msgstr "A implementação de referência da CDI (CDI RI) está sendo desenvolvida em http://seamframework.org/Weld. O blog do time de desenvolvimento da implementação de referência (RI) e do líder da especificação da CDI em: http://in.relation.to. Esse guia foi originalmente baseado em uma série de entradas de blogs publicados lá enquando a especificação estava sendo desenvolvida. Esse é provavelmente a melhor fonte de informação sobre o futuro da CDI, Weld e Seam."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pt-BR/part1.po b/docs/reference/src/main/docbook/pt-BR/part1.po
index 060aa7421fe..cc0b559c042 100644
--- a/docs/reference/src/main/docbook/pt-BR/part1.po
+++ b/docs/reference/src/main/docbook/pt-BR/part1.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-04-14 14:13-0300\n"
"Last-Translator: Bruno Leonardo Gonçalves \n"
"Language-Team: none\n"
@@ -126,7 +126,7 @@ msgstr "Eu preciso explicitamente destruí-lo?"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Where should I keep the reference to it when I'm not currently using it?"
+msgid "Where should I keep the reference to it when I'm not currently using it?"
msgstr "Onde devo manter referência a ele quando não estiver usando-o diretamente?"
#. Tag: para
@@ -141,7 +141,7 @@ msgstr "Como devo proceder no compartilhamento deste objeto com outros objetos?"
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
+msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
msgstr "CDI é mais do que um framework. É um completo e rico modelo de programação. O tema de CDI é baixo acoplamento com tipagem forte. Vamos estudar o que esta frase significa."
#. Tag: para
@@ -171,12 +171,12 @@ msgstr "decoradores permitem que questões de negócios sej
#. Tag: para
#, fuzzy, no-c-format
-msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
+msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
msgstr "O que é ainda mais poderoso (e confortável) é que CDI oferece todas essas facilidades de uma maneira typesafe. CDI nunca confia em identificadores baseados em strings para determinar como os objetos se relacionam. Em vez disso, CDI utiliza a informação de tipagem que já está disponível no modelo de objeto Java, aumentada com um novo padrão de programação, chamada de anotações qualificadoras, para unir os beans, suas dependências, seus interceptadores e decoradores, e seus consumidores de eventos. A utilização de descritores XML é minimizada para simplesmente informação específica de implantação."
#. Tag: para
#, fuzzy, no-c-format
-msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
+msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
msgstr "Mas CDI não é um modelo de programação restritivo. Ele não diz como você deve estruturar sua aplicação em camadas, como você deve lidar com a persistência, ou qual framework web você tem que usar. Você terá que decidir esses tipos de coisas por conta própria."
#. Tag: para
@@ -186,7 +186,7 @@ msgstr "CDI ainda provê um SPI abrangente, permitindo que outros tipos de objet
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
+msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
msgstr "A CDI foi influenciada por inúmeros frameworks Java existentes, incluindo Seam, Guice e Spring. Entretanto, CDI tem suas próprias e bem distintas características: mais typesafe que o Seam, mais stateful e menos centrada em XML que o Spring, mais hábil em aplicações web e corporativas que o Guice. Mas poderia ter sido nada disso sem a inspiração vinda dos frameworks mencionados e a grande quantidade de colaboração e trabalho duro do JSR-299 Expert Group (EG)."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pt-BR/part3.po b/docs/reference/src/main/docbook/pt-BR/part3.po
index fea666f6441..32011b95f8b 100644
--- a/docs/reference/src/main/docbook/pt-BR/part3.po
+++ b/docs/reference/src/main/docbook/pt-BR/part3.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-11-11 23:05-0300\n"
"Last-Translator: Bruno Leonardo Gonçalves \n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
+msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
msgstr "O primeiro grande tema de CDI é baixo acoplamento. Já vimos três meios de alcançar baixo acoplamento:"
#. Tag: para
@@ -71,7 +71,7 @@ msgstr "O segundo grande tema da CDI é a tipificação forteestereótipos CDI levam essa idéia um pouco mai
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
+msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
msgstr "Nós agora estamos prontos para verificar mais algumas funcionalidades avançadas de CDI. Tenha em mente que essas funcionalidades existem para tornar nosso código fácil para validar e, ao mesmo tempo, mais fácil de entender. Na maioria das vezes você nem precisa se preocupar em utilizar essas funcionalidades, mas se forem fáceis de usar, você apreciará seu poder."
#~ msgid "Even Web Beans XML metadata is strongly typed! There's no compiler for XML, so Web Beans takes advantage of XML schemas to validate the Java types and attributes that appear in XML. This approach turns out to make the XML more literate, just like annotations made our Java code more literate."
diff --git a/docs/reference/src/main/docbook/pt-BR/part4.po b/docs/reference/src/main/docbook/pt-BR/part4.po
index 3f62805f4af..cc1b793b39f 100644
--- a/docs/reference/src/main/docbook/pt-BR/part4.po
+++ b/docs/reference/src/main/docbook/pt-BR/part4.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-04-10 20:34-0300\n"
"Last-Translator: João Paulo Viragine \n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
+msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
msgstr ""
#. Tag: para
@@ -26,7 +26,7 @@ msgstr "Nós já vimos como Web Beans ajuda a integrar EJB e JSF, permitindo que
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
+msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
msgstr "Estamos prestes a ver como tirar o máximo proveito da plataforma Java EE em uma aplicação que utiliza Web Beans. Reuniremos, brevemente, um conjunto de SPIs que são fornecidas para suportar extensões portáveis para Web Beans. Talvez você nunca precisará usar essas SPIs diretamente, mas é bom saber que estão lá se você precisar delas. Mais importante: você tirará proveito delas indiretamente, toda vez que você utilizar uma extensão de terceiros."
#~ msgid "The third theme of Web Beans is integration. Web Beans was designed to work in concert with other technologies, helping the application developer fit the other technologies together. Web Beans is an open technology. It forms a part of the Java EE ecosystem, and is itself the foundation for a new ecosystem of portable extensions and integration with existing frameworks and technologies."
diff --git a/docs/reference/src/main/docbook/pt-BR/part5.po b/docs/reference/src/main/docbook/pt-BR/part5.po
index edc8e41b1dd..412e7e03c90 100644
--- a/docs/reference/src/main/docbook/pt-BR/part5.po
+++ b/docs/reference/src/main/docbook/pt-BR/part5.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-04-10 15:56-0300\n"
"Last-Translator: João Paulo Viragine \n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and Glassfish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
+msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and GlassFish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
msgstr "Web Beans é a implementação de referência da JSR-299 e é utilizada pelo JBoss AS e pelo Glassfish para prover serviços JSR-299 para aplicações Java Enterprise Edition. Web Beans vai além dos ambientes e APIs definidos pela especificação JSR-299 e fornece suporte a uma série de outros ambientes (tais como um servlet container como o Tomcat, ou o Java SE) e APIs e módulos adicionais (como logging, geração de XSD para os descritores de implantação XML da JSR-299)."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pt-BR/producermethods.po b/docs/reference/src/main/docbook/pt-BR/producermethods.po
index 581f4e13e78..f936375dd8d 100644
--- a/docs/reference/src/main/docbook/pt-BR/producermethods.po
+++ b/docs/reference/src/main/docbook/pt-BR/producermethods.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-11-11 23:43-0300\n"
"Last-Translator: Bruno Leonardo Gonçalves \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "Métodos produtores"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
+msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
msgstr "Métodos produtores permitem superarmos certas limitações que surgem quando um contêiner, em vez da aplicação, é responsável por instanciar objetos. Eles são também a forma mais fácil de integrar os objetos que não são beans ao ambiente CDI."
#. Tag: para
@@ -76,7 +76,7 @@ msgstr "varia a implementação de um tipo de bean em tempo de execução."
#. Tag: para
#, fuzzy, no-c-format
-msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
+msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
msgstr "Em particular, métodos produtores permitem-nos utilizar polimorfismo em tempo de execução com CDI. Como vimos, os beans alternativos são uma solução para o problema do polimorfismo em tempo de implantação. Mas, uma vez que o sistema está implantado, a implementação do CDI é imutável. Um método produtor não tem essa limitação:"
#. Tag: programlisting
@@ -157,7 +157,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
+msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
msgstr "Agora, quando o método produtor é chamado, o PaymentStrategy retornado será associado ao contexto de sessão. O método produtor não será invocado novamente na mesma sessão."
#. Tag: para
@@ -172,12 +172,12 @@ msgstr "Injeção em métodos produtores"
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
+msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
msgstr "Existe um problema potencial com o código acima. As implementações de CreditCardPaymentStrategy são instanciadas utilizando o operador new de Java. Objetos instanciados diretamente pela aplicação não usufruem da injeção de dependência e não possuem interceptadores."
#. Tag: para
#, fuzzy, no-c-format
-msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
+msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
msgstr "Se não é isso o que queremos, podemos utilizar a injeção de dependência no método produtor para obter instâncias do bean:"
#. Tag: programlisting
@@ -209,12 +209,12 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of "promoting" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left "hanging" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
+msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of \"promoting\" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left \"hanging\" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
msgstr "Espere, o que ocorre se CreditCardPaymentStrategy for um bean com escopo de requisição? Assim o método produtor tem o efeito de \"promover\" a instância atual com escopo de requisição para escopo de sessão. Isso certamente é um erro! O objeto com escopo de requisição será destruído pelo contêiner antes de terminar a sessão, mas a referência ao objeto será deixada \"presa\" ao escopo de sessão. Esse erro não será detectado pelo contêiner. Por isso, tome cuidado adicional ao retornar instâncias de bean em métodos produtores!"
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
+msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
msgstr "Existem pelo menos três maneiras de corrigirmos esse problema. Podemos alterar o escopo da implementação de CreditCardPaymentStrategy, mas isso poderia afetar outros clientes desse bean. A mehor opção seria alterar o escopo do método produtor para @Dependent ou @RequestScoped."
#. Tag: para
@@ -261,7 +261,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
+msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
msgstr "Assim a nova instância dependente de CreditCardPaymentStrategy será criada, passada para o método produtor, retornada pelo método produtor e, finalmente, associada ao contexto de sessão. O objeto dependente não será destruído até que o objeto Preferences seja destruído, ao término da sessão."
#. Tag: title
diff --git a/docs/reference/src/main/docbook/pt-BR/resources.po b/docs/reference/src/main/docbook/pt-BR/resources.po
index b8f94dd8501..5dc3893bf86 100644
--- a/docs/reference/src/main/docbook/pt-BR/resources.po
+++ b/docs/reference/src/main/docbook/pt-BR/resources.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-12-19 18:06-0300\n"
"Last-Translator: João Paulo Viragine \n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a nonportable "mapped name"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
+msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a non-portable \"mapped name\"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
msgstr ""
#. Tag: para
@@ -72,7 +72,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Produces @WebServiceRef(lookup="java:app/service/Catalog")\n"
+"@Produces @WebServiceRef(lookup=\"java:app/service/Catalog\")\n"
"Catalog catalog;"
msgstr ""
"@Alternative."
+msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
msgstr ""
#. Tag: title
@@ -181,7 +181,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
+msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
msgstr ""
#. Tag: programlisting
@@ -195,9 +195,9 @@ msgid "instead of"
msgstr ""
#. Tag: programlisting
-#, no-c-format
-msgid "@PersistenceContext(unitName="CustomerDatabase") EntityManager"
-msgstr ""
+#, fuzzy, no-c-format
+msgid "@PersistenceContext(unitName=\"CustomerDatabase\") EntityManager"
+msgstr ""
#. Tag: para
#, no-c-format
diff --git a/docs/reference/src/main/docbook/pt-BR/ri-spi.po b/docs/reference/src/main/docbook/pt-BR/ri-spi.po
index 97db11cf90a..778c64decb2 100644
--- a/docs/reference/src/main/docbook/pt-BR/ri-spi.po
+++ b/docs/reference/src/main/docbook/pt-BR/ri-spi.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-12-19 18:04-0300\n"
"Last-Translator: João Paulo Viragine \n"
"Language-Team: none\n"
@@ -31,7 +31,7 @@ msgstr "Carregando recursos"
#. Tag: para
#, no-c-format
-msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the "Weld: Servlets" extension will be sufficient, and will work in any container supporting the Servlet API."
+msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the \"Weld: Servlets\" extension will be sufficient, and will work in any container supporting the Servlet API."
msgstr ""
#. Tag: para
@@ -56,7 +56,7 @@ msgstr "Todas as interfaces na SPI suportam o padrão decorador e fornecem a cla
#. Tag: para
#, no-c-format
-msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
+msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
msgstr ""
#. Tag: para
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
+msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
msgstr ""
#. Tag: para
@@ -96,7 +96,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
+msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
msgstr ""
#. Tag: para
@@ -106,12 +106,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
+msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
+msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
msgstr ""
#. Tag: para
@@ -126,7 +126,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
+msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
msgstr ""
#. Tag: para
@@ -156,7 +156,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
+msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
msgstr ""
#. Tag: para
@@ -196,7 +196,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
+msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
msgstr ""
#. Tag: title
@@ -211,7 +211,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
+msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
msgstr ""
#. Tag: para
@@ -276,7 +276,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); intercepter will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
+msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); interceptor will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
msgstr ""
#. Tag: para
@@ -351,7 +351,7 @@ msgstr "O contexto de aplicação"
#. Tag: para
#, no-c-format
-msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
+msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
msgstr ""
#. Tag: title
@@ -366,7 +366,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programtically, or built in). Bean validation will validate all beans."
+msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programmatically, or built in). Bean validation will validate all beans."
msgstr ""
#. Tag: para
@@ -426,7 +426,7 @@ msgstr "Isolamento de Classloader (Classloader isolation)"
#. Tag: para
#, no-c-format
-msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuation, classloader isolation for each CDI application."
+msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuration, classloader isolation for each CDI application."
msgstr ""
#. Tag: term
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You must ensure that that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
+msgid "You must ensure that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
msgstr ""
#. Tag: term
@@ -582,7 +582,7 @@ msgid ""
"InjectionTarget it = weldBeanManager.fireProcessInjectionTarget(clazz);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
+"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
"\n"
"// Produce the instance, performing any constructor injection required\n"
"Object instance = it.produce();\n"
@@ -638,16 +638,16 @@ msgstr ""
msgid ""
"// Obtain the EjbDescriptor for the EJB\n"
"// You may choose to use this utility method to get the descriptor\n"
-"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
+"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
"\n"
"// Get an the Bean object\n"
-"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
+"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
"\n"
"// Create the injection target\n"
"InjectionTarget it = deploymentBeanManager.createInjectionTarget(ejbDescriptor);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
+"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
"\n"
"// Perform injection and call initializers\n"
"it.inject(instance, cc);\n"
diff --git a/docs/reference/src/main/docbook/pt-BR/scopescontexts.po b/docs/reference/src/main/docbook/pt-BR/scopescontexts.po
index 50de481ba64..3c287a373c0 100644
--- a/docs/reference/src/main/docbook/pt-BR/scopescontexts.po
+++ b/docs/reference/src/main/docbook/pt-BR/scopescontexts.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-04-14 17:27-0300\n"
"Last-Translator: Bruno Leonardo Gonçalves \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "Escopos e contextos"
#. Tag: para
#, fuzzy, no-c-format
-msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
+msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
msgstr "Até agora, vimos alguns exemplos de anotações de tipo de escopo. O escopo de um bean determina o ciclo de vida das instâncias do bean. O escopo também determina que clientes se referem a quais instâncias do bean. De acordo com a especificação CDI, um escopo determina:"
#. Tag: para
@@ -46,7 +46,7 @@ msgstr "Por exemplo, se temos um bean com escopo de sessão CurrentUser
#. Tag: para
#, fuzzy, no-c-format
-msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
+msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
msgstr "Entidades JPA não se encaixam muito bem nesse modelo. Entidades possuem seu próprio ciclo de vida e modelo de identidade que não pode ser mapeado adequadamente para o modelo utilizado em CDI. Portanto, não recomendamos o tratamento de entidades como beans CDI. Você certamente vai ter problemas se tentar dar a uma entidade um escopo diferente do escopo padrão @Dependent. O proxy cliente irá atrapalhar se você tentar passar uma instância injetada para o EntityManager do JPA."
#. Tag: title
@@ -56,7 +56,7 @@ msgstr "Tipos de escopo"
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
+msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
msgstr "CDI possui um modelo extensível de contexto. É possível definir novos escopos, criando uma nova anotação de tipo de escopo:"
#. Tag: programlisting
@@ -74,7 +74,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
+msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
msgstr "Evidentemente, essa é a parte mais fácil do trabalho. Para esse tipo de escopo ser útil, nós também precisamos definir um objeto Context que implementa o escopo! Implementar um Context é geralmente uma tarefa muito técnica, destinada apenas ao desenvolvimento do framework. Você pode esperar uma implementação do escopo de negócio, por exemplo, em uma versão futura do Seam."
#. Tag: para
@@ -93,7 +93,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Usually, you'll use one of CDI's built-in scopes."
+msgid "Usually, you'll use one of CDI's built-in scopes."
msgstr "Normalmente, você usará um dos escopos pré-definidos do CDI."
#. Tag: title
@@ -193,7 +193,7 @@ msgstr "Os managed beans com escopo @SessionScoped ou Add Product]]>"
#. Tag: para
#, fuzzy, no-c-format
-msgid "It's probably better to use one of the link components in JSF 2:"
+msgid "It's probably better to use one of the link components in JSF 2:"
msgstr "É provavelmente melhor usar um dos componentes de link em JSF 2:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:link outcome="/addProduct.xhtml" value="Add Product">\n"
-" <f:param name="cid" value="#{javax.enterprise.context.conversation.id}"/>\n"
-"</h:link>"
+"<h:link outcome=\"/addProduct.xhtml\" value=\"Add Product\">\n"
+" <f:param name=\"cid\" value=\"#{javax.enterprise.context.conversation.id}\"/>\n"
+"</h:link>"
msgstr ""
"\n"
" \n"
@@ -360,7 +360,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a "flash" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
+msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a \"flash\" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
msgstr "O contexto da conversação se propaga sobre redirecionamentos, tornando muito fácil implementar o padrão POST-então-redirecione, sem ter de recorrer a construções frágeis, como um objeto \"flash\". O contêiner adiciona automaticamente o identificador da conversação na URL redirecionada como um parâmetro de solicitação."
#. Tag: title
@@ -370,7 +370,7 @@ msgstr "Tempo limite de conversação"
#. Tag: para
#, fuzzy, no-c-format
-msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
+msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
msgstr "O contêiner pode destruir uma conversação e todo estado mantido em seu contexto, a qualquer momento, a fim de preservar recursos. A implementação do CDI irá fazer isso normalmente, com base em algum tipo de tempo limite (timeout)—embora isso não seja exigido pela especificação. O tempo limite é o período de inatividade antes que a conversação seja destruída (em contraste com a quantidade de tempo que a conversação está ativa)."
#. Tag: para
@@ -400,12 +400,12 @@ msgstr "Ao contrário dos outros escopos, os quais pertencem ao pacote
#. Tag: para
#, fuzzy, no-c-format
-msgid "You can guess what "singleton" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
+msgid "You can guess what \"singleton\" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
msgstr "Você pode adivinhar o que \"singleton\" significa aqui. Ele significa que um bean é instanciado apenas uma vez. Infelizmente, existe um pequeno problema com este pseudo-escopo. Os beans com escopo @Singleton não possuem um objeto de proxy. Os clientes mantêm uma referência direta para a instância singleton. Portanto, precisamos considerar o caso de um cliente que pode ser serializado, por exemplo, qualquer bean com escopo @SessionScoped ou @ConversationScoped, qualquer objeto dependente de um bean com escopo @SessionScoped ou @ConversationScoped, ou qualquer bean de sessão com estado."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
+msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
msgstr "Agora, se a instância singleton é simples objeto imutável e serializável como uma string, um número ou uma data, provavelmente não importaremos muito se ele ficar duplicado na serialização. No entanto, isso faz com que ele deixe de ser um verdadeiro singleton, e podemos muito bem apenas o declarar com o escopo padrão."
#. Tag: para
@@ -425,7 +425,7 @@ msgstr "certificar-se que o cliente mantém apenas uma referência transiente pa
#. Tag: para
#, fuzzy, no-c-format
-msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
+msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
msgstr "dar ao cliente uma referência do tipo Instance<X>, onde X é o tipo do bean singleton."
#. Tag: para
@@ -465,12 +465,12 @@ msgstr "Se uma expressão Unified EL se refere a um bean dependente pelo seu nom
#. Tag: para
#, fuzzy, no-c-format
-msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
+msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
msgstr "Se você precisa acessar um bean diretamente pelo nome EL em uma página JSF, você provavelmente precisa dar a ele um escopo diferente de @Dependent. Caso contrário, qualquer valor que for definido no bean por uma entrada JSF será perdido imediatamente. É por isso que CDI possui o estereótipo @Model; ele permite que você dê um nome ao bean e define seu escopo para @RequestScoped de uma só vez. Se você precisa acessar um bean que realmente necessita possuir o escopo @Dependent a partir de uma página JSF, injete-o dentro de um bean diferente e exponha-o em EL por meio de um método getter."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
+msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
msgstr "Os beans com escopo @Dependent não precisam de um objeto de proxy. O cliente mantém uma referência direta para sua instância."
#. Tag: para
@@ -537,7 +537,7 @@ msgstr "O campo calculator tem uma instância de Cal
#. Tag: para
#, fuzzy, no-c-format
-msgid "This feature is particularly useful with producer methods, as we'll see in the next chapter."
+msgid "This feature is particularly useful with producer methods, as we'll see in ."
msgstr "Essa funcionalidade é particularmente útil em métodos produtores, como poderemos verificar no próximo capítulo."
#~ msgid "@RequestScoped"
diff --git a/docs/reference/src/main/docbook/pt-BR/specialization.po b/docs/reference/src/main/docbook/pt-BR/specialization.po
index 7cd8ae59991..56803412fa4 100644
--- a/docs/reference/src/main/docbook/pt-BR/specialization.po
+++ b/docs/reference/src/main/docbook/pt-BR/specialization.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-12-19 18:08-0300\n"
"Last-Translator: João Paulo Viragine \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
+msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
msgstr ""
#. Tag: para
@@ -41,12 +41,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
+msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
+msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
msgstr ""
#. Tag: title
@@ -74,7 +74,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
+msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
msgstr "Mas, no nosso ambiente simulado, nos sobrepomos a implementação de PaymentProcessor com um Web Bean diferente:"
#. Tag: programlisting
@@ -114,12 +114,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
+msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
+msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
msgstr ""
#. Tag: programlisting
@@ -165,16 +165,16 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <alternatives>\n"
-" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
-" </alternatives>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <alternatives>\n"
+" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
+" </alternatives>\n"
+"</beans>"
msgstr ""
"
#. Tag: para
#, no-c-format
-msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
+msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
msgstr ""
#. Tag: para
@@ -269,7 +269,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
+msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pt-BR/stereotypes.po b/docs/reference/src/main/docbook/pt-BR/stereotypes.po
index ab6d4ad21f8..254f57bbc51 100644
--- a/docs/reference/src/main/docbook/pt-BR/stereotypes.po
+++ b/docs/reference/src/main/docbook/pt-BR/stereotypes.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Introduction_to_Web_Beans VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-12-19 18:10-0300\n"
"Last-Translator: João Paulo Viragine \n"
"Language-Team: none\n"
@@ -100,7 +100,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
+msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
msgstr ""
#. Tag: title
@@ -144,7 +144,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
+msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
msgstr ""
#. Tag: title
@@ -263,12 +263,12 @@ msgstr "Estereótipos"
#. Tag: para
#, no-c-format
-msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
+msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
+msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
msgstr ""
#. Tag: programlisting
@@ -295,7 +295,7 @@ msgstr "Estereótipos padrões"
#. Tag: para
#, fuzzy, no-c-format
-msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
+msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
msgstr "Já conhecemos dois estereótipos padrões definidos pela especificação de Web Beans: @Interceptor e @Decorator."
#. Tag: para
diff --git a/docs/reference/src/main/docbook/pt-BR/weldexamples.po b/docs/reference/src/main/docbook/pt-BR/weldexamples.po
index bbc878840ee..23d4a8ffad0 100644
--- a/docs/reference/src/main/docbook/pt-BR/weldexamples.po
+++ b/docs/reference/src/main/docbook/pt-BR/weldexamples.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-22 10:40-0300\n"
"Last-Translator: Bruno Leonardo Gonçalves \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "Mergulhando nos exemplos do Weld"
#. Tag: para
#, fuzzy, no-c-format
-msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
+msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
msgstr "É hora de tirar as tampas e mergulhar dentro das aplicações de exemplo do Weld. Vamos começar com o mais simples dos dois exemplos, weld-numberguess."
#. Tag: title
@@ -31,29 +31,29 @@ msgstr "O exemplo numberguess em detalhes"
#. Tag: para
#, fuzzy, no-c-format
-msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
+msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
msgstr "Na aplicação numberguess você tem 10 tentativas para adivinhar um número entre 1 e 100. Depois de cada tentativa, você é informado se seu palpite foi muito alto ou muito baixo."
#. Tag: para
#, fuzzy, no-c-format
-msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
+msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
msgstr "O exemplo numberguess é composto de uma série de beans, arquivos de configuração e páginas em Facelets (JSF), empacotados como um módulo war. Vamos começar examinando os arquivos de configuração."
#. Tag: para
#, fuzzy, no-c-format
-msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
+msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
msgstr "Todos os arquivos de configuração para este exemplo estão localizados no WEB-INF/, o qual pode ser encontrado no diretório src/main/webapp do exemplo. Primeiro, nós temos a versão JSF 2.0 de faces-config.xml. Uma versão padronizada de Facelets é o view handler padrão em JSF 2.0, então não há realmente nada a ser configurado. Assim, a configuração consiste apenas ao elemento raíz."
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<faces-config version="2.0"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<faces-config version=\"2.0\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd">\n"
-"</faces-config>"
+" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd\">\n"
+"</faces-config>"
msgstr ""
"beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
+msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
msgstr "Existe também um arquivo beans.xml vazio, que diz ao contêiner para procurar por beans nesta aplicação e ativar os serviços CDI."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Finally, there's the familiar web.xml:"
+msgid "Finally, there's the familiar web.xml:"
msgstr "Finalmente, temos o familiar web.xml:"
#. Tag: programlisting
#, no-c-format
msgid ""
-"<web-app version="2.5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<web-app version=\"2.5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd\">\n"
" \n"
-" <display-name>weld-jsf-numberguess-war</display-name>\n"
-" <description>Weld JSF numberguess example (war)</description>\n"
-"\n"
-" <servlet>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
-" <load-on-startup>1</load-on-startup>\n"
-" </servlet>\n"
-"\n"
-" <servlet-mapping>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <url-pattern>*.jsf</url-pattern>\n"
-" </servlet-mapping>\n"
+" <display-name>weld-jsf-numberguess-war</display-name>\n"
+" <description>Weld JSF numberguess example (war)</description>\n"
+"\n"
+" <servlet>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
+" <load-on-startup>1</load-on-startup>\n"
+" </servlet>\n"
+"\n"
+" <servlet-mapping>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <url-pattern>*.jsf</url-pattern>\n"
+" </servlet-mapping>\n"
" \n"
-" <context-param>\n"
-" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
-" <param-value>.xhtml</param-value>\n"
-" </context-param>\n"
+" <context-param>\n"
+" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
+" <param-value>.xhtml</param-value>\n"
+" </context-param>\n"
"\n"
-" <session-config>\n"
-" <session-timeout>10</session-timeout>\n"
-" </session-config>\n"
+" <session-config>\n"
+" <session-timeout>10</session-timeout>\n"
+" </session-config>\n"
"\n"
-"</web-app>"
+"</web-app>"
msgstr ""
#. Tag: para
@@ -136,51 +136,51 @@ msgstr "Este exemplo utiliza JSF 2 como framework de visão, mas você pode usar
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
+msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
msgstr "Vamos dar uma olhada na principal página JSF, src/main/webapp/home.xhtml."
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"\n"
-" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">\n"
-"<html xmlns="http://www.w3.org/1999/xhtml"\n"
-" xmlns:ui="http://java.sun.com/jsf/facelets"\n"
-" xmlns:h="http://java.sun.com/jsf/html"\n"
-" xmlns:f="http://java.sun.com/jsf/core">\n"
-"\n"
-" <ui:composition template="/template.xhtml">\n"
-" <ui:define name="content">\n"
-" <h1>Guess a number...</h1>\n"
-" <h:form id="numberGuess">\n"
-" <div style="color: red">\n"
-" <h:messages id="messages" globalOnly="false"/>\n"
-" <h:outputText id="Higher" value="Higher!"\n"
-" rendered="#{game.number gt game.guess and game.guess ne 0}"/>\n"
-" <h:outputText id="Lower" value="Lower!"\n"
-" rendered="#{game.number lt game.guess and game.guess ne 0}"/>\n"
-" </div>\n"
+"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
+" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n"
+"<html xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" xmlns:ui=\"http://java.sun.com/jsf/facelets\"\n"
+" xmlns:h=\"http://java.sun.com/jsf/html\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\">\n"
+"\n"
+" <ui:composition template=\"/template.xhtml\">\n"
+" <ui:define name=\"content\">\n"
+" <h1>Guess a number...</h1>\n"
+" <h:form id=\"numberGuess\">\n"
+" <div style=\"color: red\">\n"
+" <h:messages id=\"messages\" globalOnly=\"false\"/>\n"
+" <h:outputText id=\"Higher\" value=\"Higher!\"\n"
+" rendered=\"#{game.number gt game.guess and game.guess ne 0}\"/>\n"
+" <h:outputText id=\"Lower\" value=\"Lower!\"\n"
+" rendered=\"#{game.number lt game.guess and game.guess ne 0}\"/>\n"
+" </div>\n"
" \n"
-" <div>\n"
-" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
+" <div>\n"
+" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
" You have #{game.remainingGuesses} guesses remaining.\n"
-" </div>\n"
+" </div>\n"
" \n"
-" <div>\n"
+" <div>\n"
" Your guess: \n"
-" <h:inputText id="inputGuess" value="#{game.guess}"\n"
-" size="3" required="true" disabled="#{game.number eq game.guess}"\n"
-" validator="#{game.validateNumberRange}"/>\n"
-" <h:commandButton id="guessButton" value="Guess" \n"
-" action="#{game.check}" disabled="#{game.number eq game.guess}"/>\n"
-" </div>\n"
-" <div>\n"
-" <h:commandButton id="restartButton" value="Reset" action="#{game.reset}" immediate="true"/>\n"
-" </div>\n"
-" </h:form>\n"
-" </ui:define>\n"
-" </ui:composition>\n"
-"</html>"
+" <h:inputText id=\"inputGuess\" value=\"#{game.guess}\"\n"
+" size=\"3\" required=\"true\" disabled=\"#{game.number eq game.guess}\"\n"
+" validator=\"#{game.validateNumberRange}\"/>\n"
+" <h:commandButton id=\"guessButton\" value=\"Guess\" \n"
+" action=\"#{game.check}\" disabled=\"#{game.number eq game.guess}\"/>\n"
+" </div>\n"
+" <div>\n"
+" <h:commandButton id=\"restartButton\" value=\"Reset\" action=\"#{game.reset}\" immediate=\"true\"/>\n"
+" </div>\n"
+" </h:form>\n"
+" </ui:define>\n"
+" </ui:composition>\n"
+"</html>"
msgstr ""
#. Tag: para
@@ -190,7 +190,7 @@ msgstr "Facelets é o mecanismo de template embutido no JSF. Aqui estamos envolv
#. Tag: para
#, fuzzy, no-c-format
-msgid "There are a number of messages which can be sent to the user, "Higher!", "Lower!" and "Correct!""
+msgid "There are a number of messages which can be sent to the user, \"Higher!\", \"Lower!\" and \"Correct!\""
msgstr "Existe uma série de mensagens que podem ser enviadas ao usuário, \"Higher!\", \"Lower!\" e \"Correct!\""
#. Tag: para
@@ -205,7 +205,7 @@ msgstr "Este campo de entrada é vinculado a uma propriedade do bean usando uma
#. Tag: para
#, fuzzy, no-c-format
-msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
+msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
msgstr "Um validador é vinculado para ter certeza que o usuário não colocou acidentalmente um número fora do intervalo que pode ser sugerido - se o validador não fosse definido, o usuário poderia fazer um palpite fora dos limites."
#. Tag: para
@@ -302,7 +302,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The Generator is application scoped, so we don't get a different random each time."
+msgid "The Generator is application scoped, so we don't get a different random each time."
msgstr "O bean Generator possui escopo de aplicação, assim não obtemos uma instância de Random diferente a cada vez."
#. Tag: para
@@ -312,12 +312,12 @@ msgstr "A declaração de pacote e as importações foram removidas destas lista
#. Tag: para
#, fuzzy, no-c-format
-msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
+msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
msgstr "O último bean na aplicação é a classe Game com escopo de sessão. Este é o principal ponto de entrada da aplicação. É responsável por criar ou redefinir o jogo, capturando e validando o palpite do usuário e fornecendo resposta ao usuário com uma FacesMessage. Nós utilizamos o método de pós-construção para inicializar o jogo recuperando um número aleatório a partir do bean @Random Instance<Integer>."
#. Tag: para
#, fuzzy, no-c-format
-msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
+msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
msgstr "Você notará que também adicionamos a anotação @Named nesta classe. Esta anotação somente é necessária quando você quer tornar o bean acessível em uma página JSF por meio de EL (ou seja, #{game})."
#. Tag: programlisting
@@ -334,19 +334,19 @@ msgid ""
" private int remainingGuesses;\n"
"\n"
" @Inject @MaxNumber private int maxNumber;\n"
-" @Inject @Random Instance<Integer> randomNumber;\n"
+" @Inject @Random Instance<Integer> randomNumber;\n"
" \n"
" public Game() {}\n"
" \n"
" public void check() {\n"
-" if (guess > number) {\n"
+" if (guess > number) {\n"
" biggest = guess - 1;\n"
" }\n"
-" else if (guess < number) {\n"
+" else if (guess < number) {\n"
" smallest = guess + 1;\n"
" }\n"
" else if (guess == number) {\n"
-" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage("Correct!"));\n"
+" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage(\"Correct!\"));\n"
" }\n"
" remainingGuesses--;\n"
" }\n"
@@ -361,18 +361,18 @@ msgid ""
" }\n"
" \n"
" public void validateNumberRange(FacesContext context, UIComponent toValidate, Object value) {\n"
-" if (remainingGuesses <= 0) {\n"
-" FacesMessage message = new FacesMessage("No guesses left!");\n"
+" if (remainingGuesses <= 0) {\n"
+" FacesMessage message = new FacesMessage(\"No guesses left!\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" ((UIInput) toValidate).setValid(false);\n"
" return;\n"
" }\n"
" int input = (Integer) value;\n"
"\n"
-" if (input < smallest || input > biggest) {\n"
+" if (input < smallest || input > biggest) {\n"
" ((UIInput) toValidate).setValid(false);\n"
"\n"
-" FacesMessage message = new FacesMessage("Invalid guess");\n"
+" FacesMessage message = new FacesMessage(\"Invalid guess\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" }\n"
" }\n"
@@ -500,15 +500,15 @@ msgstr "Você deve também incluir os jars para JSF, EL e as anotações comuns
#. Tag: para
#, fuzzy, no-c-format
-msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
+msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
msgstr "Segundo, precisamos especificar explicitamente o servlet listener no web.xml, porque o contêiner não fará isto por você. O servlet listener inicia o Weld e controla sua interação com as solicitações."
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
"\n"
" org.jboss.weld.environment.servlet.Listener\n"
@@ -516,7 +516,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
+msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
msgstr "Quando o Weld inicia, ele coloca o javax.enterprise.inject.spi.BeanManager, o SPI portável para obtenção de instâncias de bean, no ServletContext com um nome igual ao nome da interface totalmente qualificada. Normalmente você não precisa acessar esta interface, mas o Weld faz uso dela."
#. Tag: title
@@ -535,18 +535,18 @@ msgid "Creating the Eclipse project"
msgstr "Criando o projeto no Eclipse"
#. Tag: para
-#, no-c-format
-msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin ."
+#, fuzzy, no-c-format
+msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin."
msgstr "Para usar o exemplo numberguess com Weld SE no Eclipse, você pode abrir o exemplo normalmente utilizando o plugin m2eclipse."
#. Tag: para
#, fuzzy, no-c-format
-msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects . Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
-msgstr "Tendo o m2eclipse instalado, vocẽ pode abrir qualquer projeto Maven diretamente. Dentro do Eclipse, selecione File -> Import... -> Maven Projects. Agora, navegue até o local do exemplo numberguess com Weld SE. Você deve ver que o Eclipse reconhece a existẽncia de um projeto Maven."
+msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects. Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
+msgstr "Se você possui o m2eclipse instalado, você pode abrir qualquer projeto Maven diretamente. Uma vez dentro do Eclipse, selecione File -> Import... -> Maven Projects. Então, navegue até o diretório do exemplo numberguess com Wicket. Você observará que o Eclipse reconhece a existência de um projeto Maven."
#. Tag: para
-#, no-c-format
-msgid "This will create a project in your workspace called weld-se-numberguess ."
+#, fuzzy, no-c-format
+msgid "This will create a project in your workspace called weld-se-numberguess."
msgstr "Isto criará um projeto em seu workspace com o nome weld-se-numberguess."
#. Tag: para
@@ -556,7 +556,7 @@ msgstr "Se você não está usando o plugin m2eclipse, você tem que seguir dife
#. Tag: para
#, fuzzy, no-c-format
-msgid "It's time to get the example running!"
+msgid "It's time to get the example running!"
msgstr "É hora de ver o exemplo rodando!"
#. Tag: title
@@ -566,12 +566,12 @@ msgstr "Rodando o exemplo dentro do Eclipse"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
+msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
msgstr "Desabilite a opção de Workspace Resolution do m2eclipse para assegurar que o Eclipse encontre StartMain. Clique com o botão direito sobre o projeto, selecione Properties -> Maven e desmarque Resolve dependencies from Workspace projects:"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Right click on the project, and choose Run As -> Run As Application:"
+msgid "Right click on the project, and choose Run As -> Run As Application:"
msgstr "Agora com o botão direito clique sobre o projeto novamente e selecione Run As -> Run As Application:"
#. Tag: para
@@ -621,7 +621,7 @@ msgstr "Entendendo o código"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's have a look at the significant code and configuration files that make up this example."
+msgid "Let's have a look at the significant code and configuration files that make up this example."
msgstr "Vamos dar uma olhada no código e arquivos de configuração interessantes que compõem este exemplo."
#. Tag: para
@@ -631,7 +631,7 @@ msgstr "Como usual, existe um arquivo beans.xml vazio no paco
#. Tag: para
#, fuzzy, no-c-format
-msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
+msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
msgstr "A lógica principal do jogo está em Game.java. Aqui está o código para esta classe, destacando os pontos que diferem da versão web:"
#. Tag: programlisting
@@ -676,7 +676,7 @@ msgid ""
"\n"
" public boolean isGameLost()\n"
" {\n"
-" return guess != number && remainingGuesses <= 0;\n"
+" return guess != number && remainingGuesses <= 0;\n"
" }\n"
"\n"
" public boolean check()\n"
@@ -685,12 +685,12 @@ msgid ""
"\n"
" if (checkNewNumberRangeIsValid())\n"
" {\n"
-" if (guess > number)\n"
+" if (guess > number)\n"
" {\n"
" biggest = guess - 1;\n"
" }\n"
"\n"
-" if (guess < number)\n"
+" if (guess < number)\n"
" {\n"
" smallest = guess + 1;\n"
" }\n"
@@ -708,7 +708,7 @@ msgid ""
"\n"
" private boolean checkNewNumberRangeIsValid()\n"
" {\n"
-" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
+" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
" }\n"
"\n"
" @PostConstruct\n"
@@ -725,12 +725,12 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
+msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
msgstr "O bean está com escopo de aplicação em vez de sessão, uma vez que uma instância de uma aplicação Swing representa tipicamente uma única 'sessão'."
#. Tag: para
#, fuzzy, no-c-format
-msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
+msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
msgstr "Observe que o bean não é nomeado, já que não é necessário ser acessado por meio de EL."
#. Tag: para
@@ -760,12 +760,12 @@ msgstr "Já que não existe uma fase específica para validação, os dados de e
#. Tag: para
#, fuzzy, no-c-format
-msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
+msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
msgstr "O método reset() faz uma chamada ao rndGenerator injetado para obter o número aleatório ao início de cada jogo. Note que não podemos usar Instance.get() como no exemplo JSF, porque não teremos nenhum contexto ativo como em uma solicitação JSF."
#. Tag: para
#, fuzzy, no-c-format
-msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
+msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
msgstr "A classe MessageGenerator depende da instância corrente de Game e consulta seu estado para determinar as mensagens apropriadas para solicitar o próximo palpite do usuário e responder de acordo com os palpites anteriores. O código do MessageGenerator vem a seguir:"
#. Tag: programlisting
@@ -778,11 +778,11 @@ msgid ""
"\n"
" public String getChallengeMessage()\n"
" {\n"
-" StringBuilder challengeMsg = new StringBuilder("I'm thinking of a number between ");\n"
+" StringBuilder challengeMsg = new StringBuilder(\"I'm thinking of a number between \");\n"
" challengeMsg.append(game.getSmallest());\n"
-" challengeMsg.append(" and ");\n"
+" challengeMsg.append(\" and \");\n"
" challengeMsg.append(game.getBiggest());\n"
-" challengeMsg.append(". Can you guess what it is?");\n"
+" challengeMsg.append(\". Can you guess what it is?\");\n"
"\n"
" return challengeMsg.toString();\n"
" }\n"
@@ -791,34 +791,34 @@ msgid ""
" {\n"
" if (game.isGameWon())\n"
" {\n"
-" return "You guessed it! The number was " + game.getNumber();\n"
+" return \"You guessed it! The number was \" + game.getNumber();\n"
" }\n"
" else if (game.isGameLost())\n"
" {\n"
-" return "You are fail! The number was " + game.getNumber();\n"
+" return \"You are fail! The number was \" + game.getNumber();\n"
" }\n"
" else if (!game.isValidNumberRange())\n"
" {\n"
-" return "Invalid number range!";\n"
+" return \"Invalid number range!\";\n"
" }\n"
" else if (game.getRemainingGuesses() == Game.MAX_NUM_GUESSES)\n"
" {\n"
-" return "What is your first guess?";\n"
+" return \"What is your first guess?\";\n"
" }\n"
" else\n"
" {\n"
" String direction = null;\n"
"\n"
-" if (game.getGuess() < game.getNumber())\n"
+" if (game.getGuess() < game.getNumber())\n"
" {\n"
-" direction = "Higher";\n"
+" direction = \"Higher\";\n"
" }\n"
" else\n"
" {\n"
-" direction = "Lower";\n"
+" direction = \"Lower\";\n"
" }\n"
"\n"
-" return direction + "! You have " + game.getRemainingGuesses() + " guesses left.";\n"
+" return direction + \"! You have \" + game.getRemainingGuesses() + \" guesses left.\";\n"
" }\n"
" }\n"
"}"
@@ -831,7 +831,7 @@ msgstr "A instância de Game para a aplicação é injetada a
#. Tag: para
#, fuzzy, no-c-format
-msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
+msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
msgstr "O estado de Game é interrogado para determinar a mensagem de desafio apropriada ..."
#. Tag: para
@@ -901,7 +901,7 @@ msgid ""
" private void refreshUI() {\n"
" mainLabel.setText( msgGenerator.getChallengeMessage() );\n"
" messageLabel.setText( msgGenerator.getResultMessage() );\n"
-" guessText.setText( "" );\n"
+" guessText.setText( \"\" );\n"
" guessesLeftBar.setValue( game.getRemainingGuesses() );\n"
" guessText.requestFocus();\n"
" }\n"
@@ -936,7 +936,7 @@ msgstr "Este método inicializa todos os componentes Swing. Observe o uso do
guessButtonActionPerformed
is called when the 'Guess' button is clicked, and it does the following:"
+msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
msgstr "guessButtonActionPerformed é chamado quando o botão 'Guess' é clicado, e faz o seguinte:"
#. Tag: para
@@ -946,7 +946,7 @@ msgstr "Pega o palpite digitado pelo usuário e o define como palpile corrente n
#. Tag: para
#, fuzzy, no-c-format
-msgid "Calls game.check() to validate and perform one 'turn' of the game"
+msgid "Calls game.check() to validate and perform one 'turn' of the game"
msgstr "Chama game.check() para validar e realizar uma 'rodada' do jogo"
#. Tag: para
@@ -971,7 +971,7 @@ msgstr "O exemplo translator pegará qualquer sentença que vocẽ entrar e as t
#. Tag: para
#, fuzzy, no-c-format
-msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
+msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
msgstr "O exemplo translator é construído como um ear e contém EJBs. Como resultado, sua estrutura é mais complexa do que o exemplo numberguess."
#. Tag: para
@@ -981,25 +981,25 @@ msgstr "Java EE 6, que vem com EJB 3.1, permite que você empacote EJBs em um wa
#. Tag: para
#, fuzzy, no-c-format
-msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
+msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
msgstr "Primeiro, vamos dar uma olhada no agregador eear, que está localizado no diretório ear do exemplo. O Maven automaticamente gera o application.xml para nós com esta configuração de plugin:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<plugin>\n"
-" <groupId>org.apache.maven.plugins</groupId>\n"
-" <artifactId>maven-ear-plugin</artifactId>\n"
-" <configuration>\n"
-" <modules>\n"
-" <webModule>\n"
-" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
-" <artifactId>weld-jsf-translator-war</artifactId>\n"
-" <contextRoot>/weld-translator</contextRoot>\n"
-" </webModule>\n"
-" </modules>\n"
-" </configuration>\n"
-"</plugin>"
+"<plugin>\n"
+" <groupId>org.apache.maven.plugins</groupId>\n"
+" <artifactId>maven-ear-plugin</artifactId>\n"
+" <configuration>\n"
+" <modules>\n"
+" <webModule>\n"
+" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
+" <artifactId>weld-jsf-translator-war</artifactId>\n"
+" <contextRoot>/weld-translator</contextRoot>\n"
+" </webModule>\n"
+" </modules>\n"
+" </configuration>\n"
+"</plugin>"
msgstr ""
"\n"
" org.apache.maven.plugins\n"
@@ -1022,32 +1022,32 @@ msgstr "Esta configuração sobrescreve o caminho do contexto web, resultando ne
#. Tag: para
#, fuzzy, no-c-format
-msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
+msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
msgstr "Se você não estiver utilizando o Maven para gerar estes arquivos, você deve precisar de um META-INF/application.xml:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<application version="5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<application version=\"5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/application_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/application_5.xsd\">\n"
"\n"
-" <display-name>weld-jsf-translator-ear</display-name>\n"
-" <description>The Weld JSF translator example (ear)</description>\n"
+" <display-name>weld-jsf-translator-ear</display-name>\n"
+" <description>The Weld JSF translator example (ear)</description>\n"
" \n"
-" <module>\n"
-" <web>\n"
-" <web-uri>weld-translator.war</web-uri>\n"
-" <context-root>/weld-translator</context-root>\n"
-" </web>\n"
-" </module>\n"
-" <module>\n"
-" <ejb>weld-translator.jar</ejb>\n"
-" </module>\n"
-"</application>"
+" <module>\n"
+" <web>\n"
+" <web-uri>weld-translator.war</web-uri>\n"
+" <context-root>/weld-translator</context-root>\n"
+" </web>\n"
+" </module>\n"
+" <module>\n"
+" <ejb>weld-translator.jar</ejb>\n"
+" </module>\n"
+"</application>"
msgstr ""
"war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
+msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
msgstr "Agora, vamos dar uma olhada no war, que está localizado no diretório war do exemplo. Da mesma forma do exemplo numberguess, temos um faces-config.xml para JSF 2.0 e um web.xml (para ativar JSF), ambos dentro de src/main/webapp/WEB-INF."
#. Tag: para
-#, no-c-format
-msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (ommitted here for brevity):"
+#, fuzzy, no-c-format
+msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (omitted here for brevity):"
msgstr "O mais interessante é a visão JSF usada para traduzir texto. Como no exemplo numberguess, possuimos um template (aqui omitido por brevidade) que circunda o formulário:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:form id="translator">\n"
+"<h:form id=\"translator\">\n"
"\n"
-" <table>\n"
-" <tr align="center" style="font-weight: bold">\n"
-" <td>\n"
+" <table>\n"
+" <tr align=\"center\" style=\"font-weight: bold\">\n"
+" <td>\n"
" Your text\n"
-" </td>\n"
-" <td>\n"
+" </td>\n"
+" <td>\n"
" Translation\n"
-" </td>\n"
-" </tr>\n"
-" <tr>\n"
-" <td>\n"
-" <h:inputTextarea id="text" value="#{translator.text}" required="true" rows="5" cols="80"/>\n"
-" </td>\n"
-" <td>\n"
-" <h:outputText value="#{translator.translatedText}"/>\n"
-" </td>\n"
-" </tr>\n"
-" </table>\n"
-" <div>\n"
-" <h:commandButton id="button" value="Translate" action="#{translator.translate}"/>\n"
-" </div>\n"
+" </td>\n"
+" </tr>\n"
+" <tr>\n"
+" <td>\n"
+" <h:inputTextarea id=\"text\" value=\"#{translator.text}\" required=\"true\" rows=\"5\" cols=\"80\"/>\n"
+" </td>\n"
+" <td>\n"
+" <h:outputText value=\"#{translator.translatedText}\"/>\n"
+" </td>\n"
+" </tr>\n"
+" </table>\n"
+" <div>\n"
+" <h:commandButton id=\"button\" value=\"Translate\" action=\"#{translator.translate}\"/>\n"
+" </div>\n"
" \n"
-"</h:form>"
+"</h:form>"
msgstr ""
"\n"
"\n"
@@ -1142,12 +1142,12 @@ msgstr "O usuário pode digitar algum texto no textarea à esquerda, e pressiona
#. Tag: para
#, fuzzy, no-c-format
-msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
+msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
msgstr "Finalmente vamos dar uma olhada no módulo EJB, o qual está localizado no diretório ejb do exemplo. Em src/main/resources/META-INF existe apenas um beans.xml vazio, usado para indicar que o jar possui beans."
#. Tag: para
#, fuzzy, no-c-format
-msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
+msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
msgstr "Nós temos deixado a parte mais interessante por último, o código! O projeto possui dois simples beans, SentenceParser e TextTranslator, e dois session beans, TranslatorControllerBean e SentenceTranslator. Você já deve estar bem familiarizado com beans agora, assim destacamos apenas as partes mais interessantes."
#. Tag: para
@@ -1171,7 +1171,7 @@ msgid ""
" public String translate(String text) { \n"
" StringBuilder sb = new StringBuilder(); \n"
" for (String sentence: sentenceParser.parse(text)) { \n"
-" sb.append(translator.translate(sentence)).append(". "); \n"
+" sb.append(translator.translate(sentence)).append(\". \"); \n"
" } \n"
" return sb.toString().trim(); \n"
" }\n"
@@ -1200,7 +1200,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
+msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
msgstr "TextTranslator usa o bean SentenceParser (realmente apenas uma simples classe Java!) para analisar a sentença e então chama o stateless bean com a interface local de negócio Translator para realizar a tradução. É onde a mágica acontece. Certamente, nós não pudemos desenvolver um tradutor completo, mas é suficientemente convincente para quem não conhece Latim!"
#. Tag: programlisting
@@ -1210,7 +1210,7 @@ msgid ""
"public class SentenceTranslator implements Translator { \n"
"\n"
" public String translate(String sentence) { \n"
-" return "Lorem ipsum dolor sit amet"; \n"
+" return \"Lorem ipsum dolor sit amet\"; \n"
" }\n"
"\n"
"}"
@@ -1234,7 +1234,7 @@ msgstr "Finalmente, existe um controlador orientado na interface com o usuário.
msgid ""
"@Stateful\n"
"@RequestScoped\n"
-"@Named("translator")\n"
+"@Named(\"translator\")\n"
"public class TranslatorControllerBean implements TranslatorController {\n"
"\n"
" @Inject private TextTranslator translator;\n"
@@ -1299,6 +1299,10 @@ msgstr ""
msgid "That concludes our short tour of the Weld starter examples. For more information on Weld, please visit http://www.seamframework.org/Weld."
msgstr "Isto conclui nosso rápido passeio com os exemplos de partida do Weld. Para mais informações sobre o Weld, por favor visite http://www.seamframework.org/Weld."
+#, fuzzy
+#~ msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects . Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
+#~ msgstr "Tendo o m2eclipse instalado, vocẽ pode abrir qualquer projeto Maven diretamente. Dentro do Eclipse, selecione File -> Import... -> Maven Projects. Agora, navegue até o local do exemplo numberguess com Weld SE. Você deve ver que o Eclipse reconhece a existẽncia de um projeto Maven."
+
#~ msgid "The numberguess example for Apache Wicket"
#~ msgstr "O exemplo numberguess para o Apache Wicket"
@@ -1317,9 +1321,6 @@ msgstr "Isto conclui nosso rápido passeio com os exemplos de partida do Weld. P
#~ msgid "To use the Wicket example in Eclipse, you have one of two choices. You can either use a Maven plugin to generate a regular Eclipse Web project, or you can open the example natively using the m2eclipse plugin. Since the Weld source code relies so heavily on Maven, we encourage you to bite the bullet and adopt the m2eclipse plugin. Both approaches are described here for your convenience.."
#~ msgstr "Para usar o exemplo com Wicket no Eclipse, você tem que escolher uma de duas opções. Você pode utilizar um plugin do Maven para gerar um projeto Web no Eclipse, ou pode abrir o exemplo sem grandes problemas usando o plugin m2eclipse. Uma vez que o código fonte do Weld depende bastante do Maven, nós encorajamos você a fazer um sacrifício e adotar o plugin m2eclipse. Ambas abordagens são descritas aqui para sua conveniência."
-#~ msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects. Then, browse to the location of the Wicket numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
-#~ msgstr "Se você possui o m2eclipse instalado, você pode abrir qualquer projeto Maven diretamente. Uma vez dentro do Eclipse, selecione File -> Import... -> Maven Projects. Então, navegue até o diretório do exemplo numberguess com Wicket. Você observará que o Eclipse reconhece a existência de um projeto Maven."
-
#~ msgid "This will create a project in your workspace called weld-wicket-numberguess."
#~ msgstr "Isto criará um projeto em seu workspace com o nome weld-wicket-numberguess."
diff --git a/docs/reference/src/main/docbook/zh-CN/Weld_-_JSR-299_Reference_Implementation.po b/docs/reference/src/main/docbook/zh-CN/Weld_-_JSR-299_Reference_Implementation.po
new file mode 100644
index 00000000000..f4baccac014
--- /dev/null
+++ b/docs/reference/src/main/docbook/zh-CN/Weld_-_JSR-299_Reference_Implementation.po
@@ -0,0 +1,59 @@
+#
+# AUTHOR , YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "A note about naming and nomenclature"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Shortly before the final draft of JSR-299 was submitted, the specification changed its name from \"Web Beans\" to \"Java Contexts and Dependency Injection for the Java EE platform\", abbreviated CDI. For a brief period after the renaming, the reference implementation adopted the name \"Web Beans\". However, this ended up causing more confusion than it solved and Red Hat decided to change the name of the reference implementation to \"Weld\". You may still find other documentation, blogs, forum posts, etc. that use the old nomenclature. Please update any references you can. The naming game is over."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You'll also find that some of the functionality that once existed in the specification is now missing, such as defining beans in XML. These features will be available as portable extensions for CDI in the Weld project, and perhaps other implementations."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this reference guide was started while changes were still being made to the specification. We've done our best to update it for accuracy. If you discover a conflict between what is written in this guide and the specification, the specification is the authority—assume it is correct. If you believe you have found an error in the specification, please report it to the JSR-299 EG."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Beans"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Start with Weld, the CDI Reference Implementation"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Loose coupling with strong typing"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "CDI and the Java EE ecosystem"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Weld Reference Guide"
+msgstr ""
+
diff --git a/docs/reference/src/main/docbook/zh-CN/beans.po b/docs/reference/src/main/docbook/zh-CN/beans.po
index d3a89f5458b..dd2e2b1fe30 100644
--- a/docs/reference/src/main/docbook/zh-CN/beans.po
+++ b/docs/reference/src/main/docbook/zh-CN/beans.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
+msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
msgstr ""
#. Tag: para
@@ -56,7 +56,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
+msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
msgstr ""
#. Tag: para
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
+msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
msgstr ""
#. Tag: title
@@ -131,7 +131,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's see what all this new terminology means."
+msgid "Let's see what all this new terminology means."
msgstr ""
#. Tag: title
@@ -141,7 +141,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a "contract" that must be satisfied by the bean to be injected. The contract is:"
+msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a \"contract\" that must be satisfied by the bean to be injected. The contract is:"
msgstr ""
#. Tag: para
@@ -164,14 +164,14 @@ msgstr ""
msgid ""
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
+msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
msgstr ""
#. Tag: para
@@ -192,12 +192,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
+msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
+msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
msgstr ""
#. Tag: programlisting
@@ -206,19 +206,19 @@ msgid ""
"@Typed(Shop.class)\n"
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of "quality" using a qualifier."
+msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of \"quality\" using a qualifier."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
+msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
msgstr ""
#. Tag: programlisting
@@ -232,12 +232,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
+msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
+msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
msgstr ""
#. Tag: para
@@ -252,12 +252,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
+msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
msgstr ""
#. Tag: para
@@ -275,12 +270,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If a bean does not explicitly specify a qualifier, it has the default qualifier, @Default."
+msgid "If a bean or an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
+msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
msgstr ""
#. Tag: title
@@ -312,7 +307,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
+msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
msgstr ""
#. Tag: para
@@ -322,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk more about scopes in ."
+msgid "We'll talk more about scopes in ."
msgstr ""
#. Tag: title
@@ -343,7 +338,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"public @SessionScoped @Named("cart")\n"
+"public @SessionScoped @Named(\"cart\")\n"
"class ShoppingCart implements Serializable { ... }"
msgstr ""
@@ -355,9 +350,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:dataTable value="#{cart.lineItems}" var="item">\n"
+"<h:dataTable value=\"#{cart.lineItems}\" var=\"item\">\n"
" ...\n"
-"</h:dataTable>"
+"</h:dataTable>"
msgstr ""
#. Tag: para
@@ -389,7 +384,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
+msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
msgstr ""
#. Tag: programlisting
@@ -416,12 +411,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
+msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
+msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
msgstr ""
#. Tag: para
@@ -470,17 +465,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
+msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
+msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
+msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
msgstr ""
#. Tag: title
@@ -490,7 +485,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
+msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
msgstr ""
#. Tag: title
@@ -500,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
+msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
msgstr ""
#. Tag: para
@@ -525,7 +520,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It has an appropriate constructor—either:"
+msgid "It has an appropriate constructor—either:"
msgstr ""
#. Tag: para
@@ -540,7 +535,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
+msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
msgstr ""
#. Tag: para
@@ -585,12 +580,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
+msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
+msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
msgstr ""
#. Tag: para
@@ -625,7 +620,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
+msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
msgstr ""
#. Tag: para
@@ -640,17 +635,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
+msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
+msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're "heavyweight". It's nothing more than superstition to think that something is "heavier" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like "heavyweight"."
+msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're \"heavyweight\". It's nothing more than superstition to think that something is \"heavier\" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like \"heavyweight\"."
msgstr ""
#. Tag: title
@@ -690,7 +685,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
+msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
msgstr ""
#. Tag: programlisting
@@ -705,7 +700,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<p>Your raffle number is #{randomNumber}.</p>"
+msgid "<p>Your raffle number is #{randomNumber}.</p>"
msgstr ""
#. Tag: para
@@ -746,14 +741,14 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces Set<Roles> getRoles(User user) {\n"
+"@Produces Set<Roles> getRoles(User user) {\n"
" return user.getRoles();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk much more about producer methods in ."
+msgid "We'll talk much more about producer methods in ."
msgstr ""
#. Tag: title
@@ -763,7 +758,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
+msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
msgstr ""
#. Tag: programlisting
@@ -771,7 +766,7 @@ msgstr ""
msgid ""
"public class Shop {\n"
" @Produces PaymentProcessor paymentProcessor = ....;\n"
-" @Produces @Catalog List<Product> products = ....;\n"
+" @Produces @Catalog List<Product> products = ....;\n"
"}"
msgstr ""
@@ -782,5 +777,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
+msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
msgstr ""
diff --git a/docs/reference/src/main/docbook/zh-CN/configure.po b/docs/reference/src/main/docbook/zh-CN/configure.po
index eeba87f0a16..01ef2ccd8ab 100644
--- a/docs/reference/src/main/docbook/zh-CN/configure.po
+++ b/docs/reference/src/main/docbook/zh-CN/configure.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -30,50 +30,50 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
+msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<?xml version="1.0" encoding="UTF-8"?>\n"
-"<beans xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \n"
-" xmlns:weld="http://jboss.org/schema/weld/beans" \n"
-" xsi:schemaLocation="\n"
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<beans xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" \n"
+" xmlns:weld=\"http://jboss.org/schema/weld/beans\" \n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee http://docs.jboss.org/cdi/beans_1_0.xsd\n"
-" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">\n"
+" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd\">\n"
" \n"
-" <weld:scan>\n"
+" <weld:scan>\n"
" \n"
-" <!-- Don't deploy the classes for the swing app! -->\n"
-" <weld:exclude name="com.acme.swing.**" />\n"
+" <!-- Don't deploy the classes for the swing app! -->\n"
+" <weld:exclude name=\"com.acme.swing.**\" />\n"
" \n"
-" <!-- Don't include GWT support if GWT is not installed -->\n"
-" <weld:exclude name="com.acme.gwt.**">\n"
-" <weld:if-class-available name="!com.google.GWT"/>\n"
-" </weld:exclude>\n"
+" <!-- Don't include GWT support if GWT is not installed -->\n"
+" <weld:exclude name=\"com.acme.gwt.**\">\n"
+" <weld:if-class-available name=\"!com.google.GWT\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
+" <!--\n"
" Exclude classes which end in Blether if the system property verbosity is set to low\n"
" i.e.\n"
" java ... -Dverbosity=low \n"
-" --> \n"
-" <weld:exclude pattern="^(.*)Blether$">\n"
-" <weld:if-system-property name="verbosity" value="low"/>\n"
-" </weld:exclude>\n"
+" --> \n"
+" <weld:exclude pattern=\"^(.*)Blether$\">\n"
+" <weld:if-system-property name=\"verbosity\" value=\"low\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
-" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
+" <!--\n"
+" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
" property is not set\n"
-" -->\n"
-" <weld:exclude name="com.acme.jsf.**">\n"
-" <weld:if-class-available name="org.apahce.wicket.Wicket"/>\n"
-" <weld:if-system-property name="!viewlayer"/>\n"
-" </weld:exclude>\n"
-" </weld:scan>\n"
+" -->\n"
+" <weld:exclude name=\"com.acme.jsf.**\">\n"
+" <weld:if-class-available name=\"org.apahce.wicket.Wicket\"/>\n"
+" <weld:if-system-property name=\"!viewlayer\"/>\n"
+" </weld:exclude>\n"
+" </weld:scan>\n"
" \n"
-"</beans>"
+"</beans>"
msgstr ""
#. Tag: para
@@ -83,7 +83,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
+msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
msgstr ""
#. Tag: para
@@ -93,12 +93,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
+msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
+msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
msgstr ""
#. Tag: para
@@ -113,5 +113,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
+msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
msgstr ""
diff --git a/docs/reference/src/main/docbook/zh-CN/contexts.po b/docs/reference/src/main/docbook/zh-CN/contexts.po
index 998addb61d4..6503057daf1 100644
--- a/docs/reference/src/main/docbook/zh-CN/contexts.po
+++ b/docs/reference/src/main/docbook/zh-CN/contexts.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,17 +25,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld allows you to easiy manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivaed (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
+msgid "Weld allows you to easily manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivated (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and discociating the data store after calling activate."
+msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and dissociating the data store after calling activate."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld automatically controls context lifecycle in many scenarios such as Http Requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
+msgid "Weld automatically controls context lifecycle in many scenarios such as HTTP requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
msgstr ""
#. Tag: para
@@ -145,7 +145,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
+msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
msgstr ""
#. Tag: entry
@@ -245,12 +245,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implmentations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
+msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implementations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
+msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
msgstr ""
#. Tag: programlisting
@@ -263,14 +263,14 @@ msgid ""
" ...\n"
" \n"
" /* Start the request, providing a data store which will last the lifetime of the request */\n"
-" public void startRequest(Map<String, Object> requestDataStore) {\n"
+" public void startRequest(Map<String, Object> requestDataStore) {\n"
" // Associate the store with the context and acticate the context\n"
" requestContext.associate(requestDataStore);\n"
" requestContext.activate();\n"
" }\n"
" \n"
" /* End the request, providing the same data store as was used to start the request */\n"
-" public void endRequest(Map<String, Object> requestDataStore) {\n"
+" public void endRequest(Map<String, Object> requestDataStore) {\n"
" try {\n"
" /* Invalidate the request (all bean instances will be scheduled for destruction) */\n"
" requestContext.invalidate();\n"
@@ -290,7 +290,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's session contexts are "lazy" and don't require a session to actually exist until a bean instance must be written."
+msgid "Weld's session contexts are \"lazy\" and don't require a session to actually exist until a bean instance must be written."
msgstr ""
#. Tag: para
@@ -308,16 +308,16 @@ msgid ""
" /* Start a transient conversation */\n"
" /* Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */\n"
-" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" resumeOrStartConversation(requestDataStore, sessionDataStore, null);\n"
" }\n"
"\n"
" /* Start a transient conversation (if cid is null) or resume a non-transient */\n"
" /* conversation. Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */ \n"
-" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore, \n"
+" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore, \n"
" String cid) {\n"
" /* Associate the stores with the context and acticate the context */\n"
" * BoundRequest just wraps the two datastores */\n"
@@ -329,8 +329,8 @@ msgid ""
" /* End the conversations, providing the same data store as was used to start */\n"
" /* the request. Any transient conversations will be destroyed, any newly-promoted */\n"
" /* conversations will be placed into the session */\n"
-" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" try {\n"
" /* Invalidate the conversation (all transient conversations will be scheduled for destruction) */\n"
" conversationContext.invalidate();\n"
@@ -345,15 +345,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the containber), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
+msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the container), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the abilty to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
+msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the ability to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's conversations are not assigned ids until they become non-transient."
+msgid "Weld's conversations are not assigned ids until they become non-transient."
msgstr ""
diff --git a/docs/reference/src/main/docbook/zh-CN/decorators.po b/docs/reference/src/main/docbook/zh-CN/decorators.po
index 55ca9cea275..7002eeddf4b 100644
--- a/docs/reference/src/main/docbook/zh-CN/decorators.po
+++ b/docs/reference/src/main/docbook/zh-CN/decorators.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-10 11:18+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -21,12 +21,12 @@ msgstr "装饰器"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
+msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
msgstr "拦截器能够以一种强大的方式来捕获和分离关注点,拦截器和类型系统的关系是正交的。任何拦截器都能够拦截任何Java类型的调用。这种特性能够让拦截器很好的处理技术关注点,例如事务管理和安全。不过,拦截器无法领会其所拦截时间的真实语义。因此,拦截器并不是分离业务相关的关注点的好工具。"
#. Tag: para
#, fuzzy, no-c-format
-msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
+msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
msgstr "对装饰器来说,反之亦然。一个装饰器只拦截特定Java接口的调用,因此它能够领会这个接口关联的语义。装饰器的特性使其成为某些业务关注点的理想的建模工具。这也意味着装饰器并不拥有一个拦截器的普遍性。装饰器无法解决跨越多个不同类型的技术关注点。"
#. Tag: para
@@ -124,7 +124,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
+msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
msgstr "和其他简单的Web Beans不同,一个装饰器可以是一个抽象类。如果被装饰的接口中一个特殊方法对装饰器没有用处,那么装饰器可以不实现这个方法。"
#. Tag: para
@@ -208,14 +208,14 @@ msgid ""
" \n"
" public void withdraw(BigDecimal amount) {\n"
" account.withdraw(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedWithdrawl(amount) );\n"
" }\n"
" }\n"
" \n"
" public void deposit(BigDecimal amount);\n"
" account.deposit(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedDeposit(amount) );\n"
" }\n"
" }\n"
@@ -258,21 +258,21 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <decorators>\n"
-" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
-" </decorators>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <decorators>\n"
+" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
+" </decorators>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
+msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
msgstr "这个声明对于装饰器来说和<Interceptors>声明对于拦截器来说是一样的:"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-CN/ee.po b/docs/reference/src/main/docbook/zh-CN/ee.po
index 202106d9f0d..0930f8d0780 100644
--- a/docs/reference/src/main/docbook/zh-CN/ee.po
+++ b/docs/reference/src/main/docbook/zh-CN/ee.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-11 13:00+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -56,7 +56,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
+msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
msgstr ""
#. Tag: para
@@ -81,7 +81,7 @@ msgstr "将Java EE资源注入到一个Web Bean中"
#. Tag: para
#, fuzzy, no-c-format
-msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
+msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
msgstr "所有简单的和企业的Web Beans都可以通过@Resource, @EJB和@PersistenceContext来使用Java EE的依赖注入。我们已经看过很多例子了,虽然我们没有在这上面耗费精力:"
#. Tag: programlisting
@@ -140,7 +140,7 @@ msgstr "从Servlet调用一个Web Bean"
#. Tag: para
#, fuzzy, no-c-format
-msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
+msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
msgstr "在Java EE 6中,从一个Servlet中调用一个Web Bean非常容易,只须使用Web Beans域注入一个Web Bean或者将初始方法注入即可。"
#. Tag: programlisting
@@ -153,14 +153,14 @@ msgid ""
" @Override\n"
" public void service(HttpServletRequest request, HttpServletResponse response)\n"
" throws ServletException, IOException {\n"
-" credentials.setUsername(request.getParameter("username")):\n"
-" credentials.setPassword(request.getParameter("password")):\n"
+" credentials.setUsername(request.getParameter(\"username\")):\n"
+" credentials.setPassword(request.getParameter(\"password\")):\n"
" login.login();\n"
" if ( login.isLoggedIn() ) {\n"
-" response.sendRedirect("/home.jsp");\n"
+" response.sendRedirect(\"/home.jsp\");\n"
" }\n"
" else {\n"
-" response.sendRedirect("/loginError.jsp");\n"
+" response.sendRedirect(\"/loginError.jsp\");\n"
" }\n"
" }\n"
" \n"
@@ -199,7 +199,7 @@ msgstr "从消息驱动Bean中调用一个Web Bean"
#. Tag: para
#, no-c-format
-msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
+msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
msgstr ""
#. Tag: para
@@ -261,10 +261,10 @@ msgstr ""
#, no-c-format
msgid ""
"public class OrderResources {\n"
-" @Resource(name="jms/ConnectionFactory")\n"
+" @Resource(name=\"jms/ConnectionFactory\")\n"
" private ConnectionFactory connectionFactory;\n"
" \n"
-" @Resource(name="jms/OrderQueue")\n"
+" @Resource(name=\"jms/OrderQueue\")\n"
" private Queue orderQueue;\n"
" \n"
" @Produces @OrderConnection\n"
@@ -315,7 +315,7 @@ msgid ""
"\n"
"public void sendMessage() {\n"
" MapMessage msg = orderSession.createMapMessage();\n"
-" msg.setLong("orderId", order.getId());\n"
+" msg.setLong(\"orderId\", order.getId());\n"
" ...\n"
" producer.send(msg);\n"
"}"
@@ -341,7 +341,7 @@ msgstr "打包和部署"
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a "bean archive". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
+msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a \"bean archive\". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
msgstr "Web Beans并没有指定特殊的部署包。你可以以JAR, EJB-JAR或者WAR形式将Web Beans打包在任何应用类路径中的部署位置上。然而,每个包含Web Beans的包必须在META-INF 或者 WEB-INF目录下包含一个名为 web-beans.xml的配置文件。这个文件可以是空的。没有web-beans.xml 配置文件,应用将无法使用Web Beans。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-CN/environments.po b/docs/reference/src/main/docbook/zh-CN/environments.po
index 803b51a3036..56742bcd82c 100644
--- a/docs/reference/src/main/docbook/zh-CN/environments.po
+++ b/docs/reference/src/main/docbook/zh-CN/environments.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-28 17:09+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -56,12 +56,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
+msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an "uber-jar", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
+msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an \"uber-jar\", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
msgstr ""
#. Tag: para
@@ -72,9 +72,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
#. Tag: title
@@ -84,18 +84,18 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
+msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<Context>\n"
-" <Resource name="BeanManager" \n"
-" auth="Container"\n"
-" type="javax.enterprise.inject.spi.BeanManager"\n"
-" factory="org.jboss.weld.resources.ManagerObjectFactory"/>\n"
-"</Context>"
+"<Context>\n"
+" <Resource name=\"BeanManager\" \n"
+" auth=\"Container\"\n"
+" type=\"javax.enterprise.inject.spi.BeanManager\"\n"
+" factory=\"org.jboss.weld.resources.ManagerObjectFactory\"/>\n"
+"</Context>"
msgstr ""
#. Tag: para
@@ -106,12 +106,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<resource-env-ref>\n"
-" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
-" <resource-env-ref-type>\n"
+"<resource-env-ref>\n"
+" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
+" <resource-env-ref-type>\n"
" javax.enterprise.inject.spi.BeanManager\n"
-" </resource-env-ref-type>\n"
-"</resource-env-ref>"
+" </resource-env-ref-type>\n"
+"</resource-env-ref>"
msgstr ""
#. Tag: para
@@ -131,27 +131,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
+msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.mortbay.jetty.plus.naming.Resource">\n"
-" <Arg><Ref id="webAppCtx"/></Arg> \n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.mortbay.jetty.plus.naming.Resource\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg> \n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure>"
msgstr ""
#. Tag: para
@@ -162,22 +162,22 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://www.eclipse.org/jetty/configure.dtd">\n"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://www.eclipse.org/jetty/configure.dtd\">\n"
"\n"
-"<Configure id="webAppCtx" class="org.eclipse.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.eclipse.jetty.plus.jndi.Resource">\n"
-" <Arg> <Ref id="webAppCtx"/> </Arg>\n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure> "
+"<Configure id=\"webAppCtx\" class=\"org.eclipse.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.eclipse.jetty.plus.jndi.Resource\">\n"
+" <Arg> <Ref id=\"webAppCtx\"/> </Arg>\n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure> "
msgstr ""
#. Tag: para
@@ -187,7 +187,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
+msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
msgstr ""
#. Tag: para
@@ -197,19 +197,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file META-INF/jetty-web.xml with the following content to your war:"
+msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file WEB-INF/jetty-web.xml with the following content to your war:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <Call class="org.jboss.weld.environment.jetty.WeldServletHandler" name="process">\n"
-" <Arg><Ref id="webAppCtx"/></Arg>\n"
-" </Call>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <Call class=\"org.jboss.weld.environment.jetty.WeldServletHandler\" name=\"process\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg>\n"
+" </Call>\n"
+"</Configure>"
msgstr ""
#. Tag: title
@@ -219,7 +219,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In addition to improved integration of the Enterprise Java stack, the "Contexts and Dependency Injection for the Java EE platform" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
+msgid "In addition to improved integration of the Enterprise Java stack, the \"Contexts and Dependency Injection for the Java EE platform\" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
msgstr ""
#. Tag: para
@@ -279,7 +279,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Parameters List<String> params;"
+msgid "@Inject @Parameters List<String> params;"
msgstr ""
#. Tag: programlisting
@@ -299,7 +299,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example of a simple CDI SE application:"
+msgid "Here's an example of a simple CDI SE application:"
msgstr ""
#. Tag: programlisting
@@ -308,8 +308,8 @@ msgid ""
"@Singleton\n"
"public class HelloWorld\n"
"{\n"
-" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
-" System.out.println("Hello " + parameters.get(0));\n"
+" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
+" System.out.println(\"Hello \" + parameters.get(0));\n"
" }\n"
"}"
msgstr ""
@@ -331,7 +331,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
+msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
msgstr ""
#. Tag: para
@@ -341,17 +341,17 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "java org.jboss.weld.environment.se.StartMain <args>"
+msgid "java org.jboss.weld.environment.se.StartMain <args>"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Programatic Bootstrap API"
+msgid "Programmatic Bootstrap API"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
+msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
msgstr ""
#. Tag: programlisting
@@ -377,10 +377,10 @@ msgid ""
"{\n"
"\n"
" /** Provides access to all beans within the application. */\n"
-" public Instance<Object> instance() {...}\n"
+" public Instance<Object> instance() {...}\n"
"\n"
" /** Provides access to all events within the application. */\n"
-" public Event<Object> event() {...}\n"
+" public Event<Object> event() {...}\n"
"\n"
" /** Provides direct access to the BeanManager. */\n"
" public BeanManager getBeanManager() {...}\n"
@@ -390,7 +390,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
+msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
msgstr ""
#. Tag: programlisting
@@ -430,22 +430,22 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
+msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans>\n"
-" <decorators>\n"
-" <decorator>org.jboss.weld.environment.se.threading.RunnableDecorator</decorator>\n"
-" </decorator>\n"
-"</beans>"
+"<beans>\n"
+" <decorators>\n"
+" <class>org.jboss.weld.environment.se.threading.RunnableDecorator</class>\n"
+" </decorator>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situtations where you would otherwise have used ThreadLocal directly, which are typically rare."
+msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situations where you would otherwise have used ThreadLocal directly, which are typically rare."
msgstr ""
#. Tag: title
@@ -455,7 +455,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
+msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-CN/events.po b/docs/reference/src/main/docbook/zh-CN/events.po
index d209d76edda..9d9c9aa8702 100644
--- a/docs/reference/src/main/docbook/zh-CN/events.po
+++ b/docs/reference/src/main/docbook/zh-CN/events.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-16 11:17+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -36,7 +36,7 @@ msgstr "不仅是事件产生者和观察者解耦;观察者和产生者也完
#. Tag: para
#, fuzzy, no-c-format
-msgid "observers can specify a combination of "selectors" to narrow the set of event notifications they will receive, and"
+msgid "observers can specify a combination of \"selectors\" to narrow the set of event notifications they will receive, and"
msgstr "观察者可以指定一个\"选择器\"组合来限定接受的事件通知,并且"
#. Tag: para
@@ -46,7 +46,7 @@ msgstr "观察者可以即刻被通知,也可以指定只有当前事务结束
#. Tag: para
#, no-c-format
-msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
+msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
msgstr ""
#. Tag: title
@@ -61,7 +61,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
+msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
msgstr ""
#. Tag: programlisting
@@ -104,7 +104,7 @@ msgstr "only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
+msgid "An observer method need not specify any event qualifiers—in this case it is interested in only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
msgstr "一个观察者方法无须指定一个事件绑定 在这种情况下,它对一个特定类型的 所有 事件都感兴趣(观察)。如果它没有指定事件绑定,那么它只对那些有事件绑定的事件感兴趣(观察)。"
#. Tag: para
@@ -129,7 +129,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Event<Document> documentEvent;"
+msgid "@Inject @Any Event<Document> documentEvent;"
msgstr " documentEvent]]>"
#. Tag: para
@@ -184,7 +184,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
+msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
msgstr " documentUpdatedEvent]]>"
#. Tag: para
@@ -204,12 +204,12 @@ msgstr "除了传递给fire()方法的事件绑定之外,
#. Tag: para
#, no-c-format
-msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
+msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
+msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
msgstr "(){} );]]>"
#. Tag: para
@@ -224,7 +224,7 @@ msgstr "事务性的观察者"
#. Tag: para
#, no-c-format
-msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
+msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
msgstr ""
#. Tag: para
@@ -286,7 +286,7 @@ msgstr "事件绑定类型成员可以通过事件产生者静态地指定,通
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
+msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
msgstr " LoggedInEvent;}}]]>"
#. Tag: para
@@ -298,7 +298,7 @@ msgstr "或者事件绑定类型成员的值也可以由事件产生者动态地
#, fuzzy, no-c-format
msgid ""
"abstract class RoleBinding \n"
-" extends AnnotationLiteral<Role> \n"
+" extends AnnotationLiteral<Role> \n"
" implements Role {}"
msgstr ""
" blogEvent;\n"
"...\n"
@@ -442,12 +442,12 @@ msgid ""
"\n"
" @PersistenceContext EntityManager em;\n"
" \n"
-" List<Product> products;\n"
+" List<Product> products;\n"
"\n"
" @Produces @Catalog \n"
-" List<Product> getCatalog() {\n"
+" List<Product> getCatalog() {\n"
" if (products==null) {\n"
-" products = em.createQuery("select p from Product p where p.deleted = false")\n"
+" products = em.createQuery(\"select p from Product p where p.deleted = false\")\n"
" .getResultList();\n"
" }\n"
" return products;\n"
@@ -489,16 +489,16 @@ msgid ""
"@Stateless\n"
"public class ProductManager {\n"
" @PersistenceContext EntityManager em;\n"
-" @Inject @Any Event<Product> productEvent;\n"
+" @Inject @Any Event<Product> productEvent;\n"
"\n"
" public void delete(Product product) {\n"
" em.delete(product);\n"
-" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
" }\n"
" \n"
" public void persist(Product product) {\n"
" em.persist(product);\n"
-" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
" }\n"
" ...\n"
"}"
diff --git a/docs/reference/src/main/docbook/zh-CN/example.po b/docs/reference/src/main/docbook/zh-CN/example.po
index c9509cffb05..b145b28112c 100644
--- a/docs/reference/src/main/docbook/zh-CN/example.po
+++ b/docs/reference/src/main/docbook/zh-CN/example.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-12 11:27+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "JSF Web应用例子"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
+msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
msgstr "让我们通过一个完整的例子来演示这些想法。我们将是使用JSF来实现一个应用的用户登录/退出功能。首先,我们定一个Web Bean来持有登录过程中用户输入的用户名和密码:"
#. Tag: programlisting
@@ -63,18 +63,18 @@ msgstr "这个Web Bean和下面的JSF表单的login绑定:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:form>\n"
-" <h:panelGrid columns="2" rendered="#{!login.loggedIn}">\n"
-" <f:validateBean>\n"
-" <h:outputLabel for="username">Username:</h:outputLabel>\n"
-" <h:inputText id="username" value="#{credentials.username}"/>\n"
-" <h:outputLabel for="password">Password:</h:outputLabel>\n"
-" <h:inputSecret id="password" value="#{credentials.password}"/>\n"
-" </f:validateBean>\n"
-" </h:panelGrid>\n"
-" <h:commandButton value="Login" action="#{login.login}" rendered="#{!login.loggedIn}"/>\n"
-" <h:commandButton value="Logout" action="#{login.logout}" rendered="#{login.loggedIn}"/>\n"
-"</h:form>"
+"<h:form>\n"
+" <h:panelGrid columns=\"2\" rendered=\"#{!login.loggedIn}\">\n"
+" <f:validateBean>\n"
+" <h:outputLabel for=\"username\">Username:</h:outputLabel>\n"
+" <h:inputText id=\"username\" value=\"#{credentials.username}\"/>\n"
+" <h:outputLabel for=\"password\">Password:</h:outputLabel>\n"
+" <h:inputSecret id=\"password\" value=\"#{credentials.password}\"/>\n"
+" </f:validateBean>\n"
+" </h:panelGrid>\n"
+" <h:commandButton value=\"Login\" action=\"#{login.login}\" rendered=\"#{!login.loggedIn}\"/>\n"
+" <h:commandButton value=\"Logout\" action=\"#{login.logout}\" rendered=\"#{login.loggedIn}\"/>\n"
+"</h:form>"
msgstr ""
"\n"
" \n"
@@ -121,7 +121,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
+msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
msgstr ""
#. Tag: para
@@ -141,10 +141,10 @@ msgid ""
" private User user;\n"
" \n"
" public void login() {\n"
-" List<User> results = userDatabase.createQuery(\n"
-" "select u from User u where u.username = :username and u.password = :password")\n"
-" .setParameter("username", credentials.getUsername())\n"
-" .setParameter("password", credentials.getPassword())\n"
+" List<User> results = userDatabase.createQuery(\n"
+" \"select u from User u where u.username = :username and u.password = :password\")\n"
+" .setParameter(\"username\", credentials.getUsername())\n"
+" .setParameter(\"password\", credentials.getPassword())\n"
" .getResultList();\n"
" \n"
" if (!results.isEmpty()) {\n"
@@ -290,14 +290,14 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:panelGroup rendered="#{login.loggedIn}">\n"
+"<h:panelGroup rendered=\"#{login.loggedIn}\">\n"
" signed in as #{currentUser.username}\n"
-"</h:panelGroup>"
+"</h:panelGroup>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
+msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
msgstr "希望这个例子能够让你尝试了Web Bean的编程模型。在下一章中,我们将更加深入的研究Web Bean的依赖注入。"
#~ msgid "Of course, @LoggedIn is a binding annotation:"
diff --git a/docs/reference/src/main/docbook/zh-CN/extend.po b/docs/reference/src/main/docbook/zh-CN/extend.po
index 2b85fb5da8f..9d789fb574d 100644
--- a/docs/reference/src/main/docbook/zh-CN/extend.po
+++ b/docs/reference/src/main/docbook/zh-CN/extend.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-02-16 14:16+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -76,7 +76,7 @@ msgstr " Bean 类"
#. Tag: para
#, no-c-format
-msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
+msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
msgstr ""
#. Tag: programlisting
@@ -164,15 +164,15 @@ msgid ""
"class MyExtension implements Extension {\n"
" \n"
" void beforeBeanDiscovery(@Observes BeforeBeanDiscovery bbd) {\n"
-" Logger.global.debug("beginning the scanning process");\n"
+" Logger.global.debug(\"beginning the scanning process\");\n"
" }\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
-" Logger.global.debug("scanning type: " + pat.getAnnotatedType().getJavaClass().getName());\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" Logger.global.debug(\"scanning type: \" + pat.getAnnotatedType().getJavaClass().getName());\n"
" } \n"
"\n"
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd) {\n"
-" Logger.global.debug("finished the scanning process");\n"
+" Logger.global.debug(\"finished the scanning process\");\n"
" }\n"
" \n"
"}"
@@ -180,7 +180,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
+msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
msgstr ""
#. Tag: programlisting
@@ -188,7 +188,7 @@ msgstr ""
msgid ""
"class MyExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" //tell the container to ignore the type if it is annotated @Ignore\n"
" if ( pat.getAnnotatedType().isAnnotionPresent(Ignore.class) ) pat.veto(); \n"
" } \n"
@@ -203,7 +203,7 @@ msgstr "扩展Web Bean的神经中枢是 Manager 对象。"
#. Tag: programlisting
#, no-c-format
-msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
+msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
msgstr ""
#. Tag: title
@@ -220,31 +220,31 @@ msgstr " Manager 接口能够让我们通过编程来注册
#, no-c-format
msgid ""
"public interface BeanManager {\n"
-" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
-" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
-" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
-" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
-" public Set<Bean<?>> getBeans(String name);\n"
-" public Bean<?> getPassivationCapableBean(String id);\n"
-" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
+" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
+" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
+" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
+" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
+" public Set<Bean<?>> getBeans(String name);\n"
+" public Bean<?> getPassivationCapableBean(String id);\n"
+" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
" public void validate(InjectionPoint injectionPoint);\n"
" public void fireEvent(Object event, Annotation... qualifiers);\n"
-" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
-" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
-" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
-" public boolean isScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
-" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
-" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
-" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
-" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
-" public Context getContext(Class<? extends Annotation> scopeType);\n"
+" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
+" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
+" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
+" public boolean isScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
+" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
+" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
+" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
+" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
+" public Context getContext(Class<? extends Annotation> scopeType);\n"
" public ELResolver getELResolver();\n"
" public ExpressionFactory wrapExpressionFactory(ExpressionFactory expressionFactory);\n"
-" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
-" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
+" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
+" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
"}"
msgstr ""
@@ -265,7 +265,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's study some of the interfaces exposed by the BeanManager."
+msgid "Let's study some of the interfaces exposed by the BeanManager."
msgstr "扩展Web Bean的神经中枢是 Manager 对象。"
#. Tag: title
@@ -280,21 +280,21 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to instatiate the object itself, and so only method and field injection will be supported."
+msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to insntatiate the object itself, and so only method and field injection will be supported."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"//get the BeanManager from JNDI\n"
-"BeanManager beanManager = (BeanManager) new InitialContext().lookup("java:comp/BeanManager");\n"
+"BeanManager beanManager = (BeanManager) new InitialContext().lookup(\"java:comp/BeanManager\");\n"
"\n"
"//CDI uses an AnnotatedType object to read the annotations of a class\n"
-"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
+"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
"\n"
"//The extension uses an InjectionTarget to delegate instantiation, dependency injection \n"
"//and lifecycle callbacks to the CDI container\n"
-"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
+"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
"\n"
"//each instance needs its own CDI CreationalContext\n"
"CreationalContext ctx = beanManager.createCreationalContext(null);\n"
@@ -324,33 +324,33 @@ msgstr "抽象类 Bean 的实例代表Web Bean。应用中的
#. Tag: para
#, no-c-format
-msgid "The Bean interface exposes all the interesting things we dicussed in ."
+msgid "The Bean interface exposes all the interesting things we discussed in ."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"public interface Bean<T> extends Contextual<T> {\n"
-" public Set<Type> getTypes();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Class<? extends Annotation> getScope();\n"
+"public interface Bean<T> extends Contextual<T> {\n"
+" public Set<Type> getTypes();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Class<? extends Annotation> getScope();\n"
" public String getName();\n"
-" public Set<Class<? extends Annotation>> getStereotypes();\n"
-" public Class<?> getBeanClass();\n"
+" public Set<Class<? extends Annotation>> getStereotypes();\n"
+" public Class<?> getBeanClass();\n"
" public boolean isAlternative();\n"
" public boolean isNullable();\n"
-" public Set<InjectionPoint> getInjectionPoints();\n"
+" public Set<InjectionPoint> getInjectionPoints();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's an easy way to find out what beans exist in the application:"
+msgid "There's an easy way to find out what beans exist in the application:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
+msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
msgstr ""
#. Tag: para
@@ -370,7 +370,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
+msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
msgstr ""
#. Tag: programlisting
@@ -381,49 +381,49 @@ msgid ""
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd, BeanManager bm) {\n"
" \n"
" //use this to read annotations of the class\n"
-" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
+" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
"\n"
" //use this to instantiate the class and inject dependencies\n"
-" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
+" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
"\n"
-" abd.addBean( new Bean<SecurityManager>() {\n"
+" abd.addBean( new Bean<SecurityManager>() {\n"
"\n"
" @Override\n"
-" public Class<?> getBeanClass() {\n"
+" public Class<?> getBeanClass() {\n"
" return SecurityManager.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
" public String getName() {\n"
-" return "securityManager";\n"
+" return \"securityManager\";\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getQualifiers() {\n"
-" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
-" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
-" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
+" public Set<Annotation> getQualifiers() {\n"
+" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
+" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
+" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
" return qualifiers;\n"
" }\n"
"\n"
" @Override\n"
-" public Class<? extends Annotation> getScope() {\n"
+" public Class<? extends Annotation> getScope() {\n"
" return SessionScoped.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Class<? extends Annotation>> getStereotypes() {\n"
+" public Set<Class<? extends Annotation>> getStereotypes() {\n"
" return Collections.emptySet();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypes() {\n"
-" Set<Type> types = new HashSet<Type>();\n"
+" public Set<Type> getTypes() {\n"
+" Set<Type> types = new HashSet<Type>();\n"
" types.add(SecurityManager.class);\n"
" types.add(Object.class);\n"
" return types;\n"
@@ -440,7 +440,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
+" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
" SecurityManager instance = it.produce(ctx);\n"
" it.inject(instance, ctx);\n"
" it.postConstruct(instance);\n"
@@ -449,7 +449,7 @@ msgid ""
"\n"
" @Override\n"
" public void destroy(SecurityManager instance, \n"
-" CreationalContext<SecurityManager> ctx) {\n"
+" CreationalContext<SecurityManager> ctx) {\n"
" it.preDestroy(instance);\n"
" it.dispose(instance);\n"
" ctx.release();\n"
@@ -478,7 +478,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
+msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
msgstr ""
#. Tag: programlisting
@@ -486,38 +486,38 @@ msgstr ""
msgid ""
"public class QualifiedNameExtension implements Extension {\n"
"\n"
-" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
+" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
"\n"
" //wrap this to override the annotations of the class\n"
-" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
+" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
" \n"
-" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
+" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
"\n"
" @Override\n"
-" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
+" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
" return at.getConstructors();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedField<? super X>> getFields() {\n"
+" public Set<AnnotatedField<? super X>> getFields() {\n"
" return at.getFields();\n"
" }\n"
"\n"
" @Override\n"
-" public Class<X> getJavaClass() {\n"
+" public Class<X> getJavaClass() {\n"
" return at.getJavaClass();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
+" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
" return at.getMethods();\n"
" }\n"
"\n"
" @Override\n"
-" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
+" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
" if ( Named.class.equals(annType) ) {\n"
" class NamedLiteral \n"
-" extends AnnotationLiteral<Named> \n"
+" extends AnnotationLiteral<Named> \n"
" implements Named {\n"
" @Override\n"
" public String value() {\n"
@@ -526,7 +526,7 @@ msgid ""
" final String qualifiedName;\n"
" if ( pkg.isAnnotationPresent(Named.class) ) {\n"
" qualifiedName = pkg.getAnnotation(Named.class).value() \n"
-" + '.' + unqualifiedName;\n"
+" + '.' + unqualifiedName;\n"
" }\n"
" else {\n"
" qualifiedName = unqualifiedName;\n"
@@ -542,7 +542,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getAnnotations() {\n"
+" public Set<Annotation> getAnnotations() {\n"
" return at.getAnnotations();\n"
" }\n"
"\n"
@@ -552,12 +552,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypeClosure() {\n"
+" public Set<Type> getTypeClosure() {\n"
" return at.getTypeClosure();\n"
" }\n"
"\n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
" return at.isAnnotationPresent(annType);\n"
" }\n"
" \n"
@@ -571,7 +571,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
+msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
msgstr ""
#. Tag: programlisting
@@ -579,17 +579,17 @@ msgstr ""
msgid ""
"class ServiceAlternativeExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" \n"
-" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
+" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
" \n"
" if ( Service.class.isAssignableFrom( type.getJavaClass() ) ) {\n"
" \n"
" //if the class implements Service, make it an @Alternative\n"
-" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
+" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
" \n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
" return annotationType.equals(Alternative.class) ? \n"
" true : type.isAnnotationPresent(annotationType);\n"
" }\n"
@@ -622,7 +622,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
+msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
msgstr ""
#. Tag: programlisting
@@ -642,25 +642,25 @@ msgstr ""
msgid ""
"public class ConfigExtension implements Extension {\n"
"\n"
-"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
+"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
"\t\t\n"
"\t\t//wrap this to intercept the component lifecycle\n"
-"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
+"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
"\t \n"
-" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
+" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
" \n"
" //use this to read annotations of the class and its members\n"
-" AnnotatedType<X> at = pit.getAnnotatedType();\n"
+" AnnotatedType<X> at = pit.getAnnotatedType();\n"
" \n"
" //read the properties file\n"
-" String propsFileName = at.getClass().getSimpleName() + ".properties";\n"
+" String propsFileName = at.getClass().getSimpleName() + \".properties\";\n"
" InputStream stream = at.getJavaClass().getResourceAsStream(propsFileName);\n"
" if (stream!=null) {\n"
" \n"
" try {\n"
" Properties props = new Properties();\n"
" props.load(stream);\n"
-" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
+" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
" String fieldName = property.getKey().toString();\n"
" Object value = property.getValue();\n"
" try {\n"
@@ -672,7 +672,7 @@ msgid ""
" else {\n"
" //TODO: do type conversion automatically\n"
" pit.addDefinitionError( new InjectionException(\n"
-" "field is not of type String: " + field ) );\n"
+" \"field is not of type String: \" + field ) );\n"
" }\n"
" }\n"
" catch (NoSuchFieldException nsfe) {\n"
@@ -688,14 +688,14 @@ msgid ""
" }\n"
" }\n"
" \n"
-" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
+" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
"\n"
" @Override\n"
-" public void inject(X instance, CreationalContext<X> ctx) {\n"
+" public void inject(X instance, CreationalContext<X> ctx) {\n"
" it.inject(instance, ctx);\n"
" \n"
" //set the values onto the new instance of the component\n"
-" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
+" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
" try {\n"
" configuredValue.getKey().set(instance, configuredValue.getValue());\n"
" }\n"
@@ -721,12 +721,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
-" public X produce(CreationalContext<X> ctx) {\n"
+" public X produce(CreationalContext<X> ctx) {\n"
" return it.produce(ctx);\n"
" }\n"
" \n"
@@ -741,7 +741,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
+msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
msgstr ""
#. Tag: title
@@ -758,9 +758,9 @@ msgstr " Context 接口支持向Web Bean中添加新的范围
#, fuzzy, no-c-format
msgid ""
"public interface Context {\n"
-" public Class<? extends Annotation> getScope();\n"
-" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
-" public <T> T get(Contextual<T> contextual);\n"
+" public Class<? extends Annotation> getScope();\n"
+" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
+" public <T> T get(Contextual<T> contextual);\n"
" boolean isActive();\n"
"}"
msgstr ""
diff --git a/docs/reference/src/main/docbook/zh-CN/gettingstarted.po b/docs/reference/src/main/docbook/zh-CN/gettingstarted.po
index cd6ede524e2..e22fc6353d8 100644
--- a/docs/reference/src/main/docbook/zh-CN/gettingstarted.po
+++ b/docs/reference/src/main/docbook/zh-CN/gettingstarted.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-30 09:39+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, Glassfish 3.0 or any compliant Java EE 6 container."
+msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, GlassFish 3.0 or any compliant Java EE 6 container."
msgstr ""
#. Tag: para
@@ -36,7 +36,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To run the examples with the provided build scripts, you'll need the following:"
+msgid "To run the examples with the provided build scripts, you'll need the following:"
msgstr ""
#. Tag: para
@@ -81,12 +81,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
+msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
+msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
msgstr ""
#. Tag: para
@@ -96,7 +96,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
+msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
msgstr ""
#. Tag: title
@@ -106,19 +106,19 @@ msgstr "使用JBoss AS 5"
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
+msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
+msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> unzip jboss-6.0.*.zip\n"
-"$> mv jboss-6.0.*/ jboss-as-6.0"
+"$> unzip jboss-6.0.*.zip\n"
+"$> mv jboss-6.0.*/ jboss-as-6.0"
msgstr ""
#. Tag: para
@@ -133,7 +133,7 @@ msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
#, fuzzy, no-c-format
-msgid "You're now ready to deploy your first example!"
+msgid "You're now ready to deploy your first example!"
msgstr "现在,你可以部署你的第一个例子了!"
#. Tag: para
@@ -144,22 +144,22 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant deploy"
msgstr ""
"$ cd examples/numberguess\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
+msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/jboss-as-6.0\n"
-"$> ./bin/run.sh"
+"$> cd /path/to/jboss-as-6.0\n"
+"$> ./bin/run.sh"
msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
@@ -168,11 +168,11 @@ msgid "a Windows command window:"
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
-"$> run"
-msgstr ""
+"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
+"$> run"
+msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
#, no-c-format
@@ -227,20 +227,20 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/translator\n"
-"$> ant deploy"
+"$> cd examples/jsf/translator\n"
+"$> ant deploy"
msgstr ""
"$ cd examples/traslator\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
+msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
+msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
msgstr "我们需要在这里做些事情-首先我们需要设置上下文路径为一个不错的URL(http://localhost:8080/webbeans-translator),我们还需要将JBoss AS的类加载器隔离配置激活。"
#. Tag: title
@@ -250,41 +250,43 @@ msgstr "使用Glassfish"
#. Tag: para
#, no-c-format
-msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
+msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
+msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> chmod 755 glassfish-v3-unix.sh\n"
-"$> ./glassfish-v3-unix.sh"
+"$> chmod 755 glassfish-v3-unix.sh\n"
+"$> ./glassfish-v3-unix.sh"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
+msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
+msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
-"$> ant package"
+"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
+"$> ant package"
msgstr ""
+"$ cd examples/numberguess\n"
+"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
+msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
msgstr ""
#. Tag: para
@@ -294,12 +296,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin start-domain domain1"
+msgid "$> asadmin start-domain domain1"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on "Applications", then click on the "Deploy..." button under the heading "Applications" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
+msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on \"Applications\", then click on the \"Deploy...\" button under the heading \"Applications\" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
msgstr ""
#. Tag: para
@@ -309,7 +311,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin deploy target/weld-numberguess.war"
+msgid "$> asadmin deploy target/weld-numberguess.war"
msgstr ""
#. Tag: para
@@ -329,24 +331,24 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
+msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
+msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
msgstr "然后从seamframework.org下载Web Beans的参考实现,然后解压。例如:"
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "$> unzip apache-tomcat-6.0.18.zip"
+msgid "$> unzip apache-tomcat-6.0.18.zip"
msgstr ""
""
#. Tag: para
#, no-c-format
-msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
+msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
msgstr ""
#. Tag: title
@@ -356,7 +358,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
+msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
msgstr ""
#. Tag: programlisting
@@ -366,7 +368,7 @@ msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now you're ready to deploy the numberguess example to Tomcat!"
+msgid "Now you're ready to deploy the numberguess example to Tomcat!"
msgstr "部署猜数字(numberguess)例子:"
#. Tag: para
@@ -377,15 +379,15 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant tomcat.deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant tomcat.deploy"
msgstr ""
"$ cd examples/numberguess\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with "tomcat."."
+msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with \"tomcat.\"."
msgstr ""
#. Tag: para
@@ -410,22 +412,22 @@ msgstr "ant undeploy - 将例子从服务器中移除"
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
+msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/apache-tomcat-6\n"
-"$> ./bin/start.sh"
+"$> cd /path/to/apache-tomcat-6\n"
+"$> ./bin/start.sh"
msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
-"$> start"
-msgstr ""
+"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
+"$> start"
+msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
#, no-c-format
@@ -439,12 +441,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
+msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
+msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
msgstr ""
#. Tag: para
@@ -454,7 +456,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<user username="admin" password="" roles="manager"/>"
+msgid "<user username=\"admin\" password=\"\" roles=\"manager\"/>"
msgstr ""
#. Tag: para
@@ -464,7 +466,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
+msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
msgstr ""
#. Tag: para
@@ -474,7 +476,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn tomcat:redeploy -Ptomcat"
+msgid "$> mvn tomcat:redeploy -Ptomcat"
msgstr ""
#. Tag: para
@@ -489,7 +491,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace tomcat:run -Ptomcat"
+msgid "$> mvn war:inplace tomcat:run -Ptomcat"
msgstr ""
#. Tag: para
@@ -499,12 +501,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Ptomcat"
+msgid "$> mvn compile war:inplace -Ptomcat"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
+msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
msgstr ""
#. Tag: title
@@ -519,12 +521,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
+msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
+msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
msgstr ""
#. Tag: para
@@ -533,11 +535,13 @@ msgid "To run the weld-numberguess example on Jetty, switch t
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> mvn war:inplace jetty:run -Pjetty"
+"$> cd examples/jsf/numberguess\n"
+"$> mvn war:inplace jetty:run -Pjetty"
msgstr ""
+"$ cd examples/numberguess\n"
+"ant deploy"
#. Tag: para
#, no-c-format
@@ -551,7 +555,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Pjetty"
+msgid "$> mvn compile war:inplace -Pjetty"
msgstr ""
#. Tag: para
@@ -561,7 +565,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclispe[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
+msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclipse[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
msgstr ""
#. Tag: para
@@ -571,7 +575,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
+msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
msgstr ""
#. Tag: para
@@ -581,12 +585,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace -Pjetty-ide"
+msgid "$> mvn war:inplace -Pjetty-ide"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using "Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
+msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using \"Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-CN/injection.po b/docs/reference/src/main/docbook/zh-CN/injection.po
index 4e9ab49ee01..31730e44725 100644
--- a/docs/reference/src/main/docbook/zh-CN/injection.po
+++ b/docs/reference/src/main/docbook/zh-CN/injection.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-13 10:08+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "依赖注入"
#. Tag: para
#, no-c-format
-msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
+msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
msgstr ""
#. Tag: title
@@ -146,7 +146,7 @@ msgstr "接下来,Web Bean管理器初始化这个Web bean的所有注入域
#. Tag: para
#, fuzzy, no-c-format
-msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
+msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
msgstr "然后,Web Bean管理器调用这个Web Bean的初始化方法。"
#. Tag: para
@@ -182,7 +182,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
+msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
msgstr ""
#. Tag: title
@@ -192,7 +192,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
+msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
msgstr "Web Beans规范定义了一个称为 类型安全解析算法的过程,当在注入点识别所注入的Web Bean时,Web Bean管理器会遵循这个过程。这个算法初看起来非常复杂,然而你一旦理解了它,它就相当直观。类型安全解析在系统初始化的时候执行,这意味着如果Web Bean的依赖无法被满足的时候,管理器将立刻通知用户,抛出一个 UnsatisfiedDependencyException 异常或者 AmbiguousDependencyException 异常。"
#. Tag: para
@@ -217,12 +217,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
+msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
+msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
msgstr ""
#. Tag: title
@@ -383,7 +383,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you may be thinking, "What's the different between using a qualifier and just specifying the exact implementation class you want?" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alterative implementations of @Asynchronous PaymentProcessor!"
+msgid "Now, you may be thinking, \"What's the different between using a qualifier and just specifying the exact implementation class you want?\" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alternative implementations of @Asynchronous PaymentProcessor!"
msgstr ""
#. Tag: title
@@ -393,7 +393,7 @@ msgstr "简单的Web Bean只支持 @PostConstruct 和 @Default. From time to time, you'll need to decare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
+msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to declare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
msgstr ""
#. Tag: para
@@ -405,7 +405,7 @@ msgstr ""
#, no-c-format
msgid ""
"@Inject \n"
-"void initServices(@Any Instance<Service> services) { \n"
+"void initServices(@Any Instance<Service> services) { \n"
" for (Service service: services) {\n"
" service.init();\n"
" }\n"
@@ -441,7 +441,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then we select one of the possible member values when appling the qualifier:"
+msgid "Then we select one of the possible member values when applying the qualifier:"
msgstr ""
#. Tag: programlisting
@@ -462,7 +462,7 @@ msgid ""
"@Target({METHOD, FIELD, PARAMETER, TYPE})\n"
"public @interface PayBy {\n"
" PaymentMethod value();\n"
-" @Nonbinding String comment() default "";\n"
+" @Nonbinding String comment() default \"\";\n"
"}"
msgstr ""
"this FAQ for step-by-step instructions for how to resolve an ambigous resolution exception between a raw bean type and a producer method that returns the same bean type."
+msgid "See this FAQ for step-by-step instructions for how to resolve an ambiguous resolution exception between a raw bean type and a producer method that returns the same bean type."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Just remember: "There can be only one.""
+msgid "Just remember: \"There can be only one.\""
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
+msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
+msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
msgstr "使用Web Bean依赖注入的时候还需要注意一个问题。"
#. Tag: title
@@ -645,7 +645,7 @@ msgstr "注入的Web Bean的客户通常不会直接拥有这个Web bean实例
#. Tag: para
#, fuzzy, no-c-format
-msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
+msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
msgstr "想象一下如果一个应用范围的Web Bean能够拥有一个请求范围的Web Bean的直接引用。应用范围的Web Bean是被很多不同的请求共享的。但是不同的请求应该看到不同的请求范围的Web Bean实例!"
#. Tag: para
@@ -670,7 +670,7 @@ msgstr "下面的Java类型无法被Web Bean管理器代理:"
#. Tag: para
#, fuzzy, no-c-format
-msgid "classes which don't have a non-private constructor with no parameters, and"
+msgid "classes which don't have a non-private constructor with no parameters, and"
msgstr "没有无参非私有构造器的类,以及"
#. Tag: para
@@ -685,7 +685,7 @@ msgstr "数组和原始类型。"
#. Tag: para
#, no-c-format
-msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
+msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
msgstr ""
#. Tag: para
@@ -695,7 +695,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "change the type of the injection point to Instance<X>,"
+msgid "change the type of the injection point to Instance<X>,"
msgstr ""
#. Tag: para
@@ -725,7 +725,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But we didn't get around to implementing this yet."
+msgid "But we didn't get around to implementing this yet."
msgstr ""
#. Tag: title
@@ -760,7 +760,7 @@ msgstr "应用可以通过注入获得一个 Manager 接口
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -795,7 +795,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -810,19 +810,19 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, we need to obtain an instance of our qualifier type. Since annotatons are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
+msgid "Next, we need to obtain an instance of our qualifier type. Since annotations are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"abstract class AsynchronousQualifier\n"
-"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
+"class AsynchronousQualifier\n"
+"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
msgstr ""
" \n"
@@ -837,14 +837,14 @@ msgstr ""
#, fuzzy, no-c-format
msgid ""
"PaymentProcessor p = paymentProcessorSource\n"
-" .select(new AnnotationLiteral<Asynchronous>() {});"
+" .select(new AnnotationLiteral<Asynchronous>() {});"
msgstr ""
"(){});]]>"
#. Tag: para
#, no-c-format
-msgid "We can't use an anonymous class to implement a qualifier type with members."
+msgid "However, we can't use an anonymous class to implement a qualifier type with members."
msgstr ""
#. Tag: para
@@ -892,7 +892,7 @@ msgstr "一个 @Dependent 范围的Web Bean可以注入一个
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
+msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
msgstr "我们看一个例子。下面的代码很冗长脆弱,有重构问题:"
#. Tag: programlisting
@@ -936,7 +936,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
+msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
msgstr "没被说服?我们还有第二个例子。要注入HTTP参数,我们需要定一个绑定类型:"
#. Tag: programlisting
@@ -964,8 +964,8 @@ msgstr "我们可以在注入点使用这个绑定类型:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@HttpParam("username") String username;\n"
-"@HttpParam("password") String password;"
+"@HttpParam(\"username\") String username;\n"
+"@HttpParam(\"password\") String password;"
msgstr ""
""
@@ -980,7 +980,7 @@ msgstr "下面的生产方法能够完成这个工作:"
msgid ""
"class HttpParams\n"
"\n"
-" @Produces @HttpParam("")\n"
+" @Produces @HttpParam(\"\")\n"
" String getParamValue(InjectionPoint ip) {\n"
" ServletRequest request = (ServletRequest) FacesContext.getCurrentInstance().getExternalContext().getRequest();\n"
" return request.getParameter(ip.getAnnotated().getAnnotation(HttpParam.class).value());\n"
@@ -999,7 +999,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own prodcuer for the request and have it injected as a method parameter."
+msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own producer for the request and have it injected as a method parameter."
msgstr ""
#. Tag: para
@@ -1017,8 +1017,8 @@ msgstr "Web Bean管理器提供一个内置的实现 InjectionPoint\n"
"Language-Team: none\n"
@@ -107,7 +107,7 @@ msgstr "拦截器绑定"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
+msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
msgstr "假定我们想声明我们的某些Web Beans是事务性的。我们要做的第一个事情就是需要一个 拦截器绑定注释 以便指定哪些Web Beans是事务性的:"
#. Tag: programlisting
@@ -160,7 +160,7 @@ msgstr "实现拦截器"
#. Tag: para
#, fuzzy, no-c-format
-msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
+msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
msgstr "很好,但是在代码中有些地方需要我们实现提供事务管理的拦截器。我们需要做的事情就是创建一个标准的EJB拦截器,使用 @Interceptor 和 @Transactional注释它。"
#. Tag: programlisting
@@ -222,16 +222,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -262,17 +262,17 @@ msgstr "例如,我们可以指定在 TransactionInterceptor
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -375,7 +375,7 @@ msgstr "通常我们可以组合拦截器绑定类型将多个拦截器绑定到
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Secure(rolesAllowed="admin") @Transactional\n"
+"@Secure(rolesAllowed=\"admin\") @Transactional\n"
"public class ShoppingCart { ... }"
msgstr ""
"meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
+msgid "Well, fortunately, CDI works around this missing feature of Java. We may annotate one interceptor binding type with other interceptor binding types (termed a meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
msgstr "不过幸运的是,Web Beans能够解决这个Java缺失的特性。我们可以向一个拦截器绑定类型注释另一个拦截器绑定类型。拦截器绑定是具有传递性的 拥有第一个拦截器绑定的任何Web Bean都继承被声明为元注释的拦截器绑定。"
#. Tag: programlisting
@@ -530,7 +530,7 @@ msgstr "拦截器可能无法轻松地在部署期间关闭,并且"
#. Tag: para
#, fuzzy, 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."
+msgid "the interceptor ordering is non-global — it is determined by the order in which interceptors are listed at the class level."
msgstr "拦截器的顺序是非全局性的 它由在类级别上列出的拦截器的顺序决定。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-CN/intro.po b/docs/reference/src/main/docbook/zh-CN/intro.po
index 602a22646de..68b498b146c 100644
--- a/docs/reference/src/main/docbook/zh-CN/intro.po
+++ b/docs/reference/src/main/docbook/zh-CN/intro.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-30 09:14+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
+msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
msgstr "你是否已经迫不及待想要开始编写你的第一个Web Bean了?或许,你仍旧抱有怀疑态度,想要知道Web Beans规范会给出什么样的圈套让你跳。好消息是你也许已经编写并且使用了好几百个或者好几千个Web Bean了。你也许甚至想不起来你写的第一个Web Bean了。"
#. Tag: title
@@ -36,27 +36,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Prior to Java EE 6, there was no clear definition of the term "bean" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications "beans" for years. There were even a couple of different kinds of things called "beans" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a "bean". What we've been missing is a common definition."
+msgid "Prior to Java EE 6, there was no clear definition of the term \"bean\" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications \"beans\" for years. There were even a couple of different kinds of things called \"beans\" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a \"bean\". What we've been missing is a common definition."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
+msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
+msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
+msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now let's see how to create your first bean that actually uses CDI."
+msgid "Now let's see how to create your first bean that actually uses CDI."
msgstr ""
#. Tag: title
@@ -66,14 +66,14 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
+msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
msgstr "假定我们有两个已经写好的Java类,我们已经在不同的应用中使用它们好多年了。第一个类将一个字符串解析为一个句子列表:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
"public class SentenceParser {\n"
-" public List<String> parse(String text) { ... }\n"
+" public List<String> parse(String text) { ... }\n"
"}"
msgstr ""
"TextTranslator并没有一个无
#. Tag: para
#, fuzzy, no-c-format
-msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
+msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
msgstr "就像你猜到的一样, @Initializer注释和依赖注入有关! @Initializer可以应用到一个Web Bean的构造器或者方法上,它告诉Web Bean管理器在初始化一个Web Bean的时候去调用这个构造器或者方法。Web Beam管理器能够将其他的Web Bean注入到构造器或者方法的参数中。"
#. Tag: para
@@ -181,7 +181,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
+msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
msgstr ""
#. Tag: programlisting
@@ -220,7 +220,7 @@ msgstr "Translator是本地接口:"
#. Tag: para
#, no-c-format
-msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
+msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
msgstr ""
#. Tag: para
@@ -231,7 +231,7 @@ msgstr "通过将其注入到一个Web Bean,Servlet或者EJB,我们能够获
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
+"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
"...\n"
"public void translate() {\n"
" textTranslatorInstance.get().translate(inputText);\n"
@@ -244,17 +244,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
+msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
+msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
msgstr "在系统初始化的时候,Web Bean管理器必须验证只存在一个Web Bean能够满足每个注入点。在我们的例子中,如果没有Translator实现如果SentenceTranslator EJB没有被部署Web Bean管理器将会抛出一个UnsatisfiedDependencyException异常。如果多于一个Translator实现,Web Bean管理器将会抛出一个AmbiguousDependencyException异常。"
#. Tag: para
#, no-c-format
-msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
+msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
msgstr ""
#~ msgid "Getting started with Web Beans"
diff --git a/docs/reference/src/main/docbook/zh-CN/next.po b/docs/reference/src/main/docbook/zh-CN/next.po
index 9707917b5af..0660bd087fe 100644
--- a/docs/reference/src/main/docbook/zh-CN/next.po
+++ b/docs/reference/src/main/docbook/zh-CN/next.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-23 16:53+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -21,12 +21,12 @@ msgstr "下一步"
#. Tag: para
#, no-c-format
-msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
+msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
+msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
msgstr "Web Bean参考实现正在http://seamframework.org/WebBeans项目中开发。参考实现的开发团队和Web Bean规范领导的博客位于http://in.relation.to。本篇文章的撰写完全基于先前发表在那里的一系列博客文章。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-CN/part1.po b/docs/reference/src/main/docbook/zh-CN/part1.po
index bb1b992899b..db7249725fe 100644
--- a/docs/reference/src/main/docbook/zh-CN/part1.po
+++ b/docs/reference/src/main/docbook/zh-CN/part1.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-22 10:45+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -126,7 +126,7 @@ msgstr "我需要显式地销毁它么?"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Where should I keep the reference to it when I'm not currently using it?"
+msgid "Where should I keep the reference to it when I'm not currently using it?"
msgstr "当我不再直接使用它的时候,我需要将它的引用保存到哪里?"
#. Tag: para
@@ -141,7 +141,7 @@ msgstr "我应该如何在其他对象中共享这个对象?"
#. Tag: para
#, no-c-format
-msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
+msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
msgstr ""
#. Tag: para
@@ -171,12 +171,12 @@ msgstr "装饰器允许开发者划分业务关注点。"
#. Tag: para
#, fuzzy, no-c-format
-msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
+msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
msgstr "最重要的是,Web Beans以一种类型安全的方式提供所有的特性。Web Beans从来不使用基于字符串的标识符来决定交互的对象如何关联在一起。至于XML, 虽然它仍旧是一个选项,但也可以几乎不使用。取而代之,Web Bean使用Java对象模型的类型信息和一种新的绑定注释模式将Web Beans和它们的依赖以及拦截器,装饰器和事件消费者关联在一起。"
#. Tag: para
#, no-c-format
-msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
+msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
msgstr ""
#. Tag: para
@@ -186,7 +186,7 @@ msgstr "Web Beans甚至提供了必要的整合点,以便未来的Java EE规
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
+msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
msgstr "Web Beans受到了包括Seam, Guice和Spring在内的很多现有的Java框架的影响。然而,Web Beans具有自己鲜明的特性:在类型安全方面优于Seam,比Spring更加具备状态和使用更少的XML, 比Guice更加具备Web和企业应用的能力。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-CN/part3.po b/docs/reference/src/main/docbook/zh-CN/part3.po
index 3d194005944..1ba8060856f 100644
--- a/docs/reference/src/main/docbook/zh-CN/part3.po
+++ b/docs/reference/src/main/docbook/zh-CN/part3.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-23 17:29+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
+msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
msgstr ""
#. Tag: para
@@ -71,7 +71,7 @@ msgstr "Web Bean的第二个宗旨是强类型。Web Bean
#. Tag: para
#, fuzzy, no-c-format
-msgid "You don't see string-based identifiers in CDI 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!"
+msgid "You don't see string-based identifiers in CDI 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
@@ -141,7 +141,7 @@ msgstr "Web Beans的模板是这种思想的延伸。一个
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
+msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
msgstr "我们现在可以接触Web Bean中更加高级的特性了。要记住这些特性能够让我们的代码不仅更容易验证,也更容易理解。大部分时间,你根本不需要这些特性,但是如果你能聪明地运用它们的话,你将充分体会到它们的强大。"
#~ msgid "Even Web Beans XML metadata is strongly typed! There's no compiler for XML, so Web Beans takes advantage of XML schemas to validate the Java types and attributes that appear in XML. This approach turns out to make the XML more literate, just like annotations made our Java code more literate."
diff --git a/docs/reference/src/main/docbook/zh-CN/part4.po b/docs/reference/src/main/docbook/zh-CN/part4.po
index 3538715eea6..71a4f3f23c9 100644
--- a/docs/reference/src/main/docbook/zh-CN/part4.po
+++ b/docs/reference/src/main/docbook/zh-CN/part4.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2008-12-23 17:48+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
+msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
msgstr ""
#. Tag: para
@@ -26,7 +26,7 @@ msgstr "我们已经看到了Web Bean如何帮助整合EJB和JSF, 允许我们
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
+msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
msgstr "我们已经看到了如何在应用中使用Web Bean来充分利用Java EE平台。我们也粗略地看到了一些能够支持Web Bean的便携性扩展点的SPI。你也许永远不回直接使用这些SPI,但是,知道在需要的时候你可以使用它们很有好处。最重要的是,每次你使用一个第三方扩展的时候,都有可能间接地利用了它们。"
#~ msgid "The third theme of Web Beans is integration. Web Beans was designed to work in concert with other technologies, helping the application developer fit the other technologies together. Web Beans is an open technology. It forms a part of the Java EE ecosystem, and is itself the foundation for a new ecosystem of portable extensions and integration with existing frameworks and technologies."
diff --git a/docs/reference/src/main/docbook/zh-CN/part5.po b/docs/reference/src/main/docbook/zh-CN/part5.po
index 6f9a6888a63..dbbb6ebb70b 100644
--- a/docs/reference/src/main/docbook/zh-CN/part5.po
+++ b/docs/reference/src/main/docbook/zh-CN/part5.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-28 17:09+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and Glassfish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
+msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and GlassFish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-CN/producermethods.po b/docs/reference/src/main/docbook/zh-CN/producermethods.po
index d3548bc82e5..85828845a6d 100644
--- a/docs/reference/src/main/docbook/zh-CN/producermethods.po
+++ b/docs/reference/src/main/docbook/zh-CN/producermethods.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-12 11:20+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "生产者方法"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
+msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
msgstr "生产者方法能够让我们克服使用Web Bean管理器代替应用来负责实例化对象所带来的特定的限制。生产者方法也是将非Web Beans的对象整合到Web Beans环境中的最简单的途径。(我们将在讨论第二种方法)"
#. Tag: para
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
+msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
msgstr ""
#. Tag: programlisting
@@ -158,7 +158,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
+msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
msgstr "现在,当这个生产者方法被调用时,它返回的 PaymentStrategy 对象将被绑定到会话上下文中。这个生产者方法在同一个会话范围中不会被再次调用。"
#. Tag: para
@@ -173,12 +173,12 @@ msgstr "注入到生产者方法中"
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
+msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
msgstr "上面的代码有一个潜在的问题。 CreditCardPaymentStrategy 的实现使用Java的 new 操作符来实例化。应用直接实例化的对象无法获得依赖注入的好处,也无法获得拦截器。"
#. Tag: para
#, fuzzy, no-c-format
-msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
+msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
msgstr "如果这不是我们想要的,我们可以对生产者方法使用依赖注入来获得Web Bean实例:"
#. Tag: programlisting
@@ -210,12 +210,12 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of "promoting" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left "hanging" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
+msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of \"promoting\" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left \"hanging\" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
msgstr "等一下,如果 CreditCardPaymentStrategy 是一个请求范围的Web Bean,那会怎样?生产者方法将会把当前请求范围的实例\"提升\"到会话范围。这近乎是一个Bug!请求范围的对象会在会话结束前被Web Bean管理器销毁,但是这个对象的引用将被 \"悬挂\"在会话范围。Web Bean管理器不会检测到这种错误,因此使用生产者方法返回Web bean实例的时候一定要多加小心!"
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
+msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
msgstr "我们至少有三种方式来解决这个Bug。我们可以改变 CreditCardPaymentStrategy实现的范围,但是这种方法将影响到其他使用这个Web Bean的客户。一个更好的选择是将生产者方法的范围更改到 @Dependent 或者 @RequestScoped。"
#. Tag: para
@@ -262,7 +262,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
+msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
msgstr "一个新的依赖的 CreditCardPaymentStrategy 实例将被创建,然后传递给生产者方法,然后生产者方法将其返回,最终这个实例将被绑定到会话上下文。这个依赖对象不会被提前销毁,而是在会话结束时跟随 Preferences 一起被销毁。"
#. Tag: title
diff --git a/docs/reference/src/main/docbook/zh-CN/resources.po b/docs/reference/src/main/docbook/zh-CN/resources.po
index 4eb7f41ba5d..b2eb00cf6ab 100644
--- a/docs/reference/src/main/docbook/zh-CN/resources.po
+++ b/docs/reference/src/main/docbook/zh-CN/resources.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a nonportable "mapped name"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
+msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a non-portable \"mapped name\"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
msgstr ""
#. Tag: para
@@ -72,35 +72,35 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @WebServiceRef(lookup="java:app/service/Catalog")\n"
+"@Produces @WebServiceRef(lookup=\"java:app/service/Catalog\")\n"
"Catalog catalog;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @Resource(lookup="java:global/env/jdbc/CustomerDatasource") \n"
+"@Produces @Resource(lookup=\"java:global/env/jdbc/CustomerDatasource\") \n"
"@CustomerDatabase Datasource customerDatabase;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceContext(unitName="CustomerDatabase")\n"
+"@Produces @PersistenceContext(unitName=\"CustomerDatabase\")\n"
"@CustomerDatabase EntityManager customerDatabasePersistenceContext;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceUnit(unitName="CustomerDatabase") \n"
+"@Produces @PersistenceUnit(unitName=\"CustomerDatabase\") \n"
"@CustomerDatabase EntityManagerFactory customerDatabasePersistenceUnit;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @EJB(ejbLink="../their.jar#PaymentService") \n"
+"@Produces @EJB(ejbLink=\"../their.jar#PaymentService\") \n"
"PaymentService paymentService;"
msgstr ""
@@ -126,7 +126,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
+msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
msgstr ""
#. Tag: title
@@ -171,7 +171,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
+msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
msgstr ""
#. Tag: programlisting
@@ -186,7 +186,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@PersistenceContext(unitName="CustomerDatabase") EntityManager"
+msgid "@PersistenceContext(unitName=\"CustomerDatabase\") EntityManager"
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-CN/ri-spi.po b/docs/reference/src/main/docbook/zh-CN/ri-spi.po
index eacecf7c5c8..32725ea98d7 100644
--- a/docs/reference/src/main/docbook/zh-CN/ri-spi.po
+++ b/docs/reference/src/main/docbook/zh-CN/ri-spi.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-27 13:50+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -31,7 +31,7 @@ msgstr "资源加载"
#. Tag: para
#, no-c-format
-msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the "Weld: Servlets" extension will be sufficient, and will work in any container supporting the Servlet API."
+msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the \"Weld: Servlets\" extension will be sufficient, and will work in any container supporting the Servlet API."
msgstr ""
#. Tag: para
@@ -56,7 +56,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
+msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
msgstr ""
#. Tag: para
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
+msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
msgstr ""
#. Tag: para
@@ -96,7 +96,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
+msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
msgstr ""
#. Tag: para
@@ -106,12 +106,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
+msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
+msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
msgstr ""
#. Tag: para
@@ -126,7 +126,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
+msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
msgstr ""
#. Tag: para
@@ -156,7 +156,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
+msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
msgstr ""
#. Tag: para
@@ -196,7 +196,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
+msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
msgstr ""
#. Tag: title
@@ -211,7 +211,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
+msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
msgstr ""
#. Tag: para
@@ -276,7 +276,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); intercepter will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
+msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); interceptor will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
msgstr ""
#. Tag: para
@@ -351,7 +351,7 @@ msgstr "应用上下文"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
+msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
msgstr "Web Bean期望应用服务器或者其他容器能够提供每个应用上下文的存储。org.jboss.webbeans.context.api.BeanStore 应该被实现以便提供一个应用范围的存储。你也许会发现 org.jboss.webbeans.context.api.helpers.ConcurrentHashMapBeanStore 非常有用。"
#. Tag: title
@@ -366,7 +366,7 @@ msgstr " org.jboss.webbeans.bootstrap.api.Bootstrap 接口定
#. Tag: para
#, fuzzy, no-c-format
-msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programtically, or built in). Bean validation will validate all beans."
+msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programmatically, or built in). Bean validation will validate all beans."
msgstr "自举可以划分为阶段,自举初始化和自举。初始化将创建一个管理器,添加标准(规范定义的)的上下文。自举将发现EJB,类和XML;添加注释定义的Bean;添加XML定义的Bean;和验证所有的Bean。"
#. Tag: para
@@ -426,7 +426,7 @@ msgstr "类加载器隔离"
#. Tag: para
#, fuzzy, no-c-format
-msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuation, classloader isolation for each CDI application."
+msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuration, classloader isolation for each CDI application."
msgstr "如果你将一个Web Bean参考实现整合到一个支持多应用部署的环境中,你需要以用户配置或者自动化方式为每个Web Bean应用激活类加载器隔离。"
#. Tag: term
@@ -441,7 +441,7 @@ msgstr "如果你将Web Bean整合到一个Servlet环境中,对每个使用Ser
#. Tag: para
#, no-c-format
-msgid "You must ensure that that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
+msgid "You must ensure that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
msgstr ""
#. Tag: term
@@ -582,7 +582,7 @@ msgid ""
"InjectionTarget it = weldBeanManager.fireProcessInjectionTarget(clazz);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
+"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
"\n"
"// Produce the instance, performing any constructor injection required\n"
"Object instance = it.produce();\n"
@@ -616,16 +616,16 @@ msgstr ""
msgid ""
"// Obtain the EjbDescriptor for the EJB\n"
"// You may choose to use this utility method to get the descriptor\n"
-"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
+"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
"\n"
"// Get an the Bean object\n"
-"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
+"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
"\n"
"// Create the injection target\n"
"InjectionTarget it = deploymentBeanManager.createInjectionTarget(ejbDescriptor);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
+"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
"\n"
"// Perform injection and call initializers\n"
"it.inject(instance, cc);\n"
diff --git a/docs/reference/src/main/docbook/zh-CN/scopescontexts.po b/docs/reference/src/main/docbook/zh-CN/scopescontexts.po
index 22843bea66b..3eaa6688d72 100644
--- a/docs/reference/src/main/docbook/zh-CN/scopescontexts.po
+++ b/docs/reference/src/main/docbook/zh-CN/scopescontexts.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-30 09:18+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr "范围和上下文"
#. Tag: para
#, fuzzy, no-c-format
-msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
+msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
msgstr "目前为止,我们已经看到了几个 范围类型注释的例子。Web Bean的范围决定了Web Bean实例的生命周期。范围还决定了哪个客户端引用了哪个Web Bean实例。根据Web Beans规范,一个范围决定:"
#. Tag: para
@@ -46,7 +46,7 @@ msgstr "例如,如果我们有一个会话范围的Web Bean:Current
#. Tag: para
#, no-c-format
-msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
+msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
msgstr ""
#. Tag: title
@@ -56,7 +56,7 @@ msgstr "范围类型"
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
+msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
msgstr "Web Bean有一个特性是可扩展的上下文模型。我们可以创建一个新的范围类型注释来定一个新的范围:"
#. Tag: programlisting
@@ -74,7 +74,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
+msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
msgstr "当然,这是这项工作最简单的部分。为了让这个范围类型可以使用,我们还需要定义一个Context(上下文)对象来实现这个范围!实现上下文通常是一个非常具备挑战的技术任务,这常常只能由开发编程框架的专家完成。"
#. Tag: para
@@ -93,7 +93,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Usually, you'll use one of CDI's built-in scopes."
+msgid "Usually, you'll use one of CDI's built-in scopes."
msgstr "通常,你将会使用一个Web Bean内置的范围。"
#. Tag: title
@@ -193,7 +193,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
+msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
msgstr "这四个内置范围的其中三个对于每个Java EE程序员来说都非常熟悉,所以让我们别浪费时间来讨论他们。不过有一个范围是新的。"
#. Tag: title
@@ -218,7 +218,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
+msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
msgstr "从用户角度出发,一个对话代表一个任务,或者一个工作单元。用户当前工作相关的状态由对话上下文维护。如果用户同时处理多个事情,就会有多个对话与之对应。"
#. Tag: para
@@ -341,25 +341,25 @@ msgstr "因此,下面的链接能够传播对话:"
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "<a href="/addProduct.jsp?cid=#{conversation.id}">Add Product</a>"
+msgid "<a href=\"/addProduct.jsp?cid=#{conversation.id}\">Add Product</a>"
msgstr "Add Product]]>"
#. Tag: para
#, no-c-format
-msgid "It's probably better to use one of the link components in JSF 2:"
+msgid "It's probably better to use one of the link components in JSF 2:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:link outcome="/addProduct.xhtml" value="Add Product">\n"
-" <f:param name="cid" value="#{javax.enterprise.context.conversation.id}"/>\n"
-"</h:link>"
+"<h:link outcome=\"/addProduct.xhtml\" value=\"Add Product\">\n"
+" <f:param name=\"cid\" value=\"#{javax.enterprise.context.conversation.id}\"/>\n"
+"</h:link>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a "flash" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
+msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a \"flash\" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
msgstr "Web Bean管理器也需要能够跨越任何重定向来传播对话,甚至这个对话没有被升级为长时对话。这样我们就能很容易实现常用的POST-then-redirect模式,而不需要构建一个脆弱的 \"闪存\"对象。在这个例子中,Web Bean管理器自动向重定向URL中添加一个请求参数。"
#. Tag: title
@@ -369,7 +369,7 @@ msgstr "对话超时"
#. Tag: para
#, fuzzy, no-c-format
-msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
+msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
msgstr "Web Bean管理器可以在任何时候销毁一个对话及其上下文中维护的所有状态,这样的设计可以降低资源的消耗。一个Web Bean管理器的实现将根据超时设置自动的完成上述任务,虽然这个特性在Web Bean规范中没有要求。超时指的是对话被销毁前的非激活时间。"
#. Tag: para
@@ -399,12 +399,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can guess what "singleton" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
+msgid "You can guess what \"singleton\" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
+msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
msgstr ""
#. Tag: para
@@ -424,7 +424,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
+msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
msgstr ""
#. Tag: para
@@ -464,12 +464,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
+msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
+msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
msgstr ""
#. Tag: para
@@ -538,7 +538,7 @@ msgstr "calculator域有一个对话范围的Calcula
#. Tag: para
#, fuzzy, no-c-format
-msgid "This feature is particularly useful with producer methods, as we'll see in the next chapter."
+msgid "This feature is particularly useful with producer methods, as we'll see in ."
msgstr "这个特性对于生产者方法来说特别有用,我们将在下一章看到。"
#~ msgid "@RequestScoped"
diff --git a/docs/reference/src/main/docbook/zh-CN/specialization.po b/docs/reference/src/main/docbook/zh-CN/specialization.po
index 1fd716a2fe9..57d84a89255 100644
--- a/docs/reference/src/main/docbook/zh-CN/specialization.po
+++ b/docs/reference/src/main/docbook/zh-CN/specialization.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-13 16:32+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
+msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
msgstr ""
#. Tag: para
@@ -41,12 +41,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
+msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
+msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
msgstr ""
#. Tag: title
@@ -75,7 +75,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
+msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
msgstr "但在我们的阶段开发环境中,我们可以使用一个不同的Web Bean来重载这个PaymentProcessor 实现:"
#. Tag: programlisting
@@ -115,12 +115,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
+msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
+msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
msgstr ""
#. Tag: programlisting
@@ -161,16 +161,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <alternatives>\n"
-" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
-" </alternatives>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <alternatives>\n"
+" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
+" </alternatives>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
+msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
msgstr ""
#. Tag: para
@@ -255,7 +255,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
+msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-CN/stereotypes.po b/docs/reference/src/main/docbook/zh-CN/stereotypes.po
index 69477fedd65..f9786d8cc9e 100644
--- a/docs/reference/src/main/docbook/zh-CN/stereotypes.po
+++ b/docs/reference/src/main/docbook/zh-CN/stereotypes.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: master.xml\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-13 16:04+0800\n"
"Last-Translator: Sean Wu \n"
"Language-Team: none\n"
@@ -99,7 +99,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
+msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
msgstr ""
#. Tag: title
@@ -142,7 +142,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
+msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
msgstr ""
#. Tag: title
@@ -262,12 +262,12 @@ msgstr "模板"
#. Tag: para
#, no-c-format
-msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
+msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
+msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
msgstr ""
#. Tag: programlisting
@@ -294,7 +294,7 @@ msgstr "标准的模板"
#. Tag: para
#, fuzzy, no-c-format
-msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
+msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
msgstr "我们已经见到了Web Bean规范定义的两个标准的模板:@Interceptor 和 @Decorator。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-CN/weldexamples.po b/docs/reference/src/main/docbook/zh-CN/weldexamples.po
index 4f34b3e5fe7..9b823bc12db 100644
--- a/docs/reference/src/main/docbook/zh-CN/weldexamples.po
+++ b/docs/reference/src/main/docbook/zh-CN/weldexamples.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
+msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
msgstr ""
#. Tag: title
@@ -31,75 +31,75 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
+msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
+msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
+msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<faces-config version="2.0"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<faces-config version=\"2.0\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd">\n"
-"</faces-config>"
+" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd\">\n"
+"</faces-config>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
+msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, there's the familiar web.xml:"
+msgid "Finally, there's the familiar web.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<web-app version="2.5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<web-app version=\"2.5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd\">\n"
" \n"
-" <display-name>weld-jsf-numberguess-war</display-name>\n"
-" <description>Weld JSF numberguess example (war)</description>\n"
+" <display-name>weld-jsf-numberguess-war</display-name>\n"
+" <description>Weld JSF numberguess example (war)</description>\n"
"\n"
-" <servlet>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
-" <load-on-startup>1</load-on-startup>\n"
-" </servlet>\n"
+" <servlet>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
+" <load-on-startup>1</load-on-startup>\n"
+" </servlet>\n"
"\n"
-" <servlet-mapping>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <url-pattern>*.jsf</url-pattern>\n"
-" </servlet-mapping>\n"
+" <servlet-mapping>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <url-pattern>*.jsf</url-pattern>\n"
+" </servlet-mapping>\n"
" \n"
-" <context-param>\n"
-" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
-" <param-value>.xhtml</param-value>\n"
-" </context-param>\n"
+" <context-param>\n"
+" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
+" <param-value>.xhtml</param-value>\n"
+" </context-param>\n"
"\n"
-" <session-config>\n"
-" <session-timeout>10</session-timeout>\n"
-" </session-config>\n"
+" <session-config>\n"
+" <session-timeout>10</session-timeout>\n"
+" </session-config>\n"
"\n"
-"</web-app>"
+"</web-app>"
msgstr ""
#. Tag: para
@@ -129,51 +129,51 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
+msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"\n"
-" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">\n"
-"<html xmlns="http://www.w3.org/1999/xhtml"\n"
-" xmlns:ui="http://java.sun.com/jsf/facelets"\n"
-" xmlns:h="http://java.sun.com/jsf/html"\n"
-" xmlns:f="http://java.sun.com/jsf/core">\n"
+"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
+" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n"
+"<html xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" xmlns:ui=\"http://java.sun.com/jsf/facelets\"\n"
+" xmlns:h=\"http://java.sun.com/jsf/html\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\">\n"
"\n"
-" <ui:composition template="/template.xhtml">\n"
-" <ui:define name="content">\n"
-" <h1>Guess a number...</h1>\n"
-" <h:form id="numberGuess">\n"
-" <div style="color: red">\n"
-" <h:messages id="messages" globalOnly="false"/>\n"
-" <h:outputText id="Higher" value="Higher!"\n"
-" rendered="#{game.number gt game.guess and game.guess ne 0}"/>\n"
-" <h:outputText id="Lower" value="Lower!"\n"
-" rendered="#{game.number lt game.guess and game.guess ne 0}"/>\n"
-" </div>\n"
+" <ui:composition template=\"/template.xhtml\">\n"
+" <ui:define name=\"content\">\n"
+" <h1>Guess a number...</h1>\n"
+" <h:form id=\"numberGuess\">\n"
+" <div style=\"color: red\">\n"
+" <h:messages id=\"messages\" globalOnly=\"false\"/>\n"
+" <h:outputText id=\"Higher\" value=\"Higher!\"\n"
+" rendered=\"#{game.number gt game.guess and game.guess ne 0}\"/>\n"
+" <h:outputText id=\"Lower\" value=\"Lower!\"\n"
+" rendered=\"#{game.number lt game.guess and game.guess ne 0}\"/>\n"
+" </div>\n"
" \n"
-" <div>\n"
-" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
+" <div>\n"
+" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
" You have #{game.remainingGuesses} guesses remaining.\n"
-" </div>\n"
+" </div>\n"
" \n"
-" <div>\n"
+" <div>\n"
" Your guess: \n"
-" <h:inputText id="inputGuess" value="#{game.guess}"\n"
-" size="3" required="true" disabled="#{game.number eq game.guess}"\n"
-" validator="#{game.validateNumberRange}"/>\n"
-" <h:commandButton id="guessButton" value="Guess" \n"
-" action="#{game.check}" disabled="#{game.number eq game.guess}"/>\n"
-" </div>\n"
-" <div>\n"
-" <h:commandButton id="restartButton" value="Reset" action="#{game.reset}" immediate="true"/>\n"
-" </div>\n"
-" </h:form>\n"
-" </ui:define>\n"
-" </ui:composition>\n"
-"</html>"
+" <h:inputText id=\"inputGuess\" value=\"#{game.guess}\"\n"
+" size=\"3\" required=\"true\" disabled=\"#{game.number eq game.guess}\"\n"
+" validator=\"#{game.validateNumberRange}\"/>\n"
+" <h:commandButton id=\"guessButton\" value=\"Guess\" \n"
+" action=\"#{game.check}\" disabled=\"#{game.number eq game.guess}\"/>\n"
+" </div>\n"
+" <div>\n"
+" <h:commandButton id=\"restartButton\" value=\"Reset\" action=\"#{game.reset}\" immediate=\"true\"/>\n"
+" </div>\n"
+" </h:form>\n"
+" </ui:define>\n"
+" </ui:composition>\n"
+"</html>"
msgstr ""
#. Tag: para
@@ -183,7 +183,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are a number of messages which can be sent to the user, "Higher!", "Lower!" and "Correct!""
+msgid "There are a number of messages which can be sent to the user, \"Higher!\", \"Lower!\" and \"Correct!\""
msgstr ""
#. Tag: para
@@ -198,7 +198,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
+msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
msgstr ""
#. Tag: para
@@ -266,7 +266,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Generator is application scoped, so we don't get a different random each time."
+msgid "The Generator is application scoped, so we don't get a different random each time."
msgstr ""
#. Tag: para
@@ -276,12 +276,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
+msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
+msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
msgstr ""
#. Tag: programlisting
@@ -298,19 +298,19 @@ msgid ""
" private int remainingGuesses;\n"
"\n"
" @Inject @MaxNumber private int maxNumber;\n"
-" @Inject @Random Instance<Integer> randomNumber;\n"
+" @Inject @Random Instance<Integer> randomNumber;\n"
" \n"
" public Game() {}\n"
" \n"
" public void check() {\n"
-" if (guess > number) {\n"
+" if (guess > number) {\n"
" biggest = guess - 1;\n"
" }\n"
-" else if (guess < number) {\n"
+" else if (guess < number) {\n"
" smallest = guess + 1;\n"
" }\n"
" else if (guess == number) {\n"
-" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage("Correct!"));\n"
+" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage(\"Correct!\"));\n"
" }\n"
" remainingGuesses--;\n"
" }\n"
@@ -325,18 +325,18 @@ msgid ""
" }\n"
" \n"
" public void validateNumberRange(FacesContext context, UIComponent toValidate, Object value) {\n"
-" if (remainingGuesses <= 0) {\n"
-" FacesMessage message = new FacesMessage("No guesses left!");\n"
+" if (remainingGuesses <= 0) {\n"
+" FacesMessage message = new FacesMessage(\"No guesses left!\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" ((UIInput) toValidate).setValid(false);\n"
" return;\n"
" }\n"
" int input = (Integer) value;\n"
"\n"
-" if (input < smallest || input > biggest) {\n"
+" if (input < smallest || input > biggest) {\n"
" ((UIInput) toValidate).setValid(false);\n"
"\n"
-" FacesMessage message = new FacesMessage("Invalid guess");\n"
+" FacesMessage message = new FacesMessage(\"Invalid guess\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" }\n"
" }\n"
@@ -385,20 +385,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
+msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
+msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
msgstr ""
#. Tag: title
@@ -418,17 +418,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin ."
+msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects . Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
+msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects. Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This will create a project in your workspace called weld-se-numberguess ."
+msgid "This will create a project in your workspace called weld-se-numberguess."
msgstr ""
#. Tag: para
@@ -438,7 +438,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to get the example running!"
+msgid "It's time to get the example running!"
msgstr ""
#. Tag: title
@@ -448,12 +448,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
+msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right click on the project, and choose Run As -> Run As Application:"
+msgid "Right click on the project, and choose Run As -> Run As Application:"
msgstr ""
#. Tag: para
@@ -503,7 +503,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's have a look at the significant code and configuration files that make up this example."
+msgid "Let's have a look at the significant code and configuration files that make up this example."
msgstr ""
#. Tag: para
@@ -513,7 +513,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
+msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
msgstr ""
#. Tag: programlisting
@@ -558,7 +558,7 @@ msgid ""
"\n"
" public boolean isGameLost()\n"
" {\n"
-" return guess != number && remainingGuesses <= 0;\n"
+" return guess != number && remainingGuesses <= 0;\n"
" }\n"
"\n"
" public boolean check()\n"
@@ -567,12 +567,12 @@ msgid ""
"\n"
" if (checkNewNumberRangeIsValid())\n"
" {\n"
-" if (guess > number)\n"
+" if (guess > number)\n"
" {\n"
" biggest = guess - 1;\n"
" }\n"
"\n"
-" if (guess < number)\n"
+" if (guess < number)\n"
" {\n"
" smallest = guess + 1;\n"
" }\n"
@@ -590,7 +590,7 @@ msgid ""
"\n"
" private boolean checkNewNumberRangeIsValid()\n"
" {\n"
-" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
+" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
" }\n"
"\n"
" @PostConstruct\n"
@@ -607,12 +607,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
+msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
+msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
msgstr ""
#. Tag: para
@@ -642,12 +642,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
+msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
+msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
msgstr ""
#. Tag: programlisting
@@ -660,11 +660,11 @@ msgid ""
"\n"
" public String getChallengeMessage()\n"
" {\n"
-" StringBuilder challengeMsg = new StringBuilder("I'm thinking of a number between ");\n"
+" StringBuilder challengeMsg = new StringBuilder(\"I'm thinking of a number between \");\n"
" challengeMsg.append(game.getSmallest());\n"
-" challengeMsg.append(" and ");\n"
+" challengeMsg.append(\" and \");\n"
" challengeMsg.append(game.getBiggest());\n"
-" challengeMsg.append(". Can you guess what it is?");\n"
+" challengeMsg.append(\". Can you guess what it is?\");\n"
"\n"
" return challengeMsg.toString();\n"
" }\n"
@@ -673,34 +673,34 @@ msgid ""
" {\n"
" if (game.isGameWon())\n"
" {\n"
-" return "You guessed it! The number was " + game.getNumber();\n"
+" return \"You guessed it! The number was \" + game.getNumber();\n"
" }\n"
" else if (game.isGameLost())\n"
" {\n"
-" return "You are fail! The number was " + game.getNumber();\n"
+" return \"You are fail! The number was \" + game.getNumber();\n"
" }\n"
" else if (!game.isValidNumberRange())\n"
" {\n"
-" return "Invalid number range!";\n"
+" return \"Invalid number range!\";\n"
" }\n"
" else if (game.getRemainingGuesses() == Game.MAX_NUM_GUESSES)\n"
" {\n"
-" return "What is your first guess?";\n"
+" return \"What is your first guess?\";\n"
" }\n"
" else\n"
" {\n"
" String direction = null;\n"
"\n"
-" if (game.getGuess() < game.getNumber())\n"
+" if (game.getGuess() < game.getNumber())\n"
" {\n"
-" direction = "Higher";\n"
+" direction = \"Higher\";\n"
" }\n"
" else\n"
" {\n"
-" direction = "Lower";\n"
+" direction = \"Lower\";\n"
" }\n"
"\n"
-" return direction + "! You have " + game.getRemainingGuesses() + " guesses left.";\n"
+" return direction + \"! You have \" + game.getRemainingGuesses() + \" guesses left.\";\n"
" }\n"
" }\n"
"}"
@@ -713,7 +713,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
+msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
msgstr ""
#. Tag: para
@@ -783,7 +783,7 @@ msgid ""
" private void refreshUI() {\n"
" mainLabel.setText( msgGenerator.getChallengeMessage() );\n"
" messageLabel.setText( msgGenerator.getResultMessage() );\n"
-" guessText.setText( "" );\n"
+" guessText.setText( \"\" );\n"
" guessesLeftBar.setValue( game.getRemainingGuesses() );\n"
" guessText.requestFocus();\n"
" }\n"
@@ -818,7 +818,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
+msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
msgstr ""
#. Tag: para
@@ -828,7 +828,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Calls game.check() to validate and perform one 'turn' of the game"
+msgid "Calls game.check() to validate and perform one 'turn' of the game"
msgstr ""
#. Tag: para
@@ -853,7 +853,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
+msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
msgstr ""
#. Tag: para
@@ -863,25 +863,25 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
+msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<plugin>\n"
-" <groupId>org.apache.maven.plugins</groupId>\n"
-" <artifactId>maven-ear-plugin</artifactId>\n"
-" <configuration>\n"
-" <modules>\n"
-" <webModule>\n"
-" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
-" <artifactId>weld-jsf-translator-war</artifactId>\n"
-" <contextRoot>/weld-translator</contextRoot>\n"
-" </webModule>\n"
-" </modules>\n"
-" </configuration>\n"
-"</plugin>"
+"<plugin>\n"
+" <groupId>org.apache.maven.plugins</groupId>\n"
+" <artifactId>maven-ear-plugin</artifactId>\n"
+" <configuration>\n"
+" <modules>\n"
+" <webModule>\n"
+" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
+" <artifactId>weld-jsf-translator-war</artifactId>\n"
+" <contextRoot>/weld-translator</contextRoot>\n"
+" </webModule>\n"
+" </modules>\n"
+" </configuration>\n"
+"</plugin>"
msgstr ""
#. Tag: para
@@ -891,72 +891,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
+msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<application version="5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<application version=\"5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/application_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/application_5.xsd\">\n"
"\n"
-" <display-name>weld-jsf-translator-ear</display-name>\n"
-" <description>The Weld JSF translator example (ear)</description>\n"
+" <display-name>weld-jsf-translator-ear</display-name>\n"
+" <description>The Weld JSF translator example (ear)</description>\n"
" \n"
-" <module>\n"
-" <web>\n"
-" <web-uri>weld-translator.war</web-uri>\n"
-" <context-root>/weld-translator</context-root>\n"
-" </web>\n"
-" </module>\n"
-" <module>\n"
-" <ejb>weld-translator.jar</ejb>\n"
-" </module>\n"
-"</application>"
+" <module>\n"
+" <web>\n"
+" <web-uri>weld-translator.war</web-uri>\n"
+" <context-root>/weld-translator</context-root>\n"
+" </web>\n"
+" </module>\n"
+" <module>\n"
+" <ejb>weld-translator.jar</ejb>\n"
+" </module>\n"
+"</application>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
+msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (ommitted here for brevity):"
+msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (omitted here for brevity):"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:form id="translator">\n"
+"<h:form id=\"translator\">\n"
"\n"
-" <table>\n"
-" <tr align="center" style="font-weight: bold">\n"
-" <td>\n"
+" <table>\n"
+" <tr align=\"center\" style=\"font-weight: bold\">\n"
+" <td>\n"
" Your text\n"
-" </td>\n"
-" <td>\n"
+" </td>\n"
+" <td>\n"
" Translation\n"
-" </td>\n"
-" </tr>\n"
-" <tr>\n"
-" <td>\n"
-" <h:inputTextarea id="text" value="#{translator.text}" required="true" rows="5" cols="80"/>\n"
-" </td>\n"
-" <td>\n"
-" <h:outputText value="#{translator.translatedText}"/>\n"
-" </td>\n"
-" </tr>\n"
-" </table>\n"
-" <div>\n"
-" <h:commandButton id="button" value="Translate" action="#{translator.translate}"/>\n"
-" </div>\n"
+" </td>\n"
+" </tr>\n"
+" <tr>\n"
+" <td>\n"
+" <h:inputTextarea id=\"text\" value=\"#{translator.text}\" required=\"true\" rows=\"5\" cols=\"80\"/>\n"
+" </td>\n"
+" <td>\n"
+" <h:outputText value=\"#{translator.translatedText}\"/>\n"
+" </td>\n"
+" </tr>\n"
+" </table>\n"
+" <div>\n"
+" <h:commandButton id=\"button\" value=\"Translate\" action=\"#{translator.translate}\"/>\n"
+" </div>\n"
" \n"
-"</h:form>"
+"</h:form>"
msgstr ""
#. Tag: para
@@ -966,12 +966,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
+msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
+msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
msgstr ""
#. Tag: para
@@ -995,7 +995,7 @@ msgid ""
" public String translate(String text) { \n"
" StringBuilder sb = new StringBuilder(); \n"
" for (String sentence: sentenceParser.parse(text)) { \n"
-" sb.append(translator.translate(sentence)).append(". "); \n"
+" sb.append(translator.translate(sentence)).append(\". \"); \n"
" } \n"
" return sb.toString().trim(); \n"
" }\n"
@@ -1005,7 +1005,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
+msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
msgstr ""
#. Tag: programlisting
@@ -1015,7 +1015,7 @@ msgid ""
"public class SentenceTranslator implements Translator { \n"
"\n"
" public String translate(String sentence) { \n"
-" return "Lorem ipsum dolor sit amet"; \n"
+" return \"Lorem ipsum dolor sit amet\"; \n"
" }\n"
"\n"
"}"
@@ -1031,7 +1031,7 @@ msgstr ""
msgid ""
"@Stateful\n"
"@RequestScoped\n"
-"@Named("translator")\n"
+"@Named(\"translator\")\n"
"public class TranslatorControllerBean implements TranslatorController {\n"
"\n"
" @Inject private TextTranslator translator;\n"
diff --git a/docs/reference/src/main/docbook/zh-TW/Weld_-_JSR-299_Reference_Implementation.po b/docs/reference/src/main/docbook/zh-TW/Weld_-_JSR-299_Reference_Implementation.po
new file mode 100644
index 00000000000..f4baccac014
--- /dev/null
+++ b/docs/reference/src/main/docbook/zh-TW/Weld_-_JSR-299_Reference_Implementation.po
@@ -0,0 +1,59 @@
+#
+# AUTHOR , YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
+"PO-Revision-Date: 2012-01-16T16:07:16\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "A note about naming and nomenclature"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Shortly before the final draft of JSR-299 was submitted, the specification changed its name from \"Web Beans\" to \"Java Contexts and Dependency Injection for the Java EE platform\", abbreviated CDI. For a brief period after the renaming, the reference implementation adopted the name \"Web Beans\". However, this ended up causing more confusion than it solved and Red Hat decided to change the name of the reference implementation to \"Weld\". You may still find other documentation, blogs, forum posts, etc. that use the old nomenclature. Please update any references you can. The naming game is over."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You'll also find that some of the functionality that once existed in the specification is now missing, such as defining beans in XML. These features will be available as portable extensions for CDI in the Weld project, and perhaps other implementations."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Note that this reference guide was started while changes were still being made to the specification. We've done our best to update it for accuracy. If you discover a conflict between what is written in this guide and the specification, the specification is the authority—assume it is correct. If you believe you have found an error in the specification, please report it to the JSR-299 EG."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Beans"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Start with Weld, the CDI Reference Implementation"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Loose coupling with strong typing"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "CDI and the Java EE ecosystem"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Weld Reference Guide"
+msgstr ""
+
diff --git a/docs/reference/src/main/docbook/zh-TW/beans.po b/docs/reference/src/main/docbook/zh-TW/beans.po
index a5da10e915f..c8ee6be80a7 100644
--- a/docs/reference/src/main/docbook/zh-TW/beans.po
+++ b/docs/reference/src/main/docbook/zh-TW/beans.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
+msgid "Let's back up a second. What does it really mean to be contextual? Since beans may be stateful, it matters which bean instance I have. Unlike a stateless component model (for example, stateless session beans) or a singleton component model (such as servlets, or singleton beans), different clients of a bean see the bean in different states. The client-visible state depends upon which instance of the bean the client has a reference to."
msgstr ""
#. Tag: para
@@ -56,7 +56,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
+msgid "One great advantage of the contextual model is that it allows stateful beans to be treated like services! The client need not concern itself with managing the lifecycle of the bean it's using, nor does it even need to know what that lifecycle is. Beans interact by passing messages, and the bean implementations define the lifecycle of their own state. The beans are loosely coupled because:"
msgstr ""
#. Tag: para
@@ -76,7 +76,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
+msgid "Note that not all clients of a bean are beans themselves. Other objects such as servlets or message-driven beans—which are by nature not injectable, contextual objects—may also obtain references to beans by injection."
msgstr ""
#. Tag: title
@@ -131,7 +131,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's see what all this new terminology means."
+msgid "Let's see what all this new terminology means."
msgstr ""
#. Tag: title
@@ -141,7 +141,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a "contract" that must be satisfied by the bean to be injected. The contract is:"
+msgid "Beans usually acquire references to other beans via dependency injection. Any injected attribute specifies a \"contract\" that must be satisfied by the bean to be injected. The contract is:"
msgstr ""
#. Tag: para
@@ -164,14 +164,14 @@ msgstr ""
msgid ""
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
+msgid "The bean types are BookShop, Business and Shop<Book>, as well as the implicit type java.lang.Object. (Notice that a parameterized type is a legal bean type)."
msgstr ""
#. Tag: para
@@ -192,12 +192,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
+msgid "The bean types of a session bean include local interfaces and the bean class local view (if any). EJB remote interfaces are not considered bean types of a session bean. You can't inject an EJB using its remote interface unless you define a resource, which we'll meet in ."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
+msgid "Bean types may be restricted to an explicit set by annotating the bean with the @Typed annotation and listing the classes that should be bean types. For instance, the bean types of this bean have been restricted to Shop<Book>, together with java.lang.Object:"
msgstr ""
#. Tag: programlisting
@@ -206,19 +206,19 @@ msgid ""
"@Typed(Shop.class)\n"
"public class BookShop \n"
" extends Business \n"
-" implements Shop<Book> {\n"
+" implements Shop<Book> {\n"
" ...\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of "quality" using a qualifier."
+msgid "Sometimes, a bean type alone does not provide enough information for the container to know which bean to inject. For instance, suppose we have two implementations of the PaymentProcessor interface: CreditCardPaymentProcessor and DebitPaymentProcessor. Injecting a field of type PaymentProcessor introduces an ambiguous condition. In these cases, the client must specify some additional quality of the implementation it is interested in. We model this kind of \"quality\" using a qualifier."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
+msgid "A qualifier is a user-defined annotation that is itself annotated @Qualifer. A qualifier annotation is an extension of the type system. It lets us disambiguate a type without having to fall back to string-based names. Here's an example of a qualifier annotation:"
msgstr ""
#. Tag: programlisting
@@ -232,12 +232,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
+msgid "You may not be used to seeing the definition of an annotation. In fact, this might be the first time you've encountered one. With CDI, annotation definitions will become a familiar artifact as you'll be creating them from time to time."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
+msgid "Pay attention to the names of the built-in annotations in CDI and EJB. You'll notice that they are often adjectives. We encourage you to follow this convention when creating your custom annotations, since they serve to describe the behaviors and roles of the class."
msgstr ""
#. Tag: para
@@ -252,12 +252,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
+msgid "For each injection point, the container searches for a bean which satisfies the contract, one which has the bean type and all the qualifiers. If it finds exactly one matching bean, it injects an instance of that bean. If it doesn't, it reports an error to the user."
msgstr ""
#. Tag: para
@@ -275,12 +270,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If a bean does not explicitly specify a qualifier, it has the default qualifier, @Default."
+msgid "If a bean or an injection point does not explicitly specify a qualifier, it has the default qualifier, @Default."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
+msgid "That's not quite the end of the story. CDI also defines a simple resolution rule that helps the container decide what to do if there is more than one bean that satisfies a particular contract. We'll get into the details in ."
msgstr ""
#. Tag: title
@@ -312,7 +307,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
+msgid "Keep in mind that once a bean is bound to a context, it remains in that context until the context is destroyed. There is no way to manually remove a bean from a context. If you don't want the bean to sit in the session indefinitely, consider using another scope with a shorted lifespan, such as the request or conversation scope."
msgstr ""
#. Tag: para
@@ -322,7 +317,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk more about scopes in ."
+msgid "We'll talk more about scopes in ."
msgstr ""
#. Tag: title
@@ -343,7 +338,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"public @SessionScoped @Named("cart")\n"
+"public @SessionScoped @Named(\"cart\")\n"
"class ShoppingCart implements Serializable { ... }"
msgstr ""
@@ -355,9 +350,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:dataTable value="#{cart.lineItems}" var="item">\n"
+"<h:dataTable value=\"#{cart.lineItems}\" var=\"item\">\n"
" ...\n"
-"</h:dataTable>"
+"</h:dataTable>"
msgstr ""
#. Tag: para
@@ -389,7 +384,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
+msgid "We've already seen how qualifiers let us choose between multiple implementations of an interface at development time. But sometimes we have an interface (or other bean type) whose implementation varies depending upon the deployment environment. For example, we may want to use a mock implementation in a testing environment. An alternative may be declared by annotating the bean class with the @Alternative annotation."
msgstr ""
#. Tag: programlisting
@@ -416,12 +411,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
+msgid "You might be familiar with the use of interceptors in EJB 3.0. In Java EE 6, this functionality has been generalized to work with other managed beans. That's right, you no longer have to make your bean an EJB just to intercept its methods. Holler. So what does CDI have to offer above and beyond that? Well, quite a lot actually. Let's cover some background."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
+msgid "The way that interceptors were defined in Java EE 5 was counter-intuitive. You were required to specify the implementation of the interceptor directly on the implementation of the EJB, either in the @Interceptors annotation or in the XML descriptor. You might as well just put the interceptor code in the implementation! Second, the order in which the interceptors are applied is taken from the order in which they are declared in the annotation or the XML descriptor. Perhaps this isn't so bad if you're applying the interceptors to a single bean. But, if you are applying them repeatedly, then there's a good chance that you'll inadvertently define a different order for different beans. Now that's a problem."
msgstr ""
#. Tag: para
@@ -470,17 +465,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
+msgid "Notice that ShoppingCart and TransactionInterceptor don't know anything about each other."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
+msgid "Interceptors are deployment-specific. (We don't need a TransactionInterceptor in our unit tests!) By default, an interceptor is disabled. We can enable an interceptor using the CDI deployment descriptor META-INF/beans.xml of the jar or Java EE module. This is also where we specify the interceptor ordering."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
+msgid "We'll discuss interceptors, and their cousins, decorators, in and ."
msgstr ""
#. Tag: title
@@ -490,7 +485,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
+msgid "We've already seen two types of beans: JavaBeans and EJB session beans. Is that the whole story? Actually, it's just the beginning. Let's explore the various kinds of beans that CDI implementations must support out-of-the-box."
msgstr ""
#. Tag: title
@@ -500,7 +495,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
+msgid "A managed bean is a Java class. The basic lifecycle and semantics of a managed bean are defined by the Managed Beans specification. You can explicitly declare a managed bean by annotating the bean class @ManagedBean, but in CDI you don't need to. According to the specification, the CDI container treats any class that satisfies the following conditions as a managed bean:"
msgstr ""
#. Tag: para
@@ -525,7 +520,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It has an appropriate constructor—either:"
+msgid "It has an appropriate constructor—either:"
msgstr ""
#. Tag: para
@@ -540,7 +535,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
+msgid "According to this definition, JPA entities are technically managed beans. However, entities have their own special lifecycle, state and identity model and are usually instantiated by JPA or using new. Therefore we don't recommend directly injecting an entity class. We especially recommend against assigning a scope other than @Dependent to an entity class, since JPA is not able to persist injected CDI proxies."
msgstr ""
#. Tag: para
@@ -585,12 +580,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
+msgid "There's no reason to explicitly declare the scope of a stateless session bean or singleton session bean. The EJB container controls the lifecycle of these beans, according to the semantics of the @Stateless or @Singleton declaration. On the other hand, a stateful session bean may have any scope."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
+msgid "Stateful session beans may define a remove method, annotated @Remove, that is used by the application to indicate that an instance should be destroyed. However, for a contextual instance of the bean—an instance under the control of CDI—this method may only be called by the application if the bean has scope @Dependent. For beans with other scopes, the application must let the container destroy the bean."
msgstr ""
#. Tag: para
@@ -625,7 +620,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
+msgid "When we don't need any of these things, an ordinary managed bean will serve just fine."
msgstr ""
#. Tag: para
@@ -640,17 +635,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
+msgid "Finally, it's usually obvious when method-level transaction management, method-level security, timers, remote methods or asynchronous methods are needed."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
+msgid "The point we're trying to make is: use a session bean when you need the services it provides, not just because you want to use dependency injection, lifecycle management, or interceptors. Java EE 6 provides a graduated programming model. It's usually easy to start with an ordinary managed bean, and later turn it into an EJB just by adding one of the following annotations: @Stateless, @Stateful or @Singleton."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're "heavyweight". It's nothing more than superstition to think that something is "heavier" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like "heavyweight"."
+msgid "On the other hand, don't be scared to use session beans just because you've heard your friends say they're \"heavyweight\". It's nothing more than superstition to think that something is \"heavier\" just because it's hosted natively within the Java EE container, instead of by a proprietary bean container or dependency injection framework that runs as an additional layer of obfuscation. And as a general principle, you should be skeptical of folks who use vaguely defined terminology like \"heavyweight\"."
msgstr ""
#. Tag: title
@@ -690,7 +685,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
+msgid "We can't write a bean class that is itself a random number. But we can certainly write a method that returns a random number. By making the method a producer method, we allow the return value of the method—in this case an Integer—to be injected. We can even specify a qualifier—in this case @Random, a scope—which in this case defaults to @Dependent, and an EL name—which in this case defaults to randomNumber according to the JavaBeans property name convention. Now we can get a random number anywhere:"
msgstr ""
#. Tag: programlisting
@@ -705,7 +700,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<p>Your raffle number is #{randomNumber}.</p>"
+msgid "<p>Your raffle number is #{randomNumber}.</p>"
msgstr ""
#. Tag: para
@@ -746,14 +741,14 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces Set<Roles> getRoles(User user) {\n"
+"@Produces Set<Roles> getRoles(User user) {\n"
" return user.getRoles();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll talk much more about producer methods in ."
+msgid "We'll talk much more about producer methods in ."
msgstr ""
#. Tag: title
@@ -763,7 +758,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
+msgid "A producer field is a simpler alternative to a producer method. A producer field is declared by annotating a field of a bean class with the @Produces annotation—the same annotation used for producer methods."
msgstr ""
#. Tag: programlisting
@@ -771,7 +766,7 @@ msgstr ""
msgid ""
"public class Shop {\n"
" @Produces PaymentProcessor paymentProcessor = ....;\n"
-" @Produces @Catalog List<Product> products = ....;\n"
+" @Produces @Catalog List<Product> products = ....;\n"
"}"
msgstr ""
@@ -782,5 +777,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
+msgid "A producer field is really just a shortcut that lets us avoid writing a useless getter method. However, in addition to convenience, producer fields serve a specific purpose as an adaptor for Java EE component environment injection, but to learn more about that, you'll have to wait until . Because we can't wait to get to work on some examples."
msgstr ""
diff --git a/docs/reference/src/main/docbook/zh-TW/configure.po b/docs/reference/src/main/docbook/zh-TW/configure.po
index eeba87f0a16..01ef2ccd8ab 100644
--- a/docs/reference/src/main/docbook/zh-TW/configure.po
+++ b/docs/reference/src/main/docbook/zh-TW/configure.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -30,50 +30,50 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
+msgid "In this tutorial, we'll explore this feature via an example; a more formal specification can be found in the xsd, located at http://jboss.org/schema/weld/beans_1_1.xsd."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<?xml version="1.0" encoding="UTF-8"?>\n"
-"<beans xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \n"
-" xmlns:weld="http://jboss.org/schema/weld/beans" \n"
-" xsi:schemaLocation="\n"
+"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<beans xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" \n"
+" xmlns:weld=\"http://jboss.org/schema/weld/beans\" \n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee http://docs.jboss.org/cdi/beans_1_0.xsd\n"
-" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">\n"
+" http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd\">\n"
" \n"
-" <weld:scan>\n"
+" <weld:scan>\n"
" \n"
-" <!-- Don't deploy the classes for the swing app! -->\n"
-" <weld:exclude name="com.acme.swing.**" />\n"
+" <!-- Don't deploy the classes for the swing app! -->\n"
+" <weld:exclude name=\"com.acme.swing.**\" />\n"
" \n"
-" <!-- Don't include GWT support if GWT is not installed -->\n"
-" <weld:exclude name="com.acme.gwt.**">\n"
-" <weld:if-class-available name="!com.google.GWT"/>\n"
-" </weld:exclude>\n"
+" <!-- Don't include GWT support if GWT is not installed -->\n"
+" <weld:exclude name=\"com.acme.gwt.**\">\n"
+" <weld:if-class-available name=\"!com.google.GWT\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
+" <!--\n"
" Exclude classes which end in Blether if the system property verbosity is set to low\n"
" i.e.\n"
" java ... -Dverbosity=low \n"
-" --> \n"
-" <weld:exclude pattern="^(.*)Blether$">\n"
-" <weld:if-system-property name="verbosity" value="low"/>\n"
-" </weld:exclude>\n"
+" --> \n"
+" <weld:exclude pattern=\"^(.*)Blether$\">\n"
+" <weld:if-system-property name=\"verbosity\" value=\"low\"/>\n"
+" </weld:exclude>\n"
" \n"
-" <!--\n"
-" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
+" <!--\n"
+" Don't include JSF support if Wicket classes are present, and the viewlayer system\n"
" property is not set\n"
-" -->\n"
-" <weld:exclude name="com.acme.jsf.**">\n"
-" <weld:if-class-available name="org.apahce.wicket.Wicket"/>\n"
-" <weld:if-system-property name="!viewlayer"/>\n"
-" </weld:exclude>\n"
-" </weld:scan>\n"
+" -->\n"
+" <weld:exclude name=\"com.acme.jsf.**\">\n"
+" <weld:if-class-available name=\"org.apahce.wicket.Wicket\"/>\n"
+" <weld:if-system-property name=\"!viewlayer\"/>\n"
+" </weld:exclude>\n"
+" </weld:scan>\n"
" \n"
-"</beans>"
+"</beans>"
msgstr ""
#. Tag: para
@@ -83,7 +83,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
+msgid "However, sometimes it's useful to be able to activate the filter depending on the environment used. In this case, Weld allows you to activate (or deactivate) a filter based on either system properties or whether a class is available. The second filter shows the use case of disabling scanning of certain classes depending on the capabilities of the environment you deploy to - in this case we are excluding GWT support if GWT is not installed."
msgstr ""
#. Tag: para
@@ -93,12 +93,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
+msgid "The third filter uses a regular expression to select the classes to match (normally we use simple name-based patterns, as they don't require us to escape the period which delimits the package hierarchy)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
+msgid "If you specify just a system property name, Weld will activate the filter if that system property has been set (with any value). If you also specify the system property value, then Weld will only activate the filter if the system property's value matches exactly."
msgstr ""
#. Tag: para
@@ -113,5 +113,5 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
+msgid "In general, the semantics defined by Ant's pattern sets (http://ant.apache.org/manual/dirtasks.html#patternset) are followed."
msgstr ""
diff --git a/docs/reference/src/main/docbook/zh-TW/contexts.po b/docs/reference/src/main/docbook/zh-TW/contexts.po
index 998addb61d4..6503057daf1 100644
--- a/docs/reference/src/main/docbook/zh-TW/contexts.po
+++ b/docs/reference/src/main/docbook/zh-TW/contexts.po
@@ -4,7 +4,7 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2010-10-19T02:13:49\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -25,17 +25,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld allows you to easiy manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivaed (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
+msgid "Weld allows you to easily manage the built in contexts by injecting them and calling lifecycle methods. Weld defines two types of context, managed and unmanaged. Managed contexts can be activated (allowing bean instances to be retrieved from the context), invalidated (scheduling bean instances for destruction) and deactivated (stopping bean instances from being retrieved, and if the context has been invalidated, causing the bean instances to destroyed). Unmanaged contexts are always active; some may offer the ability to destroy instances."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and discociating the data store after calling activate."
+msgid "Managed contexts can either be bound or unbound. An unbound context is scoped to the thread in which it is activated (instances placed in the context in one thread are not visible in other threads), and is destroyed upon invalidation and deactivation. Bound contexts are attached to some external data store (such as the Http Session or a manually propagated map) by associating the data store with the context before calling activate, and dissociating the data store after calling activate."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld automatically controls context lifecycle in many scenarios such as Http Requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
+msgid "Weld automatically controls context lifecycle in many scenarios such as HTTP requests, EJB remote invocations, and MDB invocations. Many of the extensions for CDI offer context lifecycle for other environments, it's worth checking to see if there is a suitable extension before deciding to manage the context yourself."
msgstr ""
#. Tag: para
@@ -145,7 +145,7 @@ msgstr ""
#. Tag: entry
#, no-c-format
-msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
+msgid "A request context bound to a an interceptor's invocation context, used for EJB invocations outside of Servlet requests"
msgstr ""
#. Tag: entry
@@ -245,12 +245,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implmentations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
+msgid "Unmanaged contexts offer little of interest in a discussion about managing context lifecycles, so from here on in we will concentrate on the managed contexts (unmanaged contexts of course play a vital role in the functioning of your application and Weld!). As you can see from the table above, the managed contexts offer a number of different implementations for the same scope; in general, each flavor of context for a scope has the same API. We'll walk through a number of common lifecycle management scenarios below; armed with this knowledge, and the Javadoc, you should be able to work with any of the context implementations Weld offers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
+msgid "We'll start simple with the BoundRequestContext, which you might use to provide the request scope outside of a Servlet request or EJB Invocation."
msgstr ""
#. Tag: programlisting
@@ -263,14 +263,14 @@ msgid ""
" ...\n"
" \n"
" /* Start the request, providing a data store which will last the lifetime of the request */\n"
-" public void startRequest(Map<String, Object> requestDataStore) {\n"
+" public void startRequest(Map<String, Object> requestDataStore) {\n"
" // Associate the store with the context and acticate the context\n"
" requestContext.associate(requestDataStore);\n"
" requestContext.activate();\n"
" }\n"
" \n"
" /* End the request, providing the same data store as was used to start the request */\n"
-" public void endRequest(Map<String, Object> requestDataStore) {\n"
+" public void endRequest(Map<String, Object> requestDataStore) {\n"
" try {\n"
" /* Invalidate the request (all bean instances will be scheduled for destruction) */\n"
" requestContext.invalidate();\n"
@@ -290,7 +290,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's session contexts are "lazy" and don't require a session to actually exist until a bean instance must be written."
+msgid "Weld's session contexts are \"lazy\" and don't require a session to actually exist until a bean instance must be written."
msgstr ""
#. Tag: para
@@ -308,16 +308,16 @@ msgid ""
" /* Start a transient conversation */\n"
" /* Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */\n"
-" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void startTransientConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" resumeOrStartConversation(requestDataStore, sessionDataStore, null);\n"
" }\n"
"\n"
" /* Start a transient conversation (if cid is null) or resume a non-transient */\n"
" /* conversation. Provide a data store which will last the lifetime of the request */\n"
" /* and one that will last the lifetime of the session */ \n"
-" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore, \n"
+" public void resumeOrStartConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore, \n"
" String cid) {\n"
" /* Associate the stores with the context and acticate the context */\n"
" * BoundRequest just wraps the two datastores */\n"
@@ -329,8 +329,8 @@ msgid ""
" /* End the conversations, providing the same data store as was used to start */\n"
" /* the request. Any transient conversations will be destroyed, any newly-promoted */\n"
" /* conversations will be placed into the session */\n"
-" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
-" Map<String, Object> sessionDataStore) {\n"
+" public void endOrPassivateConversation(Map<String, Object> requestDataStore, \n"
+" Map<String, Object> sessionDataStore) {\n"
" try {\n"
" /* Invalidate the conversation (all transient conversations will be scheduled for destruction) */\n"
" conversationContext.invalidate();\n"
@@ -345,15 +345,15 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the containber), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
+msgid "The conversation context also offers a number of properties which control the behavior of conversation expiration (after this period of inactivity the conversation will be ended and destroyed by the container), and the duration of lock timeouts (the conversation context ensures that a single thread is accessing any bean instances by locking access, if a lock can't be obtained after a certain time Weld will error rather than continue to wait for the lock). Additionally, you can alter the name of the parameter used to transfer the conversation id (by default, cid)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the abilty to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
+msgid "Weld also introduces the notion of a ManagedConversation, which extends the Conversation interface with the ability to lock, unlock and touch (update the last used timestamp) a conversation. Finally, all non-transient conversations in a session can be obtained from the conversation context, as can the current conversation."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld's conversations are not assigned ids until they become non-transient."
+msgid "Weld's conversations are not assigned ids until they become non-transient."
msgstr ""
diff --git a/docs/reference/src/main/docbook/zh-TW/decorators.po b/docs/reference/src/main/docbook/zh-TW/decorators.po
index e10d266bf18..9891e757aee 100644
--- a/docs/reference/src/main/docbook/zh-TW/decorators.po
+++ b/docs/reference/src/main/docbook/zh-TW/decorators.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: decorators\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-08 12:39+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -24,12 +24,12 @@ msgstr "裝飾器(Decorators)"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
+msgid "Interceptors are a powerful way to capture and separate concerns which are orthogonal to the application (and type system). Any interceptor is able to intercept invocations of any Java type. This makes them perfect for solving technical concerns such as transaction management, security and call logging. However, by nature, interceptors are unaware of the actual semantics of the events they intercept. Thus, interceptors aren't an appropriate tool for separating business-related concerns."
msgstr "呼叫攔截器(Interceptors)是個用來擷取和區分與型別系統垂直的相關問題的強大方式。任何攔截器皆可攔截任何 Java 類型的調用(invocation)。這使它們適用於解決涉及技術上的問題,例如交易管理和安全性。不過,就一般來講,攔截器並不會知道它們所攔截的事件之實際 語。因此,攔截器並不適合作為一個區分涉及商業問題的工具。意"
#. Tag: para
#, fuzzy, no-c-format
-msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
+msgid "The reverse is true of decorators. A decorator intercepts invocations only for a certain Java interface, and is therefore aware of all the semantics attached to that interface. Since decorators directly implement operations with business semantics, it makes them the perfect tool for modeling some kinds of business concerns. It also means that a decorator doesn't have the generality of an interceptor. Decorators aren't able to solve technical concerns that cut across many disparate types. Interceptors and decorators, though similar in many ways, are complementary. Let's look at some cases where decorators fit the bill."
msgstr "裝飾器(decorators)則是相反的。裝飾器只會針對於特定 java 介面來攔截調用,因此它知道該介面的所有語意。這使得裝飾器適用於模擬涉及商業上的問題。同時這也代表裝飾器並沒有攔截器的普遍性。裝飾器無法解決涉及多種不同類型的技術問題。"
#. Tag: para
@@ -127,7 +127,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
+msgid "Unlike other beans, a decorator may be an abstract class. Therefore, if there's nothing special the decorator needs to do for a particular method of the decorated interface, you don't need to implement that method."
msgstr "和其它單純的 Web Bean 不同的是,裝飾器可能會是個抽象類別(abstract class)。若裝飾器無須為被裝飾之介面的特定 method 進行任何特殊動作的話,您便無須實做該 method。"
#. Tag: para
@@ -211,14 +211,14 @@ msgid ""
" \n"
" public void withdraw(BigDecimal amount) {\n"
" account.withdraw(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedWithdrawl(amount) );\n"
" }\n"
" }\n"
" \n"
" public void deposit(BigDecimal amount);\n"
" account.deposit(amount);\n"
-" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
+" if ( amount.compareTo(LARGE_AMOUNT)>0 ) {\n"
" em.persist( new LoggedDeposit(amount) );\n"
" }\n"
" }\n"
@@ -261,21 +261,21 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <decorators>\n"
-" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
-" </decorators>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <decorators>\n"
+" <class>org.mycompany.myapp.LargeTransactionDecorator</class>\n"
+" </decorators>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
+msgid "This declaration serves the same purpose for decorators that the <interceptors> declaration serves for interceptors:"
msgstr "此宣告(declaration)對於裝飾器的目的和 <Interceptors> 宣告對於攔截器的目的是相同的:"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-TW/ee.po b/docs/reference/src/main/docbook/zh-TW/ee.po
index 10c5e71891f..eb38f4226c5 100644
--- a/docs/reference/src/main/docbook/zh-TW/ee.po
+++ b/docs/reference/src/main/docbook/zh-TW/ee.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: ee\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-15 12:12+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -59,7 +59,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
+msgid "The CDI specification does not require the servlet context objects, HttpServletRequest, HttpSession and ServletContext to be exposed as injectable beans. If you really want to be able to inject these objects, it's easy to create a portable extension to expose them as beans. However, we recommend that direct access to these objects be limited to servlets, servlet filters and servlet event listeners, where they may be obtained in the usual way as defined by the Java Servlets spec. The FacesContext is also not injectable. You can get at it by calling FacesContext.getCurrentInstance()."
msgstr ""
#. Tag: para
@@ -84,7 +84,7 @@ msgstr "將 Java EE 資源注入 Web Bean 中"
#. Tag: para
#, fuzzy, no-c-format
-msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
+msgid "All managed beans may take advantage of Java EE component environment injection using @Resource, @EJB, @PersistenceContext, @PeristenceUnit and @WebServiceRef. We've already seen a couple of examples of this, though we didn't pay much attention at the time:"
msgstr "所有基本與企業的 Web Bean 都能透過 @Resource、@EJB 以及 @PersistenceContext 來有效利用 Java 依賴注入(dependency injection)。我們早已見過了這方面的範例,不過當時我們並未詳細討論到:"
#. Tag: programlisting
@@ -143,7 +143,7 @@ msgstr "透過一個 Servlet 來調用 Web Bean"
#. Tag: para
#, fuzzy, no-c-format
-msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
+msgid "It's easy to use a bean from a servlet in Java EE 6. Simply inject the bean using field or initializer method injection."
msgstr "在 Java EE 6 中透過 Servlet 來使用 Web Bean 相當地簡單。只要使用 Web Bean 欄位或是 initializer method 注入來注入 Web Bean 即可。"
#. Tag: programlisting
@@ -156,14 +156,14 @@ msgid ""
" @Override\n"
" public void service(HttpServletRequest request, HttpServletResponse response)\n"
" throws ServletException, IOException {\n"
-" credentials.setUsername(request.getParameter("username")):\n"
-" credentials.setPassword(request.getParameter("password")):\n"
+" credentials.setUsername(request.getParameter(\"username\")):\n"
+" credentials.setPassword(request.getParameter(\"password\")):\n"
" login.login();\n"
" if ( login.isLoggedIn() ) {\n"
-" response.sendRedirect("/home.jsp");\n"
+" response.sendRedirect(\"/home.jsp\");\n"
" }\n"
" else {\n"
-" response.sendRedirect("/loginError.jsp");\n"
+" response.sendRedirect(\"/loginError.jsp\");\n"
" }\n"
" }\n"
" \n"
@@ -202,7 +202,7 @@ msgstr "透過訊息導向的 Bean 來調用 Web Bean"
#. Tag: para
#, no-c-format
-msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
+msgid "CDI injection applies to all EJBs, even when they aren't managed beans. In particular, you can use CDI injection in message-driven beans, which are by nature not contextual objects."
msgstr ""
#. Tag: para
@@ -264,10 +264,10 @@ msgstr ""
#, no-c-format
msgid ""
"public class OrderResources {\n"
-" @Resource(name="jms/ConnectionFactory")\n"
+" @Resource(name=\"jms/ConnectionFactory\")\n"
" private ConnectionFactory connectionFactory;\n"
" \n"
-" @Resource(name="jms/OrderQueue")\n"
+" @Resource(name=\"jms/OrderQueue\")\n"
" private Queue orderQueue;\n"
" \n"
" @Produces @OrderConnection\n"
@@ -318,7 +318,7 @@ msgid ""
"\n"
"public void sendMessage() {\n"
" MapMessage msg = orderSession.createMapMessage();\n"
-" msg.setLong("orderId", order.getId());\n"
+" msg.setLong(\"orderId\", order.getId());\n"
" ...\n"
" producer.send(msg);\n"
"}"
@@ -344,7 +344,7 @@ msgstr "封裝和建置"
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a "bean archive". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
+msgid "CDI doesn't define any special deployment archive. You can package beans in jars, ejb jars or wars—any deployment location in the application classpath. However, the archive must be a \"bean archive\". That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). The file may be empty. Beans deployed in archives that do not have a beans.xml file will not be available for use in the application."
msgstr "Web Bean 不會定義任何特殊的建置 archive。您可將 Web Bean 封裝在 JARs、EJB-JARs 或是 WARs 中,應用程式 classpath 中的任何建置位置上。不過,各個包含著 Web Bean 的 archive 在 META-INF 或是 WEB-INF 目錄中都必須包含著一個稱為 web-beans.xml 的檔案。該檔案能是空的。建置於一個沒有 web-beans.xml 檔案的 archive 中的 Web Bean 將無法使用於應用程式中。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-TW/environments.po b/docs/reference/src/main/docbook/zh-TW/environments.po
index 985a5dc7614..707bf4aca63 100644
--- a/docs/reference/src/main/docbook/zh-TW/environments.po
+++ b/docs/reference/src/main/docbook/zh-TW/environments.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:16\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-28 17:09+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -56,12 +56,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
+msgid "There is a major limitation to using a servlet container. Weld doesn't support deploying session beans, injection using @EJB or @PersistenceContext, or using transactional events in servlet containers. For enterprise features such as these, you should really be looking at a Java EE application server."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an "uber-jar", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
+msgid "Weld can be used as a library in an web application that is deployed to a Servlet container. You should place weld-servlet.jar within the WEB-INF/lib directory relative to the web root. weld-servlet.jar is an \"uber-jar\", meaning it bundles all the bits of Weld and CDI required for running in a Servlet container, for your convenience. Alternatively, you can use its component jars. A list of transitive dependencies can be found in the META-INF/DEPENDENCIES.txt file inside the weld-servlet.jar artifact."
msgstr ""
#. Tag: para
@@ -72,9 +72,9 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
#. Tag: title
@@ -84,18 +84,18 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
+msgid "Tomcat has a read-only JNDI, so Weld can't automatically bind the BeanManager extension SPI. To bind the BeanManager into JNDI, you should populate META-INF/context.xml in the web root with the following contents:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<Context>\n"
-" <Resource name="BeanManager" \n"
-" auth="Container"\n"
-" type="javax.enterprise.inject.spi.BeanManager"\n"
-" factory="org.jboss.weld.resources.ManagerObjectFactory"/>\n"
-"</Context>"
+"<Context>\n"
+" <Resource name=\"BeanManager\" \n"
+" auth=\"Container\"\n"
+" type=\"javax.enterprise.inject.spi.BeanManager\"\n"
+" factory=\"org.jboss.weld.resources.ManagerObjectFactory\"/>\n"
+"</Context>"
msgstr ""
#. Tag: para
@@ -106,12 +106,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<resource-env-ref>\n"
-" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
-" <resource-env-ref-type>\n"
+"<resource-env-ref>\n"
+" <resource-env-ref-name>BeanManager</resource-env-ref-name>\n"
+" <resource-env-ref-type>\n"
" javax.enterprise.inject.spi.BeanManager\n"
-" </resource-env-ref-type>\n"
-"</resource-env-ref>"
+" </resource-env-ref-type>\n"
+"</resource-env-ref>"
msgstr ""
#. Tag: para
@@ -131,27 +131,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
+msgid "Like Tomcat, Jetty has a read-only JNDI, so Weld can't automatically bind the BeanManager. To bind the BeanManager to JNDI in Jetty 6, you should populate WEB-INF/jetty-env.xml with the following contents:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.mortbay.jetty.plus.naming.Resource">\n"
-" <Arg><Ref id="webAppCtx"/></Arg> \n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.mortbay.jetty.plus.naming.Resource\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg> \n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg> \n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure>"
msgstr ""
#. Tag: para
@@ -162,22 +162,22 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://www.eclipse.org/jetty/configure.dtd">\n"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://www.eclipse.org/jetty/configure.dtd\">\n"
"\n"
-"<Configure id="webAppCtx" class="org.eclipse.jetty.webapp.WebAppContext">\n"
-" <New id="BeanManager" class="org.eclipse.jetty.plus.jndi.Resource">\n"
-" <Arg> <Ref id="webAppCtx"/> </Arg>\n"
-" <Arg>BeanManager</Arg>\n"
-" <Arg>\n"
-" <New class="javax.naming.Reference">\n"
-" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
-" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
-" <Arg/>\n"
-" </New>\n"
-" </Arg>\n"
-" </New>\n"
-"</Configure> "
+"<Configure id=\"webAppCtx\" class=\"org.eclipse.jetty.webapp.WebAppContext\">\n"
+" <New id=\"BeanManager\" class=\"org.eclipse.jetty.plus.jndi.Resource\">\n"
+" <Arg> <Ref id=\"webAppCtx\"/> </Arg>\n"
+" <Arg>BeanManager</Arg>\n"
+" <Arg>\n"
+" <New class=\"javax.naming.Reference\">\n"
+" <Arg>javax.enterprise.inject.spi.BeanManager</Arg>\n"
+" <Arg>org.jboss.weld.resources.ManagerObjectFactory</Arg>\n"
+" <Arg/>\n"
+" </New>\n"
+" </Arg>\n"
+" </New>\n"
+"</Configure> "
msgstr ""
#. Tag: para
@@ -187,7 +187,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
+msgid "Notice that Jetty doesn't not have built-in support for an javax.naming.spi.ObjectFactory like Tomcat, so it's necessary to manually create the javax.naming.Reference to wrap around it."
msgstr ""
#. Tag: para
@@ -197,19 +197,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file META-INF/jetty-web.xml with the following content to your war:"
+msgid "Weld also supports Servlet injection in Jetty 6. To enable this, add the file WEB-INF/jetty-web.xml with the following content to your war:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"\n"
-" "http://jetty.mortbay.org/configure.dtd">\n"
-"<Configure id="webAppCtx" class="org.mortbay.jetty.webapp.WebAppContext">\n"
-" <Call class="org.jboss.weld.environment.jetty.WeldServletHandler" name="process">\n"
-" <Arg><Ref id="webAppCtx"/></Arg>\n"
-" </Call>\n"
-"</Configure>"
+"<!DOCTYPE Configure PUBLIC \"-//Mort Bay Consulting//DTD Configure//EN\"\n"
+" \"http://jetty.mortbay.org/configure.dtd\">\n"
+"<Configure id=\"webAppCtx\" class=\"org.mortbay.jetty.webapp.WebAppContext\">\n"
+" <Call class=\"org.jboss.weld.environment.jetty.WeldServletHandler\" name=\"process\">\n"
+" <Arg><Ref id=\"webAppCtx\"/></Arg>\n"
+" </Call>\n"
+"</Configure>"
msgstr ""
#. Tag: title
@@ -219,7 +219,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In addition to improved integration of the Enterprise Java stack, the "Contexts and Dependency Injection for the Java EE platform" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
+msgid "In addition to improved integration of the Enterprise Java stack, the \"Contexts and Dependency Injection for the Java EE platform\" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types. To help developers take advantage of this, Weld provides a simple means for being executed in the Java Standard Edition (SE) environment independently of any Java EE APIs."
msgstr ""
#. Tag: para
@@ -279,7 +279,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@Inject @Parameters List<String> params;"
+msgid "@Inject @Parameters List<String> params;"
msgstr ""
#. Tag: programlisting
@@ -299,7 +299,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example of a simple CDI SE application:"
+msgid "Here's an example of a simple CDI SE application:"
msgstr ""
#. Tag: programlisting
@@ -308,8 +308,8 @@ msgid ""
"@Singleton\n"
"public class HelloWorld\n"
"{\n"
-" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
-" System.out.println("Hello " + parameters.get(0));\n"
+" public void printHello(@Observes ContainerInitialized event, @Parameters List<String> parameters) {\n"
+" System.out.println(\"Hello \" + parameters.get(0));\n"
" }\n"
"}"
msgstr ""
@@ -331,7 +331,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
+msgid "Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code. The Weld SE module comes with a built-in main method which will bootstrap CDI for you and then fire a ContainerInitialized event. The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example."
msgstr ""
#. Tag: para
@@ -341,17 +341,17 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "java org.jboss.weld.environment.se.StartMain <args>"
+msgid "java org.jboss.weld.environment.se.StartMain <args>"
msgstr ""
#. Tag: title
#, no-c-format
-msgid "Programatic Bootstrap API"
+msgid "Programmatic Bootstrap API"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
+msgid "For added flexibility, CDI SE also comes with a bootstrap API which can be called from within your application in order to initialize CDI and obtain references to your application's beans and events. The API consists of two classes: Weld and WeldContainer."
msgstr ""
#. Tag: programlisting
@@ -377,10 +377,10 @@ msgid ""
"{\n"
"\n"
" /** Provides access to all beans within the application. */\n"
-" public Instance<Object> instance() {...}\n"
+" public Instance<Object> instance() {...}\n"
"\n"
" /** Provides access to all events within the application. */\n"
-" public Event<Object> event() {...}\n"
+" public Event<Object> event() {...}\n"
"\n"
" /** Provides direct access to the BeanManager. */\n"
" public BeanManager getBeanManager() {...}\n"
@@ -390,7 +390,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
+msgid "Here's an example application main method which uses this API to initialize a bean of type MyApplicationBean."
msgstr ""
#. Tag: programlisting
@@ -430,22 +430,22 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
+msgid "To use the @ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable.run() and decorates them by setting up the thread context beforehand, bound to the current thread, and destroying the context afterwards."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans>\n"
-" <decorators>\n"
-" <decorator>org.jboss.weld.environment.se.threading.RunnableDecorator</decorator>\n"
-" </decorator>\n"
-"</beans>"
+"<beans>\n"
+" <decorators>\n"
+" <class>org.jboss.weld.environment.se.threading.RunnableDecorator</class>\n"
+" </decorator>\n"
+"</beans>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situtations where you would otherwise have used ThreadLocal directly, which are typically rare."
+msgid "It is not necessary to use @ThreadScoped in all multithreaded applications. The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situations where you would otherwise have used ThreadLocal directly, which are typically rare."
msgstr ""
#. Tag: title
@@ -455,7 +455,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
+msgid "Weld SE comes packaged as a 'shaded' jar which includes the CDI API, Weld Core and all dependant classes bundled into a single jar. Therefore the only Weld jar you need on the classpath, in addition to your application's classes and dependant jars, is the Weld SE jar. If you are working with a pure Java SE application you launch using java, this may be simpler for you."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-TW/events.po b/docs/reference/src/main/docbook/zh-TW/events.po
index 270c9e146bd..e1257acc2b5 100644
--- a/docs/reference/src/main/docbook/zh-TW/events.po
+++ b/docs/reference/src/main/docbook/zh-TW/events.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: events\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-15 12:08+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -39,7 +39,7 @@ msgstr "不只是事件產生器由觀察器被 decouple;觀察器也完全地
#. Tag: para
#, fuzzy, no-c-format
-msgid "observers can specify a combination of "selectors" to narrow the set of event notifications they will receive, and"
+msgid "observers can specify a combination of \"selectors\" to narrow the set of event notifications they will receive, and"
msgstr "觀察器可指定一組「選擇器(selectors)」的組合來過濾並減少它們所將會收到的事件通知數量,並且"
#. Tag: para
@@ -49,7 +49,7 @@ msgstr "觀察器可即刻地被通知,或是您亦可指定將事件的傳送
#. Tag: para
#, no-c-format
-msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
+msgid "The CDI event notification facility uses more or less the same typesafe approach that we've already seen with the dependency injection service."
msgstr ""
#. Tag: title
@@ -64,7 +64,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
+msgid "An event qualifier is just a normal qualifier, defined using @Qualifier. Here's an example:"
msgstr ""
#. Tag: programlisting
@@ -107,7 +107,7 @@ msgstr "only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
+msgid "An observer method need not specify any event qualifiers—in this case it is interested in only unqualified events of a particular type. If it does specify qualifiers, it's only interested in events which have those qualifiers."
msgstr "一個 observer method 不需要指定任何的事件綁定 在此情況下它會專注於特定 type 的所有事件。若它指定了事件綁定的話,它就只會專注於也具有這些事件綁定的事件。"
#. Tag: para
@@ -132,7 +132,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Event<Document> documentEvent;"
+msgid "@Inject @Any Event<Document> documentEvent;"
msgstr " documentEvent]]>"
#. Tag: para
@@ -187,7 +187,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
+msgid "@Inject @Updated Event<Document> documentUpdatedEvent;"
msgstr " documentUpdatedEvent]]>"
#. Tag: para
@@ -207,12 +207,12 @@ msgstr "不會指定任何的事件綁定,除了傳送給
#. Tag: para
#, no-c-format
-msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
+msgid "The downside of annotating the injection point is that we can't specify the qualifier dynamically. CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral. That way, we can pass the qualifier to the select() method of Event."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
+msgid "documentEvent.select(new AnnotationLiteral<Updated>(){}).fire(document);"
msgstr "(){} );]]>"
#. Tag: para
@@ -227,7 +227,7 @@ msgstr "交易觀察器(Transactional observers)"
#. Tag: para
#, no-c-format
-msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
+msgid "By default, if there is no instance of an observer in the current context, the container will instantiate the observer in order to deliver an event to it. This behavior isn't always desirable. We may want to deliver events only to instances of the observer that already exist in the current contexts."
msgstr ""
#. Tag: para
@@ -289,7 +289,7 @@ msgstr "事件綁定類型的成員可由事件產生器在事件通知器的注
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
+msgid "@Inject @Role(ADMIN) Event<LoggedIn> loggedInEvent;"
msgstr " LoggedInEvent;}}]]>"
#. Tag: para
@@ -301,7 +301,7 @@ msgstr "另外,事件綁定類型成員的值亦可藉由事件產生器來動
#, fuzzy, no-c-format
msgid ""
"abstract class RoleBinding \n"
-" extends AnnotationLiteral<Role> \n"
+" extends AnnotationLiteral<Role> \n"
" implements Role {}"
msgstr ""
" blogEvent;\n"
"...\n"
@@ -445,12 +445,12 @@ msgid ""
"\n"
" @PersistenceContext EntityManager em;\n"
" \n"
-" List<Product> products;\n"
+" List<Product> products;\n"
"\n"
" @Produces @Catalog \n"
-" List<Product> getCatalog() {\n"
+" List<Product> getCatalog() {\n"
" if (products==null) {\n"
-" products = em.createQuery("select p from Product p where p.deleted = false")\n"
+" products = em.createQuery(\"select p from Product p where p.deleted = false\")\n"
" .getResultList();\n"
" }\n"
" return products;\n"
@@ -492,16 +492,16 @@ msgid ""
"@Stateless\n"
"public class ProductManager {\n"
" @PersistenceContext EntityManager em;\n"
-" @Inject @Any Event<Product> productEvent;\n"
+" @Inject @Any Event<Product> productEvent;\n"
"\n"
" public void delete(Product product) {\n"
" em.delete(product);\n"
-" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Deleted>(){}).fire(product);\n"
" }\n"
" \n"
" public void persist(Product product) {\n"
" em.persist(product);\n"
-" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
+" productEvent.select(new AnnotationLiteral<Created>(){}).fire(product);\n"
" }\n"
" ...\n"
"}"
diff --git a/docs/reference/src/main/docbook/zh-TW/example.po b/docs/reference/src/main/docbook/zh-TW/example.po
index 933be75734a..423d34df6a3 100644
--- a/docs/reference/src/main/docbook/zh-TW/example.po
+++ b/docs/reference/src/main/docbook/zh-TW/example.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: example\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-15 12:13+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -24,7 +24,7 @@ msgstr "JSF 網站應用程式範例"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
+msgid "Let's illustrate these ideas with a full example. We're going to implement user login/logout for an application that uses JSF. First, we'll define a request-scoped bean to hold the username and password entered during login, with constraints defined using annotations from the Bean Validation specification:"
msgstr "現在我們將採用一個完整的範例來描述這些概念。我們將要為一個使用 JSF 的應用程式實做用戶的登錄/登出。首先,我們將要定義一個 Web Bean 來在登錄時保持已輸入的用戶名稱與密碼:"
#. Tag: programlisting
@@ -66,18 +66,18 @@ msgstr "這個 Web Bean 已透過下列 JSF 格式綁定至登錄提示:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"<h:form>\n"
-" <h:panelGrid columns="2" rendered="#{!login.loggedIn}">\n"
-" <f:validateBean>\n"
-" <h:outputLabel for="username">Username:</h:outputLabel>\n"
-" <h:inputText id="username" value="#{credentials.username}"/>\n"
-" <h:outputLabel for="password">Password:</h:outputLabel>\n"
-" <h:inputSecret id="password" value="#{credentials.password}"/>\n"
-" </f:validateBean>\n"
-" </h:panelGrid>\n"
-" <h:commandButton value="Login" action="#{login.login}" rendered="#{!login.loggedIn}"/>\n"
-" <h:commandButton value="Logout" action="#{login.logout}" rendered="#{login.loggedIn}"/>\n"
-"</h:form>"
+"<h:form>\n"
+" <h:panelGrid columns=\"2\" rendered=\"#{!login.loggedIn}\">\n"
+" <f:validateBean>\n"
+" <h:outputLabel for=\"username\">Username:</h:outputLabel>\n"
+" <h:inputText id=\"username\" value=\"#{credentials.username}\"/>\n"
+" <h:outputLabel for=\"password\">Password:</h:outputLabel>\n"
+" <h:inputSecret id=\"password\" value=\"#{credentials.password}\"/>\n"
+" </f:validateBean>\n"
+" </h:panelGrid>\n"
+" <h:commandButton value=\"Login\" action=\"#{login.login}\" rendered=\"#{!login.loggedIn}\"/>\n"
+" <h:commandButton value=\"Logout\" action=\"#{login.logout}\" rendered=\"#{login.loggedIn}\"/>\n"
+"</h:form>"
msgstr ""
"\n"
" \n"
@@ -124,7 +124,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
+msgid "(Note that we're also going to need a persistence.xml file to configure the JPA persistence unit containing User.)"
msgstr ""
#. Tag: para
@@ -144,10 +144,10 @@ msgid ""
" private User user;\n"
" \n"
" public void login() {\n"
-" List<User> results = userDatabase.createQuery(\n"
-" "select u from User u where u.username = :username and u.password = :password")\n"
-" .setParameter("username", credentials.getUsername())\n"
-" .setParameter("password", credentials.getPassword())\n"
+" List<User> results = userDatabase.createQuery(\n"
+" \"select u from User u where u.username = :username and u.password = :password\")\n"
+" .setParameter(\"username\", credentials.getUsername())\n"
+" .setParameter(\"password\", credentials.getPassword())\n"
" .getResultList();\n"
" \n"
" if (!results.isEmpty()) {\n"
@@ -293,14 +293,14 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:panelGroup rendered="#{login.loggedIn}">\n"
+"<h:panelGroup rendered=\"#{login.loggedIn}\">\n"
" signed in as #{currentUser.username}\n"
-"</h:panelGroup>"
+"</h:panelGroup>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
+msgid "Hopefully, this example gave you a taste of the CDI programming model. In the next chapter, we'll explore dependency injection in greater depth."
msgstr "但願此範例能針對於 Web Bean 程式撰寫模型(Programming Model)提供相關益處。在下個章節當中,我們將會更深入地探討 Web Bean 依賴注入(Web Beans dependency injection)。"
#~ msgid "Of course, @LoggedIn is a binding annotation:"
diff --git a/docs/reference/src/main/docbook/zh-TW/extend.po b/docs/reference/src/main/docbook/zh-TW/extend.po
index 8c1a14e83ae..0f832c6e508 100644
--- a/docs/reference/src/main/docbook/zh-TW/extend.po
+++ b/docs/reference/src/main/docbook/zh-TW/extend.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: extend\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-13 11:07+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -79,7 +79,7 @@ msgstr "Bean class"
#. Tag: para
#, no-c-format
-msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
+msgid "The first step in creating a portable extension is to write a class that implements Extension. This marker interface does not define any methods, but it's needed to satisfy the requirements of Java SE's service provider architecture."
msgstr ""
#. Tag: programlisting
@@ -167,15 +167,15 @@ msgid ""
"class MyExtension implements Extension {\n"
" \n"
" void beforeBeanDiscovery(@Observes BeforeBeanDiscovery bbd) {\n"
-" Logger.global.debug("beginning the scanning process");\n"
+" Logger.global.debug(\"beginning the scanning process\");\n"
" }\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
-" Logger.global.debug("scanning type: " + pat.getAnnotatedType().getJavaClass().getName());\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" Logger.global.debug(\"scanning type: \" + pat.getAnnotatedType().getJavaClass().getName());\n"
" } \n"
"\n"
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd) {\n"
-" Logger.global.debug("finished the scanning process");\n"
+" Logger.global.debug(\"finished the scanning process\");\n"
" }\n"
" \n"
"}"
@@ -183,7 +183,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
+msgid "In fact, the extension can do a lot more than just observe. The extension is permitted to modify the container's metamodel and more. Here's a very simple example:"
msgstr ""
#. Tag: programlisting
@@ -191,7 +191,7 @@ msgstr ""
msgid ""
"class MyExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" //tell the container to ignore the type if it is annotated @Ignore\n"
" if ( pat.getAnnotatedType().isAnnotionPresent(Ignore.class) ) pat.veto(); \n"
" } \n"
@@ -206,7 +206,7 @@ msgstr "延伸 Web Bean 的神經中樞為 Manager 這個物
#. Tag: programlisting
#, no-c-format
-msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
+msgid "<T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat, BeanManager beanManager) { ... }"
msgstr ""
#. Tag: title
@@ -223,31 +223,31 @@ msgstr "Manager 介面能讓我們程式性地註冊並取得
#, no-c-format
msgid ""
"public interface BeanManager {\n"
-" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
-" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
-" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
-" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
-" public Set<Bean<?>> getBeans(String name);\n"
-" public Bean<?> getPassivationCapableBean(String id);\n"
-" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
+" public Object getReference(Bean<?> bean, Type beanType, CreationalContext<?> ctx);\n"
+" public Object getInjectableReference(InjectionPoint ij, CreationalContext<?> ctx);\n"
+" public <T> CreationalContext<T> createCreationalContext(Contextual<T> contextual);\n"
+" public Set<Bean<?>> getBeans(Type beanType, Annotation... qualifiers);\n"
+" public Set<Bean<?>> getBeans(String name);\n"
+" public Bean<?> getPassivationCapableBean(String id);\n"
+" public <X> Bean<? extends X> resolve(Set<Bean<? extends X>> beans);\n"
" public void validate(InjectionPoint injectionPoint);\n"
" public void fireEvent(Object event, Annotation... qualifiers);\n"
-" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
-" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
-" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
-" public boolean isScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
-" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
-" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
-" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
-" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
-" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
-" public Context getContext(Class<? extends Annotation> scopeType);\n"
+" public <T> Set<ObserverMethod<? super T>> resolveObserverMethods(T event, Annotation... qualifiers);\n"
+" public List<Decorator<?>> resolveDecorators(Set<Type> types, Annotation... qualifiers);\n"
+" public List<Interceptor<?>> resolveInterceptors(InterceptionType type, Annotation... interceptorBindings);\n"
+" public boolean isScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isNormalScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isPassivatingScope(Class<? extends Annotation> annotationType);\n"
+" public boolean isQualifier(Class<? extends Annotation> annotationType);\n"
+" public boolean isInterceptorBinding(Class<? extends Annotation> annotationType);\n"
+" public boolean isStereotype(Class<? extends Annotation> annotationType);\n"
+" public Set<Annotation> getInterceptorBindingDefinition(Class<? extends Annotation> bindingType);\n"
+" public Set<Annotation> getStereotypeDefinition(Class<? extends Annotation> stereotype);\n"
+" public Context getContext(Class<? extends Annotation> scopeType);\n"
" public ELResolver getELResolver();\n"
" public ExpressionFactory wrapExpressionFactory(ExpressionFactory expressionFactory);\n"
-" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
-" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
+" public <T> AnnotatedType<T> createAnnotatedType(Class<T> type);\n"
+" public <T> InjectionTarget<T> createInjectionTarget(AnnotatedType<T> type);\n"
"}"
msgstr ""
@@ -268,7 +268,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's study some of the interfaces exposed by the BeanManager."
+msgid "Let's study some of the interfaces exposed by the BeanManager."
msgstr "延伸 Web Bean 的神經中樞為 Manager 這個物件。"
#. Tag: title
@@ -283,21 +283,21 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to instatiate the object itself, and so only method and field injection will be supported."
+msgid "We recommend that frameworks let CDI take over the job of actually instantiating the framework-controlled objects. That way, the framework-controlled objects can take advantage of constructor injection. However, if the framework requires use of a constructor with a special signature, the framework will need to insntatiate the object itself, and so only method and field injection will be supported."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
"//get the BeanManager from JNDI\n"
-"BeanManager beanManager = (BeanManager) new InitialContext().lookup("java:comp/BeanManager");\n"
+"BeanManager beanManager = (BeanManager) new InitialContext().lookup(\"java:comp/BeanManager\");\n"
"\n"
"//CDI uses an AnnotatedType object to read the annotations of a class\n"
-"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
+"AnnotatedType<SomeFrameworkComponent> type = beanManager.createAnnotatedType(SomeFrameworkComponent.class);\n"
"\n"
"//The extension uses an InjectionTarget to delegate instantiation, dependency injection \n"
"//and lifecycle callbacks to the CDI container\n"
-"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
+"InjectionTarget<SomeFrameworkComponent> it = beanManager.createInjectionTarget(type);\n"
"\n"
"//each instance needs its own CDI CreationalContext\n"
"CreationalContext ctx = beanManager.createCreationalContext(null);\n"
@@ -327,33 +327,33 @@ msgstr "Bean 這個 abstract class 的 instance 代表 Web Be
#. Tag: para
#, no-c-format
-msgid "The Bean interface exposes all the interesting things we dicussed in ."
+msgid "The Bean interface exposes all the interesting things we discussed in ."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"public interface Bean<T> extends Contextual<T> {\n"
-" public Set<Type> getTypes();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Class<? extends Annotation> getScope();\n"
+"public interface Bean<T> extends Contextual<T> {\n"
+" public Set<Type> getTypes();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Class<? extends Annotation> getScope();\n"
" public String getName();\n"
-" public Set<Class<? extends Annotation>> getStereotypes();\n"
-" public Class<?> getBeanClass();\n"
+" public Set<Class<? extends Annotation>> getStereotypes();\n"
+" public Class<?> getBeanClass();\n"
" public boolean isAlternative();\n"
" public boolean isNullable();\n"
-" public Set<InjectionPoint> getInjectionPoints();\n"
+" public Set<InjectionPoint> getInjectionPoints();\n"
"}"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's an easy way to find out what beans exist in the application:"
+msgid "There's an easy way to find out what beans exist in the application:"
msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
+msgid "Set<Bean<?>> allBeans = beanManager.getBeans(Obect.class, new AnnotationLiteral<Any>() {});"
msgstr ""
#. Tag: para
@@ -373,7 +373,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
+msgid "In this example, we make a framework class, SecurityManager available for injection. To make things a bit more interesting, we're going to delegate back to the container's InjectionTarget to perform instantiation and injection upon the SecurityManager instance."
msgstr ""
#. Tag: programlisting
@@ -384,49 +384,49 @@ msgid ""
" void afterBeanDiscovery(@Observes AfterBeanDiscovery abd, BeanManager bm) {\n"
" \n"
" //use this to read annotations of the class\n"
-" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
+" AnnotatedType<SecurityManager> at = bm.createAnnotatedType(SecurityManager.class); \n"
"\n"
" //use this to instantiate the class and inject dependencies\n"
-" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
+" final InjectionTarget<SecurityManager> it = bm.createInjectionTarget(at); \n"
"\n"
-" abd.addBean( new Bean<SecurityManager>() {\n"
+" abd.addBean( new Bean<SecurityManager>() {\n"
"\n"
" @Override\n"
-" public Class<?> getBeanClass() {\n"
+" public Class<?> getBeanClass() {\n"
" return SecurityManager.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
" public String getName() {\n"
-" return "securityManager";\n"
+" return \"securityManager\";\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getQualifiers() {\n"
-" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
-" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
-" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
+" public Set<Annotation> getQualifiers() {\n"
+" Set<Annotation> qualifiers = new HashSet<Annotation>();\n"
+" qualifiers.add( new AnnotationLiteral<Default>() {} );\n"
+" qualifiers.add( new AnnotationLiteral<Any>() {} );\n"
" return qualifiers;\n"
" }\n"
"\n"
" @Override\n"
-" public Class<? extends Annotation> getScope() {\n"
+" public Class<? extends Annotation> getScope() {\n"
" return SessionScoped.class;\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Class<? extends Annotation>> getStereotypes() {\n"
+" public Set<Class<? extends Annotation>> getStereotypes() {\n"
" return Collections.emptySet();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypes() {\n"
-" Set<Type> types = new HashSet<Type>();\n"
+" public Set<Type> getTypes() {\n"
+" Set<Type> types = new HashSet<Type>();\n"
" types.add(SecurityManager.class);\n"
" types.add(Object.class);\n"
" return types;\n"
@@ -443,7 +443,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
+" public SecurityManager create(CreationalContext<SecurityManager> ctx) {\n"
" SecurityManager instance = it.produce(ctx);\n"
" it.inject(instance, ctx);\n"
" it.postConstruct(instance);\n"
@@ -452,7 +452,7 @@ msgid ""
"\n"
" @Override\n"
" public void destroy(SecurityManager instance, \n"
-" CreationalContext<SecurityManager> ctx) {\n"
+" CreationalContext<SecurityManager> ctx) {\n"
" it.preDestroy(instance);\n"
" it.dispose(instance);\n"
" ctx.release();\n"
@@ -481,7 +481,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
+msgid "Let's start with an example of an extension that provides support for the use of @Named at the package level. The package-level name is used to qualify the EL names of all beans defined in that package. The portable extension uses the ProcessAnnotatedType event to wrap the AnnotatedType object and override the value() of the @Named annotation."
msgstr ""
#. Tag: programlisting
@@ -489,38 +489,38 @@ msgstr ""
msgid ""
"public class QualifiedNameExtension implements Extension {\n"
"\n"
-" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
+" <X> void processAnnotatedType(@Observes ProcessAnnotatedType<X> pat) {\n"
"\n"
" //wrap this to override the annotations of the class\n"
-" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
+" final AnnotatedType<X> at = pat.getAnnotatedType();\n"
" \n"
-" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
+" AnnotatedType<X> wrapped = new AnnotatedType<X>() {\n"
"\n"
" @Override\n"
-" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
+" public Set<AnnotatedConstructor<X>> getConstructors() {\n"
" return at.getConstructors();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedField<? super X>> getFields() {\n"
+" public Set<AnnotatedField<? super X>> getFields() {\n"
" return at.getFields();\n"
" }\n"
"\n"
" @Override\n"
-" public Class<X> getJavaClass() {\n"
+" public Class<X> getJavaClass() {\n"
" return at.getJavaClass();\n"
" }\n"
"\n"
" @Override\n"
-" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
+" public Set<AnnotatedMethod<? super X>> getMethods() {\n"
" return at.getMethods();\n"
" }\n"
"\n"
" @Override\n"
-" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
+" public <T extends Annotation> T getAnnotation(final Class<T> annType) {\n"
" if ( Named.class.equals(annType) ) {\n"
" class NamedLiteral \n"
-" extends AnnotationLiteral<Named> \n"
+" extends AnnotationLiteral<Named> \n"
" implements Named {\n"
" @Override\n"
" public String value() {\n"
@@ -529,7 +529,7 @@ msgid ""
" final String qualifiedName;\n"
" if ( pkg.isAnnotationPresent(Named.class) ) {\n"
" qualifiedName = pkg.getAnnotation(Named.class).value() \n"
-" + '.' + unqualifiedName;\n"
+" + '.' + unqualifiedName;\n"
" }\n"
" else {\n"
" qualifiedName = unqualifiedName;\n"
@@ -545,7 +545,7 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Annotation> getAnnotations() {\n"
+" public Set<Annotation> getAnnotations() {\n"
" return at.getAnnotations();\n"
" }\n"
"\n"
@@ -555,12 +555,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<Type> getTypeClosure() {\n"
+" public Set<Type> getTypeClosure() {\n"
" return at.getTypeClosure();\n"
" }\n"
"\n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annType) {\n"
" return at.isAnnotationPresent(annType);\n"
" }\n"
" \n"
@@ -574,7 +574,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
+msgid "Here's a second example, which adds the @Alternative annotation to any class which implements a certain Service interface."
msgstr ""
#. Tag: programlisting
@@ -582,17 +582,17 @@ msgstr ""
msgid ""
"class ServiceAlternativeExtension implements Extension {\n"
" \n"
-" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
+" <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) {\n"
" \n"
-" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
+" final AnnotatedType<T> type = pat.getAnnotatedType();\n"
" \n"
" if ( Service.class.isAssignableFrom( type.getJavaClass() ) ) {\n"
" \n"
" //if the class implements Service, make it an @Alternative\n"
-" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
+" AnnotatedType<T> wrapped = new AnnotatedType<T>() {\n"
" \n"
" @Override\n"
-" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
+" public boolean isAnnotationPresent(Class<? extends Annotation> annotationType) {\n"
" return annotationType.equals(Alternative.class) ? \n"
" true : type.isAnnotationPresent(annotationType);\n"
" }\n"
@@ -625,7 +625,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
+msgid "Here's a CDI portable extension that reads values from properties files and configures fields of Java EE components, including servlets, EJBs, managed beans, interceptors and more. In this example, properties for a class such as org.mydomain.blog.Blogger go in a resource named org/mydomain/blog/Blogger.properties, and the name of a property must match the name of the field to be configured. So Blogger.properties could contain:"
msgstr ""
#. Tag: programlisting
@@ -645,25 +645,25 @@ msgstr ""
msgid ""
"public class ConfigExtension implements Extension {\n"
"\n"
-"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
+"\t<X> void processInjectionTarget(@Observes ProcessInjectionTarget<X> pit) {\n"
"\t\t\n"
"\t\t//wrap this to intercept the component lifecycle\n"
-"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
+"\t final InjectionTarget<X> it = pit.getInjectionTarget();\n"
"\t \n"
-" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
+" final Map<Field, Object> configuredValues = new HashMap<Field, Object>();\n"
" \n"
" //use this to read annotations of the class and its members\n"
-" AnnotatedType<X> at = pit.getAnnotatedType();\n"
+" AnnotatedType<X> at = pit.getAnnotatedType();\n"
" \n"
" //read the properties file\n"
-" String propsFileName = at.getClass().getSimpleName() + ".properties";\n"
+" String propsFileName = at.getClass().getSimpleName() + \".properties\";\n"
" InputStream stream = at.getJavaClass().getResourceAsStream(propsFileName);\n"
" if (stream!=null) {\n"
" \n"
" try {\n"
" Properties props = new Properties();\n"
" props.load(stream);\n"
-" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
+" for (Map.Entry<Object, Object> property : props.entrySet()) {\n"
" String fieldName = property.getKey().toString();\n"
" Object value = property.getValue();\n"
" try {\n"
@@ -675,7 +675,7 @@ msgid ""
" else {\n"
" //TODO: do type conversion automatically\n"
" pit.addDefinitionError( new InjectionException(\n"
-" "field is not of type String: " + field ) );\n"
+" \"field is not of type String: \" + field ) );\n"
" }\n"
" }\n"
" catch (NoSuchFieldException nsfe) {\n"
@@ -691,14 +691,14 @@ msgid ""
" }\n"
" }\n"
" \n"
-" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
+" InjectionTarget<X> wrapped = new InjectionTarget<X>() {\n"
"\n"
" @Override\n"
-" public void inject(X instance, CreationalContext<X> ctx) {\n"
+" public void inject(X instance, CreationalContext<X> ctx) {\n"
" it.inject(instance, ctx);\n"
" \n"
" //set the values onto the new instance of the component\n"
-" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
+" for (Map.Entry<Field, Object> configuredValue: configuredValues.entrySet()) {\n"
" try {\n"
" configuredValue.getKey().set(instance, configuredValue.getValue());\n"
" }\n"
@@ -724,12 +724,12 @@ msgid ""
" }\n"
"\n"
" @Override\n"
-" public Set<InjectionPoint> getInjectionPoints() {\n"
+" public Set<InjectionPoint> getInjectionPoints() {\n"
" return it.getInjectionPoints();\n"
" }\n"
"\n"
" @Override\n"
-" public X produce(CreationalContext<X> ctx) {\n"
+" public X produce(CreationalContext<X> ctx) {\n"
" return it.produce(ctx);\n"
" }\n"
" \n"
@@ -744,7 +744,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
+msgid "There's a lot more to the portable extension SPI than what we've discussed here. Check out the CDI spec or Javadoc for more information. For now, we'll just mention one more extension point."
msgstr ""
#. Tag: title
@@ -761,9 +761,9 @@ msgstr "Context 介面支援新增額外的 Web Bean 功能
#, fuzzy, no-c-format
msgid ""
"public interface Context {\n"
-" public Class<? extends Annotation> getScope();\n"
-" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
-" public <T> T get(Contextual<T> contextual);\n"
+" public Class<? extends Annotation> getScope();\n"
+" public <T> T get(Contextual<T> contextual, CreationalContext<T> creationalContext);\n"
+" public <T> T get(Contextual<T> contextual);\n"
" boolean isActive();\n"
"}"
msgstr ""
diff --git a/docs/reference/src/main/docbook/zh-TW/gettingstarted.po b/docs/reference/src/main/docbook/zh-TW/gettingstarted.po
index 77a3c8819cc..9aed6103d4a 100644
--- a/docs/reference/src/main/docbook/zh-TW/gettingstarted.po
+++ b/docs/reference/src/main/docbook/zh-TW/gettingstarted.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: ri\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-19 18:21+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -24,7 +24,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, Glassfish 3.0 or any compliant Java EE 6 container."
+msgid "Weld comes with a number of examples. We recommend you start with examples/jsf/numberguess and examples/jsf/translator. Numberguess is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. Translator is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, GlassFish 3.0 or any compliant Java EE 6 container."
msgstr ""
#. Tag: para
@@ -39,7 +39,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To run the examples with the provided build scripts, you'll need the following:"
+msgid "To run the examples with the provided build scripts, you'll need the following:"
msgstr ""
#. Tag: para
@@ -84,12 +84,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
+msgid "You'll need a full install of Ant 1.7.0. Some linux distributions only supply a partial installation of Ant which cause the build to fail. If you encounter problems, verify that ant-nodeps.jar is on the classpath."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
+msgid "In the next few sections, you'll be using the Ant command (ant) to invoke the Ant build script in each example to compile, assemble and deploy the example to JBoss AS and, for the war example, Apache Tomcat. You can also deploy the generated artifact (war or ear) to any other container that supports Java EE 6, such as GlassFish 3."
msgstr ""
#. Tag: para
@@ -99,7 +99,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
+msgid "The sections below cover the steps for deploying with both Ant and Maven in detail. Let's start with JBoss AS."
msgstr ""
#. Tag: title
@@ -109,19 +109,19 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
+msgid "To deploy the examples to JBoss AS, you'll need JBoss AS 6.0.0 or above. If a release of the JBoss AS 6.0 line isn't yet available, you can download a nightly snapshot. The reason JBoss AS 6.0.0 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go!"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
+msgid "After you have downloaded JBoss AS, extract it. (We recommended renaming the folder to include the as qualifier so it's clear that it's the application server). You can move the extracted folder anywhere you like. Wherever it lays to rest, that's what we'll call the JBoss AS installation directory, or JBOSS_HOME."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> unzip jboss-6.0.*.zip\n"
-"$> mv jboss-6.0.*/ jboss-as-6.0"
+"$> unzip jboss-6.0.*.zip\n"
+"$> mv jboss-6.0.*/ jboss-as-6.0"
msgstr ""
#. Tag: para
@@ -136,7 +136,7 @@ msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
#, fuzzy, no-c-format
-msgid "You're now ready to deploy your first example!"
+msgid "You're now ready to deploy your first example!"
msgstr "現在,您已準備好建置您的第一個範例!"
#. Tag: para
@@ -147,22 +147,22 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant deploy"
msgstr ""
"$ cd examples/numberguess\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
+msgid "If you haven't already, start JBoss AS. You can either start JBoss AS from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/jboss-as-6.0\n"
-"$> ./bin/run.sh"
+"$> cd /path/to/jboss-as-6.0\n"
+"$> ./bin/run.sh"
msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
@@ -171,11 +171,11 @@ msgid "a Windows command window:"
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
-"$> run"
-msgstr ""
+"$> cd c:\\path\\to\\jboss-as-6.0\\bin\n"
+"$> run"
+msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
#, no-c-format
@@ -230,20 +230,20 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/translator\n"
-"$> ant deploy"
+"$> cd examples/jsf/translator\n"
+"$> ant deploy"
msgstr ""
"$ cd examples/translator\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
+msgid "The translator uses session beans, which are packaged in an EJB module within an ear. Java EE 6 will allow session beans to be deployed in war modules, but that's a topic for a later chapter."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
+msgid "Again, wait a few seconds for the application to deploy (if you're really bored, read the log messages), and visit http://localhost:8080/weld-translator to begin pseudo-translating."
msgstr "在此我們將設置 context 路徑,它能提供給我們一個網址(http://localhost:8080/webbeans-translator)。"
#. Tag: title
@@ -253,41 +253,43 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
+msgid "Deploying to GlassFish should be easy and familiar, right? After all, it's the Java EE 6 reference implementation and Weld is the JSR-299 reference implementation, meaning Weld gets bundled with GlassFish. So yes, it's all quite easy and familiar."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
+msgid "To deploy the examples to GlassFish, you'll need the final GlassFish V3 release. Select the release that ends in either -unix.sh or -windows.exe depending on your platform. After the download is complete, execute the installer. On Linux/Unix, you'll need to first make the script executable."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"$> chmod 755 glassfish-v3-unix.sh\n"
-"$> ./glassfish-v3-unix.sh"
+"$> chmod 755 glassfish-v3-unix.sh\n"
+"$> ./glassfish-v3-unix.sh"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
+msgid "On Windows you can just click on the executable. Follow the instructions in the installer. It will create a single domain named domain1. You'll use that domain to deploy the example. We recommend that you choose 7070 as the main HTTP port to avoid conflicts with a running instance of JBoss AS (or Apache Tomcat)."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
+msgid "If you've deployed either of the starter examples, weld-numberguess or weld-translator, to JBoss AS, then you already have the deployable artifact you need. If not, switch to either of the two directories and build it."
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
-"$> ant package"
+"$> cd examples/jsf/numberguess (or examples/jsf/translator)\n"
+"$> ant package"
msgstr ""
+"$ cd examples/numberguess\n"
+"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
+msgid "The deployable archive for the weld-numberguess, named weld-numberguess.war, ends up in the example's target directory. The archive for the weld-translator example, named weld-translator.ear, ends up in the example's ear/target directory. All you need to do now is deploy them to GlassFish."
msgstr ""
#. Tag: para
@@ -297,12 +299,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin start-domain domain1"
+msgid "$> asadmin start-domain domain1"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on "Applications", then click on the "Deploy..." button under the heading "Applications" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
+msgid "After a few seconds you can visit the Admin Console in the browser at the URL http://localhost:4848. In the tree on the left-hand side of the page, click on \"Applications\", then click on the \"Deploy...\" button under the heading \"Applications\" and select the deployable artifact for either of the two examples. The deployer should recognize that you have selected a Java EE artifact and allow you to start it. You can see the examples running at either http://localhost:7070/weld-numberguess or http://localhost:7070/weld-translator, depending on which example you deployed."
msgstr ""
#. Tag: para
@@ -312,7 +314,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> asadmin deploy target/weld-numberguess.war"
+msgid "$> asadmin deploy target/weld-numberguess.war"
msgstr ""
#. Tag: para
@@ -332,24 +334,24 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
+msgid "Weld comes with a servlet listener which bootstraps the CDI environment, registers the BeanManager in JNDI and provides injection into servlets. Basically, it emulates some of the work done by the Java EE container. (But you don't get enterprise features such as session beans and container-managed transactions.)"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
+msgid "Let's give the Weld servlet extension a spin on Apache Tomcat. First, you'll need to download Tomcat 6.0.18 or later from tomcat.apache.org and extract it."
msgstr "接下來,請由 seamframework.org 下載 Web Beans RI 並將它解壓縮。例如"
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "$> unzip apache-tomcat-6.0.18.zip"
+msgid "$> unzip apache-tomcat-6.0.18.zip"
msgstr ""
""
#. Tag: para
#, no-c-format
-msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
+msgid "You have two choices for how you can deploy the application to Tomcat. You can deploy it by pushing the artifact to the hot deploy directory using Ant or you can deploy to the server across HTTP using a Maven plugin. The Ant approach doesn't require that you have Maven installed, so we'll start there. If you want to use Maven, you can just skip ahead."
msgstr ""
#. Tag: title
@@ -359,7 +361,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
+msgid "In order for Ant to push the artifact to the Tomcat hot deploy directory, it needs to know where the Tomcat installation is located. Again, we need to set a property in the local.build.properties file in the examples directory of the Weld distribution. If you haven't yet created this file, do so now. Then assign the path of your Tomcat installation to the property key tomcat.home."
msgstr ""
#. Tag: programlisting
@@ -369,7 +371,7 @@ msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now you're ready to deploy the numberguess example to Tomcat!"
+msgid "Now you're ready to deploy the numberguess example to Tomcat!"
msgstr "若要建置 numberguess 範例:"
#. Tag: para
@@ -380,15 +382,15 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> ant tomcat.deploy"
+"$> cd examples/jsf/numberguess\n"
+"$> ant tomcat.deploy"
msgstr ""
"$ cd examples/numberguess\n"
"ant deploy"
#. Tag: para
#, no-c-format
-msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with "tomcat."."
+msgid "The Ant build script includes additional targets for Tomcat to deploy and undeploy the archive in either exploded or packaged format. They are the same target names used for JBoss AS, prefixed with \"tomcat.\"."
msgstr ""
#. Tag: para
@@ -413,21 +415,21 @@ msgstr "ant undeploy - 將範例由伺服器中移除"
#. Tag: para
#, no-c-format
-msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
+msgid "If you haven't already, start Tomcat. You can either start Tomcat from a Linux shell:"
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd /path/to/apache-tomcat-6\n"
-"$> ./bin/start.sh"
+"$> cd /path/to/apache-tomcat-6\n"
+"$> ./bin/start.sh"
msgstr "jboss.home=/Applications/jboss-5.0.0.GA"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
-"$> start"
+"$> cd c:\\path\\to\\apache-tomcat-6\\bin\n"
+"$> start"
msgstr ""
""
@@ -444,12 +446,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
+msgid "You can also deploy the application to Tomcat using Maven. This section is a bit more advanced, so skip it unless you're itching to use Maven natively. Of course, you'll first need to make sure that you have Maven installed on your path, similar to how you setup Ant."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
+msgid "The Maven plugin communicates with Tomcat over HTTP, so it doesn't care where you have installed Tomcat. However, the plugin configuration assumes you are running Tomcat in its default configuration, with a hostname of localhost and port 8080. The readme.txt file in the example directory has information about how to modify the Maven settings to accommodate a different setup."
msgstr ""
#. Tag: para
@@ -459,7 +461,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "<user username="admin" password="" roles="manager"/>"
+msgid "<user username=\"admin\" password=\"\" roles=\"manager\"/>"
msgstr ""
#. Tag: para
@@ -469,7 +471,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
+msgid "$> mvn compile war:exploded tomcat:exploded -Ptomcat"
msgstr ""
#. Tag: para
@@ -479,7 +481,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn tomcat:redeploy -Ptomcat"
+msgid "$> mvn tomcat:redeploy -Ptomcat"
msgstr ""
#. Tag: para
@@ -494,7 +496,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace tomcat:run -Ptomcat"
+msgid "$> mvn war:inplace tomcat:run -Ptomcat"
msgstr ""
#. Tag: para
@@ -504,12 +506,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Ptomcat"
+msgid "$> mvn compile war:inplace -Ptomcat"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
+msgid "There are several other Maven goals that you can use if you are hacking on the example, which are documented in the example's readme.txt file."
msgstr ""
#. Tag: title
@@ -524,12 +526,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
+msgid "If you've read through the entire Tomcat section, then you're all ready to go. The Maven build parallels the embedded Tomcat deployment. If not, don't worry. We'll still go over everything that you need to know again in this section."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
+msgid "The Maven POM (pom.xml) includes a profile named jetty that activates the Maven Jetty plugin, which you can use to start Jetty in embedded mode and deploy the application in place. You don't need anything else installed except to have the Maven command (mvn) on your path. The rest will be downloaded from the internet when the build is run."
msgstr ""
#. Tag: para
@@ -538,11 +540,13 @@ msgid "To run the weld-numberguess example on Jetty, switch t
msgstr ""
#. Tag: programlisting
-#, no-c-format
+#, fuzzy, no-c-format
msgid ""
-"$> cd examples/jsf/numberguess\n"
-"$> mvn war:inplace jetty:run -Pjetty"
+"$> cd examples/jsf/numberguess\n"
+"$> mvn war:inplace jetty:run -Pjetty"
msgstr ""
+"$ cd examples/numberguess\n"
+"ant deploy"
#. Tag: para
#, no-c-format
@@ -556,7 +560,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn compile war:inplace -Pjetty"
+msgid "$> mvn compile war:inplace -Pjetty"
msgstr ""
#. Tag: para
@@ -566,7 +570,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclispe[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
+msgid "You have two options if you want to run the example on Jetty from the IDE. You can either install the m2eclipse[link] plugin and run the goals as described above. Your other option is to start the Jetty container from a Java application."
msgstr ""
#. Tag: para
@@ -576,7 +580,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
+msgid "$> mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide"
msgstr ""
#. Tag: para
@@ -586,12 +590,12 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "$> mvn war:inplace -Pjetty-ide"
+msgid "$> mvn war:inplace -Pjetty-ide"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using "Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
+msgid "Now, you are ready to run the server in Eclipse. Import the project into your Eclipse workspace using \"Import Existing Project into Workspace. Then, find the start class in src/jetty/java and run its main method as a Java Application. Jetty will launch. You can view the application at the following local URL: http://localhost:8080. Pay particular attention to the port in the URL and the lack of a trailing context path."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-TW/injection.po b/docs/reference/src/main/docbook/zh-TW/injection.po
index 1f6ae75039c..a142fdea7f4 100644
--- a/docs/reference/src/main/docbook/zh-TW/injection.po
+++ b/docs/reference/src/main/docbook/zh-TW/injection.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: injection\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-19 16:05+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -24,7 +24,7 @@ msgstr "依賴注入(Dependency injection)"
#. Tag: para
#, no-c-format
-msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
+msgid "One of the most significant features of CDI—certainly the most recognized—is dependency injection; excuse me, typesafe dependency injection."
msgstr ""
#. Tag: title
@@ -149,7 +149,7 @@ msgstr "接下來,Web Bean 管理員便會初始化 Web Bean 所有已注入
#. Tag: para
#, fuzzy, no-c-format
-msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
+msgid "Next, the container calls all initializer methods of bean (the call order is not portable, don't rely on it)."
msgstr "然後,Web Bean 管理員將會調用 Web Bean 的所有 initializer method。"
#. Tag: para
@@ -185,7 +185,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
+msgid "This is a case where the @Inject annotation is not required at the injection point. The same is true for observer methods (which we'll meet in ) and disposer methods."
msgstr ""
#. Tag: title
@@ -195,7 +195,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
+msgid "The CDI specification defines a procedure, called typesafe resolution, that the container follows when identifying the bean to inject to an injection point. This algorithm looks complex at first, but once you understand it, it's really quite intuitive. Typesafe resolution is performed at system initialization time, which means that the container will inform the developer immediately if a bean's dependencies cannot be satisfied."
msgstr "Web Bean 規格定義了一個流程,該流程稱為 typesafe resolution algorithm(typesafe 解析演算法),當 Web Bean 要注入至一個注入點時,Web Bean 管理員便會遵照該流程來進行。這個演算法乍看之下非常地複雜,不過當您理解它之後,您會發現它實際上並不複雜。Typesafe 解析會在系統初始化時進行,這也代表了若 Web Bean 的相依性無法被滿足的話,管理員會即刻透過回傳一個 UnsatisfiedDependencyException 或是 AmbiguousDependencyException 來通知用戶。"
#. Tag: para
@@ -220,12 +220,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
+msgid "Obviously, if you have exactly one bean of a given type, and an injection point with that same type, then bean A is going to go into slot A. That's the simplest possible scenario. When you first start your application, you'll likely have lots of those."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
+msgid "But then, things start to get complicated. Let's explore how the container determines which bean to inject in more advanced cases. We'll start by taking a closer look at qualifiers."
msgstr ""
#. Tag: title
@@ -386,7 +386,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, you may be thinking, "What's the different between using a qualifier and just specifying the exact implementation class you want?" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alterative implementations of @Asynchronous PaymentProcessor!"
+msgid "Now, you may be thinking, \"What's the different between using a qualifier and just specifying the exact implementation class you want?\" It's important to understand that a qualifier is like an extension of the interface. It does not create a direct dependency to any particular implementation. There may be multiple alternative implementations of @Asynchronous PaymentProcessor!"
msgstr ""
#. Tag: title
@@ -396,7 +396,7 @@ msgstr "基本的 Web Bean 只支援 @PostConstruct 和 @Default. From time to time, you'll need to decare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
+msgid "Whenever a bean or injection point does not explicitly declare a qualifier, the container assumes the qualifier @Default. From time to time, you'll need to declare an injection point without specifying a qualifier. There's a qualifier for that too. All beans have the qualifier @Any. Therefore, by explicitly specifying @Any at an injection point, you suppress the default qualifier, without otherwise restricting the beans that are eligible for injection."
msgstr ""
#. Tag: para
@@ -408,7 +408,7 @@ msgstr ""
#, no-c-format
msgid ""
"@Inject \n"
-"void initServices(@Any Instance<Service> services) { \n"
+"void initServices(@Any Instance<Service> services) { \n"
" for (Service service: services) {\n"
" service.init();\n"
" }\n"
@@ -444,7 +444,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Then we select one of the possible member values when appling the qualifier:"
+msgid "Then we select one of the possible member values when applying the qualifier:"
msgstr ""
#. Tag: programlisting
@@ -465,7 +465,7 @@ msgid ""
"@Target({METHOD, FIELD, PARAMETER, TYPE})\n"
"public @interface PayBy {\n"
" PaymentMethod value();\n"
-" @Nonbinding String comment() default "";\n"
+" @Nonbinding String comment() default \"\";\n"
"}"
msgstr ""
"this FAQ for step-by-step instructions for how to resolve an ambigous resolution exception between a raw bean type and a producer method that returns the same bean type."
+msgid "See this FAQ for step-by-step instructions for how to resolve an ambiguous resolution exception between a raw bean type and a producer method that returns the same bean type."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Just remember: "There can be only one.""
+msgid "Just remember: \"There can be only one.\""
msgstr ""
#. Tag: para
#, no-c-format
-msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
+msgid "On the other hand, if you really do have an optional or multivalued injection point, you should change the type of your injection point to Instance, as we'll see in ."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
+msgid "Now there's one more issue you need to be aware of when using the dependency injection service."
msgstr "當您在 Web Bean 中使用依賴注入時,您還需要注意一個問題。"
#. Tag: title
@@ -648,7 +648,7 @@ msgstr "一個已注入的 Web Bean 的客戶端通常不會持有一個 Web Bea
#. Tag: para
#, fuzzy, no-c-format
-msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
+msgid "Imagine that a bean bound to the application scope held a direct reference to a bean bound to the request scope. The application-scoped bean is shared between many different requests. However, each request should see a different instance of the request scoped bean—the current one!"
msgstr "想像一個綁定至應用程式 scope 的 Web Bean 持有一個綁定至請求 scope 的 Web Bean 的直接參照。這個應用程式 scope 的 Web Bean 會在許多不同的請求之間被共享。不過,各個請求都應要看見一個不同的請求 scope Web Bean 的 instance!"
#. Tag: para
@@ -673,7 +673,7 @@ msgstr "下列 Java 類型無法被 Web Bean 管理員代理:"
#. Tag: para
#, fuzzy, no-c-format
-msgid "classes which don't have a non-private constructor with no parameters, and"
+msgid "classes which don't have a non-private constructor with no parameters, and"
msgstr "沒有非私密 constructor 的無參數 class,以及"
#. Tag: para
@@ -688,7 +688,7 @@ msgstr "陣列(array)與基本型別(primitive type)。"
#. Tag: para
#, no-c-format
-msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
+msgid "It's usually very easy to fix an unproxyable dependency problem. If an injection point of type X results in an unproxyable dependency, simply:"
msgstr ""
#. Tag: para
@@ -698,7 +698,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "change the type of the injection point to Instance<X>,"
+msgid "change the type of the injection point to Instance<X>,"
msgstr ""
#. Tag: para
@@ -728,7 +728,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "But we didn't get around to implementing this yet."
+msgid "But we didn't get around to implementing this yet."
msgstr ""
#. Tag: title
@@ -763,7 +763,7 @@ msgstr "應用程式可透過注入來取得 Manager 這個
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -798,7 +798,7 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Asynchronous Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
@@ -813,19 +813,19 @@ msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
+msgid "@Inject @Any Instance<PaymentProcessor> paymentProcessorSource;"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, we need to obtain an instance of our qualifier type. Since annotatons are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
+msgid "Next, we need to obtain an instance of our qualifier type. Since annotations are interfaces, we can't just write new Asynchronous(). It's also quite tedious to create a concrete implementation of an annotation type from scratch. Instead, CDI lets us obtain a qualifier instance by subclassing the helper class AnnotationLiteral."
msgstr ""
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"abstract class AsynchronousQualifier\n"
-"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
+"class AsynchronousQualifier\n"
+"extends AnnotationLiteral<Asynchronous> implements Asynchronous {}"
msgstr ""
" \n"
@@ -840,14 +840,14 @@ msgstr ""
#, fuzzy, no-c-format
msgid ""
"PaymentProcessor p = paymentProcessorSource\n"
-" .select(new AnnotationLiteral<Asynchronous>() {});"
+" .select(new AnnotationLiteral<Asynchronous>() {});"
msgstr ""
"(){});]]>"
#. Tag: para
#, no-c-format
-msgid "We can't use an anonymous class to implement a qualifier type with members."
+msgid "However, we can't use an anonymous class to implement a qualifier type with members."
msgstr ""
#. Tag: para
@@ -895,7 +895,7 @@ msgstr "含有 @Dependent 這個 scope 的 Web Bean 能夠注
#. Tag: para
#, fuzzy, no-c-format
-msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
+msgid "Let's look at an example. The following code is verbose, and vulnerable to refactoring problems:"
msgstr "讓我們來探討下列範例。下列程式碼較為冗長,並且有重構(refactoring)問題上的弱點:"
#. Tag: programlisting
@@ -939,7 +939,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
+msgid "Not convinced? Then here's a second example. To inject HTTP parameters, we need to define a qualifier type:"
msgstr "若您無法被說服的話,我們還有第二個範例。若要注入 HTTP 參數,我們需要定義一個綁定類型:"
#. Tag: programlisting
@@ -967,8 +967,8 @@ msgstr "我們可如下在注入點使用此綁定類型:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@HttpParam("username") String username;\n"
-"@HttpParam("password") String password;"
+"@HttpParam(\"username\") String username;\n"
+"@HttpParam(\"password\") String password;"
msgstr ""
""
@@ -983,7 +983,7 @@ msgstr "下列 producer method 可完成此工作:"
msgid ""
"class HttpParams\n"
"\n"
-" @Produces @HttpParam("")\n"
+" @Produces @HttpParam(\"\")\n"
" String getParamValue(InjectionPoint ip) {\n"
" ServletRequest request = (ServletRequest) FacesContext.getCurrentInstance().getExternalContext().getRequest();\n"
" return request.getParameter(ip.getAnnotated().getAnnotation(HttpParam.class).value());\n"
@@ -1002,7 +1002,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own prodcuer for the request and have it injected as a method parameter."
+msgid "Note that acquiring of the request in this example is JSF-centric. For a more generic solution you could write your own producer for the request and have it injected as a method parameter."
msgstr ""
#. Tag: para
@@ -1020,8 +1020,8 @@ msgstr "Web Bean 管理員提供了實做 InjectionPoint 介
msgid ""
"public interface InjectionPoint { \n"
" public Type getType();\n"
-" public Set<Annotation> getQualifiers();\n"
-" public Bean<?> getBean();\n"
+" public Set<Annotation> getQualifiers();\n"
+" public Bean<?> getBean();\n"
" public Member getMember();\n"
" public Annotated getAnnotated();\n"
" public boolean isDelegate();\n"
diff --git a/docs/reference/src/main/docbook/zh-TW/interceptors.po b/docs/reference/src/main/docbook/zh-TW/interceptors.po
index 00e54ead03e..c367f735fac 100644
--- a/docs/reference/src/main/docbook/zh-TW/interceptors.po
+++ b/docs/reference/src/main/docbook/zh-TW/interceptors.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: interceptors\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-15 12:13+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -110,7 +110,7 @@ msgstr "攔截器綁定"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
+msgid "Suppose we want to declare that some of our beans are transactional. The first thing we need is an interceptor binding type to specify exactly which beans we're interested in:"
msgstr "假設我們希望宣告我們有些 Web Bean 屬於交易性的 Web Bean。我們首先需要的就是一個 攔截器綁定標記(interceptor binding annotation)來明確指定我們要專注的 Web Bean 是哪個:"
#. Tag: programlisting
@@ -163,7 +163,7 @@ msgstr "實做攔截器"
#. Tag: para
#, fuzzy, no-c-format
-msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
+msgid "That's great, but somewhere along the line we're going to have to actually implement the interceptor that provides this transaction management aspect. All we need to do is create a standard interceptor, and annotate it @Interceptor and @Transactional."
msgstr "我們必須在某個階段實際地實做提供此交易管理功能的攔截器。我們只需要建立一個標準的 EJB 攔截器並將它標記為 @Interceptor 和 @Transactional。"
#. Tag: programlisting
@@ -225,16 +225,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -265,17 +265,17 @@ msgstr "比方說,我們能夠指定我們的安全性攔截器能比我們的
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <interceptors>\n"
-" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
-" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
-" </interceptors>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <interceptors>\n"
+" <class>org.mycompany.myapp.SecurityInterceptor</class>\n"
+" <class>org.mycompany.myapp.TransactionInterceptor</class>\n"
+" </interceptors>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -378,7 +378,7 @@ msgstr "通常,我們會使用不同攔截器綁定類型的組合來將多重
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Secure(rolesAllowed="admin") @Transactional\n"
+"@Secure(rolesAllowed=\"admin\") @Transactional\n"
"public class ShoppingCart { ... }"
msgstr ""
"meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
+msgid "Well, fortunately, CDI works around this missing feature of Java. We may annotate one interceptor binding type with other interceptor binding types (termed a meta-annotation). The interceptor bindings are transitive — any bean with the first interceptor binding inherits the interceptor bindings declared as meta-annotations."
msgstr "幸運的是,Web Bean 有方法來解決 Java 所缺少的這項功能上的問題。我們可利用其它攔截器綁定類型來標記某個攔截器綁定類型。攔截器綁定為可轉變的 任何含有第一個攔截器綁定的 Web Bean 都會繼承宣告為 meta-annotation 的攔截器綁定。"
#. Tag: programlisting
@@ -533,7 +533,7 @@ msgstr "攔截器無法在進行建置時輕易地被停用,以及"
#. Tag: para
#, fuzzy, 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."
+msgid "the interceptor ordering is non-global — it is determined by the order in which interceptors are listed at the class level."
msgstr "攔截器的順序會是非全域性的 會由攔截器被列於 class 層級的順序來取決。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-TW/intro.po b/docs/reference/src/main/docbook/zh-TW/intro.po
index 70c992bf256..40ea03765f3 100644
--- a/docs/reference/src/main/docbook/zh-TW/intro.po
+++ b/docs/reference/src/main/docbook/zh-TW/intro.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: intro\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-21 12:44+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -24,7 +24,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
+msgid "So you're keen to get started writing your first bean? Or perhaps you're skeptical, wondering what kinds of hoops the CDI specification will make you jump through! The good news is that you've probably already written and used hundreds, perhaps thousands of beans. CDI just makes it easier to actually use them to build an application!"
msgstr "您是否已準備好開始編寫您的第一個 Web Bean 了呢?或是您針對於 Web Bean 本身的規格還是存有著一些疑問呢?不過好消息就是您從以前到現在可能早就已經編寫並使用了上百甚至是上千個 Web Bean 了。您可能根本已經不記得您所編寫的第一個 Web Bean 為何了。"
#. Tag: title
@@ -39,27 +39,27 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Prior to Java EE 6, there was no clear definition of the term "bean" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications "beans" for years. There were even a couple of different kinds of things called "beans" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a "bean". What we've been missing is a common definition."
+msgid "Prior to Java EE 6, there was no clear definition of the term \"bean\" in the Java EE platform. Of course, we've been calling Java classes used in web and enterprise applications \"beans\" for years. There were even a couple of different kinds of things called \"beans\" in EE specifications, including EJB beans and JSF managed beans. Meanwhile, other third-party frameworks such as Spring and Seam introduced their own ideas of what it meant to be a \"bean\". What we've been missing is a common definition."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
+msgid "Java EE 6 finally lays down that common definition in the Managed Beans specification. Managed Beans are defined as container-managed objects with minimal programming restrictions, otherwise known by the acronym POJO (Plain Old Java Object). They support a small set of basic services, such as resource injection, lifecycle callbacks and interceptors. Companion specifications, such as EJB and CDI, build on this basic model. But, at last, there's a uniform concept of a bean and a lightweight component model that's aligned across the Java EE platform."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
+msgid "With very few exceptions, almost every concrete Java class that has a constructor with no parameters (or a constructor designated with the annotation @Inject) is a bean. This includes every JavaBean and every EJB session bean. If you've already got some JavaBeans or session beans lying around, they're already beans—you won't need any additional special metadata. There's just little one thing you need to do before you can start injecting them into stuff: you need to put them in an archive (a jar, or a Java EE module such as a war or EJB jar) that contains a special marker file: META-INF/beans.xml."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
+msgid "The JavaBeans and EJBs you've been writing every day, up until now, have not been able to take advantage of the new services defined by the CDI specification. But you'll be able to use every one of them with CDI—allowing the container to create and destroy instances of your beans and associate them with a designated context, injecting them into other beans, using them in EL expressions, specializing them with qualifier annotations, even adding interceptors and decorators to them—without modifying your existing code. At most, you'll need to add some annotations."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now let's see how to create your first bean that actually uses CDI."
+msgid "Now let's see how to create your first bean that actually uses CDI."
msgstr ""
#. Tag: title
@@ -69,14 +69,14 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
+msgid "Suppose that we have two existing Java classes that we've been using for years in various applications. The first class parses a string into a list of sentences:"
msgstr "假設我們目前有兩個使用於各種應用程式中多年的 Java class。第一個 class 會將一個字串剖析入一列句子中:"
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
"public class SentenceParser {\n"
-" public List<String> parse(String text) { ... }\n"
+" public List<String> parse(String text) { ... }\n"
"}"
msgstr ""
"TextTranslator 並沒有一個無
#. Tag: para
#, fuzzy, no-c-format
-msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
+msgid "As you've guessed, the @Inject annotation has something to do with dependency injection! @Inject may be applied to a constructor or method of a bean, and tells the container to call that constructor or method when instantiating the bean. The container will inject other beans into the parameters of the constructor or method."
msgstr "就如您所猜測地,@Initializer 這個標記和依賴注入有關係!@Initializer 可套用至一個 Web Bean 的 constructor 或是 method 來指示 Web Bean 管理員在例示 Web Bean 時去調用該 constructor 或 method。Web Bean 管理員會將其它 Web Bean 注入至該 constructor 或 method 的參數中。"
#. Tag: para
@@ -184,7 +184,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
+msgid "Let's create a UI controller bean that uses field injection to obtain an instance of the TextTranslator, translating the text entered by a user:"
msgstr ""
#. Tag: programlisting
@@ -223,7 +223,7 @@ msgstr "Translator 為本地介面:"
#. Tag: para
#, no-c-format
-msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
+msgid "Notice the controller bean is request-scoped and named. Since this combination is so common in web applications, there's a built-in annotation for it in CDI that we could have used as a shorthand. When the (stereotype) annotation @Model is declared on a class, it creates a request-scoped and named bean."
msgstr ""
#. Tag: para
@@ -234,7 +234,7 @@ msgstr "我們能夠藉由將注入一個 TextTranslator 的
#. Tag: programlisting
#, fuzzy, no-c-format
msgid ""
-"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
+"@Inject Instance<TextTranslator> textTranslatorInstance;\n"
"...\n"
"public void translate() {\n"
" textTranslatorInstance.get().translate(inputText);\n"
@@ -247,17 +247,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
+msgid "Notice that it isn't necessary to create a getter or setter method to inject one bean into another. CDI can access an injected field directly (even if it's private!), which sometimes helps eliminate some wasteful code. The name of the field is arbitrary. It's the field's type that determines what is injected."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
+msgid "At system initialization time, the container must validate that exactly one bean exists which satisfies each injection point. In our example, if no implementation of Translator is available—if the SentenceTranslator EJB was not deployed—the container would inform us of an unsatisfied dependency. If more than one implementation of Translator were available, the container would inform us of the ambiguous dependency."
msgstr "當系統初始化時,Web Bean 管理員必須驗證是否有正好一個滿足所有注入點的 Web Bean 存在。在我們的範例中,若沒有可用的 Translator 實做 若 SentenceTranslator EJB 沒有被建置 Web Bean 管理員便會回傳一個 UnsatisfiedDependencyException。若有超過一個可使用的 Translator 實做,那麼 Web Bean 管理員便會回傳一個 AmbiguousDependencyException。"
#. Tag: para
#, no-c-format
-msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
+msgid "Before we get too deep in the details, let's pause and examine a bean's anatomy. What aspects of the bean are significant, and what gives it its identity? Instead of just giving examples of beans, we're going to define what makes something a bean."
msgstr ""
#~ msgid "Getting started with Web Beans"
diff --git a/docs/reference/src/main/docbook/zh-TW/next.po b/docs/reference/src/main/docbook/zh-TW/next.po
index 172713a0fa8..05d7ebe38cb 100644
--- a/docs/reference/src/main/docbook/zh-TW/next.po
+++ b/docs/reference/src/main/docbook/zh-TW/next.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: next\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-08 10:54+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -24,12 +24,12 @@ msgstr "接下來的步驟"
#. Tag: para
#, no-c-format
-msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
+msgid "Because CDI is so new, there's not yet a lot of information available online. That will change over time. Regardless, the CDI specification remains the authority for information on CDI. The spec is less than 100 pages and is quite readable (don't worry, it's not like your Blu-ray player manual). Of course, it covers many details we've skipped over here. The spec is available on the JSR-299 page at the JCP website."
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
+msgid "The CDI reference implementation, Weld, is being developed at the Seam project. The RI development team and the CDI spec lead blog at in.relation.to. This guide was originally based on a series of blog entries published there while the specification was being developed. It's probably the best source of information about the future of CDI, Weld and Seam."
msgstr "Web Beans Reference 的實做開發於 http://seamframework.org/WebBeans。RI 開發團隊以及 Web Beans spec lead 的 blog 位於 http://in.relation.to。本文件大體上基於發佈於該網頁上的一系列 blog 項目。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-TW/part1.po b/docs/reference/src/main/docbook/zh-TW/part1.po
index a22bf6c612f..4854640374f 100644
--- a/docs/reference/src/main/docbook/zh-TW/part1.po
+++ b/docs/reference/src/main/docbook/zh-TW/part1.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: part1\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-15 12:16+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -129,7 +129,7 @@ msgstr "我是否需要明確地將它毀掉呢?"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Where should I keep the reference to it when I'm not currently using it?"
+msgid "Where should I keep the reference to it when I'm not currently using it?"
msgstr "當我沒有在直接使用它時,我應該將它的參照保留在哪裡呢?"
#. Tag: para
@@ -144,7 +144,7 @@ msgstr "我該如何在其它物件之間共享這個物件?"
#. Tag: para
#, no-c-format
-msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
+msgid "CDI is more than a framework. It's a whole, rich programming model. The theme of CDI is loose-coupling with strong typing. Let's study what that phrase means."
msgstr ""
#. Tag: para
@@ -174,12 +174,12 @@ msgstr "decorators(裝飾器)可將商業問題分為
#. Tag: para
#, fuzzy, no-c-format
-msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
+msgid "What's even more powerful (and comforting) is that CDI provides all these facilities in a typesafe way. CDI never relies on string-based identifiers to determine how collaborating objects fit together. Instead, CDI uses the typing information that is already available in the Java object model, augmented using a new programming pattern, called qualifier annotations, to wire together beans, their dependencies, their interceptors and decorators, and their event consumers. Usage of XML descriptors is minimized to truly deployment-specific information."
msgstr "最重要的是,Web Bean 以一種 typesafe 的方式來提供了所有的這些功能。Web Bean 從不使用基於字串的識別符號(identifier)來斷定共同協作的物件如何相輔相成。雖然 XML 也是選項之一不過卻很少被使用到。取而代之,Web Bean 使用了 Java 物件模型中可使用的 typing 資訊並統合了一個稱為 binding annotations(綁定標記)的新格式,它可將 Web Bean、它們的相依性、它們的攔截器和裝飾器以及它們的事件用戶聯繫在一起。"
#. Tag: para
#, no-c-format
-msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
+msgid "But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide those kinds of things for yourself."
msgstr ""
#. Tag: para
@@ -189,7 +189,7 @@ msgstr "Web Bean 甚至提供了必要的整合點來讓未來 Java EE 規格或
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
+msgid "CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG)."
msgstr "Web Bean 受到了幾個現有的 Java framework(包括 Seam、Guice 以及 Spring)的影響。不過,Web Bean 擁有它自己獨特的特性:比 Seam 還要完善的 typesafe、比 Spring 更 stateful 而沒有那麼地以 XML 為中心,並且針對於網站和企業級的應用程式上的處理能力比 Guice 完善。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-TW/part3.po b/docs/reference/src/main/docbook/zh-TW/part3.po
index efb21dcb505..1f635e5bc8d 100644
--- a/docs/reference/src/main/docbook/zh-TW/part3.po
+++ b/docs/reference/src/main/docbook/zh-TW/part3.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: part3\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-14 16:07+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -19,7 +19,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
+msgid "The first major theme of CDI is loose coupling. We've already seen three means of achieving loose coupling:"
msgstr ""
#. Tag: para
@@ -74,7 +74,7 @@ msgstr "Web Bean 的第二個重點就是 strong typing(強類型)
#. Tag: para
#, fuzzy, no-c-format
-msgid "You don't see string-based identifiers in CDI 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!"
+msgid "You don't see string-based identifiers in CDI 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 的程式碼中不會看見基於字串的識別符號,這不是因為 framework 透過使用預設的規則來將它隱藏起來 又稱為「configuration by convention」 而是因為一開始根本就沒有任何字串!"
#. Tag: para
@@ -144,7 +144,7 @@ msgstr "Web Bean stereotype 將這個概念帶領到了另
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
+msgid "We're now ready to meet some more advanced features of CDI. Bear in mind that these features exist to make our code both easier to validate and more understandable. Most of the time you don't ever really need to use these features, but if you use them wisely, you'll come to appreciate their power."
msgstr "我們現在已準備好談到一些更為進階的 Web Bean 功能。請記得,這些功能是為了使我們的程式碼變得易於驗證和較容易理解。實際上大部分的時候您都不會真的需要使用到這些功能,不過若您可有效地利用這些功能的話,您將可體會到這些功能的強大。"
#~ msgid "Even Web Beans XML metadata is strongly typed! There's no compiler for XML, so Web Beans takes advantage of XML schemas to validate the Java types and attributes that appear in XML. This approach turns out to make the XML more literate, just like annotations made our Java code more literate."
diff --git a/docs/reference/src/main/docbook/zh-TW/part4.po b/docs/reference/src/main/docbook/zh-TW/part4.po
index 42ced91bbf7..492728390bc 100644
--- a/docs/reference/src/main/docbook/zh-TW/part4.po
+++ b/docs/reference/src/main/docbook/zh-TW/part4.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: part4\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-14 16:59+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -19,7 +19,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
+msgid "The third theme of CDI is integration. We've already seen how CDI helps integrate EJB and JSF, allowing EJBs to be bound directly to JSF pages. That's just the beginning. The CDI services are integrated into the very core of the Java EE platform. Even EJB session beans can take advantage of the dependency injection, event bus, and contextual lifecycle management that CDI provides."
msgstr ""
#. Tag: para
@@ -29,7 +29,7 @@ msgstr "我們已經看到了 Web Bean 如何協助整合 EJB 與 JSF,它讓 E
#. Tag: para
#, fuzzy, no-c-format
-msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
+msgid "We're about to see how to take full advantage of the Java EE platform in an application that uses CDI. We'll also briefly meet a set of SPIs that are provided to support portable extensions to CDI. You might not ever need to use these SPIs directly, but don't take them for granted. You will likely be using them indirectly, every time you use a third-party extension, such as Seam."
msgstr "我們正要探討如何在一個使用 Web Bean 的應用程式中有效地利用 Java EE 平台。我們也將簡短地探討一組提供來讓 Web Bean 支援 portable extension 的 SPI。您可能永遠也不會需要直接使用到這些 SPI,不過知道它們的存在以備不時之需總是較好的。最重要的是,每當您使用第三方的 extension 時,您便會間接地利用到它們。"
#~ msgid "The third theme of Web Beans is integration. Web Beans was designed to work in concert with other technologies, helping the application developer fit the other technologies together. Web Beans is an open technology. It forms a part of the Java EE ecosystem, and is itself the foundation for a new ecosystem of portable extensions and integration with existing frameworks and technologies."
diff --git a/docs/reference/src/main/docbook/zh-TW/part5.po b/docs/reference/src/main/docbook/zh-TW/part5.po
index d2ca9ea9520..fb4cb943033 100644
--- a/docs/reference/src/main/docbook/zh-TW/part5.po
+++ b/docs/reference/src/main/docbook/zh-TW/part5.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Web_Beans:_Java_Contexts_and_Dependency_Injection VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-03-28 17:09+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -16,7 +16,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and Glassfish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
+msgid "Weld is the reference implementation of JSR-299, and is used by JBoss AS and GlassFish to provide CDI services for Java Enterprise Edition (Java EE) applications. Weld also goes beyond the environments and APIs defined by the JSR-299 specification by providing support for a number of other environments (such as a servlet container such as Tomcat, or Java SE)."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-TW/producermethods.po b/docs/reference/src/main/docbook/zh-TW/producermethods.po
index 89675fdf2fe..a0acf33d6d7 100644
--- a/docs/reference/src/main/docbook/zh-TW/producermethods.po
+++ b/docs/reference/src/main/docbook/zh-TW/producermethods.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: producermethods\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-16 12:31+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -24,7 +24,7 @@ msgstr "Producer method"
#. Tag: para
#, fuzzy, no-c-format
-msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
+msgid "Producer methods let us overcome certain limitations that arise when a container, instead of the application, is responsible for instantiating objects. They're also the easiest way to integrate objects which are not beans into the CDI environment."
msgstr "Producer method 讓我們在當 Web Bean 管理員(而不是應用程式)負責舉例說明(instantiating)物件時能夠解決一些特定發生的問題。它們同時也是將非 Web Bean 物件整合入 Web Bean 環境中最簡單的方式。(我們將在 中提及第二個方式。)"
#. Tag: para
@@ -79,7 +79,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
+msgid "In particular, producer methods let us use runtime polymorphism with CDI. As we've seen, alternative beans are one solution to the problem of deployment-time polymorphism. But once the system is deployed, the CDI implementation is fixed. A producer method has no such limitation:"
msgstr ""
#. Tag: programlisting
@@ -161,7 +161,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
+msgid "Now, when the producer method is called, the returned PaymentStrategy will be bound to the session context. The producer method won't be called again in the same session."
msgstr "現在,當 producer method 被調用時,回傳的 PaymentStrategy 將會被綁定至 session context。Producer method 將不會在相同的 session 中再次被調用。"
#. Tag: para
@@ -176,12 +176,12 @@ msgstr "注入 producer method"
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
+msgid "There's one potential problem with the code above. The implementations of CreditCardPaymentStrategy are instantiated using the Java new operator. Objects instantiated directly by the application can't take advantage of dependency injection and don't have interceptors."
msgstr "上述程式碼有個潛在的問題。CreditCardPaymentStrategy 的實做是透過使用 Java 的 new operator 來例示(instantiate)的。被應用程式直接例示的物件無法有效利用依賴注入(dependency injection)並且沒有攔截器。"
#. Tag: para
#, fuzzy, no-c-format
-msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
+msgid "If this isn't what we want, we can use dependency injection into the producer method to obtain bean instances:"
msgstr "若這不是我們所想要的,我們可使用依賴注入至 producer method 之中來取得 Web Bean 的 instance:"
#. Tag: programlisting
@@ -213,12 +213,12 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of "promoting" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left "hanging" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
+msgid "Wait, what if CreditCardPaymentStrategy is a request-scoped bean? Then the producer method has the effect of \"promoting\" the current request scoped instance into session scope. This is almost certainly a bug! The request scoped object will be destroyed by the container before the session ends, but the reference to the object will be left \"hanging\" in the session scope. This error will not be detected by the container, so please take extra care when returning bean instances from producer methods!"
msgstr "請稍等,若 CreditCardPaymentStrategy 是個請求 scope 的 Web Bean 的話要怎麼辦?若是如此那麼 producer method 便有將現有的 request scope 的 instance「推入」session scope 中的效應。這幾乎能被確定是個 bug!request scope 物件會在 session 結束前被 Web Bean 管理員毀掉,不過該物件的參照會被「保留」在 session scope 中。這項錯誤將不會被 Web Bean 管理員偵測到,所以當由 producer method 回傳 Web Bean 的 instance 時請格外小心!"
#. Tag: para
#, fuzzy, no-c-format
-msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
+msgid "There's at least three ways we could go about fixing this bug. We could change the scope of the CreditCardPaymentStrategy implementation, but this would affect other clients of that bean. A better option would be to change the scope of the producer method to @Dependent or @RequestScoped."
msgstr "我們有三種可修正這項錯誤的方法。我們可更改 CreditCardPaymentStrategy 實做的 scope,不過這將會影響該 Web Bean 的其它客戶端。較好的方式就是將 producer method 的 scope 更改為 @Dependent 或 @RequestScoped。"
#. Tag: para
@@ -265,7 +265,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
+msgid "Then a new dependent instance of CreditCardPaymentStrategy will be created, passed to the producer method, returned by the producer method and finally bound to the session context. The dependent object won't be destroyed until the Preferences object is destroyed, at the end of the session."
msgstr "接著有個新的 CreditCardPaymentStrategy 的 dependent instance 將會被建立、傳送至 producer method、被 producer method 回傳然後最後被綁定至 session context。在 Preferences 物件於 session 結束時被毀掉之前,dependent 物件不會被毀掉。"
#. Tag: title
diff --git a/docs/reference/src/main/docbook/zh-TW/resources.po b/docs/reference/src/main/docbook/zh-TW/resources.po
index ff33e009af3..30822676ec1 100644
--- a/docs/reference/src/main/docbook/zh-TW/resources.po
+++ b/docs/reference/src/main/docbook/zh-TW/resources.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:17\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -26,7 +26,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a nonportable "mapped name"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
+msgid "Naturally, there is now a slight mismatch with the new style of dependency injection in CDI. Most notably, component environment injection relies on string-based names to qualify ambiguous types, and there is no real consistency as to the nature of the names (sometimes a JNDI name, sometimes a persistence unit name, sometimes an EJB link, sometimes a non-portable \"mapped name\"). Producer fields turned out to be an elegant adaptor to reduce all this complexity to a common model and get component environment resources to participate in the CDI system just like any other kind of bean."
msgstr ""
#. Tag: para
@@ -72,35 +72,35 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @WebServiceRef(lookup="java:app/service/Catalog")\n"
+"@Produces @WebServiceRef(lookup=\"java:app/service/Catalog\")\n"
"Catalog catalog;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @Resource(lookup="java:global/env/jdbc/CustomerDatasource") \n"
+"@Produces @Resource(lookup=\"java:global/env/jdbc/CustomerDatasource\") \n"
"@CustomerDatabase Datasource customerDatabase;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceContext(unitName="CustomerDatabase")\n"
+"@Produces @PersistenceContext(unitName=\"CustomerDatabase\")\n"
"@CustomerDatabase EntityManager customerDatabasePersistenceContext;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @PersistenceUnit(unitName="CustomerDatabase") \n"
+"@Produces @PersistenceUnit(unitName=\"CustomerDatabase\") \n"
"@CustomerDatabase EntityManagerFactory customerDatabasePersistenceUnit;"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"@Produces @EJB(ejbLink="../their.jar#PaymentService") \n"
+"@Produces @EJB(ejbLink=\"../their.jar#PaymentService\") \n"
"PaymentService paymentService;"
msgstr ""
@@ -126,7 +126,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
+msgid "It might feel strange to be declaring resources in Java code. Isn't this stuff that might be deployment-specific? Certainly, and that's why it makes sense to declare your resources in a class annotated @Alternative."
msgstr ""
#. Tag: title
@@ -171,7 +171,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
+msgid "It might seem like a pain to have to write these extra producer field declarations, just to gain an additional level of indirection. You could just as well use component environment injection directly, right? But remember that you're going to be using resources like the EntityManager in several different beans. Isn't it nicer and more typesafe to write"
msgstr ""
#. Tag: programlisting
@@ -186,7 +186,7 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
-msgid "@PersistenceContext(unitName="CustomerDatabase") EntityManager"
+msgid "@PersistenceContext(unitName=\"CustomerDatabase\") EntityManager"
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-TW/ri-spi.po b/docs/reference/src/main/docbook/zh-TW/ri-spi.po
index 07f898c244d..ce7d648efd8 100644
--- a/docs/reference/src/main/docbook/zh-TW/ri-spi.po
+++ b/docs/reference/src/main/docbook/zh-TW/ri-spi.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: ri-spi\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-20 11:43+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -34,7 +34,7 @@ msgstr "資源載入"
#. Tag: para
#, no-c-format
-msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the "Weld: Servlets" extension will be sufficient, and will work in any container supporting the Servlet API."
+msgid "If you just want to use managed beans, and not take advantage of enterprise services (EE resource injection, CDI injection into EE component classes, transactional events, support for CDI services in EJBs) and non-flat deployments, then the generic servlet support provided by the \"Weld: Servlets\" extension will be sufficient, and will work in any container supporting the Servlet API."
msgstr ""
#. Tag: para
@@ -59,7 +59,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
+msgid "Weld supports multiple environments. An environment is defined by an implementation of the Environment interface. A number of standard environments are built in, and described by the Environments enumeration. Different environments require different services to be present (for example a Servlet container doesn't require transaction, EJB or JPA services). By default an EE environment is assumed, but you can adjust the environment by calling bootstrap.setEnvironment()."
msgstr ""
#. Tag: para
@@ -79,7 +79,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
+msgid "The CDI specification discusses Bean Deployment Archives (BDAs)—archives which are marked as containing beans which should be deployed to the CDI container, and made available for injection and resolution. Weld reuses this description of Bean Deployment Archives in its deployment structure SPI. Each deployment exposes the BDAs which it contains; each BDA may also reference other which it can access. Together, the transitive closure of this graph forms the beans which are deployed in the application."
msgstr ""
#. Tag: para
@@ -99,7 +99,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
+msgid "In a strict container, each BDA might have to explicitly specify which other BDAs it can access. However many containers will allow an easy mechanism to make BDAs bi-directionally accessible (such as a library directory). In this case, it is allowable (and reasonable) to describe all such archives as a single, 'virtual' BeanDeploymentArchive."
msgstr ""
#. Tag: para
@@ -109,12 +109,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
+msgid "BeanDeploymentArchive provides three methods which allow it's contents to be discovered by Weld—BeanDeploymentArchive.getBeanClasses() must return all the classes in the BDA, BeanDeploymentArchive.getBeansXml() must return a data structure representing the beans.xml deployment descriptor for the archive, and BeanDeploymentArchive.getEjbs() must provide an EJB descriptor for every EJB in the BDA, or an empty list if it is not an EJB archive."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
+msgid "To aid container integrator, Weld provides a built-in beans.xml parser. To parse a beans.xml into the data-structure required by BeanDeploymentArchive, the container should call Bootstrap.parseBeansXml(URL). Weld can also parse multiple beans.xml files, merging them to become a single data-structure. This can be achieved by calling Bootstrap.parseBeansXml(Iterable<URL>)."
msgstr ""
#. Tag: para
@@ -129,7 +129,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
+msgid "In practice, you can regard the deployment structure represented by Deployment, and the virtual BDA graph as a mirror of the classloader structure for a deployment. If a class can from BDA X can be loaded by another in BDA Y, it is accessible, and therefore BDA Y's accessible BDAs should include BDA X."
msgstr ""
#. Tag: para
@@ -159,7 +159,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
+msgid "Weld delegates EJB 3 bean discovery to the container so that it doesn't duplicate the work done by the EJB container, and respects any vendor-extensions to the EJB definition."
msgstr ""
#. Tag: para
@@ -199,7 +199,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
+msgid "If you use a non-EE environment then you may implement any of the EE service SPIs, and Weld will provide the associated functionality. There is no need to implement those services you don't need!"
msgstr ""
#. Tag: title
@@ -214,7 +214,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
+msgid "EJBServices is used to resolve local EJBs used to back session beans, and must always be provided in an EE environment. EJBServices.resolveEjb(EjbDescriptor ejbDescriptor) returns a wrapper—SessionObjectReference—around the EJB reference. This wrapper allows Weld to request a reference that implements the given business interface, and, in the case of SFSBs, both request the removal of the EJB from the container and query whether the EJB has been previously removed."
msgstr ""
#. Tag: para
@@ -279,7 +279,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); intercepter will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
+msgid "InjectionServices provides a very simple contract, the InjectionServices.aroundInject(InjectionContext ic); interceptor will be called for every instance that CDI injects, whether it is a contextual instance, or a non-contextual instance injected by InjectionTarget.inject()."
msgstr ""
#. Tag: para
@@ -354,7 +354,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
+msgid "Weld expects the Application Server or other container to provide the storage for each application's context. The org.jboss.weld.context.api.BeanStore should be implemented to provide an application scoped storage."
msgstr ""
#. Tag: title
@@ -369,7 +369,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programtically, or built in). Bean validation will validate all beans."
+msgid "The bootstrap is split into phases, container initialization, bean deployment, bean validation and shutdown. Initialization will create a manager, and add the built-in contexts, and examine the deployment structure. Bean deployment will deploy any beans (defined using annotations, programmatically, or built in). Bean validation will validate all beans."
msgstr ""
#. Tag: para
@@ -429,7 +429,7 @@ msgstr "Classloader 隔離"
#. Tag: para
#, fuzzy, no-c-format
-msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuation, classloader isolation for each CDI application."
+msgid "If you are integrating Weld into an environment that supports deployment of multiple applications, you must enable, automatically, or through user configuration, classloader isolation for each CDI application."
msgstr "若您要將 Web Bean RI 整合入某個支援多重應用程式建置的環境中,您就必須為各個 Web Bean 應用程式透過自動的方式,或是透過用戶配置來啟用 classloader 隔離。"
#. Tag: term
@@ -444,7 +444,7 @@ msgstr "若您要將 Web Bean 整合入一個 Servlet 環境中,您就必須
#. Tag: para
#, no-c-format
-msgid "You must ensure that that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
+msgid "You must ensure that WeldListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called)."
msgstr ""
#. Tag: term
@@ -585,7 +585,7 @@ msgid ""
"InjectionTarget it = weldBeanManager.fireProcessInjectionTarget(clazz);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
+"CreationalContext<?> cc = beanManager.createCreationalContext(null);\n"
"\n"
"// Produce the instance, performing any constructor injection required\n"
"Object instance = it.produce();\n"
@@ -619,16 +619,16 @@ msgstr ""
msgid ""
"// Obtain the EjbDescriptor for the EJB\n"
"// You may choose to use this utility method to get the descriptor\n"
-"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
+"EjbDescriptor<?> ejbDescriptor = beanManager.getEjbDescriptor(ejbName);\n"
"\n"
"// Get an the Bean object\n"
-"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
+"Bean<?> bean = beanManager.getBean(ejbDescriptor);\n"
"\n"
"// Create the injection target\n"
"InjectionTarget it = deploymentBeanManager.createInjectionTarget(ejbDescriptor);\n"
"\n"
"// Per instance required, create the creational context\n"
-"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
+"CreationalContext<?> cc = deploymentBeanManager.createCreationalContext(bean);\n"
"\n"
"// Perform injection and call initializers\n"
"it.inject(instance, cc);\n"
diff --git a/docs/reference/src/main/docbook/zh-TW/scopescontexts.po b/docs/reference/src/main/docbook/zh-TW/scopescontexts.po
index 253668dd318..c7a71062126 100644
--- a/docs/reference/src/main/docbook/zh-TW/scopescontexts.po
+++ b/docs/reference/src/main/docbook/zh-TW/scopescontexts.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: scopescontexts\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-20 16:49+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -24,7 +24,7 @@ msgstr "Scope 與 context"
#. Tag: para
#, fuzzy, no-c-format
-msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
+msgid "So far, we've seen a few examples of scope type annotations. The scope of a bean determines the lifecycle of instances of the bean. The scope also determines which clients refer to which instances of the bean. According to the CDI specification, a scope determines:"
msgstr "到目前為止,我們已見過了一些 scope 類型標記(scope type annotations)的範例了。Web Bean 的 scope 可決定 Web Bean instance 的生命週期(lifecycle)。Scope 也能決定哪個客戶端參照哪個 Web Bean 的 instance。根據 Web Bean 規格,scope 可決定:"
#. Tag: para
@@ -49,7 +49,7 @@ msgstr "比方說若我們有個 session scope 的 Web Bean CurrentUser
#. Tag: para
#, no-c-format
-msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
+msgid "JPA entities aren't a great fit for this model. Entities have their whole own lifecycle and identity model which just doesn't map naturally to the model used in CDI. Therefore, we recommend against treating entities as CDI beans. You're certainly going to run into problems if you try to give an entity a scope other than the default scope @Dependent. The client proxy will get in the way if you try to pass an injected instance to the JPA EntityManager."
msgstr ""
#. Tag: title
@@ -59,7 +59,7 @@ msgstr "Scope type"
#. Tag: para
#, fuzzy, no-c-format
-msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
+msgid "CDI features an extensible context model. It's possible to define new scopes by creating a new scope type annotation:"
msgstr "Web Bean 含有著一個 extensible context model(可延伸的 context 模型)。您可藉由建立新的 scope 類型標記來定義新的 scope:"
#. Tag: programlisting
@@ -77,7 +77,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
+msgid "Of course, that's the easy part of the job. For this scope type to be useful, we will also need to define a Context object that implements the scope! Implementing a Context is usually a very technical task, intended for framework development only. You can expect an implementation of the business scope, for instance, in a future version of Seam."
msgstr "當然,那是這項工作中最簡單的部份。若要此 scope 類型能被有效使用,我們還需要定義一個能夠實做該 scope 的 Context 物件!實做一個 Context 通常是一項非常技術性的工作,這只應使用於架構開發(framework development)上。"
#. Tag: para
@@ -96,7 +96,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Usually, you'll use one of CDI's built-in scopes."
+msgid "Usually, you'll use one of CDI's built-in scopes."
msgstr "您通常會使用到其中一個 Web Bean 的內建 scope。"
#. Tag: title
@@ -196,7 +196,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
+msgid "Three of the four built-in scopes should be extremely familiar to every Java EE developer, so let's not waste time discussing them here. One of the scopes, however, is new."
msgstr "四個內建 scope 中有其中的三個對於所有 Java EE 開發人員來說應該都不陌生,所以我們將不花時間在此討論它們。不過在這之中有個 scope 則是新的。"
#. Tag: title
@@ -221,7 +221,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
+msgid "A conversation represents a task—a unit of work from the point of view of the user. The conversation context holds state associated with what the user is currently working on. If the user is doing multiple things at the same time, there are multiple conversations."
msgstr "Conversation(對話)代表一項工作,從用戶角度來看是項工作的單位。conversation 的 context 持有和用戶目前工作相關的狀態。若用戶同時間一次進行多項工作的話,那就會有多個 conversation。"
#. Tag: para
@@ -344,25 +344,25 @@ msgstr "因此,下列連結會傳播 conversation:"
#. Tag: programlisting
#, fuzzy, no-c-format
-msgid "<a href="/addProduct.jsp?cid=#{conversation.id}">Add Product</a>"
+msgid "<a href=\"/addProduct.jsp?cid=#{conversation.id}\">Add Product</a>"
msgstr "Add Product]]>"
#. Tag: para
#, no-c-format
-msgid "It's probably better to use one of the link components in JSF 2:"
+msgid "It's probably better to use one of the link components in JSF 2:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:link outcome="/addProduct.xhtml" value="Add Product">\n"
-" <f:param name="cid" value="#{javax.enterprise.context.conversation.id}"/>\n"
-"</h:link>"
+"<h:link outcome=\"/addProduct.xhtml\" value=\"Add Product\">\n"
+" <f:param name=\"cid\" value=\"#{javax.enterprise.context.conversation.id}\"/>\n"
+"</h:link>"
msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a "flash" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
+msgid "The conversation context propagates across redirects, making it very easy to implement the common POST-then-redirect pattern, without resort to fragile constructs such as a \"flash\" object. The container automatically adds the conversation id to the redirect URL as a request parameter."
msgstr "Web Bean 管理員也必須將 conversation 在任何重定向作業之間進行傳播,儘管該 conversation 沒有被標記為 long-running。這使得實做一般的 POST-then-redirect 模式變得非常簡單,這樣便無須使用一些像是「flash」物件的脆弱 construct。在此情況下,Web Bean 管理員會自動地新增一個請求參數至重定向 URL。"
#. Tag: title
@@ -372,7 +372,7 @@ msgstr "Conversation timeout(逾時)"
#. Tag: para
#, fuzzy, no-c-format
-msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
+msgid "The container is permitted to destroy a conversation and all state held in its context at any time in order to conserve resources. A CDI implementation will normally do this on the basis of some kind of timeout—though this is not required by the specification. The timeout is the period of inactivity before the conversation is destroyed (as opposed to the amount of time the conversation is active)."
msgstr "Web Bean 管理員能夠隨時隨地刪除它 context 中的 conversation 以及所有狀態以保留資源。一個 Web Bean 管理員實做一般會利用某種形式的 timeout 來這麼作 儘管這在 Web Bean 規格中是非必要的。Timeout 代表 conversation 在被刪除之前所經過的休止狀態時間。"
#. Tag: para
@@ -402,12 +402,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "You can guess what "singleton" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
+msgid "You can guess what \"singleton\" means here. It means a bean that is instantiated once. Unfortunately, there's a little problem with this pseudo-scope. Beans with scope @Singleton don't have a proxy object. Clients hold a direct reference to the singleton instance. So we need to consider the case of a client that can be serialized, for example, any bean with scope @SessionScoped or @ConversationScoped, any dependent object of a bean with scope @SessionScoped or @ConversationScoped, or any stateful session bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
+msgid "Now, if the singleton instance is a simple, immutable, serializable object like a string, a number or a date, we probably don't mind too much if it gets duplicated via serialization. However, that makes it no stop being a true singleton, and we may as well have just declared it with the default scope."
msgstr ""
#. Tag: para
@@ -427,7 +427,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
+msgid "give the client a reference of type Instance<X> where X is the bean type of the singleton bean."
msgstr ""
#. Tag: para
@@ -467,12 +467,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
+msgid "If you need to access a bean directly by EL name in a JSF page, you probably need to give it a scope other than @Dependent. Otherwise, any value that gets set to the bean by a JSF input will be lost immediately. That's why CDI features the @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke. If you need to access a bean that really has to have the scope @Dependent from a JSF page, inject it into a different bean, and expose it to EL via a getter method."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
+msgid "Beans with scope @Dependent don't need a proxy object. The client holds a direct reference to its instance."
msgstr ""
#. Tag: para
@@ -541,7 +541,7 @@ msgstr "calculator 這個欄位中注入了一個 Ca
#. Tag: para
#, fuzzy, no-c-format
-msgid "This feature is particularly useful with producer methods, as we'll see in the next chapter."
+msgid "This feature is particularly useful with producer methods, as we'll see in ."
msgstr "這項功能對於 producer method 來講特別有幫助,我們將在下個章節中討論到。"
#~ msgid "@RequestScoped"
diff --git a/docs/reference/src/main/docbook/zh-TW/specialization.po b/docs/reference/src/main/docbook/zh-TW/specialization.po
index e7419a93f43..61357026274 100644
--- a/docs/reference/src/main/docbook/zh-TW/specialization.po
+++ b/docs/reference/src/main/docbook/zh-TW/specialization.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: specialization\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-20 11:42+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -24,7 +24,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
+msgid "When you first start developing with CDI, you'll likely be dealing only with a single bean implementation for each bean type. In this case, it's easy to understand how beans get selected for injection. As the complexity of your application grows, multiple occurrences of the same bean type start appearing, either because you have multiple implementations or two beans share a common (Java) inheritance. That's when you have to begin studying the specialization, inheritance and alternative rules to work through unsatisfied or ambiguous dependencies or to avoid certain beans from being called."
msgstr ""
#. Tag: para
@@ -44,12 +44,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
+msgid "The second case is the default assumed by CDI. It's possible to have two beans in the system with the same part bean type (interface or parent class). As you've learned, you select between the two implementations using qualifiers."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
+msgid "The first case is the exception, and also requires more care. In any given deployment, only one bean can fulfill a given role at a time. That means one bean needs to be enabled and the other disabled. There are a two modifiers involved: @Alternative and @Specializes. We'll start by looking at alternatives and then show the guarantees that specialization adds."
msgstr ""
#. Tag: title
@@ -78,7 +78,7 @@ msgstr ""
#. Tag: para
#, fuzzy, no-c-format
-msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
+msgid "But in our staging environment, we don't really want to submit payments to the external system, so we override that implementation of PaymentProcessor with a different bean:"
msgstr "不過在我們的中繼環境(staging environment)中,我們利用了不同的 Web Bean 來置換了 PaymentProcessor 的實做:"
#. Tag: programlisting
@@ -118,12 +118,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
+msgid "We've already seen how we can enable this alternative by listing its class in the beans.xml descriptor."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
+msgid "But suppose we have many alternatives in the staging environment. It would be much more convenient to be able to enable them all at once. So let's make @Staging an @Alternative stereotype and annotate the staging beans with this stereotype instead. You'll see how this level of indirection pays off. First, we create the stereotype:"
msgstr ""
#. Tag: programlisting
@@ -164,16 +164,16 @@ msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<beans\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<beans\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd">\n"
-" <alternatives>\n"
-" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
-" </alternatives>\n"
-"</beans>"
+" http://java.sun.com/xml/ns/javaee/beans_1_0.xsd\">\n"
+" <alternatives>\n"
+" <stereotype>org.mycompany.myapp.Staging</stereotype>\n"
+" </alternatives>\n"
+"</beans>"
msgstr ""
#. Tag: para
@@ -198,7 +198,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
+msgid "So we haven't completely replaced the default implementation in this deployment of the system. The only way one bean can completely override a second bean at all injection points is if it implements all the bean types and declares all the qualifiers of the second bean. However, if the second bean declares a producer method or observer method, then even this is not enough to ensure that the second bean is never called! We need something extra."
msgstr ""
#. Tag: para
@@ -258,7 +258,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
+msgid "Since we're informing the container that our alternative bean is meant to stand in as a replacement for the default implementation, the alternative implementation automatically inherits all qualifiers of the default implementation. Thus, in our example, MockCreditCardPaymentProcessor inherits the qualifiers @Default and @CreditCard."
msgstr ""
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-TW/stereotypes.po b/docs/reference/src/main/docbook/zh-TW/stereotypes.po
index 13be6506f58..141e29b790c 100644
--- a/docs/reference/src/main/docbook/zh-TW/stereotypes.po
+++ b/docs/reference/src/main/docbook/zh-TW/stereotypes.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: stereotypes\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-01-13 15:44+1000\n"
"Last-Translator: Terry Chuang \n"
"Language-Team: Traditional Chinese \n"
@@ -102,7 +102,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
+msgid "Of course, we need to apply some other annotations to our stereotype or else it wouldn't be adding much value."
msgstr ""
#. Tag: title
@@ -145,7 +145,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
+msgid "Naturally, overriding a single default isn't much use. But remember, stereotypes can define more than just the default scope."
msgstr ""
#. Tag: title
@@ -265,12 +265,12 @@ msgstr "主要探討模板(Stereotypes)"
#. Tag: para
#, no-c-format
-msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
+msgid "This may blow your mind a bit, but stereotypes may declare other stereotypes, which we'll call stereotype stacking. You may want to do this if you have two distinct stereotypes which are meaningful on their own, but in other situation may be meaningful when combined."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
+msgid "Here's an example that combines the @Action and @Auditable stereotypes:"
msgstr ""
#. Tag: programlisting
@@ -297,7 +297,7 @@ msgstr "標準主要探討模板"
#. Tag: para
#, fuzzy, no-c-format
-msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
+msgid "We've already met two standard stereotypes defined by the CDI specification: @Interceptor and @Decorator."
msgstr "我們已談到了 Web Bean 規格所定義的兩個標準主要探討模板:@Interceptor 與 @Decorator。"
#. Tag: para
diff --git a/docs/reference/src/main/docbook/zh-TW/weldexamples.po b/docs/reference/src/main/docbook/zh-TW/weldexamples.po
index e4c60ece2a9..68f32b5bdde 100644
--- a/docs/reference/src/main/docbook/zh-TW/weldexamples.po
+++ b/docs/reference/src/main/docbook/zh-TW/weldexamples.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Weld_-_JSR-299_Reference_Implementation VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2010-12-14T13:35:18\n"
+"POT-Creation-Date: 2012-01-16T16:07:16\n"
"PO-Revision-Date: 2009-11-11 15:00+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,7 +21,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
+msgid "It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the simpler of the two examples, weld-numberguess."
msgstr ""
#. Tag: title
@@ -31,75 +31,75 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
+msgid "In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
+msgid "The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
+msgid "All the configuration files for this example are located in WEB-INF/, which can be found in the src/main/webapp directory of the example. First, we have the JSF 2.0 version of faces-config.xml. A standardized version of Facelets is the default view handler in JSF 2.0, so there's really nothing that we have to configure. Thus, the configuration consists of only the root element."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<faces-config version="2.0"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<faces-config version=\"2.0\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd">\n"
-"</faces-config>"
+" http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd\">\n"
+"</faces-config>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
+msgid "There's also an empty beans.xml file, which tells the container to look for beans in this application and to activate the CDI services."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, there's the familiar web.xml:"
+msgid "Finally, there's the familiar web.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<web-app version="2.5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee"\n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<web-app version=\"2.5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd\">\n"
" \n"
-" <display-name>weld-jsf-numberguess-war</display-name>\n"
-" <description>Weld JSF numberguess example (war)</description>\n"
+" <display-name>weld-jsf-numberguess-war</display-name>\n"
+" <description>Weld JSF numberguess example (war)</description>\n"
"\n"
-" <servlet>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
-" <load-on-startup>1</load-on-startup>\n"
-" </servlet>\n"
+" <servlet>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
+" <load-on-startup>1</load-on-startup>\n"
+" </servlet>\n"
"\n"
-" <servlet-mapping>\n"
-" <servlet-name>Faces Servlet</servlet-name>\n"
-" <url-pattern>*.jsf</url-pattern>\n"
-" </servlet-mapping>\n"
+" <servlet-mapping>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <url-pattern>*.jsf</url-pattern>\n"
+" </servlet-mapping>\n"
" \n"
-" <context-param>\n"
-" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
-" <param-value>.xhtml</param-value>\n"
-" </context-param>\n"
+" <context-param>\n"
+" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
+" <param-value>.xhtml</param-value>\n"
+" </context-param>\n"
"\n"
-" <session-config>\n"
-" <session-timeout>10</session-timeout>\n"
-" </session-config>\n"
+" <session-config>\n"
+" <session-timeout>10</session-timeout>\n"
+" </session-config>\n"
"\n"
-"</web-app>"
+"</web-app>"
msgstr ""
#. Tag: para
@@ -129,51 +129,51 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
+msgid "Let's take a look at the main JSF view, src/main/webapp/home.xhtml."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"\n"
-" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">\n"
-"<html xmlns="http://www.w3.org/1999/xhtml"\n"
-" xmlns:ui="http://java.sun.com/jsf/facelets"\n"
-" xmlns:h="http://java.sun.com/jsf/html"\n"
-" xmlns:f="http://java.sun.com/jsf/core">\n"
+"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
+" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n"
+"<html xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" xmlns:ui=\"http://java.sun.com/jsf/facelets\"\n"
+" xmlns:h=\"http://java.sun.com/jsf/html\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\">\n"
"\n"
-" <ui:composition template="/template.xhtml">\n"
-" <ui:define name="content">\n"
-" <h1>Guess a number...</h1>\n"
-" <h:form id="numberGuess">\n"
-" <div style="color: red">\n"
-" <h:messages id="messages" globalOnly="false"/>\n"
-" <h:outputText id="Higher" value="Higher!"\n"
-" rendered="#{game.number gt game.guess and game.guess ne 0}"/>\n"
-" <h:outputText id="Lower" value="Lower!"\n"
-" rendered="#{game.number lt game.guess and game.guess ne 0}"/>\n"
-" </div>\n"
+" <ui:composition template=\"/template.xhtml\">\n"
+" <ui:define name=\"content\">\n"
+" <h1>Guess a number...</h1>\n"
+" <h:form id=\"numberGuess\">\n"
+" <div style=\"color: red\">\n"
+" <h:messages id=\"messages\" globalOnly=\"false\"/>\n"
+" <h:outputText id=\"Higher\" value=\"Higher!\"\n"
+" rendered=\"#{game.number gt game.guess and game.guess ne 0}\"/>\n"
+" <h:outputText id=\"Lower\" value=\"Lower!\"\n"
+" rendered=\"#{game.number lt game.guess and game.guess ne 0}\"/>\n"
+" </div>\n"
" \n"
-" <div>\n"
-" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
+" <div>\n"
+" I'm thinking of a number between #{game.smallest} and #{game.biggest}.\n"
" You have #{game.remainingGuesses} guesses remaining.\n"
-" </div>\n"
+" </div>\n"
" \n"
-" <div>\n"
+" <div>\n"
" Your guess: \n"
-" <h:inputText id="inputGuess" value="#{game.guess}"\n"
-" size="3" required="true" disabled="#{game.number eq game.guess}"\n"
-" validator="#{game.validateNumberRange}"/>\n"
-" <h:commandButton id="guessButton" value="Guess" \n"
-" action="#{game.check}" disabled="#{game.number eq game.guess}"/>\n"
-" </div>\n"
-" <div>\n"
-" <h:commandButton id="restartButton" value="Reset" action="#{game.reset}" immediate="true"/>\n"
-" </div>\n"
-" </h:form>\n"
-" </ui:define>\n"
-" </ui:composition>\n"
-"</html>"
+" <h:inputText id=\"inputGuess\" value=\"#{game.guess}\"\n"
+" size=\"3\" required=\"true\" disabled=\"#{game.number eq game.guess}\"\n"
+" validator=\"#{game.validateNumberRange}\"/>\n"
+" <h:commandButton id=\"guessButton\" value=\"Guess\" \n"
+" action=\"#{game.check}\" disabled=\"#{game.number eq game.guess}\"/>\n"
+" </div>\n"
+" <div>\n"
+" <h:commandButton id=\"restartButton\" value=\"Reset\" action=\"#{game.reset}\" immediate=\"true\"/>\n"
+" </div>\n"
+" </h:form>\n"
+" </ui:define>\n"
+" </ui:composition>\n"
+"</html>"
msgstr ""
#. Tag: para
@@ -183,7 +183,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "There are a number of messages which can be sent to the user, "Higher!", "Lower!" and "Correct!""
+msgid "There are a number of messages which can be sent to the user, \"Higher!\", \"Lower!\" and \"Correct!\""
msgstr ""
#. Tag: para
@@ -198,7 +198,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
+msgid "A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number."
msgstr ""
#. Tag: para
@@ -266,7 +266,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Generator is application scoped, so we don't get a different random each time."
+msgid "The Generator is application scoped, so we don't get a different random each time."
msgstr ""
#. Tag: para
@@ -276,12 +276,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
+msgid "The final bean in the application is the session-scoped Game class. This is the primary entry point of the application. It's responsible for setting up or resetting the game, capturing and validating the user's guess and providing feedback to the user with a FacesMessage. We've used the post-construct lifecycle method to initialize the game by retrieving a random number from the @Random Instance<Integer> bean."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
+msgid "You'll notice that we've also added the @Named annotation to this class. This annotation is only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game})."
msgstr ""
#. Tag: programlisting
@@ -298,19 +298,19 @@ msgid ""
" private int remainingGuesses;\n"
"\n"
" @Inject @MaxNumber private int maxNumber;\n"
-" @Inject @Random Instance<Integer> randomNumber;\n"
+" @Inject @Random Instance<Integer> randomNumber;\n"
" \n"
" public Game() {}\n"
" \n"
" public void check() {\n"
-" if (guess > number) {\n"
+" if (guess > number) {\n"
" biggest = guess - 1;\n"
" }\n"
-" else if (guess < number) {\n"
+" else if (guess < number) {\n"
" smallest = guess + 1;\n"
" }\n"
" else if (guess == number) {\n"
-" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage("Correct!"));\n"
+" FacesContext.getCurrentInstance().addMessage(null, new FacesMessage(\"Correct!\"));\n"
" }\n"
" remainingGuesses--;\n"
" }\n"
@@ -325,18 +325,18 @@ msgid ""
" }\n"
" \n"
" public void validateNumberRange(FacesContext context, UIComponent toValidate, Object value) {\n"
-" if (remainingGuesses <= 0) {\n"
-" FacesMessage message = new FacesMessage("No guesses left!");\n"
+" if (remainingGuesses <= 0) {\n"
+" FacesMessage message = new FacesMessage(\"No guesses left!\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" ((UIInput) toValidate).setValid(false);\n"
" return;\n"
" }\n"
" int input = (Integer) value;\n"
"\n"
-" if (input < smallest || input > biggest) {\n"
+" if (input < smallest || input > biggest) {\n"
" ((UIInput) toValidate).setValid(false);\n"
"\n"
-" FacesMessage message = new FacesMessage("Invalid guess");\n"
+" FacesMessage message = new FacesMessage(\"Invalid guess\");\n"
" context.addMessage(toValidate.getClientId(context), message);\n"
" }\n"
" }\n"
@@ -385,20 +385,20 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
+msgid "Second, we need to explicitly specify the servlet listener in web.xml, again because the container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with requests."
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<listener>\n"
-" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
-"</listener>"
+"<listener>\n"
+" <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>\n"
+"</listener>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
+msgid "When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified interface name. You generally don't need to access this interface, but Weld makes use of it."
msgstr ""
#. Tag: title
@@ -418,17 +418,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin ."
+msgid "To use the Weld SE numberguess example in Eclipse, you can open the example natively using the m2eclipse plugin."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects . Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
+msgid "If you have m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Maven Projects. Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the existence of a Maven project."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "This will create a project in your workspace called weld-se-numberguess ."
+msgid "This will create a project in your workspace called weld-se-numberguess."
msgstr ""
#. Tag: para
@@ -438,7 +438,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "It's time to get the example running!"
+msgid "It's time to get the example running!"
msgstr ""
#. Tag: title
@@ -448,12 +448,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
+msgid "Disable m2eclipse's Workspace Resolution, to make sure that Eclipse can find StartMain. Right click on the project, and choose Properties -> Maven, and uncheck Resolve dependencies from Workspace projects:"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Right click on the project, and choose Run As -> Run As Application:"
+msgid "Right click on the project, and choose Run As -> Run As Application:"
msgstr ""
#. Tag: para
@@ -503,7 +503,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Let's have a look at the significant code and configuration files that make up this example."
+msgid "Let's have a look at the significant code and configuration files that make up this example."
msgstr ""
#. Tag: para
@@ -513,7 +513,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
+msgid "The game's main logic is located in Game.java. Here is the code for that class, highlighting the ways in which this differs from the web application version:"
msgstr ""
#. Tag: programlisting
@@ -558,7 +558,7 @@ msgid ""
"\n"
" public boolean isGameLost()\n"
" {\n"
-" return guess != number && remainingGuesses <= 0;\n"
+" return guess != number && remainingGuesses <= 0;\n"
" }\n"
"\n"
" public boolean check()\n"
@@ -567,12 +567,12 @@ msgid ""
"\n"
" if (checkNewNumberRangeIsValid())\n"
" {\n"
-" if (guess > number)\n"
+" if (guess > number)\n"
" {\n"
" biggest = guess - 1;\n"
" }\n"
"\n"
-" if (guess < number)\n"
+" if (guess < number)\n"
" {\n"
" smallest = guess + 1;\n"
" }\n"
@@ -590,7 +590,7 @@ msgid ""
"\n"
" private boolean checkNewNumberRangeIsValid()\n"
" {\n"
-" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
+" return validNumberRange = ((guess >= smallest) && (guess <= biggest));\n"
" }\n"
"\n"
" @PostConstruct\n"
@@ -607,12 +607,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
+msgid "The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
+msgid "Notice that the bean is not named, since it doesn't need to be accessed via EL."
msgstr ""
#. Tag: para
@@ -642,12 +642,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
+msgid "The reset() method makes a call to the injected rndGenerator in order to get the random number at the start of each game. Note that it can't use Instance.get() like the JSF example does because there will not be any active contexts like there are during a JSF request."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
+msgid "The MessageGenerator class depends on the current instance of Game and queries its state in order to determine the appropriate messages to provide as the prompt for the user's next guess and the response to the previous guess. The code for MessageGenerator is as follows:"
msgstr ""
#. Tag: programlisting
@@ -660,11 +660,11 @@ msgid ""
"\n"
" public String getChallengeMessage()\n"
" {\n"
-" StringBuilder challengeMsg = new StringBuilder("I'm thinking of a number between ");\n"
+" StringBuilder challengeMsg = new StringBuilder(\"I'm thinking of a number between \");\n"
" challengeMsg.append(game.getSmallest());\n"
-" challengeMsg.append(" and ");\n"
+" challengeMsg.append(\" and \");\n"
" challengeMsg.append(game.getBiggest());\n"
-" challengeMsg.append(". Can you guess what it is?");\n"
+" challengeMsg.append(\". Can you guess what it is?\");\n"
"\n"
" return challengeMsg.toString();\n"
" }\n"
@@ -673,34 +673,34 @@ msgid ""
" {\n"
" if (game.isGameWon())\n"
" {\n"
-" return "You guessed it! The number was " + game.getNumber();\n"
+" return \"You guessed it! The number was \" + game.getNumber();\n"
" }\n"
" else if (game.isGameLost())\n"
" {\n"
-" return "You are fail! The number was " + game.getNumber();\n"
+" return \"You are fail! The number was \" + game.getNumber();\n"
" }\n"
" else if (!game.isValidNumberRange())\n"
" {\n"
-" return "Invalid number range!";\n"
+" return \"Invalid number range!\";\n"
" }\n"
" else if (game.getRemainingGuesses() == Game.MAX_NUM_GUESSES)\n"
" {\n"
-" return "What is your first guess?";\n"
+" return \"What is your first guess?\";\n"
" }\n"
" else\n"
" {\n"
" String direction = null;\n"
"\n"
-" if (game.getGuess() < game.getNumber())\n"
+" if (game.getGuess() < game.getNumber())\n"
" {\n"
-" direction = "Higher";\n"
+" direction = \"Higher\";\n"
" }\n"
" else\n"
" {\n"
-" direction = "Lower";\n"
+" direction = \"Lower\";\n"
" }\n"
"\n"
-" return direction + "! You have " + game.getRemainingGuesses() + " guesses left.";\n"
+" return direction + \"! You have \" + game.getRemainingGuesses() + \" guesses left.\";\n"
" }\n"
" }\n"
"}"
@@ -713,7 +713,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
+msgid "The Game's state is interrogated to determine the appropriate challenge message ..."
msgstr ""
#. Tag: para
@@ -783,7 +783,7 @@ msgid ""
" private void refreshUI() {\n"
" mainLabel.setText( msgGenerator.getChallengeMessage() );\n"
" messageLabel.setText( msgGenerator.getResultMessage() );\n"
-" guessText.setText( "" );\n"
+" guessText.setText( \"\" );\n"
" guessesLeftBar.setValue( game.getRemainingGuesses() );\n"
" guessText.requestFocus();\n"
" }\n"
@@ -818,7 +818,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
+msgid "guessButtonActionPerformed is called when the 'Guess' button is clicked, and it does the following:"
msgstr ""
#. Tag: para
@@ -828,7 +828,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Calls game.check() to validate and perform one 'turn' of the game"
+msgid "Calls game.check() to validate and perform one 'turn' of the game"
msgstr ""
#. Tag: para
@@ -853,7 +853,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
+msgid "The translator example is built as an ear and contains EJBs. As a result, it's structure is more complex than the numberguess example."
msgstr ""
#. Tag: para
@@ -863,25 +863,25 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
+msgid "First, let's take a look at the ear aggregator, which is located in the example's ear directory. Maven automatically generates the application.xml for us from this plugin configuration:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<plugin>\n"
-" <groupId>org.apache.maven.plugins</groupId>\n"
-" <artifactId>maven-ear-plugin</artifactId>\n"
-" <configuration>\n"
-" <modules>\n"
-" <webModule>\n"
-" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
-" <artifactId>weld-jsf-translator-war</artifactId>\n"
-" <contextRoot>/weld-translator</contextRoot>\n"
-" </webModule>\n"
-" </modules>\n"
-" </configuration>\n"
-"</plugin>"
+"<plugin>\n"
+" <groupId>org.apache.maven.plugins</groupId>\n"
+" <artifactId>maven-ear-plugin</artifactId>\n"
+" <configuration>\n"
+" <modules>\n"
+" <webModule>\n"
+" <groupId>org.jboss.weld.examples.jsf.translator</groupId>\n"
+" <artifactId>weld-jsf-translator-war</artifactId>\n"
+" <contextRoot>/weld-translator</contextRoot>\n"
+" </webModule>\n"
+" </modules>\n"
+" </configuration>\n"
+"</plugin>"
msgstr ""
#. Tag: para
@@ -891,72 +891,72 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
+msgid "If you weren't using Maven to generate these files, you would need META-INF/application.xml:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<application version="5"\n"
-" xmlns="http://java.sun.com/xml/ns/javaee" \n"
-" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"\n"
-" xsi:schemaLocation="\n"
+"<application version=\"5\"\n"
+" xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
" http://java.sun.com/xml/ns/javaee\n"
-" http://java.sun.com/xml/ns/javaee/application_5.xsd">\n"
+" http://java.sun.com/xml/ns/javaee/application_5.xsd\">\n"
"\n"
-" <display-name>weld-jsf-translator-ear</display-name>\n"
-" <description>The Weld JSF translator example (ear)</description>\n"
+" <display-name>weld-jsf-translator-ear</display-name>\n"
+" <description>The Weld JSF translator example (ear)</description>\n"
" \n"
-" <module>\n"
-" <web>\n"
-" <web-uri>weld-translator.war</web-uri>\n"
-" <context-root>/weld-translator</context-root>\n"
-" </web>\n"
-" </module>\n"
-" <module>\n"
-" <ejb>weld-translator.jar</ejb>\n"
-" </module>\n"
-"</application>"
+" <module>\n"
+" <web>\n"
+" <web-uri>weld-translator.war</web-uri>\n"
+" <context-root>/weld-translator</context-root>\n"
+" </web>\n"
+" </module>\n"
+" <module>\n"
+" <ejb>weld-translator.jar</ejb>\n"
+" </module>\n"
+"</application>"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
+msgid "Next, lets look at the war, which is located in the example's war directory. Just as in the numberguess example, we have a faces-config.xml for JSF 2.0 and a web.xml (to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (ommitted here for brevity):"
+msgid "More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (omitted here for brevity):"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid ""
-"<h:form id="translator">\n"
+"<h:form id=\"translator\">\n"
"\n"
-" <table>\n"
-" <tr align="center" style="font-weight: bold">\n"
-" <td>\n"
+" <table>\n"
+" <tr align=\"center\" style=\"font-weight: bold\">\n"
+" <td>\n"
" Your text\n"
-" </td>\n"
-" <td>\n"
+" </td>\n"
+" <td>\n"
" Translation\n"
-" </td>\n"
-" </tr>\n"
-" <tr>\n"
-" <td>\n"
-" <h:inputTextarea id="text" value="#{translator.text}" required="true" rows="5" cols="80"/>\n"
-" </td>\n"
-" <td>\n"
-" <h:outputText value="#{translator.translatedText}"/>\n"
-" </td>\n"
-" </tr>\n"
-" </table>\n"
-" <div>\n"
-" <h:commandButton id="button" value="Translate" action="#{translator.translate}"/>\n"
-" </div>\n"
+" </td>\n"
+" </tr>\n"
+" <tr>\n"
+" <td>\n"
+" <h:inputTextarea id=\"text\" value=\"#{translator.text}\" required=\"true\" rows=\"5\" cols=\"80\"/>\n"
+" </td>\n"
+" <td>\n"
+" <h:outputText value=\"#{translator.translatedText}\"/>\n"
+" </td>\n"
+" </tr>\n"
+" </table>\n"
+" <div>\n"
+" <h:commandButton id=\"button\" value=\"Translate\" action=\"#{translator.translate}\"/>\n"
+" </div>\n"
" \n"
-"</h:form>"
+"</h:form>"
msgstr ""
#. Tag: para
@@ -966,12 +966,12 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
+msgid "Finally, let's look at the EJB module, which is located in the example's ejb directory. In src/main/resources/META-INF there is just an empty beans.xml, used to mark the archive as containing beans."
msgstr ""
#. Tag: para
#, no-c-format
-msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
+msgid "We've saved the most interesting bit to last, the code! The project has two simple beans, SentenceParser and TextTranslator and two session beans, TranslatorControllerBean and SentenceTranslator. You should be getting quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here."
msgstr ""
#. Tag: para
@@ -995,7 +995,7 @@ msgid ""
" public String translate(String text) { \n"
" StringBuilder sb = new StringBuilder(); \n"
" for (String sentence: sentenceParser.parse(text)) { \n"
-" sb.append(translator.translate(sentence)).append(". "); \n"
+" sb.append(translator.translate(sentence)).append(\". \"); \n"
" } \n"
" return sb.toString().trim(); \n"
" }\n"
@@ -1005,7 +1005,7 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
+msgid "TextTranslator uses the simple bean (really just a plain Java class!) SentenceParser to parse the sentence and then calls on the stateless bean with the local business interface Translator to perform the translation. That's where the magic happens. Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand Latin!"
msgstr ""
#. Tag: programlisting
@@ -1015,7 +1015,7 @@ msgid ""
"public class SentenceTranslator implements Translator { \n"
"\n"
" public String translate(String sentence) { \n"
-" return "Lorem ipsum dolor sit amet"; \n"
+" return \"Lorem ipsum dolor sit amet\"; \n"
" }\n"
"\n"
"}"
@@ -1031,7 +1031,7 @@ msgstr ""
msgid ""
"@Stateful\n"
"@RequestScoped\n"
-"@Named("translator")\n"
+"@Named(\"translator\")\n"
"public class TranslatorControllerBean implements TranslatorController {\n"
"\n"
" @Inject private TextTranslator translator;\n"
diff --git a/docs/reference/src/main/scripts/zanata_draft_build b/docs/reference/src/main/scripts/zanata_draft_build
index 52d8480cdba..9ad06f94cd6 100755
--- a/docs/reference/src/main/scripts/zanata_draft_build
+++ b/docs/reference/src/main/scripts/zanata_draft_build
@@ -11,13 +11,13 @@ mkdir -p $draft_dir
echo "Pulling latest translations from Zanata server"
# write PO files to a different directory under target
-mvn zanata:publican-pull -e -Dzanata.dstDir=$draft_dir
+mvn zanata:pull -e -Dzanata.transDir=$draft_dir -B
# draft build the translated documents
# (alternative: run Ant from weld/build/dist)
# copy en-US source to draft dir for use by jDocBook
-cp -a src/main/docbook/en-US $draft_dir/en-US
+cp -a src/main/docbook/en-US $draft_dir/
echo "Building translated documentation with jDocBook"
diff --git a/docs/reference/src/main/scripts/zanata_export_translations b/docs/reference/src/main/scripts/zanata_export_translations
index 3576b40c323..86548b36318 100755
--- a/docs/reference/src/main/scripts/zanata_export_translations
+++ b/docs/reference/src/main/scripts/zanata_export_translations
@@ -5,6 +5,6 @@ set -eu
# pull latest translations into po files
echo "Pulling latest translations from Zanata server"
-mvn zanata:publican-pull -e
+mvn zanata:pull -e
echo "Finished! Don't forget to check src/main/docbook into version control to record the updated PO files"
diff --git a/docs/reference/src/main/scripts/zanata_import_source b/docs/reference/src/main/scripts/zanata_import_source
index c1511a86a87..5ee08f8b213 100755
--- a/docs/reference/src/main/scripts/zanata_import_source
+++ b/docs/reference/src/main/scripts/zanata_import_source
@@ -9,7 +9,7 @@ echo "Updating POT files"
# push updated pot files to zanata for translation
echo "Pushing updated POT files to Zanata for translation"
-mvn zanata:publican-push -e -B
+mvn zanata:push -e -B
# optional: push pot files back to VCS (probably best avoided for nightly jobs)
echo "Finished! You may want to check src/main/docbook into version control to track the updated POT files"
diff --git a/docs/reference/zanata.xml b/docs/reference/zanata.xml
index efee0937239..350b54534fb 100644
--- a/docs/reference/zanata.xml
+++ b/docs/reference/zanata.xml
@@ -3,6 +3,7 @@
https://translate.jboss.org/weld-ref-guide1.1.0
+ podirdees
diff --git a/docs/xslt/pom.xml b/docs/xslt/pom.xml
index 0a5707de257..4c45f50777c 100644
--- a/docs/xslt/pom.xml
+++ b/docs/xslt/pom.xml
@@ -6,7 +6,6 @@
org.jboss.weldweld-docbook-xsltjar
- 1.1.3-SNAPSHOTWeld DocBook XSLT
@@ -18,15 +17,15 @@
org.jboss.weldweld-core-parent
- 1.1.3-SNAPSHOT
+ 1.2.0-SNAPSHOT../../pom.xml
- scm:git:git://github.com/weld/core.git
- scm:git:git://github.com/weld/core.git
- scm:git:git://github.com/weld/core.git
+ scm:git:git@github.com:weld/core.git
+ scm:git:git@github.com:weld/core.git
+ scm:git:git@github.com:weld/core.git
@@ -38,12 +37,4 @@
-
-
- repository.jboss.org
- JBoss Repository
- http://repository.jboss.org/maven2
-
-
-
diff --git a/environments/osgi/build/pom.xml b/environments/osgi/build/pom.xml
new file mode 100644
index 00000000000..621589b2a39
--- /dev/null
+++ b/environments/osgi/build/pom.xml
@@ -0,0 +1,26 @@
+
+
+
+ weld-osgi-parent
+ org.jboss.weld.osgi
+ 1.2.0-SNAPSHOT
+ ../pom.xml
+
+ 4.0.0
+ org.jboss.weld.osgi
+ weld-osgi
+ jar
+ Weld OSGi (Build)
+
+
+
+ Apache License, Version 2.0
+ repo
+ http://www.apache.org/licenses/LICENSE-2.0.html
+
+
+ http://www.seamframework.org/Weld
+
+
diff --git a/environments/osgi/core/api/pom.xml b/environments/osgi/core/api/pom.xml
new file mode 100644
index 00000000000..599b230a4bc
--- /dev/null
+++ b/environments/osgi/core/api/pom.xml
@@ -0,0 +1,77 @@
+
+
+
+
+
+ org.jboss.weld.osgi
+ weld-osgi-core
+ 1.2.0-SNAPSHOT
+ ../pom.xml
+
+ 4.0.0
+ org.jboss.weld.osgi
+ weld-osgi-core-api
+ bundle
+ Weld OSGi (API bundle)
+ Weld OSGi API bundle
+
+
+
+ Apache License, Version 2.0
+ repo
+ http://www.apache.org/licenses/LICENSE-2.0.html
+
+
+ http://www.seamframework.org/Weld
+
+
+
+
+ org.osgi
+ org.osgi.core
+
+
+
+ javax.inject
+ javax.inject
+
+
+
+ javax.el
+ el-api
+
+
+
+ javax.enterprise
+ cdi-api
+
+
+
+
+
+
+
+ org.apache.felix
+ maven-bundle-plugin
+
+
+
+
+
\ No newline at end of file
diff --git a/environments/osgi/core/api/src/etc/header.txt b/environments/osgi/core/api/src/etc/header.txt
new file mode 100644
index 00000000000..77292be2469
--- /dev/null
+++ b/environments/osgi/core/api/src/etc/header.txt
@@ -0,0 +1,14 @@
+JBoss, Home of Professional Open Source
+Copyright 20011, Red Hat, Inc. and/or its affiliates, and individual
+contributors by the @authors tag. See the copyright.txt in the
+distribution for a full listing of individual contributors.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+http://www.apache.org/licenses/LICENSE-2.0
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/BundleState.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/BundleState.java
new file mode 100644
index 00000000000..0aa361eeead
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/BundleState.java
@@ -0,0 +1,39 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api;
+
+/**
+ *
This enumeration lists the two new states of a bean bundle.
+ *
A bean bundle is in {@link BundleState#VALID} state if all its required
+ * service dependencies are validated otherwise is in
+ * {@link BundleState#INVALID} state. Every time a bean bundle goes from one
+ * state to another a corresponding
+ * {@link org.jboss.weld.environment.osgi.api.events.Valid} or
+ * {@link org.jboss.weld.environment.osgi.api.events.Invalid} event may be
+ * fired.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see org.osgi.framework.Bundle
+ * @see org.jboss.weld.environment.osgi.api.events.Valid
+ * @see org.jboss.weld.environment.osgi.api.events.Invalid
+ */
+public enum BundleState {
+ VALID,
+ INVALID
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/Registration.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/Registration.java
new file mode 100644
index 00000000000..f5baef4b41f
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/Registration.java
@@ -0,0 +1,91 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api;
+
+import java.lang.annotation.Annotation;
+
+/**
+ *
This interface represents the registrations of an injectable service in
+ * the service registry. Its behavior is similar to {@link Service}, thus
+ * it might represent the iterable set of all the registrations of a
+ * service.
+ *
It allows to:
+ *
+ *
Wrap a list of service registration (i.e. the bindings between a
+ * service and its implementations) as an {@link Iterable} java
+ * object,
+ *
+ *
+ *
Select a subset of these registration filtered by
+ * {@link javax.inject.Qualifier}s or LDAP filters,
+ *
+ *
+ *
Iterate through these service registrations,
+ *
+ *
+ *
Obtain the service implementations list as a
+ * {@link Service},
+ *
+ *
+ *
Get the number of registrations (i.e the number of registered
+ * service implementations).
+ *
+ *
+ *
OSGi services should not be subtyped.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see ServiceRegistry
+ * @see Service
+ * @see RegistrationHolder
+ */
+public interface Registration extends Iterable> {
+ /**
+ * Unregister all the service implementations in this registration.
+ */
+ void unregister();
+
+ /**
+ * Get all the service implementation in this registration.
+ *
+ * @param the type of the concerned service.
+ * @return all the service implementations as a {@link Service}.
+ */
+ Service getServiceReference();
+
+ /**
+ * Get a subset of this registration with particular service implementations.
+ *
+ * @param qualifiers the {@link javax.inject.Qualifier} annotations that
+ * filter the requested implementation.
+ * @return a {@link Registration} that is a subset of this registration with
+ * the matching service implementations.
+ */
+ Registration select(Annotation... qualifiers);
+
+ /**
+ * Get a subset of this registration with particular service implementations.
+ *
+ * @param filter the LDAP filter that filters the requested implementation.
+ * @return a {@link Registration} that is a subset of this registration with
+ * the matching service implementations.
+ */
+ Registration select(String filter);
+
+ int size();
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/RegistrationHolder.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/RegistrationHolder.java
new file mode 100644
index 00000000000..cefcf09cd3a
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/RegistrationHolder.java
@@ -0,0 +1,77 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api;
+
+import org.osgi.framework.ServiceRegistration;
+
+import java.util.List;
+
+/**
+ *
This interface represents the bindings between a service and its registered
+ * implementations. It is used by {@link Registration} to maintain the list of
+ * registration bindings. It uses OSGi {@link ServiceRegistration}.
+ *
It allows to:
+ *
+ *
Wrap a list of {@link ServiceRegistration} as binding between
+ * a service and its implementations as a {@link java.util.List},
+ *
+ *
+ *
Handle this list with addition, removal, clearing and size
+ * operations.
+ *
+ *
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Registration
+ * @see ServiceRegistration
+ */
+public interface RegistrationHolder {
+ /**
+ * Get all service registration in this registration holder.
+ *
+ * @return the list of {@link ServiceRegistration} in this holder.
+ */
+ List getRegistrations();
+
+ /**
+ * Add a service registration in this registration holder.
+ *
+ * @param registration the {@link ServiceRegistration} to add to this holder.
+ */
+ void addRegistration(ServiceRegistration registration);
+
+ /**
+ * Remove a service registration from this registration holder.
+ *
+ * @param registration the {@link ServiceRegistration} to remove from this holder.
+ */
+ void removeRegistration(ServiceRegistration registration);
+
+ /**
+ * Clear this registration holder, removing all its contained {@link ServiceRegistration}s.
+ */
+ void clear();
+
+ /**
+ * Get the number of service registrations in this registration holder.
+ *
+ * @return the number of {@link ServiceRegistration} in this holder.
+ */
+ int size();
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/Service.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/Service.java
new file mode 100644
index 00000000000..f86b4136b4a
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/Service.java
@@ -0,0 +1,112 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api;
+
+import java.lang.annotation.Annotation;
+
+/**
+ *
It represents a service instance producer parametrized by the service to
+ * inject. It has the same behavior than CDI
+ * {@link javax.enterprise.inject.Instance} except that it represents only OSGi
+ * service beans.
+ *
IT allows to:
+ *
+ *
Wrap a list of potential service implementations as an
+ * {@link Iterable} java object,
+ *
+ *
+ *
Select a subset of these service implementations filtered by
+ * {@link javax.inject.Qualifier}s or LDAP filters,
+ *
+ *
+ *
Iterate through these service implementations,
+ *
+ *
+ *
Obtain an instance of the first remaining service
+ * implementations,
+ *
+ *
+ *
Obtain utility information about the contained service
+ * implementations.
+ *
+ *
+ *
OSGi services should not be subtyped.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see javax.enterprise.inject.Instance
+ * @see javax.inject.Provider
+ * @see Iterable
+ * @see ServiceRegistry
+ * @see Registration
+ */
+public interface Service extends Iterable {
+ /**
+ * Obtain the first service instance.
+ *
+ * @return an instance of the service.
+ */
+ T get();
+
+ /**
+ * Obtain a subset of the service implementations containing the first
+ * implementation found.
+ *
+ * @return a subset of the service implementations as another {@link Service}.
+ */
+ Iterable first();
+
+ /**
+ * Obtain a subset of the service implementations that matches the given
+ * {@link javax.inject.Qualifier}
+ *
+ * @param qualifiers the filtering {@link javax.inject.Qualifier}s.
+ * @return a subset of the service implementations as another {@link Service}.
+ */
+ Service select(Annotation... qualifiers);
+
+ /**
+ * Obtain a subset of the service implementations that matches the given
+ * {@link javax.inject.Qualifier}
+ *
+ * @param filter the filtering LDAP {@link String}.
+ * @return a subset of the service implementations as another {@link Service}.
+ */
+ Service select(String filter);
+
+ /**
+ * Test if there is no available implementation.
+ *
+ * @return true if there is no implementation, false otherwise.
+ */
+ boolean isUnsatisfied();
+
+ /**
+ * Test if there are multiple implementations.
+ *
+ * @return true if there are multiple implementations, false otherwise.
+ */
+ boolean isAmbiguous();
+
+ /**
+ * Obtain the number of available implementations
+ *
+ * @return the number of available implementations.
+ */
+ int size();
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/ServiceRegistry.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/ServiceRegistry.java
new file mode 100644
index 00000000000..c9ca10c7a46
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/ServiceRegistry.java
@@ -0,0 +1,75 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api;
+
+/**
+ *
This interface represents a service registry where all OSGi services may be
+ * handled.
+ *
It allows to:
+ *
+ *
Register a service implementation with a service, getting back the
+ * corresponding {@link Registration},
+ *
+ *
+ *
Obtain the service implementations list as a
+ * {@link Service}.
+ *
+ *
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Service
+ * @see Registration
+ */
+public interface ServiceRegistry {
+ /**
+ * Register a service implementation.
+ *
+ * @param contract the service contract interface.
+ * @param implementation the service implementation class.
+ * @param the service type.
+ * @return the new service {@link Registration} or null if the registration
+ * goes wrong.
+ */
+ Registration registerService(Class contract,
+ Class extends T> implementation);
+
+ /**
+ * Register a service implementation.
+ *
+ * @param contract the service contract interface.
+ * @param implementation the service implementation class.
+ * @param the service type.
+ * @param the service implementation type.
+ * @return the new service {@link Registration} or null if the registration
+ * goes wrong.
+ */
+ Registration registerService(Class contract,
+ U implementation);
+
+ /**
+ * Get available service implementations of a service.
+ *
+ * @param contract the service contract interface that implementations are
+ * requested.
+ * @param the service type.
+ * @return the available service implementations as a {@link Service} or null
+ * if there is no such implementation.
+ */
+ Service getServiceReferences(Class contract);
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/BundleDataFile.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/BundleDataFile.java
new file mode 100644
index 00000000000..e3383173f14
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/BundleDataFile.java
@@ -0,0 +1,65 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.annotation;
+
+import javax.enterprise.util.Nonbinding;
+import javax.inject.Qualifier;
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.RetentionPolicy;
+import java.lang.annotation.Target;
+
+import static java.lang.annotation.ElementType.FIELD;
+import static java.lang.annotation.ElementType.METHOD;
+import static java.lang.annotation.ElementType.PARAMETER;
+
+/**
+ *
This annotation qualifies an injection point that represents a bundle data
+ * file.
+ *
It allows to specify the relative path of the file in the bundle, as a
+ * required value.
+ *
The file path is not actually qualifying the
+ * injection point, thus this annotation is for global bundle data file injection
+ * point with additional data. To discriminate the bundle use
+ * {@link OSGiBundle} or {@link BundleName} and
+ * {@link BundleVersion} annotations.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Qualifier
+ * @see org.osgi.framework.Bundle
+ * @see OSGiBundle
+ * @see BundleName
+ * @see BundleVersion
+ */
+@Target(
+ {
+ METHOD, PARAMETER, FIELD
+ })
+@Retention(RetentionPolicy.RUNTIME)
+@Documented
+@Qualifier
+public @interface BundleDataFile {
+ /**
+ * The data file that should be injected. Nondiscriminatory value for the
+ * typesafe resolution algorithm.
+ *
+ * @return the relative path of the data file in the current bundle.
+ */
+ @Nonbinding String value();
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/BundleHeader.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/BundleHeader.java
new file mode 100644
index 00000000000..acb5039b839
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/BundleHeader.java
@@ -0,0 +1,67 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.annotation;
+
+import javax.enterprise.util.Nonbinding;
+import javax.inject.Qualifier;
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.RetentionPolicy;
+import java.lang.annotation.Target;
+
+import static java.lang.annotation.ElementType.FIELD;
+import static java.lang.annotation.ElementType.METHOD;
+import static java.lang.annotation.ElementType.PARAMETER;
+
+/**
+ *
This annotation qualifies an injection point that represents a specific bundle
+ * header.
+ *
It allows to specify the name of the bundle header, as a required
+ * value.
+ *
The header name is not actually qualifying
+ * the injection point, thus this annotation is for global specific bundle header
+ * injection point with additional data. To discriminate the bundle use
+ * {@link OSGiBundle} or {@link BundleName} and
+ * {@link BundleVersion} annotations. To obtain all the bundle headers see
+ * {@link BundleHeaders} annotations.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Qualifier
+ * @see org.osgi.framework.Bundle
+ * @see OSGiBundle
+ * @see BundleName
+ * @see BundleVersion
+ * @see BundleHeaders
+ */
+@Target(
+ {
+ METHOD, PARAMETER, FIELD
+ })
+@Retention(RetentionPolicy.RUNTIME)
+@Documented
+@Qualifier
+public @interface BundleHeader {
+ /**
+ * The name of the specific bundle header. Nondiscriminatory value for the
+ * typesafe resolution algorithm.
+ *
+ * @return the name of the bundle header.
+ */
+ @Nonbinding String value();
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/BundleHeaders.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/BundleHeaders.java
new file mode 100644
index 00000000000..d9847f07dd3
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/BundleHeaders.java
@@ -0,0 +1,53 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.annotation;
+
+import javax.inject.Qualifier;
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.RetentionPolicy;
+import java.lang.annotation.Target;
+
+import static java.lang.annotation.ElementType.FIELD;
+import static java.lang.annotation.ElementType.METHOD;
+import static java.lang.annotation.ElementType.PARAMETER;
+
+/**
+ *
This annotation qualifies an injection point that represents all headers of a
+ * bundle.
+ *
To discriminate the bundle use {@link OSGiBundle} or
+ * {@link BundleName} and {@link BundleVersion} annotations. To
+ * obtain a specific bundle header see {@link BundleHeader} annotation.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Qualifier
+ * @see org.osgi.framework.Bundle
+ * @see OSGiBundle
+ * @see BundleName
+ * @see BundleVersion
+ * @see BundleHeader
+ */
+@Target(
+ {
+ METHOD, PARAMETER, FIELD
+ })
+@Retention(RetentionPolicy.RUNTIME)
+@Documented
+@Qualifier
+public @interface BundleHeaders {
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/BundleName.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/BundleName.java
new file mode 100644
index 00000000000..031cac93340
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/BundleName.java
@@ -0,0 +1,63 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.annotation;
+
+import javax.enterprise.util.Nonbinding;
+import javax.inject.Qualifier;
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.RetentionPolicy;
+import java.lang.annotation.Target;
+
+import static java.lang.annotation.ElementType.FIELD;
+import static java.lang.annotation.ElementType.METHOD;
+import static java.lang.annotation.ElementType.PARAMETER;
+
+/**
+ *
This annotation qualifies an injection point that represents a bundle or a
+ * bundle relative object.
+ *
It allows to specify the symbolic name of the bundle, as a required
+ * value.
+ *
The symbolic name actually discriminate the injection point, thus this
+ * annotation is for specific bundle relative injection point. For global bundle
+ * relative injection point see {@link OSGiBundle} annotation. To discriminate
+ * the bundle version see {@link BundleVersion}.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Qualifier
+ * @see org.osgi.framework.Bundle
+ * @see OSGiBundle
+ * @see BundleVersion
+ */
+@Target(
+ {
+ METHOD, PARAMETER, FIELD
+ })
+@Retention(RetentionPolicy.RUNTIME)
+@Documented
+@Qualifier
+public @interface BundleName {
+ /**
+ * The bundle symbolic name. Discriminatory value for the typesafe resolution
+ * algorithm.
+ *
+ * @return the bundle symbolic name.
+ */
+ @Nonbinding String value();
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/BundleVersion.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/BundleVersion.java
new file mode 100644
index 00000000000..b6f48648de1
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/BundleVersion.java
@@ -0,0 +1,62 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.annotation;
+
+import javax.enterprise.util.Nonbinding;
+import javax.inject.Qualifier;
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.RetentionPolicy;
+import java.lang.annotation.Target;
+
+import static java.lang.annotation.ElementType.FIELD;
+import static java.lang.annotation.ElementType.METHOD;
+import static java.lang.annotation.ElementType.PARAMETER;
+
+/**
+ *
This annotation qualifies an injection point that represents a bundle or a
+ * bundle relative object.
+ *
It allows to specify the version of the bundle, as a required value.
+ *
The version actually discriminate the injection point, thus this annotation is
+ * for specific bundle relative injection point. For global bundle relative
+ * injection point see {@link OSGiBundle} annotation. To discriminate the
+ * bundle symbolic name see {@link BundleName}.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Qualifier
+ * @see org.osgi.framework.Bundle
+ * @see OSGiBundle
+ * @see BundleName
+ */
+@Target(
+ {
+ METHOD, PARAMETER, FIELD
+ })
+@Retention(RetentionPolicy.RUNTIME)
+@Documented
+@Qualifier
+public @interface BundleVersion {
+ /**
+ * The bundle version. Discriminatory value for the typesafe resolution
+ * algorithm.
+ *
+ * @return the bundle version.
+ */
+ @Nonbinding String value();
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Filter.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Filter.java
new file mode 100644
index 00000000000..723bdbe8812
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Filter.java
@@ -0,0 +1,62 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.annotation;
+
+import javax.inject.Qualifier;
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.RetentionPolicy;
+import java.lang.annotation.Target;
+
+import static java.lang.annotation.ElementType.FIELD;
+import static java.lang.annotation.ElementType.METHOD;
+import static java.lang.annotation.ElementType.PARAMETER;
+import static java.lang.annotation.ElementType.TYPE;
+
+/**
+ *
This annotation qualifies an injection point that represents a LDAP
+ * filtered service.
+ *
It allows to specify the LDAP filter, as a required {@link String}.
+ *
It may be coupled with a {@link OSGiService} annotation in order to
+ * filter the injected service implementations.
+ * The LDAP filtering acts on {@link Qualifier} or {@link Properties}
+ * annotations or regular OSGi LDAP properties used in service publishing.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Properties
+ * @see Qualifier
+ * @see OSGiService
+ * @see org.jboss.weld.environment.osgi.api.Service
+ * @see org.jboss.weld.environment.osgi.api.ServiceRegistry
+ */
+@Target(
+ {
+ TYPE, METHOD, PARAMETER, FIELD
+ })
+@Retention(RetentionPolicy.RUNTIME)
+@Documented
+@Qualifier
+public @interface Filter {
+ /**
+ * The LDAP filter.
+ *
+ * @return the LDAP filter as a String.
+ */
+ String value();
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/OSGiBundle.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/OSGiBundle.java
new file mode 100644
index 00000000000..1b5b0e10700
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/OSGiBundle.java
@@ -0,0 +1,73 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.annotation;
+
+import javax.enterprise.util.Nonbinding;
+import javax.inject.Qualifier;
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.RetentionPolicy;
+import java.lang.annotation.Target;
+
+import static java.lang.annotation.ElementType.FIELD;
+import static java.lang.annotation.ElementType.METHOD;
+import static java.lang.annotation.ElementType.PARAMETER;
+
+/**
+ *
This annotation qualifies an injection point that represents a bundle or a
+ * bundle relative object.
+ *
It allows to specify:
+ *
The symbolic name of the bundle, as a required value,
+ *
The version of the bundle, as an optional value.
+ *
The symbolic name and version are not actually qualifying the
+ * injection point, thus this annotation is for global bundle injection point
+ * with additional data.
+ * In order to actually discriminate on the symbolic name or version see
+ * {@link BundleName} and {@link BundleVersion} annotations.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Qualifier
+ * @see org.osgi.framework.Bundle
+ * @see BundleName
+ * @see BundleVersion
+ */
+@Target(
+ {
+ METHOD, PARAMETER, FIELD
+ })
+@Retention(RetentionPolicy.RUNTIME)
+@Documented
+@Qualifier
+public @interface OSGiBundle {
+ /**
+ * The symbolic name of the bundle. Nondiscriminatory value for the typesafe
+ * resolution algorithm.
+ *
+ * @return the symbolic name of the bundle.
+ */
+ @Nonbinding String value();
+
+ /**
+ * The version of the bundle. Nondiscriminatory value for the typesafe
+ * resolution algorithm.
+ *
+ * @return the version of the bundle.
+ */
+ @Nonbinding String version() default "";
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/OSGiService.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/OSGiService.java
new file mode 100644
index 00000000000..9bd9c61b30f
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/OSGiService.java
@@ -0,0 +1,58 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.annotation;
+
+import javax.enterprise.util.Nonbinding;
+import javax.inject.Qualifier;
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.RetentionPolicy;
+import java.lang.annotation.Target;
+
+import static java.lang.annotation.ElementType.FIELD;
+import static java.lang.annotation.ElementType.METHOD;
+import static java.lang.annotation.ElementType.PARAMETER;
+
+/**
+ *
This annotation qualifies an injection point that represents a service from
+ * the OSGi service registry.
+ *
It may be use to obtain an injected OSGi service using
+ * {@link org.jboss.weld.environment.osgi.api.Service} interface or directly the
+ * service contract interface. The injected service might be filtered using
+ * regular {@link Qualifier} annotations or a LDAP filter with {@link Filter}
+ * annotation. It also might be mark as required for bundle running using
+ * {@link Required} annotation.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Qualifier
+ * @see Filter
+ * @see Required
+ * @see org.jboss.weld.environment.osgi.api.Service
+ * @see org.jboss.weld.environment.osgi.api.ServiceRegistry
+ */
+@Target(
+ {
+ METHOD, PARAMETER, FIELD
+ })
+@Retention(RetentionPolicy.RUNTIME)
+@Documented
+@Qualifier
+public @interface OSGiService {
+ @Nonbinding int value() default 1;
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Properties.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Properties.java
new file mode 100644
index 00000000000..ef503586365
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Properties.java
@@ -0,0 +1,58 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.annotation;
+
+import javax.inject.Qualifier;
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.RetentionPolicy;
+import java.lang.annotation.Target;
+
+import static java.lang.annotation.ElementType.TYPE;
+
+/**
+ *
This annotation qualifies a class that represents a LDAP filtered service.
+ *
It allows to specify multiple LDAP properties, as a array of {@link Property}.
+ *
It may be coupled with a {@link Publish} annotation in order to qualify
+ * the published service implementations. The LDAP filtering acts on
+ * {@link Qualifier} or {@link Properties} annotations or regular OSGi LDAP
+ * properties used in service publishing.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Filter
+ * @see Qualifier
+ * @see Property
+ * @see Publish
+ * @see org.jboss.weld.environment.osgi.api.Service
+ * @see org.jboss.weld.environment.osgi.api.ServiceRegistry
+ */
+@Target({TYPE})
+@Retention(RetentionPolicy.RUNTIME)
+@Documented
+@Qualifier
+public @interface Properties {
+ /**
+ * The properties of the annotated class as OSGi service properties (for LDAP
+ * filtering).
+ *
+ * @return the properties of the service implementation as an array of
+ * {@link Property}.
+ */
+ Property[] value() default {};
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Property.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Property.java
new file mode 100644
index 00000000000..8d8263dc0d5
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Property.java
@@ -0,0 +1,66 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.annotation;
+
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.RetentionPolicy;
+import java.lang.annotation.Target;
+
+/**
+ *
This annotation wraps an OSGi service property used for automatic OSGi service
+ * publishing.
+ *
It allows to specify:
+ *
+ *
The name of the property, as a required
+ * String,
+ *
+ *
+ *
The value of the property, as a required
+ * {@link String}.
+ *
+ *
+ *
It may be used within the {@link Publish} annotation to provide the
+ * published service implementation properties.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Publish
+ * @see org.jboss.weld.environment.osgi.api.Service
+ * @see org.jboss.weld.environment.osgi.api.ServiceRegistry
+ */
+@Target(
+ {
+ })
+@Retention(RetentionPolicy.RUNTIME)
+@Documented
+public @interface Property {
+ /**
+ * The property name.
+ *
+ * @return the property name.
+ */
+ String name();
+
+ /**
+ * The property value.
+ *
+ * @return the property value.
+ */
+ String value();
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Publish.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Publish.java
new file mode 100644
index 00000000000..5af673dba03
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Publish.java
@@ -0,0 +1,70 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.annotation;
+
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.RetentionPolicy;
+import java.lang.annotation.Target;
+
+import static java.lang.annotation.ElementType.TYPE;
+
+/**
+ *
This annotation notices that this type is an OSGi service implementation and
+ * should be automatically published in the OSGi service registry.
+ *
It allows to specify:
+ *
+ *
The contract interfaces of implemented service, as an optional
+ * array of {@link Class}es,
+ *
+ *
+ *
The properties of the published service implementation, as an
+ * optional array of {@link Property},
+ *
+ *
+ *
The published implementation might be discriminated using regular
+ * {@link javax.inject.Qualifier} annotations or a LDAP filter with {@link Filter}
+ * annotation.
+ *
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see javax.inject.Qualifier
+ * @see Filter
+ * @see Property
+ * @see org.jboss.weld.environment.osgi.api.Service
+ * @see org.jboss.weld.environment.osgi.api.ServiceRegistry
+ */
+@Target({TYPE})
+@Retention(RetentionPolicy.RUNTIME)
+@Documented
+public @interface Publish {
+ /**
+ * The contracts the annotated class fulfills.
+ *
+ * @return the contracts of the annotated implementation as an array of interfaces.
+ */
+ Class[] contracts() default {};
+
+ /**
+ * The rank of the service to find the best available service on lookups.
+ *
+ * @return the rank of the service. Default is 0.
+ */
+ int rank() default 0;
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Required.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Required.java
new file mode 100644
index 00000000000..f995721db21
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Required.java
@@ -0,0 +1,49 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.annotation;
+
+import javax.inject.Qualifier;
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.RetentionPolicy;
+import java.lang.annotation.Target;
+
+import static java.lang.annotation.ElementType.FIELD;
+import static java.lang.annotation.ElementType.METHOD;
+import static java.lang.annotation.ElementType.PARAMETER;
+
+/**
+ *
This annotation qualifies an injection point that represents a required
+ * service.
+ *
It may be coupled with the {@link OSGiService} annotation in order to
+ * qualify a service that must be available for the application to start.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Qualifier
+ * @see org.jboss.weld.environment.osgi.api.Service
+ * @see org.jboss.weld.environment.osgi.api.ServiceRegistry
+ */
+@Target(
+ {
+ METHOD, PARAMETER, FIELD
+ })
+@Retention(RetentionPolicy.RUNTIME)
+@Documented
+@Qualifier
+public @interface Required {
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Sent.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Sent.java
new file mode 100644
index 00000000000..ae2f2ba3af5
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Sent.java
@@ -0,0 +1,52 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.annotation;
+
+import javax.inject.Qualifier;
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.RetentionPolicy;
+import java.lang.annotation.Target;
+
+import static java.lang.annotation.ElementType.PARAMETER;
+
+/**
+ *
This annotation qualifies an injection point that represents an
+ * {@link org.jboss.weld.environment.osgi.api.events.InterBundleEvent} from
+ * outside the current {@link org.osgi.framework.Bundle}.
+ *
It may be used in an {@link javax.enterprise.event.Observes} method to
+ * restrict the listened
+ * {@link org.jboss.weld.environment.osgi.api.events.InterBundleEvent}.
+ * It allows to ignore the
+ * {@link org.jboss.weld.environment.osgi.api.events.InterBundleEvent}
+ * from within the current bundle.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Qualifier
+ * @see org.jboss.weld.environment.osgi.api.events.InterBundleEvent
+ * @see org.osgi.framework.Bundle
+ */
+@Target(
+ {
+ PARAMETER
+ })
+@Retention(RetentionPolicy.RUNTIME)
+@Documented
+@Qualifier
+public @interface Sent {
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Specification.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Specification.java
new file mode 100644
index 00000000000..a2aced05225
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/annotation/Specification.java
@@ -0,0 +1,58 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.annotation;
+
+import javax.inject.Qualifier;
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.RetentionPolicy;
+import java.lang.annotation.Target;
+
+import static java.lang.annotation.ElementType.PARAMETER;
+
+/**
+ *
This annotation qualifies an injection point that represents events whose
+ * match one of the specifications.
+ *
It allows to specify the specification interfaces of the
+ * {@link javax.enterprise.event.Event}s parametrizing types, as a required
+ * {@link Class}.
+ *
It may be used in an {@link javax.enterprise.event.Observes} method to
+ * restrict the listened events.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Qualifier
+ * @see javax.enterprise.event.Event
+ * @see javax.enterprise.event.Observes
+ */
+@Target(
+ {
+ PARAMETER
+ })
+@Retention(RetentionPolicy.RUNTIME)
+@Documented
+@Qualifier
+public @interface Specification {
+ /**
+ * The specification class filtering the received
+ * {@link javax.enterprise.event.Event}.
+ *
+ * @return the specification class.
+ */
+ Class value();
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/AbstractBundleContainerEvent.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/AbstractBundleContainerEvent.java
new file mode 100644
index 00000000000..1cdbb3de07b
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/AbstractBundleContainerEvent.java
@@ -0,0 +1,75 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.events;
+
+import org.osgi.framework.BundleContext;
+
+/**
+ *
This abstract class represents all the Weld-OSGi bundle container events as a
+ * superclass.
+ *
It allows to:
+ *
+ *
Represent all bundle container events,
+ *
+ *
+ *
Retrieve the current event type as a
+ * {@link BundleContainerEventType},
+ *
+ *
+ *
Retrieve the firing {@link BundleContext}.
+ *
+ *
+ *
It may be used in {@link javax.enterprise.event.Observes} method in order
+ * to listen all bundle container events.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see org.osgi.framework.Bundle
+ * @see BundleContext
+ * @see BundleContainerEvents
+ * @see BundleContainerEventType
+ * @see javax.enterprise.event.Observes
+ */
+public abstract class AbstractBundleContainerEvent {
+ private BundleContext bundleContext;
+
+ /**
+ * Construct a new bundle container event for the current bundle.
+ *
+ * @param context the firing bundle context (current bundle context).
+ */
+ public AbstractBundleContainerEvent(final BundleContext context) {
+ this.bundleContext = context;
+ }
+
+ /**
+ * Get the firing bundle context.
+ *
+ * @return the firing {@link org.osgi.framework.BundleContext}.
+ */
+ public BundleContext getBundleContext() {
+ return bundleContext;
+ }
+
+ /**
+ * Get the bundle container event type.
+ *
+ * @return the {@link BundleContainerEventType} of the fired bundle container event.
+ */
+ public abstract BundleContainerEventType getType();
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/AbstractBundleEvent.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/AbstractBundleEvent.java
new file mode 100644
index 00000000000..419646ba34e
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/AbstractBundleEvent.java
@@ -0,0 +1,102 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.events;
+
+import org.osgi.framework.Bundle;
+import org.osgi.framework.Version;
+
+/**
+ *
This abstract class represents all the Weld-OSGi bundle events as a
+ * superclass.
+ *
It allows to:
+ *
+ *
Represent all bundle events,
+ *
+ *
+ *
Retrieve the current event type as a
+ * {@link BundleEventType},
+ *
+ *
+ *
Retrieve the firing bundle and its information.
+ *
+ *
+ *
It may be used in {@link javax.enterprise.event.Observes} method in order
+ * to listen all bundle events.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Bundle
+ * @see BundleEvents
+ * @see BundleEventType
+ * @see javax.enterprise.event.Observes
+ */
+public abstract class AbstractBundleEvent {
+ private final Bundle bundle;
+
+ /**
+ * Construct a new bundle event for the current bundle.
+ *
+ * @param bundle the firing bundle (current bundle).
+ */
+ public AbstractBundleEvent(Bundle bundle) {
+ this.bundle = bundle;
+ }
+
+ /**
+ * Get the bundle event type.
+ *
+ * @return the {@link BundleEventType} of the fired bundle event.
+ */
+ public abstract BundleEventType getType();
+
+ /**
+ * Get the firing bundle id.
+ *
+ * @return the firing bundle id.
+ */
+ public long getBundleId() {
+ return bundle.getBundleId();
+ }
+
+ /**
+ * Get the firing bundle symbolic name.
+ *
+ * @return the firing bundle symbolic name.
+ */
+ public String getSymbolicName() {
+ return bundle.getSymbolicName();
+ }
+
+ /**
+ * Get the firing bundle version.
+ *
+ * @return the firing bundle version.
+ */
+ public Version getVersion() {
+ return bundle.getVersion();
+ }
+
+ /**
+ * Get the firing bundle.
+ *
+ * @return the firing bundle.
+ */
+ public Bundle getBundle() {
+ return bundle;
+ }
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/AbstractServiceEvent.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/AbstractServiceEvent.java
new file mode 100644
index 00000000000..abd5699aebe
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/AbstractServiceEvent.java
@@ -0,0 +1,208 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.events;
+
+import org.osgi.framework.Bundle;
+import org.osgi.framework.BundleContext;
+import org.osgi.framework.Constants;
+import org.osgi.framework.ServiceReference;
+
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Map;
+
+/**
+ *
This abstract class represents all the Weld-OSGi service events as a
+ * superclass.
+ *
It allows to:
+ *
+ *
Represent all service events,
+ *
+ *
+ *
Retrieve the current event type as a
+ * {@link ServiceEventType},
+ *
+ *
+ *
Retrieve the affected {@link ServiceReference}, the
+ * corresponding information and registering
+ * {@link Bundle},
+ *
+ *
+ *
Manipulate the service,
+ *
+ *
+ *
Retrieve the firing {@link BundleContext}.
+ *
+ *
+ *
It may be used in {@link javax.enterprise.event.Observes} method in order
+ * to listen all service events.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see Bundle
+ * @see BundleContext
+ * @see ServiceReference
+ * @see ServiceEvents
+ * @see ServiceEventType
+ * @see javax.enterprise.event.Observes
+ */
+public abstract class AbstractServiceEvent {
+ private final ServiceReference reference;
+
+ private final BundleContext context;
+
+ private List classesNames;
+
+ private List> classes;
+
+ private Map assignable = new HashMap();
+
+ /**
+ * Construct a new service event for the specified service.
+ *
+ * @param reference the {@link ServiceReference} that changes of state.
+ * @param context the service {@link BundleContext}.
+ */
+ public AbstractServiceEvent(ServiceReference reference, BundleContext context) {
+ this.reference = reference;
+ this.context = context;
+ }
+
+ /**
+ * Get the service event type.
+ *
+ * @return the {@link ServiceEventType} of the fired service event.
+ */
+ public abstract ServiceEventType eventType();
+
+ /**
+ * Get the service reference of the firing service.
+ *
+ * @return the {@link ServiceReference} of the fired service event.
+ */
+ public ServiceReference getReference() {
+ return reference;
+ }
+
+ /**
+ * Get a service instance of the firing service.
+ *
+ * @return the service instance of the firing service.
+ * @see BundleContext#getService(org.osgi.framework.ServiceReference)
+ */
+ public Object getService() {
+ return context.getService(reference);
+ }
+
+ /**
+ * Release the service instance of the firing service.
+ *
+ * @return false if the service instance is already released or if the
+ * service is unavailable, true otherwhise.
+ * @see BundleContext#ungetService(org.osgi.framework.ServiceReference)
+ */
+ public boolean ungetService() {
+ return context.ungetService(reference);
+ }
+
+ /**
+ * Get the registering bundle of the firing service.
+ *
+ * @return the registering bundle.
+ */
+ public Bundle getRegisteringBundle() {
+ return reference.getBundle();
+ }
+
+ /**
+ * Get the class names under which the firing service was registered.
+ *
+ * @return all the class names for the firing service.
+ */
+ public List getServiceClassNames() {
+ if (classesNames == null) {
+ classesNames = Arrays.asList(
+ (String[]) reference.getProperty(Constants.OBJECTCLASS));
+ }
+ return classesNames;
+ }
+
+ /**
+ * Get a service instance of the firing service with the specific type.
+ *
+ * @param type the wanted class for the service instance
+ * @param the wanted type for the service instance
+ * @return the service instance of the firing service with the given type.
+ * @see BundleContext#getService(org.osgi.framework.ServiceReference)
+ */
+ public T getService(Class type) {
+ if (isTyped(type)) {
+ return type.cast(getService());
+ } else {
+ throw new RuntimeException("the type " + type
+ + " isn't supported for the service."
+ + " Supported types are "
+ + getServiceClasses(type));
+ }
+ }
+
+ /**
+ * If the specified type is a implementation of the firing service.
+ *
+ * @param type the tested type for being a firing service implementation.
+ * @return true if the specified type is assignable for the firing service,
+ * false otherwise.
+ */
+ public boolean isTyped(Class> type) {
+ boolean typed = false;
+ if (!assignable.containsKey(type)) {
+ for (Class clazz : getServiceClasses(type)) {
+ if (type.isAssignableFrom(clazz)) {
+ typed = true;
+ break;
+ }
+ }
+ assignable.put(type, typed);
+ }
+ return assignable.get(type);
+ }
+
+ /**
+ * Get the class that are the firing service implementations.
+ *
+ * @param type the class from which the service will be loaded
+ * @return all the firing service implementation classes.
+ */
+ public List> getServiceClasses(Class> type) {
+ if (classes == null) {
+ classes = new ArrayList>();
+ for (String className : getServiceClassNames()) {
+ try {
+ classes.add(type.getClassLoader().loadClass(className));
+ } catch (ClassNotFoundException ex) {
+ ex.printStackTrace();
+ return Collections.emptyList();
+ }
+ }
+ }
+ return classes;
+ }
+
+}
\ No newline at end of file
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/BundleContainerEventType.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/BundleContainerEventType.java
new file mode 100644
index 00000000000..4ef4036c6c5
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/BundleContainerEventType.java
@@ -0,0 +1,32 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.events;
+
+/**
+ *
This enumeration list all possible states of a bundle container and the
+ * corresponding event types.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see AbstractBundleContainerEvent
+ * @see BundleContainerEvents
+ */
+public enum BundleContainerEventType {
+ INITIALIZED,
+ SHUTDOWN
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/BundleContainerEvents.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/BundleContainerEvents.java
new file mode 100644
index 00000000000..01855c87988
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/BundleContainerEvents.java
@@ -0,0 +1,88 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.events;
+
+import org.osgi.framework.BundleContext;
+
+/**
+ *
This class wraps all the bundle container events as inner static classes.
+ * There is one event class by BundleContainerEventType.
+ *
Each inner class allows to:
+ *
+ *
Represent a specific bundle container event,
+ *
+ *
+ *
Retrieve the same information as
+ * AbstractBundleContainerEvent.
+ *
+ *
+ *
They may be used in Observes method in order to listen a
+ * specific bundle container event.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see AbstractBundleContainerEvent
+ * @see org.osgi.framework.Bundle
+ * @see BundleContext
+ * @see BundleContainerEventType
+ * @see javax.enterprise.event.Observes
+ */
+public class BundleContainerEvents {
+ /**
+ * Represents the bundle events for the
+ * {@link BundleContainerEventType#INITIALIZED} state.
+ */
+ public static class BundleContainerInitialized
+ extends AbstractBundleContainerEvent {
+ /**
+ * Construct a new {@link BundleContainerInitialized} event.
+ *
+ * @param context the firing {@link BundleContext}.
+ */
+ public BundleContainerInitialized(BundleContext context) {
+ super(context);
+ }
+
+ @Override
+ public BundleContainerEventType getType() {
+ return BundleContainerEventType.INITIALIZED;
+ }
+
+ }
+
+ /**
+ * Represents the bundle events for the
+ * {@link BundleContainerEventType#SHUTDOWN} state.
+ */
+ public static class BundleContainerShutdown
+ extends AbstractBundleContainerEvent {
+ /**
+ * Construct a new {@link BundleContainerShutdown} event.
+ *
+ * @param context the firing {@link BundleContext}.
+ */
+ public BundleContainerShutdown(BundleContext context) {
+ super(context);
+ }
+
+ @Override
+ public BundleContainerEventType getType() {
+ return BundleContainerEventType.SHUTDOWN;
+ }
+
+ }
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/BundleEventType.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/BundleEventType.java
new file mode 100644
index 00000000000..55a8171869f
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/BundleEventType.java
@@ -0,0 +1,39 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.events;
+
+/**
+ *
This enumeration lists all possible states of a bundle and the
+ * corresponding event types.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see AbstractBundleEvent
+ * @see BundleEvents
+ */
+public enum BundleEventType {
+ INSTALLED,
+ LAZY_ACTIVATION,
+ RESOLVED,
+ STARTED,
+ STARTING,
+ STOPPED,
+ STOPPING,
+ UNINSTALLED,
+ UNRESOLVED,
+ UPDATED,
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/BundleEvents.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/BundleEvents.java
new file mode 100644
index 00000000000..050b96992be
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/BundleEvents.java
@@ -0,0 +1,245 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.events;
+
+import org.osgi.framework.Bundle;
+
+/**
+ *
This class wraps all the bundle events as inner static classes. There is one
+ * event class by {@link BundleEventType}.
+ *
Each inner class allows to:
+ *
+ *
Represent a specific bundle event,
+ *
+ *
+ *
Retrieve the same information as
+ * {@link AbstractBundleEvent}.
+ *
+ *
+ *
They may be used in {@link javax.enterprise.event.Observes} method in
+ * order to listen a specific bundle event.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see AbstractBundleEvent
+ * @see Bundle
+ * @see BundleEventType
+ * @see javax.enterprise.event.Observes
+ */
+public class BundleEvents {
+ /**
+ * Represents the bundle events for the {@link BundleEventType#INSTALLED} state.
+ */
+ public static class BundleInstalled extends AbstractBundleEvent {
+ /**
+ * Construct a new {@link BundleInstalled} event.
+ *
+ * @param bundle the firing {@link Bundle}.
+ */
+ public BundleInstalled(Bundle bundle) {
+ super(bundle);
+ }
+
+ @Override
+ public BundleEventType getType() {
+ return BundleEventType.INSTALLED;
+ }
+
+ }
+
+ /**
+ * Represents the bundle events for the
+ * {@link BundleEventType#LAZY_ACTIVATION} state.
+ */
+ public static class BundleLazyActivation extends AbstractBundleEvent {
+ /**
+ * Construct a new {@link BundleLazyActivation} event.
+ *
+ * @param bundle the firing {@link Bundle}.
+ */
+ public BundleLazyActivation(Bundle bundle) {
+ super(bundle);
+ }
+
+ @Override
+ public BundleEventType getType() {
+ return BundleEventType.LAZY_ACTIVATION;
+ }
+
+ }
+
+ /**
+ * Represents the bundle events for the {@link BundleEventType#RESOLVED}
+ * state.
+ */
+ public static class BundleResolved extends AbstractBundleEvent {
+ /**
+ * Construct a new {@link BundleResolved} event.
+ *
+ * @param bundle the firing {@link Bundle}.
+ */
+ public BundleResolved(Bundle bundle) {
+ super(bundle);
+ }
+
+ @Override
+ public BundleEventType getType() {
+ return BundleEventType.RESOLVED;
+ }
+
+ }
+
+ /**
+ * Represents the bundle events for the {@link BundleEventType#STARTED} state.
+ */
+ public static class BundleStarted extends AbstractBundleEvent {
+ /**
+ * Construct a new {@link BundleStarted} event.
+ *
+ * @param bundle the firing {@link Bundle}.
+ */
+ public BundleStarted(Bundle bundle) {
+ super(bundle);
+ }
+
+ @Override
+ public BundleEventType getType() {
+ return BundleEventType.STARTED;
+ }
+
+ }
+
+ /**
+ * Represents the bundle events for the {@link BundleEventType#STARTING} state.
+ */
+ public static class BundleStarting extends AbstractBundleEvent {
+ /**
+ * Construct a new {@link BundleStarting} event.
+ *
+ * @param bundle the firing {@link Bundle}.
+ */
+ public BundleStarting(Bundle bundle) {
+ super(bundle);
+ }
+
+ @Override
+ public BundleEventType getType() {
+ return BundleEventType.STARTING;
+ }
+
+ }
+
+ /**
+ * Represents the bundle events for the {@link BundleEventType#STOPPED} state.
+ */
+ public static class BundleStopped extends AbstractBundleEvent {
+ /**
+ * Construct a new {@link BundleStopped} event.
+ *
+ * @param bundle the firing {@link Bundle}.
+ */
+ public BundleStopped(Bundle bundle) {
+ super(bundle);
+ }
+
+ @Override
+ public BundleEventType getType() {
+ return BundleEventType.STOPPED;
+ }
+
+ }
+
+ /**
+ * Represents the bundle events for the {@link BundleEventType#STOPPING} state.
+ */
+ public static class BundleStopping extends AbstractBundleEvent {
+ /**
+ * Construct a new {@link BundleStopping} event.
+ *
+ * @param bundle the firing {@link Bundle}.
+ */
+ public BundleStopping(Bundle bundle) {
+ super(bundle);
+ }
+
+ @Override
+ public BundleEventType getType() {
+ return BundleEventType.STOPPING;
+ }
+
+ }
+
+ /**
+ * Represents the bundle events for the {@link BundleEventType#UNINSTALLED} state.
+ */
+ public static class BundleUninstalled extends AbstractBundleEvent {
+ /**
+ * Construct a new {@link BundleUninstalled} event.
+ *
+ * @param bundle the firing {@link Bundle}.
+ */
+ public BundleUninstalled(Bundle bundle) {
+ super(bundle);
+ }
+
+ @Override
+ public BundleEventType getType() {
+ return BundleEventType.UNINSTALLED;
+ }
+
+ }
+
+ /**
+ * Represents the bundle events for the {@link BundleEventType#UNRESOLVED} state.
+ */
+ public static class BundleUnresolved extends AbstractBundleEvent {
+ /**
+ * Construct a new {@link BundleUnresolved} event.
+ *
+ * @param bundle the firing {@link Bundle}.
+ */
+ public BundleUnresolved(Bundle bundle) {
+ super(bundle);
+ }
+
+ @Override
+ public BundleEventType getType() {
+ return BundleEventType.UNRESOLVED;
+ }
+
+ }
+
+ /**
+ * Represents the bundle events for the {@link BundleEventType#UPDATED} state.
+ */
+ public static class BundleUpdated extends AbstractBundleEvent {
+ /**
+ * Construct a new {@link BundleUpdated} event.
+ *
+ * @param bundle the firing {@link Bundle}.
+ */
+ public BundleUpdated(Bundle bundle) {
+ super(bundle);
+ }
+
+ @Override
+ public BundleEventType getType() {
+ return BundleEventType.UPDATED;
+ }
+
+ }
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/InterBundleEvent.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/InterBundleEvent.java
new file mode 100644
index 00000000000..3fc00586c28
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/InterBundleEvent.java
@@ -0,0 +1,144 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.events;
+
+import javax.inject.Provider;
+
+/**
+ *
This class represents a communication event between bean bundles.
+ *
It allows to specify:
+ *
+ *
The message as an {@link Object},
+ *
+ *
+ *
The type of the message as a {@link Class},
+ *
+ *
+ *
The origin of the message (within or outside the bundle).
+ *
+ *
+ *
It may be used in {@link javax.enterprise.event.Observes} method in order
+ * to listen inter-bundle communications.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see org.osgi.framework.Bundle
+ * @see javax.enterprise.event.Observes
+ * @see org.jboss.weld.environment.osgi.api.annotation.Sent
+ */
+public class InterBundleEvent {
+ private final Object event;
+
+ private boolean sent = false;
+
+ private Class> type;
+
+ /**
+ * Construct a new {@link InterBundleEvent} with a message.
+ *
+ * @param event the message as an {@link Object}.
+ */
+ public InterBundleEvent(Object event) {
+ this.event = event;
+ }
+
+ /**
+ * Construct a new {@link InterBundleEvent} with a typed message.
+ *
+ * @param event the message as an {@link Object}.
+ * @param type the type of the message as a {@link Class}
+ */
+ public InterBundleEvent(Object event, Class> type) {
+ this.event = event;
+ this.type = type;
+ }
+
+ /**
+ * Obtain the type of the message.
+ *
+ * @return the type of the message as a {@link Class}.
+ */
+ public Class> type() {
+ if (type != null) {
+ return type;
+ } else {
+ return event.getClass();
+ }
+ }
+
+ /**
+ * Test if the message type matches the given type.
+ *
+ * @param type the tested type as a {@link Class}
+ * @return true if the given type matches the message type, false otherwise.
+ */
+ public boolean isTyped(Class> type) {
+ if (this.type != null) {
+ return this.type.equals(type);
+ } else {
+ return type.isAssignableFrom(event.getClass());
+ }
+ }
+
+ /**
+ * Obtain a parametrized provider if the given type matches the message type.
+ *
+ * @param type the wanted provider type as a {@link Class}.
+ * @param the wanted provider type.
+ * @return a {@link Provider} for the wanted type.
+ * @throws {@link RuntimeException} if the wanted type does not match the message type.
+ */
+ public Provider typed(Class type) {
+ if (isTyped(type)) {
+ return new Provider() {
+ @Override
+ public T get() {
+ return (T) event;
+ }
+
+ };
+ } else {
+ throw new RuntimeException("The event is not of type " + type.getName());
+ }
+ }
+
+ /**
+ * Obtain the message.
+ *
+ * @return the message as an {@link Object}
+ */
+ public Object get() {
+ return event;
+ }
+
+ /**
+ * Test if the communication event comes from within or outside the current bundle.
+ *
+ * @return
+ */
+ public boolean isSent() {
+ return sent;
+ }
+
+ /**
+ * Mark the communication event as sent outside the firing bundle.
+ */
+ public void sent() {
+ this.sent = true;
+ }
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/Invalid.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/Invalid.java
new file mode 100644
index 00000000000..a1f8ba86f34
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/Invalid.java
@@ -0,0 +1,42 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.events;
+
+/**
+ *
This class represents all bean bundle invalidation event.
+ *
It allows to:
+ *
+ *
Represent all bean bundle invalidation events,
+ *
+ *
+ *
Retrieve the invalidated bean bundle and its information.
+ *
+ *
+ *
It may be used in Observes method in order to listen all bean
+ * bundle invalidation events.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see org.osgi.framework.Bundle
+ * @see org.osgi.cdi.api.extension.BundleState
+ * @see Valid
+ */
+public class Invalid {
+ // TODO : find a better name
+ // as @UnconsistantDependencies
+ // or make it as a start/stop event for container only when deps. are OK
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/ServiceEventType.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/ServiceEventType.java
new file mode 100644
index 00000000000..49568857a4b
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/ServiceEventType.java
@@ -0,0 +1,33 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.events;
+
+/**
+ *
This enumeration lists all possible states of a service and the
+ * corresponding event types.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see AbstractServiceEvent
+ * @see ServiceEvents
+ */
+public enum ServiceEventType {
+ SERVICE_ARRIVAL,
+ SERVICE_DEPARTURE,
+ SERVICE_CHANGED
+
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/ServiceEvents.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/ServiceEvents.java
new file mode 100644
index 00000000000..846d8a9462e
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/ServiceEvents.java
@@ -0,0 +1,115 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.events;
+
+import org.osgi.framework.BundleContext;
+import org.osgi.framework.ServiceReference;
+
+/**
+ *
This class wraps all the service events as inner static classes. There is one
+ * event class by {@link ServiceEventType}.
+ *
Each inner class allows to:
+ *
+ *
Represent a specific service event,
+ *
+ *
+ *
Retrieve the same information as
+ * {@link AbstractServiceEvent}.
+ *
+ *
+ *
They may be used in {@link javax.enterprise.event.Observes} method in
+ * order to listen a specific service event.
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see AbstractBundleEvent
+ * @see org.osgi.framework.Bundle
+ * @see BundleContext
+ * @see ServiceReference
+ * @see ServiceEventType
+ * @see javax.enterprise.event.Observes
+ */
+public class ServiceEvents {
+ /**
+ * Represents the service events for the
+ * {@link ServiceEventType#SERVICE_ARRIVAL} state.
+ */
+ public static class ServiceArrival extends AbstractServiceEvent {
+ /**
+ * Construct a new {@link ServiceArrival} event.
+ *
+ * @param ref the firing {@link ServiceReference}
+ * @param context the firing {@link BundleContext}
+ */
+ public ServiceArrival(
+ ServiceReference ref, BundleContext context) {
+ super(ref, context);
+ }
+
+ @Override
+ public ServiceEventType eventType() {
+ return ServiceEventType.SERVICE_ARRIVAL;
+ }
+
+ }
+
+ /**
+ * Represents the service events for the
+ * {@link ServiceEventType#SERVICE_CHANGED} state.
+ */
+ public static class ServiceChanged extends AbstractServiceEvent {
+ /**
+ * Construct a new {@link ServiceChanged} event.
+ *
+ * @param ref the firing {@link ServiceReference}
+ * @param context the firing {@link BundleContext}
+ */
+ public ServiceChanged(
+ ServiceReference ref, BundleContext context) {
+ super(ref, context);
+ }
+
+ @Override
+ public ServiceEventType eventType() {
+ return ServiceEventType.SERVICE_CHANGED;
+ }
+
+ }
+
+ /**
+ * Represents the service events for the
+ * {@link ServiceEventType#SERVICE_DEPARTURE} state.
+ */
+ public static class ServiceDeparture extends AbstractServiceEvent {
+ /**
+ * Construct a new {@link ServiceDeparture} event.
+ *
+ * @param ref the firing {@link ServiceReference}
+ * @param context the firing {@link BundleContext}
+ */
+ public ServiceDeparture(
+ ServiceReference ref, BundleContext context) {
+ super(ref, context);
+ }
+
+ @Override
+ public ServiceEventType eventType() {
+ return ServiceEventType.SERVICE_DEPARTURE;
+ }
+
+ }
+}
diff --git a/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/Valid.java b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/Valid.java
new file mode 100644
index 00000000000..d0048d52f88
--- /dev/null
+++ b/environments/osgi/core/api/src/main/java/org/jboss/weld/environment/osgi/api/events/Valid.java
@@ -0,0 +1,43 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.api.events;
+
+/**
+ *
This class represents all bean bundle validation event.
+ *
It allows to:
+ *
+ *
Represent all bean bundle validation events,
+ *
+ *
+ *
Retrieve the validated bean bundle and its information.
+ *
+ *
+ *
It may be used in Observes method in order to listen all bean
+ * bundle validation events.
+ *
+ *
+ * @author Mathieu ANCELIN - SERLI (mathieu.ancelin@serli.com)
+ * @author Matthieu CLOCHARD - SERLI (matthieu.clochard@serli.com)
+ * @see org.osgi.framework.Bundle
+ * @see org.osgi.cdi.api.extension.BundleState
+ * @see Invalid
+ */
+public class Valid {
+ // TODO : find a better name
+ // as @ConsistantDependencies
+ // or make it as a start/stop event for container only when deps. are OK
+}
diff --git a/environments/osgi/core/api/src/main/resources/META-INF/weld-osgi-core-api.bnd b/environments/osgi/core/api/src/main/resources/META-INF/weld-osgi-core-api.bnd
new file mode 100644
index 00000000000..67353dfb7bf
--- /dev/null
+++ b/environments/osgi/core/api/src/main/resources/META-INF/weld-osgi-core-api.bnd
@@ -0,0 +1,3 @@
+Export-Package org.jboss.weld.environment.osgi.api; \
+ org.jboss.weld.environment.osgi.api.annotation; \
+ org.jboss.weld.environment.osgi.api.events;version=${pom.version}
diff --git a/environments/osgi/core/ee/pom.xml b/environments/osgi/core/ee/pom.xml
new file mode 100644
index 00000000000..49c463acafb
--- /dev/null
+++ b/environments/osgi/core/ee/pom.xml
@@ -0,0 +1,63 @@
+
+
+
+
+
+ org.jboss.weld.osgi
+ weld-osgi-core
+ 1.2.0-SNAPSHOT
+ ../pom.xml
+
+ 4.0.0
+ org.jboss.weld.osgi
+ weld-osgi-ee-integration
+ jar
+ Weld OSGi (EE Integration)
+ Weld OSGi EE bundle
+
+
+
+ Apache License, Version 2.0
+ repo
+ http://www.apache.org/licenses/LICENSE-2.0.html
+
+
+ http://www.seamframework.org/Weld
+
+
+
+
+ org.jboss.weld.osgi
+ weld-osgi-core-extension
+
+
+ javax
+ javaee-web-api
+ provided
+
+
+ org.osgi
+ org.osgi.core
+ provided
+
+
+
+
+
\ No newline at end of file
diff --git a/environments/osgi/core/ee/src/main/java/org/jboss/weld/environment/osgi/ee/BundleContextAccessor.java b/environments/osgi/core/ee/src/main/java/org/jboss/weld/environment/osgi/ee/BundleContextAccessor.java
new file mode 100644
index 00000000000..6a6ad909d44
--- /dev/null
+++ b/environments/osgi/core/ee/src/main/java/org/jboss/weld/environment/osgi/ee/BundleContextAccessor.java
@@ -0,0 +1,115 @@
+/*
+ * JBoss, Home of Professional Open Source
+ * Copyright 2011, Red Hat Middleware LLC, and individual contributors
+ * by the @authors tag. See the copyright.txt in the distribution for a
+ * full listing of individual contributors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * http://www.apache.org/licenses/LICENSE-2.0
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jboss.weld.environment.osgi.ee;
+
+import javax.annotation.PostConstruct;
+import javax.annotation.PreDestroy;
+import javax.annotation.Resource;
+import javax.ejb.Singleton;
+import javax.ejb.Startup;
+import javax.enterprise.event.Event;
+import javax.enterprise.inject.Any;
+import javax.enterprise.inject.Instance;
+import javax.inject.Inject;
+import javax.naming.Context;
+import javax.naming.InitialContext;
+import javax.naming.NamingException;
+import org.jboss.weld.environment.osgi.api.events.BundleContainerEvents;
+import org.jboss.weld.environment.osgi.api.events.Invalid;
+import org.jboss.weld.environment.osgi.impl.extension.beans.BundleHolder;
+import org.jboss.weld.environment.osgi.impl.extension.beans.ContainerObserver;
+import org.jboss.weld.environment.osgi.impl.extension.beans.RegistrationsHolderImpl;
+import org.jboss.weld.environment.osgi.impl.extension.beans.ServiceRegistryImpl;
+import org.jboss.weld.environment.osgi.impl.extension.service.WeldOSGiExtension;
+import org.jboss.weld.environment.osgi.impl.integration.ServicePublisher;
+import org.osgi.framework.BundleContext;
+import org.osgi.framework.ServiceRegistration;
+
+@Singleton
+@Startup
+public class BundleContextAccessor {
+
+ @Inject
+ private WeldOSGiExtension ext;
+ @Resource
+ private BundleContext injectedContext;
+ private BundleContext actualContext;
+ @Inject
+ private BundleHolder holder;
+ @Inject
+ private ServiceRegistryImpl sr;
+ @Inject
+ private ContainerObserver observer;
+ @Inject
+ private Event invalid;
+ @Inject
+ private Event init;
+ @Inject
+ private Event shutdown;
+ @Inject
+ private RegistrationsHolderImpl registrations;
+ @Inject
+ @Any
+ private Instance