Author: nico.ben Date: 2008-12-27 08:29:19 -0500 (Sat, 27 Dec 2008) New Revision: 9845 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Getting_Started_With_JBoss_Tools.po trunk/doc/Seam_Reference_Guide/it-IT/Gettingstarted.po trunk/doc/Seam_Reference_Guide/it-IT/Glassfish.po trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po trunk/doc/Seam_Reference_Guide/it-IT/Wicket.po Log: JBSEAM-3767: Italian translation of Seam guide Modified: trunk/doc/Seam_Reference_Guide/it-IT/Getting_Started_With_JBoss_Tools.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Getting_Started_With_JBoss_Tools.po 2008-12-27 11:43:06 UTC (rev 9844) +++ trunk/doc/Seam_Reference_Guide/it-IT/Getting_Started_With_JBoss_Tools.po 2008-12-27 13:29:19 UTC (rev 9845) @@ -6,8 +6,8 @@ "Project-Id-Version: seam 2_0\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2008-05-03 11:34+0000\n" -"PO-Revision-Date: 2008-05-03 11:34+0000\n" -"Last-Translator: Automatically generated\n" +"PO-Revision-Date: 2008-12-27 12:52+0100\n" +"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: none\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -17,17 +17,12 @@ #: Getting_Started_With_JBoss_Tools.xml:5 #, no-c-format msgid "Getting started with Seam, using JBoss Tools" -msgstr "" +msgstr "Iniziare con Seam usando JBoss Tools" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:7 #, no-c-format -msgid "" -"JBoss Tools is a collection of Eclipse plugins. JBoss Tools a project " -"creation wizard for Seam, Content Assist for the Unified Expression Language " -"(EL) in both facelets and Java code, a graphical editor for jPDL, a " -"graphical editor for Seam configuration files, support for running Seam " -"integration tests from within Eclipse, and much more." +msgid "JBoss Tools is a collection of Eclipse plugins. JBoss Tools a project creation wizard for Seam, Content Assist for the Unified Expression Language (EL) in both facelets and Java code, a graphical editor for jPDL, a graphical editor for Seam configuration files, support for running Seam integration tests from within Eclipse, and much more." msgstr "" #. Tag: para @@ -39,26 +34,19 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:19 #, no-c-format -msgid "" -"JBoss Tools, as with seam-gen, works best with JBoss AS, but it's possible " -"with a few tweaks to get your app running on other application servers. The " -"changes are much like those described for seam-gen later in this reference " -"manual." +msgid "JBoss Tools, as with seam-gen, works best with JBoss AS, but it's possible with a few tweaks to get your app running on other application servers. The changes are much like those described for seam-gen later in this reference manual." msgstr "" #. Tag: title #: Getting_Started_With_JBoss_Tools.xml:27 #, no-c-format msgid "Before you start" -msgstr "" +msgstr "Prima di iniziare" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:29 #, no-c-format -msgid "" -"Make sure you have JDK 5, JBoss AS 4.2, Eclipse 3.3, the JBoss Tools plugins " -"(at least Seam Tools, the Visual Page Editor, jBPM Tools and JBoss AS Tools) " -"and the TestNG plugin for Eclipse correctly installed before starting." +msgid "Make sure you have JDK 5, JBoss AS 4.2, Eclipse 3.3, the JBoss Tools plugins (at least Seam Tools, the Visual Page Editor, jBPM Tools and JBoss AS Tools) and the TestNG plugin for Eclipse correctly installed before starting." msgstr "" #. Tag: para @@ -82,26 +70,19 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:47 #, no-c-format -msgid "" -"Go to <emphasis>File</emphasis> -> <emphasis>New</emphasis> -> " -"<emphasis>Seam Web Project</emphasis>." +msgid "Go to <emphasis>File</emphasis> -> <emphasis>New</emphasis> -> <emphasis>Seam Web Project</emphasis>." msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:63 #, no-c-format -msgid "" -"First, enter a name for your new project. For this tutorial, we're going to " -"use <literal>helloworld</literal> ." +msgid "First, enter a name for your new project. For this tutorial, we're going to use <literal>helloworld</literal> ." msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:71 #, no-c-format -msgid "" -"Now, we need to tell JBoss Tools about JBoss AS. This is a two stage " -"process, first we need to define a runtime, make sure you select JBoss AS " -"4.2:" +msgid "Now, we need to tell JBoss Tools about JBoss AS. This is a two stage process, first we need to define a runtime, make sure you select JBoss AS 4.2:" msgstr "" #. Tag: para @@ -113,69 +94,43 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:103 #, no-c-format -msgid "" -"Next, we need to define a server JBoss Tools can deploy the project to. Make " -"sure to again select JBoss AS 4.2, and also the runtime you just defined:" +msgid "Next, we need to define a server JBoss Tools can deploy the project to. Make sure to again select JBoss AS 4.2, and also the runtime you just defined:" msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:118 #, no-c-format -msgid "" -"On the next screen give the server a name, and hit <emphasis>Finish</" -"emphasis>:" +msgid "On the next screen give the server a name, and hit <emphasis>Finish</emphasis>:" msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:134 #, no-c-format -msgid "" -"Make sure the runtime and server you just created are selected, select " -"<emphasis>Dynamic Web Project with Seam 2.0 (technology preview)</emphasis> " -"and hit <emphasis>Next</emphasis>:" +msgid "Make sure the runtime and server you just created are selected, select <emphasis>Dynamic Web Project with Seam 2.0 (technology preview)</emphasis> and hit <emphasis>Next</emphasis>:" msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:151 #, no-c-format -msgid "" -"The next 3 screens allow you to further customize your new project, but for " -"us the defaults are fine. So just hit <empahsis>Next</empahsis> until you " -"reach the final screen." +msgid "The next 3 screens allow you to further customize your new project, but for us the defaults are fine. So just hit <empahsis>Next</empahsis> until you reach the final screen." msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:157 #, no-c-format -msgid "" -"The first step here is to tell JBoss Tools about the Seam download you want " -"to use. <emphasis>Add</emphasis> a new <emphasis>Seam Runtime</emphasis> - " -"make sure to give it a name, and select <emphasis>2.0</emphasis> as the " -"version:" +msgid "The first step here is to tell JBoss Tools about the Seam download you want to use. <emphasis>Add</emphasis> a new <emphasis>Seam Runtime</emphasis> - make sure to give it a name, and select <emphasis>2.0</emphasis> as the version:" msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:175 #, 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 <emphasis>EAR</" -"emphasis>. Otherwise, choose <emphasis>WAR</emphasis>. We'll assume that " -"you've chosen a WAR deployment for the rest of the tutorial, but you can " -"follow exactly the same steps for a EAR 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 <emphasis>EAR</emphasis>. Otherwise, choose <emphasis>WAR</emphasis>. We'll assume that you've chosen a WAR deployment for the rest of the tutorial, but you can follow exactly the same steps for a EAR deployment." msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:187 #, no-c-format -msgid "" -"Next, select your database type. We'll assume you have MySQL installed, with " -"an existing schema. You'll need to tell JBoss Tools about the database, " -"select <emphasis>MySQL</emphasis> as the database, and create a new " -"connection profile. Select <emphasis>Generic JDBC Connection</emphasis>:" +msgid "Next, select your database type. We'll assume you have MySQL installed, with an existing schema. You'll need to tell JBoss Tools about the database, select <emphasis>MySQL</emphasis> as the database, and create a new connection profile. Select <emphasis>Generic JDBC Connection</emphasis>:" msgstr "" #. Tag: para @@ -187,10 +142,7 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:221 #, no-c-format -msgid "" -"JBoss Tools doesn't come with drivers for any databases, so you need to tell " -"JBoss Tools where the MySQL JDBC driver is. Tell it about the driver by " -"clicking <emphasis>...</emphasis>." +msgid "JBoss Tools doesn't come with drivers for any databases, so you need to tell JBoss Tools where the MySQL JDBC driver is. Tell it about the driver by clicking <emphasis>...</emphasis>." msgstr "" #. Tag: para @@ -208,17 +160,13 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:257 #, no-c-format -msgid "" -"Locate the jar on your computer by choosing <emphasis>Edit Jar/Zip</" -"emphasis>:" +msgid "Locate the jar on your computer by choosing <emphasis>Edit Jar/Zip</emphasis>:" msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:273 #, no-c-format -msgid "" -"Review the username and password used to connect, and if correct, hit " -"<emphasis>Ok</emphasis>." +msgid "Review the username and password used to connect, and if correct, hit <emphasis>Ok</emphasis>." msgstr "" #. Tag: para @@ -230,65 +178,49 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:293 #, no-c-format -msgid "" -"If you are working with an existing data model, make sure you tell JBoss " -"Tools that the tables already exist in the database." +msgid "If you are working with an existing data model, make sure you tell JBoss Tools that the tables already exist in the database." msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:298 #, no-c-format -msgid "" -"Review the username and password used to connect, test the connection using " -"the <emphasis>Test Connection</emphasis> button, and if it works, hit " -"<emphasis>Finish</emphasis>:" +msgid "Review the username and password used to connect, test the connection using the <emphasis>Test Connection</emphasis> button, and if it works, hit <emphasis>Finish</emphasis>:" msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:304 #, no-c-format -msgid "" -"Finally, review the package names for your generated beans, and if you are " -"happy, click <emphasis>Finish</emphasis>:" +msgid "Finally, review the package names for your generated beans, and if you are happy, click <emphasis>Finish</emphasis>:" msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:320 #, 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. 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. We suggest the following values:" msgstr "" #. Tag: programlisting #: Getting_Started_With_JBoss_Tools.xml:329 #, no-c-format msgid "-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512" -msgstr "" +msgstr "-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:331 #, 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 #: Getting_Started_With_JBoss_Tools.xml:336 #, no-c-format msgid "-Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256" -msgstr "" +msgstr "-Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:338 #, no-c-format -msgid "" -"Locate the server in the <emphasis>JBoss Server View</emphasis>, right click " -"on the server and select <emphasis>Edit Launch Configuration</emphasis>:" +msgid "Locate the server in the <emphasis>JBoss Server View</emphasis>, right click on the server and select <emphasis>Edit Launch Configuration</emphasis>:" msgstr "" #. Tag: para @@ -300,28 +232,19 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:370 #, 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: para #: Getting_Started_With_JBoss_Tools.xml:376 #, no-c-format -msgid "" -"To start JBoss, and deploy the project, just right click on the server you " -"created, and click <emphasis>Start</emphasis>, (or <emphasis>Debug</" -"emphasis> to start in debug mode):" +msgid "To start JBoss, and deploy the project, just right click on the server you created, and click <emphasis>Start</emphasis>, (or <emphasis>Debug</emphasis> to start in debug mode):" msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:393 #, 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." +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." msgstr "" #. Tag: title @@ -333,26 +256,20 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:405 #, 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." +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." msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:411 #, no-c-format -msgid "" -"First, select <emphasis>New</emphasis> -> <emphasis>Seam Action</emphasis>:" +msgid "First, select <emphasis>New</emphasis> -> <emphasis>Seam Action</emphasis>:" msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:426 #: Getting_Started_With_JBoss_Tools.xml:492 #, no-c-format -msgid "" -"Now, enter the name of the Seam component. JBoss Tools selects sensible " -"defaults for other fields:" +msgid "Now, enter the name of the Seam component. JBoss Tools selects sensible defaults for other fields:" msgstr "" #. Tag: para @@ -364,20 +281,13 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:446 #, 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 #: Getting_Started_With_JBoss_Tools.xml:454 #, no-c-format -msgid "" -"Finally, open the <literal>helloworld-test</literal> project, locate " -"<literal>PingTest</literal> class, right click on it, and choose " -"<emphasis>Run As</emphasis> -> <emphasis>TestNG Test</emphasis>:" +msgid "Finally, open the <literal>helloworld-test</literal> project, locate <literal>PingTest</literal> class, right click on it, and choose <emphasis>Run As</emphasis> -> <emphasis>TestNG Test</emphasis>:" msgstr "" #. Tag: title @@ -389,21 +299,13 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:476 #, no-c-format -msgid "" -"The first step is to create a form. Select <emphasis>New</emphasis> -> " -"<emphasis>Seam Form</emphasis>:" +msgid "The first step is to create a form. Select <emphasis>New</emphasis> -> <emphasis>Seam Form</emphasis>:" msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:508 #, no-c-format -msgid "" -"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 (note, you don't need to restart the app " -"server each time you change the code in <literal>src/action</literal> as " -"Seam hot reloads the component for you <xref linkend=" -"\"gettingstartedwithjbosstools.hotdeployment\"/>)." +msgid "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 (note, you don't need to restart the app server each time you change the code in <literal>src/action</literal> as Seam hot reloads the component for you <xref linkend=\"gettingstartedwithjbosstools.hotdeployment\"/>)." msgstr "" #. Tag: title @@ -415,21 +317,13 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:521 #, no-c-format -msgid "" -"Manually create some tables in your database. (If you need to switch to a " -"different database, create a new project, and select the correct database). " -"Then, select <emphasis>New</emphasis> -> <emphasis>Seam Generate Entities</" -"emphasis>:" +msgid "Manually create some tables in your database. (If you need to switch to a different database, create a new project, and select the correct database). Then, select <emphasis>New</emphasis> -> <emphasis>Seam Generate Entities</emphasis>:" msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:539 #, no-c-format -msgid "" -"JBoss Tools gives you the option to either reverse engineer entities, " -"components and views from a database schema or to reverse engineer " -"components and views from existing JPA entities. We're going to do " -"<emphasis>Reverse engieneer from database</emphasis>." +msgid "JBoss Tools gives you the option to either reverse engineer entities, components and views from a database schema or to reverse engineer components and views from existing JPA entities. We're going to do <emphasis>Reverse engieneer from database</emphasis>." msgstr "" #. Tag: para @@ -441,12 +335,7 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:561 #, no-c-format -msgid "" -"Then 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 reverse engineering." +msgid "Then 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 reverse engineering." msgstr "" #. Tag: title @@ -482,20 +371,13 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:594 #, no-c-format -msgid "" -"But if we want to change any Java code, we still need to do a full restart " -"of the application by doing a <emphasis>Full Publish</emphasis>." +msgid "But if we want to change any Java code, we still need to do a full restart of the application by doing a <emphasis>Full Publish</emphasis>." msgstr "" #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:600 #, 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 @@ -507,9 +389,7 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:613 #, 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 @@ -521,25 +401,19 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:626 #, 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 #: Getting_Started_With_JBoss_Tools.xml:633 #, 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 #: Getting_Started_With_JBoss_Tools.xml:640 #, 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 @@ -551,17 +425,12 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:654 #, 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 #: Getting_Started_With_JBoss_Tools.xml:662 #, no-c-format -msgid "" -"If you create a WAR project using JBoss Tools, incremental hot deployment is " -"available out of the box for classes in the <literal>src/action</literal> " -"source directory. However, JBoss Tools does not support incremental hot " -"deployment for EAR projects." +msgid "If you create a WAR project using JBoss Tools, incremental hot deployment is available out of the box for classes in the <literal>src/action</literal> source directory. However, JBoss Tools does not support incremental hot deployment for EAR projects." msgstr "" + Modified: trunk/doc/Seam_Reference_Guide/it-IT/Gettingstarted.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Gettingstarted.po 2008-12-27 11:43:06 UTC (rev 9844) +++ trunk/doc/Seam_Reference_Guide/it-IT/Gettingstarted.po 2008-12-27 13:29:19 UTC (rev 9845) @@ -6,7 +6,7 @@ "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-12-14 19:09+0100\n" +"PO-Revision-Date: 2008-12-27 12:51+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -71,7 +71,7 @@ #: Gettingstarted.xml:39 #, no-c-format msgid "-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m" -msgstr "" +msgstr "-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m" #. Tag: para #: Gettingstarted.xml:41 @@ -83,7 +83,7 @@ #: Gettingstarted.xml:43 #, no-c-format msgid "-Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256m" -msgstr "" +msgstr "-Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256m" #. Tag: para #: Gettingstarted.xml:45 @@ -116,6 +116,8 @@ "cd jboss-seam-2.0.x\n" "seam setup" msgstr "" +"cd jboss-seam-2.0.x\n" +"seam setup" #. Tag: para #: Gettingstarted.xml:60 @@ -182,6 +184,60 @@ "Total time: 1 minute 32 seconds\n" "~/workspace/jboss-seam $" msgstr "" +"~/workspace/jboss-seam$ ./seam setup\n" +"Buildfile: build.xml\n" +"\n" +"init:\n" +"\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" +"/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" +"/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" +"\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" +"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" +"\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" +"\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" +"\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" +"\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" +"n\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" +" [echo] Installing JDBC driver jar to JBoss server\n" +" [echo] Type 'seam create-project' to create the new project\n" +"\n" +"BUILD SUCCESSFUL\n" +"Total time: 1 minute 32 seconds\n" +"~/workspace/jboss-seam $" #. Tag: para #: Gettingstarted.xml:64 @@ -217,7 +273,7 @@ #: Gettingstarted.xml:81 #, no-c-format msgid "seam new-project" -msgstr "" +msgstr "seam new-project" #. Tag: programlisting #: Gettingstarted.xml:83 @@ -238,6 +294,20 @@ "Total time: 7 seconds\n" "C:\\Projects\\jboss-seam&gt;" msgstr "" +"C:\\Projects\\jboss-seam&gt;seam new-project\n" +"Buildfile: build.xml\n" +"\n" +"...\n" +"\n" +"new-project:\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 &gt; New &gt; Project and select General &gt; Project (not Java Project)\n" +" [echo] NetBeans Users: Open the project in NetBeans\n" +"\n" +"BUILD SUCCESSFUL\n" +"Total time: 7 seconds\n" +"C:\\Projects\\jboss-seam&gt;" #. Tag: para #: Gettingstarted.xml:85 @@ -291,7 +361,7 @@ #: Gettingstarted.xml:126 #, no-c-format msgid "seam new-action" -msgstr "" +msgstr "seam new-action" #. Tag: para #: Gettingstarted.xml:128 @@ -337,6 +407,39 @@ "Total time: 13 seconds\n" "C:\\Projects\\jboss-seam&gt;" msgstr "" +"C:\\Projects\\jboss-seam&gt;seam new-action\n" +"Buildfile: build.xml\n" +"\n" +"validate-workspace:\n" +"\n" +"validate-project:\n" +"\n" +"action-input:\n" +" [input] Enter the Seam component name\n" +"ping\n" +" [input] Enter the local interface name [Ping]\n" +"\n" +" [input] Enter the bean class name [PingBean]\n" +"\n" +" [input] Enter the action method name [ping]\n" +"\n" +" [input] Enter the page name [ping]\n" +"\n" +"\n" +"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" +" [copy] Copying 1 file to C:\\Projects\\helloworld\\view\n" +" [echo] Type 'seam restart' and go to http://localhost:8080/helloworld/ping.seam\n" +"\n" +"BUILD SUCCESSFUL\n" +"Total time: 13 seconds\n" +"C:\\Projects\\jboss-seam&gt;" #. Tag: para #: Gettingstarted.xml:133 @@ -372,7 +475,7 @@ #: Gettingstarted.xml:153 #, no-c-format msgid "seam new-form" -msgstr "" +msgstr "seam new-form" #. Tag: programlisting #: Gettingstarted.xml:155 @@ -412,6 +515,39 @@ "Total time: 5 seconds\n" "C:\\Projects\\jboss-seam&gt;" msgstr "" +"C:\\Projects\\jboss-seam&gt;seam new-form\n" +"Buildfile: C:\\Projects\\jboss-seam\\seam-gen\\build.xml\n" +"\n" +"validate-workspace:\n" +"\n" +"validate-project:\n" +"\n" +"action-input:\n" +" [input] Enter the Seam component name\n" +"hello\n" +" [input] Enter the local interface name [Hello]\n" +"\n" +" [input] Enter the bean class name [HelloBean]\n" +"\n" +" [input] Enter the action method name [hello]\n" +"\n" +" [input] Enter the page name [hello]\n" +"\n" +"\n" +"setup-filters:\n" +"\n" +"new-form:\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\\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" +"\n" +"BUILD SUCCESSFUL\n" +"Total time: 5 seconds\n" +"C:\\Projects\\jboss-seam&gt;" #. Tag: para #: Gettingstarted.xml:157 @@ -435,7 +571,7 @@ #: Gettingstarted.xml:168 #, no-c-format msgid "seam generate-entities" -msgstr "" +msgstr "seam generate-entities" #. Tag: para #: Gettingstarted.xml:170 @@ -459,7 +595,7 @@ #: Gettingstarted.xml:181 #, no-c-format msgid "seam generate-ui" -msgstr "" +msgstr "seam generate-ui" #. Tag: para #: Gettingstarted.xml:183 @@ -489,7 +625,7 @@ #: Gettingstarted.xml:200 #, no-c-format msgid "seam -Dprofile=prod deploy" -msgstr "" +msgstr "seam -Dprofile=prod deploy" #. Tag: para #: Gettingstarted.xml:202 @@ -513,7 +649,7 @@ #: Gettingstarted.xml:215 #, no-c-format msgid "<![CDATA[<core:init debug=\"true\">]]>" -msgstr "" +msgstr "<![CDATA[<core:init debug=\"true\">]]>" #. Tag: para #: Gettingstarted.xml:217 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Glassfish.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Glassfish.po 2008-12-27 11:43:06 UTC (rev 9844) +++ trunk/doc/Seam_Reference_Guide/it-IT/Glassfish.po 2008-12-27 13:29:19 UTC (rev 9845) @@ -3,11 +3,11 @@ # msgid "" msgstr "" -"Project-Id-Version: Seam_Reference_Guide \n" +"Project-Id-Version: Seam_Reference_Guide\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:58+0000\n" -"PO-Revision-Date: 2008-10-14 11:38+0000\n" -"Last-Translator: Automatically generated\n" +"POT-Creation-Date: 2008-12-27 11:29+0000\n" +"PO-Revision-Date: 2008-12-27 12:50+0100\n" +"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: none\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -22,19 +22,13 @@ #. Tag: para #: Glassfish.xml:5 #, no-c-format -msgid "" -"GlassFish is an open source application server which fully implements Java " -"EE 5. The latest stable release is v2 UR2." +msgid "GlassFish is an open source application server which fully implements Java EE 5. The latest stable release is v2 UR2." msgstr "" #. Tag: para #: Glassfish.xml:10 #, no-c-format -msgid "" -"First, we'll discuss the GlassFish environment. Then we will go over the how " -"you deploy the jee5 example. Next, we will deploy the JPA example " -"application. Finally we show how to get a seam-gen's generated application " -"running on GlassFish." +msgid "First, we'll discuss the GlassFish environment. Then we will go over the how you deploy the jee5 example. Next, we will deploy the JPA example application. Finally we show how to get a seam-gen's generated application running on GlassFish." msgstr "" #. Tag: title @@ -47,14 +41,12 @@ #: Glassfish.xml:21 #, no-c-format msgid "Installation" -msgstr "" +msgstr "Installazione" #. Tag: para #: Glassfish.xml:23 #, no-c-format -msgid "" -"All of the examples and information in this chapter are based on the the " -"latest version of GlassFish at the time of this writing." +msgid "All of the examples and information in this chapter are based on the the latest version of GlassFish at the time of this writing." msgstr "" #. Tag: ulink @@ -73,7 +65,7 @@ #: Glassfish.xml:41 #, no-c-format msgid "$ java -Xmx256m -jar glassfish-installer-v2ur2-b04-linux.jar" -msgstr "" +msgstr "$ java -Xmx256m -jar glassfish-installer-v2ur2-b04-linux.jar" #. Tag: para #: Glassfish.xml:43 @@ -85,7 +77,7 @@ #: Glassfish.xml:47 #, no-c-format msgid "$ cd glassfish; ant -f setup.xml" -msgstr "" +msgstr "$ cd glassfish; ant -f setup.xml" #. Tag: para #: Glassfish.xml:49 @@ -103,14 +95,12 @@ #: Glassfish.xml:57 #, no-c-format msgid "$ bin/asadmin start-database" -msgstr "" +msgstr "$ bin/asadmin start-database" #. Tag: para #: Glassfish.xml:60 #, no-c-format -msgid "" -"JavaDB is an embedded database that is included with GlassFish, just as " -"HSQLDB is included in JBoss AS." +msgid "JavaDB is an embedded database that is included with GlassFish, just as HSQLDB is included in JBoss AS." msgstr "" #. Tag: para @@ -123,19 +113,12 @@ #: Glassfish.xml:70 #, no-c-format msgid "$ bin/asadmin start-domain domain1" -msgstr "" +msgstr "$ bin/asadmin start-domain domain1" #. Tag: para #: Glassfish.xml:72 #, no-c-format -msgid "" -"The web administration console is available at <literal>http://" -"localhost:4848/</literal>. You can access the web admin console with the " -"default username (<literal>admin</literal>) and password " -"(<literal>adminadmin</literal>). We will be using the the admin console to " -"deploy our examples. You can also copy EAR/WAR files to the " -"<literal>glassfish/domains/domain1/autodeploy</literal> directory to deploy " -"them, although we are not going to cover that." +msgid "The web administration console is available at <literal>http://localhost:4848/</literal>. You can access the web admin console with the default username (<literal>admin</literal>) and password (<literal>adminadmin</literal>). We will be using the the admin console to deploy our examples. You can also copy EAR/WAR files to the <literal>glassfish/domains/domain1/autodeploy</literal> directory to deploy them, although we are not going to cover that." msgstr "" #. Tag: para @@ -148,7 +131,7 @@ #: Glassfish.xml:86 #, no-c-format msgid "$ bin/asadmin stop-domain domain1; bin/asadmin stop-database" -msgstr "" +msgstr "$ bin/asadmin stop-domain domain1; bin/asadmin stop-database" #. Tag: title #: Glassfish.xml:91 @@ -159,11 +142,7 @@ #. Tag: para #: Glassfish.xml:93 #, no-c-format -msgid "" -"The <literal>jee5/booking</literal> example is based on the Hotel Booking " -"example (which runs on JBoss AS). Out of the box it is also designed to run " -"on GlassFish. It is located in <literal>$SEAM_DIST/examples/jee5/booking</" -"literal>." +msgid "The <literal>jee5/booking</literal> example is based on the Hotel Booking example (which runs on JBoss AS). Out of the box it is also designed to run on GlassFish. It is located in <literal>$SEAM_DIST/examples/jee5/booking</literal>." msgstr "" #. Tag: title @@ -175,24 +154,19 @@ #. Tag: para #: Glassfish.xml:103 #, no-c-format -msgid "" -"To build the example, simply execute the default <literal>ant</literal> " -"target:" +msgid "To build the example, simply execute the default <literal>ant</literal> target:" msgstr "" #. Tag: programlisting #: Glassfish.xml:108 #, no-c-format msgid "$ ant" -msgstr "" +msgstr "$ ant" #. Tag: para #: Glassfish.xml:110 #, no-c-format -msgid "" -"in the <literal>examples/jee5/booking</literal> directory. This will create " -"the <literal>dist</literal> and <literal>exploded-archives</literal> " -"directories." +msgid "in the <literal>examples/jee5/booking</literal> directory. This will create the <literal>dist</literal> and <literal>exploded-archives</literal> directories." msgstr "" #. Tag: title @@ -204,9 +178,7 @@ #. Tag: para #: Glassfish.xml:119 #, no-c-format -msgid "" -"We will deploy the application on GlassFish using the GlassFish admin " -"console." +msgid "We will deploy the application on GlassFish using the GlassFish admin console." msgstr "" #. Tag: para @@ -218,21 +190,18 @@ #. Tag: para #: Glassfish.xml:131 #, no-c-format -msgid "" -"Access the <literal>Enterprise Applications</literal> in the menu option " -"under the <literal>Applications</literal> left side menu." +msgid "Access the <literal>Enterprise Applications</literal> in the menu option under the <literal>Applications</literal> left side menu." msgstr "" #. Tag: para #: Glassfish.xml:138 #, no-c-format -msgid "" -"At the top of the <literal>Enterprise Application</literal> table select " -"<literal>Deploy</literal>. Follow through the wizard, using these hints:" +msgid "At the top of the <literal>Enterprise Application</literal> table select <literal>Deploy</literal>. Follow through the wizard, using these hints:" msgstr "" #. Tag: literal -#: Glassfish.xml:146 Glassfish.xml:227 +#: Glassfish.xml:146 +#: Glassfish.xml:227 #, no-c-format msgid "Preparing for the application installation" msgstr "" @@ -240,12 +209,12 @@ #. Tag: para #: Glassfish.xml:150 #, no-c-format -msgid "" -"Browse to <literal>examples/jee5/booking/dist/jboss-seam-jee5.ear</literal>." +msgid "Browse to <literal>examples/jee5/booking/dist/jboss-seam-jee5.ear</literal>." msgstr "" #. Tag: para -#: Glassfish.xml:155 Glassfish.xml:238 +#: Glassfish.xml:155 +#: Glassfish.xml:238 #, no-c-format msgid "Select the <literal>OK</literal> button." msgstr "" @@ -253,9 +222,7 @@ #. Tag: para #: Glassfish.xml:164 #, no-c-format -msgid "" -"You can now access the application at <literal>http://localhost:8081/seam-" -"jee5/</literal>." +msgid "You can now access the application at <literal>http://localhost:8081/seam-jee5/</literal>." msgstr "" #. Tag: title @@ -267,18 +234,13 @@ #. Tag: para #: Glassfish.xml:176 #, no-c-format -msgid "" -"This is the Hotel Booking example implemented in Seam POJOs and using " -"Hibernate JPA with JPA transactions. It does not require EJB3 support to run " -"on application server." +msgid "This is the Hotel Booking example implemented in Seam POJOs and using Hibernate JPA with JPA transactions. It does not require EJB3 support to run on application server." msgstr "" #. Tag: para #: Glassfish.xml:182 #, no-c-format -msgid "" -"The example already has a break-out of configurations and build scripts for " -"many of the common containers including GlassFish." +msgid "The example already has a break-out of configurations and build scripts for many of the common containers including GlassFish." msgstr "" #. Tag: title @@ -297,14 +259,12 @@ #: Glassfish.xml:194 #, no-c-format msgid "$ ant glassfish" -msgstr "" +msgstr "$ ant glassfish" #. Tag: para #: Glassfish.xml:196 #, no-c-format -msgid "" -"This will create the container specific <literal>dist-glassfish</literal> " -"and <literal>exploded-archives-glasfish</literal> directories." +msgid "This will create the container specific <literal>dist-glassfish</literal> and <literal>exploded-archives-glasfish</literal> directories." msgstr "" #. Tag: title @@ -316,10 +276,7 @@ #. Tag: para #: Glassfish.xml:205 #, no-c-format -msgid "" -"This is very similar to the <literal>jee5</literal> example at <xref linkend=" -"\"jee5-glassfish-deploy\"/> except that this is a <literal>war</literal> and " -"not an <literal>ear</literal>." +msgid "This is very similar to the <literal>jee5</literal> example at <xref linkend=\"jee5-glassfish-deploy\"/> except that this is a <literal>war</literal> and not an <literal>ear</literal>." msgstr "" #. Tag: para @@ -332,29 +289,24 @@ #: Glassfish.xml:216 #, no-c-format msgid "http://localhost:4848" -msgstr "" +msgstr "http://localhost:4848" #. Tag: para #: Glassfish.xml:219 #, no-c-format -msgid "" -"Access the <literal>Web Applications</literal> in the menu option under the " -"<literal>Applications</literal> left side menu." +msgid "Access the <literal>Web Applications</literal> in the menu option under the <literal>Applications</literal> left side menu." msgstr "" #. Tag: para #: Glassfish.xml:233 #, no-c-format -msgid "" -"Browse to <literal>examples/jpa/dist-glassfish/jboss-seam-jpa.war</literal>." +msgid "Browse to <literal>examples/jpa/dist-glassfish/jboss-seam-jpa.war</literal>." msgstr "" #. Tag: para #: Glassfish.xml:245 #, no-c-format -msgid "" -"You can now access the application at <literal>http://localhost:8081/jboss-" -"seam-jpa/</literal>." +msgid "You can now access the application at <literal>http://localhost:8081/jboss-seam-jpa/</literal>." msgstr "" #. Tag: title @@ -366,13 +318,7 @@ #. Tag: note #: Glassfish.xml:255 #, no-c-format -msgid "" -"In order for the app to work out of the box with GlassFish, we have used the " -"Derby (aka JavaDB) database in GlassFish. However, we strongly recommend " -"that you use another database (e.g. HSQL). <literal>examples/jpa/resources-" -"glassfish/WEB-INF/classes/GlassFishDerbyDialect.class</literal> is a hack to " -"get around a Derby bug in GlassFish server. You must use it as your " -"Hibernate dialect if you use Derby with GlassFish." +msgid "In order for the app to work out of the box with GlassFish, we have used the Derby (aka JavaDB) database in GlassFish. However, we strongly recommend that you use another database (e.g. HSQL). <literal>examples/jpa/resources-glassfish/WEB-INF/classes/GlassfishDerbyDialect.class</literal> is a hack to get around a Derby bug in GlassFish server. You must use it as your Hibernate dialect if you use Derby with GlassFish." msgstr "" #. Tag: title @@ -390,48 +336,31 @@ #. Tag: para #: Glassfish.xml:276 #, no-c-format -msgid "" -"<literal>META-INF/persistence.xml</literal> — the main changes needed are " -"the datasource JNDI, switching to the GlassFish transaction manager lookup " -"class, and changing the hibernate dialect to be " -"<literal>GlassFishDerbyDialect</literal>." +msgid "<literal>META-INF/persistence.xml</literal> — the main changes needed are the datasource JNDI, switching to the GlassFish transaction manager lookup class, and changing the hibernate dialect to be <literal>GlassfishDerbyDialect</literal>." msgstr "" #. Tag: para #: Glassfish.xml:285 #, no-c-format -msgid "" -"<literal>WEB-INF/classes/GlassFishDerbyDialect.class</literal> — this class " -"is needed for the Hibernate dialect change to " -"<literal>GlassFishDerbyDialect</literal>" +msgid "<literal>WEB-INF/classes/GlassfishDerbyDialect.class</literal> — this class is needed for the Hibernate dialect change to <literal>GlassfishDerbyDialect</literal>" msgstr "" #. Tag: para #: Glassfish.xml:292 #, no-c-format -msgid "" -"<literal>import.sql</literal> — either for the dialect or Derby DB the " -"<literal>ID</literal> column can not be populated by this file and was " -"removed." +msgid "<literal>import.sql</literal> — either for the dialect or Derby DB the <literal>ID</literal> column can not be populated by this file and was removed." msgstr "" #. Tag: title #: Glassfish.xml:305 #, no-c-format -msgid "" -"Deploying an application generated by <literal>seam-gen</literal> on " -"GlassFish v2 UR2" +msgid "Deploying an application generated by <literal>seam-gen</literal> on GlassFish v2 UR2" msgstr "" #. Tag: para #: Glassfish.xml:307 #, no-c-format -msgid "" -"<literal>seam-gen</literal> is a very useful tool for developers to quickly " -"get an application up and running, and provides a foundation to add your own " -"functionality. Out of box <literal>seam-gen</literal> will produce " -"applications configured to run on JBoss AS. These instructions will show the " -"steps needed to get it to run on GlassFish." +msgid "<literal>seam-gen</literal> is a very useful tool for developers to quickly get an application up and running, and provides a foundation to add your own functionality. Out of box <literal>seam-gen</literal> will produce applications configured to run on JBoss AS. These instructions will show the steps needed to get it to run on GlassFish." msgstr "" #. Tag: title @@ -443,11 +372,7 @@ #. Tag: para #: Glassfish.xml:318 #, no-c-format -msgid "" -"The first step is setting up <literal>seam-gen</literal> to construct the " -"base project. There are several choices made below, specifically the " -"datasource and hibernate values that we will adjust once the project is " -"created." +msgid "The first step is setting up <literal>seam-gen</literal> to construct the base project. There are several choices made below, specifically the datasource and hibernate values that we will adjust once the project is created." msgstr "" #. Tag: programlisting @@ -533,14 +458,89 @@ "BUILD SUCCESSFUL\n" "Total time: 4 minutes 5 seconds]]>" msgstr "" +"<![CDATA[$ ./seam setup\n" +"Buildfile: build.xml\n" +"\n" +"init:\n" +"\n" +"setup:\n" +"[echo] Welcome to seam-gen :-)\n" +"[input] Enter your Java project workspace (the directory that contains your\n" +"Seam projects) [C:/Projects] [C:/Projects]\n" +"/projects\n" +"[input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.3.GA]\n" +"[C:/Program Files/jboss-4.2.3.GA]\n" +"\n" +"[input] Enter the project name [myproject] [myproject]\n" +"seamgen_example\n" +"[echo] Accepted project name as: seamgen_example\n" +"[input] Do you want to use ICEfaces instead of RichFaces [n] (y, [n])\n" +"\n" +"[input] skipping input as property icefaces.home.new has already\n" +"been set.\n" +"[input] Select a RichFaces skin [blueSky] ([blueSky], classic, ruby, wine,\n" +"deepMarine, emeraldTown, japanCherry, DEFAULT)\n" +"\n" +"[input] Is this project deployed as an EAR (with EJB components) or a WAR\n" +"(with no EJB support) [ear] ([ear], war)\n" +"\n" +"[input] Enter the Java package name for your session beans\n" +"[com.mydomain.seamgen_example] [com.mydomain.seamgen_example]\n" +"org.jboss.seam.tutorial.glassfish.action\n" +"[input] Enter the Java package name for your entity beans\n" +"[org.jboss.seam.tutorial.glassfish.action]\n" +"[org.jboss.seam.tutorial.glassfish.action]\n" +"org.jboss.seam.tutorial.glassfish.model\n" +"[input] Enter the Java package name for your test cases\n" +"[org.jboss.seam.tutorial.glassfish.action.test]\n" +"[org.jboss.seam.tutorial.glassfish.action.test]\n" +"org.jboss.seam.tutorial.glassfish.test\n" +"[input] What kind of database are you using? [hsql] ([hsql], mysql, oracle,\n" +"postgres, mssql, db2, sybase, enterprisedb, h2)\n" +"\n" +"[input] Enter the Hibernate dialect for your database\n" +"[org.hibernate.dialect.HSQLDialect]\n" +"[org.hibernate.dialect.HSQLDialect]\n" +"\n" +"[input] Enter the filesystem path to the JDBC driver jar\n" +"[/tmp/seam/lib/hsqldb.jar] [/tmp/seam/lib/hsqldb.jar]\n" +"\n" +"[input] Enter JDBC driver class for your database [org.hsqldb.jdbcDriver]\n" +"[org.hsqldb.jdbcDriver]\n" +"\n" +"[input] Enter the JDBC URL for your database [jdbc:hsqldb:.]\n" +"[jdbc:hsqldb:.]\n" +"\n" +"[input] Enter database username [sa] [sa]\n" +"\n" +"[input] Enter database password [] []\n" +"\n" +"[input] Enter the database schema name (it is OK to leave this blank) [] []\n" +"\n" +"[input] Enter the database catalog name (it is OK to leave this\n" +"blank) [] []\n" +"\n" +"[input] Are you working with tables that already exist in the database? [n]\n" +"(y, [n])\n" +"\n" +"[input] Do you want to drop and recreate the database tables and data in\n" +"import.sql each time you deploy? [n] (y, [n])\n" +"\n" +"[propertyfile] Creating new property file:\n" +"/home/mnovotny/workspaces/jboss/jboss-seam/seam-gen/build.properties\n" +"[echo] Installing JDBC driver jar to JBoss server\n" +"[copy] Copying 1 file to\n" +"/home/mnovotny/workspaces/jboss/jboss-seam/seam-gen/C:/Program\n" +"Files/jboss-4.2.3.GA/server/default/lib\n" +"[echo] Type 'seam create-project' to create the new project\n" +"\n" +"BUILD SUCCESSFUL\n" +"Total time: 4 minutes 5 seconds]]>" #. Tag: para #: Glassfish.xml:327 #, no-c-format -msgid "" -"Type <literal>$ ./seam new-project</literal> to create your project and then " -"<literal>cd /projects/seamgen_example</literal> to the newly created " -"structure." +msgid "Type <literal>$ ./seam new-project</literal> to create your project and then <literal>cd /projects/seamgen_example</literal> to the newly created structure." msgstr "" #. Tag: title @@ -565,60 +565,54 @@ #: Glassfish.xml:347 #, no-c-format msgid "resources/META-INF/persistence-dev.xml" -msgstr "" +msgstr "resources/META-INF/persistence-dev.xml" #. Tag: para #: Glassfish.xml:353 #, no-c-format -msgid "" -"Alter the <literal>jta-data-source</literal> to be <literal>jdbc/__default</" -"literal>. We are going to be using the integrated GlassFish Derby DB." +msgid "Alter the <literal>jta-data-source</literal> to be <literal>jdbc/__default</literal>. We are going to be using the integrated GlassFish Derby DB." msgstr "" #. Tag: para #: Glassfish.xml:360 #, no-c-format -msgid "" -"Replace all of the properties with the following. The key differences are " -"briefly described in <xref linkend=\"glassfish_jpa_diff\"/>:" +msgid "Replace all of the properties with the following. The key differences are briefly described in <xref linkend=\"glassfish_jpa_diff\"/>:" msgstr "" #. Tag: programlisting #: Glassfish.xml:365 #, no-c-format msgid "" -"<![CDATA[<property name=\"hibernate.dialect\" value=\"GlassFishDerbyDialect" -"\"/>\n" +"<![CDATA[<property name=\"hibernate.dialect\" value=\"GlassfishDerbyDialect\"/>\n" "<property name=\"hibernate.hbm2ddl.auto\" value=\"update\"/>\n" "<property name=\"hibernate.show_sql\" value=\"true\"/>\n" "<property name=\"hibernate.format_sql\" value=\"true\"/>\n" -"<property name=\"hibernate.cache.provider_class\" value=\"org.hibernate." -"cache.HashtableCacheProvider\"/>\n" -"<property name=\"hibernate.transaction.manager_lookup_class\" value=\"org." -"hibernate.transaction.SunONETransactionManagerLookup\"/>]]>" +"<property name=\"hibernate.cache.provider_class\" value=\"org.hibernate.cache.HashtableCacheProvider\"/>\n" +"<property name=\"hibernate.transaction.manager_lookup_class\" value=\"org.hibernate.transaction.SunONETransactionManagerLookup\"/>]]>" msgstr "" +"<![CDATA[<property name=\"hibernate.dialect\" value=\"GlassfishDerbyDialect\"/>\n" +"<property name=\"hibernate.hbm2ddl.auto\" value=\"update\"/>\n" +"<property name=\"hibernate.show_sql\" value=\"true\"/>\n" +"<property name=\"hibernate.format_sql\" value=\"true\"/>\n" +"<property name=\"hibernate.cache.provider_class\" value=\"org.hibernate.cache.HashtableCacheProvider\"/>\n" +"<property name=\"hibernate.transaction.manager_lookup_class\" value=\"org.hibernate.transaction.SunONETransactionManagerLookup\"/>]]>" #. Tag: para #: Glassfish.xml:368 #, no-c-format -msgid "" -"You'll need to alter <literal>persistence-prod.xml</literal> as well if you " -"want to deploy to GlassFish using the prod profile." +msgid "You'll need to alter <literal>persistence-prod.xml</literal> as well if you want to deploy to GlassFish using the prod profile." msgstr "" #. Tag: literal #: Glassfish.xml:380 #, no-c-format -msgid "resources/GlassFishDerbyDialect.class" -msgstr "" +msgid "resources/GlassfishDerbyDialect.class" +msgstr "resources/GlassfishDerbyDialect.class" #. Tag: para #: Glassfish.xml:383 #, no-c-format -msgid "" -"As with other examples we need to include this class for DB support. It can " -"be copied from the <literal>jpa</literal> example into the " -"<literal>seamgen_example/resources</literal> directory." +msgid "As with other examples we need to include this class for DB support. It can be copied from the <literal>jpa</literal> example into the <literal>seamgen_example/resources</literal> directory." msgstr "" #. Tag: programlisting @@ -626,79 +620,65 @@ #, no-c-format msgid "" "$ cp \\ \n" -"$SEAM_DIST/examples/jpa/resources-glassfish/WEB-INF/classes/" -"GlassFishDerbyDialect.class \\ \n" +"$SEAM_DIST/examples/jpa/resources-glassfish/WEB-INF/classes/GlassfishDerbyDialect.class \\ \n" "./resources" msgstr "" +"$ cp \\ \n" +"$SEAM_DIST/examples/jpa/resources-glassfish/WEB-INF/classes/GlassfishDerbyDialect.class \\ \n" +"./resources" #. Tag: literal #: Glassfish.xml:394 #, no-c-format msgid "resources/META-INF/jboss-app.xml" -msgstr "" +msgstr "resources/META-INF/jboss-app.xml" #. Tag: para #: Glassfish.xml:397 #, no-c-format -msgid "" -"You can delete this file as we aren't deploying to JBoss AS (<literal>jboss-" -"app.xml</literal> is used to enable classloading isolation in JBoss AS)" +msgid "You can delete this file as we aren't deploying to JBoss AS (<literal>jboss-app.xml</literal> is used to enable classloading isolation in JBoss AS)" msgstr "" #. Tag: literal #: Glassfish.xml:406 #, no-c-format msgid "resources/*-ds.xml" -msgstr "" +msgstr "resources/*-ds.xml" #. Tag: para #: Glassfish.xml:409 #, no-c-format -msgid "" -"You can delete these file as we aren't deploying to JBoss AS (these files " -"define data sources in JBoss AS, we are using GlassFish's default data " -"source)" +msgid "You can delete these file as we aren't deploying to JBoss AS (these files define data sources in JBoss AS, we are using GlassFish's default data source)" msgstr "" #. Tag: literal #: Glassfish.xml:418 #, no-c-format msgid "resources/WEB-INF/components.xml" -msgstr "" +msgstr "resources/WEB-INF/components.xml" #. Tag: para #: Glassfish.xml:423 #, no-c-format -msgid "" -"Enable container managed transaction integration - add the <literal><![CDATA" -"[<transaction:ejb-transaction/>]]></literal> component, and it's namespace " -"declaration <literal>xmlns:transaction=\"http://jboss.com/products/seam/" -"transaction\"</literal>" +msgid "Enable container managed transaction integration - add the <literal><![CDATA[<transaction:ejb-transaction/>]]></literal> component, and it's namespace declaration <literal>xmlns:transaction=\"http://jboss.com/products/seam/transa... msgstr "" #. Tag: para #: Glassfish.xml:431 #, no-c-format -msgid "" -"Alter the <literal>jndi-pattern</literal> to <literal>java:comp/env/" -"seamgen_example/#{ejbName}</literal>" +msgid "Alter the <literal>jndi-pattern</literal> to <literal>java:comp/env/seamgen_example/#{ejbName}</literal>" msgstr "" #. Tag: literal #: Glassfish.xml:441 #, no-c-format msgid "resources/WEB-INF/web.xml" -msgstr "" +msgstr "resources/WEB-INF/web.xml" #. Tag: para #: Glassfish.xml:444 #, no-c-format -msgid "" -"As with the <literal>jee5/booking</literal> example, we need to add EJB " -"references to web.xml. Technically, the reference type is not required, but " -"we add it here for good measure. Note that these references require the " -"presence of an empty <literal>local-home</literal> element to retain " -"compatibility with a JBoss AS 4.x deployment." +msgid "As with the <literal>jee5/booking</literal> example, we need to add EJB references to web.xml. Technically, the reference type is not required, but we add it here for good measure. Note that these references require the presence of an empty <literal>local-home</literal> element to retain compatibility with a JBoss AS 4.x deployment." msgstr "" #. Tag: programlisting @@ -706,8 +686,7 @@ #, no-c-format msgid "" "<![CDATA[<ejb-local-ref> \n" -" <ejb-ref-name>seamgen_example/AuthenticatorAction</ejb-ref-" -"name> \n" +" <ejb-ref-name>seamgen_example/AuthenticatorAction</ejb-ref-name> \n" " <ejb-ref-type>Session</ejb-ref-type> \n" " <local-home/>\n" " <local>org.jboss.seam.tutorial.glassfish.action.Authenticator</local> \n" @@ -720,17 +699,24 @@ " <local>org.jboss.seam.transaction.LocalEjbSynchronizations</local>\n" " </ejb-local-ref>]]>" msgstr "" +"<![CDATA[<ejb-local-ref> \n" +" <ejb-ref-name>seamgen_example/AuthenticatorAction</ejb-ref-name> \n" +" <ejb-ref-type>Session</ejb-ref-type> \n" +" <local-home/>\n" +" <local>org.jboss.seam.tutorial.glassfish.action.Authenticator</local> \n" +" </ejb-local-ref>\n" +" \n" +" <ejb-local-ref>\n" +" <ejb-ref-name>seamgen_example/EjbSynchronizations</ejb-ref-name> \n" +" <ejb-ref-type>Session</ejb-ref-type>\n" +" <local-home/>\n" +" <local>org.jboss.seam.transaction.LocalEjbSynchronizations</local>\n" +" </ejb-local-ref>]]>" #. Tag: para #: Glassfish.xml:454 #, no-c-format -msgid "" -"Keep in mind that if you are deploying to JBoss AS 4.x, and have defined the " -"EJB references shown above in your web.xml, you will need to also define " -"local JNDI names for each of them in jboss-web.xml, as shown below. This " -"step is not required when deploying to GlassFish, but it's mentioned here in " -"case you are also deploying the application to JBoss AS 4.x (not required " -"for JBoss AS 5)." +msgid "Keep in mind that if you are deploying to JBoss AS 4.x, and have defined the EJB references shown above in your web.xml, you will need to also define local JNDI names for each of them in jboss-web.xml, as shown below. This step is not required when deploying to GlassFish, but it's mentioned here in case you are also deploying the application to JBoss AS 4.x (not required for JBoss AS 5)." msgstr "" #. Tag: programlisting @@ -738,8 +724,7 @@ #, no-c-format msgid "" "<![CDATA[<ejb-local-ref> \n" -" <ejb-ref-name>seamgen_example/AuthenticatorAction</ejb-ref-" -"name> \n" +" <ejb-ref-name>seamgen_example/AuthenticatorAction</ejb-ref-name> \n" " <local-jndi-name>AuthenticatorAction</local-jndi-name> \n" " </ejb-local-ref>\n" " \n" @@ -748,6 +733,15 @@ " <local-jndi-name>EjbSynchronizations</local-jndi-name>\n" " </ejb-local-ref>]]>" msgstr "" +"<![CDATA[<ejb-local-ref> \n" +" <ejb-ref-name>seamgen_example/AuthenticatorAction</ejb-ref-name> \n" +" <local-jndi-name>AuthenticatorAction</local-jndi-name> \n" +" </ejb-local-ref>\n" +" \n" +" <ejb-local-ref>\n" +" <ejb-ref-name>seamgen_example/EjbSynchronizations</ejb-ref-name> \n" +" <local-jndi-name>EjbSynchronizations</local-jndi-name>\n" +" </ejb-local-ref>]]>" #. Tag: title #: Glassfish.xml:470 @@ -758,9 +752,7 @@ #. Tag: para #: Glassfish.xml:472 #, no-c-format -msgid "" -"We want to take the existing <literal>Authenticator</literal> Seam POJO " -"component and create an EJB3 out of it." +msgid "We want to take the existing <literal>Authenticator</literal> Seam POJO component and create an EJB3 out of it." msgstr "" #. Tag: para @@ -772,21 +764,13 @@ #. Tag: para #: Glassfish.xml:488 #, no-c-format -msgid "" -"Add the <literal>@Stateless</literal> annotation to the new " -"<literal>AuthenticatorAction</literal> class." +msgid "Add the <literal>@Stateless</literal> annotation to the new <literal>AuthenticatorAction</literal> class." msgstr "" #. Tag: para #: Glassfish.xml:495 #, no-c-format -msgid "" -"Create an interface called <literal>Authenticator</literal> which " -"<literal>AuthenticatorAction</literal> implements (EJB3 requires session " -"beans to have a local interface). Annotate the interface with " -"<literal>@Local</literal>, and add a single method with same signature as " -"the <literal>authenticate</literal> in <literal>AuthenticatorAction</" -"literal>." +msgid "Create an interface called <literal>Authenticator</literal> which <literal>AuthenticatorAction</literal> implements (EJB3 requires session beans to have a local interface). Annotate the interface with <literal>@Local</literal>, and add a single method with same signature as the <literal>authenticate</literal> in <literal>AuthenticatorAction</literal>." msgstr "" #. Tag: programlisting @@ -797,6 +781,9 @@ "@Stateless\n" "public class AuthenticatorAction implements Authenticator {]]>" msgstr "" +"<![CDATA[@Name(\"authenticator\") \n" +"@Stateless\n" +"public class AuthenticatorAction implements Authenticator {]]>" #. Tag: programlisting #: Glassfish.xml:510 @@ -808,79 +795,76 @@ " public boolean authenticate(); \n" "}]]>" msgstr "" +"<![CDATA[@Local\n" +"public interface Authenticator { \n" +"\n" +" public boolean authenticate(); \n" +"}]]>" #. Tag: para #: Glassfish.xml:514 #, no-c-format -msgid "" -"We've already added its reference to the <literal>web.xml</literal> file so " -"we are good to go." +msgid "We've already added its reference to the <literal>web.xml</literal> file so we are good to go." msgstr "" #. Tag: title #: Glassfish.xml:523 #, no-c-format -msgid "" -"Extra jar dependencies and other changes to the <literal>build.xml</literal>" +msgid "Extra jar dependencies and other changes to the <literal>build.xml</literal>" msgstr "" #. Tag: para #: Glassfish.xml:528 #, no-c-format -msgid "" -"This application has similar requirements as the <literal>jee5/booking</" -"literal> example." +msgid "This application has similar requirements as the <literal>jee5/booking</literal> example." msgstr "" #. Tag: para #: Glassfish.xml:534 #, no-c-format -msgid "" -"Change the default target to <literal>archive</literal> (we aren't going to " -"cover automatic deployment to GlassFish)." +msgid "Change the default target to <literal>archive</literal> (we aren't going to cover automatic deployment to GlassFish)." msgstr "" #. Tag: programlisting #: Glassfish.xml:539 #, no-c-format -msgid "" -"<![CDATA[<project name=\"seamgen_example\" default=\"archive\" basedir=\"." -"\">]]>" -msgstr "" +msgid "<![CDATA[<project name=\"seamgen_example\" default=\"archive\" basedir=\".\">]]>" +msgstr "<![CDATA[<project name=\"seamgen_example\" default=\"archive\" basedir=\".\">]]>" #. Tag: para #: Glassfish.xml:542 #, no-c-format -msgid "" -"We need to get the <literal>GlassFishDerbyDialect.class</literal> into our " -"application jar. To do that find the <literal>jar</literal> task and add the " -"<literal>GlassFishDerbyDialect.class</literal> line as shown below:" +msgid "We need to get the <literal>GlassfishDerbyDialect.class</literal> into our application jar. To do that find the <literal>jar</literal> task and add the <literal>GlassfishDerbyDialect.class</literal> line as shown below:" msgstr "" #. Tag: programlisting #: Glassfish.xml:549 #, no-c-format msgid "" -"<![CDATA[<target name=\"jar\" depends=\"compile,copyclasses\" description=" -"\"Build the distribution .jar file\">\n" +"<![CDATA[<target name=\"jar\" depends=\"compile,copyclasses\" description=\"Build the distribution .jar file\">\n" " <copy todir=\"${jar.dir}\">\n" " <fileset dir=\"${basedir}/resources\">\n" " <include name=\"seam.properties\" />\n" " <include name=\"*.drl\" />\n" -" <include name=\"GlassFishDerbyDialect.class\" />\n" +" <include name=\"GlassfishDerbyDialect.class\" />\n" " </fileset> \n" " </copy>\n" " ...]]>" msgstr "" +"<![CDATA[<target name=\"jar\" depends=\"compile,copyclasses\" description=\"Build the distribution .jar file\">\n" +" <copy todir=\"${jar.dir}\">\n" +" <fileset dir=\"${basedir}/resources\">\n" +" <include name=\"seam.properties\" />\n" +" <include name=\"*.drl\" />\n" +" <include name=\"GlassfishDerbyDialect.class\" />\n" +" </fileset> \n" +" </copy>\n" +" ...]]>" #. Tag: para #: Glassfish.xml:552 #, no-c-format -msgid "" -"Now we need to get extra jars into the <literal>ear</literal> file. Look for " -"the <literal><![CDATA[<copy todir=\"${ear.dir}/lib\">]]></literal> section " -"of the <literal>ear</literal> target. Add the following to the child " -"<literal><![CDATA[<fileset dir=\"${lib.dir}\">]]></literal> element." +msgid "Now we need to get extra jars into the <literal>ear</literal> file. Look for the <literal><![CDATA[<copy todir=\"${ear.dir}/lib\">]]></literal> section of the <literal>ear</literal> target. Add the following to the child <literal><![CDATA[<fileset dir=\"${lib.dir}\">]]></literal> element." msgstr "" #. Tag: para @@ -901,6 +885,13 @@ "<include name=\"hibernate-validator.jar\"/>\n" "<include name=\"jboss-common-core.jar\"/>]]>" msgstr "" +"<![CDATA[<!-- Hibernate and deps --> \n" +"<include name=\"hibernate.jar\"/>\n" +"<include name=\"hibernate-commons-annotations.jar\"/>\n" +"<include name=\"hibernate-annotations.jar\"/>\n" +"<include name=\"hibernate-entitymanager.jar\"/>\n" +"<include name=\"hibernate-validator.jar\"/>\n" +"<include name=\"jboss-common-core.jar\"/>]]>" #. Tag: para #: Glassfish.xml:569 @@ -922,6 +913,15 @@ "<include name=\"commons-logging.jar\" />\n" "<include name=\"commons-collections.jar\" />]]>" msgstr "" +"<![CDATA[<!-- 3rd party and supporting jars -->\n" +"<include name=\"javassist.jar\"/>\n" +"<include name=\"dom4j.jar\"/> \n" +"<include name=\"concurrent.jar\" />\n" +"<include name=\"cglib.jar\"/>\n" +"<include name=\"asm.jar\"/>\n" +"<include name=\"antlr.jar\" />\n" +"<include name=\"commons-logging.jar\" />\n" +"<include name=\"commons-collections.jar\" />]]>" #. Tag: para #: Glassfish.xml:574 @@ -955,6 +955,27 @@ " <include name=\"commons-collections.jar\" />\n" "</fileset>]]>" msgstr "" +"<![CDATA[<fileset dir=\"${lib.dir}\">\n" +" <includesfile name=\"deployed-jars-ear.list\" />\n" +" \n" +" <!-- Hibernate and deps -->\n" +" <include name=\"hibernate.jar\"/>\n" +" <include name=\"hibernate-commons-annotations.jar\"/>\n" +" <include name=\"hibernate-annotations.jar\"/>\n" +" <include name=\"hibernate-entitymanager.jar\"/>\n" +" <include name=\"hibernate-validator.jar\"/>\n" +" <include name=\"jboss-common-core.jar\" />\n" +" \n" +" <!-- 3rd party and supporting jars -->\n" +" <include name=\"javassist.jar\" />\n" +" <include name=\"dom4j.jar\" />\n" +" <include name=\"concurrent.jar\" />\n" +" <include name=\"cglib.jar\" />\n" +" <include name=\"asm.jar\" />\n" +" <include name=\"antlr.jar\" />\n" +" <include name=\"commons-logging.jar\" />\n" +" <include name=\"commons-collections.jar\" />\n" +"</fileset>]]>" #. Tag: title #: Glassfish.xml:582 @@ -965,25 +986,18 @@ #. Tag: para #: Glassfish.xml:586 #, no-c-format -msgid "" -"Build your application by calling <literal>ant</literal> in the base " -"directory of your project (for example <literal>/projects/seamgen-example</" -"literal>). The target of the build will be <literal>dist/seamgen-example." -"ear</literal>." +msgid "Build your application by calling <literal>ant</literal> in the base directory of your project (for example <literal>/projects/seamgen-example</literal>). The target of the build will be <literal>dist/seamgen-example.ear</literal>." msgstr "" #. Tag: para #: Glassfish.xml:595 #, no-c-format -msgid "" -"To deploy the application follow the instructions here <xref linkend=\"jee5-" -"glassfish-deploy\"/> but use references to this project <literal>seamgen-" -"example</literal> instead of <literal>jboss-seam-jee5</literal>." +msgid "To deploy the application follow the instructions here <xref linkend=\"jee5-glassfish-deploy\"/> but use references to this project <literal>seamgen-example</literal> instead of <literal>jboss-seam-jee5</literal>." msgstr "" #. Tag: para #: Glassfish.xml:604 #, no-c-format -msgid "" -"Checkout the app at <literal>http://localhost:8081/seamgen_example/</literal>" +msgid "Checkout the app at <literal>http://localhost:8081/seamgen_example/</literal>" msgstr "" + Modified: trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po 2008-12-27 11:43:06 UTC (rev 9844) +++ trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po 2008-12-27 13:29:19 UTC (rev 9845) @@ -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-27 11:05+0100\n" +"PO-Revision-Date: 2008-12-27 12:47+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -31,13 +31,13 @@ #: Hsearch.xml:10 #, no-c-format msgid "Full text search engines like Apache Lucene™ are a very powerful technology that bring full text and efficient queries to applications. Hibernate Search, which uses Apache Lucene under the covers, indexes your domain model with the addition of a few annotations, takes care of the database / index synchronization and returns regular managed objects that are matched by full text queries. Keep in mind, thought, that there are mismatches that arise when dealing with an object domain model over a text index (keeping the index up to date, mismatch between the index structure and the domain model, and querying mismatch). But the benefits of speed and efficiency far outweigh these limitations." -msgstr "Motori di ricerca full text come Apache Lucene™ sono un potentissima tecnologia che apporta alle applicazioni query full text ed efficienti. Hibernate Search, che utilizza Apache Lucene al suo interno, indicizza il modello di dominio con l'aggiunta di alcune annotazioni, si prende cura del database, della sincronizzazione degli indici e restituisce oggetti regolari gestiti che corrispondono alle query full text. Tuttavia si tenga presente che ci sono delle irregolarità quando si ha a che fare con un modello di dominio a oggetti sopra ad un indice di testo (mantenere l'indice aggiornato, irregolarità tra la struttura dell'indice ed il modello di dominio, e irregolarità di query). Ma i benefici di velocità ed efficienza superano di gran lunga queste limitazioni." +msgstr "Motori di ricerca full text come Apache Lucene™ sono una potentissima tecnologia che fornisce alle applicazioni efficienti query full text. Hibernate Search, che utilizza Apache Lucene al suo interno, indicizza il modello di dominio con l'aggiunta di alcune annotazioni, si prende cura del database, della sincronizzazione degli indici e restituisce oggetti regolari gestiti che corrispondono alle query full text. Tuttavia si tenga presente che ci sono delle irregolarità quando si ha a che fare con un modello di dominio a oggetti sopra ad un indice di testo (mantenere l'indice aggiornato, irregolarità tra la struttura dell'indice ed il modello di dominio, e irregolarità di query). Ma i benefici di velocità ed efficienza superano di gran lunga queste limitazioni." #. Tag: para #: Hsearch.xml:21 #, no-c-format msgid "Hibernate Search has been designed to integrates nicely and as naturally as possible with JPA and Hibernate. As a natural extension, JBoss Seam provides an Hibernate Search integration." -msgstr "Hibernate Search è stato progettato per integrarsi nel modo pià naturale possibile con JPA ed Hibernate. Come naturale estensione, JBoss Seam fornisce l'integrazione con Hibernate Search." +msgstr "Hibernate Search è stato progettato per integrarsi nel modo più naturale possibile con JPA ed Hibernate. Essendo una naturale estensione, JBoss Seam fornisce l'integrazione con Hibernate Search." #. Tag: para #: Hsearch.xml:25 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-27 11:43:06 UTC (rev 9844) +++ trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-27 13:29:19 UTC (rev 9845) @@ -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-25 15:16+0100\n" +"PO-Revision-Date: 2008-12-27 14:28+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -621,7 +621,7 @@ #: Jbpm.xml:342 #, no-c-format msgid "The <literal>view-id</literal> is the JSF view id. The <literal>&lt;redirect/&gt;</literal> element has the same effect as <literal>&lt;redirect/&gt;</literal> in a JSF navigation rule: namely, a post-then-redirect behavior, to overcome problems with the browser's refresh button. (Note that Seam propagates conversation contexts over these browser redirects. So there is no need for a Ruby on Rails style \"flash\" construct in Seam!)" -msgstr "" +msgstr "<literal>view-id</literal> è l'id della vista JSF. L'elemento <literal>&lt;redirect/&gt;</literal> ha lo stesso effetto di <literal>&lt;redirect/&gt;</literal> in una regola di navigazione JSF: cioè un comportamento post-then-redirect per superare i problemi del pulsante aggiorna del browser. (Si noti che Seam propaga i contesti di conversazioni assieme a questi redirect. Quindi in Seam non serve alcun construtto \"flash\" dello stile di Ruby on Rails!)" #. Tag: para #: Jbpm.xml:351 @@ -639,13 +639,13 @@ #: Jbpm.xml:358 #, no-c-format msgid "When the transition is triggered by clicking this button, jBPM will activate the transition action by calling the <literal>guess()</literal> method of the <literal>numberGuess</literal> component. Notice that the syntax used for specifying actions in the jPDL is just a familiar JSF EL expression, and that the transition action handler is just a method of a Seam component in the current Seam contexts. So we have exactly the same event model for jBPM events that we already have for JSF events! (The <emphasis>One Kind of Stuff</emphasis> principle.)" -msgstr "" +msgstr "Quando cliccando il pulsante verrà invocata la transizione, jBPM attiverà l'azione della transizione chiamando il metodo <literal>guess()</literal> del componente <literal>numberGuess</literal>. Si noti che la sintassi usata per specificare le azioni in jPDL non è che un'espressione JSF EL già familiare, e che l'action handler della transizione è solo un metodo di un componente Seam negli attuali contesti. Così per gli eventi jBPM si ha esattamente lo stesso modello ad eventi visto per gli eventi JSF! (Il principio <emphasis>Unico tipo di \"cosa\"</emphasis>.)" #. Tag: para #: Jbpm.xml:369 #, no-c-format msgid "In the case of a null outcome (for example, a command button with no <literal>action</literal> defined), Seam will signal the transition with no name if one exists, or else simply redisplay the page if all transitions have names. So we could slightly simplify our example pageflow and this button:" -msgstr "" +msgstr "Nel caso di esito nullo (per esempio un pulsante di comando senza la definizione di <literal>action</literal>), Seam segnalerà la transizione senza nome se ne esiste una, oppure rivisualizzerà la pagina se tutte le transizioni hanno un nome. Così è possibile semplificare leggermente l'esempio del pageflow e questo pulsante:" #. Tag: programlisting #: Jbpm.xml:376 @@ -708,7 +708,7 @@ #: Jbpm.xml:393 #, no-c-format msgid "However, this is considered an inferior style, since it moves responsibility for controlling the flow out of the pageflow definition and back into the other components. It is much better to centralize this concern in the pageflow itself." -msgstr "" +msgstr "Comunque questo è considerato uno stile inferiore, poiché sposta la responsabilità del controllo del flusso fuori dalla definizione del pageflow e la mette negli altri componenti. E' molto meglio centralizzare questo concern nel pageflow stesso." #. Tag: title #: Jbpm.xml:402 @@ -720,7 +720,7 @@ #: Jbpm.xml:404 #, no-c-format msgid "Usually, we don't need the more powerful features of jPDL when defining pageflows. We do need the <literal>&lt;decision&gt;</literal> node, however:" -msgstr "" +msgstr "Di solito non occorrono le funzionalità più potenti di jPDL nella definizione dei pageflow. Serve comunque il nodo <literal>&lt;decision&gt;</literal>:" #. Tag: programlisting #: Jbpm.xml:409 @@ -752,7 +752,7 @@ #: Jbpm.xml:420 #, no-c-format msgid "We end the conversation using <literal>&lt;end-conversation&gt;</literal> or <literal>@End</literal>. (In fact, for readability, use of <emphasis>both</emphasis> is encouraged.)" -msgstr "" +msgstr "Si termina una conversazione usando <literal>&lt;end-conversation&gt;</literal> oppure <literal>@End</literal>. (Infatti per chiarezza si consiglia l'uso di <emphasis>entrambi</emphasis>.)\"" #. Tag: programlisting #: Jbpm.xml:426 @@ -798,7 +798,7 @@ #: Jbpm.xml:440 #, no-c-format msgid "It is possible to compose pageflows and have one pageflow pause pause while another pageflow executes. The <literal>&lt;process-state&gt;</literal> node pauses the outer pageflow, and begins execution of a named pageflow:" -msgstr "" +msgstr "E' possibile comporre pageflow ed avere una pausa in un pageflow mentre viene eseguito un altro pageflow. Il nodo <literal>&lt;process-state&gt;</literal> effettua una pausa nel pageflow più esterno e comincia l'esecuzione di un pageflow con nome:" #. Tag: programlisting #: Jbpm.xml:447 @@ -818,7 +818,7 @@ #: Jbpm.xml:449 #, no-c-format msgid "The inner flow begins executing at a <literal>&lt;start-state&gt;</literal> node. When it reaches an <literal>&lt;end-state&gt;</literal> node, execution of the inner flow ends, and execution of the outer flow resumes with the transition defined by the <literal>&lt;process-state&gt;</literal> element." -msgstr "" +msgstr "Il flusso più interno comincia l'esecuzione al nodo <literal>&lt;start-state&gt;</literal>. Quando raggiunge un nodo <literal>&lt;end-state&gt;</literal>, l'esecuzione del flusso più interno termina, e riprende quella del flusso più esterno con la transizione definita dall'elemento <literal>&lt;process-state&gt;</literal>." #. Tag: title #: Jbpm.xml:462 @@ -830,13 +830,13 @@ #: Jbpm.xml:463 #, no-c-format msgid "A business process is a well-defined set of tasks that must be performed by users or software systems according to well-defined rules about <emphasis>who</emphasis> can perform a task, and <emphasis>when</emphasis> it should be performed. Seam's jBPM integration makes it easy to display lists of tasks to users and let them manage their tasks. Seam also lets the application store state associated with the business process in the <literal>BUSINESS_PROCESS</literal> context, and have that state made persistent via jBPM variables." -msgstr "" +msgstr "Un processo di business è un set di task ben-definiti che deve essere eseguito dagli utenti o dai sistemi software secondo regole ben-definite riguardo <emphasis>chi</emphasis> può eseguire un task, e <emphasis>quando</emphasis>deve essere eseguito. L'integrazione jBPM di Seam facilita la visione della lista di task agli utenti e consente loro di gestire questi task. Seam consente anche all'applicazione di memorizzare lo stato associato al processo di business nel contesto <literal>BUSINESS_PROCESS</literal>, ed rendere questo stato persistente tramite variabili jBPM." #. Tag: para #: Jbpm.xml:475 #, no-c-format msgid "A simple business process definition looks much the same as a page flow definition (<emphasis>One Kind of Stuff</emphasis>), except that instead of <literal>&lt;page&gt;</literal> nodes, we have <literal>&lt;task-node&gt;</literal> nodes. In a long-running business process, the wait states are where the system is waiting for some user to log in and perform a task." -msgstr "" +msgstr "Una semplice definizione di processo di business appare più o meno come una definizione di pageflow (<emphasis>Unico tipo di cosa</emphasis>), tranne che invece dei nodi <literal>&lt;page&gt;</literal>, si hanno i nodi <literal>&lt;task-node&gt;</literal>. In un processo di business long-running, gli stati di attesa si verificano quando il sistema aspetta che un qualche utente entri ed esegua un task." #. Tag: programlisting #: Jbpm.xml:484 @@ -880,7 +880,7 @@ #: Jbpm.xml:496 #, no-c-format msgid "It is perfectly possible that we might have both jPDL business process definitions and jPDL pageflow definitions in the same project. If so, the relationship between the two is that a single <literal>&lt;task&gt;</literal> in a business process corresponds to a whole pageflow <literal>&lt;pageflow-definition&gt;</literal>" -msgstr "" +msgstr "E' perfettamente possibile avere entrambi le definizioni di processo di business jPDL e le definizioni di pageflow jPDL nello stesso progetto. Se questo è il caso, la relazione tra i due è che un singolo <literal>&lt;task&gt;</literal> in un processo di business corrisponde ad un intero pageflow <literal>&lt;pageflow-definition&gt;</literal>" #. Tag: title #: Jbpm.xml:507 @@ -920,7 +920,7 @@ #: Jbpm.xml:519 #, no-c-format msgid "As jBPM processes are persistent across application restarts, when using Seam in a production environment you won't want to install the process definition every time the application starts. Therefore, in a production environment, you'll need to deploy the process to jBPM outside of Seam. In other words, only install process definitions from <literal>components.xml</literal> when developing your application." -msgstr "" +msgstr "Poichéi processi jBPM sono persistenti nel corso dei riavvii dell'applicazione, quando si usa Seam in ambiente di produzione non si vorrà sicuramente installare ogni volta le definizioni dei processi adogni riavvio. Quindi, in ambiente di produzione, occorre fare il deploy del processo in jBPM fuori da Seam. In altre parole, si installano le definizioni dei processi dal file <literal>components.xml</literal> durante lo sviluppo dell'applicazione." #. Tag: title #: Jbpm.xml:532 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Wicket.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Wicket.po 2008-12-27 11:43:06 UTC (rev 9844) +++ trunk/doc/Seam_Reference_Guide/it-IT/Wicket.po 2008-12-27 13:29:19 UTC (rev 9845) @@ -5,8 +5,8 @@ msgstr "" "Project-Id-Version: Seam_Reference_Guide\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-11-06 00:24+0000\n" -"PO-Revision-Date: 2008-12-24 09:35+0100\n" +"POT-Creation-Date: 2008-12-27 11:29+0000\n" +"PO-Revision-Date: 2008-12-27 12:47+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: Italian <stefano.travelli(a)gmail.com&gt;\n&quot; "MIME-Version: 1.0\n" @@ -350,28 +350,68 @@ #. Tag: para #: Wicket.xml:230 #, no-c-format -msgid "Seam automatically installs the Wicket filter for you (ensuring that it is inserted in the correct place for you). But you still need to tell Wicket which <code>WebApplication</code> class to use:" -msgstr "Seam installa automaticamente il filtro Wicket (assicurando che sia inserito nella posizione corretta), ma è ancora necessario dire a Wicket quale classe <code>WebApplication</code> usare:" +msgid "Seam automatically installs the Wicket filter for you (ensuring that it is inserted in the correct place for you). But you still need to tell Wicket which <code>WebApplication</code> class to use." +msgstr "Seam installa automaticamente il filtro Wicket (assicurando che sia inserito nella posizione corretta), ma è ancora necessario indircare a Wicket quale classe <code>WebApplication</code> usare:" #. Tag: programlisting #: Wicket.xml:236 #, no-c-format msgid "" "<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n" -" xmlns:wicket=\"http://jboss.com/products/seam/wicket\">\n" -" \n" -" <wicket:web-application application-class=\"org.jboss.seam.example.wicket.WicketBookingApplication\" />\n" +" xmlns:wicket=\"http://jboss.com/products/seam/wicket\"\n" +" xsi:schemaLocation=\n" +" \"http://jboss.com/products/seam/wicket\n" +" http://jboss.com/products/seam/wicket-2.1.xsd\">\n" +" \n" +" <wicket:web-application \n" +" application-class=\"org.jboss.seam.example.wicket.WicketBookingApplication\" />\n" "</components]]>" msgstr "" "<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n" -" xmlns:wicket=\"http://jboss.com/products/seam/wicket\">\n" -" \n" -" <wicket:web-application application-class=\"org.jboss.seam.example.wicket.WicketBookingApplication\" />\n" +" xmlns:wicket=\"http://jboss.com/products/seam/wicket\"\n" +" xsi:schemaLocation=\n" +" \"http://jboss.com/products/seam/wicket\n" +" http://jboss.com/products/seam/wicket-2.1.xsd\">\n" +" \n" +" <wicket:web-application \n" +" application-class=\"org.jboss.seam.example.wicket.WicketBookingApplication\" />\n" "</components]]>" #. Tag: para -#: Wicket.xml:239 +#: Wicket.xml:238 #, no-c-format +msgid "In addition, if you plan to use JSF-based pages in the same application as wicket pages, you'll need to ensure that the jsf exception filter is only enabled for jsf urls:" +msgstr "In aggiunta se si pensa di usare le pagine basate su JSF in un'appliczione con pagine wicket, bisogna assicurarsi che il filtro delle eccezioni jsf sia abilitato per gli url jsf:" + +#. Tag: programlisting +#: Wicket.xml:243 +#, no-c-format +msgid "" +"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n" +" xmlns:web=\"http://jboss.com/products/seam/web\"\n" +" xmlns:wicket=\"http://jboss.com/products/seam/wicket\"\n" +" xsi:schemaLocation=\n" +" \"http://jboss.com/products/seam/web\n" +" http://jboss.com/products/seam/web-2.1.xsd\">\n" +" \n" +" <!-- Only map the seam jsf exception filter to jsf paths, which we identify with the *.seam path -->\n" +" <web:exception-filter url-pattern=\"*.seam\"/>\n" +"</components]]>" +msgstr "" +"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n" +" xmlns:web=\"http://jboss.com/products/seam/web\"\n" +" xmlns:wicket=\"http://jboss.com/products/seam/wicket\"\n" +" xsi:schemaLocation=\n" +" \"http://jboss.com/products/seam/web\n" +" http://jboss.com/products/seam/web-2.1.xsd\">\n" +" \n" +" <!-- Si mappa solo il filtro per le eccezioni jsf di seam nel path jsf, che viene identificato con il path *.seam -->\n" +" <web:exception-filter url-pattern=\"*.seam\"/>\n" +"</components]]>" + +#. Tag: para +#: Wicket.xml:247 +#, no-c-format msgid "Take a look at the Wicket documentation for more on authorization strategies and other methods you can override on the <code>Application</code> class." msgstr "Per maggiori informazioni sulle strategie di autorizzazione e gli altri metodi che possono essere implementati sulla classe <code>Application</code> fare riferimento alla documentazione Wicket."