[seam-commits] Seam SVN: r10919 - branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT.
seam-commits at lists.jboss.org
seam-commits at lists.jboss.org
Sat May 16 15:27:10 EDT 2009
Author: nico.ben
Date: 2009-05-16 15:27:10 -0400 (Sat, 16 May 2009)
New Revision: 10919
Modified:
branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Author_Group.po
branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Wicket.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Author_Group.po
===================================================================
--- branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Author_Group.po 2009-05-16 19:16:17 UTC (rev 10918)
+++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Author_Group.po 2009-05-16 19:27:10 UTC (rev 10919)
@@ -5,8 +5,8 @@
msgstr ""
"Project-Id-Version: seam 2_0\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-02-19 21:44+0000\n"
-"PO-Revision-Date: 2009-02-19 22:52+0100\n"
+"POT-Creation-Date: 2009-05-16 19:18+0000\n"
+"PO-Revision-Date: 2009-05-16 21:24+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -161,6 +161,7 @@
#. Tag: shortaffil
#: Author_Group.xml:103
#: Author_Group.xml:110
+#: Author_Group.xml:117
#, no-c-format
msgid "Italian Translation"
msgstr "Traduzione in italiano"
@@ -174,17 +175,23 @@
#. Tag: othercredit
#: Author_Group.xml:113
#, no-c-format
+msgid "<firstname>Francesco</firstname> <surname>Milesi</surname>"
+msgstr "<firstname>Francesco</firstname> <surname>Milesi</surname>"
+
+#. Tag: othercredit
+#: Author_Group.xml:120
+#, no-c-format
msgid "<firstname>Japan</firstname> <surname>JBoss User Group</surname>"
msgstr "<firstname>Japan</firstname> <surname>JBoss User Group</surname>"
#. Tag: shortaffil
-#: Author_Group.xml:117
+#: Author_Group.xml:124
#, no-c-format
msgid "Japanese Translation"
msgstr "Traduzione in giapponese"
#. Tag: editor
-#: Author_Group.xml:120
+#: Author_Group.xml:127
#, no-c-format
msgid "<firstname>Samson</firstname> <surname>Kittoli</surname>"
msgstr "<firstname>Samson</firstname> <surname>Kittoli</surname>"
Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Wicket.po
===================================================================
--- branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Wicket.po 2009-05-16 19:16:17 UTC (rev 10918)
+++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Wicket.po 2009-05-16 19:27:10 UTC (rev 10919)
@@ -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-12-27 11:29+0000\n"
-"PO-Revision-Date: 2009-04-07 15:43+0100\n"
+"POT-Creation-Date: 2009-05-16 19:19+0000\n"
+"PO-Revision-Date: 2009-05-16 21:26+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: Italian <stefano.travelli at gmail.com>\n"
"MIME-Version: 1.0\n"
@@ -140,7 +140,7 @@
#. Tag: para
#: Wicket.xml:109
#: Wicket.xml:136
-#: Wicket.xml:211
+#: Wicket.xml:295
#, no-c-format
msgid "For example:"
msgstr "Ad esempio:"
@@ -246,12 +246,102 @@
#. Tag: para
#: Wicket.xml:176
#, no-c-format
-msgid "Seam needs to instrument the bytecode of your Wicket classes to be able to intercept the annotations you use. Seam provides two ways to do this.The first is to place your classes in <code>WEB-INF/wicket</code>. Seam will look for classes placed in this directory at startup and instrument them. An alternative approach, which can be used alongside the first, is to use an ant task for instrumention. Seam provides such a task; it is packaged in <literal>jboss-seam-wicket-ant.jar </literal>, and can be used in the following manner:"
-msgstr "Seam ha bisogno di intervenire sul bytecode delle classi Wicket in modo da poter intercettare le annotazioni usate. Seam fornisce due modi per fare questo. Il primo è di mettere le classi in <code>WEB-INF/wicket</code>. Seam cercherà le classi messe in questa cartella durante l'avvio e interverrà sul loro bytecode. Un approccio alternativo, che può essere utilizzato insieme al primo, è di usare un task ant per modificare il bytecode. Seam fornisce questo task: è contenuto in <literal>jboss-seam-wicket-ant.jar</literal> e può essere usato nel seguento modo: "
+msgid "Seam needs to instrument the bytecode of your Wicket classes to be able to intercept the annotations you use. The first decision to make is: do you want your code instrumented at runtime as your app is running, or at compile time? The former requires no integration with your build environment, but has a performance penalty when loading each instrumented class for the first time. The latter is faster, but requires you to integrate this instrumentation into your build environment."
+msgstr ""
-#. Tag: programlisting
+#. Tag: title
#: Wicket.xml:186
#, no-c-format
+msgid "Runtime instrumentation"
+msgstr ""
+
+#. Tag: para
+#: Wicket.xml:187
+#, no-c-format
+msgid "There are two ways to achieve runtime instrumentation. One relies on placing wicket components to be instrumented in a special folder in your WAR deployment. If this is not acceptable or possible, you can also use an instrumentation \"agent,\" which you specify in the command line for launching your container."
+msgstr ""
+
+#. Tag: title
+#: Wicket.xml:195
+#, no-c-format
+msgid "Location-specific instrumentation"
+msgstr ""
+
+#. Tag: para
+#: Wicket.xml:196
+#, no-c-format
+msgid "Any classes placed in the <literal>WEB-INF/wicket</literal> folder within your WAR deployment will be automatically instrumented by the seam-wicket runtime. You can arrange to place your wicket pages and components here by specifying a separate output folder for those classes in your IDE, or through the use of ant scripts."
+msgstr ""
+
+#. Tag: title
+#: Wicket.xml:205
+#, no-c-format
+msgid "Runtime instrumentation agent"
+msgstr ""
+
+#. Tag: para
+#: Wicket.xml:206
+#, no-c-format
+msgid "The jar file <literal>jboss-seam-wicket.jar</literal> can be used as an iinstrumentation agent through the Java Instrumentation api. This is accomplished through the following steps:"
+msgstr ""
+
+#. Tag: para
+#: Wicket.xml:211
+#, no-c-format
+msgid "Arrange for the <literal>jboss-seam-wicket.jar</literal> file to live in a location for which you have an absolute path, as the Java Instrumentation API does not allow relative paths when specifying the location of an agent lib."
+msgstr ""
+
+#. Tag: para
+#: Wicket.xml:216
+#, no-c-format
+msgid "Add <literal>javaagent:/path/to/jboss-seam-wicket.jar</literal> to the command line options when launching your webapp container:"
+msgstr ""
+
+#. Tag: para
+#: Wicket.xml:220
+#, no-c-format
+msgid "In addition, you will need to add an environment variable that specifies packages that the agent should instrument. This is accomplished by a comma separated list of package names:"
+msgstr ""
+
+#. Tag: programlisting
+#: Wicket.xml:223
+#, no-c-format
+msgid "-Dorg.jboss.seam.wicket.instrumented-packages=my.package.one,my.other.package"
+msgstr "-Dorg.jboss.seam.wicket.instrumented-packages=my.package.one,my.other.package"
+
+#. Tag: para
+#: Wicket.xml:224
+#, no-c-format
+msgid "Note that if a package A is specified, classes in subpackages of A are also examined. The classes chosen for instrumentation can be further limited by specifying: <programlisting>-Dorg.jboss.seam.wicket.scanAnnotations=true</programlisting> and then marking instrumentable classes with the <literal>@SeamWicketComponent</literal> annotation, see <xref linkend=\"SeamWicketComponent\"/>."
+msgstr ""
+
+#. Tag: title
+#: Wicket.xml:234
+#, no-c-format
+msgid "Compile-time instrumentation"
+msgstr ""
+
+#. Tag: para
+#: Wicket.xml:235
+#, no-c-format
+msgid "Seam supports instrumentation at compile time through either Apache Ant or Apache Maven."
+msgstr ""
+
+#. Tag: title
+#: Wicket.xml:238
+#, no-c-format
+msgid "Instrumenting with ant"
+msgstr ""
+
+#. Tag: para
+#: Wicket.xml:239
+#, no-c-format
+msgid "Seam provides an ant task in the <literal>jboss-seam-wicket-ant.jar </literal>. This is used in the following manner:"
+msgstr ""
+
+#. Tag: programlisting
+#: Wicket.xml:242
+#, no-c-format
msgid ""
"<![CDATA[<taskdef name=\"instrumentWicket\" \n"
" classname=\"org.jboss.seam.wicket.ioc.WicketInstrumentationTask\">\n"
@@ -263,7 +353,7 @@
" </classpath>\n"
"</taskdef>\n"
"\n"
-"<instrumentWicket outputDirectory=\"${build.instrumented}\">\n"
+"<instrumentWicket outputDirectory=\"${build.instrumented}\" useAnnotations=\"true\">\n"
" <classpath refid=\"build.classpath\"/>\n"
" <fileset dir=\"${build.classes}\" includes=\"**/*.class\"/>\n"
"</instrumentWicket>]]>"
@@ -278,43 +368,113 @@
" </classpath>\n"
"</taskdef>\n"
"\n"
-"<instrumentWicket outputDirectory=\"${build.instrumented}\">\n"
+"<instrumentWicket outputDirectory=\"${build.instrumented}\" useAnnotations=\"true\">\n"
" <classpath refid=\"build.classpath\"/>\n"
" <fileset dir=\"${build.classes}\" includes=\"**/*.class\"/>\n"
"</instrumentWicket>]]>"
#. Tag: para
-#: Wicket.xml:187
+#: Wicket.xml:244
#, no-c-format
-msgid "Then have ant copy the instrumented classes in <literal>${build.instrumented}</literal> into <literal>WEB-INF/classes</literal>. If you want to hot deploy the Wicket components, you can copy the instrumented classes to <literal>WEB-INF/dev</literal>; if you use hot deploy, make sure that your <literal>WicketApplication</literal> class is also hot-deployed. Upon a reload of hot-deployed classes, the entire WicketApplication instance has to be re-initialized, in order to pick up new references to the classes of mounted pages."
-msgstr "Dopo bisogna fare in modo che Ant copi le classi alterate da <literal>${build.instrumented}</literal> a <literal>WEB-INF/classes</literal>. Se si vuole attivare l'esecuzione a caldo dei componenti Wicket è possibile copiare le classi alterate in <literal>WEB-INF/hot</literal>. Se si usa l'esecuzione a caldo, accertarsi che anche la classe <literal>WicketApplication</literal> sia eseguita nello stesso modo. Dopo che le classi eseguite a caldo vengono ricaricate, l'intera istanza di WicketApplication deve essere reinizializzata allo scopo di recuperare tutti i nuovi riferimenti alle classi delle pagine montate."
+msgid "This results in the instrumented classes being placed in the directory specified by <literal>${build.instrumented}</literal>. You will then need to instruct ant to copy these classes into <literal>WEB-INF/classes</literal>. If you want to hot deploy the Wicket components, you can copy the instrumented classes to <literal>WEB-INF/dev</literal>; if you use hot deploy, make sure that your <literal>WicketApplication</literal> class is also hot-deployed. Upon a reload of hot-deployed classes, the entire WicketApplication instance has to be re-initialized, in order to pick up new references to the classes of mounted pages."
+msgstr "Questo ha effetto nelle classi instrumented che vengono messe nella directory specificata da <literal>${build.instrumented}</literal>.Occorre poi fare in modo che Ant copi le classi alterate da <literal>${build.instrumented}</literal> a <literal>WEB-INF/classes</literal>. Se si vuole attivare l'esecuzione a caldo dei componenti Wicket è possibile copiare le classi alterate in <literal>WEB-INF/hot</literal>. Se si usa l'esecuzione a caldo, accertarsi che anche la classe <literal>WicketApplication</literal> sia eseguita nello stesso modo. Dopo che le classi eseguite a caldo vengono ricaricate, l'intera istanza di WicketApplication deve essere reinizializzata allo scopo di recuperare tutti i nuovi riferimenti alle classi delle pagine montate."
+#. Tag: para
+#: Wicket.xml:255
+#, no-c-format
+msgid "The <literal>useAnnotations</literal> attribute is used to make the ant task only include classes that have been marked with the <literal>@SeamWicketComponent</literal> annotation, see <xref linkend=\"SeamWicketComponent\"/>."
+msgstr ""
+
#. Tag: title
-#: Wicket.xml:202
+#: Wicket.xml:261
#, no-c-format
+msgid "Instrumenting with maven"
+msgstr ""
+
+#. Tag: para
+#: Wicket.xml:262
+#, no-c-format
+msgid ""
+"The jboss maven repository <literal>repository.jboss.org</literal> provides a plugin named <literal>seam-instrument-wicket</literal> with a <literal>process-classes</literal> mojo. An example configuration in your pom.xml might look like: <programlisting role=\"XML\"><![CDATA[<build>\n"
+" <plugins>\n"
+" <plugin>\n"
+" <groupId>org.jboss.seam</groupId>\n"
+" <artifactId>seam-instrument-wicket</artifactId>\n"
+" <version>2.1.2</version>\n"
+" <configuration>\n"
+" <scanAnnotations>true</scanAnnotations>\n"
+" <includes>\n"
+" <include>your.package.name</include>\n"
+" </includes>\n"
+" </configuration>\n"
+" <executions>\n"
+" <execution>\n"
+" <id>instrument</id>\n"
+" <phase>process-classes</phase>\n"
+" <goals>\n"
+" <goal>instrument</goal>\n"
+" </goals>\n"
+" </execution>\n"
+" </executions>\n"
+" </plugin>\n"
+" </plugins>\n"
+"</build>]]></programlisting> The above example illustrates that the instrumentation is limited to classes specified by the <literal>includes</literal> element. In this example, the <literal>scanAnnotations</literal> is specified, see <xref linkend=\"SeamWicketComponent\"/>."
+msgstr ""
+
+#. Tag: title
+#: Wicket.xml:274
+#, no-c-format
+msgid "The <literal>@SeamWicketComponent</literal> annotation"
+msgstr ""
+
+#. Tag: para
+#: Wicket.xml:275
+#, no-c-format
+msgid "Classes placed in WEB-INF/wicket will unconditionally be instrumented. The other instrumentation mechanisms all allow you to specify that instrumentation should only be applied to classes annotated with the <literal>@SeamWicketComponent</literal> annotation. This annotation is inherited, which means all subclasses of an annotated class will also be instrumented. An example usage is:"
+msgstr ""
+
+#. Tag: programlisting
+#: Wicket.xml:280
+#, no-c-format
+msgid ""
+"<![CDATA[import org.jboss.seam.wicket.ioc.SeamWicketComponent;\n"
+"@SeamWicketComponent\n"
+"public class MyPage extends WebPage{\n"
+" ...\n"
+"}]]>"
+msgstr ""
+"<![CDATA[import org.jboss.seam.wicket.ioc.SeamWicketComponent;\n"
+"@SeamWicketComponent\n"
+"public class MyPage extends WebPage{\n"
+" ...\n"
+"}]]>"
+
+#. Tag: title
+#: Wicket.xml:286
+#, no-c-format
msgid "Defining the Application"
msgstr "Definire l'applicazione"
#. Tag: para
-#: Wicket.xml:204
+#: Wicket.xml:288
#, no-c-format
msgid "A Wicket web application which uses Seam should use <code>SeamWebApplication</code> as the base class; this creates hooks into the Wicket lifecycle allowing Seam to automagically propagate the conversation as needed. It also adds status messages to the page."
msgstr "Un'applicazione web Wicket che usa Seam deve usare <code>SeamWebApplication</code> come classe base. Questa crea gli agganci nel ciclo Wicket che consentono a Seam di propagare auto-magicamente la conversazione quando necessario. Aggiunge pure i messaggi di stato alla pagina."
#. Tag: para
-#: Wicket.xml:215
+#: Wicket.xml:299
#, no-c-format
msgid "The <code>SeamAuthorizationStrategy</code> delegates authorization to Seam Security, allowing the use of <code>@Restrict</code> on Wicket components. <code>SeamWebApplication</code> installs the authorization strategy for you. You can specify the login page by implementing the <code>getLoginPage()</code> method."
msgstr "La <code>SeamAuthorizationStrategy</code> delega le autorizzazioni a Seam Security, consentendo l'uso di <code>@Restrict</code> nei componenti Wicket. <code>SeamWebApplication</code> provvede ad installare la strategia di autorizzazioni. E' possibile specificare una pagina di login implementando il metodo <code>getLoginPage()</code>."
#. Tag: para
-#: Wicket.xml:223
+#: Wicket.xml:307
#, no-c-format
msgid "You'll also need to set the home page of the application by implementing the <code>getHomePage()</code> method."
msgstr "C'è poi bisogno di impostare la home page dell'applicazione implementando il metodo <code>getHomePage()</code>."
#. Tag: programlisting
-#: Wicket.xml:228
+#: Wicket.xml:312
#, no-c-format
msgid ""
"<![CDATA[public class WicketBookingApplication extends SeamWebApplication {\n"
@@ -348,13 +508,13 @@
"]]>"
#. Tag: para
-#: Wicket.xml:230
+#: Wicket.xml:314
#, 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 indicare a Wicket quale classe <code>WebApplication</code> usare:"
#. Tag: programlisting
-#: Wicket.xml:236
+#: Wicket.xml:320
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
@@ -378,13 +538,13 @@
"</components]]>"
#. Tag: para
-#: Wicket.xml:238
+#: Wicket.xml:322
#, 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
+#: Wicket.xml:327
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
@@ -410,8 +570,27 @@
"</components]]>"
#. Tag: para
-#: Wicket.xml:247
+#: Wicket.xml:331
#, 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."
+#~ msgid ""
+#~ "Seam needs to instrument the bytecode of your Wicket classes to be able "
+#~ "to intercept the annotations you use. Seam provides two ways to do this."
+#~ "The first is to place your classes in <code>WEB-INF/wicket</code>. Seam "
+#~ "will look for classes placed in this directory at startup and instrument "
+#~ "them. An alternative approach, which can be used alongside the first, is "
+#~ "to use an ant task for instrumention. Seam provides such a task; it is "
+#~ "packaged in <literal>jboss-seam-wicket-ant.jar </literal>, and can be "
+#~ "used in the following manner:"
+#~ msgstr ""
+#~ "Seam ha bisogno di intervenire sul bytecode delle classi Wicket in modo "
+#~ "da poter intercettare le annotazioni usate. Seam fornisce due modi per "
+#~ "fare questo. Il primo è di mettere le classi in <code>WEB-INF/wicket</"
+#~ "code>. Seam cercherà le classi messe in questa cartella durante l'avvio e "
+#~ "interverrà sul loro bytecode. Un approccio alternativo, che può essere "
+#~ "utilizzato insieme al primo, è di usare un task ant per modificare il "
+#~ "bytecode. Seam fornisce questo task: è contenuto in <literal>jboss-seam-"
+#~ "wicket-ant.jar</literal> e può essere usato nel seguento modo: "
+
More information about the seam-commits
mailing list