[seam-commits] Seam SVN: r9772 - trunk/doc/Seam_Reference_Guide/it-IT.
seam-commits at lists.jboss.org
seam-commits at lists.jboss.org
Sat Dec 13 14:45:32 EST 2008
Author: nico.ben
Date: 2008-12-13 14:45:32 -0500 (Sat, 13 Dec 2008)
New Revision: 9772
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po
trunk/doc/Seam_Reference_Guide/it-IT/Book_Info.po
trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
trunk/doc/Seam_Reference_Guide/it-IT/Testing.po
trunk/doc/Seam_Reference_Guide/it-IT/Validation.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po 2008-12-13 18:59:46 UTC (rev 9771)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po 2008-12-13 19:45:32 UTC (rev 9772)
@@ -6,7 +6,7 @@
"Project-Id-Version: seam 2_0\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-12-13 17:58+0000\n"
-"PO-Revision-Date: 2008-11-23 17:06+0100\n"
+"PO-Revision-Date: 2008-12-13 16:40+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -141,19 +141,19 @@
#: Author_Group.xml:88
#, no-c-format
msgid "<firstname>Steve</firstname> <surname>Ebersole</surname>"
-msgstr ""
+msgstr "<firstname>Steve</firstname> <surname>Ebersole</surname>"
#. Tag: othercredit
#: Author_Group.xml:92
#, no-c-format
msgid "<firstname>Michael</firstname> <surname>Courcy</surname>"
-msgstr ""
+msgstr "<firstname>Michael</firstname> <surname>Courcy</surname>"
#. Tag: shortaffil
#: Author_Group.xml:96
#, no-c-format
msgid "French Translation"
-msgstr ""
+msgstr "Traduzione in francese"
#. Tag: editor
#: Author_Group.xml:99
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Book_Info.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Book_Info.po 2008-12-13 18:59:46 UTC (rev 9771)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Book_Info.po 2008-12-13 19:45:32 UTC (rev 9772)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-13 16:38+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,10 +17,11 @@
#: Book_Info.xml:5
#, no-c-format
msgid "Seam - Contextual Components"
-msgstr ""
+msgstr "Seam - Componenti Contestuali"
#. Tag: subtitle
#: Book_Info.xml:6
#, no-c-format
msgid "A Framework for Enterprise Java"
-msgstr ""
+msgstr "Un framework per Java Enterprise"
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-13 18:59:46 UTC (rev 9771)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-13 19:45:32 UTC (rev 9772)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-12-12 19:46+0100\n"
+"PO-Revision-Date: 2008-12-13 20:10+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -35,7 +35,7 @@
#: Preface.xml:18
#, no-c-format
msgid "Seam defines a uniform component model for all business logic in your application. A Seam component may be stateful, with the state associated with any one of several well-defined contexts, including the long-running, persistent, <emphasis>business process context</emphasis> and the <emphasis>conversation context</emphasis>, which is preserved across multiple web requests in a user interaction."
-msgstr "Seam definisce un modello uniforme a componenti per tutte le business logic nella tua applicazione. Un componente Seam può essere stateful, con uno stato associato ad uno dei tanti contesti ben-definiti, che includono long-running, persistenza, <emphasis>contesto processo di business</emphasis> e il <emphasis>contesto conversazionale</emphasis>, che viene preservato lungo le richieste web multiple nell'interazione con l'utente."
+msgstr "Seam definisce un modello uniforme a componenti per tutte le business logic dell'applicazione. Un componente Seam può essere stateful, con uno stato associato ad uno dei tanti contesti ben-definiti, che includono long-running, persistenza, <emphasis>contesto del processo di business</emphasis> e il <emphasis>contesto conversazionale</emphasis>, che viene preservato lungo le diverse richieste web durante l'interazione dell'utente."
#. Tag: para
#: Preface.xml:25
@@ -47,7 +47,7 @@
#: Preface.xml:32
#, no-c-format
msgid "Unlike plain Java EE or J2EE components, Seam components may <emphasis>simultaneously</emphasis> access state associated with the web request and state held in transactional resources (without the need to propagate web request state manually via method parameters). You might object that the application layering imposed upon you by the old J2EE platform was a Good Thing. Well, nothing stops you creating an equivalent layered architecture using Seam—the difference is that <emphasis>you</emphasis> get to architect your own application and decide what the layers are and how they work together."
-msgstr "A differenza dei componenti J2EE o del semplice Java EE, i componenti Seam possono <emphasis>simultaneamente</emphasis> accedere allo stato associato allarichiesta web e allo stato mantenuto nelle risorse transazionali (senza il bisogno di propagare manualmente lo stato della richiesta web attraverso i parametri). Si potrebbe obbiettare che la stratificazione dell'applicazione impostadalla vecchia piattaforma J2EE fosse una Cosa Buona. Bene, niente ti vieta di creare un'architettura a strati equivalente usando Seam— la differenza è che <emphasis>tu</emphasis> decidi l'architettura della tua applicazione e decidi quali sono i layer e come lavorano assieme"
+msgstr "A differenza dei componenti J2EE o del semplice Java EE, i componenti Seam possono <emphasis>simultaneamente</emphasis> accedere allo stato associato alla richiesta web e allo stato mantenuto nelle risorse transazionali (senza il bisogno di propagare manualmente lo stato della richiesta web attraverso i parametri). Si potrebbe obbiettare che la stratificazione dell'applicazione impostadalla vecchia piattaforma J2EE fosse una Cosa Buona. Bene, niente ti vieta di creare un'architettura a strati equivalente usando Seam— la differenza è che <emphasis>tu</emphasis> decidi l'architettura della tua applicazione e decidi quali sono i layer e come lavorano assieme"
#. Tag: emphasis
#: Preface.xml:45
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Testing.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Testing.po 2008-12-13 18:59:46 UTC (rev 9771)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Testing.po 2008-12-13 19:45:32 UTC (rev 9772)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:39+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-13 20:13+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,17 +17,12 @@
#: Testing.xml:2
#, no-c-format
msgid "Testing Seam applications"
-msgstr ""
+msgstr "Test delle applicazioni Seam"
#. Tag: para
#: Testing.xml:3
#, no-c-format
-msgid ""
-"Most Seam applications will need at least two kinds of automated tests: "
-"<emphasis>unit tests</emphasis>, which test a particular Seam component in "
-"isolation, and scripted <emphasis>integration tests</emphasis> which "
-"exercise all Java layers of the application (that is, everything except the "
-"view pages)."
+msgid "Most Seam applications will need at least two kinds of automated tests: <emphasis>unit tests</emphasis>, which test a particular Seam component in isolation, and scripted <emphasis>integration tests</emphasis> which exercise all Java layers of the application (that is, everything except the view pages)."
msgstr ""
#. Tag: para
@@ -40,24 +35,18 @@
#: Testing.xml:15
#, no-c-format
msgid "Unit testing Seam components"
-msgstr ""
+msgstr "Test d'unità dei componenti Seam"
#. Tag: para
#: Testing.xml:16
#, no-c-format
-msgid ""
-"All Seam components are POJOs. This is a great place to start if you want "
-"easy unit testing. And since Seam emphasises the use of bijection for inter-"
-"component interactions and access to contextual objects, it's very easy to "
-"test a Seam component outside of its normal runtime environment."
+msgid "All Seam components are POJOs. This is a great place to start if you want easy unit testing. And since Seam emphasises the use of bijection for inter-component interactions and access to contextual objects, it's very easy to test a Seam component outside of its normal runtime environment."
msgstr ""
#. Tag: para
#: Testing.xml:23
#, no-c-format
-msgid ""
-"Consider the following Seam Component which creates a statement of account "
-"for a customer:"
+msgid "Consider the following Seam Component which creates a statement of account for a customer:"
msgstr ""
#. Tag: programlisting
@@ -79,8 +68,7 @@
" @Create\n"
" public void create() {\n"
" List<Invoice> invoices = entityManager\n"
-" .createQuery(\"select invoice from Invoice invoice where invoice."
-"customer = :customer\")\n"
+" .createQuery(\"select invoice from Invoice invoice where invoice.customer = :customer\")\n"
" .setParameter(\"customer\", customer)\n"
" .getResultList();\n"
" statementTotal = calculateTotal(invoices);\n"
@@ -99,13 +87,44 @@
" \n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateless\n"
+"@Scope(EVENT)\n"
+"@Name(\"statementOfAccount\")\n"
+"public class StatementOfAccount {\n"
+" \n"
+" @In(create=true) EntityManager entityManager\n"
+" \n"
+" private double statementTotal;\n"
+" \n"
+" @In\n"
+" private Customer customer;\n"
+" \n"
+" @Create\n"
+" public void create() {\n"
+" List<Invoice> invoices = entityManager\n"
+" .createQuery(\"select invoice from Invoice invoice where invoice.customer = :customer\")\n"
+" .setParameter(\"customer\", customer)\n"
+" .getResultList();\n"
+" statementTotal = calculateTotal(invoices);\n"
+" }\n"
+" \n"
+" public double calculateTotal(List<Invoice> invoices) {\n"
+" double total = 0.0;\n"
+" for (Invoice invoice: invoices)\n"
+" {\n"
+" double += invoice.getTotal();\n"
+" }\n"
+" return total;\n"
+" }\n"
+" \n"
+" // getter and setter for statementTotal\n"
+" \n"
+"}]]>"
#. Tag: para
#: Testing.xml:30
#, no-c-format
-msgid ""
-"We could write a unit test for the calculateTotal method (which tests the "
-"business logic of the component) as follows:"
+msgid "We could write a unit test for the calculateTotal method (which tests the business logic of the component) as follows:"
msgstr ""
#. Tag: programlisting
@@ -116,25 +135,28 @@
" \n"
" @Test\n"
" public testCalculateTotal {\n"
-" List<Invoice> invoices = generateTestInvoices(); // A test data "
-"generator\n"
-" double statementTotal = new StatementOfAccount().calculateTotal"
-"(invoices);\n"
+" List<Invoice> invoices = generateTestInvoices(); // A test data generator\n"
+" double statementTotal = new StatementOfAccount().calculateTotal(invoices);\n"
" assert statementTotal = 123.45;\n"
" } \n"
"}\n"
"]]>"
msgstr ""
+"<![CDATA[public class StatementOfAccountTest {\n"
+" \n"
+" @Test\n"
+" public testCalculateTotal {\n"
+" List<Invoice> invoices = generateTestInvoices(); // A test data generator\n"
+" double statementTotal = new StatementOfAccount().calculateTotal(invoices);\n"
+" assert statementTotal = 123.45;\n"
+" } \n"
+"}\n"
+"]]>"
#. Tag: para
#: Testing.xml:37
#, no-c-format
-msgid ""
-"You'll notice we aren't testing retrieving data from or persisting data to "
-"the database; nor are we testing any functionality provided by Seam. We are "
-"just testing the logic of our POJOs. Seam components don't usually depend "
-"directly upon container infrastructure, so most unit testing as as easy as "
-"that!"
+msgid "You'll notice we aren't testing retrieving data from or persisting data to the database; nor are we testing any functionality provided by Seam. We are just testing the logic of our POJOs. Seam components don't usually depend directly upon container infrastructure, so most unit testing as as easy as that!"
msgstr ""
#. Tag: para
@@ -147,29 +169,18 @@
#: Testing.xml:51
#, no-c-format
msgid "Integration testing Seam components"
-msgstr ""
+msgstr "Test d'integrazione dei componenti Seam"
#. Tag: para
#: Testing.xml:53
#, no-c-format
-msgid ""
-"Integration testing is slightly more difficult. In this case, we can't "
-"eliminate the container infrastructure; indeed, that is part of what is "
-"being tested! At the same time, we don't want to be forced to deploy our "
-"application to an application server to run the automated tests. We need to "
-"be able to reproduce just enough of the container infrastructure inside our "
-"testing environment to be able to exercise the whole application, without "
-"hurting performance too much."
+msgid "Integration testing is slightly more difficult. In this case, we can't eliminate the container infrastructure; indeed, that is part of what is being tested! At the same time, we don't want to be forced to deploy our application to an application server to run the automated tests. We need to be able to reproduce just enough of the container infrastructure inside our testing environment to be able to exercise the whole application, without hurting performance too much."
msgstr ""
#. Tag: para
#: Testing.xml:62
#, no-c-format
-msgid ""
-"The approach taken by Seam is to let you write tests that exercise your "
-"components while running inside a pruned down container environment (Seam, "
-"together with the JBoss Embedded container; see <xref linkend=\"config."
-"install.embedded\"/> for configuration details)"
+msgid "The approach taken by Seam is to let you write tests that exercise your components while running inside a pruned down container environment (Seam, together with the JBoss Embedded container; see <xref linkend=\"config.install.embedded\"/> for configuration details)"
msgstr ""
#. Tag: programlisting
@@ -190,8 +201,7 @@
" setValue(\"#{user.username}\", \"1ovthafew\");\n"
" setValue(\"#{user.name}\", \"Gavin King\");\n"
" setValue(\"#{user.password}\", \"secret\");\n"
-" assert invokeMethod(\"#{register.register}\").equals(\"success"
-"\");\n"
+" assert invokeMethod(\"#{register.register}\").equals(\"success\");\n"
" assert getValue(\"#{user.username}\").equals(\"1ovthafew\");\n"
" assert getValue(\"#{user.name}\").equals(\"Gavin King\");\n"
" assert getValue(\"#{user.password}\").equals(\"secret\");\n"
@@ -205,6 +215,33 @@
" \n"
"}]]>"
msgstr ""
+"<![CDATA[public class RegisterTest extends SeamTest\n"
+"{\n"
+" \n"
+" @Test\n"
+" public void testRegisterComponent() throws Exception\n"
+" {\n"
+" \n"
+" new ComponentTest() {\n"
+"\n"
+" protected void testComponents() throws Exception\n"
+" {\n"
+" setValue(\"#{user.username}\", \"1ovthafew\");\n"
+" setValue(\"#{user.name}\", \"Gavin King\");\n"
+" setValue(\"#{user.password}\", \"secret\");\n"
+" assert invokeMethod(\"#{register.register}\").equals(\"success\");\n"
+" assert getValue(\"#{user.username}\").equals(\"1ovthafew\");\n"
+" assert getValue(\"#{user.name}\").equals(\"Gavin King\");\n"
+" assert getValue(\"#{user.password}\").equals(\"secret\");\n"
+" }\n"
+" \n"
+" }.run();\n"
+" \n"
+" }\n"
+"\n"
+" ...\n"
+" \n"
+"}]]>"
#. Tag: title
#: Testing.xml:73
@@ -215,11 +252,7 @@
#. Tag: para
#: Testing.xml:75
#, no-c-format
-msgid ""
-"Occasionally, we need to be able to replace the implementation of some Seam "
-"component that depends upon resources which are not available in the "
-"integration test environment. For example, suppose we have some Seam "
-"component which is a facade to some payment processing system:"
+msgid "Occasionally, we need to be able to replace the implementation of some Seam component that depends upon resources which are not available in the integration test environment. For example, suppose we have some Seam component which is a facade to some payment processing system:"
msgstr ""
#. Tag: programlisting
@@ -231,6 +264,10 @@
" public boolean processPayment(Payment payment) { .... }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"paymentProcessor\")\n"
+"public class PaymentProcessor {\n"
+" public boolean processPayment(Payment payment) { .... }\n"
+"}]]>"
#. Tag: para
#: Testing.xml:84
@@ -250,16 +287,18 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"paymentProcessor\")\n"
+"@Install(precedence=MOCK)\n"
+"public class MockPaymentProcessor extends PaymentProcessor {\n"
+" public boolean processPayment(Payment payment) {\n"
+" return true;\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Testing.xml:90
#, no-c-format
-msgid ""
-"Since the <literal>MOCK</literal> precedence is higher than the default "
-"precedence of application components, Seam will install the mock "
-"implementation whenever it is in the classpath. When deployed into "
-"production, the mock implementation is absent, so the real component will be "
-"installed."
+msgid "Since the <literal>MOCK</literal> precedence is higher than the default precedence of application components, Seam will install the mock implementation whenever it is in the classpath. When deployed into production, the mock implementation is absent, so the real component will be installed."
msgstr ""
#. Tag: title
@@ -271,22 +310,13 @@
#. Tag: para
#: Testing.xml:105
#, no-c-format
-msgid ""
-"An even harder problem is emulating user interactions. A third problem is "
-"where to put our assertions. Some test frameworks let us test the whole "
-"application by reproducing user interactions with the web browser. These "
-"frameworks have their place, but they are not appropriate for use at "
-"development time."
+msgid "An even harder problem is emulating user interactions. A third problem is where to put our assertions. Some test frameworks let us test the whole application by reproducing user interactions with the web browser. These frameworks have their place, but they are not appropriate for use at development time."
msgstr ""
#. Tag: para
#: Testing.xml:112
#, no-c-format
-msgid ""
-"<literal>SeamTest</literal> lets you write <emphasis>scripted</emphasis> "
-"tests, in a simulated JSF environment. The role of a scripted test is to "
-"reproduce the interaction between the view and the Seam components. In other "
-"words, you get to pretend you are the JSF implementation!"
+msgid "<literal>SeamTest</literal> lets you write <emphasis>scripted</emphasis> tests, in a simulated JSF environment. The role of a scripted test is to reproduce the interaction between the view and the Seam components. In other words, you get to pretend you are the JSF implementation!"
msgstr ""
#. Tag: para
@@ -327,21 +357,44 @@
" </tr>\n"
" </table>\n"
" <h:messages/>\n"
-" <h:commandButton type=\"submit\" value=\"Register\" action=\"#{register."
-"register}\"/>\n"
+" <h:commandButton type=\"submit\" value=\"Register\" action=\"#{register.register}\"/>\n"
" </h:form>\n"
" </f:view>\n"
" </body>\n"
"</html>]]>"
msgstr ""
+"<![CDATA[<html>\n"
+" <head>\n"
+" <title>Register New User</title>\n"
+" </head>\n"
+" <body>\n"
+" <f:view>\n"
+" <h:form>\n"
+" <table border=\"0\">\n"
+" <tr>\n"
+" <td>Username</td>\n"
+" <td><h:inputText value=\"#{user.username}\"/></td>\n"
+" </tr>\n"
+" <tr>\n"
+" <td>Real Name</td>\n"
+" <td><h:inputText value=\"#{user.name}\"/></td>\n"
+" </tr>\n"
+" <tr>\n"
+" <td>Password</td>\n"
+" <td><h:inputSecret value=\"#{user.password}\"/></td>\n"
+" </tr>\n"
+" </table>\n"
+" <h:messages/>\n"
+" <h:commandButton type=\"submit\" value=\"Register\" action=\"#{register.register}\"/>\n"
+" </h:form>\n"
+" </f:view>\n"
+" </body>\n"
+"</html>]]>"
#. Tag: para
#: Testing.xml:129
#, no-c-format
-msgid ""
-"We want to test the registration functionality of our application (the stuff "
-"that happens when the user clicks the Register button). We'll reproduce the "
-"JSF request lifecycle in an automated TestNG test:"
+msgid "We want to test the registration functionality of our application (the stuff that happens when the user clicks the Register button). We'll reproduce the JSF request lifecycle in an automated TestNG test:"
msgstr ""
#. Tag: programlisting
@@ -377,8 +430,7 @@
" @Override\n"
" protected void invokeApplication()\n"
" {\n"
-" assert invokeMethod(\"#{register.register}\").equals(\"success"
-"\");\n"
+" assert invokeMethod(\"#{register.register}\").equals(\"success\");\n"
" }\n"
"\n"
" @Override\n"
@@ -397,43 +449,76 @@
" \n"
"}]]>"
msgstr ""
+"<![CDATA[public class RegisterTest extends SeamTest\n"
+"{\n"
+" \n"
+" @Test\n"
+" public void testRegister() throws Exception\n"
+" {\n"
+" \n"
+" new FacesRequest() {\n"
+"\n"
+" @Override\n"
+" protected void processValidations() throws Exception\n"
+" {\n"
+" validateValue(\"#{user.username}\", \"1ovthafew\");\n"
+" validateValue(\"#{user.name}\", \"Gavin King\");\n"
+" validateValue(\"#{user.password}\", \"secret\");\n"
+" assert !isValidationFailure();\n"
+" }\n"
+" \n"
+" @Override\n"
+" protected void updateModelValues() throws Exception\n"
+" {\n"
+" setValue(\"#{user.username}\", \"1ovthafew\");\n"
+" setValue(\"#{user.name}\", \"Gavin King\");\n"
+" setValue(\"#{user.password}\", \"secret\");\n"
+" }\n"
+"\n"
+" @Override\n"
+" protected void invokeApplication()\n"
+" {\n"
+" assert invokeMethod(\"#{register.register}\").equals(\"success\");\n"
+" }\n"
+"\n"
+" @Override\n"
+" protected void renderResponse()\n"
+" {\n"
+" assert getValue(\"#{user.username}\").equals(\"1ovthafew\");\n"
+" assert getValue(\"#{user.name}\").equals(\"Gavin King\");\n"
+" assert getValue(\"#{user.password}\").equals(\"secret\");\n"
+" }\n"
+" \n"
+" }.run();\n"
+" \n"
+" }\n"
+"\n"
+" ...\n"
+" \n"
+"}]]>"
#. Tag: para
#: Testing.xml:137
#, no-c-format
-msgid ""
-"Notice that we've extended <literal>SeamTest</literal>, which provides a "
-"Seam environment for our components, and written our test script as an "
-"anonymous class that extends <literal>SeamTest.FacesRequest</literal>, which "
-"provides an emulated JSF request lifecycle. (There is also a "
-"<literal>SeamTest.NonFacesRequest</literal> for testing GET requests.) We've "
-"written our code in methods which are named for the various JSF phases, to "
-"emulate the calls that JSF would make to our components. Then we've thrown "
-"in various assertions."
+msgid "Notice that we've extended <literal>SeamTest</literal>, which provides a Seam environment for our components, and written our test script as an anonymous class that extends <literal>SeamTest.FacesRequest</literal>, which provides an emulated JSF request lifecycle. (There is also a <literal>SeamTest.NonFacesRequest</literal> for testing GET requests.) We've written our code in methods which are named for the various JSF phases, to emulate the calls that JSF would make to our components. Then we've thrown in various assertions."
msgstr ""
#. Tag: para
#: Testing.xml:148
#, no-c-format
-msgid ""
-"You'll find plenty of integration tests for the Seam example applications "
-"which demonstrate more complex cases. There are instructions for running "
-"these tests using Ant, or using the TestNG plugin for eclipse:"
+msgid "You'll find plenty of integration tests for the Seam example applications which demonstrate more complex cases. There are instructions for running these tests using Ant, or using the TestNG plugin for eclipse:"
msgstr ""
#. Tag: title
#: Testing.xml:164
#, no-c-format
msgid "Configuration"
-msgstr ""
+msgstr "Configurazione"
#. Tag: para
#: Testing.xml:166
#, no-c-format
-msgid ""
-"If you used seam-gen to create your project you are ready to start writing "
-"tests. Otherwise you'll need to setup the testing environment in your "
-"favorite build tool (e.g. ant, maven, eclipse)."
+msgid "If you used seam-gen to create your project you are ready to start writing tests. Otherwise you'll need to setup the testing environment in your favorite build tool (e.g. ant, maven, eclipse)."
msgstr ""
#. Tag: para
@@ -446,13 +531,13 @@
#: Testing.xml:182
#, no-c-format
msgid "Group Id"
-msgstr ""
+msgstr "Group Id"
#. Tag: entry
#: Testing.xml:185
#, no-c-format
msgid "Artifact Id"
-msgstr ""
+msgstr "Artifact Id"
#. Tag: entry
#: Testing.xml:188
@@ -461,184 +546,169 @@
msgstr ""
#. Tag: literal
-#: Testing.xml:196 Testing.xml:207 Testing.xml:218 Testing.xml:229
+#: Testing.xml:196
+#: Testing.xml:207
+#: Testing.xml:218
+#: Testing.xml:229
#, no-c-format
msgid "org.jboss.seam.embedded"
-msgstr ""
+msgstr "org.jboss.seam.embedded"
#. Tag: literal
#: Testing.xml:199
#, no-c-format
msgid "hibernate-all"
-msgstr ""
+msgstr "hibernate-all"
#. Tag: literal
#: Testing.xml:202
#, no-c-format
msgid "lib/test/hibernate-all.jar"
-msgstr ""
+msgstr "lib/test/hibernate-all.jar"
#. Tag: literal
#: Testing.xml:210
#, no-c-format
msgid "jboss-embedded-all"
-msgstr ""
+msgstr "jboss-embedded-all"
#. Tag: literal
#: Testing.xml:213
#, no-c-format
msgid "lib/test/jboss-embedded-all.jar"
-msgstr ""
+msgstr "lib/test/jboss-embedded-all.jar"
#. Tag: literal
#: Testing.xml:221
#, no-c-format
msgid "thirdparty-all"
-msgstr ""
+msgstr "thirdparty-all"
#. Tag: literal
#: Testing.xml:224
#, no-c-format
msgid "lib/test/thirdparty-all.jar"
-msgstr ""
+msgstr "lib/test/thirdparty-all.jar"
#. Tag: literal
#: Testing.xml:232
#, no-c-format
msgid "jboss-embedded-api"
-msgstr ""
+msgstr "jboss-embedded-api"
#. Tag: literal
#: Testing.xml:235
#, no-c-format
msgid "lib/jboss-embedded-api.jar"
-msgstr ""
+msgstr "lib/jboss-embedded-api.jar"
#. Tag: literal
#: Testing.xml:240
#, no-c-format
msgid "org.jboss.seam"
-msgstr ""
+msgstr "org.jboss.seam"
#. Tag: literal
#: Testing.xml:243
#, no-c-format
msgid "jboss-seam"
-msgstr ""
+msgstr "jboss-seam"
#. Tag: literal
#: Testing.xml:246
#, no-c-format
msgid "lib/jboss-seam.jar"
-msgstr ""
+msgstr "lib/jboss-seam.jar"
#. Tag: literal
#: Testing.xml:251
#, no-c-format
msgid "org.jboss.el"
-msgstr ""
+msgstr "org.jboss.el"
#. Tag: literal
#: Testing.xml:254
#, no-c-format
msgid "jboss-el"
-msgstr ""
+msgstr "jboss-el"
#. Tag: literal
#: Testing.xml:257
#, no-c-format
msgid "lib/jboss-el.jar"
-msgstr ""
+msgstr "lib/jboss-el.jar"
#. Tag: literal
#: Testing.xml:262
#, no-c-format
msgid "javax.faces"
-msgstr ""
+msgstr "javax.faces"
#. Tag: literal
#: Testing.xml:265
#, no-c-format
msgid "jsf-api"
-msgstr ""
+msgstr "jsf-api"
#. Tag: literal
#: Testing.xml:268
#, no-c-format
msgid "lib/jsf-api.jar"
-msgstr ""
+msgstr "lib/jsf-api.jar"
#. Tag: literal
#: Testing.xml:273
#, no-c-format
msgid "javax.el"
-msgstr ""
+msgstr "javax.el"
#. Tag: literal
#: Testing.xml:276
#, no-c-format
msgid "el-api"
-msgstr ""
+msgstr "el-api"
#. Tag: literal
#: Testing.xml:279
#, no-c-format
msgid "lib/el-api.jar"
-msgstr ""
+msgstr "lib/el-api.jar"
#. Tag: literal
-#: Testing.xml:284 Testing.xml:287
+#: Testing.xml:284
+#: Testing.xml:287
#, no-c-format
msgid "javax.activation"
-msgstr ""
+msgstr "javax.activation"
#. Tag: literal
#: Testing.xml:290
#, no-c-format
msgid "lib/activation.jar"
-msgstr ""
+msgstr "lib/activation.jar"
#. Tag: para
#: Testing.xml:297
#, no-c-format
-msgid ""
-"It's very important you don't put the compile time JBoss AS dependencies "
-"from <literal>lib/</literal> (e.g. <literal>jboss-system.jar</literal>) on "
-"the classpath, these will cause Embedded JBoss to not boot. So, just add the "
-"dependencies (e.g. Drools, jBPM)you need as you go."
+msgid "It's very important you don't put the compile time JBoss AS dependencies from <literal>lib/</literal> (e.g. <literal>jboss-system.jar</literal>) on the classpath, these will cause Embedded JBoss to not boot. So, just add the dependencies (e.g. Drools, jBPM)you need as you go."
msgstr ""
#. Tag: para
#: Testing.xml:305
#, no-c-format
-msgid ""
-"You also need to include the <literal>bootstrap/</literal> directory on the "
-"classpath; <literal>bootstrap/</literal> contains the configuration for "
-"Embedded JBoss."
+msgid "You also need to include the <literal>bootstrap/</literal> directory on the classpath; <literal>bootstrap/</literal> contains the configuration for Embedded JBoss."
msgstr ""
#. Tag: para
#: Testing.xml:311
#, no-c-format
-msgid ""
-"And, of course you need to put your built project and tests onto the "
-"classpath as well as jar for your test framework. Don't forget to put all "
-"the correct configuration files for JPA and Seam onto the classpath as well."
-"Seam asks Embedded JBoss to deploy any resource (jar or directory) which has "
-"<literal>seam.properties</literal> in it's root. Therefore, if you don't "
-"assemble a directory structure that resembles a deployable archive "
-"containing your built project, you must put a <literal>seam.properties</"
-"literal> in each resource."
+msgid "And, of course you need to put your built project and tests onto the classpath as well as jar for your test framework. Don't forget to put all the correct configuration files for JPA and Seam onto the classpath as well.Seam asks Embedded JBoss to deploy any resource (jar or directory) which has <literal>seam.properties</literal> in it's root. Therefore, if you don't assemble a directory structure that resembles a deployable archive containing your built project, you must put a <literal>seam.properties</literal> in each resource."
msgstr ""
#. Tag: para
#: Testing.xml:323
#, no-c-format
-msgid ""
-"By default, a generated project will use the <literal>java:/DefaultDS</"
-"literal> (a built in HSQL datasource in Embedded JBoss) for testing. If you "
-"want to use another datasource place the <literal>foo-ds.xml</literal> into "
-"<literal>bootstrap/deploy</literal> directory."
+msgid "By default, a generated project will use the <literal>java:/DefaultDS</literal> (a built in HSQL datasource in Embedded JBoss) for testing. If you want to use another datasource place the <literal>foo-ds.xml</literal> into <literal>bootstrap/deploy</literal> directory."
msgstr ""
#. Tag: title
@@ -650,17 +720,13 @@
#. Tag: para
#: Testing.xml:336
#, no-c-format
-msgid ""
-"Seam provides TestNG support out of the box, but you can also use another "
-"test framework, such as JUnit, if you want."
+msgid "Seam provides TestNG support out of the box, but you can also use another test framework, such as JUnit, if you want."
msgstr ""
#. Tag: para
#: Testing.xml:341
#, no-c-format
-msgid ""
-"You'll need to provide an implementation of <literal>AbstractSeamTest</"
-"literal> which does the following:"
+msgid "You'll need to provide an implementation of <literal>AbstractSeamTest</literal> which does the following:"
msgstr ""
#. Tag: para
@@ -678,33 +744,25 @@
#. Tag: para
#: Testing.xml:360
#, no-c-format
-msgid ""
-"Calls <literal>super.setupClass()</literal> to setup integration test "
-"environment. This should be called before any test methods are called."
+msgid "Calls <literal>super.setupClass()</literal> to setup integration test environment. This should be called before any test methods are called."
msgstr ""
#. Tag: para
#: Testing.xml:367
#, no-c-format
-msgid ""
-"Calls <literal>super.cleanupClass()</literal> to clean up the integration "
-"test environment."
+msgid "Calls <literal>super.cleanupClass()</literal> to clean up the integration test environment."
msgstr ""
#. Tag: para
#: Testing.xml:373
#, no-c-format
-msgid ""
-"Calls <literal>super.startSeam()</literal> to start Seam at the start of "
-"integration testing."
+msgid "Calls <literal>super.startSeam()</literal> to start Seam at the start of integration testing."
msgstr ""
#. Tag: para
#: Testing.xml:379
#, no-c-format
-msgid ""
-"Calls <literal>super.stopSeam()</literal> to cleanly shut down Seam at the "
-"end of integration testing."
+msgid "Calls <literal>super.stopSeam()</literal> to cleanly shut down Seam at the end of integration testing."
msgstr ""
#. Tag: title
@@ -716,25 +774,19 @@
#. Tag: para
#: Testing.xml:390
#, no-c-format
-msgid ""
-"If you need to insert or clean data in your database before each test you "
-"can use Seam's integration with DBUnit. To do this, extend DBUnitSeamTest "
-"rather than SeamTest."
+msgid "If you need to insert or clean data in your database before each test you can use Seam's integration with DBUnit. To do this, extend DBUnitSeamTest rather than SeamTest."
msgstr ""
#. Tag: para
#: Testing.xml:396
#, no-c-format
msgid "You need to provide a dataset for DBUnit."
-msgstr ""
+msgstr "Devi fornire un dataset per DBUnit."
#. Tag: caution
#: Testing.xml:400
#, no-c-format
-msgid ""
-"DBUnit supports two formats for dataset files, flat and XML. Seam's "
-"DBUnitSeamTest assumes the flat format is used, so make sure that your "
-"dataset is in this format."
+msgid "DBUnit supports two formats for dataset files, flat and XML. Seam's DBUnitSeamTest assumes the flat format is used, so make sure that your dataset is in this format."
msgstr ""
#. Tag: programlisting
@@ -755,13 +807,24 @@
" \n"
"</dataset>]]>"
msgstr ""
+"<![CDATA[<dataset>\n"
+" \n"
+" <ARTIST \n"
+" id=\"1\"\n"
+" dtype=\"Band\"\n"
+" name=\"Pink Floyd\" />\n"
+" \n"
+" <DISC\n"
+" id=\"1\"\n"
+" name=\"Dark Side of the Moon\"\n"
+" artist_id=\"1\" />\n"
+" \n"
+"</dataset>]]>"
#. Tag: para
#: Testing.xml:408
#, no-c-format
-msgid ""
-"and tell Seam about it by overriding <literal>prepareDBUnitOperations()</"
-"literal>:"
+msgid "and tell Seam about it by overriding <literal>prepareDBUnitOperations()</literal>:"
msgstr ""
#. Tag: programlisting
@@ -774,104 +837,89 @@
" );\n"
" }]]>"
msgstr ""
+"<![CDATA[protected void prepareDBUnitOperations() {\n"
+" beforeTestOperations.add(\n"
+" new DataSetOperation(\"my/datasets/BaseData.xml\")\n"
+" );\n"
+" }]]>"
#. Tag: para
#: Testing.xml:414
#, no-c-format
-msgid ""
-"<literal>DataSetOperation</literal> defaults to <literal>DatabaseOperation."
-"CLEAN_INSERT</literal> if no other operation is specified as a constructor "
-"argument. The above example cleans all tables defined <literal>BaseData.xml</"
-"literal>, then inserts all rows declared in <literal>BaseData.xml</literal> "
-"before each <literal>@Test</literal> method is invoked."
+msgid "<literal>DataSetOperation</literal> defaults to <literal>DatabaseOperation.CLEAN_INSERT</literal> if no other operation is specified as a constructor argument. The above example cleans all tables defined <literal>BaseData.xml</literal>, then inserts all rows declared in <literal>BaseData.xml</literal> before each <literal>@Test</literal> method is invoked."
msgstr ""
#. Tag: para
#: Testing.xml:422
#, no-c-format
-msgid ""
-"If you require extra cleanup after a test method executes, add operations to "
-"<literal>afterTestOperations</literal> list."
+msgid "If you require extra cleanup after a test method executes, add operations to <literal>afterTestOperations</literal> list."
msgstr ""
#. Tag: para
#: Testing.xml:427
#, no-c-format
-msgid ""
-"You need to tell DBUnit about the datasource you are using by setting a "
-"TestNG test parameter named <literal>datasourceJndiName</literal>:"
+msgid "You need to tell DBUnit about the datasource you are using by setting a TestNG test parameter named <literal>datasourceJndiName</literal>:"
msgstr ""
#. Tag: programlisting
#: Testing.xml:432
#, no-c-format
-msgid ""
-"<![CDATA[<parameter name=\"datasourceJndiName\" value=\"java:/"
-"seamdiscsDatasource\"/>]]>"
-msgstr ""
+msgid "<![CDATA[<parameter name=\"datasourceJndiName\" value=\"java:/seamdiscsDatasource\"/>]]>"
+msgstr "<![CDATA[<parameter name=\"datasourceJndiName\" value=\"java:/seamdiscsDatasource\"/>]]>"
#. Tag: para
#: Testing.xml:434
#, no-c-format
-msgid ""
-"DBUnitSeamTest has support for MySQL and HSQL - you need to tell it which "
-"database is being used:"
+msgid "DBUnitSeamTest has support for MySQL and HSQL - you need to tell it which database is being used:"
msgstr ""
#. Tag: programlisting
#: Testing.xml:439
#, no-c-format
msgid "<![CDATA[<parameter name=\"database\" value=\"HSQL\" />]]>"
-msgstr ""
+msgstr "<![CDATA[<parameter name=\"database\" value=\"HSQL\" />]]>"
#. Tag: para
#: Testing.xml:441
#, no-c-format
-msgid ""
-"It also allows you to insert binary data into the test data set (n.b. this "
-"is untested on Windows). You need to tell it where to locate these resources:"
+msgid "It also allows you to insert binary data into the test data set (n.b. this is untested on Windows). You need to tell it where to locate these resources:"
msgstr ""
#. Tag: programlisting
#: Testing.xml:447
#, no-c-format
msgid "<![CDATA[<parameter name=\"binaryDir\" value=\"images/\" />]]>"
-msgstr ""
+msgstr "<![CDATA[<parameter name=\"binaryDir\" value=\"images/\" />]]>"
#. Tag: para
#: Testing.xml:449
#, no-c-format
-msgid ""
-"You <emphasis>must</emphasis> specify these three parameters in your "
-"<literal>testng.xml</literal>."
+msgid "You <emphasis>must</emphasis> specify these three parameters in your <literal>testng.xml</literal>."
msgstr ""
#. Tag: para
#: Testing.xml:454
#, no-c-format
-msgid ""
-"If you want to use DBUnitSeamTest with another database, you'll need to "
-"implement some methods. Read the javadoc of <literal>AbstractDBUnitSeamTest</"
-"literal> for more."
+msgid "If you want to use DBUnitSeamTest with another database, you'll need to implement some methods. Read the javadoc of <literal>AbstractDBUnitSeamTest</literal> for more."
msgstr ""
#. Tag: title
#: Testing.xml:463
#, no-c-format
msgid "Integration Testing Seam Mail"
-msgstr ""
+msgstr "Test d'integrazione di Seam Mail"
#. Tag: caution
#: Testing.xml:465
#, no-c-format
msgid "Warning! This feature is still under development."
-msgstr ""
+msgstr "Attenzione! Questa funzionalità è ancora in fase di sviluppo."
#. Tag: para
#: Testing.xml:469
#, no-c-format
msgid "It's very easy to integration test your Seam Mail:"
-msgstr ""
+msgstr "E' facilissimo eseguire il test d'integrazione con Seam Mail:"
#. Tag: programlisting
#: Testing.xml:473
@@ -893,11 +941,9 @@
" \n"
" @Override\n"
" protected void invokeApplication() throws Exception {\n"
-" MimeMessage renderedMessage = getRenderedMailMessage(\"/simple."
-"xhtml\");\n"
+" MimeMessage renderedMessage = getRenderedMailMessage(\"/simple.xhtml\");\n"
" assert renderedMessage.getAllRecipients().length == 1;\n"
-" InternetAddress to = (InternetAddress) renderedMessage."
-"getAllRecipients()[0];\n"
+" InternetAddress to = (InternetAddress) renderedMessage.getAllRecipients()[0];\n"
" assert to.getAddress().equals(\"test at example.com\");\n"
" }\n"
" \n"
@@ -905,23 +951,41 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[public class MailTest extends SeamTest {\n"
+" \n"
+" @Test\n"
+" public void testSimpleMessage() throws Exception {\n"
+" \n"
+" new FacesRequest() {\n"
+"\n"
+" @Override\n"
+" protected void updateModelValues() throws Exception {\n"
+" setValue(\"#{person.firstname}\", \"Pete\");\n"
+" setValue(\"#{person.lastname}\", \"Muir\");\n"
+" setValue(\"#{person.address}\", \"test at example.com\");\n"
+" }\n"
+" \n"
+" @Override\n"
+" protected void invokeApplication() throws Exception {\n"
+" MimeMessage renderedMessage = getRenderedMailMessage(\"/simple.xhtml\");\n"
+" assert renderedMessage.getAllRecipients().length == 1;\n"
+" InternetAddress to = (InternetAddress) renderedMessage.getAllRecipients()[0];\n"
+" assert to.getAddress().equals(\"test at example.com\");\n"
+" }\n"
+" \n"
+" }.run(); \n"
+" }\n"
+"}]]>"
#. Tag: para
#: Testing.xml:475
#, no-c-format
-msgid ""
-"We create a new <literal>FacesRequest</literal> as normal. Inside the "
-"invokeApplication hook we render the message using "
-"<literal>getRenderedMailMessage(viewId);</literal>, passing the viewId of "
-"the message to render. The method returns the rendered message on which you "
-"can do your tests. You can of course also use any of the standard JSF "
-"lifecycle methods."
+msgid "We create a new <literal>FacesRequest</literal> as normal. Inside the invokeApplication hook we render the message using <literal>getRenderedMailMessage(viewId);</literal>, passing the viewId of the message to render. The method returns the rendered message on which you can do your tests. You can of course also use any of the standard JSF lifecycle methods."
msgstr ""
#. Tag: para
#: Testing.xml:484
#, no-c-format
-msgid ""
-"There is no support for rendering standard JSF components so you can't test "
-"the content body of the mail message easily."
+msgid "There is no support for rendering standard JSF components so you can't test the content body of the mail message easily."
msgstr ""
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Validation.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Validation.po 2008-12-13 18:59:46 UTC (rev 9771)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Validation.po 2008-12-13 19:45:32 UTC (rev 9772)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:39+0000\n"
-"PO-Revision-Date: 2008-12-13 16:30+0100\n"
+"PO-Revision-Date: 2008-12-13 20:44+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -123,7 +123,7 @@
#: Validation.xml:24
#, no-c-format
msgid "Well, that's a decent first cut, but in practice it might be more elegant to use custom constraints instead of the ones built into Hibernate Validator:"
-msgstr ""
+msgstr "Bene, questo è una buona riduzione, ma in pratica puoi essere più elegante se utilizzi dei vincoli personalizzati invece di quelli interni a Hibernate Validator:"
#. Tag: programlisting
#: Validation.xml:30
@@ -163,7 +163,7 @@
#: Validation.xml:32
#, no-c-format
msgid "Whichever route we take, we no longer need to specify the type of validation to be used in the JSF page. Instead, we can use <literal><s:validate></literal> to validate against the constraint defined on the model object."
-msgstr ""
+msgstr "Qualsiasi strada prendiamo non dobbiamo più specificare il tipo di validazione da usare nelle pagine JSF. Invece possiamo usare <literal><s:validate></literal> per validare il vincolo definito nell'oggetto modello."
#. Tag: programlisting
#: Validation.xml:39
@@ -215,13 +215,13 @@
#: Validation.xml:41
#, no-c-format
msgid "<emphasis>Note:</emphasis> specifying <literal>@NotNull</literal> on the model does <emphasis>not</emphasis> eliminate the requirement for <literal>required=\"true\"</literal> to appear on the control! This is due to a limitation of the JSF validation architecture."
-msgstr ""
+msgstr "<emphasis>Nota:</emphasis> specificare <literal>@NotNull</literal> nel modello <emphasis>non</emphasis> elimina la necessità di <literal>required=\"true\"</literal> per farlo apparire nel controllo! Questo è dovuto ad una limitazione nell'architettura di validazione in JSF."
#. Tag: para
#: Validation.xml:48
#, no-c-format
msgid "This approach <emphasis>defines</emphasis> constraints on the model, and <emphasis>presents</emphasis> constraint violations in the view—a significantly better design."
-msgstr ""
+msgstr "Quest'approccio <emphasis>definisce</emphasis> i vincoli sul modello e <emphasis>presenta</emphasis> le violazioni al vincolo nella vista—di gran lunga un miglior design."
#. Tag: para
#: Validation.xml:54
@@ -287,7 +287,7 @@
#: Validation.xml:67
#, no-c-format
msgid "Now we need to do something about displaying feedback to the user when validation fails. Currently we are displaying all messages at the top of the form. In order for the user to correlate the message with an input, you need to define a label using the standard <literal>label</literal> attribute on the input component."
-msgstr ""
+msgstr "Adesso occorre fare qualcosa per mostrare all'utente un messaggio quando la validazione fallisce. Ora vengono mostrati tutti i messaggi in cima alla form. Per consentire all'utente di associare il messaggio al singolo input, occorre definire un'etichetta e usare l'attributo standard <literal>label</literal> sul componente d'input."
#. Tag: programlisting
#: Validation.xml:73
@@ -305,7 +305,7 @@
#: Validation.xml:75
#, no-c-format
msgid "You can then inject this value into the message string using the placeholder {0} (the first and only parameter passed to a JSF message for a Hiberate Validator restriction). See the internationalization section for more information regarding where to define these messages."
-msgstr ""
+msgstr "Puoi iniettare questo valore nella stringa del messaggio usando il placeholder {0} (il primo ed unico parametro passato al messaggio JSF a causa di una restrizione in Hibernate Validator). Vedere la sezione Internazionalizzazione per ulteriori informazioni sulla definizione dei messaggi."
#. Tag: programlisting
#: Validation.xml:83
@@ -317,13 +317,13 @@
#: Validation.xml:85
#, no-c-format
msgid "What we would really like to do, though, is display the message next to the field with the error (this is possible in plain JSF), highlight the field and label (this is not possible) and, for good measure, display some image next to the field (also not possible). We also want to display a little colored asterisk next to the label for each required form field. Using this approach, the identifying label is not necessary."
-msgstr ""
+msgstr "Ciò che vorremmo fare, tuttavia, è mostrare il messaggio vicino al campo con l'errore (questo è possibile nel semplice JSF), ed evidenziare il campo e l'etichetta (questo non è possibile) ed, eventualmente, mostrare un'immagine vicino al campo (anche questo non è possibile). Vogliamo anche mostrare un piccolo asterisco colorato vicino all'etichetta per ciascun campo richiesto. Utilizzando quest'approccio non è più necessario identificare l'etichetta."
#. Tag: para
#: Validation.xml:95
#, no-c-format
msgid "That's quite a lot of functionality we need for each field of our form. We wouldn't want to have to specify higlighting and the layout of the image, message and input field for every field on the form. So, instead, we'll specify the common layout in a facelets template:"
-msgstr ""
+msgstr "Abbiamo quindi bisogno di parecchia funzionalità per ogni singolo campo della form. Ma non vogliamo essere costretti a specificare per ogni campo della form come evidenziare, come disporre l'immagine, quale messaggio scrivere e quale è il campo d'input da associare."
#. Tag: programlisting
#: Validation.xml:103
@@ -385,7 +385,7 @@
#: Validation.xml:105
#, no-c-format
msgid "We can include this template for each of our form fields using <literal><s:decorate></literal>."
-msgstr ""
+msgstr "Possiamo includere questo template per ciascuna campo della form utilizzando <literal><s:decorate></literal>."
#. Tag: programlisting
#: Validation.xml:110
@@ -485,7 +485,7 @@
#: Validation.xml:119
#, no-c-format
msgid "It's better style to define explicit ids for important controls on the page, especially if you want to do automated testing for the UI, using some toolkit like Selenium. If you don't provide explicit ids, JSF will generate them, but the generated values will change if you change anything on the page."
-msgstr ""
+msgstr "E' uno stile migliore definire esplicitamente gli id per i controlli importanti all'interno della pagina, specialmente in caso di test automatico della UI, utilizzando dei toolkit quale Selenium. Se non vengono forniti gli id in modo esplicito, JSF li genererà, mai valori generati cambieranno se si cambia qualcosa nella pagina."
#. Tag: programlisting
#: Validation.xml:128
@@ -535,11 +535,12 @@
"\n"
"</h:form>]]>"
+# message bundle = ?
#. Tag: para
#: Validation.xml:130
#, no-c-format
msgid "And what if you want to specify a different message to be displayed when validation fails? You can use the Seam message bundle (and all it's goodies like el expressions inside the message, and per-view message bundles) with the Hibernate Validator:"
-msgstr ""
+msgstr "E se vuoi specificare un messaggio diverso quando la validazione fallisce? Puoi utilizzare il message bundle di Seam con Hibernate Validator (e tutte le altre finezze come le espressioni EL dentro il messaggio ed i message bundle per ogni singola vista)."
#. Tag: programlisting
#: Validation.xml:137
More information about the seam-commits
mailing list