Seam SVN: r10957 - branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: milesif
Date: 2009-05-24 09:12:26 -0400 (Sun, 24 May 2009)
New Revision: 10957
Modified:
branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Remoting.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Remoting.po
===================================================================
--- branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Remoting.po 2009-05-24 12:51:49 UTC (rev 10956)
+++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Remoting.po 2009-05-24 13:12:26 UTC (rev 10957)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-05-23 11:30+0000\n"
-"PO-Revision-Date: 2009-05-23 15:27+0100\n"
+"PO-Revision-Date: 2009-05-24 14:06+0100\n"
"Last-Translator: Francesco Milesi <milesif(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -204,9 +204,9 @@
#. Tag: para
#: Remoting.xml:78
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Now for our web page - create a new page and import the <literal>helloAction</literal> component:"
-msgstr "Questo è tutto il codice lato server che bisogna scrivere. Ora, per quantro riguarda la pagina web - bisogna creare una nuova pagina e importare il componente <literal>helloAction</literal>:"
+msgstr "Ora, per quantro riguarda la pagina web - bisogna creare una nuova pagina e importare il componente <literal>helloAction</literal>:"
#. Tag: programlisting
#: Remoting.xml:81
@@ -728,7 +728,7 @@
#: Remoting.xml:327
#, no-c-format
msgid "There is support for all number types supported by Java. On the client side, number values are always serialized as their String representation and then on the server side they are converted to the correct destination type. Conversion into either a primitive or wrapper type is supported for <literal>Byte</literal>, <literal>Double</literal>, <literal>Float</literal>, <literal>Integer</literal>, <literal>Long</literal> and <literal>Short</literal> types."
-msgstr ""
+msgstr "Sono supportati tutti i tipi numerici di Java. Sul client viene sempre serializzata la rappresentazione come stringhe dei valori numerici e sul server essi sono riconvertiti nei rispettivi tipi di destinazione. La conversione in un tipo primitivo o nel suo corrispondente wrapper è supportata per i tipi <literal>Byte</literal>, <literal>Double</literal>, <literal>Float</literal>, <literal>Integer</literal>, <literal>Long</literal> e <literal>Short</literal>."
#. Tag: title
#: Remoting.xml:335
@@ -740,7 +740,7 @@
#: Remoting.xml:337
#, no-c-format
msgid "Booleans are represented client side by Javascript Boolean values, and server side by a Java boolean."
-msgstr ""
+msgstr "I tipi Boolean sul client sono rappresentati dai Boolean di Javascript e sul server dai Boolean di Java."
#. Tag: title
#: Remoting.xml:343
@@ -752,13 +752,13 @@
#: Remoting.xml:345
#, no-c-format
msgid "In general these will be either Seam entity or JavaBean components, or some other non-component class. Use the appropriate method (either <literal>Seam.Component.newInstance()</literal> for Seam components or <literal>Seam.Remoting.createType()</literal> for everything else) to create a new instance of the object."
-msgstr ""
+msgstr "In generale questi saranno o entity di Seam o componenti JavaBean o qualche altra classe che non corrisponde a un componente. Bisogna usare il metodo appropriato (o <literal>Seam.Component.newInstance()</literal> per i componenti o <literal>Seam.Remoting.createType()</literal> per tutto il resto) per creare una nuova istanza dell'oggetto."
#. Tag: para
#: Remoting.xml:349
#, no-c-format
msgid "It is important to note that only objects that are created by either of these two methods should be used as parameter values, where the parameter is not one of the other valid types mentioned anywhere else in this section. In some situations you may have a component method where the exact parameter type cannot be determined, such as:"
-msgstr ""
+msgstr "E' importante notare che solo oggetti creati da uno di questi due metodi dovrebbero essere usati come valori parametrici, ogni volta che il parametro non corrisponde ad uno degli altri tipi validi menzionati altrove in questa sezione. In alcune situazioni può darsi che vi sia un metodo del componente per il quale non si può determinare l'esatto tipo del parametro, come in questo caso:"
#. Tag: programlisting
#: Remoting.xml:354
@@ -782,7 +782,7 @@
#: Remoting.xml:356
#, no-c-format
msgid "In this case you might want to pass in an instance of your <literal>myWidget</literal> component, however the interface for <literal>myAction</literal> won't include <literal>myWidget</literal> as it is not directly referenced by any of its methods. To get around this, <literal>MyWidget</literal> needs to be explicitly imported:"
-msgstr ""
+msgstr "In questo caso si potrebbe voler passare come parametro un'istanza del componente <literal>myWidget</literal>, ma l'interfaccia di <literal>myAction</literal> non include <literal>myWidget</literal> poiché esso non è referenziato direttamente da nessun altgro metodo. Pe risolvere la questione, <literal>MyWidget</literal> deve essere importato esplicitamente:"
#. Tag: programlisting
#: Remoting.xml:361
@@ -794,7 +794,7 @@
#: Remoting.xml:363
#, no-c-format
msgid "This will then allow a <literal>myWidget</literal> object to be created with <literal>Seam.Component.newInstance(\"myWidget\")</literal>, which can then be passed to <literal>myAction.doSomethingWithObject()</literal>."
-msgstr ""
+msgstr "Ciò permetterà all'oggetto <literal>myWidget</literal> di essere creato con <literal>Seam.Component.newInstance(\"myWidget\")</literal>, che può allora essere passato a <literal>myAction.doSomethingWithObject()</literal>."
#. Tag: title
#: Remoting.xml:370
@@ -818,7 +818,7 @@
#: Remoting.xml:381
#, no-c-format
msgid "On the client side, enums are treated the same as Strings. When setting the value for an enum parameter, simply use the String representation of the enum. Take the following component as an example:"
-msgstr ""
+msgstr "Sul client, le enum sono trattate come stringhe. Quando si valorizza un parametro enum, basta usare la rappresentazione stringa della enum. Si prenda il componente seguente come esempio:"
#. Tag: programlisting
#: Remoting.xml:384
@@ -846,7 +846,7 @@
#: Remoting.xml:386
#, no-c-format
msgid "To call the <literal>paint()</literal> method with the color <literal>red</literal>, pass the parameter value as a String literal:"
-msgstr ""
+msgstr "Per chiamare il metodo <literal>paint()</literal> con il colore <literal>red</literal>, occorre passare come parametro il literal di tipo String:"
#. Tag: programlisting
#: Remoting.xml:389
@@ -858,7 +858,7 @@
#: Remoting.xml:391
#, no-c-format
msgid "The inverse is also true - that is, if a component method returns an enum parameter (or contains an enum field anywhere in the returned object graph) then on the client-side it will be represented as a String."
-msgstr ""
+msgstr "E' vero anche l'inverso - cioè, se il metodo di un componente restituisce un parametro di tipo enum (o contiene un campo enum in un qualunque punto del grafo di oggetti restituito) allora esso sul client essa sarà rappresentato come stringa."
#. Tag: title
#: Remoting.xml:396
@@ -876,7 +876,7 @@
#: Remoting.xml:401
#, no-c-format
msgid "Bags cover all collection types including arrays, collections, lists, sets, (but excluding Maps - see the next section for those), and are implemented client-side as a Javascript array. When calling a component method that accepts one of these types as a parameter, your parameter should be a Javascript array. If a component method returns one of these types, then the return value will also be a Javascript array. The remoting framework is clever enough on the server side to convert the bag to an appropriate type for the component method call."
-msgstr ""
+msgstr "Le bag coprono tutti i tipi collezione inclusi array, collezioni, liste, insiemi, (ma escluse le mappe - per le quali bisogna fare riferimento alla prossima sezione), e sul client sono implementate come array Javascript. Quando si chiama un metodo che accetta uno di questi tipi come parametro, il parametro dovrebbe essere un array di Javascript. Se un metodo restituisce uno di questi tipi, anche il valore restituito sarà un array di Javascript. Il framework sul server è sufficientemente intelligente da convertire la bag nel tipo adatto al metodo chiamato."
#. Tag: title
#: Remoting.xml:410
@@ -888,7 +888,7 @@
#: Remoting.xml:412
#, no-c-format
msgid "As there is no native support for Maps within Javascript, a simple Map implementation is provided with the Seam Remoting framework. To create a Map which can be used as a parameter to a remote call, create a new <literal>Seam.Remoting.Map</literal> object:"
-msgstr ""
+msgstr "Poichè in Javascript le mappe non sono supportate nativamente, insieme al framework viene fornita una semplice implementazione di Map. Per creare un oggetto Map che possa essere usato come parametro di una chiamata remota, bisogna creare un nuovo oggetto di tipo <literal>Seam.Remoting.Map</literal>:"
#. Tag: programlisting
#: Remoting.xml:416
@@ -900,7 +900,7 @@
#: Remoting.xml:418
#, no-c-format
msgid "This Javascript implementation provides basic methods for working with Maps: <literal>size()</literal>, <literal>isEmpty()</literal>, <literal>keySet()</literal>, <literal>values()</literal>, <literal>get(key)</literal>, <literal>put(key, value)</literal>, <literal>remove(key)</literal> and <literal>contains(key)</literal>. Each of these methods are equivalent to their Java counterpart. Where the method returns a collection, such as <literal>keySet()</literal> and <literal>values()</literal>, a Javascript Array object will be returned that contains the key or value objects (respectively)."
-msgstr ""
+msgstr "Questa implementazione Javascript fornisce i metodi di base per lavorare con le mappe: <literal>size()</literal>, <literal>isEmpty()</literal>, <literal>keySet()</literal>, <literal>values()</literal>, <literal>get(key)</literal>, <literal>put(key, value)</literal>, <literal>remove(key)</literal> e <literal>contains(key)</literal>. Ciascuno di essi è equivalente alla controparte Java. Quando il metodo restituisce una collezione, come con <literal>keySet()</literal> e <literal>values()</literal>, sarà restituito un Array Javascript che contiene le chiavi o i valori (ripettivamente)."
#. Tag: title
#: Remoting.xml:429
@@ -912,7 +912,7 @@
#: Remoting.xml:431
#, no-c-format
msgid "To aid in tracking down bugs, it is possible to enable a debug mode which will display the contents of all the packets send back and forth between the client and server in a popup window. To enable debug mode, either execute the <literal>setDebug()</literal> method in Javascript:"
-msgstr ""
+msgstr "Per aiutare l'individuazione dei bug, è possibile abilitare una modalità di debug che mostrerà in una finestra di popup il contenuto di tutti i pacchetti inviati avanti e indietro tra client e server. Per abilitare tale modalità, o si chiama il metodo <literal>setDebug()</literal> in Javascript:"
#. Tag: programlisting
#: Remoting.xml:435
@@ -936,7 +936,7 @@
#: Remoting.xml:441
#, no-c-format
msgid "To turn off debugging, call <literal>setDebug(false)</literal>. If you want to write your own messages to the debug log, call <literal>Seam.Remoting.log(message)</literal>."
-msgstr ""
+msgstr "Per disabiliare la modalità di debug, occorre chiamare <literal>setDebug(false)</literal>. Se si vogliono scrivere dei messaggi propri nel log di debug, occorre chiamare <literal>Seam.Remoting.log(message)</literal>."
#. Tag: title
#: Remoting.xml:446
@@ -948,7 +948,7 @@
#: Remoting.xml:448
#, no-c-format
msgid "When invoking a remote component method, it is possible to specify an exception handler which will process the response in the event of an exception during component invocation. To specify an exception handler function, include a reference to it after the callback parameter in your JavaScript:"
-msgstr ""
+msgstr "Quando si fa una chiamata remota, è possibile specificare un gestore di eccezioni che processerà la risposta nell'eventualità che il metodo lanci un'eccezione. Per specificare una funzione di gestione delle eccezioni, bisogna includere nel Javascript un riferimento ad essa dopo il parametro di callback:"
#. Tag: programlisting
#: Remoting.xml:454
@@ -966,7 +966,7 @@
#: Remoting.xml:456
#, no-c-format
msgid "If you do not have a callback handler defined, you must specify <literal>null</literal> in its place:"
-msgstr ""
+msgstr "Se non viene indicato il gestore della callback, al suo posto bisogna specificare <literal>null</literal>:"
#. Tag: programlisting
#: Remoting.xml:460
@@ -982,7 +982,7 @@
#: Remoting.xml:462
#, no-c-format
msgid "The exception object that is passed to the exception handler exposes one method, <literal>getMessage()</literal> that returns the exception message which is produced by the exception thrown by the <literal>@WebRemote</literal> method."
-msgstr ""
+msgstr "L'oggetto eccezione che viene passato al gestore espone un solo metodo, <literal>getMessage()</literal>, che restituisce il messaggio di errore prodotto dall'eccezione lanciata dal memtodo annotato con <literal>@WebRemote</literal>."
#. Tag: title
#: Remoting.xml:471
@@ -994,7 +994,7 @@
#: Remoting.xml:473
#, no-c-format
msgid "The default loading message that appears in the top right corner of the screen can be modified, its rendering customised or even turned off completely."
-msgstr ""
+msgstr "Il messaggio di caricamento predefinito che appare nell'angolo dello schermo in alto a destra può essere modificato e il suo rendering personalizzato o anche eliminato completamente."
#. Tag: title
#: Remoting.xml:477
@@ -1024,7 +1024,7 @@
#: Remoting.xml:488
#, no-c-format
msgid "To completely suppress the display of the loading message, override the implementation of <literal>displayLoadingMessage()</literal> and <literal>hideLoadingMessage()</literal> with functions that instead do nothing:"
-msgstr ""
+msgstr "Per sopprimere il messaggio di caricamento, occorre fare l'override dell'implementazione di <literal>displayLoadingMessage()</literal> e <literal>hideLoadingMessage()</literal> con funzioni che non fanno nulla:"
#. Tag: programlisting
#: Remoting.xml:492
@@ -1042,13 +1042,13 @@
#: Remoting.xml:496
#, no-c-format
msgid "A Custom Loading Indicator"
-msgstr ""
+msgstr "Un indicatore di caricamento personalizzato"
#. Tag: para
#: Remoting.xml:498
#, no-c-format
msgid "It is also possible to override the loading indicator to display an animated icon, or anything else that you want. To do this override the <literal>displayLoadingMessage()</literal> and <literal>hideLoadingMessage()</literal> messages with your own implementation:"
-msgstr ""
+msgstr "E' anche possibile sovrascrivere l'indicatore di caricamento per mostrare un'icona animata o qualunque altra cosa si voglia. A questo scopo occorre fare l'override di <literal>displayLoadingMessage()</literal> e <literal>hideLoadingMessage()</literal> con un'implementazione propria:"
#. Tag: programlisting
#: Remoting.xml:502
@@ -1074,25 +1074,25 @@
#: Remoting.xml:507
#, no-c-format
msgid "Controlling what data is returned"
-msgstr ""
+msgstr "Controllare i dati restituiti"
#. Tag: para
#: Remoting.xml:509
#, no-c-format
msgid "When a remote method is executed, the result is serialized into an XML response that is returned to the client. This response is then unmarshaled by the client into a Javascript object. For complex types (i.e. Javabeans) that include references to other objects, all of these referenced objects are also serialized as part of the response. These objects may reference other objects, which may reference other objects, and so forth. If left unchecked, this object \"graph\" could potentially be enormous, depending on what relationships exist between your objects. And as a side issue (besides the potential verbosity of the response), you might also wish to prevent sensitive information from being exposed to the client."
-msgstr ""
+msgstr "Quando un metodo remoto viene esegutio, il risultato viene serializzato in una risposta XML che viene restituita al client. Questa risposta viene allora deserializzata dal client in un oggetto Javascript. Nel caso di tipi complessi (vedi JavaBean) che includono riferimenti ad altri oggetti, anche tutti gli oggetti referenziati vengono serializzati all'interno della risposta. Questi oggetti possono referenziarne altri, che possono referenziarne altri ancora e così via. Se non lo si controlla, questo \"grafo\" di oggetti potrebbe essere potenzialmente enorme, a seconda delle relazioni esistenti tra gli oggetti stessi. E vi è l'ulteriore problema (oltre alla potenziale verbosità della risposta) che potrebbe essere desiderabile impedire che delle informazioni sensibili vengano esposte al client."
#. Tag: para
#: Remoting.xml:517
#, no-c-format
msgid "Seam Remoting provides a simple means to \"constrain\" the object graph, by specifying the <literal>exclude</literal> field of the remote method's <literal>@WebRemote</literal> annotation. This field accepts a String array containing one or more paths specified using dot notation. When invoking a remote method, the objects in the result's object graph that match these paths are excluded from the serialized result packet."
-msgstr ""
+msgstr "Seam Remoting fornisce un modo semplice per \"vincolare\" il grafo di oggetti: basta valorizzare il campo <literal>exclude</literal> dell'annotazione <literal>@WebRemote</literal> del metodo remoto. Questo campo accetta un array di stringhe contenenti uno o più percorsi specificati usando la notazione col punto. Quando un metodo remoto viene invocato, gli oggetti del grafo risultante il cui percorso coincide con uno di questi vengono esclusi dalla serializzazione."
#. Tag: para
#: Remoting.xml:522
#, no-c-format
msgid "For all our examples, we'll use the following <literal>Widget</literal> class:"
-msgstr ""
+msgstr "Per tutti gli esempi utilizzeremo la seguente classe <literal>Widget</literal>:"
#. Tag: programlisting
#: Remoting.xml:524
@@ -1126,13 +1126,13 @@
#: Remoting.xml:527
#, no-c-format
msgid "Constraining normal fields"
-msgstr ""
+msgstr "Vincolare campi normali"
#. Tag: para
#: Remoting.xml:529
#, no-c-format
msgid "If your remote method returns an instance of <literal>Widget</literal>, but you don't want to expose the <literal>secret</literal> field because it contains sensitive information, you would constrain it like this:"
-msgstr ""
+msgstr "Se il metodo remoto restituisce un'istanza di <literal>Widget</literal>, ma non si volesse esporre il campo <literal>secret</literal> poiché contiene delle informazioni sensibili, sarebbe possibile escluderlo in questo modo:"
#. Tag: programlisting
#: Remoting.xml:532
@@ -1148,7 +1148,7 @@
#: Remoting.xml:534
#, no-c-format
msgid "The value \"secret\" refers to the <literal>secret</literal> field of the returned object. Now, suppose that we don't care about exposing this particular field to the client. Instead, notice that the <literal>Widget</literal> value that is returned has a field <literal>child</literal> that is also a <literal>Widget</literal>. What if we want to hide the <literal>child</literal>'s <literal>secret</literal> value instead? We can do this by using dot notation to specify this field's path within the result's object graph:"
-msgstr ""
+msgstr "Il valore \"secret\" si riferisce al campo <literal>secret</literal> dell'oggetto restituito. Ora, supponiamo che non ci importi di esporre questo campo particolare al client. Invece, si noti che il valore <literal>Widget</literal> che viene restituito ha un campo <literal>figlio</literal> che pure è un <literal>Widget</literal>. Cosa succede se, invece, si vuole nascondere il valore <literal>secret</literal> del <literal>figlio</literal>? Possiamo raggiungere lo scopo usando la notazione col punto per indicare il percorso di questo campo all'interno del grafo di oggetti risultante:"
#. Tag: programlisting
#: Remoting.xml:541
@@ -1164,13 +1164,13 @@
#: Remoting.xml:546
#, no-c-format
msgid "Constraining Maps and Collections"
-msgstr ""
+msgstr "Vincolare mappe e collezioni"
#. Tag: para
#: Remoting.xml:548
#, no-c-format
msgid "The other place that objects can exist within an object graph are within a <literal>Map</literal> or some kind of collection (<literal>List</literal>, <literal>Set</literal>, <literal>Array</literal>, etc). Collections are easy, and are treated like any other field. For example, if our <literal>Widget</literal> contained a list of other <literal>Widget</literal>s in its <literal>widgetList</literal> field, to constrain the <literal>secret</literal> field of the <literal>Widget</literal>s in this list the annotation would look like this:"
-msgstr ""
+msgstr "L'altro luogo dove degli oggetti possono esistere all'interno di un grafo sono oggetti di tipo <literal>Map</literal> o qualche genere di collezione (<literal>List</literal>, <literal>Set</literal>, <literal>Array</literal>, etc). Le collezioni sono semplici e trattate come qualunque altro campo. Per esempio, se <literal>Widget</literal> contenesse una lista di altri <literal>Widget</literal> nel suo campo <literal>widgetList</literal>, per escludere il campo <literal>secret</literal> dei <literal>Widget</literal> di questa lista l'annotazione avrebbe questo aspetto:"
#. Tag: programlisting
#: Remoting.xml:555
@@ -1186,7 +1186,7 @@
#: Remoting.xml:557
#, no-c-format
msgid "To constrain a <literal>Map</literal>'s key or value, the notation is slightly different. Appending <literal>[key]</literal> after the <literal>Map</literal>'s field name will constrain the <literal>Map</literal>'s key object values, while <literal>[value]</literal> will constrain the value object values. The following example demonstrates how the values of the <literal>widgetMap</literal> field have their <literal>secret</literal> field constrained:"
-msgstr ""
+msgstr "Per vincolare la chiave o il valore di un oggetto <literal>Map</literal>, la notazione è leggermente diversa. Aggiungere <literal>[key]</literal> dopo il nome del campo di tipo <literal>Map</literal> vincolerà il valore delle chiavi del campo di tipo <literal>Map</literal>, mentre <literal>[value]</literal> vincolerà il valore dei valori del campo di tipo <literal>Map</literal>. Gli esempi seguenti mostrano come i valori del campo <literal>widgetMap</literal> si trovino ad avere il campo <literal>secret</literal> vincolato:"
#. Tag: programlisting
#: Remoting.xml:563
@@ -1202,13 +1202,13 @@
#: Remoting.xml:567
#, no-c-format
msgid "Constraining objects of a specific type"
-msgstr ""
+msgstr "Vincolare oggetti di tipo specifico"
#. Tag: para
#: Remoting.xml:569
#, no-c-format
msgid "There is one last notation that can be used to constrain the fields of a type of object no matter where in the result's object graph it appears. This notation uses either the name of the component (if the object is a Seam component) or the fully qualified class name (only if the object is not a Seam component) and is expressed using square brackets:"
-msgstr ""
+msgstr "Vi è un'ultima notazione che può essere usata per vincolare i campi di un tipo di oggetto, indipendentemente da dove appare all'interno del grafo di oggetti restituito. Questa notazione utilizza o il nome del componente (se l'oggetto è un componente Seam) o il nome completo della classe (soltanto se l'oggetto non è un componente Seam) ed viene costruita usando le parentesi quadre:"
#. Tag: programlisting
#: Remoting.xml:574
@@ -1224,13 +1224,14 @@
#: Remoting.xml:579
#, no-c-format
msgid "Combining Constraints"
-msgstr ""
+msgstr "Combinare i vincoli"
+# verificare multiple paths
#. Tag: para
#: Remoting.xml:581
#, no-c-format
msgid "Constraints can also be combined, to filter objects from multiple paths within the object graph:"
-msgstr ""
+msgstr "I vincoli possono anche essere usati combinandoli, per filtrare oggetti con percorsi multipli all'interno del grafo:"
#. Tag: programlisting
#: Remoting.xml:583
@@ -1252,7 +1253,7 @@
#: Remoting.xml:591
#, no-c-format
msgid "By default there is no active transaction during a remoting request, so if you wish to perform database updates during a remoting request, you need to annotate the <literal>@WebRemote</literal> method with <literal>@Transactional</literal>, like so:"
-msgstr ""
+msgstr "Di default non vi è alcuna transazione attiva durante una richiesta remota, così che, se si vogliono apportare delle modifiche al database, è necessario annotare il metodo <literal>@WebRemote</literal> con <literal>@Transactional</literal>, come di seguito:"
#. Tag: programlisting
#: Remoting.xml:597
@@ -1263,6 +1264,10 @@
" entityManager.merge(order);\n"
" }]]>"
msgstr ""
+"<![CDATA[ @WebRemote @Transactional(TransactionPropagationType.REQUIRED)\n"
+" public void updateOrder(Order order) {\n"
+" entityManager.merge(order);\n"
+" }]]>"
#. Tag: title
#: Remoting.xml:601
@@ -1270,17 +1275,18 @@
msgid "JMS Messaging"
msgstr "Messaggistica JMS"
+# si raccomanda di non o non si raccomanda di?
#. Tag: para
#: Remoting.xml:603
#, no-c-format
msgid "Seam Remoting provides experimental support for JMS Messaging. This section describes the JMS support that is currently implemented, but please note that this may change in the future. It is currently not recommended that this feature is used within a production environment."
-msgstr ""
+msgstr "Seam Remoting fornisce supporto sperimentale per la gestione di messaggi JMS. Questa sezione descrive il tipo di supporto attualmente implementato, ma si tenga presente che esso potrà cambiare in futuro. Attualmente si raccomanda di non usare tale funzionalità in un ambiente di produzione."
#. Tag: para
#: Remoting.xml:610
#, no-c-format
msgid "Before you can subscribe to a JMS topic, you must first configure a list of the topics that can be subscribed to by Seam Remoting. List the topics under <literal>org.jboss.seam.remoting.messaging.subscriptionRegistry.allowedTopics</literal> in <literal>seam.properties</literal>, <literal>web.xml</literal> or <literal>components.xml</literal>."
-msgstr ""
+msgstr "Prima di sottoscrivere una topic JMS, occorre configurare la lista di topic che Seam Remoting può sottoscrivere. Occorre elencare le topic nella proprietà <literal>org.jboss.seam.remoting.messaging.subscriptionRegistry.allowedTopics</literal> in <literal>seam.properties</literal>, <literal>web.xml</literal> o <literal>components.xml</literal>."
#. Tag: programlisting
#: Remoting.xml:615
@@ -1299,7 +1305,7 @@
#: Remoting.xml:622
#, no-c-format
msgid "The following example demonstrates how to subscribe to a JMS Topic:"
-msgstr ""
+msgstr "L'esempio seguente mostra come sottoscrivere una topic JMS:"
#. Tag: programlisting
#: Remoting.xml:624
@@ -1325,13 +1331,14 @@
#: Remoting.xml:626
#, no-c-format
msgid "The <literal>Seam.Remoting.subscribe()</literal> method accepts two parameters, the first being the name of the JMS Topic to subscribe to, the second being the callback function to invoke when a message is received."
-msgstr ""
+msgstr "Il metodo <literal>Seam.Remoting.subscribe()</literal> accetta due parametri, di cui il primo è il nome della topic JMS da sottoscrivere e il secondo la funzione di callback che deve essere invocata quando si riceve un messaggio."
+# messaggi testuali e messaggi con oggetti.
#. Tag: para
#: Remoting.xml:629
#, no-c-format
msgid "There are two types of messages supported, Text messages and Object messages. If you need to test for the type of message that is passed to your callback function you can use the <literal>instanceof</literal> operator to test whether the message is a <literal>Seam.Remoting.TextMessage</literal> or <literal>Seam.Remoting.ObjectMessage</literal>. A <literal>TextMessage</literal> contains the text value in its <literal>text</literal> field (or alternatively call <literal>getText()</literal> on it), while an <literal>ObjectMessage</literal> contains its object value in its <literal>value</literal> field (or call its <literal>getValue()</literal> method)."
-msgstr ""
+msgstr "Due sono i tipi di messaggi supportati, messaggi testuali e messaggi oggetto. Per verificare il tipo di messaggio passato alla callback è possibile usare l'operatore <literal>instanceof</literal> per vedere se il messaggio sia un <literal>Seam.Remoting.TextMessage</literal> o un <literal>Seam.Remoting.ObjectMessage</literal>. Un <literal>TextMessage</literal> contiene il valore testuale nel campo <literal>text</literal> (si può anche fare una chiamata al metodo <literal>getText()</literal>), mentre un <literal>ObjectMessage</literal> contiene il valore oggetto nel campo <literal>value</literal> (si può anche fare una chiamata al metodo <literal>getValue()</literal>)."
#. Tag: title
#: Remoting.xml:639
@@ -1339,11 +1346,12 @@
msgid "Unsubscribing from a Topic"
msgstr "Disiscriversi da un Topic"
+# una topic o un topic?
#. Tag: para
#: Remoting.xml:641
#, no-c-format
msgid "To unsubscribe from a topic, call <literal>Seam.Remoting.unsubscribe()</literal> and pass in the topic name:"
-msgstr ""
+msgstr "Per annullare la sottoscrizione ad una topic, bisogna fare una chiamata a <literal>Seam.Remoting.unsubscribe()</literal> passando il nome della topic come parametro:"
#. Tag: programlisting
#: Remoting.xml:644
@@ -1351,35 +1359,38 @@
msgid "Seam.Remoting.unsubscribe(\"topicName\");"
msgstr "Seam.Remoting.unsubscribe(\"topicName\");"
+# Fare il tuning del processo di polling
+# Ottimizzare il processo di polling?
#. Tag: title
#: Remoting.xml:648
#, no-c-format
msgid "Tuning the Polling Process"
-msgstr ""
+msgstr "Fare il tuning del processo di polling"
+# polling????????
#. Tag: para
#: Remoting.xml:650
#, no-c-format
msgid "There are two parameters which you can modify to control how polling occurs. The first one is <literal>Seam.Remoting.pollInterval</literal>, which controls how long to wait between subsequent polls for new messages. This parameter is expressed in seconds, and its default setting is 10."
-msgstr ""
+msgstr "E' possibile controllare il polling dei messaggi attraverso due parametri. Il primo è <literal>Seam.Remoting.pollInterval</literal>, che controlla quanto tempo passa tra due polling successivi per verificare l'arrivo di nuovi messaggi. Tale parametro è espresso in secondi, e il suo valore predefinito è 10."
#. Tag: para
#: Remoting.xml:654
#, no-c-format
msgid "The second parameter is <literal>Seam.Remoting.pollTimeout</literal>, and is also expressed as seconds. It controls how long a request to the server should wait for a new message before timing out and sending an empty response. Its default is 0 seconds, which means that when the server is polled, if there are no messages ready for delivery then an empty response will be immediately returned."
-msgstr ""
+msgstr "Il secondo parametro è <literal>Seam.Remoting.pollTimeout</literal>, che pure è espresso in secondi. Controlla per quanto tempo una richiesta al server debba stare in attesa di un nuovo messaggio prima di andare in time out e inviare una risposta vuota. Il valore predefinito è 0: ciò significa che quando il server viene interrogato, se non ci sono nuovi messaggi pronti alla consegna, allora viene immediatamente restituita una risposta vuota."
#. Tag: para
#: Remoting.xml:659
#, no-c-format
msgid "Caution should be used when setting a high <literal>pollTimeout</literal> value; each request that has to wait for a message means that a server thread is tied up until a message is received, or until the request times out. If many such requests are being served simultaneously, it could mean a large number of threads become tied up because of this reason."
-msgstr ""
+msgstr "Occorre essere molto cauti nell'impostare un valore alto di <literal>pollTimeout</literal>; ogni richiesta in attesa di un messaggio tiene un thread attivo finché non viene ricevuto un messaggio o finché la richiesta non va in time out. Se molte di queste richieste devono essere gestite contemporaneamente, si potrebbero avere molti thread in attesa."
#. Tag: para
#: Remoting.xml:664
#, no-c-format
msgid "It is recommended that you set these options via components.xml, however they can be overridden via Javascript if desired. The following example demonstrates how to configure the polling to occur much more aggressively. You should set these parameters to suitable values for your application:"
-msgstr ""
+msgstr "Si raccomanda si impostare queste opzioni in components.xml, anche se possono essere sovrascritte dal codice Javascript. L'esempio seguente mostra come configurare il polling in modo da renderlo molto aggressivo. Dovreste impostare questi parametri a dei valori adatti alla vostra applicazione:"
#. Tag: para
#: Remoting.xml:668
14 years, 11 months
- 1
- 0
Seam SVN: r10956 - branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2009-05-24 08:51:49 -0400 (Sun, 24 May 2009)
New Revision: 10956
Modified:
branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Mail.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Mail.po
===================================================================
--- branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Mail.po 2009-05-24 12:20:25 UTC (rev 10955)
+++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Mail.po 2009-05-24 12:51:49 UTC (rev 10956)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\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:57+0100\n"
+"PO-Revision-Date: 2009-05-24 14:50+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -165,7 +165,7 @@
#: Mail.xml:69
#, no-c-format
msgid "If you wanted to email the <literal>jboss-seam-mail.jar</literal>:"
-msgstr "Se si vuole spedire le email <literal>jboss-seam-mail.jar</literal>:"
+msgstr "Se si vuole spedire <literal>jboss-seam-mail.jar</literal>:"
#. Tag: programlisting
#: Mail.xml:73
@@ -241,7 +241,7 @@
#: Mail.xml:109
#, no-c-format
msgid "If you had a set of files you wanted to attach (for example a set of pictures loaded from a database) you can just use a <literal><ui:repeat></literal>:"
-msgstr "Con un set di file da allegare (per esempio un gruppo di fotografie caricate da un database= si utilizza un <literal><ui:repeat></literal>:"
+msgstr "Con un set di file da allegare (per esempio un gruppo di fotografie caricate da un database) si utilizza un <literal><ui:repeat></literal>:"
#. Tag: programlisting
#: Mail.xml:114
@@ -285,7 +285,7 @@
#: Mail.xml:122
#, no-c-format
msgid "You may be wondering what <literal>cid:#{...}</literal> does. Well, the IETF specified that by putting this as the src for your image, the attachments will be looked at when trying to locate the image (the <literal>Content-ID</literal>'s must match) — magic!"
-msgstr "Ci si potrebbe chiedere cosa faccia <literal>cid:#{...}</literal>. IETF specifica che mettendo questo come src dell'immagine, gli allegati verranno visualizzati quando si tenta di localizzare l'immagine (il <literal>Content-ID</literal> deve corrispondere) — magia!"
+msgstr "Ci si potrebbe chiedere a cosa serva <literal>cid:#{...}</literal>. IETF specifica che mettendo questo come src dell'immagine, gli allegati verranno visualizzati quando si tenta di localizzare l'immagine (il <literal>Content-ID</literal> deve corrispondere) — magia!"
#. Tag: para
#: Mail.xml:129
@@ -329,7 +329,7 @@
#: Mail.xml:150
#, no-c-format
msgid "Often you'll want to send an email to a group of recipients (for example your users). All of the recipient mail tags can be placed inside a <literal><ui:repeat></literal>:"
-msgstr "Spesso si vuole spedire una mail adun gruppo di destinatari (per esempio i propri utenti). Tutti i tag dei destinatari possono essere messi dentro un <literal><ui:repeat></literal>:"
+msgstr "Spesso si vuole spedire una mail ad un gruppo di destinatari (per esempio i propri utenti). Tutti i tag dei destinatari possono essere messi dentro un <literal><ui:repeat></literal>:"
#. Tag: programlisting
#: Mail.xml:156
@@ -483,7 +483,7 @@
#: Mail.xml:223
#, no-c-format
msgid "The body, subject and recipient (and from) name will be encoded. You'll need to make sure facelets uses the correct charset for parsing your pages by setting encoding of the template:"
-msgstr "Il corpo, soggetto e nome destinatario (e mittente)verranno codificati. Occorre assicurarsi che facelets usi il set di caratteri corretto per il parsing delle pagine, impostando la codifica del template:"
+msgstr "Il corpo, soggetto e nome destinatario (e mittente) verranno codificati. Occorre assicurarsi che facelets usi il set di caratteri corretto per il parsing delle pagine, impostando la codifica del template:"
#. Tag: programlisting
#: Mail.xml:229
@@ -537,7 +537,7 @@
#: Mail.xml:257
#, no-c-format
msgid "If you are using EJB then you can use a MDB (Message Driven Bean) to receive email. JBoss provides a JCA adaptor — <literal>mail-ra.rar</literal> — but the version distributed with JBoss AS has a number of limitations (and isn't bundled in some versions) therefore we recommend using the <literal>mail-ra.rar</literal> distributed with Seam (it's in the <literal>extras/</literal> directory in the Seam bundle). <literal>mail-ra.rar</literal> should be placed in <literal>$JBOSS_HOME/server/default/deploy</literal>; if the version of JBoss AS you use already has this file, replace it."
-msgstr "Se si usa EJB, allora si può impiegare MDB (Message Driven Bean) per ricevere una mail. JBoss fornisce un adattatore JCA — <literal>mail-ra.rar</literal> — ma la versione distribuita cone JBoss AS ha un numero di limitazioni (e non è incorporata in alcune versioni) quindi si raccomanda di usare <literal>mail-ra.rar</literal> distribuito con Seam (si trova nella directory <literal>extras/</literal> nella distribuzione Seam). <literal>mail-ra.rar</literal> deve essere messo in <literal>$JBOSS_HOME/server/default/deploy</literal>; se la versione di JBoss già lo contiene, lo si sostituisca."
+msgstr "Se si usa EJB, allora si può impiegare MDB (Message Driven Bean) per ricevere una mail. JBoss fornisce un adattatore JCA — <literal>mail-ra.rar</literal> — ma la versione distribuita con JBoss AS ha un numero di limitazioni (e non è incorporata in alcune versioni) quindi si raccomanda di usare <literal>mail-ra.rar</literal> distribuito con Seam (si trova nella directory <literal>extras/</literal> nella distribuzione Seam). <literal>mail-ra.rar</literal> deve essere messo in <literal>$JBOSS_HOME/server/default/deploy</literal>; se la versione di JBoss già lo contiene, lo si sostituisca."
#. Tag: para
#: Mail.xml:269
@@ -595,7 +595,7 @@
#: Mail.xml:275
#, no-c-format
msgid "Each message received will cause <literal>onMessage(Message message)</literal> to be called. Most Seam annotations will work inside a MDB but you musn't access the persistence context."
-msgstr "Ogni messaggio ricevuto causerà una chiamata a <literal>onMessage(Message message)</literal>. La maggior parte delle annotazioni di Seam funzioneranno dentro MDB, manon sarà possibile accedere al contesto di persistenza."
+msgstr "Ogni messaggio ricevuto causerà una chiamata a <literal>onMessage(Message message)</literal>. La maggior parte delle annotazioni di Seam funzioneranno dentro MDB, ma non sarà possibile accedere al contesto di persistenza."
#. Tag: para
#: Mail.xml:281
@@ -619,13 +619,13 @@
#: Mail.xml:296
#, no-c-format
msgid "To include Email support in your application, include <literal>jboss-seam-mail.jar</literal> in your <literal>WEB-INF/lib</literal> directory. If you are using JBoss AS there is no further configuration needed to use Seam's email support. Otherwise you need to make sure you have the JavaMail API, an implementation of the JavaMail API present (the API and impl used in JBoss AS are distributed with seam as <literal>lib/mail.jar</literal>), and a copy of the Java Activation Framework (distributed with Seam as <literal>lib/activation.jar</literal>."
-msgstr "Per includere il supporto email nella propria applicazione, si includa <literal>jboss-seam-mail.jar</literal> nella directory <literal>WEB-INF/lib</literal>. Se si usa JBoss AS non c'è nessuna configurazione ulteriore per usare il supporto email di Seam. Altrimenti occorre assicurarsi di avere JavaMail API, un'implementazione di JavaMail API presente (l'API e l'impl usante in JBoss AS sono distribuite con seam in <literal>lib/mail.jar</literal>), ed una copia di Java Activation Framework (distribuito con seam in <literal>lib/activation.jar</literal>."
+msgstr "Per includere il supporto email nella propria applicazione, si includa <literal>jboss-seam-mail.jar</literal> nella directory <literal>WEB-INF/lib</literal>. Se si usa JBoss AS non c'è nessuna configurazione ulteriore per usare il supporto email di Seam. Altrimenti occorre assicurarsi di avere JavaMail API, un'implementazione di JavaMail API presente (l'API e l'impl usate in JBoss AS sono distribuite con seam in <literal>lib/mail.jar</literal>), ed una copia di Java Activation Framework (distribuito con seam in <literal>lib/activation.jar</literal>."
#. Tag: para
#: Mail.xml:308
#, no-c-format
msgid "The Seam Mail module requires the use of Facelets as the view technology. Future versions of the library may also support the use of JSP. Additionally, it requires the use of the seam-ui package."
-msgstr "Il module Seam Mail richiede l'uso di Facelets come tecnologia per la vista. Future versioni della libreria potranno supportare l'uso di JSP. In aggiunta si richiede l'uso del pacchetto seam-ui."
+msgstr "Il modulo Seam Mail richiede l'uso di Facelets come tecnologia per la vista. Future versioni della libreria potranno supportare l'uso di JSP. In aggiunta si richiede l'uso del pacchetto seam-ui."
#. Tag: para
#: Mail.xml:315
@@ -661,7 +661,7 @@
#: Mail.xml:336
#, no-c-format
msgid "The JBossAS <literal>deploy/mail-service.xml</literal> configures a JavaMail session binding into JNDI. The default service configuration will need altering for your network. <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JavaMail\">http://wiki.jboss.org/wiki/Wiki.jsp?page=JavaMail</ulink> describes the service in more detail."
-msgstr "<literal>deploy/mail-service.xml</literal> di JBoss AS configura una sessione JavaMail legandla a JNDI. La configurazione di default del servizio deve essere modificata per la propria rete. <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JavaMail\">http://wiki.jboss.org/wiki/Wiki.jsp?page=JavaMail</ulink> descrive il servizion con maggiore dettaglio."
+msgstr "<literal>deploy/mail-service.xml</literal> di JBoss AS configura una sessione JavaMail legandola a JNDI. La configurazione di default del servizio deve essere modificata per la propria rete. <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JavaMail\">http://wiki.jboss.org/wiki/Wiki.jsp?page=JavaMail</ulink> descrive il servizio con maggiore dettaglio."
#. Tag: programlisting
#: Mail.xml:344
@@ -687,7 +687,7 @@
#: Mail.xml:346
#, no-c-format
msgid "Here we tell Seam to get the mail session bound to <literal>java:/Mail</literal> from JNDI."
-msgstr "Qua viene detto a Seam di ottenere da JNDI la sessione mail legata <literal>java:/Mail</literal>."
+msgstr "Qua viene detto a Seam di ottenere da JNDI la sessione mail associata <literal>java:/Mail</literal>."
#. Tag: title
#: Mail.xml:354
@@ -773,7 +773,7 @@
#: Mail.xml:418
#, no-c-format
msgid "<literal>importance</literal> — low, normal or high. By default normal, this sets the importance of the mail message."
-msgstr "<literal>importance</literal> — low, normal or high. Di default è normal, questo imposta l'importanza del messaggio email."
+msgstr "<literal>importance</literal> — low, normal o high. Di default è normal, questo imposta l'importanza del messaggio email."
#. Tag: para
#: Mail.xml:424
@@ -785,7 +785,7 @@
#: Mail.xml:430
#, no-c-format
msgid "<literal>requestReadReceipt</literal> — by default false, if set, a read receipt request will be will be added, with the read receipt being sent to the <literal>From:</literal> address."
-msgstr "<literal>requestReadReceipt</literal> — di default è false, se impostato, verrà aggiunta un richiesta di conferma di lettura, da inviare all'indirizzo <literal>From:</literal>."
+msgstr "<literal>requestReadReceipt</literal> — di default è false, se impostato, verrà aggiunta una richiesta di conferma di lettura, da inviare all'indirizzo <literal>From:</literal>."
#. Tag: para
#: Mail.xml:438
14 years, 11 months
- 1
- 0
Seam SVN: r10955 - branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2009-05-24 08:20:25 -0400 (Sun, 24 May 2009)
New Revision: 10955
Modified:
branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/Rss.xml
Log:
added <ulink>
Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/Rss.xml
===================================================================
--- branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/Rss.xml 2009-05-24 11:28:05 UTC (rev 10954)
+++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/Rss.xml 2009-05-24 12:20:25 UTC (rev 10955)
@@ -253,7 +253,7 @@
<title>Links and further documentation</title>
<para>
The core of the RSs functionality is based on the YARFRAW library
- which can be found on http://yarfraw.sourceforge.net/ and most
+ which can be found on <ulink url="http://yarfraw.sourceforge.net/">http://yarfraw.sourceforge.net/</ulink> and most
features and possible limitations are inherited from here.
</para>
<para>
14 years, 11 months
- 1
- 0
Seam SVN: r10954 - branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2009-05-24 07:28:05 -0400 (Sun, 24 May 2009)
New Revision: 10954
Modified:
branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Configuration.po
branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Spring.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Configuration.po
===================================================================
--- branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Configuration.po 2009-05-24 11:01:47 UTC (rev 10953)
+++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Configuration.po 2009-05-24 11:28:05 UTC (rev 10954)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-05-05 12:31+0000\n"
-"PO-Revision-Date: 2009-05-24 12:30+0100\n"
+"PO-Revision-Date: 2009-05-24 13:07+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -23,7 +23,7 @@
#: Configuration.xml:6
#, no-c-format
msgid "Configuration is a very boring topic and an extremely tedious pastime. Unfortunately, several lines of XML are required to integrate Seam into your JSF implementation and servlet container. There's no need to be too put off by the following sections; you'll never need to type any of this stuff yourself, since you can just use seam-gen to start your application or you can copy and paste from the example applications!"
-msgstr "La configurazione è un argomento molto noioso ed un passatempo estremamente tedioso. Sfortunatamente sono richieste parecchie linee di XML per integrare Seam con l'implementazione JSF ed il servlet container. Non c'è alcun bisogno di soffermarsi sulle seguenti sezioni; non si dovrà mai scrivere queste cose a mano, poiché basta usare seam-gen per iniziare l'applicazione oppure basta copiare ed incollare il codice dagli esempi di applicazione!"
+msgstr "La configurazione è un argomento molto noioso ed un passatempo estremamente tedioso. Sfortunatamente sono richieste parecchie linee di XML per integrare Seam con l'implementazione JSF ed il servlet container. Non c'è bisogno di soffermarsi sulle seguenti sezioni; non si dovrà mai scrivere queste cose a mano, poiché basta usare seam-gen per creare ed avviare l'applicazione oppure basta copiare ed incollare il codice dagli esempi di applicazione!"
#. Tag: title
#: Configuration.xml:12
@@ -35,7 +35,7 @@
#: Configuration.xml:14
#, no-c-format
msgid "First, let's look at the basic configuration that is needed whenever we use Seam with JSF."
-msgstr "In primo luogo si comincia a guardare alla configurazione base che server ogni volta che si usa Seam con JSF."
+msgstr "In primo luogo si cominci col guardare alla configurazione base che serve ogni volta che si usa Seam con JSF."
#. Tag: title
#: Configuration.xml:17
@@ -129,7 +129,7 @@
#: Configuration.xml:38
#, no-c-format
msgid "There is a minor gray area in the JSF specification regarding the mutability of view state values. Since Seam uses the JSF view state to back its PAGE scope this can become an issue in some cases. If you're using server side state saving with the JSF-RI and you want a PAGE scoped bean to keep its exact value for a given view of a page you will need to specify the following context-param. Otherwise if a user uses the \"back\" button a PAGE scoped component will have the latest value if it has changed not the value of the \"back\" page. (see <ulink url=\"https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=295\"> Spec Issue </ulink> ). This setting is not enabled by default because of the performance hit of serializing the JSF view with every request."
-msgstr "C'è una piccola parte grigia nella specifica JSF riguardante la mutabilità dei valore dello stato della vista. Poiché Seam usa lo stato della vista JSF per tornare allo scope PAGE, questo in alcuni casi può diventare un problema. Se si usa la conservazione dello stato lato server con JSF-RI e si vuole che il bean con scope PAGE mantenga l'esatto valore per una data vista di pagina, occorre specificare il seguente parametro di contesto. Altrimenti se un utente usa il pulsante \"indietro\" un componente con scope PAGE avrà l'ultimo valore se questo non è cambiato nella pagina \"indietro\". (si veda <ulink url=\"https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=295\"> Spec Issue </ulink> ). Quest'impostazione non è abilitata di default a causa della performance nella serializzazione della vista JSF ad ogni richiesta."
+msgstr "C'è una piccola parte grigia nella specifica JSF riguardante la mutabilità dei valore dello stato della vista. Poiché Seam usa lo stato della vista JSF per tornare allo scope PAGE, questo in alcuni casi può diventare un problema. Se si usa la conservazione dello stato lato server con JSF-RI e si vuole che il bean con scope PAGE mantenga l'esatto valore per una data vista di pagina, occorre specificare il seguente parametro di contesto. Altrimenti se un utente usa il pulsante \"indietro\", un componente con scope PAGE avrà l'ultimo valore se questo non è cambiato nella pagina \"indietro\". (si veda <ulink url=\"https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=295\"> Spec Issue </ulink> ). Quest'impostazione non è abilitata di default a causa della performance nella serializzazione della vista JSF ad ogni richiesta."
#. Tag: programlisting
#: Configuration.xml:52
Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Spring.po
===================================================================
--- branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Spring.po 2009-05-24 11:01:47 UTC (rev 10953)
+++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Spring.po 2009-05-24 11:28:05 UTC (rev 10954)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-04-15 13:52+0000\n"
-"PO-Revision-Date: 2009-04-15 16:05+0100\n"
+"PO-Revision-Date: 2009-05-24 13:27+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -23,61 +23,61 @@
#: Spring.xml:8
#, no-c-format
msgid "The Spring integration (part of the Seam IoC module) allows easy migration of Spring-based projects to Seam and allows Spring applications to take advantage of key Seam features like conversations and Seam's more sophisticated persistence context management."
-msgstr ""
+msgstr "L'integrazione con Spring (parte del modulo IoC di Seam) consente una facile migrazione a Seam dei progetti basati su Spring e consente alla applicazioni Spring di sfruttare le funzionalità chiave di Seam come le conversazioni e la sofisticata gestione del contesto di persistenza."
#. Tag: para
#: Spring.xml:12
#, no-c-format
msgid "Note! The Spring integration code is included in the jboss-seam-ioc library. This dependency is required for all seam-spring integration techniques covered in this chapter."
-msgstr ""
+msgstr "Nota! Il codice di integrazione di Spring è incluso nella libreria jboss-seam-ioc. Questa dipendenza è richiesta per tutte le tecniche di integrazione seam-spring coperte in questo capitolo."
#. Tag: para
#: Spring.xml:15
#, no-c-format
msgid "Seam's support for Spring provides the ability to:"
-msgstr ""
+msgstr "Il supporto di Seam per Spring fornisce la possibilità di:"
#. Tag: para
#: Spring.xml:19
#, no-c-format
msgid "inject Seam component instances into Spring beans"
-msgstr ""
+msgstr "iniettare le istanze dei componenti Seam nei bean Spring"
#. Tag: para
#: Spring.xml:22
#, no-c-format
msgid "inject Spring beans into Seam components"
-msgstr ""
+msgstr "iniettare i bean Spring nei componenti Seam"
#. Tag: para
#: Spring.xml:25
#, no-c-format
msgid "turn Spring beans into Seam components"
-msgstr ""
+msgstr "trasformare i bean Spring in componenti Seam"
#. Tag: para
#: Spring.xml:28
#, no-c-format
msgid "allow Spring beans to live in any Seam context"
-msgstr ""
+msgstr "consentire ai bean Spring di vivere in un qualsiasi contesto Seam"
#. Tag: para
#: Spring.xml:31
#, no-c-format
msgid "start a spring WebApplicationContext with a Seam component"
-msgstr ""
+msgstr "avviare un WebApplicationContext di Spring con un componente Seam"
#. Tag: para
#: Spring.xml:34
#, no-c-format
msgid "Support for Spring PlatformTransactionManagement"
-msgstr ""
+msgstr "Supporto a PlatformTransactionManagement di Spring"
#. Tag: para
#: Spring.xml:37
#, no-c-format
msgid "provides a Seam managed replacement for Spring's <literal>OpenEntityManagerInViewFilter</literal> and <literal>OpenSessionInViewFilter</literal>"
-msgstr ""
+msgstr "fornisce un sostituto gestito da Seam per <literal>OpenEntityManagerInViewFilter</literal> e <literal>OpenSessionInViewFilter</literal> di Spring"
#. Tag: para
#: Spring.xml:40
@@ -189,7 +189,7 @@
#: Spring.xml:65
#, no-c-format
msgid "Now for the caveat!"
-msgstr ""
+msgstr "Adesso alcuni caveat!"
#. Tag: para
#: Spring.xml:67
@@ -229,7 +229,7 @@
#: Spring.xml:88
#, no-c-format
msgid "Injecting Spring beans into Seam components"
-msgstr ""
+msgstr "Iniettare i bean Spring nei componenti Seam"
#. Tag: para
#: Spring.xml:90
@@ -577,7 +577,7 @@
#: Spring.xml:258
#, no-c-format
msgid "The <literal>component.xml</literal> might look like:"
-msgstr ""
+msgstr "<literal>component.xml</literal> potrebbe così apparire:"
#. Tag: programlisting
#: Spring.xml:259
14 years, 11 months
- 1
- 0
Seam SVN: r10953 - branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2009-05-24 07:01:47 -0400 (Sun, 24 May 2009)
New Revision: 10953
Modified:
branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/Tools.xml
Log:
added <ulink>
Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/Tools.xml
===================================================================
--- branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/Tools.xml 2009-05-24 10:54:43 UTC (rev 10952)
+++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/Tools.xml 2009-05-24 11:01:47 UTC (rev 10953)
@@ -6,7 +6,7 @@
<para>
The jBPM designer and viewer will let you design and view in a nice way your business processes and your pageflows.
- This convenient tool is part of JBoss Eclipse IDE and more details can be found in the jBPM's documentation (http://docs.jboss.com/jbpm/v3/gpd/)
+ This convenient tool is part of JBoss Eclipse IDE and more details can be found in the jBPM's <ulink url="http://docs.jboss.com/jbpm/v3/gpd/">documentation</ulink>
</para>
<section>
14 years, 11 months
- 1
- 0
Seam SVN: r10952 - branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2009-05-24 06:54:43 -0400 (Sun, 24 May 2009)
New Revision: 10952
Modified:
branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Persistence.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Persistence.po
===================================================================
--- branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Persistence.po 2009-05-24 10:34:44 UTC (rev 10951)
+++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Persistence.po 2009-05-24 10:54:43 UTC (rev 10952)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-02-19 21:44+0000\n"
-"PO-Revision-Date: 2009-05-21 15:36+0100\n"
-"Last-Translator: Francesco Milesi <milesif(a)gmail.com>\n"
+"PO-Revision-Date: 2009-05-24 12:53+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -245,7 +245,7 @@
#: Persistence.xml:256
#, no-c-format
msgid "To explicitly disable Seam managed transactions declare the following in your components.xml:"
-msgstr ""
+msgstr "Per disabilitare esplicitamente le transazioni gestite da Seam si dichiari in components.xml:"
#. Tag: programlisting
#: Persistence.xml:259
@@ -257,7 +257,7 @@
#: Persistence.xml:260
#, no-c-format
msgid "For configuring Spring managed transactions see <link linkend=\"spring-transactions\">using Spring PlatformTransactionManagement</link> ."
-msgstr ""
+msgstr "Per configurare le transazioni gestite da Spring si veda <link linkend=\"spring-transactions\">uso di Spring PlatformTransactionManagement</link> ."
#. Tag: title
#: Persistence.xml:267
@@ -299,13 +299,13 @@
#: Persistence.xml:312
#, no-c-format
msgid "Using a Seam-managed persistence context with JPA"
-msgstr ""
+msgstr "Utilizzo di un contesto di persistenza gestito da Seam con JPA"
#. Tag: para
#: Persistence.xml:314
#, no-c-format
msgid "Configuring a managed persistence context is easy. In <literal>components.xml</literal>, we can write:"
-msgstr ""
+msgstr "E' facile configurare un contesto di persistenza gestito. Si scriva in <literal>components.xml</literal>:"
#. Tag: programlisting
#: Persistence.xml:319
@@ -329,7 +329,7 @@
#: Persistence.xml:328
#, no-c-format
msgid "Of course, you need to make sure that you have bound the <literal>EntityManagerFactory</literal> into JNDI. In JBoss, you can do this by adding the following property setting to <literal>persistence.xml</literal>."
-msgstr ""
+msgstr "Certamente occorre assicurarsi che <literal>EntityManagerFactory</literal> sia stato associato a JNDI. In JBoss si può fare ciò aggiungendo la seguente proprietà a <literal>persistence.xml</literal>."
#. Tag: programlisting
#: Persistence.xml:334
@@ -345,7 +345,7 @@
#: Persistence.xml:336
#, no-c-format
msgid "Now we can have our <literal>EntityManager</literal> injected using:"
-msgstr ""
+msgstr "Ora si può iniettare <literal>EntityManager</literal> usando:"
#. Tag: programlisting
#: Persistence.xml:340
@@ -419,13 +419,13 @@
#: Persistence.xml:371
#, no-c-format
msgid "Note that Seam does not flush the session, so you should always enable <literal>hibernate.transaction.flush_before_completion</literal> to ensure that the session is automatically flushed before the JTA transaction commits."
-msgstr ""
+msgstr "Si noti che Seam non esegue il flush della sessione, quindi occorre sempre abilitare <literal>hibernate.transaction.flush_before_completion</literal> per assicurarsi che di eseguire il flush della sessione prima che venga fatto il commit della transazioni JTA."
#. Tag: para
#: Persistence.xml:378
#, no-c-format
msgid "We can now have a managed Hibernate <literal>Session</literal> injected into our JavaBean components using the following code:"
-msgstr ""
+msgstr "Ora si può iniettare nei componenti JavaBean una <literal>Session</literal> di Hibernate gestita usando il seguente codice:"
#. Tag: programlisting
#: Persistence.xml:383
@@ -437,7 +437,7 @@
#: Persistence.xml:388
#, no-c-format
msgid "Seam-managed persistence contexts and atomic conversations"
-msgstr ""
+msgstr "Contesti di persistenza gestiti da Seam e conversazioni atomiche"
#. Tag: para
#: Persistence.xml:389
@@ -449,7 +449,7 @@
#: Persistence.xml:398
#, no-c-format
msgid "As with any optimistic transaction management, transaction isolation and consistency can be achieved via use of optimistic locking. Fortunately, both Hibernate and EJB 3.0 make it very easy to use optimistic locking, by providing the <literal>@Version</literal> annotation."
-msgstr ""
+msgstr "Come ogni altra gestione ottimistica delle transazioni , l'isolamento e la consistenza delle transazioni può essere ottenuta tramite l'uso del lock ottimistico. Fortunatamente sia Hibernate che EJB 3.0 semplificano l'uso del lock ottimistico, fornendo l'annotazione <literal>@Version</literal>."
#. Tag: para
#: Persistence.xml:405
@@ -485,7 +485,7 @@
#: Persistence.xml:427
#, no-c-format
msgid "Now, the <literal>claim</literal> object remains managed by the persistence context for the rest ot the conversation. We can make changes to the claim:"
-msgstr ""
+msgstr "Ora l'oggetto <literal>claim</literal> viene gestito nel contesto di persistenza per il resto della conversazione. Si possono apportare modifiche a claim:"
#. Tag: programlisting
#: Persistence.xml:432
@@ -505,7 +505,7 @@
#: Persistence.xml:434
#, no-c-format
msgid "But these changes will not be flushed to the database until we explicitly force the flush to occur:"
-msgstr ""
+msgstr "Ma questi cambiamenti non verranno eseguiti nel database finché non si forza esplicitamente il flush:"
#. Tag: programlisting
#: Persistence.xml:439
@@ -525,7 +525,7 @@
#: Persistence.xml:441
#, no-c-format
msgid "Of course, you could set the <literal>flushMode</literal> to <literal>MANUAL</literal> from pages.xml, for example in a navigation rule:"
-msgstr ""
+msgstr "Certamente si può impostare <literal>flushMode</literal> a <literal>MANUAL</literal> da pages.xml, per esempio in una regola di navigazione:"
#. Tag: programlisting
#: Persistence.xml:446
14 years, 11 months
- 1
- 0
Seam SVN: r10951 - branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2009-05-24 06:34:44 -0400 (Sun, 24 May 2009)
New Revision: 10951
Modified:
branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Configuration.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Configuration.po
===================================================================
--- branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Configuration.po 2009-05-23 13:29:35 UTC (rev 10950)
+++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Configuration.po 2009-05-24 10:34:44 UTC (rev 10951)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-05-05 12:31+0000\n"
-"PO-Revision-Date: 2009-05-23 14:43+0100\n"
+"PO-Revision-Date: 2009-05-24 12:30+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -934,7 +934,7 @@
#: Configuration.xml:464
#, no-c-format
msgid "That covers how JNDI names are defined and used. The lesson is that with some application servers, such as GlassFish, you are going to have to specify JNDI names for all EJB components explicitly, and sometimes twice! And even if you are following the same naming convention as JBoss AS, the JNDI pattern in Seam may need to be altered. For instance, the global JNDI names are automatically prefixed with java:comp/env on GlassFish, so you need to define the JNDI pattern as follows:"
-msgstr ""
+msgstr "Vediamo ora come vengono definiti ed usati i nomi JNDI. La lezione riguarda alcuni application server, come GlassFish, con cui occorre specificare i nomi JNDI esplicitamente per tutti i componenti EJB, ed alcune volte in modo doppio! Ed anche se si segue la stessa convenzione di nomi di JBoss AS, il pattern JNDI in Seam deve essere alterato. Per esempio in GlasshFish ai nomi JNDI viene automaticamente aggiunto il prefisso java:comp/env, e quindi occorre definire il pattern JNDI come segue:"
#. Tag: programlisting
#: Configuration.xml:470
@@ -946,7 +946,7 @@
#: Configuration.xml:472
#, no-c-format
msgid "Finally, let's talk about transactions. In an EJB3 environment, we recommend the use of a special built-in component for transaction management, that is fully aware of container transactions, and can correctly process transaction success events registered with the <literal>Events</literal> component. If you don't add this line to your <literal>components.xml</literal> file, Seam won't know when container-managed transactions end:"
-msgstr ""
+msgstr "Infine parliamo di transazioni. In un ambiente EJB3 si raccomanda l'uso di un componente speciale predefinito per la gestione delle transazioni, che sia pienamente consapevole delle transazioni del container e possa correttamente processare gli eventi di successo legati alle transazioni registrato con il componente <literal>Events</literal>. Se non viene aggiunta questa linea al file <literal>components.xml</literal>, Seam non saprà quando finiscono le transazioni gestite dal container:"
#. Tag: programlisting
#: Configuration.xml:479
@@ -964,7 +964,7 @@
#: Configuration.xml:486
#, no-c-format
msgid "There is one final item you need to know about. You must place a <literal>seam.properties</literal>, <literal>META-INF/seam.properties</literal> or <literal>META-INF/components.xml</literal> file in any archive in which your Seam components are deployed (even an empty properties file will do). At startup, Seam will scan any archives with <literal>seam.properties</literal> files for seam components."
-msgstr ""
+msgstr "C'è un ulteriore punto finale da sapere. Occorre mettere un file <literal>seam.properties</literal>, <literal>META-INF/seam.properties</literal> o <literal>META-INF/components.xml</literal> in qualsiasi archivio in cui vengono deployati componenti Seam (anche un file vuoto). All'avvio Seam scansionerà ogni archivio con il file <literal>seam.properties</literal> per cercare componenti seam."
#. Tag: para
#: Configuration.xml:491
@@ -982,7 +982,7 @@
#: Configuration.xml:497
#, no-c-format
msgid "You might think this is silly and what kind of idiot framework designers would make an empty file affect the behavior of their software?? Well, this is a workaround for a limitation of the JVM — if we didn't use this mechanism, our next best option would be to force you to list every component explicitly in <literal>components.xml</literal>, just like some other competing frameworks do! I think you'll like our way better."
-msgstr ""
+msgstr "Si potrebbe ritenere che ciò sia stupido e chiedersi quale stupida razza di designer di framework farebbe influenzare il proprio software da un file vuoto? Questo è un workaroundper una limitazione della JVM — se non venisse usato questo meccanismo la migliore opzione sarebbe quella di obbligarvi ad elencare esplicitamente in <literal>components.xml</literal> ciascun componente, proprio come fanno gli altri framework! Riflettete su quale sia il modo migliore."
#. Tag: title
#: Configuration.xml:508
@@ -1018,7 +1018,7 @@
#: Configuration.xml:525
#, no-c-format
msgid "Update your application's <literal>components.xml</literal> so that the generic <literal>PersistenceProvider</literal> takes precedence over the hibernate version. Simply add the following to the file:"
-msgstr ""
+msgstr "Si aggiorni il <literal>components.xml</literal> della propria applicazione affinché <literal>PersistenceProvider</literal> abbia la precedenza sulla versione Hibernate. Semplicemente si aggiunga al file:"
#. Tag: programlisting
#: Configuration.xml:530
@@ -1038,7 +1038,7 @@
#: Configuration.xml:531
#, no-c-format
msgid "If you want to take advantage of your JPA provider's non-standard features you will need to write you own implementation of the <literal>PersistenceProvider</literal>. Use <literal>HibernatePersistenceProvider</literal> as a starting point (don't forget to give back to the community :). Then you will need to tell <literal>seam</literal> to use it as before."
-msgstr ""
+msgstr "Se si vogliono sfruttare le caratteristiche nonstandard del proprio provider JPA occorre scrivere la propria implementazione di <literal>PersistenceProvider</literal>. Si usa <literal>HibernatePersistenceProvider</literal> come punto di partenza (si ricordi di dare qualcosa alla comunità :). Quindi occorrerà dire a <literal>seam</literal> di usarlo come prima."
#. Tag: programlisting
#: Configuration.xml:538
@@ -1056,7 +1056,7 @@
#: Configuration.xml:539
#, no-c-format
msgid "All that is left is updating the <literal>persistence.xml</literal> file with the correct provider class, and what ever properties your provider needs. Don't forget to package your new provider's jar files in the application if they are needed."
-msgstr ""
+msgstr "Ciò che rimane da fare è aggiornare il file <literal>persistence.xml</literal> come la giusta classe del provider e quelle proprietà che il provider richiede. Non dimenticare di impacchettare nell'applicazione i file jar del provider se richiesti."
#. Tag: title
#: Configuration.xml:547
@@ -1068,7 +1068,7 @@
#: Configuration.xml:558
#, no-c-format
msgid "If you're running in a Java EE 5 environment, this is all the configuration required to start using Seam!"
-msgstr ""
+msgstr "Se si esegue il software in ambiente Java EE 5, questa è tutta la configurazione richiesta per usare Seam!"
# come tradurre?
#. Tag: title
@@ -1182,13 +1182,13 @@
#: Configuration.xml:578
#, no-c-format
msgid "If you want to use the Seam tag library (most Seam applications do), you must include <literal>jboss-seam-ui.jar</literal> in the <literal>WEB-INF/lib</literal> directory of the WAR. If you want to use the PDF or email tag libraries, you need to put <literal>jboss-seam-pdf.jar</literal> or <literal>jboss-seam-mail.jar</literal> in <literal>WEB-INF/lib</literal>."
-msgstr ""
+msgstr "Se si vuole usare la libreria dei tag di Seam (come per la maggior parte delle applicazioni), occorre includere <literal>jboss-seam-ui.jar</literal> nella directory <literal>WEB-INF/lib</literal> del WAR. Se si vuole usare la libreria PDF o quella email, occorre mettere <literal>jboss-seam-pdf.jar</literal> o <literal>jboss-seam-mail.jar</literal> in <literal>WEB-INF/lib</literal>."
#. Tag: para
#: Configuration.xml:583
#, no-c-format
msgid "If you want to use the Seam debug page (only works for applications using facelets), you must include <literal>jboss-seam-debug.jar</literal> in the <literal>WEB-INF/lib</literal> directory of the WAR."
-msgstr ""
+msgstr "Se si vuole usare la pagina di debug di Seam (funziona solo per applicazioni con facelets), occorre includere <literal>jboss-seam-debug.jar</literal> nella directory <literal>WEB-INF/lib</literal> del WAR."
#. Tag: para
#: Configuration.xml:586
@@ -1200,7 +1200,7 @@
#: Configuration.xml:589
#, no-c-format
msgid "I really wish that was all there was to say on the topic of configuration but unfortunately we're only about a third of the way there. If you're too overwhelmed by all this tedious configuration stuff, feel free to skip over the rest of this section and come back to it later."
-msgstr ""
+msgstr "Ci piacerebbe aver terminato l'argomento configurazione, ma sfortunatamente siamo solo ad un terzo. Se si è troppo sopraffatti da questo tedioso argomento, si può saltare alla prossima sezione e tornare qua più tardi."
#. Tag: title
#: Configuration.xml:598
@@ -1212,19 +1212,19 @@
#: Configuration.xml:600
#, no-c-format
msgid "Seam is useful even if you're not yet ready to take the plunge into EJB 3.0. In this case you would use Hibernate3 or JPA instead of EJB 3.0 persistence, and plain JavaBeans instead of session beans. You'll miss out on some of the nice features of session beans but it will be very easy to migrate to EJB 3.0 when you're ready and, in the meantime, you'll be able to take advantage of Seam's unique declarative state management architecture."
-msgstr ""
+msgstr "Seam è utile anche se non si è ancora pronti per il grande salto in EJB3.0. In questo caso si usa Hibernate3 o JPA invece della persistenza EJB3.0, ed i JavaBean invece dei bean di sessione. Non si avranno a disposizione alcune funzionalità carine per i session bean, ma sarà molto semplice migrare a EJB3.0 quando si sarà pronti ed allora si potrà sfruttare l'architettura unica di Seam per la gestione dichiarativa dello stato."
#. Tag: para
#: Configuration.xml:615
#, no-c-format
msgid "Seam JavaBean components do not provide declarative transaction demarcation like session beans do. You <emphasis>could</emphasis> manage your transactions manually using the JTA <literal>UserTransaction</literal> or declaratively using Seam's <literal>@Transactional</literal> annotation. But most applications will just use Seam managed transactions when using Hibernate with JavaBeans."
-msgstr ""
+msgstr "I componenti JavaBean di Seam non forniscono la demarcazione dichiarativa delle transazioni come fanno i session bean. Si <emphasis>possono</emphasis> gestire manualmente le transazioni usando <literal>UserTransaction</literal> di JTA od in modo dichiarativo usando l'annotazione <literal>@Transactional</literal> di Seam. Ma la maggior parte delle applicazioni userà solo le transazioni gestite da Seam con Hibernate ed i JavaBean."
#. Tag: para
#: Configuration.xml:621
#, no-c-format
msgid "The Seam distribution includes a version of the booking example application that uses Hibernate3 and JavaBeans instead of EJB3, and another version that uses JPA and JavaBeans. These example applications are ready to deploy into any J2EE application server."
-msgstr ""
+msgstr "La distribuzione Seam include una versione dell'esempio booking che usa Hibernate3 e JavaBean invece di EJB3, ed un'altra versione che usa JPA e JavaBean. Queste applicazioni d'esempio sono pronte per essere deployate in ogni application server J2EE."
#. Tag: title
#: Configuration.xml:626
@@ -1248,7 +1248,7 @@
#: Configuration.xml:633
#, no-c-format
msgid "You will also need to configure a <emphasis>managed session</emphasis> if you want a Seam managed Hibernate <literal>Session</literal> to be available via injection."
-msgstr ""
+msgstr "Occorre anche configurare una <emphasis>sessione gestita</emphasis> se si vuole disponibile via injection una <literal>Session</literal> di Hibernate gestita da Seam."
#. Tag: programlisting
#: Configuration.xml:636
@@ -1270,7 +1270,7 @@
#: Configuration.xml:643
#, no-c-format
msgid "Seam will bootstrap a JPA <literal>EntityManagerFactory</literal> from your <literal>persistence.xml</literal> file if you install this built-in component:"
-msgstr ""
+msgstr "Seam avvierà un <literal>EntityManagerFactory</literal> JPA dal file <literal>persistence.xml</literal> se è stato installato il seguente componente predefinito:"
#. Tag: programlisting
#: Configuration.xml:646
@@ -1282,7 +1282,7 @@
#: Configuration.xml:648
#, no-c-format
msgid "You will also need to configure a <emphasis>managed persistence context</emphasis> if you want a Seam managed JPA <literal>EntityManager</literal> to be available via injection."
-msgstr ""
+msgstr "Occorre anche configurare un <emphasis>contesto di persistenza gestito</emphasis> se si vuole avere disponibile via injection un <literal>EntityManager</literal> JPA gestito da Seam."
#. Tag: programlisting
#: Configuration.xml:651
@@ -1298,7 +1298,7 @@
#: Configuration.xml:658
#, no-c-format
msgid "We can package our application as a WAR, in the following structure:"
-msgstr ""
+msgstr "Si può impacchettare l'applicazione come WAR nella seguente struttura:"
#. Tag: programlisting
#: Configuration.xml:660
@@ -1372,7 +1372,7 @@
#: Configuration.xml:662
#, no-c-format
msgid "If we want to deploy Hibernate in a non-EE environment like Tomcat or TestNG, we need to do a little bit more work."
-msgstr ""
+msgstr "Se si vuole fare ildeploy di Hibernate in un ambiente non EE come Tomcat o TestNG, occorre un pò di lavoro."
#. Tag: title
#: Configuration.xml:669
@@ -1384,7 +1384,7 @@
#: Configuration.xml:671
#, no-c-format
msgid "It is possible to use Seam completely outside of an EE environment. In this case, you need to tell Seam how to manage transactions, since there will be no JTA available. If you're using JPA, you can tell Seam to use JPA resource-local transactions, ie. <literal>EntityTransaction</literal>, like so:"
-msgstr ""
+msgstr "E' possibile usare Seam completamente fuori dall'ambiente EE. In questo caso serve istruire Seam come gestire le transazioni gestire, poiché non sarà disponibile JTA. Se si usa JTA, si può dire a Seam di usare le transazioni resource-local di JTA, cioè <literal>EntityTransaction</literal>, in questo modo:"
#. Tag: programlisting
#: Configuration.xml:675
@@ -1396,7 +1396,7 @@
#: Configuration.xml:677
#, no-c-format
msgid "If you're using Hibernate, you can tell Seam to use the Hibernate transaction API like this:"
-msgstr ""
+msgstr "Se si usa Hibernate, si può dire a Seam di usare l'API transaction di Hibernate in questo modo:"
#. Tag: programlisting
#: Configuration.xml:679
@@ -1426,19 +1426,19 @@
#: Configuration.xml:690
#, no-c-format
msgid "JBoss Embedded lets you run EJB3 components outside the context of the Java EE 5 application server. This is especially, but not only, useful for testing."
-msgstr ""
+msgstr "JBoss Embedded consente di eseguire i componenti EJB3 fuori dal contesto dell'application server Java EE 5. Questo è utile specialmente, ma non solo, per il testing."
#. Tag: para
#: Configuration.xml:693
#, no-c-format
msgid "The Seam booking example application includes a TestNG integration test suite that runs on JBoss Embedded via <literal>SeamTest</literal>."
-msgstr ""
+msgstr "L'applicazione d'esempio booking include la suite d'integrazione per TestNG che esegue JBoss Embedded via <literal>SeamTest</literal>."
#. Tag: para
#: Configuration.xml:705
#, no-c-format
msgid "The booking example application may even be deployed to Tomcat."
-msgstr ""
+msgstr "L'applicazione d'esempio booking può essere deployata via Tomcat."
#. Tag: title
#: Configuration.xml:717
@@ -1450,13 +1450,13 @@
#: Configuration.xml:720
#, no-c-format
msgid "Embedded JBoss must by installed into Tomcat for Seam applications to run correctly on it. Embedded JBoss runs with JDK 5 or JDK 6 ( see <xref linkend=\"jdk_dependencies\"/> for details on using JDK 6). Embedded JBoss can be downloaded <ulink url=\"http://sourceforge.net/project/showfiles.php?group_id=22866&package_i...">here</ulink>. The process for installing Embedded JBoss into Tomcat 6 is quite simple. First, you should copy the Embedded JBoss JARs and configuration files into Tomcat."
-msgstr ""
+msgstr "Embedded JBoss deve essere installato in Tomcat per le eseguire correttamente le applicazioni Seam. Embedded JBoss gira con JDK 5 o JDK 6 (si veda <xref linkend=\"jdk_dependencies\"/> per i dettagli con JDK 6). Embedded JBoss può essere scaricato <ulink url=\"http://sourceforge.net/project/showfiles.php?group_id=22866&package_i...">qua</ulink>. Il processo di installazione di Embedded JBoss in Tomcat 6 è abbastanza semplice. Innanzitutto bisogna copiare i jar di Embedded JBoss ed i file di configurazione in Tomcat."
#. Tag: para
#: Configuration.xml:734
#, no-c-format
msgid "Copy all files and directories under the Embedded JBoss <literal>bootstrap</literal> and <literal>lib</literal> directories, except for the <literal>jndi.properties</literal> file, into the Tomcat <literal>lib</literal> directory."
-msgstr ""
+msgstr "Copiare tutti i file e le directory di Embedded JBoss <literal>bootstrap</literal> e la directory <literal>lib</literal>, tranne il file <literal>jndi.properties</literal>, nella directory di Tomcat <literal>lib</literal>."
#. Tag: para
#: Configuration.xml:741
@@ -1512,7 +1512,7 @@
#: Configuration.xml:761
#, no-c-format
msgid "WAR file scanning should be enabled by adding the <literal>WebinfScanner</literal> listener to <literal>conf/context.xml</literal>:"
-msgstr ""
+msgstr "La scansione del file WAR può essere abilitata aggiungendo il listener <literal>WebinfScanner</literal> in <literal>conf/context.xml</literal>:"
#. Tag: programlisting
#: Configuration.xml:764
@@ -1556,13 +1556,13 @@
#: Configuration.xml:770
#, no-c-format
msgid "If you are using Sun JDK 6, you need to set the Java option <literal>sun.lang.ClassLoader.allowArraySyntax</literal> to <literal>true</literal> in the JAVA_OPTS environment variable used by the Catalina startup script (catalina.bat on Windows or catalina.sh on Unix)."
-msgstr ""
+msgstr "Se si usa Sun JDK 6, occorre impostare l'opzione Java <literal>sun.lang.ClassLoader.allowArraySyntax</literal> a <literal>true</literal> nella variabile d'ambiente JAVA_OPTS usata dallo script di avvio Catalina (catalina.bat in Windows o catalina.sh in Unix)."
#. Tag: para
#: Configuration.xml:775
#, no-c-format
msgid "Open the script appropriate for your operating system in a text editor. Add a new line immediately below the comments at the top of the file where you will define the JAVA_OPTS environment variable. On Windows, use the following syntax:"
-msgstr ""
+msgstr "Aprire in un editor lo script appropriato per il proprio sistema operativo. Aggiungere una nuova linea immediatamente sotto i commenti in cima al file dove verrà definita la variabile d'ambiente JAVA_OPTS. Su Windows, usare la seguente sintassi:"
#. Tag: programlisting
#: Configuration.xml:779
@@ -1592,7 +1592,7 @@
#: Configuration.xml:796
#, no-c-format
msgid "The archive structure of a WAR-based deployment on an servlet engine like Tomcat will look something like this:"
-msgstr ""
+msgstr "La struttura dell'archivio di un deploy basato su WAR per un servlet engine come Tomcat appare in questo modo:"
#. Tag: programlisting
#: Configuration.xml:799
@@ -1668,7 +1668,7 @@
#: Configuration.xml:801
#, no-c-format
msgid "Most of the Seam example applications may be deployed to Tomcat by running <literal>ant deploy.tomcat</literal>."
-msgstr ""
+msgstr "La maggior parte delle applicazioni d'esempio può essere deployata in Tomcat eseguendo <literal>ant deploy.tomcat</literal>."
#. Tag: title
#: Configuration.xml:809
@@ -1680,7 +1680,7 @@
#: Configuration.xml:810
#, no-c-format
msgid "Seam's jBPM integration is not installed by default, so you'll need to enable jBPM by installing a built-in component. You'll also need to explicitly list your process and pageflow definitions. In <literal>components.xml</literal>:"
-msgstr ""
+msgstr "L'integrazione jBPM di Seam non è installata di default, quindi occorre abilitare jBPM installando il componente predefinito. Serve anche elencare esplicitamente le definizioni di processo ed i pageflow. In <literal>components.xml</literal>:"
#. Tag: programlisting
#: Configuration.xml:814
@@ -1712,7 +1712,7 @@
#: Configuration.xml:816
#, no-c-format
msgid "No further special configuration is needed if you only have pageflows. If you do have business process definitions, you need to provide a jBPM configuration, and a Hibernate configuration for jBPM. The Seam DVD Store demo includes example <literal>jbpm.cfg.xml</literal> and <literal>hibernate.cfg.xml</literal> files that will work with Seam:"
-msgstr ""
+msgstr "Non servono ulteriori configurazioni se si usano solo i pageflow. Se si hanno definizioni di processi di business, bisogna fornire una configurazione jBPM ed una configurazione Hibernate per jBPM. La demo Seam DVD Store include i file d'esempio <literal>jbpm.cfg.xml</literal> e <literal>hibernate.cfg.xml</literal> che funzionano con Seam:"
#. Tag: programlisting
#: Configuration.xml:821
@@ -1768,7 +1768,7 @@
#: Configuration.xml:829
#, no-c-format
msgid "There is not yet any well-defined packaging format for jBPM configuration and process/pageflow definition files. In the Seam examples we've decided to simply package all these files into the root of the EAR. In future, we will probably design some other standard packaging format. So the EAR looks something like this:"
-msgstr ""
+msgstr "Non c'è ancora un formato di impacchettamento ben-definito per la configurazione jBPM ed i file di definizione processo/pageflow. Negli esempi Seam si è deciso di impacchettare semplicemente tutti questi file nella directory radice dell'EAR. In future, si progetterà probabilmente un formato standard di impacchettamento. Quindi l'EAR appare così:"
#. Tag: programlisting
#: Configuration.xml:834
@@ -1868,7 +1868,7 @@
#: Configuration.xml:843
#, no-c-format
msgid "It is very important that the timeout for Stateful Session Beans is set higher than the timeout for HTTP Sessions, otherwise SFSB's may time out before the user's HTTP session has ended. JBoss Application Server has a default session bean timeout of 30 minutes, which is configured in <literal>server/default/conf/standardjboss.xml</literal> (replace <emphasis>default</emphasis> with your own configuration)."
-msgstr ""
+msgstr "E' molto importante che il timeout per i bean di sessione stateful sia impostato ad un tempo maggiore del timeout per le sessioni HTTP, altrimenti SFSB può andare in timeout primache la sessione HTTP sia terminata. JBoss AS ha un timeout di default di 30 minuti, che è impostato nel file <literal>server/default/conf/standardjboss.xml</literal> (sostituire <emphasis>default</emphasis>con la propria configurazione)."
#. Tag: para
#: Configuration.xml:849
@@ -1922,7 +1922,7 @@
#: Configuration.xml:854
#, no-c-format
msgid "The default HTTP session timeout can be modified in <literal>server/default/deploy/jbossweb-tomcat55.sar/conf/web.xml</literal> for JBoss 4.0.x, or in <literal>server/default/deploy/jboss-web.deployer/conf/web.xml</literal> for JBoss 4.2.x or later. The following entry in this file controls the default session timeout for all web applications:"
-msgstr ""
+msgstr "Il timeout di default per la sessione HTTP può essere modificato in <literal>server/default/deploy/jbossweb-tomcat55.sar/conf/web.xml</literal> per JBoss 4.0.x, o in <literal>server/default/deploy/jboss-web.deployer/conf/web.xml</literal> per JBoss 4.2.x o successivi. La seguente riga in questo file controlla il timeout di default per la sessione di tutte le applicazioni web:"
#. Tag: programlisting
#: Configuration.xml:859
@@ -1954,7 +1954,7 @@
#: Configuration.xml:869
#, no-c-format
msgid "If you want to run your Seam application in a portlet, take a look at the JBoss Portlet Bridge, an implementation of JSR-301 that supports JSF within a portlet, with extensions for Seam and RichFaces. See <ulink url=\"http://labs.jboss.com/portletbridge\">http://labs.jboss.com/portletbridge</ulink> for more."
-msgstr ""
+msgstr "Se si vogliono eseguire le applicazioni in un portlet, si guardi JBoss Portlet Bridge, un'implementazione di JSR-301 che supporta JSF con i portlet, con estensioni per Seam e RichFaces. Si veda <ulink url=\"http://labs.jboss.com/portletbridge\">http://labs.jboss.com/portletbridge</ulink>."
#. Tag: title
#: Configuration.xml:880
@@ -1972,7 +1972,7 @@
#: Configuration.xml:889
#, no-c-format
msgid "You may also want Seam to handle custom resources. A common use case is to handle a specific annotation and Seam provides specific support for this. First, tell Seam which annotations to handle in <literal>/META-INF/seam-deployment.properties</literal>:"
-msgstr ""
+msgstr "Si potrebbe volere fare gestire a Seam delle risorse personalizzate. Un comune caso d'uso è gestire una specifica annotazione, Seam fornisce un supporto specifico per questo. Innanzitutto, dire a Seam quali annotazioni gestire in <literal>/META-INF/seam-deployment.properties</literal>:"
#. Tag: programlisting
#: Configuration.xml:896
@@ -2053,7 +2053,7 @@
#: Configuration.xml:905
#, no-c-format
msgid "You can also handle <emphasis>any</emphasis> resource. For example, you process any files with the extension <literal>.foo.xml</literal>. To do this, we need to write a custom deployment handler:"
-msgstr ""
+msgstr "Si può gestire <emphasis>qualsiasi</emphasis> risorsa. Per esempio, si processano i file con estensione <literal>.foo.xml</literal>. Per fare questo occorre scrivere un deployment handler personalizzato:"
#. Tag: programlisting
#: Configuration.xml:911
14 years, 11 months
- 1
- 0
Seam SVN: r10950 - branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: milesif
Date: 2009-05-23 09:29:35 -0400 (Sat, 23 May 2009)
New Revision: 10950
Modified:
branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Remoting.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Remoting.po
===================================================================
--- branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Remoting.po 2009-05-23 12:58:13 UTC (rev 10949)
+++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Remoting.po 2009-05-23 13:29:35 UTC (rev 10950)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-05-23 11:30+0000\n"
-"PO-Revision-Date: 2009-05-23 13:44+0100\n"
+"PO-Revision-Date: 2009-05-23 15:27+0100\n"
"Last-Translator: Francesco Milesi <milesif(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -22,25 +22,12 @@
#. Tag: para
#: Remoting.xml:6
#, no-c-format
-msgid ""
-"Seam provides a convenient method of remotely accessing components from a "
-"web page, using AJAX (Asynchronous Javascript and XML). The framework for "
-"this functionality is provided with almost no up-front development effort - "
-"your components only require simple annotating to become accessible via "
-"AJAX. This chapter describes the steps required to build an AJAX-enabled web "
-"page, then goes on to explain the features of the Seam Remoting framework in "
-"more detail."
-msgstr ""
-"Seam fornisce un metodo per accedere in modo remoto i componenti da una "
-"pagina web, usando AJAX (Asynchronous Javascript and XML). Il framework per "
-"questa funzionalità viene fornito con quasi nessuno sforzo di sviluppo - i "
-"componenti richiedono solamente una semplice annotazione per diventare "
-"accessibile via AJAX. Questo capitolo descrive i passi richiesti per "
-"costruire una pagina web abilitata a AJAX, poi spiega con maggior dettaglio "
-"le caratteristiche del framework Seam Remoting."
+msgid "Seam provides a convenient method of remotely accessing components from a web page, using AJAX (Asynchronous Javascript and XML). The framework for this functionality is provided with almost no up-front development effort - your components only require simple annotating to become accessible via AJAX. This chapter describes the steps required to build an AJAX-enabled web page, then goes on to explain the features of the Seam Remoting framework in more detail."
+msgstr "Seam fornisce un metodo per accedere in modo remoto i componenti da una pagina web, usando AJAX (Asynchronous Javascript and XML). Il framework per questa funzionalità viene fornito con quasi nessuno sforzo di sviluppo - i componenti richiedono solamente una semplice annotazione per diventare accessibile via AJAX. Questo capitolo descrive i passi richiesti per costruire una pagina web abilitata a AJAX, poi spiega con maggior dettaglio le caratteristiche del framework Seam Remoting."
#. Tag: title
-#: Remoting.xml:13 Remoting.xml:608
+#: Remoting.xml:13
+#: Remoting.xml:608
#, no-c-format
msgid "Configuration"
msgstr "Configurazione"
@@ -48,12 +35,8 @@
#. Tag: para
#: Remoting.xml:14
#, no-c-format
-msgid ""
-"To use remoting, the Seam Resource servlet must first be configured in your "
-"<literal>web.xml</literal> file:"
-msgstr ""
-"Per usare remoting, il resource servlet di Seam deve essere innanzitutto "
-"configurato nel file <literal>web.xml</literal>:"
+msgid "To use remoting, the Seam Resource servlet must first be configured in your <literal>web.xml</literal> file:"
+msgstr "Per usare remoting, il resource servlet di Seam deve essere innanzitutto configurato nel file <literal>web.xml</literal>:"
#. Tag: programlisting
#: Remoting.xml:16
@@ -82,92 +65,52 @@
#. Tag: para
#: Remoting.xml:18
#, no-c-format
-msgid ""
-"The next step is to import the necessary Javascript into your web page. "
-"There are a minimum of two scripts that must be imported. The first one "
-"contains all the client-side framework code that enables remoting "
-"functionality:"
-msgstr ""
-"Il passo successivi è importare il Javascript necessario nella propria "
-"pagina web. Ci sono un minimo di due script da importare. Il primo contiene "
-"tutto il codice del framework lato client che abilita le funzionalità di "
-"remoting:"
+msgid "The next step is to import the necessary Javascript into your web page. There are a minimum of two scripts that must be imported. The first one contains all the client-side framework code that enables remoting functionality:"
+msgstr "Il passo successivi è importare il Javascript necessario nella propria pagina web. Ci sono un minimo di due script da importare. Il primo contiene tutto il codice del framework lato client che abilita le funzionalità di remoting:"
#. Tag: programlisting
#: Remoting.xml:22
#, no-c-format
-msgid ""
-"<![CDATA[<script type=\"text/javascript\" src=\"seam/resource/remoting/"
-"resource/remote.js\"></script>]]>"
-msgstr ""
-"<![CDATA[<script type=\"text/javascript\" src=\"seam/resource/remoting/"
-"resource/remote.js\"></script>]]>"
+msgid "<![CDATA[<script type=\"text/javascript\" src=\"seam/resource/remoting/resource/remote.js\"></script>]]>"
+msgstr "<![CDATA[<script type=\"text/javascript\" src=\"seam/resource/remoting/resource/remote.js\"></script>]]>"
#. Tag: para
#: Remoting.xml:24
#, no-c-format
-msgid ""
-"The second script contains the stubs and type definitions for the components "
-"you wish to call. It is generated dynamically based on the local interface "
-"of your components, and includes type definitions for all of the classes "
-"that can be used to call the remotable methods of the interface. The name of "
-"the script reflects the name of your component. For example, if you have a "
-"stateless session bean annotated with <literal>@Name(\"customerAction\")</"
-"literal>, then your script tag should look like this:"
-msgstr ""
-"Il secondo script contiene gli stub e le definizioni tipo per i componenti "
-"da chiamare. Viene generato dinamicamente basandosi sull'interfaccia locale "
-"dei propri componenti, ed include le definizioni tipo per tutte le classi "
-"che possono essere usate per chiamare i metodi remoti dell'interfaccia. Il "
-"nome dello script riflette il nome del componente. Per esempio se si ha un "
-"bean di sessione stateless annotato con <literal>@Name(\"customerAction\")</"
-"literal>, allora il tag dello script dovrebbe essere simile a:"
+msgid "The second script contains the stubs and type definitions for the components you wish to call. It is generated dynamically based on the local interface of your components, and includes type definitions for all of the classes that can be used to call the remotable methods of the interface. The name of the script reflects the name of your component. For example, if you have a stateless session bean annotated with <literal>@Name(\"customerAction\")</literal>, then your script tag should look like this:"
+msgstr "Il secondo script contiene gli stub e le definizioni tipo per i componenti da chiamare. Viene generato dinamicamente basandosi sull'interfaccia locale dei propri componenti, ed include le definizioni tipo per tutte le classi che possono essere usate per chiamare i metodi remoti dell'interfaccia. Il nome dello script riflette il nome del componente. Per esempio se si ha un bean di sessione stateless annotato con <literal>@Name(\"customerAction\")</literal>, allora il tag dello script dovrebbe essere simile a:"
#. Tag: programlisting
#: Remoting.xml:30
#, no-c-format
msgid ""
"<![CDATA[<script type=\"text/javascript\" \n"
-" src=\"seam/resource/remoting/interface.js?customerAction\"></"
-"script>]]>"
+" src=\"seam/resource/remoting/interface.js?customerAction\"></script>]]>"
msgstr ""
"<![CDATA[<script type=\"text/javascript\" \n"
-" src=\"seam/resource/remoting/interface.js?customerAction\"></"
-"script>]]>"
+" src=\"seam/resource/remoting/interface.js?customerAction\"></script>]]>"
#. Tag: para
#: Remoting.xml:32
#, no-c-format
-msgid ""
-"If you wish to access more than one component from the same page, then "
-"include them all as parameters of your script tag:"
-msgstr ""
-"Se si vuole accedere a più di un componente dalla stessa pagina, allora li "
-"si includa tutti come parametri nel tag script:"
+msgid "If you wish to access more than one component from the same page, then include them all as parameters of your script tag:"
+msgstr "Se si vuole accedere a più di un componente dalla stessa pagina, allora li si includa tutti come parametri nel tag script:"
#. Tag: programlisting
#: Remoting.xml:35
#, no-c-format
msgid ""
"<![CDATA[<script type=\"text/javascript\" \n"
-" src=\"seam/resource/remoting/interface.js?"
-"customerAction&accountAction\"></script>]]>"
+" src=\"seam/resource/remoting/interface.js?customerAction&accountAction\"></script>]]>"
msgstr ""
"<![CDATA[<script type=\"text/javascript\" \n"
-" src=\"seam/resource/remoting/interface.js?"
-"customerAction&accountAction\"></script>]]>"
+" src=\"seam/resource/remoting/interface.js?customerAction&accountAction\"></script>]]>"
#. Tag: para
#: Remoting.xml:38
#, no-c-format
-msgid ""
-"Alternatively, you may use the <literal>s:remote</literal> tag to import the "
-"required Javascript. Separate each component or class name you wish to "
-"import with a comma:"
-msgstr ""
-"In alternativa si può usare il tag <literal>s:remote</literal> per importare "
-"il Javascript richiesto. Si separi ciascun componente o nome di classe che "
-"si vuole importare con una virgola:"
+msgid "Alternatively, you may use the <literal>s:remote</literal> tag to import the required Javascript. Separate each component or class name you wish to import with a comma:"
+msgstr "In alternativa si può usare il tag <literal>s:remote</literal> per importare il Javascript richiesto. Si separi ciascun componente o nome di classe che si vuole importare con una virgola:"
#. Tag: programlisting
#: Remoting.xml:43
@@ -190,24 +133,8 @@
#. Tag: para
#: Remoting.xml:50
#, no-c-format
-msgid ""
-"Client-side interaction with your components is all performed via the "
-"<literal>Seam</literal> Javascript object. This object is defined in "
-"<literal>remote.js</literal>, and you'll be using it to make asynchronous "
-"calls against your component. It is split into two areas of functionality; "
-"<literal>Seam.Component</literal> contains methods for working with "
-"components and <literal>Seam.Remoting</literal> contains methods for "
-"executing remote requests. The easiest way to become familiar with this "
-"object is to start with a simple example."
-msgstr ""
-"L'interazione lato client con i componenti viene eseguita tutta tramite "
-"l'oggetto Javascript <literal>Seam</literal>. Quest'oggetti è definito in "
-"<literal>remote.js</literal>, e lo si userà per fare chiamate asincrone "
-"verso il componente. E' suddiviso in due aree di funzionalità; <literal>Seam."
-"Component</literal> contiene metodi per lavorare con i componenti e "
-"<literal>Seam.Remoting</literal> contiene metodi per eseguire le richieste "
-"remote. La via più facile per diventare familiare con quest'oggetto è "
-"cominciare con un semplice esempio."
+msgid "Client-side interaction with your components is all performed via the <literal>Seam</literal> Javascript object. This object is defined in <literal>remote.js</literal>, and you'll be using it to make asynchronous calls against your component. It is split into two areas of functionality; <literal>Seam.Component</literal> contains methods for working with components and <literal>Seam.Remoting</literal> contains methods for executing remote requests. The easiest way to become familiar with this object is to start with a simple example."
+msgstr "L'interazione lato client con i componenti viene eseguita tutta tramite l'oggetto Javascript <literal>Seam</literal>. Quest'oggetti è definito in <literal>remote.js</literal>, e lo si userà per fare chiamate asincrone verso il componente. E' suddiviso in due aree di funzionalità; <literal>Seam.Component</literal> contiene metodi per lavorare con i componenti e <literal>Seam.Remoting</literal> contiene metodi per eseguire le richieste remote. La via più facile per diventare familiare con quest'oggetto è cominciare con un semplice esempio."
#. Tag: title
#: Remoting.xml:57
@@ -218,13 +145,8 @@
#. Tag: para
#: Remoting.xml:59
#, no-c-format
-msgid ""
-"Let's step through a simple example to see how the <literal>Seam</literal> "
-"object works. First of all, let's create a new Seam component called "
-"<literal>helloAction</literal>."
-msgstr ""
-"Si cominci con un semplice esempio per vedere come funziona l'oggetto "
-"<literal>Seam</literal>"
+msgid "Let's step through a simple example to see how the <literal>Seam</literal> object works. First of all, let's create a new Seam component called <literal>helloAction</literal>."
+msgstr "Si cominci con un semplice esempio per vedere come funziona l'oggetto <literal>Seam</literal>"
#. Tag: programlisting
#: Remoting.xml:62
@@ -249,14 +171,8 @@
#. Tag: para
#: Remoting.xml:64
#, no-c-format
-msgid ""
-"You also need to create a local interface for our new component - take "
-"special note of the <literal>@WebRemote</literal> annotation, as it's "
-"required to make our method accessible via remoting:"
-msgstr ""
-"E' anche necessario creare un'interfaccia locale per il nuovo componente - "
-"tenete a mente in particolare l'annotazione <literal>@WebRemote</literal>, "
-"poiché è necessaria a rendere un metodo accessibile via remoting:"
+msgid "You also need to create a local interface for our new component - take special note of the <literal>@WebRemote</literal> annotation, as it's required to make our method accessible via remoting:"
+msgstr "E' anche necessario creare un'interfaccia locale per il nuovo componente - tenete a mente in particolare l'annotazione <literal>@WebRemote</literal>, poiché è necessaria a rendere un metodo accessibile via remoting:"
#. Tag: programlisting
#: Remoting.xml:67
@@ -278,30 +194,19 @@
#: Remoting.xml:69
#, no-c-format
msgid "That's all the server-side code we need to write."
-msgstr ""
+msgstr "Quello è tutto il codice da scrivere."
#. Tag: para
#: Remoting.xml:72
#, no-c-format
-msgid ""
-"If you are performing a persistence operation in the method marked "
-"<literal>@WebRemote</literal> you will also need to add a "
-"<literal>@Transactional</literal> annotation to the method. Otherwise, your "
-"method would execute outside of a transaction without this extra hint.That's "
-"because unlike a JSF request, Seam does not wrap the remoting request in a "
-"transaction automatically."
-msgstr ""
+msgid "If you are performing a persistence operation in the method marked <literal>@WebRemote</literal> you will also need to add a <literal>@Transactional</literal> annotation to the method. Otherwise, your method would execute outside of a transaction without this extra hint.That's because unlike a JSF request, Seam does not wrap the remoting request in a transaction automatically."
+msgstr "Se nel metodo annotato con <literal>@WebRemote</literal> viene eseguita un'operazione di persistenza, occorre marcare il metodo anche con l'annotazione <literal>@Transactional</literal>. Altrimenti, senza questa indicazione extra, il metodo non viene eseguito all'interno di una transazione. Ciò perché, a differenza di una richiesta JSF, Seam non include automaticamente una richiesta remota in una transazione."
#. Tag: para
#: Remoting.xml:78
#, fuzzy, no-c-format
-msgid ""
-"Now for our web page - create a new page and import the "
-"<literal>helloAction</literal> component:"
-msgstr ""
-"Questo è tutto il codice lato server che bisogna scrivere. Ora, per quantro "
-"riguarda la pagina web - bisogna creare una nuova pagina e importare il "
-"componente <literal>helloAction</literal>:"
+msgid "Now for our web page - create a new page and import the <literal>helloAction</literal> component:"
+msgstr "Questo è tutto il codice lato server che bisogna scrivere. Ora, per quantro riguarda la pagina web - bisogna creare una nuova pagina e importare il componente <literal>helloAction</literal>:"
#. Tag: programlisting
#: Remoting.xml:81
@@ -312,30 +217,20 @@
#. Tag: para
#: Remoting.xml:83
#, no-c-format
-msgid ""
-"To make this a fully interactive user experience, let's add a button to our "
-"page:"
-msgstr ""
-"Per rendere l'esperienza dell'utente veramente interattiva, si aggiunga un "
-"bottone alla pagina:"
+msgid "To make this a fully interactive user experience, let's add a button to our page:"
+msgstr "Per rendere l'esperienza dell'utente veramente interattiva, si aggiunga un bottone alla pagina:"
#. Tag: programlisting
#: Remoting.xml:85
#, no-c-format
-msgid ""
-"<![CDATA[<button onclick=\"javascript:sayHello()\">Say Hello</button>]]>"
-msgstr ""
-"<![CDATA[<button onclick=\"javascript:sayHello()\">Say Hello</button>]]>"
+msgid "<![CDATA[<button onclick=\"javascript:sayHello()\">Say Hello</button>]]>"
+msgstr "<![CDATA[<button onclick=\"javascript:sayHello()\">Say Hello</button>]]>"
#. Tag: para
#: Remoting.xml:87
#, no-c-format
-msgid ""
-"We'll also need to add some more script to make our button actually do "
-"something when it's clicked:"
-msgstr ""
-"Bisognerà anche aggiungere uno script per far fare qualcosa al bottone "
-"quando viene cliccato:"
+msgid "We'll also need to add some more script to make our button actually do something when it's clicked:"
+msgstr "Bisognerà anche aggiungere uno script per far fare qualcosa al bottone quando viene cliccato:"
#. Tag: programlisting
#: Remoting.xml:89
@@ -346,8 +241,7 @@
"\n"
" function sayHello() {\n"
" var name = prompt(\"What is your name?\");\n"
-" Seam.Component.getInstance(\"helloAction\").sayHello(name, "
-"sayHelloCallback);\n"
+" Seam.Component.getInstance(\"helloAction\").sayHello(name, sayHelloCallback);\n"
" }\n"
"\n"
" function sayHelloCallback(result) {\n"
@@ -362,8 +256,7 @@
"\n"
" function sayHello() {\n"
" var name = prompt(\"What is your name?\");\n"
-" Seam.Component.getInstance(\"helloAction\").sayHello(name, "
-"sayHelloCallback);\n"
+" Seam.Component.getInstance(\"helloAction\").sayHello(name, sayHelloCallback);\n"
" }\n"
"\n"
" function sayHelloCallback(result) {\n"
@@ -376,94 +269,38 @@
#. Tag: para
#: Remoting.xml:91
#, no-c-format
-msgid ""
-"We're done! Deploy your application and browse to your page. Click the "
-"button, and enter a name when prompted. A message box will display the hello "
-"message confirming that the call was successful. If you want to save some "
-"time, you'll find the full source code for this Hello World example in "
-"Seam's <literal>/examples/remoting/helloworld</literal> directory."
-msgstr ""
-"Abbiamo finito! Installate l'applicazione e andate col browser alla pagina "
-"creata. Premete il pulsante e inserite un nome quando richiesto. Una "
-"finestra mostrerà il messaggio di saluto che confermerà che la chiamata è "
-"avvenuta con successo. Per risparmiare tempo, cercate il codice dell'esempio "
-"Hello World nella directory <literal>/examples/remoting/helloworld</literal> "
-"di Seam."
+msgid "We're done! Deploy your application and browse to your page. Click the button, and enter a name when prompted. A message box will display the hello message confirming that the call was successful. If you want to save some time, you'll find the full source code for this Hello World example in Seam's <literal>/examples/remoting/helloworld</literal> directory."
+msgstr "Abbiamo finito! Installate l'applicazione e andate col browser alla pagina creata. Premete il pulsante e inserite un nome quando richiesto. Una finestra mostrerà il messaggio di saluto che confermerà che la chiamata è avvenuta con successo. Per risparmiare tempo, cercate il codice dell'esempio Hello World nella directory <literal>/examples/remoting/helloworld</literal> di Seam."
#. Tag: para
#: Remoting.xml:96
#, no-c-format
-msgid ""
-"So what does the code of our script actually do? Let's break it down into "
-"smaller pieces. To start with, you can see from the Javascript code listing "
-"that we have implemented two methods - the first method is responsible for "
-"prompting the user for their name and then making a remote request. Take a "
-"look at the following line:"
-msgstr ""
-"Quindi, cosa fa realmente il codice del nostro script? Dividiamolo in pezzi "
-"più piccoli. Tanto per iniziare, dal listato Javascript si vede che abbiamo "
-"implementato due metodi - il primo serve a chiedere all'utente il suo nome e "
-"a fare una richiesta remota. Guardate la seguente linea:"
+msgid "So what does the code of our script actually do? Let's break it down into smaller pieces. To start with, you can see from the Javascript code listing that we have implemented two methods - the first method is responsible for prompting the user for their name and then making a remote request. Take a look at the following line:"
+msgstr "Quindi, cosa fa realmente il codice del nostro script? Dividiamolo in pezzi più piccoli. Tanto per iniziare, dal listato Javascript si vede che abbiamo implementato due metodi - il primo serve a chiedere all'utente il suo nome e a fare una richiesta remota. Guardate la seguente linea:"
#. Tag: programlisting
#: Remoting.xml:101
#, no-c-format
-msgid ""
-"Seam.Component.getInstance(\"helloAction\").sayHello(name, sayHelloCallback);"
-msgstr ""
-"Seam.Component.getInstance(\"helloAction\").sayHello(name, sayHelloCallback);"
+msgid "Seam.Component.getInstance(\"helloAction\").sayHello(name, sayHelloCallback);"
+msgstr "Seam.Component.getInstance(\"helloAction\").sayHello(name, sayHelloCallback);"
#. Tag: para
#: Remoting.xml:103
#, no-c-format
-msgid ""
-"The first section of this line, <literal>Seam.Component.getInstance"
-"(\"helloAction\")</literal> returns a proxy, or \"stub\" for our "
-"<literal>helloAction</literal> component. We can invoke the methods of our "
-"component against this stub, which is exactly what happens with the "
-"remainder of the line: <literal>sayHello(name, sayHelloCallback);</literal>."
-msgstr ""
-"La prima parte di questa linea, <literal>Seam.Component.getInstance"
-"(\"helloAction\")</literal> restituisce un proxy, o \"stub\", del componente "
-"<literal>helloAction</literal>. Possiamo chiamare i metodi di questo "
-"componente usando tale stub, che è ciò che accade nel resto della linea: "
-"<literal>sayHello(name, sayHelloCallback);</literal>."
+msgid "The first section of this line, <literal>Seam.Component.getInstance(\"helloAction\")</literal> returns a proxy, or \"stub\" for our <literal>helloAction</literal> component. We can invoke the methods of our component against this stub, which is exactly what happens with the remainder of the line: <literal>sayHello(name, sayHelloCallback);</literal>."
+msgstr "La prima parte di questa linea, <literal>Seam.Component.getInstance(\"helloAction\")</literal> restituisce un proxy, o \"stub\", del componente <literal>helloAction</literal>. Possiamo chiamare i metodi di questo componente usando tale stub, che è ciò che accade nel resto della linea: <literal>sayHello(name, sayHelloCallback);</literal>."
#. Tag: para
#: Remoting.xml:108
#, no-c-format
-msgid ""
-"What this line of code in its completeness does, is invoke the "
-"<literal>sayHello</literal> method of our component, passing in "
-"<literal>name</literal> as a parameter. The second parameter, "
-"<literal>sayHelloCallback</literal> isn't a parameter of our component's "
-"<literal>sayHello</literal> method, instead it tells the Seam Remoting "
-"framework that once it receives the response to our request, it should pass "
-"it to the <literal>sayHelloCallback</literal> Javascript method. This "
-"callback parameter is entirely optional, so feel free to leave it out if "
-"you're calling a method with a <literal>void</literal> return type or if you "
-"don't care about the result."
-msgstr ""
-"Nel suo complesso questa linea di codice invoca il metodo <literal>sayHello</"
-"literal> del componente, passandogli <literal>name</literal> come parametro. "
-"Il secondo parametro, <literal>sayHelloCallback</literal> non è un parametro "
-"del metodo <literal>sayHello</literal> del componente, ma, invece, comunica "
-"al Remoting framework di Seam che, una volta ricevuta la risposta alla "
-"richiesta, deve passarla al metodo Javascript <literal>sayHelloCallback</"
-"literal>. Questo parametro di callback è completamente opzionale, quindi "
-"sentitevi liberi di non usarlo se chiamate un metodo che restituisce "
-"<literal>void</literal> o se non siete interessati al risultato."
+msgid "What this line of code in its completeness does, is invoke the <literal>sayHello</literal> method of our component, passing in <literal>name</literal> as a parameter. The second parameter, <literal>sayHelloCallback</literal> isn't a parameter of our component's <literal>sayHello</literal> method, instead it tells the Seam Remoting framework that once it receives the response to our request, it should pass it to the <literal>sayHelloCallback</literal> Javascript method. This callback parameter is entirely optional, so feel free to leave it out if you're calling a method with a <literal>void</literal> return type or if you don't care about the result."
+msgstr "Nel suo complesso questa linea di codice invoca il metodo <literal>sayHello</literal> del componente, passandogli <literal>name</literal> come parametro. Il secondo parametro, <literal>sayHelloCallback</literal> non è un parametro del metodo <literal>sayHello</literal> del componente, ma, invece, comunica al Remoting framework di Seam che, una volta ricevuta la risposta alla richiesta, deve passarla al metodo Javascript <literal>sayHelloCallback</literal>. Questo parametro di callback è completamente opzionale, quindi sentitevi liberi di non usarlo se chiamate un metodo che restituisce <literal>void</literal> o se non siete interessati al risultato."
#. Tag: para
#: Remoting.xml:116
#, no-c-format
-msgid ""
-"The <literal>sayHelloCallback</literal> method, once receiving the response "
-"to our remote request then pops up an alert message displaying the result of "
-"our method call."
-msgstr ""
-"Il metodo <literal>sayHelloCallback</literal>, una volta ricevuta la "
-"risposta, mostra un messaggio di avviso con il risultato della chiamata."
+msgid "The <literal>sayHelloCallback</literal> method, once receiving the response to our remote request then pops up an alert message displaying the result of our method call."
+msgstr "Il metodo <literal>sayHelloCallback</literal>, una volta ricevuta la risposta, mostra un messaggio di avviso con il risultato della chiamata."
#. Tag: title
#: Remoting.xml:122
@@ -474,23 +311,8 @@
#. Tag: para
#: Remoting.xml:124
#, no-c-format
-msgid ""
-"The <literal>Seam.Component</literal> Javascript object provides a number of "
-"client-side methods for working with your Seam components. The two main "
-"methods, <literal>newInstance()</literal> and <literal>getInstance()</"
-"literal> are documented in the following sections however their main "
-"difference is that <literal>newInstance()</literal> will always create a new "
-"instance of a component type, and <literal>getInstance()</literal> will "
-"return a singleton instance."
-msgstr ""
-"L'oggetto Javascript <literal>Seam.Component</literal> fornisce un serie di "
-"metodi lato client per lavorare con i componenti Seam dell'applicazione. I "
-"due metodi principali, <literal>newInstance()</literal> e "
-"<literal>getInstance()</literal> sono documentati nelle sezioni successive, "
-"comunque, la loro differenza principale sta nel fatto che "
-"<literal>newInstance()</literal> crea sempre una nuova istanza di un tipo di "
-"componente, mentre <literal>getInstance()</literal> restituisce un'istanza "
-"singleton."
+msgid "The <literal>Seam.Component</literal> Javascript object provides a number of client-side methods for working with your Seam components. The two main methods, <literal>newInstance()</literal> and <literal>getInstance()</literal> are documented in the following sections however their main difference is that <literal>newInstance()</literal> will always create a new instance of a component type, and <literal>getInstance()</literal> will return a singleton instance."
+msgstr "L'oggetto Javascript <literal>Seam.Component</literal> fornisce un serie di metodi lato client per lavorare con i componenti Seam dell'applicazione. I due metodi principali, <literal>newInstance()</literal> e <literal>getInstance()</literal> sono documentati nelle sezioni successive, comunque, la loro differenza principale sta nel fatto che <literal>newInstance()</literal> crea sempre una nuova istanza di un tipo di componente, mentre <literal>getInstance()</literal> restituisce un'istanza singleton."
#. Tag: title
#: Remoting.xml:131
@@ -501,12 +323,8 @@
#. Tag: para
#: Remoting.xml:132
#, no-c-format
-msgid ""
-"Use this method to create a new instance of an entity or Javabean component. "
-"The object returned by this method will have the same getter/setter methods "
-"as its server-side counterpart, or alternatively if you wish you can access "
-"its fields directly. Take the following Seam entity component for example:"
-msgstr ""
+msgid "Use this method to create a new instance of an entity or Javabean component. The object returned by this method will have the same getter/setter methods as its server-side counterpart, or alternatively if you wish you can access its fields directly. Take the following Seam entity component for example:"
+msgstr "Usate questo metodo per creare una nuova istanza di un entity o di un componente Javabean. L'oggetto restituito da questo metodo avrà gli stessi metodi get/set della sua controparte lato server, o, di preferenza, sarà possibile accedere ai suoi campi direttamente. Ad esempio, prendete il seguente componente Seam:"
#. Tag: programlisting
#: Remoting.xml:136
@@ -582,7 +400,7 @@
#: Remoting.xml:138
#, no-c-format
msgid "To create a client-side Customer you would write the following code:"
-msgstr ""
+msgstr "Per creare un Customer lato client, bisognerebbe scrivere il codice seguente:"
#. Tag: programlisting
#: Remoting.xml:140
@@ -594,7 +412,7 @@
#: Remoting.xml:142
#, no-c-format
msgid "Then from here you can set the fields of the customer object:"
-msgstr ""
+msgstr "Allora da qui è possibile valorizzare i campi dell'oggetto customer:"
#. Tag: programlisting
#: Remoting.xml:144
@@ -617,23 +435,14 @@
#. Tag: para
#: Remoting.xml:151
#, no-c-format
-msgid ""
-"The <literal>getInstance()</literal> method is used to get a reference to a "
-"Seam session bean component stub, which can then be used to remotely execute "
-"methods against your component. This method returns a singleton for the "
-"specified component, so calling it twice in a row with the same component "
-"name will return the same instance of the component."
-msgstr ""
+msgid "The <literal>getInstance()</literal> method is used to get a reference to a Seam session bean component stub, which can then be used to remotely execute methods against your component. This method returns a singleton for the specified component, so calling it twice in a row with the same component name will return the same instance of the component."
+msgstr "Il metodo <literal>getInstance()</literal> viene usato per ottenere un riferimento allo stub di un componente Seam di tipo session bean, che può essere utilizzato per eseguire chiamate remote al componente stesso. Questo metodo restituisce un singleton del componente specificato, così che chiamarlo due volte di fila passando lo stesso nome come parametro restituirà la stessa istanza del suddetto componente."
#. Tag: para
#: Remoting.xml:156
#, no-c-format
-msgid ""
-"To continue our example from before, if we have created a new "
-"<literal>customer</literal> and we now wish to save it, we would pass it to "
-"the <literal>saveCustomer()</literal> method of our <literal>customerAction</"
-"literal> component:"
-msgstr ""
+msgid "To continue our example from before, if we have created a new <literal>customer</literal> and we now wish to save it, we would pass it to the <literal>saveCustomer()</literal> method of our <literal>customerAction</literal> component:"
+msgstr "Per continuare l'esempio precedente, se è stato creato un nuovo <literal>customer</literal> e si vuole salvarlo, occorre passarlo al metodo <literal>saveCustomer()</literal> del componente <literal>customerAction</literal>:"
#. Tag: programlisting
#: Remoting.xml:160
@@ -650,10 +459,8 @@
#. Tag: para
#: Remoting.xml:166
#, no-c-format
-msgid ""
-"Passing an object into this method will return its component name if it is a "
-"component, or <literal>null</literal> if it is not."
-msgstr ""
+msgid "Passing an object into this method will return its component name if it is a component, or <literal>null</literal> if it is not."
+msgstr "Passare un oggetto a questo metodo, restituirà il suo nome di componente, se è un componente, o <literal>null</literal> se non lo è."
#. Tag: programlisting
#: Remoting.xml:169
@@ -678,12 +485,8 @@
#. Tag: para
#: Remoting.xml:177
#, no-c-format
-msgid ""
-"Most of the client side functionality for Seam Remoting is contained within "
-"the <literal>Seam.Remoting</literal> object. While you shouldn't need to "
-"directly call most of its methods, there are a couple of important ones "
-"worth mentioning."
-msgstr ""
+msgid "Most of the client side functionality for Seam Remoting is contained within the <literal>Seam.Remoting</literal> object. While you shouldn't need to directly call most of its methods, there are a couple of important ones worth mentioning."
+msgstr "La maggior parte delle funzionalità lato client di Seam Remoting sono contenute nell'oggetto <literal>Seam.Remoting</literal>. Mentre non dovrebbe essere necessario chiamare direttamente la maggior parte di questi metodi, ce ne sono un paio che meritano di essere menzionati per la loro importanza."
#. Tag: title
#: Remoting.xml:182
@@ -694,13 +497,8 @@
#. Tag: para
#: Remoting.xml:184
#, no-c-format
-msgid ""
-"If your application contains or uses Javabean classes that aren't Seam "
-"components, you may need to create these types on the client side to pass as "
-"parameters into your component method. Use the <literal>createType()</"
-"literal> method to create an instance of your type. Pass in the fully "
-"qualified Java class name as a parameter:"
-msgstr ""
+msgid "If your application contains or uses Javabean classes that aren't Seam components, you may need to create these types on the client side to pass as parameters into your component method. Use the <literal>createType()</literal> method to create an instance of your type. Pass in the fully qualified Java class name as a parameter:"
+msgstr "Se l'applicazione contiene o usa classi Javabean che non sono componenti Seam, potrebbe essere necessario creare questi tipi sul lato del client per passarli come parametri al metodo del componente che si vuole chiamare. Si usi il metodo <literal>createType()</literal> per creare un'istanza di tale tipo. Come parametro occore passare il nome completo della classe Java:"
#. Tag: programlisting
#: Remoting.xml:189
@@ -717,12 +515,8 @@
#. Tag: para
#: Remoting.xml:195
#, no-c-format
-msgid ""
-"This method is the equivalent of <literal>Seam.Component.getComponentName()</"
-"literal> but for non-component types. It will return the name of the type "
-"for an object instance, or <literal>null</literal> if the type is not known. "
-"The name is the fully qualified name of the type's Java class."
-msgstr ""
+msgid "This method is the equivalent of <literal>Seam.Component.getComponentName()</literal> but for non-component types. It will return the name of the type for an object instance, or <literal>null</literal> if the type is not known. The name is the fully qualified name of the type's Java class."
+msgstr "Tale metodo è l'equivalente di <literal>Seam.Component.getComponentName()</literal> ma per tipi che non sono componenti. Restituirà il nome del tipo data un'istanza, o <literal>null</literal> se il tipo è sconosciuto. Il nome è il nome completo della classe Java del tipo stesso."
#. Tag: title
#: Remoting.xml:203
@@ -733,15 +527,8 @@
#. Tag: para
#: Remoting.xml:205
#, no-c-format
-msgid ""
-"Seam Remoting also supports the evaluation of EL expressions, which provides "
-"another convenient method for retrieving data from the server. Using the "
-"<literal>Seam.Remoting.eval()</literal> function, an EL expression can be "
-"remotely evaluated on the server and the resulting value returned to a "
-"client-side callback method. This function accepts two parameters, the first "
-"being the EL expression to evaluate, and the second being the callback "
-"method to invoke with the value of the expression. Here's an example:"
-msgstr ""
+msgid "Seam Remoting also supports the evaluation of EL expressions, which provides another convenient method for retrieving data from the server. Using the <literal>Seam.Remoting.eval()</literal> function, an EL expression can be remotely evaluated on the server and the resulting value returned to a client-side callback method. This function accepts two parameters, the first being the EL expression to evaluate, and the second being the callback method to invoke with the value of the expression. Here's an example:"
+msgstr "Seam Remoting supporta anche il calcolo di espressioni EL, che forniscono un altro metodo conveniente per ottenere dati dal server. Usando la funzione <literal>Seam.Remoting.eval()</literal>, è possibile calcolare un'espressione EL da remoto sul server e restituire il valore risultante a un metodo callback lato del client. Questa funzione accetta due parametri, di cui il primo è l'espressione EL da calcolare e il secondo il metodo callback da invocare con il valore dell'espressione. Ecco un esempio:"
#. Tag: programlisting
#: Remoting.xml:213
@@ -768,16 +555,8 @@
#. Tag: para
#: Remoting.xml:215
#, no-c-format
-msgid ""
-"In this example, the expression <literal>#{customers}</literal> is evaluated "
-"by Seam, and the value of the expression (in this case a list of Customer "
-"objects) is returned to the <literal>customersCallback()</literal> method. "
-"It is important to remember that the objects returned this way must have "
-"their types imported (via <literal>s:remote</literal>) to be able to work "
-"with them in Javascript. So to work with a list of <literal>customer</"
-"literal> objects, it is required to import the <literal>customer</literal> "
-"type:"
-msgstr ""
+msgid "In this example, the expression <literal>#{customers}</literal> is evaluated by Seam, and the value of the expression (in this case a list of Customer objects) is returned to the <literal>customersCallback()</literal> method. It is important to remember that the objects returned this way must have their types imported (via <literal>s:remote</literal>) to be able to work with them in Javascript. So to work with a list of <literal>customer</literal> objects, it is required to import the <literal>customer</literal> type:"
+msgstr "In questo esempio l'espressione <literal>#{customers}</literal> è calcolata da Seam, e il suo valore (in questo caso una lista di oggetti customer) è restituita al metodo <literal>customersCallback()</literal>. E' importante ricordare che occorre importare i tipi degli oggetti restituiti in questo modo (via <literal>s:remote</literal>) per poterli usare nel Javascript. Così per lavorare con una lista di oggetti <literal>customer</literal>, è necessario importare il tipo <literal>customer</literal>:"
#. Tag: programlisting
#: Remoting.xml:223
@@ -794,24 +573,18 @@
#. Tag: para
#: Remoting.xml:229
#, no-c-format
-msgid ""
-"In the configuration section above, the interface, or \"stub\" for our "
-"component is imported into our page either via <literal>seam/resource/"
-"remoting/interface.js</literal>: or using the <literal>s:remote</literal> "
-"tag:"
-msgstr ""
+msgid "In the configuration section above, the interface, or \"stub\" for our component is imported into our page either via <literal>seam/resource/remoting/interface.js</literal>: or using the <literal>s:remote</literal> tag:"
+msgstr "Nella sezione di configurazione vista sopra, l'interfaccia, o \"stub\", del componente è importata nella pagina o attraverso <literal>seam/resource/remoting/interface.js</literal> o usando la tag <literal>s:remote</literal>."
#. Tag: programlisting
#: Remoting.xml:234
#, no-c-format
msgid ""
"<![CDATA[<script type=\"text/javascript\" \n"
-" src=\"seam/resource/remoting/interface.js?customerAction\"></"
-"script>]]>"
+" src=\"seam/resource/remoting/interface.js?customerAction\"></script>]]>"
msgstr ""
"<![CDATA[<script type=\"text/javascript\" \n"
-" src=\"seam/resource/remoting/interface.js?customerAction\"></"
-"script>]]>"
+" src=\"seam/resource/remoting/interface.js?customerAction\"></script>]]>"
#. Tag: programlisting
#: Remoting.xml:236
@@ -822,38 +595,20 @@
#. Tag: para
#: Remoting.xml:238
#, no-c-format
-msgid ""
-"By including this script in our page, the interface definitions for our "
-"component, plus any other components or types that are required to execute "
-"the methods of our component are generated and made available for the "
-"remoting framework to use."
-msgstr ""
+msgid "By including this script in our page, the interface definitions for our component, plus any other components or types that are required to execute the methods of our component are generated and made available for the remoting framework to use."
+msgstr "Includenco questo script nella pagina, le definizioni delle interfacce del componente, più quelle di ogni di ogni altro componente o tipo necessario a eseguire i metodi del componente in questione sono generate e rese visibili perché il framework di remoting possa utilizzarle."
#. Tag: para
#: Remoting.xml:242
#, no-c-format
-msgid ""
-"There are two types of client stub that can be generated, \"executable\" "
-"stubs and \"type\" stubs. Executable stubs are behavioural, and are used to "
-"execute methods against your session bean components, while type stubs "
-"contain state and represent the types that can be passed in as parameters or "
-"returned as a result."
-msgstr ""
+msgid "There are two types of client stub that can be generated, \"executable\" stubs and \"type\" stubs. Executable stubs are behavioural, and are used to execute methods against your session bean components, while type stubs contain state and represent the types that can be passed in as parameters or returned as a result."
+msgstr "E' possibile generare due tipi di stub client, stubs \"eseguibili\" stubs e stubs \"tipo\". Gli stubs eseguibili sono dotati di comportamento, e sono usati per eseguire metodi dei componenti session bean, mentre gli stubs tipo servono a contenere dello stato e rappresentano i tipi che possono essere passati come parametri o restituiti come risultati."
#. Tag: para
#: Remoting.xml:246
#, no-c-format
-msgid ""
-"The type of client stub that is generated depends on the type of your Seam "
-"component. If the component is a session bean, then an executable stub will "
-"be generated, otherwise if it's an entity or JavaBean, then a type stub will "
-"be generated. There is one exception to this rule; if your component is a "
-"JavaBean (ie it is not a session bean nor an entity bean) and any of its "
-"methods are annotated with @WebRemote, then an executable stub will be "
-"generated for it instead of a type stub. This allows you to use remoting to "
-"call methods of your JavaBean components in a non-EJB environment where you "
-"don't have access to session beans."
-msgstr ""
+msgid "The type of client stub that is generated depends on the type of your Seam component. If the component is a session bean, then an executable stub will be generated, otherwise if it's an entity or JavaBean, then a type stub will be generated. There is one exception to this rule; if your component is a JavaBean (ie it is not a session bean nor an entity bean) and any of its methods are annotated with @WebRemote, then an executable stub will be generated for it instead of a type stub. This allows you to use remoting to call methods of your JavaBean components in a non-EJB environment where you don't have access to session beans."
+msgstr "Il tipo di stub client che viene generato dipende dal tipo di componente Seam. Se il componente è un session bean, allora sarà generato uno stub eseguibile, altrimenti, se si tratta di un entity bean o di un Java bean, sarò generato uno stub tipo. Vi è una sola eccezione a questa regola; se il componente è un Javabean (cioè non è né un session bean né un entity bean) e uno dei suoi metodi è annotato con @WebRemote, allora sarà generato uno stub eseguibile invece di uno stub tipo. Questo consente di usare il remoting per chiamare i componenti JavaBean in un ambiente non EJB dove non occorre avere accesso ai session bean."
#. Tag: title
#: Remoting.xml:256
@@ -864,11 +619,8 @@
#. Tag: para
#: Remoting.xml:258
#, no-c-format
-msgid ""
-"The Seam Remoting Context contains additional information which is sent and "
-"received as part of a remoting request/response cycle. At this stage it only "
-"contains the conversation ID but may be expanded in the future."
-msgstr ""
+msgid "The Seam Remoting Context contains additional information which is sent and received as part of a remoting request/response cycle. At this stage it only contains the conversation ID but may be expanded in the future."
+msgstr "L'oggetto contesto (Seam Remoting Context) contiene informazioni aggiuntive che sono inviate e ricevute come parte del ciclo di richiesta/risposta. Attualmente contiene l'id della conversazione, ma potrebbe essere espanso in futuro."
#. Tag: title
#: Remoting.xml:262
@@ -879,54 +631,32 @@
#. Tag: para
#: Remoting.xml:265
#, no-c-format
-msgid ""
-"If you intend on using remote calls within the scope of a conversation then "
-"you need to be able to read or set the conversation ID in the Seam Remoting "
-"Context. To read the conversation ID after making a remote request call "
-"<literal>Seam.Remoting.getContext().getConversationId()</literal>. To set "
-"the conversation ID before making a request, call <literal>Seam.Remoting."
-"getContext().setConversationId()</literal>."
-msgstr ""
+msgid "If you intend on using remote calls within the scope of a conversation then you need to be able to read or set the conversation ID in the Seam Remoting Context. To read the conversation ID after making a remote request call <literal>Seam.Remoting.getContext().getConversationId()</literal>. To set the conversation ID before making a request, call <literal>Seam.Remoting.getContext().setConversationId()</literal>."
+msgstr "Se si vuole usare le chiamate remote all'interno di una conversazione, bisogna essere in grado di leggere o scrivere l'id della conversazione nell'oggetto contesto (Seam Remoting Context). Per leggere l'id della conversazione dopo avere fatto una richiesta remota occorre chiamare <literal>Seam.Remoting.getContext().getConversationId()</literal>. Per scriverlo prima di fare una richiesta, bisogna chiamare <literal>Seam.Remoting.getContext().setConversationId()</literal>."
#. Tag: para
#: Remoting.xml:270
#, no-c-format
-msgid ""
-"If the conversation ID hasn't been explicitly set with <literal>Seam."
-"Remoting.getContext().setConversationId()</literal>, then it will be "
-"automatically assigned the first valid conversation ID that is returned by "
-"any remoting call. If you are working with multiple conversations within "
-"your page, then you may need to explicitly set the conversation ID before "
-"each call. If you are working with just a single conversation, then you "
-"don't need to do anything special."
-msgstr ""
+msgid "If the conversation ID hasn't been explicitly set with <literal>Seam.Remoting.getContext().setConversationId()</literal>, then it will be automatically assigned the first valid conversation ID that is returned by any remoting call. If you are working with multiple conversations within your page, then you may need to explicitly set the conversation ID before each call. If you are working with just a single conversation, then you don't need to do anything special."
+msgstr "Se l'ID della conversazione non è stato esplicitamente valorizzato usando <literal>Seam.Remoting.getContext().setConversationId()</literal>, allora sarà assegnato in automatico il primo ID valido restituito da una chiamata remota. Se si sta lavorando con più conversazioni all'interno della pagina, allora può essere necessario indicare esplicitamente il valore dell'ID della conversazione prima di ciascuna chiamata. Se si sta lavorando con una sola conversazione, non occorre fare nulla di speciale."
#. Tag: title
#: Remoting.xml:277
#, no-c-format
msgid "Remote calls within the current conversation scope"
-msgstr ""
+msgstr "Chiamate remote all'interno della conversazone corrente"
#. Tag: para
#: Remoting.xml:279
#, no-c-format
-msgid ""
-"In some circumstances it may be required to make a remote call within the "
-"scope of the current view's conversation. To do this, you must explicitly "
-"set the conversation ID to that of the view before making the remote call. "
-"This small snippet of JavaScript will set the conversation ID that is used "
-"for remoting calls to the current view's conversation ID:"
-msgstr ""
+msgid "In some circumstances it may be required to make a remote call within the scope of the current view's conversation. To do this, you must explicitly set the conversation ID to that of the view before making the remote call. This small snippet of JavaScript will set the conversation ID that is used for remoting calls to the current view's conversation ID:"
+msgstr "In alcuni casi può essere necessario fare una chiamata remota all'interno della conversazione della pagina corrente. A questo scopo bisogna esplicitamente valorizzare l'ID della conversazione a quello della pagina prima di fare la chiamata remota. Questo piccolo estratto di Javascript assegna come ID della conversazione da usare per le chiamate remote quello della conversazione della pagina corrente:"
#. Tag: programlisting
#: Remoting.xml:284
#, no-c-format
-msgid ""
-"<![CDATA[Seam.Remoting.getContext().setConversationId( #{conversation."
-"id} );]]>"
-msgstr ""
-"<![CDATA[Seam.Remoting.getContext().setConversationId( #{conversation."
-"id} );]]>"
+msgid "<![CDATA[Seam.Remoting.getContext().setConversationId( #{conversation.id} );]]>"
+msgstr "<![CDATA[Seam.Remoting.getContext().setConversationId( #{conversation.id} );]]>"
#. Tag: title
#: Remoting.xml:289
@@ -937,44 +667,26 @@
#. Tag: para
#: Remoting.xml:291
#, no-c-format
-msgid ""
-"Seam Remoting allows multiple component calls to be executed within a single "
-"request. It is recommended that this feature is used wherever it is "
-"appropriate to reduce network traffic."
-msgstr ""
+msgid "Seam Remoting allows multiple component calls to be executed within a single request. It is recommended that this feature is used wherever it is appropriate to reduce network traffic."
+msgstr "Seam Remoting permette di eseguire più chiamate a componenti all'interno di una singola richiesta. Si raccomanda di usare questa funzionalità ogni volta che si riveli appropriato allo scopo di ridurre il traffico di rete."
#. Tag: para
#: Remoting.xml:294
#, no-c-format
-msgid ""
-"The method <literal>Seam.Remoting.startBatch()</literal> will start a new "
-"batch, and any component calls executed after starting a batch are queued, "
-"rather than being sent immediately. When all the desired component calls "
-"have been added to the batch, the <literal>Seam.Remoting.executeBatch()</"
-"literal> method will send a single request containing all of the queued "
-"calls to the server, where they will be executed in order. After the calls "
-"have been executed, a single response containining all return values will be "
-"returned to the client and the callback functions (if provided) triggered in "
-"the same order as execution."
-msgstr ""
+msgid "The method <literal>Seam.Remoting.startBatch()</literal> will start a new batch, and any component calls executed after starting a batch are queued, rather than being sent immediately. When all the desired component calls have been added to the batch, the <literal>Seam.Remoting.executeBatch()</literal> method will send a single request containing all of the queued calls to the server, where they will be executed in order. After the calls have been executed, a single response containining all return values will be returned to the client and the callback functions (if provided) triggered in the same order as execution."
+msgstr "Il metodo <literal>Seam.Remoting.startBatch()</literal> avvierà un nuovo batch, e tutte le chiamate a componenti eseguite in seguito saranno messe in coda invece che inviate immediatamente. Quando tutte le chiamate desiderate saranno state aggiunte al batch, il metodo <literal>Seam.Remoting.executeBatch()</literal> invierà una singola richiesta con la coda delle chiamate al server, dove saranno eseguite nell'ordine specificato. Dopo l'esecuzione delle chiamate, una singola risposta con tutti i valori di ritorno sarà restituita al client e le funzioni callback (se specificate) saranno chiamate nello steso ordine di esecuzione."
#. Tag: para
#: Remoting.xml:301
#, no-c-format
-msgid ""
-"If you start a new batch via the <literal>startBatch()</literal> method but "
-"then decide you don't want to send it, the <literal>Seam.Remoting.cancelBatch"
-"()</literal> method will discard any calls that were queued and exit the "
-"batch mode."
-msgstr ""
+msgid "If you start a new batch via the <literal>startBatch()</literal> method but then decide you don't want to send it, the <literal>Seam.Remoting.cancelBatch()</literal> method will discard any calls that were queued and exit the batch mode."
+msgstr "Se si da il via ad un nuovo batch usando il metodo <literal>startBatch()</literal>, ma successivamente si decide di non inviarlo, il metodo <literal>Seam.Remoting.cancelBatch()</literal> annullerà tutte le chiamate già in coda e uscirà dalla modalità batch."
#. Tag: para
#: Remoting.xml:305
#, no-c-format
-msgid ""
-"To see an example of a batch being used, take a look at <literal>/examples/"
-"remoting/chatroom</literal>."
-msgstr ""
+msgid "To see an example of a batch being used, take a look at <literal>/examples/remoting/chatroom</literal>."
+msgstr "Per vedere un esempio di batch in azione, date un'occhiata a <literal>/examples/remoting/chatroom</literal>."
#. Tag: title
#: Remoting.xml:310
@@ -986,16 +698,13 @@
#: Remoting.xml:313
#, no-c-format
msgid "Primitives / Basic Types"
-msgstr ""
+msgstr "Tipi primitivi/base"
#. Tag: para
#: Remoting.xml:315
#, no-c-format
-msgid ""
-"This section describes the support for basic data types. On the server side "
-"these values are generally compatible with either their primitive type or "
-"their corresponding wrapper class."
-msgstr ""
+msgid "This section describes the support for basic data types. On the server side these values are generally compatible with either their primitive type or their corresponding wrapper class."
+msgstr "Questa sezione descrive il supporto per i tipi di dati di base. Sul lato del server tali valori generalmente sono compatibili o con il proprio tipo primitivo o con il corrispondente tipo wrapper."
#. Tag: title
#: Remoting.xml:319
@@ -1006,9 +715,8 @@
#. Tag: para
#: Remoting.xml:321
#, no-c-format
-msgid ""
-"Simply use Javascript String objects when setting String parameter values."
-msgstr ""
+msgid "Simply use Javascript String objects when setting String parameter values."
+msgstr "Quando si settano i valori di parametri stringa, basta usare oggetti Javascript di tipo String."
#. Tag: title
#: Remoting.xml:325
@@ -1019,14 +727,7 @@
#. Tag: para
#: Remoting.xml:327
#, no-c-format
-msgid ""
-"There is support for all number types supported by Java. On the client side, "
-"number values are always serialized as their String representation and then "
-"on the server side they are converted to the correct destination type. "
-"Conversion into either a primitive or wrapper type is supported for "
-"<literal>Byte</literal>, <literal>Double</literal>, <literal>Float</"
-"literal>, <literal>Integer</literal>, <literal>Long</literal> and "
-"<literal>Short</literal> types."
+msgid "There is support for all number types supported by Java. On the client side, number values are always serialized as their String representation and then on the server side they are converted to the correct destination type. Conversion into either a primitive or wrapper type is supported for <literal>Byte</literal>, <literal>Double</literal>, <literal>Float</literal>, <literal>Integer</literal>, <literal>Long</literal> and <literal>Short</literal> types."
msgstr ""
#. Tag: title
@@ -1038,9 +739,7 @@
#. Tag: para
#: Remoting.xml:337
#, no-c-format
-msgid ""
-"Booleans are represented client side by Javascript Boolean values, and "
-"server side by a Java boolean."
+msgid "Booleans are represented client side by Javascript Boolean values, and server side by a Java boolean."
msgstr ""
#. Tag: title
@@ -1052,23 +751,13 @@
#. Tag: para
#: Remoting.xml:345
#, no-c-format
-msgid ""
-"In general these will be either Seam entity or JavaBean components, or some "
-"other non-component class. Use the appropriate method (either <literal>Seam."
-"Component.newInstance()</literal> for Seam components or <literal>Seam."
-"Remoting.createType()</literal> for everything else) to create a new "
-"instance of the object."
+msgid "In general these will be either Seam entity or JavaBean components, or some other non-component class. Use the appropriate method (either <literal>Seam.Component.newInstance()</literal> for Seam components or <literal>Seam.Remoting.createType()</literal> for everything else) to create a new instance of the object."
msgstr ""
#. Tag: para
#: Remoting.xml:349
#, no-c-format
-msgid ""
-"It is important to note that only objects that are created by either of "
-"these two methods should be used as parameter values, where the parameter is "
-"not one of the other valid types mentioned anywhere else in this section. In "
-"some situations you may have a component method where the exact parameter "
-"type cannot be determined, such as:"
+msgid "It is important to note that only objects that are created by either of these two methods should be used as parameter values, where the parameter is not one of the other valid types mentioned anywhere else in this section. In some situations you may have a component method where the exact parameter type cannot be determined, such as:"
msgstr ""
#. Tag: programlisting
@@ -1092,12 +781,7 @@
#. Tag: para
#: Remoting.xml:356
#, no-c-format
-msgid ""
-"In this case you might want to pass in an instance of your "
-"<literal>myWidget</literal> component, however the interface for "
-"<literal>myAction</literal> won't include <literal>myWidget</literal> as it "
-"is not directly referenced by any of its methods. To get around this, "
-"<literal>MyWidget</literal> needs to be explicitly imported:"
+msgid "In this case you might want to pass in an instance of your <literal>myWidget</literal> component, however the interface for <literal>myAction</literal> won't include <literal>myWidget</literal> as it is not directly referenced by any of its methods. To get around this, <literal>MyWidget</literal> needs to be explicitly imported:"
msgstr ""
#. Tag: programlisting
@@ -1109,10 +793,7 @@
#. Tag: para
#: Remoting.xml:363
#, no-c-format
-msgid ""
-"This will then allow a <literal>myWidget</literal> object to be created with "
-"<literal>Seam.Component.newInstance(\"myWidget\")</literal>, which can then "
-"be passed to <literal>myAction.doSomethingWithObject()</literal>."
+msgid "This will then allow a <literal>myWidget</literal> object to be created with <literal>Seam.Component.newInstance(\"myWidget\")</literal>, which can then be passed to <literal>myAction.doSomethingWithObject()</literal>."
msgstr ""
#. Tag: title
@@ -1124,18 +805,8 @@
#. Tag: para
#: Remoting.xml:372
#, no-c-format
-msgid ""
-"Date values are serialized into a String representation that is accurate to "
-"the millisecond. On the client side, use a Javascript Date object to work "
-"with date values. On the server side, use any <literal>java.util.Date</"
-"literal> (or descendent, such as <literal>java.sql.Date</literal> or "
-"<literal>java.sql.Timestamp</literal> class."
-msgstr ""
-"I valori delle date sono serializzati in una rappresentazione di Strina che "
-"è accurata al millisecondo. Lato client, si usi un oggetto Date Javascript "
-"per lavorare con i valori delle date. Late server, si usi <literal>java.util."
-"Date</literal> (o discendenti, come le classi <literal>java.sql.Date</"
-"literal> o <literal>java.sql.Timestamp</literal>)."
+msgid "Date values are serialized into a String representation that is accurate to the millisecond. On the client side, use a Javascript Date object to work with date values. On the server side, use any <literal>java.util.Date</literal> (or descendent, such as <literal>java.sql.Date</literal> or <literal>java.sql.Timestamp</literal> class."
+msgstr "I valori delle date sono serializzati in una rappresentazione di Strina che è accurata al millisecondo. Lato client, si usi un oggetto Date Javascript per lavorare con i valori delle date. Late server, si usi <literal>java.util.Date</literal> (o discendenti, come le classi <literal>java.sql.Date</literal> o <literal>java.sql.Timestamp</literal>)."
#. Tag: title
#: Remoting.xml:379
@@ -1146,10 +817,7 @@
#. Tag: para
#: Remoting.xml:381
#, no-c-format
-msgid ""
-"On the client side, enums are treated the same as Strings. When setting the "
-"value for an enum parameter, simply use the String representation of the "
-"enum. Take the following component as an example:"
+msgid "On the client side, enums are treated the same as Strings. When setting the value for an enum parameter, simply use the String representation of the enum. Take the following component as an example:"
msgstr ""
#. Tag: programlisting
@@ -1177,9 +845,7 @@
#. Tag: para
#: Remoting.xml:386
#, no-c-format
-msgid ""
-"To call the <literal>paint()</literal> method with the color <literal>red</"
-"literal>, pass the parameter value as a String literal:"
+msgid "To call the <literal>paint()</literal> method with the color <literal>red</literal>, pass the parameter value as a String literal:"
msgstr ""
#. Tag: programlisting
@@ -1191,10 +857,7 @@
#. Tag: para
#: Remoting.xml:391
#, no-c-format
-msgid ""
-"The inverse is also true - that is, if a component method returns an enum "
-"parameter (or contains an enum field anywhere in the returned object graph) "
-"then on the client-side it will be represented as a String."
+msgid "The inverse is also true - that is, if a component method returns an enum parameter (or contains an enum field anywhere in the returned object graph) then on the client-side it will be represented as a String."
msgstr ""
#. Tag: title
@@ -1212,15 +875,7 @@
#. Tag: para
#: Remoting.xml:401
#, no-c-format
-msgid ""
-"Bags cover all collection types including arrays, collections, lists, sets, "
-"(but excluding Maps - see the next section for those), and are implemented "
-"client-side as a Javascript array. When calling a component method that "
-"accepts one of these types as a parameter, your parameter should be a "
-"Javascript array. If a component method returns one of these types, then the "
-"return value will also be a Javascript array. The remoting framework is "
-"clever enough on the server side to convert the bag to an appropriate type "
-"for the component method call."
+msgid "Bags cover all collection types including arrays, collections, lists, sets, (but excluding Maps - see the next section for those), and are implemented client-side as a Javascript array. When calling a component method that accepts one of these types as a parameter, your parameter should be a Javascript array. If a component method returns one of these types, then the return value will also be a Javascript array. The remoting framework is clever enough on the server side to convert the bag to an appropriate type for the component method call."
msgstr ""
#. Tag: title
@@ -1232,11 +887,7 @@
#. Tag: para
#: Remoting.xml:412
#, no-c-format
-msgid ""
-"As there is no native support for Maps within Javascript, a simple Map "
-"implementation is provided with the Seam Remoting framework. To create a Map "
-"which can be used as a parameter to a remote call, create a new "
-"<literal>Seam.Remoting.Map</literal> object:"
+msgid "As there is no native support for Maps within Javascript, a simple Map implementation is provided with the Seam Remoting framework. To create a Map which can be used as a parameter to a remote call, create a new <literal>Seam.Remoting.Map</literal> object:"
msgstr ""
#. Tag: programlisting
@@ -1248,16 +899,7 @@
#. Tag: para
#: Remoting.xml:418
#, no-c-format
-msgid ""
-"This Javascript implementation provides basic methods for working with Maps: "
-"<literal>size()</literal>, <literal>isEmpty()</literal>, <literal>keySet()</"
-"literal>, <literal>values()</literal>, <literal>get(key)</literal>, "
-"<literal>put(key, value)</literal>, <literal>remove(key)</literal> and "
-"<literal>contains(key)</literal>. Each of these methods are equivalent to "
-"their Java counterpart. Where the method returns a collection, such as "
-"<literal>keySet()</literal> and <literal>values()</literal>, a Javascript "
-"Array object will be returned that contains the key or value objects "
-"(respectively)."
+msgid "This Javascript implementation provides basic methods for working with Maps: <literal>size()</literal>, <literal>isEmpty()</literal>, <literal>keySet()</literal>, <literal>values()</literal>, <literal>get(key)</literal>, <literal>put(key, value)</literal>, <literal>remove(key)</literal> and <literal>contains(key)</literal>. Each of these methods are equivalent to their Java counterpart. Where the method returns a collection, such as <literal>keySet()</literal> and <literal>values()</literal>, a Javascript Array object will be returned that contains the key or value objects (respectively)."
msgstr ""
#. Tag: title
@@ -1269,11 +911,7 @@
#. Tag: para
#: Remoting.xml:431
#, no-c-format
-msgid ""
-"To aid in tracking down bugs, it is possible to enable a debug mode which "
-"will display the contents of all the packets send back and forth between the "
-"client and server in a popup window. To enable debug mode, either execute "
-"the <literal>setDebug()</literal> method in Javascript:"
+msgid "To aid in tracking down bugs, it is possible to enable a debug mode which will display the contents of all the packets send back and forth between the client and server in a popup window. To enable debug mode, either execute the <literal>setDebug()</literal> method in Javascript:"
msgstr ""
#. Tag: programlisting
@@ -1297,10 +935,7 @@
#. Tag: para
#: Remoting.xml:441
#, no-c-format
-msgid ""
-"To turn off debugging, call <literal>setDebug(false)</literal>. If you want "
-"to write your own messages to the debug log, call <literal>Seam.Remoting.log"
-"(message)</literal>."
+msgid "To turn off debugging, call <literal>setDebug(false)</literal>. If you want to write your own messages to the debug log, call <literal>Seam.Remoting.log(message)</literal>."
msgstr ""
#. Tag: title
@@ -1312,12 +947,7 @@
#. Tag: para
#: Remoting.xml:448
#, no-c-format
-msgid ""
-"When invoking a remote component method, it is possible to specify an "
-"exception handler which will process the response in the event of an "
-"exception during component invocation. To specify an exception handler "
-"function, include a reference to it after the callback parameter in your "
-"JavaScript:"
+msgid "When invoking a remote component method, it is possible to specify an exception handler which will process the response in the event of an exception during component invocation. To specify an exception handler function, include a reference to it after the callback parameter in your JavaScript:"
msgstr ""
#. Tag: programlisting
@@ -1325,47 +955,33 @@
#, no-c-format
msgid ""
"<![CDATA[var callback = function(result) { alert(result); };\n"
-"var exceptionHandler = function(ex) { alert(\"An exception occurred: \" + ex."
-"getMessage()); };\n"
-"Seam.Component.getInstance(\"helloAction\").sayHello(name, callback, "
-"exceptionHandler);]]>"
+"var exceptionHandler = function(ex) { alert(\"An exception occurred: \" + ex.getMessage()); };\n"
+"Seam.Component.getInstance(\"helloAction\").sayHello(name, callback, exceptionHandler);]]>"
msgstr ""
"<![CDATA[var callback = function(result) { alert(result); };\n"
-"var exceptionHandler = function(ex) { alert(\"An exception occurred: \" + ex."
-"getMessage()); };\n"
-"Seam.Component.getInstance(\"helloAction\").sayHello(name, callback, "
-"exceptionHandler);]]>"
+"var exceptionHandler = function(ex) { alert(\"An exception occurred: \" + ex.getMessage()); };\n"
+"Seam.Component.getInstance(\"helloAction\").sayHello(name, callback, exceptionHandler);]]>"
#. Tag: para
#: Remoting.xml:456
#, no-c-format
-msgid ""
-"If you do not have a callback handler defined, you must specify "
-"<literal>null</literal> in its place:"
+msgid "If you do not have a callback handler defined, you must specify <literal>null</literal> in its place:"
msgstr ""
#. Tag: programlisting
#: Remoting.xml:460
#, no-c-format
msgid ""
-"<![CDATA[var exceptionHandler = function(ex) { alert(\"An exception "
-"occurred: \" + ex.getMessage()); };\n"
-"Seam.Component.getInstance(\"helloAction\").sayHello(name, null, "
-"exceptionHandler);]]>"
+"<![CDATA[var exceptionHandler = function(ex) { alert(\"An exception occurred: \" + ex.getMessage()); };\n"
+"Seam.Component.getInstance(\"helloAction\").sayHello(name, null, exceptionHandler);]]>"
msgstr ""
-"<![CDATA[var exceptionHandler = function(ex) { alert(\"An exception "
-"occurred: \" + ex.getMessage()); };\n"
-"Seam.Component.getInstance(\"helloAction\").sayHello(name, null, "
-"exceptionHandler);]]>"
+"<![CDATA[var exceptionHandler = function(ex) { alert(\"An exception occurred: \" + ex.getMessage()); };\n"
+"Seam.Component.getInstance(\"helloAction\").sayHello(name, null, exceptionHandler);]]>"
#. Tag: para
#: Remoting.xml:462
#, no-c-format
-msgid ""
-"The exception object that is passed to the exception handler exposes one "
-"method, <literal>getMessage()</literal> that returns the exception message "
-"which is produced by the exception thrown by the <literal>@WebRemote</"
-"literal> method."
+msgid "The exception object that is passed to the exception handler exposes one method, <literal>getMessage()</literal> that returns the exception message which is produced by the exception thrown by the <literal>@WebRemote</literal> method."
msgstr ""
#. Tag: title
@@ -1377,10 +993,7 @@
#. Tag: para
#: Remoting.xml:473
#, no-c-format
-msgid ""
-"The default loading message that appears in the top right corner of the "
-"screen can be modified, its rendering customised or even turned off "
-"completely."
+msgid "The default loading message that appears in the top right corner of the screen can be modified, its rendering customised or even turned off completely."
msgstr ""
#. Tag: title
@@ -1392,13 +1005,8 @@
#. Tag: para
#: Remoting.xml:479
#, no-c-format
-msgid ""
-"To change the message from the default \"Please Wait...\" to something "
-"different, set the value of <literal>Seam.Remoting.loadingMessage</literal>:"
-msgstr ""
-"Per cambiare il messaggio dal default \"Attendere prego...\" a qualcosa di "
-"differente, si imposti il valore di <literal>Seam.Remoting.loadingMessage</"
-"literal>:"
+msgid "To change the message from the default \"Please Wait...\" to something different, set the value of <literal>Seam.Remoting.loadingMessage</literal>:"
+msgstr "Per cambiare il messaggio dal default \"Attendere prego...\" a qualcosa di differente, si imposti il valore di <literal>Seam.Remoting.loadingMessage</literal>:"
#. Tag: programlisting
#: Remoting.xml:482
@@ -1415,11 +1023,7 @@
#. Tag: para
#: Remoting.xml:488
#, no-c-format
-msgid ""
-"To completely suppress the display of the loading message, override the "
-"implementation of <literal>displayLoadingMessage()</literal> and "
-"<literal>hideLoadingMessage()</literal> with functions that instead do "
-"nothing:"
+msgid "To completely suppress the display of the loading message, override the implementation of <literal>displayLoadingMessage()</literal> and <literal>hideLoadingMessage()</literal> with functions that instead do nothing:"
msgstr ""
#. Tag: programlisting
@@ -1443,11 +1047,7 @@
#. Tag: para
#: Remoting.xml:498
#, no-c-format
-msgid ""
-"It is also possible to override the loading indicator to display an animated "
-"icon, or anything else that you want. To do this override the "
-"<literal>displayLoadingMessage()</literal> and <literal>hideLoadingMessage()"
-"</literal> messages with your own implementation:"
+msgid "It is also possible to override the loading indicator to display an animated icon, or anything else that you want. To do this override the <literal>displayLoadingMessage()</literal> and <literal>hideLoadingMessage()</literal> messages with your own implementation:"
msgstr ""
#. Tag: programlisting
@@ -1479,37 +1079,19 @@
#. Tag: para
#: Remoting.xml:509
#, no-c-format
-msgid ""
-"When a remote method is executed, the result is serialized into an XML "
-"response that is returned to the client. This response is then unmarshaled "
-"by the client into a Javascript object. For complex types (i.e. Javabeans) "
-"that include references to other objects, all of these referenced objects "
-"are also serialized as part of the response. These objects may reference "
-"other objects, which may reference other objects, and so forth. If left "
-"unchecked, this object \"graph\" could potentially be enormous, depending on "
-"what relationships exist between your objects. And as a side issue (besides "
-"the potential verbosity of the response), you might also wish to prevent "
-"sensitive information from being exposed to the client."
+msgid "When a remote method is executed, the result is serialized into an XML response that is returned to the client. This response is then unmarshaled by the client into a Javascript object. For complex types (i.e. Javabeans) that include references to other objects, all of these referenced objects are also serialized as part of the response. These objects may reference other objects, which may reference other objects, and so forth. If left unchecked, this object \"graph\" could potentially be enormous, depending on what relationships exist between your objects. And as a side issue (besides the potential verbosity of the response), you might also wish to prevent sensitive information from being exposed to the client."
msgstr ""
#. Tag: para
#: Remoting.xml:517
#, no-c-format
-msgid ""
-"Seam Remoting provides a simple means to \"constrain\" the object graph, by "
-"specifying the <literal>exclude</literal> field of the remote method's "
-"<literal>@WebRemote</literal> annotation. This field accepts a String array "
-"containing one or more paths specified using dot notation. When invoking a "
-"remote method, the objects in the result's object graph that match these "
-"paths are excluded from the serialized result packet."
+msgid "Seam Remoting provides a simple means to \"constrain\" the object graph, by specifying the <literal>exclude</literal> field of the remote method's <literal>@WebRemote</literal> annotation. This field accepts a String array containing one or more paths specified using dot notation. When invoking a remote method, the objects in the result's object graph that match these paths are excluded from the serialized result packet."
msgstr ""
#. Tag: para
#: Remoting.xml:522
#, no-c-format
-msgid ""
-"For all our examples, we'll use the following <literal>Widget</literal> "
-"class:"
+msgid "For all our examples, we'll use the following <literal>Widget</literal> class:"
msgstr ""
#. Tag: programlisting
@@ -1549,10 +1131,7 @@
#. Tag: para
#: Remoting.xml:529
#, no-c-format
-msgid ""
-"If your remote method returns an instance of <literal>Widget</literal>, but "
-"you don't want to expose the <literal>secret</literal> field because it "
-"contains sensitive information, you would constrain it like this:"
+msgid "If your remote method returns an instance of <literal>Widget</literal>, but you don't want to expose the <literal>secret</literal> field because it contains sensitive information, you would constrain it like this:"
msgstr ""
#. Tag: programlisting
@@ -1568,15 +1147,7 @@
#. Tag: para
#: Remoting.xml:534
#, no-c-format
-msgid ""
-"The value \"secret\" refers to the <literal>secret</literal> field of the "
-"returned object. Now, suppose that we don't care about exposing this "
-"particular field to the client. Instead, notice that the <literal>Widget</"
-"literal> value that is returned has a field <literal>child</literal> that is "
-"also a <literal>Widget</literal>. What if we want to hide the "
-"<literal>child</literal>'s <literal>secret</literal> value instead? We can "
-"do this by using dot notation to specify this field's path within the "
-"result's object graph:"
+msgid "The value \"secret\" refers to the <literal>secret</literal> field of the returned object. Now, suppose that we don't care about exposing this particular field to the client. Instead, notice that the <literal>Widget</literal> value that is returned has a field <literal>child</literal> that is also a <literal>Widget</literal>. What if we want to hide the <literal>child</literal>'s <literal>secret</literal> value instead? We can do this by using dot notation to specify this field's path within the result's object graph:"
msgstr ""
#. Tag: programlisting
@@ -1598,15 +1169,7 @@
#. Tag: para
#: Remoting.xml:548
#, no-c-format
-msgid ""
-"The other place that objects can exist within an object graph are within a "
-"<literal>Map</literal> or some kind of collection (<literal>List</literal>, "
-"<literal>Set</literal>, <literal>Array</literal>, etc). Collections are "
-"easy, and are treated like any other field. For example, if our "
-"<literal>Widget</literal> contained a list of other <literal>Widget</"
-"literal>s in its <literal>widgetList</literal> field, to constrain the "
-"<literal>secret</literal> field of the <literal>Widget</literal>s in this "
-"list the annotation would look like this:"
+msgid "The other place that objects can exist within an object graph are within a <literal>Map</literal> or some kind of collection (<literal>List</literal>, <literal>Set</literal>, <literal>Array</literal>, etc). Collections are easy, and are treated like any other field. For example, if our <literal>Widget</literal> contained a list of other <literal>Widget</literal>s in its <literal>widgetList</literal> field, to constrain the <literal>secret</literal> field of the <literal>Widget</literal>s in this list the annotation would look like this:"
msgstr ""
#. Tag: programlisting
@@ -1622,14 +1185,7 @@
#. Tag: para
#: Remoting.xml:557
#, no-c-format
-msgid ""
-"To constrain a <literal>Map</literal>'s key or value, the notation is "
-"slightly different. Appending <literal>[key]</literal> after the "
-"<literal>Map</literal>'s field name will constrain the <literal>Map</"
-"literal>'s key object values, while <literal>[value]</literal> will "
-"constrain the value object values. The following example demonstrates how "
-"the values of the <literal>widgetMap</literal> field have their "
-"<literal>secret</literal> field constrained:"
+msgid "To constrain a <literal>Map</literal>'s key or value, the notation is slightly different. Appending <literal>[key]</literal> after the <literal>Map</literal>'s field name will constrain the <literal>Map</literal>'s key object values, while <literal>[value]</literal> will constrain the value object values. The following example demonstrates how the values of the <literal>widgetMap</literal> field have their <literal>secret</literal> field constrained:"
msgstr ""
#. Tag: programlisting
@@ -1651,12 +1207,7 @@
#. Tag: para
#: Remoting.xml:569
#, no-c-format
-msgid ""
-"There is one last notation that can be used to constrain the fields of a "
-"type of object no matter where in the result's object graph it appears. This "
-"notation uses either the name of the component (if the object is a Seam "
-"component) or the fully qualified class name (only if the object is not a "
-"Seam component) and is expressed using square brackets:"
+msgid "There is one last notation that can be used to constrain the fields of a type of object no matter where in the result's object graph it appears. This notation uses either the name of the component (if the object is a Seam component) or the fully qualified class name (only if the object is not a Seam component) and is expressed using square brackets:"
msgstr ""
#. Tag: programlisting
@@ -1678,9 +1229,7 @@
#. Tag: para
#: Remoting.xml:581
#, no-c-format
-msgid ""
-"Constraints can also be combined, to filter objects from multiple paths "
-"within the object graph:"
+msgid "Constraints can also be combined, to filter objects from multiple paths within the object graph:"
msgstr ""
#. Tag: programlisting
@@ -1702,11 +1251,7 @@
#. Tag: para
#: Remoting.xml:591
#, no-c-format
-msgid ""
-"By default there is no active transaction during a remoting request, so if "
-"you wish to perform database updates during a remoting request, you need to "
-"annotate the <literal>@WebRemote</literal> method with "
-"<literal>@Transactional</literal>, like so:"
+msgid "By default there is no active transaction during a remoting request, so if you wish to perform database updates during a remoting request, you need to annotate the <literal>@WebRemote</literal> method with <literal>@Transactional</literal>, like so:"
msgstr ""
#. Tag: programlisting
@@ -1728,30 +1273,21 @@
#. Tag: para
#: Remoting.xml:603
#, no-c-format
-msgid ""
-"Seam Remoting provides experimental support for JMS Messaging. This section "
-"describes the JMS support that is currently implemented, but please note "
-"that this may change in the future. It is currently not recommended that "
-"this feature is used within a production environment."
+msgid "Seam Remoting provides experimental support for JMS Messaging. This section describes the JMS support that is currently implemented, but please note that this may change in the future. It is currently not recommended that this feature is used within a production environment."
msgstr ""
#. Tag: para
#: Remoting.xml:610
#, no-c-format
-msgid ""
-"Before you can subscribe to a JMS topic, you must first configure a list of "
-"the topics that can be subscribed to by Seam Remoting. List the topics under "
-"<literal>org.jboss.seam.remoting.messaging.subscriptionRegistry."
-"allowedTopics</literal> in <literal>seam.properties</literal>, <literal>web."
-"xml</literal> or <literal>components.xml</literal>."
+msgid "Before you can subscribe to a JMS topic, you must first configure a list of the topics that can be subscribed to by Seam Remoting. List the topics under <literal>org.jboss.seam.remoting.messaging.subscriptionRegistry.allowedTopics</literal> in <literal>seam.properties</literal>, <literal>web.xml</literal> or <literal>components.xml</literal>."
msgstr ""
#. Tag: programlisting
-#: Remoting.xml:615 Remoting.xml:670
+#: Remoting.xml:615
+#: Remoting.xml:670
#, no-c-format
msgid "<![CDATA[<remoting:remoting poll-timeout=\"5\" poll-interval=\"1\"/>]]>"
-msgstr ""
-"<![CDATA[<remoting:remoting poll-timeout=\"5\" poll-interval=\"1\"/>]]>"
+msgstr "<![CDATA[<remoting:remoting poll-timeout=\"5\" poll-interval=\"1\"/>]]>"
#. Tag: title
#: Remoting.xml:620
@@ -1788,26 +1324,13 @@
#. Tag: para
#: Remoting.xml:626
#, no-c-format
-msgid ""
-"The <literal>Seam.Remoting.subscribe()</literal> method accepts two "
-"parameters, the first being the name of the JMS Topic to subscribe to, the "
-"second being the callback function to invoke when a message is received."
+msgid "The <literal>Seam.Remoting.subscribe()</literal> method accepts two parameters, the first being the name of the JMS Topic to subscribe to, the second being the callback function to invoke when a message is received."
msgstr ""
#. Tag: para
#: Remoting.xml:629
#, no-c-format
-msgid ""
-"There are two types of messages supported, Text messages and Object "
-"messages. If you need to test for the type of message that is passed to your "
-"callback function you can use the <literal>instanceof</literal> operator to "
-"test whether the message is a <literal>Seam.Remoting.TextMessage</literal> "
-"or <literal>Seam.Remoting.ObjectMessage</literal>. A <literal>TextMessage</"
-"literal> contains the text value in its <literal>text</literal> field (or "
-"alternatively call <literal>getText()</literal> on it), while an "
-"<literal>ObjectMessage</literal> contains its object value in its "
-"<literal>value</literal> field (or call its <literal>getValue()</literal> "
-"method)."
+msgid "There are two types of messages supported, Text messages and Object messages. If you need to test for the type of message that is passed to your callback function you can use the <literal>instanceof</literal> operator to test whether the message is a <literal>Seam.Remoting.TextMessage</literal> or <literal>Seam.Remoting.ObjectMessage</literal>. A <literal>TextMessage</literal> contains the text value in its <literal>text</literal> field (or alternatively call <literal>getText()</literal> on it), while an <literal>ObjectMessage</literal> contains its object value in its <literal>value</literal> field (or call its <literal>getValue()</literal> method)."
msgstr ""
#. Tag: title
@@ -1819,9 +1342,7 @@
#. Tag: para
#: Remoting.xml:641
#, no-c-format
-msgid ""
-"To unsubscribe from a topic, call <literal>Seam.Remoting.unsubscribe()</"
-"literal> and pass in the topic name:"
+msgid "To unsubscribe from a topic, call <literal>Seam.Remoting.unsubscribe()</literal> and pass in the topic name:"
msgstr ""
#. Tag: programlisting
@@ -1839,44 +1360,25 @@
#. Tag: para
#: Remoting.xml:650
#, no-c-format
-msgid ""
-"There are two parameters which you can modify to control how polling occurs. "
-"The first one is <literal>Seam.Remoting.pollInterval</literal>, which "
-"controls how long to wait between subsequent polls for new messages. This "
-"parameter is expressed in seconds, and its default setting is 10."
+msgid "There are two parameters which you can modify to control how polling occurs. The first one is <literal>Seam.Remoting.pollInterval</literal>, which controls how long to wait between subsequent polls for new messages. This parameter is expressed in seconds, and its default setting is 10."
msgstr ""
#. Tag: para
#: Remoting.xml:654
#, no-c-format
-msgid ""
-"The second parameter is <literal>Seam.Remoting.pollTimeout</literal>, and is "
-"also expressed as seconds. It controls how long a request to the server "
-"should wait for a new message before timing out and sending an empty "
-"response. Its default is 0 seconds, which means that when the server is "
-"polled, if there are no messages ready for delivery then an empty response "
-"will be immediately returned."
+msgid "The second parameter is <literal>Seam.Remoting.pollTimeout</literal>, and is also expressed as seconds. It controls how long a request to the server should wait for a new message before timing out and sending an empty response. Its default is 0 seconds, which means that when the server is polled, if there are no messages ready for delivery then an empty response will be immediately returned."
msgstr ""
#. Tag: para
#: Remoting.xml:659
#, no-c-format
-msgid ""
-"Caution should be used when setting a high <literal>pollTimeout</literal> "
-"value; each request that has to wait for a message means that a server "
-"thread is tied up until a message is received, or until the request times "
-"out. If many such requests are being served simultaneously, it could mean a "
-"large number of threads become tied up because of this reason."
+msgid "Caution should be used when setting a high <literal>pollTimeout</literal> value; each request that has to wait for a message means that a server thread is tied up until a message is received, or until the request times out. If many such requests are being served simultaneously, it could mean a large number of threads become tied up because of this reason."
msgstr ""
#. Tag: para
#: Remoting.xml:664
#, no-c-format
-msgid ""
-"It is recommended that you set these options via components.xml, however "
-"they can be overridden via Javascript if desired. The following example "
-"demonstrates how to configure the polling to occur much more aggressively. "
-"You should set these parameters to suitable values for your application:"
+msgid "It is recommended that you set these options via components.xml, however they can be overridden via Javascript if desired. The following example demonstrates how to configure the polling to occur much more aggressively. You should set these parameters to suitable values for your application:"
msgstr ""
#. Tag: para
@@ -1895,16 +1397,15 @@
#: Remoting.xml:674
#, no-c-format
msgid ""
-"// Only wait 1 second between receiving a poll response and sending the next "
-"poll request.\n"
+"// Only wait 1 second between receiving a poll response and sending the next poll request.\n"
"Seam.Remoting.pollInterval = 1;\n"
" \n"
"// Wait up to 5 seconds on the server for new messages\n"
"Seam.Remoting.pollTimeout = 5;"
msgstr ""
-"// Attendere 1 secondo tra la ricezione della risposta del pool e l'invio "
-"della successiva richiesta di pool.\n"
+"// Attendere 1 secondo tra la ricezione della risposta del pool e l'invio della successiva richiesta di pool.\n"
"Seam.Remoting.pollInterval = 1;\n"
" \n"
"// Attendere fino a 5 secondi sul server per nuovi messaggi\n"
"Seam.Remoting.pollTimeout = 5;"
+
14 years, 11 months
- 1
- 0
Seam SVN: r10949 - branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2009-05-23 08:58:13 -0400 (Sat, 23 May 2009)
New Revision: 10949
Modified:
branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/I18n.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/I18n.po
===================================================================
--- branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/I18n.po 2009-05-23 12:50:08 UTC (rev 10948)
+++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/I18n.po 2009-05-23 12:58:13 UTC (rev 10949)
@@ -97,7 +97,7 @@
#: I18n.xml:73
#, no-c-format
msgid "You can write your translation of labels (<xlink linkend=\"labels\">Labels</xlink>) to your messages resource bundle in the native encoding and then convert the content of the file into the escaped format through the tool <literal>native2ascii</literal> provided in the JDK. This tool will convert a file written in your native encoding to one that represents non-ASCII characters as Unicode escape sequences."
-msgstr "E' possibile scrivere la traduzione delle etichette (<xlink linked=\"labels\">Etichette</xlink>) nei resource bundles con la codifica del proprio sistema e poi convertire il contenuto del file nel formato con le notazioni Unicode attraverso lo strumento <literal>native2ascii</literal> fornito con JDK. Questo strumento converte un file scritto nella codifica originale in uno dove i caratteri non-ASCII sono rappresentati come sequenze di notazioni Unicode."
+msgstr "E' possibile scrivere la traduzione delle etichette (<xlink linkend=\"labels\">Etichette</xlink>) nei resource bundles con la codifica del proprio sistema e poi convertire il contenuto del file nel formato con le notazioni Unicode attraverso lo strumento <literal>native2ascii</literal> fornito con JDK. Questo strumento converte un file scritto nella codifica originale in uno dove i caratteri non-ASCII sono rappresentati come sequenze di notazioni Unicode."
#. Tag: para
#: I18n.xml:83
14 years, 11 months
- 1
- 0
Seam SVN: r10948 - branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2009-05-23 08:50:08 -0400 (Sat, 23 May 2009)
New Revision: 10948
Modified:
branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Rss.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Rss.po
===================================================================
--- branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Rss.po 2009-05-23 12:44:18 UTC (rev 10947)
+++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/Rss.po 2009-05-23 12:50:08 UTC (rev 10948)
@@ -6,7 +6,7 @@
"Project-Id-Version: Seam_Reference_Guide\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-18 15:00+0000\n"
-"PO-Revision-Date: 2009-02-08 12:35+0100\n"
+"PO-Revision-Date: 2009-05-23 14:49+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: Italian <kde-i18n-it(a)lists.kde.org>\n"
"MIME-Version: 1.0\n"
@@ -37,7 +37,7 @@
#: Rss.xml:15
#, no-c-format
msgid "To enable RSS support, include the <literal>jboss-seam-rss.jar</literal> in your applications <literal>WEB-INF/lib</literal> directory. The RSS library also has some dependent libraries that should be placed in the same directory. See <xref linkend=\"dependencies.rss\"/> for a list of libraries to include."
-msgstr "Per abilitare il supporto RSS includere <literal>jboss-seam-rss.jar</literal> nella cartella <literal>WEB-INF/lib</literal> dell'applicazione. La libreria RSS ha anche alcune dipendenze che devono essere posizionate nella stessa cartella. Vedi <xref linked=\"dependencies.rss\"/> per la lista delle librerie da includere."
+msgstr "Per abilitare il supporto RSS includere <literal>jboss-seam-rss.jar</literal> nella cartella <literal>WEB-INF/lib</literal> dell'applicazione. La libreria RSS ha anche alcune dipendenze che devono essere posizionate nella stessa cartella. Vedi <xref linkend=\"dependencies.rss\"/> per la lista delle librerie da includere."
#. Tag: para
#: Rss.xml:22
14 years, 11 months
- 1
- 0