[seam-commits] Seam SVN: r9776 - trunk/doc/Seam_Reference_Guide/it-IT.
seam-commits at lists.jboss.org
seam-commits at lists.jboss.org
Sun Dec 14 16:16:35 EST 2008
Author: nico.ben
Date: 2008-12-14 16:16:33 -0500 (Sun, 14 Dec 2008)
New Revision: 9776
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Gettingstarted.po
trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.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/Tutorial.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Gettingstarted.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Gettingstarted.po 2008-12-13 23:24:40 UTC (rev 9775)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Gettingstarted.po 2008-12-14 21:16:33 UTC (rev 9776)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-11-06 00:23+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-14 19:09+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,85 +17,54 @@
#: Gettingstarted.xml:5
#, no-c-format
msgid "Getting started with Seam, using seam-gen"
-msgstr ""
+msgstr "Iniziare con Seam usando seam-gen"
#. Tag: para
#: Gettingstarted.xml:7
#, no-c-format
-msgid ""
-"The Seam distribution includes a command line utility that makes it really "
-"easy to set up an Eclipse project, generate some simple Seam skeleton code, "
-"and reverse engineer an application from a preexisting database."
+msgid "The Seam distribution includes a command line utility that makes it really easy to set up an Eclipse project, generate some simple Seam skeleton code, and reverse engineer an application from a preexisting database."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:10
#, no-c-format
-msgid ""
-"This is the easy way to get your feet wet with Seam, and gives you some "
-"ammunition for next time you find yourself trapped in an elevator with one "
-"of those tedious Ruby guys ranting about how great and wonderful his new toy "
-"is for building totally trivial applications that put things in databases."
-msgstr ""
+msgid "This is the easy way to get your feet wet with Seam, and gives you some ammunition for next time you find yourself trapped in an elevator with one of those tedious Ruby guys ranting about how great and wonderful his new toy is for building totally trivial applications that put things in databases."
+msgstr "Questo è il modo più semplice di sporcarti le mani con Seam e di preparare il colpo in canna per la prossima volta che ti troverai intrappolato in ascensore con uno di quei noiosi tipi di Ruby-on-Rail che farneticano quanto magnifico e meraviglioso sia l'ultimo giochino che hanno scoperto per realizzare applicazioni completamente banali che schiaffano delle cose nel database."
#. Tag: para
#: Gettingstarted.xml:14
#, no-c-format
-msgid ""
-"In this release, seam-gen works best for people with JBoss AS. You can use "
-"the generated project with other J2EE or Java EE 5 application servers by "
-"making a few manual changes to the project configuration."
+msgid "In this release, seam-gen works best for people with JBoss AS. You can use the generated project with other J2EE or Java EE 5 application servers by making a few manual changes to the project configuration."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:17
#, no-c-format
-msgid ""
-"You <emphasis>can</emphasis> use seam-gen without Eclipse, but in this "
-"tutorial, we want to show you how to use it in conjunction with Eclipse for "
-"debugging and integration testing. If you don't want to install Eclipse, you "
-"can still follow along with this tutorial—all steps can be performed from "
-"the command line."
+msgid "You <emphasis>can</emphasis> use seam-gen without Eclipse, but in this tutorial, we want to show you how to use it in conjunction with Eclipse for debugging and integration testing. If you don't want to install Eclipse, you can still follow along with this tutorial—all steps can be performed from the command line."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:21
#, no-c-format
-msgid ""
-"Seam-gen is basically just a big ugly Ant script wrapped around Hibernate "
-"Tools, together with some templates. That makes it easy to customize if you "
-"need to."
+msgid "Seam-gen is basically just a big ugly Ant script wrapped around Hibernate Tools, together with some templates. That makes it easy to customize if you need to."
msgstr ""
#. Tag: title
#: Gettingstarted.xml:25
#, no-c-format
msgid "Before you start"
-msgstr ""
+msgstr "Prima di iniziare"
#. Tag: para
#: Gettingstarted.xml:27
#, no-c-format
-msgid ""
-"Make sure you have JDK 5 or JDK 6 (see <xref linkend=\"jdk_dependencies\"/> "
-"for details), JBoss AS 4.2 and Ant 1.6, along with recent versions of "
-"Eclipse, the JBoss IDE plugin for Eclipse and the TestNG plugin for Eclipse "
-"correctly installed before starting. Add your JBoss installation to the "
-"JBoss Server View in Eclipse. Start JBoss in debug mode. Finally, start a "
-"command prompt in the directory where you unzipped the Seam distribution."
+msgid "Make sure you have JDK 5 or JDK 6 (see <xref linkend=\"jdk_dependencies\"/> for details), JBoss AS 4.2 and Ant 1.6, along with recent versions of Eclipse, the JBoss IDE plugin for Eclipse and the TestNG plugin for Eclipse correctly installed before starting. Add your JBoss installation to the JBoss Server View in Eclipse. Start JBoss in debug mode. Finally, start a command prompt in the directory where you unzipped the Seam distribution."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:33
#, no-c-format
-msgid ""
-"JBoss has sophisticated support for hot re-deployment of WARs and EARs. "
-"Unfortunately, due to bugs in the JVM, repeated redeployment of an EAR—which "
-"is common during development—eventually causes the JVM to run out of perm "
-"gen space. For this reason, we recommend running JBoss in a JVM with a large "
-"perm gen space at development time. If you're running JBoss from JBoss IDE, "
-"you can configure this in the server launch configuration, under \"VM "
-"arguments\". We suggest the following values:"
+msgid "JBoss has sophisticated support for hot re-deployment of WARs and EARs. Unfortunately, due to bugs in the JVM, repeated redeployment of an EAR—which is common during development—eventually causes the JVM to run out of perm gen space. For this reason, we recommend running JBoss in a JVM with a large perm gen space at development time. If you're running JBoss from JBoss IDE, you can configure this in the server launch configuration, under \"VM arguments\". We suggest the following values:"
msgstr ""
#. Tag: programlisting
@@ -107,9 +76,7 @@
#. Tag: para
#: Gettingstarted.xml:41
#, no-c-format
-msgid ""
-"If you don't have so much memory available, the following is our minimum "
-"recommendation:"
+msgid "If you don't have so much memory available, the following is our minimum recommendation:"
msgstr ""
#. Tag: programlisting
@@ -121,17 +88,13 @@
#. Tag: para
#: Gettingstarted.xml:45
#, no-c-format
-msgid ""
-"If you're running JBoss from the command line, you can configure the JVM "
-"options in <literal>bin/run.conf</literal>."
+msgid "If you're running JBoss from the command line, you can configure the JVM options in <literal>bin/run.conf</literal>."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:48
#, no-c-format
-msgid ""
-"If you don't want to bother with this stuff now, you don't have to—come back "
-"to it later, when you get your first <literal>OutOfMemoryException</literal>."
+msgid "If you don't want to bother with this stuff now, you don't have to—come back to it later, when you get your first <literal>OutOfMemoryException</literal>."
msgstr ""
#. Tag: title
@@ -143,10 +106,7 @@
#. Tag: para
#: Gettingstarted.xml:55
#, no-c-format
-msgid ""
-"The first thing we need to do is configure seam-gen for your environment: "
-"JBoss AS installation directory, Eclipse workspace, and database connection. "
-"It's easy, just type:"
+msgid "The first thing we need to do is configure seam-gen for your environment: JBoss AS installation directory, Eclipse workspace, and database connection. It's easy, just type:"
msgstr ""
#. Tag: programlisting
@@ -174,66 +134,47 @@
"\n"
"setup:\n"
" [echo] Welcome to seam-gen :-)\n"
-" [input] Enter your Java project workspace (the directory that contains "
-"your Seam projects) [C:/Projects] [C:/Projects]\n"
+" [input] Enter your Java project workspace (the directory that contains your Seam projects) [C:/Projects] [C:/Projects]\n"
"/Users/pmuir/workspace\n"
-" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.2."
-"GA] [C:/Program Files/jboss-4.2.2.GA]\n"
+" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.2.GA] [C:/Program Files/jboss-4.2.2.GA]\n"
"/Applications/jboss-4.2.2.GA\n"
" [input] Enter the project name [myproject] [myproject]\n"
"helloworld\n"
" [echo] Accepted project name as: helloworld\n"
-" [input] Select a RichFaces skin (not applicable if using ICEFaces) "
-"[blueSky] ([blueSky], classic, ruby, wine, deepMarine, emeraldTown, sakura, "
-"DEFAULT)\n"
+" [input] Select a RichFaces skin (not applicable if using ICEFaces) [blueSky] ([blueSky], classic, ruby, wine, deepMarine, emeraldTown, sakura, DEFAULT)\n"
"\n"
-" [input] Is this project deployed as an EAR (with EJB components) or a "
-"WAR (with no EJB support) [ear] ([ear], war, )\n"
+" [input] Is this project deployed as an EAR (with EJB components) or a WAR (with no EJB support) [ear] ([ear], war, )\n"
"\n"
-" [input] Enter the Java package name for your session beans [com.mydomain."
-"helloworld] [com.mydomain.helloworld]\n"
+" [input] Enter the Java package name for your session beans [com.mydomain.helloworld] [com.mydomain.helloworld]\n"
"org.jboss.helloworld\n"
-" [input] Enter the Java package name for your entity beans [org.jboss."
-"helloworld] [org.jboss.helloworld]\n"
+" [input] Enter the Java package name for your entity beans [org.jboss.helloworld] [org.jboss.helloworld]\n"
"\n"
-" [input] Enter the Java package name for your test cases [org.jboss."
-"helloworld.test] [org.jboss.helloworld.test]\n"
+" [input] Enter the Java package name for your test cases [org.jboss.helloworld.test] [org.jboss.helloworld.test]\n"
"\n"
-" [input] What kind of database are you using? [hsql] ([hsql], mysql, "
-"oracle, postgres, mssql, db2, sybase, enterprisedb, h2)\n"
+" [input] What kind of database are you using? [hsql] ([hsql], mysql, oracle, postgres, mssql, db2, sybase, enterprisedb, h2)\n"
"mysql\n"
-" [input] Enter the Hibernate dialect for your database [org.hibernate."
-"dialect.MySQLDialect] [org.hibernate.dialect.MySQLDialect]\n"
+" [input] Enter the Hibernate dialect for your database [org.hibernate.dialect.MySQLDialect] [org.hibernate.dialect.MySQLDialect]\n"
"\n"
-" [input] Enter the filesystem path to the JDBC driver jar [lib/hsqldb."
-"jar] [lib/hsqldb.jar]\n"
+" [input] Enter the filesystem path to the JDBC driver jar [lib/hsqldb.jar] [lib/hsqldb.jar]\n"
"/Users/pmuir/java/mysql.jar\n"
-" [input] Enter JDBC driver class for your database [com.mysql.jdbc."
-"Driver] [com.mysql.jdbc.Driver]\n"
+" [input] Enter JDBC driver class for your database [com.mysql.jdbc.Driver] [com.mysql.jdbc.Driver]\n"
"\n"
-" [input] Enter the JDBC URL for your database [jdbc:mysql:///test] [jdbc:"
-"mysql:///test]\n"
+" [input] Enter the JDBC URL for your database [jdbc:mysql:///test] [jdbc:mysql:///test]\n"
"jdbc:mysql:///helloworld\n"
" [input] Enter database username [sa] [sa]\n"
"pmuir\n"
" [input] Enter database password [] []\n"
"\n"
-" [input] skipping input as property hibernate.default_schema.new has "
-"already been set.\n"
-" [input] Enter the database catalog name (it is OK to leave this blank) "
-"[] []\n"
+" [input] skipping input as property hibernate.default_schema.new has already been set.\n"
+" [input] Enter the database catalog name (it is OK to leave this blank) [] []\n"
"\n"
-" [input] Are you working with tables that already exist in the database? "
-"[n] (y, [n], )\n"
+" [input] Are you working with tables that already exist in the database? [n] (y, [n], )\n"
"y\n"
-" [input] Do you want to drop and recreate the database tables and data in "
-"import.sql each time you deploy? [n] (y, [n], )\n"
+" [input] Do you want to drop and recreate the database tables and data in import.sql each time you deploy? [n] (y, [n], )\n"
"n\n"
-" [input] Enter your ICEfaces home directory (leave blank to omit "
-"ICEfaces) [] []\n"
+" [input] Enter your ICEfaces home directory (leave blank to omit ICEfaces) [] []\n"
"\n"
-"[propertyfile] Creating new property file: /Users/pmuir/workspace/jboss-seam/"
-"seam-gen/build.properties\n"
+"[propertyfile] Creating new property file: /Users/pmuir/workspace/jboss-seam/seam-gen/build.properties\n"
" [echo] Installing JDBC driver jar to JBoss server\n"
" [echo] Type 'seam create-project' to create the new project\n"
"\n"
@@ -245,48 +186,31 @@
#. Tag: para
#: Gettingstarted.xml:64
#, no-c-format
-msgid ""
-"The tool provides sensible defaults, which you can accept by just pressing "
-"enter at the prompt."
+msgid "The tool provides sensible defaults, which you can accept by just pressing enter at the prompt."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:66
#, no-c-format
-msgid ""
-"The most important choice you need to make is between EAR deployment and WAR "
-"deployment of your project. EAR projects support EJB 3.0 and require Java EE "
-"5. WAR projects do not support EJB 3.0, but may be deployed to a J2EE "
-"environment. The packaging of a WAR is also simpler to understand. If you "
-"installed an EJB3-ready application server like JBoss, choose <literal>ear</"
-"literal>. Otherwise, choose <literal>war</literal>. We'll assume that you've "
-"chosen an EAR deployment for the rest of the tutorial, but you can follow "
-"exactly the same steps for a WAR deployment."
+msgid "The most important choice you need to make is between EAR deployment and WAR deployment of your project. EAR projects support EJB 3.0 and require Java EE 5. WAR projects do not support EJB 3.0, but may be deployed to a J2EE environment. The packaging of a WAR is also simpler to understand. If you installed an EJB3-ready application server like JBoss, choose <literal>ear</literal>. Otherwise, choose <literal>war</literal>. We'll assume that you've chosen an EAR deployment for the rest of the tutorial, but you can follow exactly the same steps for a WAR deployment."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:73
#, no-c-format
-msgid ""
-"If you are working with an existing data model, make sure you tell seam-gen "
-"that the tables already exist in the database."
+msgid "If you are working with an existing data model, make sure you tell seam-gen that the tables already exist in the database."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:76
#, no-c-format
-msgid ""
-"The settings are stored in <literal>seam-gen/build.properties</literal>, but "
-"you can also modify them simply by running <literal>seam setup</literal> a "
-"second time."
+msgid "The settings are stored in <literal>seam-gen/build.properties</literal>, but you can also modify them simply by running <literal>seam setup</literal> a second time."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:79
#, no-c-format
-msgid ""
-"Now we can create a new project in our Eclipse workspace directory, by "
-"typing:"
+msgid "Now we can create a new project in our Eclipse workspace directory, by typing:"
msgstr ""
#. Tag: programlisting
@@ -305,11 +229,9 @@
"...\n"
"\n"
"new-project:\n"
-" [echo] A new Seam project named 'helloworld' was created in the C:"
-"\\Projects directory\n"
+" [echo] A new Seam project named 'helloworld' was created in the C:\\Projects directory\n"
" [echo] Type 'seam explode' and go to http://localhost:8080/helloworld\n"
-" [echo] Eclipse Users: Add the project into Eclipse using File > New "
-"> Project and select General > Project (not Java Project)\n"
+" [echo] Eclipse Users: Add the project into Eclipse using File > New > Project and select General > Project (not Java Project)\n"
" [echo] NetBeans Users: Open the project in NetBeans\n"
"\n"
"BUILD SUCCESSFUL\n"
@@ -320,75 +242,37 @@
#. Tag: para
#: Gettingstarted.xml:85
#, no-c-format
-msgid ""
-"This copies the Seam jars, dependent jars and the JDBC driver jar to a new "
-"Eclipse project, and generates all needed resources and configuration files, "
-"a facelets template file and stylesheet, along with Eclipse metadata and an "
-"Ant build script. The Eclipse project will be automatically deployed to an "
-"exploded directory structure in JBoss AS as soon as you add the project "
-"using <literal>New -> Project... -> General -> Project -> Next</"
-"literal>, typing the <literal>Project name</literal> (<literal>helloworld</"
-"literal> in this case), and then clicking <literal>Finish</literal>. Do not "
-"select <literal>Java Project</literal> from the New Project wizard."
+msgid "This copies the Seam jars, dependent jars and the JDBC driver jar to a new Eclipse project, and generates all needed resources and configuration files, a facelets template file and stylesheet, along with Eclipse metadata and an Ant build script. The Eclipse project will be automatically deployed to an exploded directory structure in JBoss AS as soon as you add the project using <literal>New -> Project... -> General -> Project -> Next</literal>, typing the <literal>Project name</literal> (<literal>helloworld</literal> in this case), and then clicking <literal>Finish</literal>. Do not select <literal>Java Project</literal> from the New Project wizard."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:93
#, no-c-format
-msgid ""
-"If your default JDK in Eclipse is not a Java SE 5 or Java SE 6 JDK, you will "
-"need to select a Java SE 5 compliant JDK using <literal>Project -> "
-"Properties -> Java Compiler</literal>."
+msgid "If your default JDK in Eclipse is not a Java SE 5 or Java SE 6 JDK, you will need to select a Java SE 5 compliant JDK using <literal>Project -> Properties -> Java Compiler</literal>."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:96
#, no-c-format
-msgid ""
-"Alternatively, you can deploy the project from outside Eclipse by typing "
-"<literal>seam explode</literal>."
+msgid "Alternatively, you can deploy the project from outside Eclipse by typing <literal>seam explode</literal>."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:98
#, no-c-format
-msgid ""
-"Go to <literal>http://localhost:8080/helloworld</literal> to see a welcome "
-"page. This is a facelets page, <literal>view/home.xhtml</literal>, using the "
-"template <literal>view/layout/template.xhtml</literal>. You can edit this "
-"page, or the template, in eclipse, and see the results "
-"<emphasis>immediately</emphasis>, by clicking refresh in your browser."
+msgid "Go to <literal>http://localhost:8080/helloworld</literal> to see a welcome page. This is a facelets page, <literal>view/home.xhtml</literal>, using the template <literal>view/layout/template.xhtml</literal>. You can edit this page, or the template, in eclipse, and see the results <emphasis>immediately</emphasis>, by clicking refresh in your browser."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:103
#, no-c-format
-msgid ""
-"Don't get scared by the XML configuration documents that were generated into "
-"the project directory. They are mostly standard Java EE stuff, the stuff you "
-"need to create once and then never look at again, and they are 90% the same "
-"between all Seam projects. (They are so easy to write that even seam-gen can "
-"do it.)"
+msgid "Don't get scared by the XML configuration documents that were generated into the project directory. They are mostly standard Java EE stuff, the stuff you need to create once and then never look at again, and they are 90% the same between all Seam projects. (They are so easy to write that even seam-gen can do it.)"
msgstr ""
#. Tag: para
#: Gettingstarted.xml:107
#, no-c-format
-msgid ""
-"The generated project includes three database and persistence "
-"configurations. The <literal>persistence-test.xml</literal> and "
-"<literal>import-test.sql</literal> files are used when running the TestNG "
-"unit tests against HSQLDB. The database schema and the test data in "
-"<literal>import-test.sql</literal> is always exported to the database before "
-"running tests. The <literal>myproject-dev-ds.xml</literal>, "
-"<literal>persistence-dev.xml</literal>and <literal>import-dev.sql</literal> "
-"files are for use when deploying the application to your development "
-"database. The schema might be exported automatically at deployment, "
-"depending upon whether you told seam-gen that you are working with an "
-"existing database. The <literal>myproject-prod-ds.xml</literal>, "
-"<literal>persistence-prod.xml</literal>and <literal>import-prod.sql</"
-"literal> files are for use when deploying the application to your production "
-"database. The schema is not exported automatically at deployment."
+msgid "The generated project includes three database and persistence configurations. The <literal>persistence-test.xml</literal> and <literal>import-test.sql</literal> files are used when running the TestNG unit tests against HSQLDB. The database schema and the test data in <literal>import-test.sql</literal> is always exported to the database before running tests. The <literal>myproject-dev-ds.xml</literal>, <literal>persistence-dev.xml</literal>and <literal>import-dev.sql</literal> files are for use when deploying the application to your development database. The schema might be exported automatically at deployment, depending upon whether you told seam-gen that you are working with an existing database. The <literal>myproject-prod-ds.xml</literal>, <literal>persistence-prod.xml</literal>and <literal>import-prod.sql</literal> files are for use when deploying the application to your production database. The schema is not exported automatically at deployment."
msgstr ""
#. Tag: title
@@ -400,10 +284,7 @@
#. Tag: para
#: Gettingstarted.xml:123
#, no-c-format
-msgid ""
-"If you're used to traditional action-style web frameworks, you're probably "
-"wondering how you can create a simple web page with a stateless action "
-"method in Java. If you type:"
+msgid "If you're used to traditional action-style web frameworks, you're probably wondering how you can create a simple web page with a stateless action method in Java. If you type:"
msgstr ""
#. Tag: programlisting
@@ -415,9 +296,7 @@
#. Tag: para
#: Gettingstarted.xml:128
#, no-c-format
-msgid ""
-"Seam will prompt for some information, and generate a new facelets page and "
-"Seam component for your project."
+msgid "Seam will prompt for some information, and generate a new facelets page and Seam component for your project."
msgstr ""
#. Tag: programlisting
@@ -446,19 +325,13 @@
"setup-filters:\n"
"\n"
"new-action:\n"
-" [echo] Creating a new stateless session bean component with an action "
-"method\n"
-" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss"
-"\\helloworld\n"
-" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss"
-"\\helloworld\n"
-" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss"
-"\\helloworld\\test\n"
-" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss"
-"\\helloworld\\test\n"
+" [echo] Creating a new stateless session bean component with an action method\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\\test\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\\test\n"
" [copy] Copying 1 file to C:\\Projects\\helloworld\\view\n"
-" [echo] Type 'seam restart' and go to http://localhost:8080/helloworld/"
-"ping.seam\n"
+" [echo] Type 'seam restart' and go to http://localhost:8080/helloworld/ping.seam\n"
"\n"
"BUILD SUCCESSFUL\n"
"Total time: 13 seconds\n"
@@ -468,34 +341,19 @@
#. Tag: para
#: Gettingstarted.xml:133
#, no-c-format
-msgid ""
-"Because we've added a new Seam component, we need to restart the exploded "
-"directory deployment. You can do this by typing <literal>seam restart</"
-"literal>, or by running the <literal>restart</literal> target in the "
-"generated project <literal>build.xml</literal> file from inside Eclipse. "
-"Another way to force a restart is to edit the file <literal>resources/META-"
-"INF/application.xml</literal> in Eclipse. <emphasis>Note that you do not "
-"need to restart JBoss each time you change the application.</emphasis>"
+msgid "Because we've added a new Seam component, we need to restart the exploded directory deployment. You can do this by typing <literal>seam restart</literal>, or by running the <literal>restart</literal> target in the generated project <literal>build.xml</literal> file from inside Eclipse. Another way to force a restart is to edit the file <literal>resources/META-INF/application.xml</literal> in Eclipse. <emphasis>Note that you do not need to restart JBoss each time you change the application.</emphasis>"
msgstr ""
#. Tag: para
#: Gettingstarted.xml:139
#, no-c-format
-msgid ""
-"Now go to <literal>http://localhost:8080/helloworld/ping.seam</literal> and "
-"click the button. You can see the code behind this action by looking in the "
-"project <literal>src</literal> directory. Put a breakpoint in the "
-"<literal>ping()</literal> method, and click the button again."
+msgid "Now go to <literal>http://localhost:8080/helloworld/ping.seam</literal> and click the button. You can see the code behind this action by looking in the project <literal>src</literal> directory. Put a breakpoint in the <literal>ping()</literal> method, and click the button again."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:143
#, no-c-format
-msgid ""
-"Finally, locate the <literal>PingTest.xml</literal> file in the test package "
-"and run the integration tests using the TestNG plugin for Eclipse. "
-"Alternatively, run the tests using <literal>seam test</literal> or the "
-"<literal>test</literal> target of the generated build."
+msgid "Finally, locate the <literal>PingTest.xml</literal> file in the test package and run the integration tests using the TestNG plugin for Eclipse. Alternatively, run the tests using <literal>seam test</literal> or the <literal>test</literal> target of the generated build."
msgstr ""
#. Tag: title
@@ -542,17 +400,13 @@
"setup-filters:\n"
"\n"
"new-form:\n"
-" [echo] Creating a new stateful session bean component with an action "
-"method\n"
+" [echo] Creating a new stateful session bean component with an action method\n"
" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\n"
" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\n"
-" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello"
-"\\test\n"
+" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\\test\n"
" [copy] Copying 1 file to C:\\Projects\\hello\\view\n"
-" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello"
-"\\test\n"
-" [echo] Type 'seam restart' and go to http://localhost:8080/hello/hello."
-"seam\n"
+" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\\test\n"
+" [echo] Type 'seam restart' and go to http://localhost:8080/hello/hello.seam\n"
"\n"
"BUILD SUCCESSFUL\n"
"Total time: 5 seconds\n"
@@ -562,11 +416,7 @@
#. Tag: para
#: Gettingstarted.xml:157
#, no-c-format
-msgid ""
-"Restart the application again, and go to <literal>http://localhost:8080/"
-"helloworld/hello.seam</literal>. Then take a look at the generated code. Run "
-"the test. Try adding some new fields to the form and Seam component "
-"(remember to restart the deployment each time you change the Java code)."
+msgid "Restart the application again, and go to <literal>http://localhost:8080/helloworld/hello.seam</literal>. Then take a look at the generated code. Run the test. Try adding some new fields to the form and Seam component (remember to restart the deployment each time you change the Java code)."
msgstr ""
#. Tag: title
@@ -578,9 +428,7 @@
#. Tag: para
#: Gettingstarted.xml:165
#, no-c-format
-msgid ""
-"Manually create some tables in your database. (If you need to switch to a "
-"different database, just run <literal>seam setup</literal> again.) Now type:"
+msgid "Manually create some tables in your database. (If you need to switch to a different database, just run <literal>seam setup</literal> again.) Now type:"
msgstr ""
#. Tag: programlisting
@@ -592,12 +440,7 @@
#. Tag: para
#: Gettingstarted.xml:170
#, no-c-format
-msgid ""
-"Restart the deployment, and go to <literal>http://localhost:8080/helloworld</"
-"literal>. You can browse the database, edit existing objects, and create new "
-"objects. If you look at the generated code, you'll probably be amazed how "
-"simple it is! Seam was designed so that data access code is easy to write by "
-"hand, even for people who don't want to cheat by using seam-gen."
+msgid "Restart the deployment, and go to <literal>http://localhost:8080/helloworld</literal>. You can browse the database, edit existing objects, and create new objects. If you look at the generated code, you'll probably be amazed how simple it is! Seam was designed so that data access code is easy to write by hand, even for people who don't want to cheat by using seam-gen."
msgstr ""
#. Tag: title
@@ -609,9 +452,7 @@
#. Tag: para
#: Gettingstarted.xml:179
#, no-c-format
-msgid ""
-"Place your existing, valid entity classes inside the <literal>src/main</"
-"literal>. Now type"
+msgid "Place your existing, valid entity classes inside the <literal>src/main</literal>. Now type"
msgstr ""
#. Tag: programlisting
@@ -623,9 +464,7 @@
#. Tag: para
#: Gettingstarted.xml:183
#, no-c-format
-msgid ""
-"Restart the deployment, and go to <literal>http://localhost:8080/helloworld</"
-"literal>."
+msgid "Restart the deployment, and go to <literal>http://localhost:8080/helloworld</literal>."
msgstr ""
#. Tag: title
@@ -637,25 +476,13 @@
#. Tag: para
#: Gettingstarted.xml:189
#, no-c-format
-msgid ""
-"Finally, we want to be able to deploy the application using standard Java EE "
-"5 packaging. First, we need to remove the exploded directory by running "
-"<literal>seam unexplode</literal>. To deploy the EAR, we can type "
-"<literal>seam deploy</literal> at the command prompt, or run the "
-"<literal>deploy</literal> target of the generated project build script. You "
-"can undeploy using <literal>seam undeploy</literal> or the "
-"<literal>undeploy</literal> target."
+msgid "Finally, we want to be able to deploy the application using standard Java EE 5 packaging. First, we need to remove the exploded directory by running <literal>seam unexplode</literal>. To deploy the EAR, we can type <literal>seam deploy</literal> at the command prompt, or run the <literal>deploy</literal> target of the generated project build script. You can undeploy using <literal>seam undeploy</literal> or the <literal>undeploy</literal> target."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:195
#, no-c-format
-msgid ""
-"By default, the application will be deployed with the <emphasis>dev profile</"
-"emphasis>. The EAR will include the <literal>persistence-dev.xml</literal> "
-"and <literal>import-dev.sql</literal> files, and the <literal>myproject-dev-"
-"ds.xml</literal> file will be deployed. You can change the profile, and use "
-"the <emphasis>prod profile</emphasis>, by typing"
+msgid "By default, the application will be deployed with the <emphasis>dev profile</emphasis>. The EAR will include the <literal>persistence-dev.xml</literal> and <literal>import-dev.sql</literal> files, and the <literal>myproject-dev-ds.xml</literal> file will be deployed. You can change the profile, and use the <emphasis>prod profile</emphasis>, by typing"
msgstr ""
#. Tag: programlisting
@@ -667,12 +494,7 @@
#. Tag: para
#: Gettingstarted.xml:202
#, no-c-format
-msgid ""
-"You can even define new deployment profiles for your application. Just add "
-"appropriately named files to your project—for example, <literal>persistence-"
-"staging.xml</literal>, <literal>import-staging.sql</literal> and "
-"<literal>myproject-staging-ds.xml</literal>—and select the name of the "
-"profile using <literal>-Dprofile=staging</literal>."
+msgid "You can even define new deployment profiles for your application. Just add appropriately named files to your project—for example, <literal>persistence-staging.xml</literal>, <literal>import-staging.sql</literal> and <literal>myproject-staging-ds.xml</literal>—and select the name of the profile using <literal>-Dprofile=staging</literal>."
msgstr ""
#. Tag: title
@@ -684,11 +506,7 @@
#. Tag: para
#: Gettingstarted.xml:211
#, no-c-format
-msgid ""
-"When you deploy your Seam application as an exploded directory, you'll get "
-"some support for incremental hot deployment at development time. You need to "
-"enable debug mode in both Seam and Facelets, by adding this line to "
-"<literal>components.xml</literal>:"
+msgid "When you deploy your Seam application as an exploded directory, you'll get some support for incremental hot deployment at development time. You need to enable debug mode in both Seam and Facelets, by adding this line to <literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -700,9 +518,7 @@
#. Tag: para
#: Gettingstarted.xml:217
#, no-c-format
-msgid ""
-"Now, the following files may be redeployed without requiring a full restart "
-"of the web application:"
+msgid "Now, the following files may be redeployed without requiring a full restart of the web application:"
msgstr ""
#. Tag: para
@@ -720,22 +536,13 @@
#. Tag: para
#: Gettingstarted.xml:229
#, no-c-format
-msgid ""
-"But if we want to change any Java code, we still need to do a full restart "
-"of the application. (In JBoss this may be accomplished by touching the top "
-"level deployment descriptor: <literal>application.xml</literal> for an EAR "
-"deployment, or <literal>web.xml</literal> for a WAR deployment.)"
+msgid "But if we want to change any Java code, we still need to do a full restart of the application. (In JBoss this may be accomplished by touching the top level deployment descriptor: <literal>application.xml</literal> for an EAR deployment, or <literal>web.xml</literal> for a WAR deployment.)"
msgstr ""
#. Tag: para
#: Gettingstarted.xml:233
#, no-c-format
-msgid ""
-"But if you really want a fast edit/compile/test cycle, Seam supports "
-"incremental redeployment of JavaBean components. To make use of this "
-"functionality, you must deploy the JavaBean components into the <literal>WEB-"
-"INF/dev</literal> directory, so that they will be loaded by a special Seam "
-"classloader, instead of by the WAR or EAR classloader."
+msgid "But if you really want a fast edit/compile/test cycle, Seam supports incremental redeployment of JavaBean components. To make use of this functionality, you must deploy the JavaBean components into the <literal>WEB-INF/dev</literal> directory, so that they will be loaded by a special Seam classloader, instead of by the WAR or EAR classloader."
msgstr ""
#. Tag: para
@@ -747,9 +554,7 @@
#. Tag: para
#: Gettingstarted.xml:242
#, no-c-format
-msgid ""
-"the components must be JavaBean components, they cannot be EJB3 beans (we "
-"are working on fixing this limitation)"
+msgid "the components must be JavaBean components, they cannot be EJB3 beans (we are working on fixing this limitation)"
msgstr ""
#. Tag: para
@@ -761,25 +566,19 @@
#. Tag: para
#: Gettingstarted.xml:251
#, no-c-format
-msgid ""
-"components deployed via <literal>components.xml</literal> may not be hot-"
-"deployed"
+msgid "components deployed via <literal>components.xml</literal> may not be hot-deployed"
msgstr ""
#. Tag: para
#: Gettingstarted.xml:255
#, no-c-format
-msgid ""
-"the hot-deployable components will not be visible to any classes deployed "
-"outside of <literal>WEB-INF/dev</literal>"
+msgid "the hot-deployable components will not be visible to any classes deployed outside of <literal>WEB-INF/dev</literal>"
msgstr ""
#. Tag: para
#: Gettingstarted.xml:260
#, no-c-format
-msgid ""
-"Seam debug mode must be enabled and <literal>jboss-seam-debug.jar</literal> "
-"must be in <literal>WEB-INF/lib</literal>"
+msgid "Seam debug mode must be enabled and <literal>jboss-seam-debug.jar</literal> must be in <literal>WEB-INF/lib</literal>"
msgstr ""
#. Tag: para
@@ -791,19 +590,13 @@
#. Tag: para
#: Gettingstarted.xml:269
#, no-c-format
-msgid ""
-"You may see errors if the system is placed under any load and debug is "
-"enabled."
+msgid "You may see errors if the system is placed under any load and debug is enabled."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:274
#, no-c-format
-msgid ""
-"If you create a WAR project using seam-gen, incremental hot deployment is "
-"available out of the box for classes in the <literal>src/hot</literal> "
-"source directory. However, seam-gen does not support incremental hot "
-"deployment for EAR projects."
+msgid "If you create a WAR project using seam-gen, incremental hot deployment is available out of the box for classes in the <literal>src/hot</literal> source directory. However, seam-gen does not support incremental hot deployment for EAR projects."
msgstr ""
#. Tag: title
@@ -815,14 +608,7 @@
#. Tag: para
#: Gettingstarted.xml:282
#, no-c-format
-msgid ""
-"Seam 2.0 was developed for JavaServer Faces 1.2. When using JBoss AS, we "
-"recommend using JBoss 4.2, which bundles the JSF 1.2 reference "
-"implementation. However, it is still possible to use Seam 2.0 on the JBoss "
-"4.0 platform. There are two basic steps required to do this: install an EJB3-"
-"enabled version of JBoss 4.0 and replace MyFaces with the JSF 1.2 reference "
-"implementation. Once you complete these steps, Seam 2.0 applications can be "
-"deployed to JBoss 4.0."
+msgid "Seam 2.0 was developed for JavaServer Faces 1.2. When using JBoss AS, we recommend using JBoss 4.2, which bundles the JSF 1.2 reference implementation. However, it is still possible to use Seam 2.0 on the JBoss 4.0 platform. There are two basic steps required to do this: install an EJB3-enabled version of JBoss 4.0 and replace MyFaces with the JSF 1.2 reference implementation. Once you complete these steps, Seam 2.0 applications can be deployed to JBoss 4.0."
msgstr ""
#. Tag: title
@@ -834,13 +620,7 @@
#. Tag: para
#: Gettingstarted.xml:290
#, no-c-format
-msgid ""
-"JBoss 4.0 does not ship a default configuration compatible with Seam. To run "
-"Seam, you must install JBoss 4.0.5 using the JEMS 1.2 installer with the "
-"ejb3 profile selected. Seam will not run with an installation that doesn't "
-"include EJB3 support. The JEMS installer can be downloaded from <ulink url="
-"\"http://labs.jboss.com/jemsinstaller/downloads\">http://labs.jboss.com/"
-"jemsinstaller/downloads</ulink>."
+msgid "JBoss 4.0 does not ship a default configuration compatible with Seam. To run Seam, you must install JBoss 4.0.5 using the JEMS 1.2 installer with the ejb3 profile selected. Seam will not run with an installation that doesn't include EJB3 support. The JEMS installer can be downloaded from <ulink url=\"http://labs.jboss.com/jemsinstaller/downloads\">http://labs.jboss.com/jemsinstaller/downloads</ulink>."
msgstr ""
#. Tag: title
@@ -852,21 +632,12 @@
#. Tag: para
#: Gettingstarted.xml:299
#, no-c-format
-msgid ""
-"The web configuration for JBoss 4.0 can be found in the <literal>server/"
-"default/deploy/jbossweb-tomcat55.sar</literal>. You'll need to delete "
-"<literal>myfaces-api.jar</literal> any <literal>myfaces-impl.jar</literal> "
-"from the <literal>jsf-libs </literal>directory. Then, you'll need to copy "
-"<literal>jsf-api.jar</literal>, <literal>jsf-impl.jar</literal>, <literal>el-"
-"api.jar</literal>, and <literal>el-ri.jar</literal> to that directory. The "
-"JSF JARs can be found in the Seam <literal>lib</literal> directory. The el "
-"JARs can be obtained from the Seam 1.2 release."
+msgid "The web configuration for JBoss 4.0 can be found in the <literal>server/default/deploy/jbossweb-tomcat55.sar</literal>. You'll need to delete <literal>myfaces-api.jar</literal> any <literal>myfaces-impl.jar</literal> from the <literal>jsf-libs </literal>directory. Then, you'll need to copy <literal>jsf-api.jar</literal>, <literal>jsf-impl.jar</literal>, <literal>el-api.jar</literal>, and <literal>el-ri.jar</literal> to that directory. The JSF JARs can be found in the Seam <literal>lib</literal> directory. The el JARs can be obtained from the Seam 1.2 release."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:307
#, no-c-format
-msgid ""
-"You'll also need to edit the <literal>conf/web.xml</literal>, replacing "
-"<literal>myfaces-impl.jar</literal> with <literal>jsf-impl.jar</literal>."
+msgid "You'll also need to edit the <literal>conf/web.xml</literal>, replacing <literal>myfaces-impl.jar</literal> with <literal>jsf-impl.jar</literal>."
msgstr ""
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-13 23:24:40 UTC (rev 9775)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-14 21:16:33 UTC (rev 9776)
@@ -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:38+0000\n"
-"PO-Revision-Date: 2008-12-12 00:17+0100\n"
+"PO-Revision-Date: 2008-12-14 22:11+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -23,7 +23,7 @@
#: Jbpm.xml:4
#, no-c-format
msgid "JBoss jBPM is a business process management engine for any Java SE or EE environment. jBPM lets you represent a business process or user interaction as a graph of nodes representing wait states, decisions, tasks, web pages, etc. The graph is defined using a simple, very readable, XML dialect called jPDL, and may be edited and visualised graphically using an eclipse plugin. jPDL is an extensible language, and is suitable for a range of problems, from defining web application page flow, to traditional workflow management, all the way up to orchestration of services in a SOA environment."
-msgstr ""
+msgstr "JBoss jBPM è un motore di gestione dei processi di business per ambiente Java SE o EE. jBPM ti consente di rappresentare un processo di business o un'interazione utente come un grafo di nodi, raffiguranti stati d'attesa, decisioni, compiti (task), pagine web, ecc. Il grafo viene definito usando un dialetto XML semplice, molto leggibile, chiamato jPDL, che può essere editato e visualizzato graficamente usando un plugin di eclipse. jPDL è un linguaggio estendibile ed è adatto per un range di problemi, dalla definizione di un flusso di pagine dell'applicazione web alla gestione tradizionale del workflow, fino all'orchestrazione di servizi in un ambiente SOA."
#. Tag: para
#: Jbpm.xml:16
@@ -71,7 +71,7 @@
#: Jbpm.xml:67
#, no-c-format
msgid "Using JSF or Seam navigation rules - the <emphasis>stateless navigation model</emphasis>"
-msgstr ""
+msgstr "Uso di JSF o delle regole di navigazione di Seam - il <emphasis>modello di navigazione stateless</emphasis>"
#. Tag: para
#: Jbpm.xml:73
@@ -89,7 +89,7 @@
#: Jbpm.xml:86
#, no-c-format
msgid "The two navigation models"
-msgstr ""
+msgstr "I due modelli di navigazione"
#. Tag: para
#: Jbpm.xml:88
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-13 23:24:40 UTC (rev 9775)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-14 21:16:33 UTC (rev 9776)
@@ -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-14 00:24+0100\n"
+"PO-Revision-Date: 2008-12-14 21:05+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -223,7 +223,7 @@
#: Preface.xml:234
#, no-c-format
msgid "We think the latest incarnation of Java EE is great. But we know it's never going to be perfect. Where there are holes in the specifications (for example, limitations in the JSF lifecycle for GET requests), Seam fixes them. And the authors of Seam are working with the JCP expert groups to make sure those fixes make their way back into the next revision of the standards."
-msgstr "Pensiamo che l'ultima incarnazione di Java EE sia ottima. Ma sappiamo che non sarà mai perfetta. Dove ci sono dei buchi nella specifica) per esempio, limitazioni nel ciclo di vita JSF per le richieste GET), Seam li risolve. E gli autori di Seam stanno lavorando con i gruppi esperti JCP per assicurare che queste soluzioni siano incorporate nelle prossime revisioni degli standard."
+msgstr "Pensiamo che l'ultima incarnazione di Java EE sia ottima. Ma sappiamo che non sarà mai perfetta. Dove ci sono dei buchi nella specifica (per esempio limitazioni nel ciclo di vita JSF per le richieste GET), Seam li risolve. E gli autori di Seam stanno lavorando con i gruppi esperti JCP per assicurare che queste soluzioni siano incorporate nelle prossime revisioni degli standard."
#. Tag: emphasis
#: Preface.xml:245
@@ -253,11 +253,11 @@
#: Preface.xml:270
#, no-c-format
msgid "Seam works in any Java EE application server, and even works in Tomcat. If your environment supports EJB 3.0, great! If it doesn't, no problem, you can use Seam's built-in transaction management with JPA or Hibernate3 for persistence. Or, you can deploy JBoss Embedded in Tomcat, and get full support for EJB 3.0."
-msgstr "Seam funziona in qualsiasi application server Java EE, e perfino in Tomcat. Se il tuo ambiente supporta EJB 3.0, benissimo! Altrimenti, nessun problema, puoi utilizzare la gestione delle transazioni interna di Seam con JPA o Hibernate3 per la persistenza. Oppure puoi fare il deploy di JBoss Embedded in Tomcat, ed ottenere pieno supporto per EJB 3.0."
+msgstr "Seam funziona in qualsiasi application server Java EE, e perfino in Tomcat. Se il tuo ambiente supporta EJB 3.0, benissimo! Altrimenti, nessun problema, puoi utilizzare la gestione delle transazioni interna a Seam con JPA o Hibernate3 per la persistenza. Oppure puoi fare il deploy di JBoss Embedded in Tomcat, ed ottenere pieno supporto per EJB 3.0."
#. Tag: para
#: Preface.xml:286
#, no-c-format
msgid "It turns out that the combination of Seam, JSF and EJB3 is <emphasis>the</emphasis> simplest way to write a complex web application in Java. You won't believe how little code is required!"
-msgstr "Risulta che la combinazione di Seam, JSF e EJB3 è <emphasis>il</emphasis> modo più semplice per scrivere un'applicazione web complessa in Java. Ti stupirai di quanto poco codice viene richiesto!"
+msgstr "La combinazione di Seam, JSF e EJB3 è <emphasis>il</emphasis> modo più semplice per scrivere una complessa applicazione web in Java. Ti stupirai di quanto poco codice viene richiesto!"
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Testing.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Testing.po 2008-12-13 23:24:40 UTC (rev 9775)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Testing.po 2008-12-14 21:16:33 UTC (rev 9776)
@@ -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 20:13+0100\n"
+"PO-Revision-Date: 2008-12-14 21:53+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -23,13 +23,13 @@
#: 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)."
-msgstr ""
+msgstr "La maggior parte delle applicazioni Seam hanno bisogno di almeno due tipi di test automatici: <emphasis>test di unità</emphasis> per testare un particolare componente Seam in isolamento, e <emphasis>test d'integrazione</emphasis> per provare tutti i layer java dell'applicazione (cioè tutto, tranne le pagine di vista)."
#. Tag: para
#: Testing.xml:10
#, no-c-format
msgid "Both kinds of tests are very easy to write."
-msgstr ""
+msgstr "Entrambi i tipi di test sono facili da scrivere."
#. Tag: title
#: Testing.xml:15
@@ -163,7 +163,7 @@
#: Testing.xml:44
#, no-c-format
msgid "However, if you want to test the entire application, read on."
-msgstr ""
+msgstr "Comunque se vuoi testare l'intera applicazione, continua nella lettura."
#. Tag: title
#: Testing.xml:51
@@ -987,5 +987,5 @@
#: 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."
-msgstr ""
+msgstr "Non c'è alcun supporto per il rendering dei componenti JSF standard, così non è possibile testare facilmente il corpo dei messaggi email."
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-13 23:24:40 UTC (rev 9775)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-14 21:16:33 UTC (rev 9776)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-12-13 17:58+0000\n"
-"PO-Revision-Date: 2008-12-14 00:06+0100\n"
+"PO-Revision-Date: 2008-12-14 21:19+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -95,7 +95,7 @@
#: Tutorial.xml:73
#, no-c-format
msgid "The examples are also configured for use on Tomcat 6.0. You will need to follow the instructions in <xref linkend=\"config.install.embedded\"/> for installing JBoss Embedded on Tomcat 6.0. JBoss Embedded is only required to run the Seam demos that use EJB3 components on Tomcat. There are also examples of non-EJB3 applications that can be run on Tomcat without the use of JBoss Embedded."
-msgstr ""
+msgstr "Questi esempi sono configurati anche per essere usati in Tomcat 6.0. Occorreràseguire le istruzioni in <xref linkend=\"config.install.embedded\"/> per installare JBoss Embedded in Tomcat 6.0. JBoss Embedded è richiesto per eseguire le demo di Seam che usano componenti EJB3 in Tomcat. Ci sono anche esempio di applicazioni non-EJB3 che possono funzionare in Tomcat senza JBoss Embedded."
#. Tag: para
#: Tutorial.xml:79
@@ -107,7 +107,7 @@
#: Tutorial.xml:85
#, no-c-format
msgid "You'll need to use a different Ant target when using Tomcat. Use <literal>ant tomcat.deploy</literal> in example subdirectory to build and deploy any example for Tomcat."
-msgstr ""
+msgstr "Dovrai usare un diverso target Ant per utilizzare Tomcat. Usa <literal>ant tomcat.deploy</literal> nella sotto-directory d'esempio per il build ed il deploy in Tomcat."
#. Tag: para
#: Tutorial.xml:90
@@ -143,7 +143,7 @@
#: Tutorial.xml:119
#, no-c-format
msgid "We'll go slowly, since we realize you might not yet be familiar with EJB 3.0."
-msgstr ""
+msgstr "Andiamo piano, poiché ci rendiamo conto che EJB 3.0 potrebbe non esserti familiare."
#. Tag: para
#: Tutorial.xml:121
@@ -4560,13 +4560,13 @@
#: Tutorial.xml:1669
#, no-c-format
msgid "Feel free to deploy the application, open many windows or tabs and attempt combinations of various hotels with various room preferences. Confirming a booking always results in the correct hotel and room preference thanks to the nested conversation model."
-msgstr ""
+msgstr "Prova il deploy dell'applicazione, apri più finestre o tab e prova combinzioni di vari hotel con varie opzioni di camera. La conferma risulterà sempre nel giusto hotel e con la corretta opzione grazie al modello di conversazioni innestate."
#. Tag: title
#: Tutorial.xml:1676
#, no-c-format
msgid "A complete application featuring Seam and jBPM: the DVD Store example"
-msgstr ""
+msgstr "Un'applicazione completa di Seam e jBPM: esempio di Negozio DVD"
#. Tag: para
#: Tutorial.xml:1678
@@ -4761,7 +4761,7 @@
#: Tutorial.xml:1798
#, no-c-format
msgid "Bookmarkable search results page"
-msgstr ""
+msgstr "Pagina bookmarkable dei risultati di ricerca"
#. Tag: para
#: Tutorial.xml:1800
@@ -4897,7 +4897,7 @@
#: Tutorial.xml:1860
#, no-c-format
msgid "The redirect takes us to the <literal>search.xhtml</literal> page:"
-msgstr ""
+msgstr "Il redirect di porta alla pagina <literal>search.xhtml</literal>:"
#. Tag: programlisting
#: Tutorial.xml:1862
@@ -5051,7 +5051,7 @@
#: Tutorial.xml:1874
#, no-c-format
msgid "Using \"push\"-style MVC in a RESTful application"
-msgstr ""
+msgstr "Uso di MVC push in un'applicazione RESTful"
#. Tag: para
#: Tutorial.xml:1876
@@ -5063,7 +5063,7 @@
#: Tutorial.xml:1881
#, no-c-format
msgid "The <literal>entryAction</literal> component works much like an action class in a traditional push-MVC action-oriented framework like Struts:"
-msgstr ""
+msgstr "Il componente <literal>entryAction</literal> funziona come una action class in un framework tradizionale orientato alle azioni e push-MVC come Struts:"
#. Tag: programlisting
#: Tutorial.xml:1884
More information about the seam-commits
mailing list