[seam-commits] Seam SVN: r11432 - branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT.
seam-commits at lists.jboss.org
seam-commits at lists.jboss.org
Wed Aug 26 15:14:03 EDT 2009
Author: nico.ben
Date: 2009-08-26 15:14:02 -0400 (Wed, 26 Aug 2009)
New Revision: 11432
Modified:
branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Configuration.po
branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Webservices.po
branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Websphere.po
Log:
Italian translation
Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Configuration.po
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Configuration.po 2009-08-26 19:12:36 UTC (rev 11431)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Configuration.po 2009-08-26 19:14:02 UTC (rev 11432)
@@ -5,8 +5,8 @@
msgstr ""
"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 13:07+0100\n"
+"POT-Creation-Date: 2009-08-26 18:47+0000\n"
+"PO-Revision-Date: 2009-08-26 21:08+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -596,20 +596,65 @@
msgid "You are also responsible for ensuring propagation of any new conversation id back to the client. Seam exposes the conversation id as a property of the built in component <literal>conversation</literal>."
msgstr "Si è responsabili della propagazione di ogni nuovo id della conversazione attraverso il client. Seam espone l'id di conversazione come proprietà del componente predefinito <literal>conversation</literal>."
+# controllare
#. Tag: title
+#: Configuration.xml:325
+#, no-c-format
+msgid "Enabling HTTP cache-control headers"
+msgstr "Abilitazione delle intestazioni HTTP cache-control"
+
+#. Tag: para
#: Configuration.xml:326
#, no-c-format
+msgid "Seam does <emphasis>not</emphasis> automatically add <literal>cache-control</literal> HTTP headers to any resources served by the Seam resource servlet, or directly from your view directory by the servlet container. This means that your images, Javascript and CSS files, and resource representations from Seam resource servlet such as Seam Remoting Javascript interfaces are usually not cached by the browser. This is convenient in development but should be changed in production when optimizing the application."
+msgstr "Seam <emphasis>non</emphasis> aggiunge automaticamente le intestazioni HTTP <literal>cache-control</literal> alle risorse servite dal servlet resource Seam, o direttamente dalla directory di vista dal servlet container. Questo significa che le immagini, Javascript ed i file CSS, e le rappresentazioni delle risorse da parte del resource servlet di Seam quali le interfacce Seam Remoting Javascript solitamente non vengono messe nella cache del browser. Questo va bene in fase di sviluppo ma dovrebbe essere cambiato in fase di produzione quando si ottimizza l'applicazione."
+
+#. Tag: para
+#: Configuration.xml:334
+#, no-c-format
+msgid "You can configure a Seam filter to enable automatic addition of <literal>cache-control</literal> headers depending on the requested URI in <literal>components.xml</literal>:"
+msgstr "Si può configurare un filtro Seam ed abilitare l'aggiunta automatica delle intestazioni <literal>cache-control</literal> che dipendono dall'URI richiesta in <literal>components.xml</literal>:"
+
+#. Tag: programlisting
+#: Configuration.xml:339
+#, no-c-format
+msgid ""
+"<![CDATA[<web:cache-control-filter name=\"commonTypesCacheControlFilter\"\n"
+" regex-url-pattern=\".*(\\.gif|\\.png|\\.jpg|\\.jpeg|\\.css|\\.js)\"\n"
+" value=\"max-age=86400\"/> <!-- 1 day -->\n"
+"\n"
+"<web:cache-control-filter name=\"anotherCacheControlFilter\"\n"
+" url-pattern=\"/my/cachable/resources/*\"\n"
+" value=\"max-age=432000\"/> <!-- 5 days -->]]>"
+msgstr ""
+"<![CDATA[<web:cache-control-filter name=\"commonTypesCacheControlFilter\"\n"
+" regex-url-pattern=\".*(\\.gif|\\.png|\\.jpg|\\.jpeg|\\.css|\\.js)\"\n"
+" value=\"max-age=86400\"/> <!-- 1 day -->\n"
+"\n"
+"<web:cache-control-filter name=\"anotherCacheControlFilter\"\n"
+" url-pattern=\"/my/cachable/resources/*\"\n"
+" value=\"max-age=432000\"/> <!-- 5 days -->]]>"
+
+#. Tag: para
+#: Configuration.xml:341
+#, no-c-format
+msgid "You do not have to name the filters unless you have more than one filter enabled."
+msgstr "Non occorre dare il nome ai filtri amenoché vi sia più di un filtro abilitato."
+
+#. Tag: title
+#: Configuration.xml:348
+#, no-c-format
msgid "Adding custom filters"
msgstr "Aggiunta di filtri personalizzati"
#. Tag: para
-#: Configuration.xml:327
+#: Configuration.xml:349
#, no-c-format
msgid "Seam can install your filters for you, allowing you to specify <emphasis>where</emphasis> in the chain your filter is placed (the servlet specification doesn't provide a well defined order if you specify your filters in a <literal>web.xml</literal>). Just add the <literal>@Filter</literal> annotation to your Seam component (which must implement <literal>javax.servlet.Filter</literal>):"
msgstr "Seam può installare i filtri per voi, consentendo di specificare <emphasis>dove</emphasis> debba essere collocato il filtro nella catena (la specifica servlet non fornisce un ordine ben definito se si specificano i filtri in <literal>web.xml</literal>). Si aggiunga l'annotazione <literal>@Filter</literal> al componente Seam (che deve implementare <literal>javax.servlet.Filter</literal>):"
#. Tag: programlisting
-#: Configuration.xml:332
+#: Configuration.xml:354
#, no-c-format
msgid ""
"<![CDATA[@Startup\n"
@@ -627,31 +672,31 @@
"public class MultipartFilter extends AbstractFilter {]]>"
#. Tag: para
-#: Configuration.xml:334
+#: Configuration.xml:356
#, no-c-format
msgid "Adding the <literal>@Startup</literal> annotation means thar the component is available during Seam startup; bijection isn't available here (<literal>@BypassInterceptors</literal>); and the filter should be further down the chain than the RichFaces filter (<literal>@Filter(within=\"org.jboss.seam.web.ajax4jsfFilter\")</literal>)."
msgstr "Aggiungere l'annotazione <literal>@Startup</literal> significa che il componente è disponibile durante lo startup di Seam; la bijection non è disponibile qua (<literal>@BypassInterceptors</literal>); ed il filtro dovrebbe essere più in fondo alla catena rispetto al filtro RichFaces (<literal>@Filter(within=\"org.jboss.seam.web.ajax4jsfFilter\")</literal>)."
#. Tag: title
-#: Configuration.xml:343
+#: Configuration.xml:365
#, no-c-format
msgid "Integrating Seam with your EJB container"
msgstr "Integrazione di Seam con l'EJB container"
#. Tag: para
-#: Configuration.xml:345
+#: Configuration.xml:367
#, no-c-format
msgid "In a Seam application, EJB components have a certain duality, as they are managed by both the EJB container and Seam. Actually, it's more that Seam resolves EJB component references, manages the lifetime of stateful session bean components, and also participates in each method call via interceptors. Let's start with the configuration of the Seam interceptor chain."
msgstr "Nelle applicazioni Seam i componenti EJB hanno una certa dualità, poiché sono gestiti da entrambi: il container EJB e Seam. In verità Seam risolve i riferimenti ai componenti EJB, gestisce il ciclo di vita dei componenti bean con sessione stateful, e partecipa anche ad ogni chiamata di metodo via interceptor. Iniziamo con la configurazione della catena interceptor di Seam."
#. Tag: para
-#: Configuration.xml:350
+#: Configuration.xml:372
#, no-c-format
msgid "We need to apply the <literal>SeamInterceptor</literal> to our Seam EJB components. This interceptor delegates to a set of built-in server-side interceptors that handle such concerns as bijection, conversation demarcation, and business process signals. The simplest way to do this across an entire application is to add the following interceptor configuration in <literal>ejb-jar.xml</literal>:"
msgstr "Occorre applicare <literal>SeamInterceptor</literal> ai componenti EJB di Seam. Quest'interceptor delega ad un set di interceptor predefiniti lato server che gestiscono i concern quali la bijection, la demarcazione delle conversazioni ed i segnali del processo di business. Il modo più semplice per fare questo in tutta l'applicazione è aggiungere la seguente configurazione per l'interceptor in <literal>ejb-jar.xml</literal>:"
#. Tag: programlisting
-#: Configuration.xml:355
+#: Configuration.xml:377
#, no-c-format
msgid ""
"<![CDATA[<interceptors>\n"
@@ -683,79 +728,79 @@
"]]>"
#. Tag: para
-#: Configuration.xml:357
+#: Configuration.xml:379
#, no-c-format
msgid "Seam needs to know where to go to find session beans in JNDI. One way to do this is specify the <literal>@JndiName</literal> annotation on every session bean Seam component. However, this is quite tedious. A better approach is to specify a pattern that Seam can use to calculate the JNDI name from the EJB name. Unfortunately, there is no standard mapping to global JNDI defined in the EJB3 specification, so this mapping is vendor-specific (and may depend on your own naming conventions as well). We usually specify this option in <literal>components.xml</literal>."
msgstr "Seam necessita di sapere dove trovare i session bean in JNDI. Un modo per farlo è specificare l'annotazione <literal>@JndiName</literal> su ogni componente session bean. Comunque questa modalità è abbastanza noiosa. Un approccio migliore è specificare un pattern che Seam usa per calcolare il nome JNDI dal nome EJB. Sfortunatamente nella specifica EJB3 non è definita una mappatura standard al JNDI globale, quindi questa mappatura è specificata dal venditore (e può dipendere anche dalle proprie convenzioni di nome). Solitamente si specifica quest'opzione in <literal>components.xml</literal>."
#. Tag: para
-#: Configuration.xml:364
+#: Configuration.xml:386
#, no-c-format
msgid "For JBoss AS, the following pattern is correct:"
msgstr "Per JBoss AS ilseguente pattern è corretto:"
#. Tag: programlisting
-#: Configuration.xml:366
+#: Configuration.xml:388
#, no-c-format
msgid "<![CDATA[<core:init jndi-name=\"earName/#{ejbName}/local\" />]]>"
msgstr "<![CDATA[<core:init jndi-name=\"earName/#{ejbName}/local\" />]]>"
#. Tag: para
-#: Configuration.xml:368
+#: Configuration.xml:390
#, no-c-format
msgid "In this case, <literal>earName</literal> is the name of the EAR in which the bean is deployed, Seam replaces <literal>#{ejbName}</literal> with the name of the EJB, and the final segment represents the type of interface (local or remote)."
msgstr "In questo caso <literal>earName</literal> è il nome dell'EAR in cui viene deployato il bean, Seam sostituisce <literal>#{ejbName}</literal> con il nome dell'EJB ed il segmento finale rappresenta il tipo di interfaccia (locale o remota)."
#. Tag: para
-#: Configuration.xml:372
+#: Configuration.xml:394
#, no-c-format
msgid "Outside the context of an EAR (when using the JBoss Embeddable EJB3 container), the first segment is dropped since there is no EAR, leaving us with the following pattern:"
msgstr "Fuori dal contesto di un EAR (quando si usa il container JBoss Embeddable EJB3) il primo segmento viene ignorato poiché non c'è alcun EAR, rimanendo quindi con il seguente pattern:"
#. Tag: programlisting
-#: Configuration.xml:375
+#: Configuration.xml:397
#, no-c-format
msgid "<![CDATA[<core:init jndi-name=\"#{ejbName}/local\" />]]>"
msgstr "<![CDATA[<core:init jndi-name=\"#{ejbName}/local\" />]]>"
#. Tag: para
-#: Configuration.xml:377
+#: Configuration.xml:399
#, no-c-format
msgid "How these JNDI names are resolved and somehow locate an EJB component might appear a bit like black magic at this point, so let's dig into the details. First, let's talk about how the EJB components get into JNDI."
msgstr "Come questi nomi JNDI vengono risolti e come localizzare un componente EJB potrebbe apparire a questo punto un pò una questione di magia, quindi indaghiamo meglio i dettagli. Innanzitutto vediamo come i componenti EJB entrano in JNDI."
#. Tag: para
-#: Configuration.xml:381
+#: Configuration.xml:403
#, no-c-format
msgid "The folks at JBoss don't care much for XML, if you can't tell. So when they designed JBoss AS, they decided that EJB components would get assigned a global JNDI name automatically, using the pattern just described (i.e., EAR name/EJB name/interface type). The EJB name is the first non-empty value from the following list:"
msgstr "Le persone di JBoss non si preoccupano molto di XML. Quindi quando hanno progettato JBoss AS, hanno deciso che i componenti EJB avrebbero visto assegnarsi automaticamente un nome JNDI globale, usando il pattern appena descritto (cioè nome EAR/nome EJB/tipo interfaccia). Il nome EJB è il primo valore non vuoto della seguente lista:"
#. Tag: para
-#: Configuration.xml:387
+#: Configuration.xml:409
#, no-c-format
msgid "The value of the <literal><ejb-name></literal> element in ejb-jar.xml"
msgstr "Il valore dell'elemento <literal><ejb-name></literal> in ejb-jar.xml"
#. Tag: para
-#: Configuration.xml:390
+#: Configuration.xml:412
#, no-c-format
msgid "The value of the <literal>name</literal> attribute in the @Stateless or @Stateful annotation"
msgstr "Il valore dell'attributo <literal>name</literal> nell'annotazione @Stateless o @Stateful"
#. Tag: para
-#: Configuration.xml:393
+#: Configuration.xml:415
#, no-c-format
msgid "The simple name of the bean class"
msgstr "Il semplice nome della classe bean"
#. Tag: para
-#: Configuration.xml:397
+#: Configuration.xml:419
#, no-c-format
msgid "Let's look at an example. Assume that you have the following EJB bean and interface defined."
msgstr "Guardiamo un esempio. Si assuma di avere definiti il seguente bean EJB ed un'interfaccia."
#. Tag: programlisting
-#: Configuration.xml:399
+#: Configuration.xml:421
#, no-c-format
msgid ""
"<![CDATA[package com.example.myapp;\n"
@@ -803,25 +848,25 @@
"]]>"
#. Tag: para
-#: Configuration.xml:401
+#: Configuration.xml:423
#, no-c-format
msgid "Assuming your EJB bean class is deployed in an EAR named myapp, the global JNDI name myapp/AuthenticatorBean/local will be assigned to it on JBoss AS. As you learned, you can reference this EJB component as a Seam component with the name <literal>authenticator</literal> and Seam will take care of finding it in JNDI according to the JNDI pattern (or <literal>@JndiName</literal> annotation)."
msgstr "Assumendo che la classe del bean EJB sia deployata in un'applicazione EAR chiamata myapp, il nome JNDI globale myapp/AuthenticatorBean/local verrà assegnato a lei in JBoss AS. Come visto, si può fare riferimento a questo componente EJB come componente Seam con il nome <literal>authenticator</literal> e Seam si preoccuperà di trovarlo in JNDI secondo il pattern JNDI (o l'annotazione <literal>@JndiName</literal>)."
#. Tag: para
-#: Configuration.xml:407
+#: Configuration.xml:429
#, no-c-format
msgid "So what about the rest of the application servers? Well, according to the Java EE spec, which most vendors try to adhere to religiously, you have to declare an EJB reference for your EJB in order for it to be assigned a JNDI name. That requires some XML. It also means that it is up to you to establish a JNDI naming convention so that you can leverage the Seam JNDI pattern. You might find the JBoss convention a good one to follow."
msgstr "Ma cosa dire rispetto ai restanti application server? In accordo alla specifica Java EE, alla quale la maggior parte dei venditori cerca di aderire in modo religioso, si deve dichiarare un riferimento EJB per il proprio EJB affinché gli venga assegnato un nome JNDI. Questo richiede un pò di XML. Significa che sta a voi stabilire una convenzione di nomi JNDI per poter sfruttare il pattern JNDI di Seam. Si potrebbe ritenere buona e usare la convenzione JBoss."
#. Tag: para
-#: Configuration.xml:413
+#: Configuration.xml:435
#, no-c-format
msgid "There are two places you have to define the EJB reference when using Seam on non-JBoss application servers. If you are going to be looking up the Seam EJB component through JSF (in a JSF view or as a JSF action listener) or a Seam JavaBean component, then you must declare the EJB reference in web.xml. Here is the EJB reference for the example component just shown:"
msgstr "Ci sono due posti dove poter definire il riferimento EJB usando Seam su application server non-JBoss. Se si cercheranno i componenti EJB di Seam attraverso JSF (in una vista JSF o in un action listener JSF) od un componente JavaBean di Seam, allora occorre dichiarare il riferimento EJB in web.xml. Ecco qua il riferimento EJB per il componente d'esempio appena mostrato:"
#. Tag: programlisting
-#: Configuration.xml:418
+#: Configuration.xml:440
#, no-c-format
msgid ""
"<![CDATA[<ejb-local-ref>\n"
@@ -839,31 +884,31 @@
"]]>"
#. Tag: para
-#: Configuration.xml:420
+#: Configuration.xml:442
#, no-c-format
msgid "This reference will cover most uses of the component in a Seam application. However, if you want to be able to inject a Seam EJB component into another Seam EJB component using <literal>@In</literal>, you need to define this EJB reference in another location. This time, it must be defined in ejb-jar.xml, and it's a bit tricker."
msgstr "Questo riferimento coprirà la maggior parte degli usi dei componenti in un'applicazione Seam. Comunque se si vuole essere in grado di iniettare un componente EJB di Seam in un altro componente usando <literal>@In</literal>, occorre definire questo riferimento EJB in un'altra posizione. Questa volta deve essere definito in ejb-jar.xml, ed è un pò più complicato."
#. Tag: para
-#: Configuration.xml:425
+#: Configuration.xml:447
#, no-c-format
msgid "Within the context of an EJB method call, you have to deal with a somewhat sheltered JNDI context. When Seam attempts to find another Seam EJB component to satisfy an injection point defined using <literal>@In</literal>, whether or not it finds it depends on whether an EJB reference exists in JNDI. Strictly speaking, you cannot simply resolve JNDI names as you please. You have to define the references explicitly. Fortunately, JBoss recognized how aggrevating this would be for the developer and all versions of JBoss automatically register EJBs so they are always available in JNDI, both to the web container and the EJB container. So if you are using JBoss, you can skip the next few paragraphs. However, if you are deploying to GlassFish, pay close attention."
msgstr "Dentro il contesto di una chiamata di metodo EJB, occorre avere a che fare con un contesto JNDI protetto. Quando Seam tenta di trovare un altro componente EJB Seam per soddisfare un punto d'iniezione definito con <literal>@In</literal>, il fatto che Seam lo trovi oppure no dipende dal fatto che esista un riferimento EJB in JNDI. In senso letterale non si può semplicemente risolvere i nomi JNDI a proprio piacimento. Occorre definire esplicitamente i riferimenti. Fortunatamente JBoss ha capito come questo sarebbe aggravante per lo sviluppatore e quindi tutte le versioni di JBoss registrano automaticamente gli EJB cosicché siano sempre disponibili in JNDI, sia nel web container sia nell'EJB container. In definitiva se si usa JBoss, si possono saltare i prossimi paragrafi. Comunque, se si usa GlassFish, si presti molta attenzione."
#. Tag: para
-#: Configuration.xml:434
+#: Configuration.xml:456
#, no-c-format
msgid "For application servers that stubbornly adhere to the EJB specification, EJB references must always be defined explicitly. But unlike with the web context, where a single resource reference covers all uses of the EJB from the web environment, you cannot declare EJB references globally in the EJB container. Instead, you have to specify the JNDI resources for a given EJB component one-by-one."
msgstr "Per gli application server che aderiscono testardamente alla specifica EJB, i riferimenti EJB devono sempre essere definititi esplicitamente. Ma diversamente dal contesto web, dove un singolo riferimento di una risorsa copre tutti gli usi di EJB, non si possono dichiarare i riferimenti EJB in modo globale nel container EJB. Invece si devono specificare le risorse JNDI per un dato componente EJB una per una."
#. Tag: para
-#: Configuration.xml:439
+#: Configuration.xml:461
#, no-c-format
msgid "Let's assume that we have an EJB named RegisterAction (the name is resolved using the three steps mentioned previously). That EJB has the following Seam injection:"
msgstr "Si assuma di avere un EJB chiamato RegisterAction (nome che viene risolto usando i tre passi menzionati prima). Questo EJB ha la seguente injection Seam:"
#. Tag: programlisting
-#: Configuration.xml:442
+#: Configuration.xml:464
#, no-c-format
msgid ""
"<![CDATA[@In(create = true)\n"
@@ -875,13 +920,13 @@
"]]>"
#. Tag: para
-#: Configuration.xml:444
+#: Configuration.xml:466
#, no-c-format
msgid "In order for this injection to work, the link must be established in the ejb-jar.xml file as follows:"
msgstr "Per fare funzionare quest'injection, il link deve essere messo nel file ejb-jar.xml come mostrato:"
#. Tag: programlisting
-#: Configuration.xml:446
+#: Configuration.xml:468
#, no-c-format
msgid ""
"<![CDATA[<ejb-jar>\n"
@@ -919,109 +964,109 @@
"]]>"
#. Tag: para
-#: Configuration.xml:448
+#: Configuration.xml:470
#, no-c-format
msgid "Notice that the contents of the <literal><ejb-local-ref></literal> are identical to what we defined in web.xml. What we are doing is bringing the reference into the EJB context where it can be used by the RegisterAction bean. You will need to add one of these references for any injection of a Seam EJB compoenent into another Seam EJB component using <literal>@In</literal>. (You can see an example of this setup in the jee5/booking example)."
msgstr "Si noti che i contenuti di <literal><ejb-local-ref></literal> sono identici a ciò che viene definito in web.xml. Ciò che viene fatto è portare il riferimento nel contesto EJB dove può essere usato dal bean RegisterAction. Occorre aggiungere uno di questi riferimenti per qualsiasi injection di componente EJB Seam in un altro componente EJB Seam con <literal>@In</literal>. (Vedere l'esempio di setup di jee5/booking)."
#. Tag: para
-#: Configuration.xml:454
+#: Configuration.xml:476
#, no-c-format
msgid "But what about <literal>@EJB</literal>? It's true that you can inject one EJB into another using <literal>@EJB</literal>. However, by doing so, you are injecting the actual EJB reference rather than the Seam EJB component instance. In this case, some Seam features will work, while others won't. That's because Seam's interceptor is invoked on any method call to an EJB component. But that only invokes Seam's server-side interceptor chain. What you lose is Seam's state management and Seam's client-side interceptor chain. Client-side interceptors handle concerns such as security and concurrency. Also, when injecting a SFSB, there is no guarantee that you will get the SFSB bound to the active session or conversation, whatever the case may be. Thus, you definitely want to inject the Seam EJB component using <literal>@In</literal>."
msgstr "E riguardo <literal>@EJB</literal>? E' vero che si può iniettare un EJB in un altro usando <literal>@EJB</literal>. Comunque, facendo così, si sta iniettando il riferimento EJB piuttosto che l'istanza del componente EJB Seam. In questo caso, alcune funzionalità di Seam funzioneranno, mentre altre no. Questo perchè l'interceptor di Seam viene invocato ad ogni chiamata di metodo in un componente EJB. Ma questo invoca solo la catena dell'interceptor Seam lato server. Ciò che viene persa è la gestione dello stato di Seam e la catena dell'interceptor lato client. Gli interceptor lato client gestiscono i concern quali sicurezza e concorrenza. Inoltre, quando si inietta un SFSB, non c'è garanzia che il SFSB venga associato alla conversazione o sessione attiva, qualunque sia il caso. Quindi si inietterà il componente EJB Seam usando <literal>@In</literal>."
#. Tag: para
-#: Configuration.xml:464
+#: Configuration.xml:486
#, 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 "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
+#: Configuration.xml:492
#, no-c-format
msgid "<![CDATA[<core:init jndi-name=\"java:comp/env/earName/#{ejbName}/local\" />]]>"
msgstr "<![CDATA[<core:init jndi-name=\"java:comp/env/earName/#{ejbName}/local\" />]]>"
#. Tag: para
-#: Configuration.xml:472
+#: Configuration.xml:494
#, 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 "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
+#: Configuration.xml:501
#, no-c-format
msgid "<![CDATA[<transaction:ejb-transaction/>]]>"
msgstr "<![CDATA[<transaction:ejb-transaction/>]]>"
#. Tag: title
-#: Configuration.xml:484
+#: Configuration.xml:506
#, no-c-format
msgid "Don't forget!"
msgstr "Non dimenticare!"
#. Tag: para
-#: Configuration.xml:486
+#: Configuration.xml:508
#, 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 "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
+#: Configuration.xml:513
#, no-c-format
msgid "In a web archive (WAR) file, you must place a <literal>seam.properties</literal> file in the <literal>WEB-INF/classes</literal> directory if you have any Seam components included here."
msgstr "Nel file WAR occorre mettere il file <literal>seam.properties</literal> nella directory <literal>WEB-INF/classes</literal> qualora si abbiano componenti Seam da includere."
#. Tag: para
-#: Configuration.xml:494
+#: Configuration.xml:516
#, no-c-format
msgid "That's why all the Seam examples have an empty <literal>seam.properties</literal> file. You can't just delete this file and expect everything to still work!"
msgstr "E' questo il motivo per cui tutti gli esempi Seam hanno un file <literal>seam.properties</literal> vuoto. Non si può cancellare questo file ed attendersi che tutto funzioni!"
#. Tag: para
-#: Configuration.xml:497
+#: Configuration.xml:519
#, 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 "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
+#: Configuration.xml:530
#, no-c-format
msgid "Using Alternate JPA Providers"
msgstr "Uso di provider JPA alternativi"
#. Tag: para
-#: Configuration.xml:510
+#: Configuration.xml:532
#, no-c-format
msgid "Seam comes packaged and configured with Hibernate as the default JPA provider. If you require using a different JPA provider you must tell <literal>seam</literal> about it."
msgstr "Seam viene assemblato e configurato con Hibernate in qualità di provider JPA. Se si vuole usare un diverso provider JPA occorre dirlo a <literal>seam</literal>."
#. Tag: title
-#: Configuration.xml:516
+#: Configuration.xml:538
#, no-c-format
msgid "This is a workaround"
msgstr "Questo è un workaround"
#. Tag: para
-#: Configuration.xml:517
+#: Configuration.xml:539
#, no-c-format
msgid "Configuration of the JPA provider will be easier in the future and will not require configuration changes, unless you are adding a custom persistence provider implementation."
msgstr "La configurazione del provider JPA sarà più semplice in futuro e non richiederà cambiamenti nella configurazione, amenoché non si aggiunga un'implementazione personalizzata del provider di persistenza."
#. Tag: para
-#: Configuration.xml:524
+#: Configuration.xml:546
#, no-c-format
msgid "Telling seam about a different JPA provider can be be done in one of two ways:"
msgstr "Comunicare a Seam di usare un altro provider JPA può essere realizzato in uno dei due modi:"
#. Tag: para
-#: Configuration.xml:525
+#: Configuration.xml:547
#, 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 "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
+#: Configuration.xml:552
#, no-c-format
msgid ""
"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider\" \n"
@@ -1035,13 +1080,13 @@
"</component>]]>"
#. Tag: para
-#: Configuration.xml:531
+#: Configuration.xml:553
#, 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 "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
+#: Configuration.xml:560
#, no-c-format
msgid ""
"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider\" \n"
@@ -1053,41 +1098,41 @@
"</component>]]>"
#. Tag: para
-#: Configuration.xml:539
+#: Configuration.xml:561
#, 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 "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
+#: Configuration.xml:569
#, no-c-format
msgid "Configuring Seam in Java EE 5"
msgstr "Configurazione di Seam in java EE 5"
#. Tag: para
-#: Configuration.xml:558
+#: Configuration.xml:580
#, 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 "Se si esegue il software in ambiente Java EE 5, questa è tutta la configurazione richiesta per usare Seam!"
# come tradurre?
#. Tag: title
-#: Configuration.xml:561
-#: Configuration.xml:656
-#: Configuration.xml:794
-#: Configuration.xml:827
+#: Configuration.xml:583
+#: Configuration.xml:678
+#: Configuration.xml:816
+#: Configuration.xml:849
#, no-c-format
msgid "Packaging"
msgstr "Packaging"
#. Tag: para
-#: Configuration.xml:563
+#: Configuration.xml:585
#, no-c-format
msgid "Once you've packaged all this stuff together into an EAR, the archive structure will look something like this:"
msgstr "Una volta impacchettato assieme tutte queste cose in un EAR, la struttura dell'archivio apparirà così:"
#. Tag: programlisting
-#: Configuration.xml:566
+#: Configuration.xml:588
#, no-c-format
msgid ""
"<![CDATA[my-application.ear/\n"
@@ -1161,97 +1206,97 @@
" ...]]>"
#. Tag: para
-#: Configuration.xml:568
+#: Configuration.xml:590
#, no-c-format
msgid "You should declare <literal>jboss-seam.jar</literal> as an ejb module in <literal>META-INF/application.xml</literal>; <literal>jboss-el.jar</literal> should be placed in the EAR's lib directory (putting it in the EAR classpath."
msgstr "Si dovrebbe dichiarare <literal>jboss-seam.jar</literal> come modulo ejb in <literal>META-INF/application.xml</literal>; <literal>jboss-el.jar</literal> dovrebbe essere collocato nella directory lib dell'EAR (mettendolo nel classpath dell'EAR)."
#. Tag: para
-#: Configuration.xml:573
+#: Configuration.xml:595
#, no-c-format
msgid "If you want to use jBPM or Drools, you must include the needed jars in the EAR's lib directory."
msgstr "Se si vuole usare jBPM o Drools, occorre includere i jar necessari nella directory lib di EAR."
#. Tag: para
-#: Configuration.xml:575
+#: Configuration.xml:597
#, no-c-format
msgid "If you want to use facelets (our recommendation), you must include <literal>jsf-facelets.jar</literal> in the <literal>WEB-INF/lib</literal> directory of the WAR."
msgstr "Se si vuole usare facelets (consigliato), occorre includere <literal>jsf-facelets.jar</literal> nella directory <literal>WEB-INF/lib</literal> del WAR."
#. Tag: para
-#: Configuration.xml:578
+#: Configuration.xml:600
#, 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 "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
+#: Configuration.xml:605
#, 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 "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
+#: Configuration.xml:608
#, no-c-format
msgid "Seam ships with several example applications that are deployable in any Java EE container that supports EJB 3.0."
msgstr "Seam porta con sé parecchi esempi di applicazioni che sono deployate in un container Java EE che supporta EJB 3.0."
#. Tag: para
-#: Configuration.xml:589
+#: Configuration.xml:611
#, 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 "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
+#: Configuration.xml:620
#, no-c-format
msgid "Configuring Seam in J2EE"
msgstr "Configurare Seam in J2EE"
#. Tag: para
-#: Configuration.xml:600
+#: Configuration.xml:622
#, 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 "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
+#: Configuration.xml:637
#, 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 "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
+#: Configuration.xml:643
#, 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 "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
+#: Configuration.xml:648
#, no-c-format
msgid "Boostrapping Hibernate in Seam"
msgstr "Boostrapping di Hibernate in Seam"
#. Tag: para
-#: Configuration.xml:628
+#: Configuration.xml:650
#, no-c-format
msgid "Seam will bootstrap a Hibernate <literal>SessionFactory</literal> from your <literal>hibernate.cfg.xml</literal> file if you install a built-in component:"
msgstr "Seam avvierà un <literal>SessionFactory</literal> di Hibernate dal file <literal>hibernate.cfg.xml</literal> se si installa un componente predefinito:"
#. Tag: programlisting
-#: Configuration.xml:631
+#: Configuration.xml:653
#, no-c-format
msgid "<![CDATA[<persistence:hibernate-session-factory name=\"hibernateSessionFactory\"/>]]>"
msgstr "<![CDATA[<persistence:hibernate-session-factory name=\"hibernateSessionFactory\"/>]]>"
#. Tag: para
-#: Configuration.xml:633
+#: Configuration.xml:655
#, 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 "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
+#: Configuration.xml:658
#, no-c-format
msgid ""
"<![CDATA[<persistence:managed-hibernate-session name=\"hibernateSession\"\n"
@@ -1261,31 +1306,31 @@
" session-factory=\"#{hibernateSessionFactory}\"/>]]>"
#. Tag: title
-#: Configuration.xml:641
+#: Configuration.xml:663
#, no-c-format
msgid "Boostrapping JPA in Seam"
msgstr "Boostrapping di JPA in Seam"
#. Tag: para
-#: Configuration.xml:643
+#: Configuration.xml:665
#, 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 "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
+#: Configuration.xml:668
#, no-c-format
msgid "<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/>]]>"
msgstr "<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/>]]>"
#. Tag: para
-#: Configuration.xml:648
+#: Configuration.xml:670
#, 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 "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
+#: Configuration.xml:673
#, no-c-format
msgid ""
"<![CDATA[<persistence:managed-persistence-context name=\"entityManager\"\n"
@@ -1295,13 +1340,13 @@
" entity-manager-factory=\"#{entityManagerFactory}\"/>]]>"
#. Tag: para
-#: Configuration.xml:658
+#: Configuration.xml:680
#, no-c-format
msgid "We can package our application as a WAR, in the following structure:"
msgstr "Si può impacchettare l'applicazione come WAR nella seguente struttura:"
#. Tag: programlisting
-#: Configuration.xml:660
+#: Configuration.xml:682
#, no-c-format
msgid ""
"<![CDATA[my-application.war/\n"
@@ -1369,115 +1414,115 @@
" ...]]>"
#. Tag: para
-#: Configuration.xml:662
+#: Configuration.xml:684
#, 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 "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
+#: Configuration.xml:691
#, no-c-format
msgid "Configuring Seam in Java SE, without JBoss Embedded"
msgstr "Configurazione di Seam in java EE 5 senza JBoss Embedded"
#. Tag: para
-#: Configuration.xml:671
+#: Configuration.xml:693
#, 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 "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
+#: Configuration.xml:697
#, no-c-format
msgid "<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/>]]>"
msgstr "<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/>]]>"
#. Tag: para
-#: Configuration.xml:677
+#: Configuration.xml:699
#, no-c-format
msgid "If you're using Hibernate, you can tell Seam to use the Hibernate transaction API like this:"
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
+#: Configuration.xml:701
#, no-c-format
msgid "<![CDATA[<transaction:hibernate-transaction session=\"#{session}\"/>]]>"
msgstr "<![CDATA[<transaction:hibernate-transaction session=\"#{session}\"/>]]>"
#. Tag: para
-#: Configuration.xml:681
+#: Configuration.xml:703
#, no-c-format
msgid "Of course, you'll also need to define a datasource."
msgstr "Certamente occorre definire un datasource."
#. Tag: para
-#: Configuration.xml:683
+#: Configuration.xml:705
#, no-c-format
msgid "A better alternative is to use JBoss Embedded to get access to the EE APIs."
msgstr "Un'alternativa migliore è usare JBoss Embedded per accedere alle API EE."
#. Tag: title
-#: Configuration.xml:688
+#: Configuration.xml:710
#, no-c-format
msgid "Configuring Seam in Java SE, with JBoss Embedded"
msgstr "Configurazione di Seam in java EE 5 con JBoss Embedded"
#. Tag: para
-#: Configuration.xml:690
+#: Configuration.xml:712
#, 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 "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
+#: Configuration.xml:715
#, 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 "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
+#: Configuration.xml:727
#, no-c-format
msgid "The booking example application may even be deployed to Tomcat."
msgstr "L'applicazione d'esempio booking può essere deployata via Tomcat."
#. Tag: title
-#: Configuration.xml:717
+#: Configuration.xml:739
#, no-c-format
msgid "Installing Embedded JBoss"
msgstr "Installare JBoss Embedded"
#. Tag: para
-#: Configuration.xml:720
+#: Configuration.xml:742
#, 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_id=228977\">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 "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_id=228977\">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
+#: Configuration.xml:756
#, 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 "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
+#: Configuration.xml:763
#, no-c-format
msgid "Remove the <literal>annotations-api.jar</literal> file from the Tomcat <literal>lib</literal> directory."
msgstr "Rimuovere il file <literal>annotations-api.jar</literal> dalla directory Tomcat <literal>lib</literal>."
#. Tag: para
-#: Configuration.xml:747
+#: Configuration.xml:769
#, no-c-format
msgid "Next, two configuration files need to be updated to add Embedded JBoss-specific functionality."
msgstr "Poi devono essere aggiornati due file di configurazione per poter aggiungere funzionalità specifiche di JBoss Embedded."
#. Tag: para
-#: Configuration.xml:753
+#: Configuration.xml:775
#, no-c-format
msgid "Add the Embedded JBoss listener <literal>EmbeddedJBossBootstrapListener</literal> to <literal>conf/server.xml</literal>. It must appear after all other listeners in the file:"
msgstr "Aggiungere il listener Embedded JBoss <literal>EmbeddedJBossBootstrapListener</literal> a <literal>conf/server.xml</literal>. Deve apparire dopo tutti gli altri listener nel file:"
#. Tag: programlisting
-#: Configuration.xml:756
+#: Configuration.xml:778
#, no-c-format
msgid ""
"<![CDATA[<Server port=\"8005\" shutdown=\"SHUTDOWN\">\n"
@@ -1499,7 +1544,7 @@
" <Listener className=\"org.apache.catalina.storeconfig.StoreConfigLifecycleListener\" />]]>"
#. Tag: programlisting
-#: Configuration.xml:757
+#: Configuration.xml:779
#, no-c-format
msgid ""
"<![CDATA[ <!-- Add this listener -->\n"
@@ -1509,13 +1554,13 @@
" <Listener className=\"org.jboss.embedded.tomcat.EmbeddedJBossBootstrapListener\" />]]>"
#. Tag: para
-#: Configuration.xml:761
+#: Configuration.xml:783
#, no-c-format
msgid "WAR file scanning should be enabled by adding the <literal>WebinfScanner</literal> listener to <literal>conf/context.xml</literal>:"
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
+#: Configuration.xml:786
#, no-c-format
msgid ""
"<![CDATA[<Context>\n"
@@ -1537,7 +1582,7 @@
" -->]]>"
#. Tag: programlisting
-#: Configuration.xml:765
+#: Configuration.xml:787
#, no-c-format
msgid ""
"<![CDATA[ <!-- Add this listener -->\n"
@@ -1547,55 +1592,55 @@
" <Listener className=\"org.jboss.embedded.tomcat.WebinfScanner\" />]]>"
#. Tag: programlisting
-#: Configuration.xml:766
+#: Configuration.xml:788
#, no-c-format
msgid "<![CDATA[</Context>]]>"
msgstr "<![CDATA[</Context>]]>"
#. Tag: para
-#: Configuration.xml:770
+#: Configuration.xml:792
#, 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 "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
+#: Configuration.xml:797
#, 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 "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
+#: Configuration.xml:801
#, no-c-format
msgid "<![CDATA[set JAVA_OPTS=%JAVA_OPTS% -Dsun.lang.ClassLoader.allowArraySyntax=true]]>"
msgstr "<![CDATA[set JAVA_OPTS=%JAVA_OPTS% -Dsun.lang.ClassLoader.allowArraySyntax=true]]>"
#. Tag: para
-#: Configuration.xml:781
+#: Configuration.xml:803
#, no-c-format
msgid "On Unix, use this syntax instead:"
msgstr "In Unix, usare invece questa sintassi:"
#. Tag: programlisting
-#: Configuration.xml:783
+#: Configuration.xml:805
#, no-c-format
msgid "<![CDATA[JAVA_OPTS=\"$JAVA_OPTS -Dsun.lang.ClassLoader.allowArraySyntax=true\"]]>"
msgstr "<![CDATA[JAVA_OPTS=\"$JAVA_OPTS -Dsun.lang.ClassLoader.allowArraySyntax=true\"]]>"
#. Tag: para
-#: Configuration.xml:788
+#: Configuration.xml:810
#, no-c-format
msgid "For more configuration options, please see the Embedded JBoss Tomcat integration <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=EmbeddedAndTomcat\">wiki entry</ulink>."
msgstr "Per ulteriorio opzioni di configurazione, si prega di vedere l'integrazione con Embedded JBoss Tomcat <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=EmbeddedAndTomcat\">wiki entry</ulink>."
#. Tag: para
-#: Configuration.xml:796
+#: Configuration.xml:818
#, no-c-format
msgid "The archive structure of a WAR-based deployment on an servlet engine like Tomcat will look something like this:"
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
+#: Configuration.xml:821
#, no-c-format
msgid ""
"<![CDATA[my-application.war/\n"
@@ -1665,25 +1710,25 @@
" ...]]>"
#. Tag: para
-#: Configuration.xml:801
+#: Configuration.xml:823
#, no-c-format
msgid "Most of the Seam example applications may be deployed to Tomcat by running <literal>ant deploy.tomcat</literal>."
msgstr "La maggior parte delle applicazioni d'esempio può essere deployata in Tomcat eseguendo <literal>ant deploy.tomcat</literal>."
#. Tag: title
-#: Configuration.xml:809
+#: Configuration.xml:831
#, no-c-format
msgid "Configuring jBPM in Seam"
msgstr "Configurazione jBPM in Seam"
#. Tag: para
-#: Configuration.xml:810
+#: Configuration.xml:832
#, 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 "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
+#: Configuration.xml:836
#, no-c-format
msgid ""
"<![CDATA[<bpm:jbpm>\n"
@@ -1709,13 +1754,13 @@
"</bpm:jbpm>]]>"
#. Tag: para
-#: Configuration.xml:816
+#: Configuration.xml:838
#, 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 "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
+#: Configuration.xml:843
#, no-c-format
msgid ""
"<![CDATA[<jbpm-configuration>\n"
@@ -1759,19 +1804,19 @@
"</jbpm-configuration>]]>"
#. Tag: para
-#: Configuration.xml:823
+#: Configuration.xml:845
#, no-c-format
msgid "The most important thing to notice here is that jBPM transaction control is disabled. Seam or EJB3 should control the JTA transactions."
msgstr "La cosa più importante da notare è che il controllo della transazione jBPM è disabilitato. Seam o EJB3 dovrebbero controllare le transazioni JTA."
#. Tag: para
-#: Configuration.xml:829
+#: Configuration.xml:851
#, 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 "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
+#: Configuration.xml:856
#, no-c-format
msgid ""
"<![CDATA[my-application.ear/\n"
@@ -1859,25 +1904,25 @@
" documentLifecycle.jpdl.xml]]>"
#. Tag: title
-#: Configuration.xml:841
+#: Configuration.xml:863
#, no-c-format
msgid "Configuring SFSB and Session Timeouts in JBoss AS"
msgstr "Configurazione di SFSB e dei timeout di sessione in JBoss AS"
#. Tag: para
-#: Configuration.xml:843
+#: Configuration.xml:865
#, 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 "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
+#: Configuration.xml:871
#, no-c-format
msgid "The default SFSB timeout can be adjusted by modifying the value of <literal>max-bean-life</literal> in the <literal>LRUStatefulContextCachePolicy</literal> cache configuration:"
msgstr "Il timeout di default di SFSB può essere impostato modificando il valore di <literal>max-bean-life</literal> nella configurazione della cache <literal>LRUStatefulContextCachePolicy</literal>:"
#. Tag: programlisting
-#: Configuration.xml:852
+#: Configuration.xml:874
#, no-c-format
msgid ""
"<![CDATA[<container-cache-conf>\n"
@@ -1919,13 +1964,13 @@
"</container-cache-conf>]]>"
#. Tag: para
-#: Configuration.xml:854
+#: Configuration.xml:876
#, 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 "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
+#: Configuration.xml:881
#, no-c-format
msgid ""
"<![CDATA[<session-config>\n"
@@ -1939,43 +1984,43 @@
"</session-config>]]>"
#. Tag: para
-#: Configuration.xml:861
+#: Configuration.xml:883
#, no-c-format
msgid "To override this value for your own application, simply include this entry in your application's own <literal>web.xml</literal>."
msgstr "Per sovrascrivere questo valore per la propria applicazione, si includa semplicemente questa riga nel proprio <literal>web.xml</literal>."
#. Tag: title
-#: Configuration.xml:867
+#: Configuration.xml:889
#, no-c-format
msgid "Running Seam in a Portlet"
msgstr "Esecuzione di Seam in un Portlet"
#. Tag: para
-#: Configuration.xml:869
+#: Configuration.xml:891
#, 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 "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
+#: Configuration.xml:902
#, no-c-format
msgid "Deploying custom resources"
msgstr "Deploy di risorse personalizzate"
#. Tag: para
-#: Configuration.xml:882
+#: Configuration.xml:904
#, no-c-format
msgid "Seam scans all jars containing <literal>/seam.properties</literal>, <literal>/META-INF/components.xml</literal> or <literal>/META-INF/seam.properties</literal> on startup for resources. For example, all classes annotated with <literal>@Name</literal> are registered with Seam as Seam components."
msgstr "Seam scansiona all'avvio tutti i jar contenenti <literal>/seam.properties</literal>, <literal>/META-INF/components.xml</literal> o <literal>/META-INF/seam.properties</literal>. Per esempio, tutte le classi annotate con <literal>@Name</literal> vengono registrate da Seam come componenti Seam."
#. Tag: para
-#: Configuration.xml:889
+#: Configuration.xml:911
#, 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 "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
+#: Configuration.xml:918
#, no-c-format
msgid ""
"<![CDATA[# A colon-separated list of annotation types to handle\n"
@@ -1986,13 +2031,13 @@
# can get hold = ?
#. Tag: para
-#: Configuration.xml:898
+#: Configuration.xml:920
#, no-c-format
msgid "Then, during application startup you can get hold of all classes annotated with <literal>@Foo</literal>:"
msgstr "Poi durante l'avvio dell'applicazione si può comunicare con tutte le classi annotate con <literal>@Foo</literal>:"
#. Tag: programlisting
-#: Configuration.xml:903
+#: Configuration.xml:925
#, no-c-format
msgid ""
"<![CDATA[@Name(\"fooStartup\")\n"
@@ -2050,13 +2095,13 @@
"}]]>"
#. Tag: para
-#: Configuration.xml:905
+#: Configuration.xml:927
#, 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 "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
+#: Configuration.xml:933
#, no-c-format
msgid ""
"<![CDATA[public class FooDeploymentHandler implements DeploymentHandler {\n"
@@ -2096,19 +2141,19 @@
"}]]>"
#. Tag: para
-#: Configuration.xml:913
+#: Configuration.xml:935
#, no-c-format
msgid "Here we are just building a list of any files with the suffix <literal>.foo.xml</literal>."
msgstr "Qua viene costruita una lista di file con il suffisso <literal>.foo.xml</literal>."
#. Tag: para
-#: Configuration.xml:918
+#: Configuration.xml:940
#, no-c-format
msgid "Then, we need to register the deployment handler with Seam in <literal>/META-INF/seam-deployment.properties</literal>. You can register multiple deployment handler using a comma separated list."
msgstr "Poi occorre registrare il deployment handler con Seam in <literal>/META-INF/seam-deployment.properties</literal>. Si possono registrare più deployment handler usando una lista separata da virgola."
#. Tag: programlisting
-#: Configuration.xml:925
+#: Configuration.xml:947
#, no-c-format
msgid ""
"<![CDATA[# For standard deployment\n"
@@ -2122,13 +2167,13 @@
"org.jboss.seam.deployment.hotDeploymentHandlers=com.acme.FooDeploymentHandler]]>"
#. Tag: para
-#: Configuration.xml:931
+#: Configuration.xml:953
#, no-c-format
msgid "Seam uses deployment handlers internally to install components and namespaces. You can easily access the deployment handler during an <literal>APPLICATION</literal> scoped component's startup:"
msgstr "Seam utilizza internamente dei deployment handler per installare componenti e namespace. Si può facilmente accedere ad un deployment handler durante l'avvio di un componente con scope <literal>APPLICATION</literal>:"
#. Tag: programlisting
-#: Configuration.xml:937
+#: Configuration.xml:959
#, no-c-format
msgid ""
"<![CDATA[@Name(\"fooStartup\")\n"
Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Webservices.po
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Webservices.po 2009-08-26 19:12:36 UTC (rev 11431)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Webservices.po 2009-08-26 19:14:02 UTC (rev 11432)
@@ -5,8 +5,8 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-07-08 14:32+0000\n"
-"PO-Revision-Date: 2009-07-08 16:40+0100\n"
+"POT-Creation-Date: 2009-08-26 18:48+0000\n"
+"PO-Revision-Date: 2009-08-26 21:12+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -359,29 +359,35 @@
#. Tag: para
#: Webservices.xml:186
#, no-c-format
-msgid "The URI starts with the pattern mapped in <literal>web.xml</literal> for the <literal>SeamResourceServlet</literal>, e.g <literal>/seam/resource</literal> if you follow the common examples. Change this setting to expose your RESTful resources under a different base. Note that this is a global change and other Seam resources (e.g. <literal>s:graphicImage</literal>) are then also served under that base path."
-msgstr "L'URI inizia con il pattern mappato in <literal>web.xml</literal> per il servlet <literal>SeamResourceServlet</literal>, ad esempio <literal>/seam/resource</literal>, se si seguono gli esempi comuni. Modificate questa impostazione per esporre le risorse RESTful con un diverso percorso di base. Si noti che questo cambiamento è globale e anche altre risorse Seam (ad esempio <literal>s:graphicImage</literal>) saranno servite sotto questo percorso di base."
+msgid "The URI starts with the host and context path of your application, e.g. <literal>http://your.hostname/myapp</literal>."
+msgstr "L'URI inizia con l'host ed il percorso del contesto dell'applicazione, es. <literal>http://your.hostname/myapp</literal>."
#. Tag: para
-#: Webservices.xml:195
+#: Webservices.xml:192
#, no-c-format
-msgid "The RESTEasy integration for Seam then appends a configurable string to the base path, by default this is <literal>/rest</literal>. Hence, the full base path of your resources would e.g. be <literal>/seam/resource/rest</literal>. We recommend that you change this string in your application, you could for example add a version number to prepare for a future REST API upgrade of your services (old clients would keep the old URI base): <literal>/seam/resource/restv1</literal>."
-msgstr "L'integratzione RESTEasy di Seam appende allora una stringa configurabile al percorso base, di default <literal>/rest</literal>. Quindi, il percorso completo delle risorse sarebbe, ad esempio, <literal>/seam/resource/rest</literal>. Si raccomanda di modificare questa stringa nella vostra applicazione. Ad esempio, si potrebbe aggiungere un numero di versione per prepararsi a futuri aggiornamenti di versione delle API REST dei vostri servizi (i vecchi client manterrebbero il vecchio URI di base): <literal>/seam/resource/restv1</literal>."
+msgid "Then the pattern mapped in <literal>web.xml</literal> for the <literal>SeamResourceServlet</literal>, e.g <literal>/seam/resource</literal> if you follow the common examples, is appended. Change this setting to expose your RESTful resources under a different base. Note that this is a global change and other Seam resources (e.g. <literal>s:graphicImage</literal>) are then also served under that base path."
+msgstr "Quindi viene accodato il pattern mappato in <literal>web.xml</literal> per il servlet <literal>SeamResourceServlet</literal>, ad esempio <literal>/seam/resource</literal>, se si seguono gli esempi comuni. Modificate questa impostazione per esporre le risorse RESTful con un diverso percorso di base. Si noti che questo cambiamento è globale e anche altre risorse Seam (ad esempio <literal>s:graphicImage</literal>) saranno servite sotto questo percorso di base."
#. Tag: para
-#: Webservices.xml:204
+#: Webservices.xml:201
#, no-c-format
-msgid "Finally, the actual resource is available under the defined <literal>@Path</literal>, e.g. a resource mapped with <literal>@Path(\"/customer\")</literal> would be available under <literal>/seam/resource/rest/customer</literal>."
-msgstr "Infine, la risorsa vera e propria è disponibile sotto il<literal>@Path</literal> definito, ad esempio una risorsa mappata con <literal>@Path(\"/customer\")</literal> sarebbe raggiungibile sotto <literal>/seam/resource/rest/customer</literal>."
+msgid "The RESTEasy integration for Seam then appends a configurable string to the base path, by default this is <literal>/rest</literal>. Hence, the full base path of your resources would e.g. be <literal>/myapp/seam/resource/rest</literal>. We recommend that you change this string in your application, you could for example add a version number to prepare for a future REST API upgrade of your services (old clients would keep the old URI base): <literal>/myapp/seam/resource/restv1</literal>."
+msgstr "L'integrazione RESTEasy di Seam accoda allora una stringa configurabile al percorso base, di default <literal>/rest</literal>. Quindi, il percorso completo delle risorse sarebbe, ad esempio, <literal>/myapp/seam/resource/rest</literal>. Si raccomanda di modificare questa stringa nella vostra applicazione. Ad esempio, si potrebbe aggiungere un numero di versione per prepararsi a futuri aggiornamenti di versione delle API REST dei vostri servizi (i vecchi client manterrebbero il vecchio URI di base): <literal>/seam/resource/restv1</literal>."
#. Tag: para
-#: Webservices.xml:212
+#: Webservices.xml:210
#, no-c-format
-msgid "As an example, the following resource definition would return a plaintext representation for any GET requests using the URI <literal>http://your.hostname/seam/resource/rest/customer/123</literal>:"
-msgstr "Come esempio, la seguente definizione di risorsa restituirebbe una rappresentazione puramente testuale for ogni richiesta GET diretta all'URI <literal>http://your.hostname/seam/resource/rest/customer/123</literal>:"
+msgid "Finally, the actual resource is available under the defined <literal>@Path</literal>, e.g. a resource mapped with <literal>@Path(\"/customer\")</literal> would be available under <literal>/myapp/seam/resource/rest/customer</literal>."
+msgstr "Infine, la risorsa vera e propria è disponibile sotto il<literal>@Path</literal> definito, ad esempio una risorsa mappata con <literal>@Path(\"/customer\")</literal> sarebbe raggiungibile sotto <literal>/myapp/seam/resource/rest/customer</literal>."
+#. Tag: para
+#: Webservices.xml:218
+#, no-c-format
+msgid "As an example, the following resource definition would return a plaintext representation for any GET requests using the URI <literal>http://your.hostname/myapp/seam/resource/rest/customer/123</literal>:"
+msgstr "Come esempio, la seguente definizione di risorsa restituirebbe una rappresentazione puramente testuale for ogni richiesta GET diretta all'URI <literal>http://your.hostname/myapp/seam/resource/rest/customer/123</literal>:"
+
#. Tag: programlisting
-#: Webservices.xml:217
+#: Webservices.xml:223
#, no-c-format
msgid ""
"<![CDATA[@Path(\"/customer\")\n"
@@ -409,13 +415,13 @@
"}]]>"
#. Tag: para
-#: Webservices.xml:219
+#: Webservices.xml:225
#, no-c-format
msgid "No additional configuration is required, you do not have to edit <literal>web.xml</literal> or any other setting if these defauls are acceptable. However, you can configure RESTEasy in your Seam application. First import the <literal>resteasy</literal> namespace into your XML configuration file header:"
msgstr "Non è richiesta alcuna configurazione addizionale, non è necessario editare il file <literal>web.xml</literal> o nessun altra configurazione se questi valori di default sono accettabili. Comunque, è possibile procedere alla configurazione RESTEasy in un'applicazione Seam. Innanzitutto, occorre importare il namespace <literal>resteasy</literal> nell'header del file di configurazione XML:"
#. Tag: programlisting
-#: Webservices.xml:225
+#: Webservices.xml:231
#, no-c-format
msgid ""
"<![CDATA[<components\n"
@@ -439,50 +445,31 @@
" http://jboss.com/products/seam/components-2.2.xsd\">]]>"
#. Tag: para
-#: Webservices.xml:227
+#: Webservices.xml:233
#, no-c-format
msgid "You can then change the <literal>/rest</literal> prefix as mentioned earlier:"
msgstr "Allora è possibile modificare il prefisso <literal>/rest</literal> come accennato in precedenza:"
#. Tag: programlisting
-#: Webservices.xml:231
+#: Webservices.xml:237
#, no-c-format
msgid "<![CDATA[<resteasy:application resource-path-prefix=\"/restv1\"/>]]>"
msgstr "<![CDATA[<resteasy:application resource-path-prefix=\"/restv1\"/>]]>"
#. Tag: para
-#: Webservices.xml:233
-#, no-c-format
-msgid "The full base path to your resources is now <literal>/seam/resource/restv1/{resource}</literal> - note that your <literal>@Path</literal> definitions and mappings do NOT change. This is an application-wide switch usually used for versioning of the HTTP API."
-msgstr "Il percorso completo alle risorse è ora <literal>/seam/resource/restv1/{resource}</literal> - si noti che che le definizioni e le mappature di tipo path <literal>@Path</literal> NON cambiano. Questo è uno \"switch\" a livello di applicazione di solito usato per la gestione delle versioni delle API HTTP."
-
-# troncamento??? ritaglio....
-#. Tag: para
#: Webservices.xml:239
#, no-c-format
-msgid "You can disable stripping of the base path if you'd like to map the full path in your resources:"
-msgstr "E' possibile disabilitare il troncamento del percorso base, qualora nelle risorse si voglia mappare il percorso completo:"
+msgid "The full base path to your resources is now <literal>/myapp/seam/resource/restv1/{resource}</literal> - note that your <literal>@Path</literal> definitions and mappings do NOT change. This is an application-wide switch usually used for versioning of the HTTP interface."
+msgstr "Il percorso completo alle risorse è ora <literal>/myapp/seam/resource/restv1/{resource}</literal> - si noti che che le definizioni e le mappature di tipo path <literal>@Path</literal> NON cambiano. Questo è uno \"switch\" a livello di applicazione di solito usato per la gestione delle versioni delle API HTTP."
-#. Tag: programlisting
-#: Webservices.xml:243
-#, no-c-format
-msgid "<![CDATA[<resteasy:application strip-seam-resource-path=\"false\"/>]]>"
-msgstr "<![CDATA[<resteasy:application strip-seam-resource-path=\"false\"/>]]>"
-
#. Tag: para
#: Webservices.xml:245
#, no-c-format
-msgid "The path of a resource is now mapped with e.g. <literal>@Path(\"/seam/resource/rest/customer\")</literal>. We do not recommend disabling this feature, as your resource class mappings are then bound to a particular deployment scenario."
-msgstr "Il percorso di una risorsa è ora mappato, per esempio, con <literal>@Path(\"/seam/resource/rest/customer\")</literal>. Non è raccomandabile disabilitare questa caratteristica, poiché le mappature delle classi delle risorse risultano allora legate al particolare scenario di deploy."
-
-#. Tag: para
-#: Webservices.xml:251
-#, no-c-format
msgid "Seam will scan your classpath for any deployed <literal>@javax.ws.rs.Path</literal> resources and any <literal>@javax.ws.rs.ext.Provider</literal> classes. You can disable scanning and configure these classes manually:"
msgstr "Seam scandaglierà il classpath alla ricerca delle risorsa <literal>@javax.ws.rs.Path</literal> e di ogni classe <literal>@javax.ws.rs.ext.Provider</literal>. E' possibile disabilitare la ricerca e configurare queste classi manualmente:"
#. Tag: programlisting
-#: Webservices.xml:257
+#: Webservices.xml:251
#, no-c-format
msgid ""
"<![CDATA[<resteasy:application\n"
@@ -522,27 +509,27 @@
# interni, precostituiti=built-in???
# marshalling=serializzazione, invio???
#. Tag: para
-#: Webservices.xml:259
+#: Webservices.xml:253
#, no-c-format
msgid "The <literal>use-built-in-providers</literal> switch enables (default) or disables the RESTEasy built-in providers. We recommend you leave them enabled, as they provide plaintext, JSON, and JAXB marshalling out of the box."
msgstr "L'interruttore <literal>use-built-in-providers</literal> abilita (default) o disabilita i provider RESTEasy precostituiti. Si raccomanda di lasciarli abilitati, poiché essi forniscono automaticamente la gestione del \"marshalling\" testuale, JSON, e JAXB."
# Seam <literal>jndi-pattern</literal> su <literal><core:init/></literal>????????????
#. Tag: para
-#: Webservices.xml:265
+#: Webservices.xml:259
#, no-c-format
-msgid "RESTEasy supports plain EJBs (EJBs that are not Seam components) as resources. Instead of configuring the JNDI names in a non-portable fashion in <literal>web.xml</literal> (see RESTEasy documentation), you can simply list the EJB implementation classes, not the business interfaces, in <literal>components.xml</literal> as shown above. Note that you have to annotate the <literal>@Local</literal> interface of the EJB with <literal>@Path</literal>, <literal>@GET</literal>, and so on - not the bean implementation class. This allows you to keep your application deployment-portable with the global Seam <literal>jndi-pattern</literal> switch on <literal><core:init/></literal>. Note that EJB resources will not be found even if scanning of resources is enabled, you always have to list them manually. Again, this is only relevant for EJB resources that are not also Seam components and that do not have a <literal>@Name</literal> annotation."
-msgstr "RESTEasy supporta gli EJB semplici (EJB che non sono componenti Seam) alla stregua di risorse. Invece di configurare i nomi JNDI in modo non portabile nel file<literal>web.xml</literal> (si veda la documentazione RESTEasy), è possibile elencare semplicemente le classi di implementazione degli EJB, non le interfacce di business, nel file <literal>components.xml</literal>, come mostrato sopra. Si noti che si deve annotare l'interfaccia <literal>@Local</literal> dell'EJB con <literal>@Path</literal>, <literal>@GET</literal>, e così via - non la classe di implementazionedel bean. Ciò permette di mantenere l'applicazione portabile rispetto al tipo di deploy con lo switch globale di Seam <literal>jndi-pattern</literal> su <literal><core:init/></literal>. Si noti che le risorse EJB non verrano trovate anche se la ricerca delle risorse è abilitata, bisogna sempre elencarle manualmente. Di nuovo, ciò è rilevante solo per risorse EJB che non sono anche componenti !
Seam e che non hanno l'annotazione <literal>@Name</literal>."
+msgid "RESTEasy supports plain EJBs (EJBs that are not Seam components) as resources. Instead of configuring the JNDI names in a non-portable fashion in <literal>web.xml</literal> (see RESTEasy documentation), you can simply list the EJB implementation classes, not the business interfaces, in <literal>components.xml</literal> as shown above. Note that you have to annotate the <literal>@Local</literal> interface of the EJB with <literal>@Path</literal>, <literal>@GET</literal>, and so on - not the bean implementation class. This allows you to keep your application deployment-portable with the global Seam <literal>jndi-pattern</literal> switch on <literal><core:init/></literal>. Note that plain (non-Seam component) EJB resources will not be found even if scanning of resources is enabled, you always have to list them manually. Again, this whole paragraph is only relevant for EJB resources that are not also Seam components and that do not have an <literal>@Name</literal> !
annotation."
+msgstr "RESTEasy supporta gli EJB semplici (EJB che non sono componenti Seam) alla stregua di risorse. Invece di configurare i nomi JNDI in modo non portabile nel file<literal>web.xml</literal> (si veda la documentazione RESTEasy), è possibile elencare semplicemente le classi di implementazione degli EJB, non le interfacce di business, nel file <literal>components.xml</literal>, come mostrato sopra. Si noti che si deve annotare l'interfaccia <literal>@Local</literal> dell'EJB con <literal>@Path</literal>, <literal>@GET</literal>, e così via - non la classe di implementazione del bean. Ciò permette di mantenere l'applicazione portabile rispetto al tipo di deploy con lo switch globale di Seam <literal>jndi-pattern</literal> su <literal><core:init/></literal>. Si noti che le risorse EJB (componenti non-Seam) non verranno trovate anche se la ricerca delle risorse è abilitata, bisogna sempre elencarle manualmente. Di nuovo, ciò è rilevante solo per risorse EJB che no!
n sono anche componenti Seam e che non hanno l'annotazione <literal>@Name</literal>."
# verificare, molto aprossimativo
#. Tag: para
-#: Webservices.xml:277
+#: Webservices.xml:272
#, no-c-format
msgid "Finally, you can configure media type and language URI extensions:"
msgstr "Infine, è possibile configurare le estensioni degli URI dei tipi di media e dei linguaggi:"
#. Tag: programlisting
-#: Webservices.xml:281
+#: Webservices.xml:276
#, no-c-format
msgid ""
"<![CDATA[<resteasy:application>\n"
@@ -571,31 +558,31 @@
# VERIFICARE
#. Tag: para
-#: Webservices.xml:283
+#: Webservices.xml:278
#, no-c-format
msgid "This definition would map the URI suffix of <literal>.txt.deutsch</literal> to additional <literal>Accept</literal> and <literal>Accept-Language</literal> header values <literal>text/plain</literal> and <literal>de-DE</literal>."
msgstr "Questa definizione mapperebbe il suffisso dell'URI di <literal>.txt.deutsch</literal> sui valori aggiuntivi <literal>text/plain</literal> and <literal>de-DE</literal> ripettivamente degli header <literal>Accept</literal> e <literal>Accept-Language</literal>."
#. Tag: title
-#: Webservices.xml:292
+#: Webservices.xml:287
#, no-c-format
msgid "Resources and providers as Seam components"
msgstr "Risorse e provider come componenti Seam"
#. Tag: para
-#: Webservices.xml:294
+#: Webservices.xml:289
#, no-c-format
msgid "Any resource and provider instances are managed by RESTEasy by default. That means a resource class will be instantiated by RESTEasy and serve a single request, after which it will be destroyed. This is the default JAX-RS lifecycle. Providers are instantiated once for the whole application and are effectively singletons and supposed to be stateless."
msgstr "Qualunque istanza di risorsa e di provider è gestita da RESTEasy di default. Ciò significa che la classe di una risorsa sarà istanziata da RESTEasy e servirà una singola richiesta, dopo di ché sarà distrutta. I provider sono istanziati una sola volta per tutta l'applicazione e in effetti sono dei singletons che sono supposti stateless."
#. Tag: para
-#: Webservices.xml:301
+#: Webservices.xml:296
#, no-c-format
msgid "You can write resources and providers as Seam components and benefit from the richer lifecycle management of Seam, and interception for bijection, security, and so on. Simply make your resource class a Seam component:"
msgstr "E' possibile scrivere risorse e provider come componenti Seam e trarre beneficio dalla più ricca gestione del ciclo di vita di Seam e dall'interception, dalla bijection, dalla sicurezza e così via. Occorre semplicemente rendere la classe della risorsa un componente Seam:"
#. Tag: programlisting
-#: Webservices.xml:307
+#: Webservices.xml:302
#, no-c-format
msgid ""
"<![CDATA[@Name(\"customerResource\")\n"
@@ -631,19 +618,19 @@
"}]]>"
#. Tag: para
-#: Webservices.xml:309
+#: Webservices.xml:304
#, no-c-format
msgid "An instance of <literal>customerResource</literal> is now handled by Seam when a request hits the server. This is a Seam JavaBean component that is <literal>EVENT</literal>-scoped, hence no different than the default JAX-RS lifecycle. You get full Seam injection and interception support, and all other Seam components and contexts are available to you. Currently also supported are <literal>APPLICATION</literal> and <literal>STATELESS</literal> resource Seam components. These three scopes allow you to create an effectively stateless Seam middle-tier HTTP request-processing application."
msgstr "Quando una richiesta raggiunge il server, un'istanza di <literal>customerResource</literal> viene ora gestita da Seam. Si tratta di un componente JavaBean di Seam con scope <literal>EVENT</literal>, quindi in nulla diverso dal ciclo di vita del JAX-RS di default. Si ottiene il completo supporto di Seam per la bijection e tutti gli altri componenti e contesti di Seam sono disponibili. Attualmente sono supportati anche i componenti Seam che sono risorse di tipo <literal>APPLICATION</literal> e <literal>STATELESS</literal>. Questi tre scope permettono di creare un'applicazione Seam middle-tier che processa le richieste HTTP in modo stateless."
#. Tag: para
-#: Webservices.xml:318
+#: Webservices.xml:313
#, no-c-format
msgid "You can annotate an interface and keep the implementation free from JAX-RS annotations:"
msgstr "Si può annotare un'interfaccia e mantenere l'implementazione libera da annotazioni JAX-RS:"
#. Tag: programlisting
-#: Webservices.xml:322
+#: Webservices.xml:317
#, no-c-format
msgid ""
"<![CDATA[@Path(\"/customer\")\n"
@@ -667,7 +654,7 @@
"}]]>"
#. Tag: programlisting
-#: Webservices.xml:324
+#: Webservices.xml:319
#, no-c-format
msgid ""
"<![CDATA[@Name(\"customerResource\")\n"
@@ -697,105 +684,105 @@
"}]]>"
#. Tag: para
-#: Webservices.xml:326
+#: Webservices.xml:321
#, no-c-format
msgid "You can use <literal>SESSION</literal>-scoped Seam components. By default, the session will however be shortened to a single request. In other words, when an HTTP request is being processed by the RESTEasy integration code, an HTTP session will be created so that Seam components can utilize that context. When the request has been processed, Seam will look at the session and decide if the session was created only to serve that single request (no session identifier has been provided with the request, or no session existed for the request). If the session has been created only to serve this request, the session will be destroyed after the request!"
msgstr "E' possibile utilizzare componenti Seam con scope <literal>SESSION</literal>. Di default, la sessione sarà comunque ridotta ad una singola richiesta. In altre parole, mentre una richiesta HTTP viene processata dal codice di integrazione RESTEasy, viene creata una sessione HTTP in modo che i componenti Seam possano utilizzare tale contesto. Dopo che la richiesta è stata processata, Seam esamina la sessione e decide se è stata creata soltanto per servire quella singola richiesta (nessun identificatore di sessione è stato fornito con la richiesta o nessuna sessione esiste per la richiesta). Se la sessione è stata creata solo per servire la richiesta corrente, essa sarà distrutta al termine della richiesta!"
#. Tag: para
-#: Webservices.xml:335
+#: Webservices.xml:330
#, no-c-format
msgid "Assuming that your Seam application only uses event, application, or stateless components, this procedure prevents exhaustion of available HTTP sessions on the server. The RESTEasy integration with Seam assumes by default that sessions are not used, hence anemic sessions would add up as every REST request would start a session that will only be removed when timed out."
msgstr "Assumendo che l'applicazione Seam usi solo componenti evento, applicazione o stateless, questa procedura previene l'esaurimento delle sessioni HTTP sul server. L'integrazione RESTEasy di Seam assume di default che le sessioni non siano usate, poiché si aggiungerebbero sessioni anemiche all'avvio di una sessione da parte di ciascuna richiesta REST, sessione che sarà rimossa solo alla scadenza."
#. Tag: para
-#: Webservices.xml:342
+#: Webservices.xml:337
#, no-c-format
msgid "If your RESTful Seam application has to preserve session state across REST HTTP requests, disable this behavior in your configuration file:"
msgstr "Se l'applicazione RESTful di Seam deve preservare lo stato della sessione fra richieste HTTP REST, occorre disabilitare questo comportamento nel file di configurazione:"
#. Tag: programlisting
-#: Webservices.xml:347
+#: Webservices.xml:342
#, no-c-format
msgid "<![CDATA[<resteasy:application destroy-session-after-request=\"false\"/>]]>"
msgstr "<![CDATA[<resteasy:application destroy-session-after-request=\"false\"/>]]>"
#. Tag: para
-#: Webservices.xml:349
+#: Webservices.xml:344
#, no-c-format
msgid "Every REST HTTP request will now create a new session that will only be removed by timeout or explicit invalidation in your code through <literal>Session.instance().invalidate()</literal>. It is your responsibility to pass a valid session identifier along with your HTTP requests, if you want to utilize the session context across requests."
msgstr "Tutte le richieste HTTP RESTful creeranno ora una nuova sessione che sarà rimossa soltanto alla sua scadenza o per invalidazione esplicita da parte del codice dell'applicazione usando <literal>Session.instance().invalidate()</literal>. E' responsabilità dello sviluppatore passare un identificatore di sessione valido insieme a ciascuna richiesta HTTP, se si vuole utilizzare il contesto di sessione tra una richiesta e l'altra."
#. Tag: para
-#: Webservices.xml:356
+#: Webservices.xml:351
#, no-c-format
msgid "<literal>CONVERSATION</literal>-scoped resource components and mapping of conversations to temporary HTTP resources and paths is planned but currently not supported."
msgstr "Risorse che siano componenti con scope <literal>CONVERSATION</literal> e la mappatura delle conversazioni su risorse e percorsi HTTP temporanei è nei piani ma non ancora supportato."
#. Tag: para
-#: Webservices.xml:361
+#: Webservices.xml:356
#, no-c-format
msgid "EJB Seam components are supported. Always annotate the local business interface, not the EJB implementation class, with JAX-RS annotations. The EJB has to be <literal>STATELESS</literal>."
msgstr "Sono supportati i componenti EJB Seam. Si annoti sempre l'interfaccia locale di business, non la classe di implementazione EJB, con le annotazioni JAX-RS. L'EJB deve essere <literal>STATELESS</literal>."
#. Tag: para
-#: Webservices.xml:366
+#: Webservices.xml:361
#, no-c-format
msgid "Provider classes can also be Seam components, only <literal>APPLICATION</literal>-scoped provider components are supported. You can annotate the bean interface or implementation with JAX-RS annotations. EJB Seam components as providers are currently <emphasis>NOT</emphasis> supported, only POJOs!"
msgstr "Le classi del provider possono essere componenti Seam, vengono supportati solo i componenti provider con scope <literal>APPLICATION</literal>. Si può annotare l'interfaccia bean o l'implementazione con le annotazioni JAX-RS. I componenti EJB Seam come provider <emphasis>NON</emphasis> sono attualmente supportati, solo i POJO!"
#. Tag: title
-#: Webservices.xml:375
+#: Webservices.xml:370
#, no-c-format
msgid "Securing resources"
msgstr "Sicurezza della risorse"
#. Tag: para
-#: Webservices.xml:377
+#: Webservices.xml:372
#, no-c-format
msgid "You can enable the Seam authentication filter for HTTP Basic and Digest authentication in <literal>components.xml</literal>:"
msgstr "Si può abilitare il filtro di autenticazione per l'autenticazione HTTP Basic e Digest in <literal>components.xml</literal>:"
#. Tag: programlisting
-#: Webservices.xml:382
+#: Webservices.xml:377
#, no-c-format
msgid "<![CDATA[<web:authentication-filter url-pattern=\"/seam/resource/rest/*\" auth-type=\"basic\"/>]]>"
msgstr "<![CDATA[<web:authentication-filter url-pattern=\"/seam/resource/rest/*\" auth-type=\"basic\"/>]]>"
#. Tag: para
-#: Webservices.xml:384
+#: Webservices.xml:379
#, no-c-format
msgid "See the Seam security chapter on how to write an authentication routine."
msgstr "Si veda il capitolo sulla sicurezza di Seam per sapere come scrivere la routine di autenticazione."
#. Tag: para
-#: Webservices.xml:388
+#: Webservices.xml:383
#, no-c-format
msgid "After successful authentication, authorization rules with the common <literal>@Restrict</literal> and <literal>@PermissionCheck</literal> annotations are in effect. You can also access the client <literal>Identity</literal>, work with permission mapping, and so on. All regular Seam security features for authorization are available."
msgstr "Dopo che l'autenticazione ha avuto successo, hanno effetto le regole di autorizzazione con le annotazioni <literal>@Restrict</literal> e <literal>@PermissionCheck</literal>. Si può anche accedere <literal>Identity</literal> del client, lavorare con la mappatura dei permessi, e così via. Sono disponibili tutte le caratteristiche di sicurezza di Seam per l'autorizzazione."
#. Tag: title
-#: Webservices.xml:398
+#: Webservices.xml:393
#, no-c-format
msgid "Mapping exceptions to HTTP responses"
msgstr "Mappare eccezioni e risposte HTTP"
# VERIFICARE ultima frase
#. Tag: para
-#: Webservices.xml:400
+#: Webservices.xml:395
#, no-c-format
msgid "Section 3.3.4 of the JAX-RS specification defines how checked or unchecked exceptions are handled by the JAX RS implementation. In addition to using an exception mapping provider as defined by JAX-RS, the integration of RESTEasy with Seam allows you to map exceptions to HTTP response codes within Seam's <literal>pages.xml</literal> facility. If you are already using <literal>pages.xml</literal> declarations, this is easier to maintain than potentially many JAX RS exception mapper classes."
msgstr "La sezione 3.3.4 delle specifiche JAX-RS definisce come le eccezioni di tipo checked o unchecked debbano essere trattate dall'implementazione JAX-RS. Oltre all'utilizzo di un provider della mappatura delle eccezioni come definito dalle JAX-RS, l'integrazione di RESTEasy con Seam permette di mappare le eccezioni con i codici di risposta HTTP all'interno del file <literal>pages.xml</literal> di Seam. Se si stanno già utilizzando dichiarazioni di <literal>pages.xml</literal>, ciò è più semplice da manutenetere delle numerose potenziali classi JAX RS di mappatura delle eccezioni."
# VERIFICARE: not - as some Seam examples might show - a request URI pattern that doesn't cover your REST request paths
#. Tag: para
-#: Webservices.xml:408
+#: Webservices.xml:403
#, no-c-format
msgid "Exception handling within Seam requires that the Seam filter is executed for your HTTP request. Ensure that you do filter <emphasis>all</emphasis> requests in your <literal>web.xml</literal>, not - as some Seam examples might show - a request URI pattern that doesn't cover your REST request paths. The following example intercepts <emphasis>all</emphasis> HTTP requests and enables Seam exception handling:"
msgstr "In Seam la gestione delle eccezioni richiede che il filtro di Seam intercetti le richieste HTTP. Assicuratevi di filtrare <emphasis>tutte</emphasis> le richieste nel file <literal>web.xml</literal>, e non - come mostrato in alcuni esempi di Seam - quelle corrispondenti ad URI di richiesta che non coprono i percorsi delle richieste REST. L'esempio seguente intercetta <emphasis>tutte</emphasis> le richieste HTTP e abilita la gestione delle eccezioni di Seam:"
#. Tag: programlisting
-#: Webservices.xml:415
+#: Webservices.xml:410
#, no-c-format
msgid ""
"<![CDATA[<filter>\n"
@@ -819,13 +806,13 @@
"</filter-mapping>]]>"
#. Tag: para
-#: Webservices.xml:417
+#: Webservices.xml:412
#, no-c-format
msgid "To convert the unchecked <literal>UnsupportedOperationException</literal> thrown by your resource methods to a <literal>501 Not Implemented</literal> HTTP status response, add the following to your <literal>pages.xml</literal> descriptor:"
msgstr "Per convertire l'eccezione unchecked <literal>UnsupportedOperationException</literal> lanciata dai metodi delle risorse nel codice di riposta HTTP <literal>501 Not Implemented</literal> , occorre aggiungere ciò che segue al descrittore <literal>pages.xml</literal>:"
#. Tag: programlisting
-#: Webservices.xml:423
+#: Webservices.xml:418
#, no-c-format
msgid ""
"<![CDATA[<exception class=\"java.lang.UnsupportedOperationException\">\n"
@@ -841,13 +828,13 @@
"</exception>]]>"
#. Tag: para
-#: Webservices.xml:425
+#: Webservices.xml:420
#, no-c-format
msgid "Custom or checked exceptions are handled the same:"
msgstr "Le eccezioni di tipo custom e di tipo checked sono gestite allo stesso modo:"
#. Tag: programlisting
-#: Webservices.xml:429
+#: Webservices.xml:424
#, no-c-format
msgid ""
"<![CDATA[<exception class=\"my.CustomException\" log=\"false\">\n"
@@ -863,31 +850,31 @@
"</exception>]]>"
#. Tag: para
-#: Webservices.xml:431
+#: Webservices.xml:426
#, no-c-format
msgid "You do not have to send an HTTP error to the client if an exception occurs. Seam allows you to map the exception as a redirect to a view of your Seam application. As this feature is typically used for human clients (web browsers) and not for REST API remote clients, you should pay extra attention to conflicting exception mappings in <literal>pages.xml</literal>."
msgstr "Se si verifica un'eccezione, non è necessario inviare al client un codice di errore HTTP. Seam permette di mappare l'eccezione con la redirezione ad una vista dell'applicazione Seam . Poichè questa caratteristica è tipicamente usata per i client umani (browser web) e non per i client remoti dell'API REST, occorre prestare un'attenzione particolare a mappature di eccezioni in conflitto fra loro in <literal>pages.xml</literal>."
#. Tag: para
-#: Webservices.xml:438
+#: Webservices.xml:433
#, no-c-format
msgid "Note that the HTTP response still passes through the servlet container, so an additional mapping might apply if you have <literal><error-page></literal> mappings in your <literal>web.xml</literal> configuration. The HTTP status code would then be mapped to a rendered HTML error page with status <literal>200 OK</literal>!"
msgstr "Si noti che la risposta HTTP continua a passare attraverso il servlet container, così che è possibile apportare una mappatura aggiuntiva se nel file <literal>web.xml</literal> vi sono delle mappature <literal><error-page></literal>. Il codice di risposta HHTP sarebbe in questo caso mappato con una pagina HTML di errore con codice <literal>200 OK</literal>!"
#. Tag: title
-#: Webservices.xml:447
+#: Webservices.xml:442
#, no-c-format
msgid "Testing resources and providers"
msgstr "Test delle risorse e dei provider"
#. Tag: para
-#: Webservices.xml:449
+#: Webservices.xml:444
#, no-c-format
msgid "Seam includes a unit testing utility class that helps you create unit tests for a RESTful architecture. Extend the <literal>SeamTest</literal> class as usual and use the <literal>ResourceRequestEnvironment.ResourceRequest</literal> to emulate HTTP requests/response cycles:"
msgstr "Seam include una classe d'utilità che agevola la creazione di test d'unità per un architettura RESTful. Si estenda la classe <literal>SeamTest</literal> come al solito e si usi <literal>ResourceRequestEnvironment.ResourceRequest</literal> per emulare i cicli richiesta/risposta HTTP:"
#. Tag: programlisting
-#: Webservices.xml:455
+#: Webservices.xml:450
#, no-c-format
msgid ""
"<![CDATA[import org.jboss.seam.mock.ResourceRequestEnvironment;\n"
@@ -985,13 +972,13 @@
"}]]>"
#. Tag: para
-#: Webservices.xml:457
+#: Webservices.xml:452
#, no-c-format
msgid "This test only executes local calls, it does not communicate with the <literal>SeamResourceServlet</literal> through TCP. The mock request is passed through the Seam servlet and filters and the response is then available for test assertions. Overriding the <literal>getDefaultHeaders()</literal> method in a shared instance of <literal>ResourceRequestEnvironment</literal> allows you to set request headers for every test method in the test class."
msgstr "Questo test esegue soltanto chiamate locali, non comunica con <literal>SeamResourceServlet</literal> attraverso TCP. La richiesta mock viene passata attraverso il servlet ed i filtri Seam e la risposta è poi disponibile per asserzioni di test. L'override del metodo <literal>getDefaultHeaders()</literal> in un'istanza condivisa di <literal>ResourceRequestEnvironment</literal> consente di impostare gli header di richiesta per ogni metodo di test nella classe di test."
#. Tag: para
-#: Webservices.xml:465
+#: Webservices.xml:460
#, no-c-format
msgid "Note that a <literal>ResourceRequest</literal> has to be executed in a <literal>@Test</literal> method or in a <literal>@BeforeMethod</literal> callback. You can not execute it in any other callback, such as <literal>@BeforeClass</literal>."
msgstr "Si noti che <literal>ResourceRequest</literal> deve essere eseguita in un metodo <literal>@Test</literal> o in una callback <literal>@BeforeMethod</literal>. Si può, ma non si dovrebbe eseguirla in altre callback, come <literal>@BeforeClass</literal>."
Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Websphere.po
===================================================================
--- branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Websphere.po 2009-08-26 19:12:36 UTC (rev 11431)
+++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/it-IT/Websphere.po 2009-08-26 19:14:02 UTC (rev 11432)
@@ -5,8 +5,8 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-08-22 13:17+0000\n"
-"PO-Revision-Date: 2009-08-22 15:25+0100\n"
+"POT-Creation-Date: 2009-08-26 18:48+0000\n"
+"PO-Revision-Date: 2009-08-26 21:13+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -58,13 +58,13 @@
#. Tag: para
#: Websphere.xml:35
#, no-c-format
-msgid "The following sections in this chapter assume that WebSphere is correctly installed and is functional, and a profile has been successfully created."
+msgid "The following sections in this chapter assume that WebSphere is correctly installed and is functional, and a WebSphere \"profile\" has been successfully created."
msgstr ""
#. Tag: para
#: Websphere.xml:40
#, no-c-format
-msgid "This chapter explain how to compile, deploy and run some sample applications in WebSphere. These sample applications require a database. WebSphere comes by default with a set of sample applications called \"Default Application\". This set of sample applications use a Derby database running on the Derby instance installed with WebSphere. In order to keep this simple we'll use this Derby database created for the \"Default Applications\". However, to run the sample application with the Derby database \"as-is\", a patched Hibernate dialect must be used (The patch changes the default \"auto\" key generation strategy) as explained in <xref linkend=\"glassfish\"/>. If you want to use another database, it's just a matter of creating a connection pool in WebSphere pointing to this database, declare the correct Hibernate dialect and set the correct JNDI name in <literal>persistence.xml</literal>."
+msgid "This chapter explains how to compile, deploy and run some sample applications in WebSphere. These sample applications require a database. WebSphere comes by default with a set of sample applications called \"Default Application\". This set of sample applications use a Derby database running on the Derby instance installed within WebSphere. In order to keep this simple we'll use this Derby database created for the \"Default Applications\". However, to run the sample application with the Derby database \"as-is\", a patched Hibernate dialect must be used (The patch changes the default \"auto\" key generation strategy) as explained in <xref linkend=\"glassfish\"/>. If you want to use another database, it's just a matter of creating a connection pool in WebSphere pointing to this database, declare the correct Hibernate dialect and set the correct JNDI name in <literal>persistence.xml</literal>."
msgstr ""
#. Tag: title
@@ -106,32 +106,32 @@
#. Tag: listitem
#: Websphere.xml:70
#, no-c-format
-msgid "On the right navigation menu, select <literal>Web Container Settings/Web container</literal>)"
+msgid "On the right navigation menu, select <literal>Web Container Settings/Web container</literal>"
msgstr ""
#. Tag: listitem
#: Websphere.xml:73
-#, no-c-format
-msgid "On the right navigation menu, select <literal>custom properties</literal>) and add the following properties:"
-msgstr ""
+#, fuzzy, no-c-format
+msgid "On the right navigation menu, select <literal>custom properties</literal> and add the following properties:"
+msgstr "Aggiornamento del file <literal>build.xml</literal>"
#. Tag: literal
#: Websphere.xml:77
#, no-c-format
msgid "prependSlashToResource = true"
-msgstr ""
+msgstr "prependSlashToResource = true"
#. Tag: literal
#: Websphere.xml:80
#, no-c-format
msgid "com.ibm.ws.webcontainer.invokefilterscompatibility = true"
-msgstr ""
+msgstr "com.ibm.ws.webcontainer.invokefilterscompatibility = true"
#. Tag: listitem
#: Websphere.xml:84
-#, no-c-format
-msgid "Save and restart the server"
-msgstr ""
+#, fuzzy, no-c-format
+msgid "Save the configuration and restart the server"
+msgstr "Sotto sono riportate le modifiche al file di configurazione necessarie all'esempio base."
#. Tag: title
#: Websphere.xml:92
@@ -146,99 +146,99 @@
msgstr ""
#. Tag: listitem
-#: Websphere.xml:97
+#: Websphere.xml:96
#, no-c-format
-msgid "The global <literal>jndi-pattern</literal> switch on the <literal><core:init></literal>. in <literal>components.xml</literal>. The switch can use a special placeholder \"<literal>#{ejbName}</literal>\" that resolves to the unqualified name of the EJB"
+msgid "The global <literal>jndi-pattern</literal> switch on the <literal><core:init></literal>tag in <literal>components.xml</literal>. The switch can use a special placeholder \"<literal>#{ejbName}</literal>\" that resolves to the unqualified name of the EJB"
msgstr ""
#. Tag: para
-#: Websphere.xml:102
+#: Websphere.xml:100
#, fuzzy, no-c-format
msgid "The <literal>@JndiName</literal> annotation"
msgstr "Selezionare il pulsante <literal>Next</literal>."
#. Tag: para
-#: Websphere.xml:108
+#: Websphere.xml:106
#, no-c-format
msgid "gives detailed explanations on how those mechanisms work."
msgstr ""
#. Tag: para
-#: Websphere.xml:112
+#: Websphere.xml:110
#, no-c-format
-msgid "By default, WebSphere will bind the session bean in its local JNDI name space under a \"short\" binding name that adheres to the following pattern <literal>ejblocal:<package.qualified.local.interface.name></literal>."
+msgid "By default, WebSphere will bind session beans in its local JNDI name space under a \"short\" binding name that adheres to the following pattern <literal>ejblocal:<package.qualified.local.interface.name></literal>."
msgstr ""
#. Tag: para
-#: Websphere.xml:117
+#: Websphere.xml:115
#, no-c-format
msgid "For a detailed description on how WebSphere v7 organizes and binds EJBs in its JNDI name spaces, please refer to the WebSphere Information Center."
msgstr ""
#. Tag: para
-#: Websphere.xml:120
+#: Websphere.xml:118
#, no-c-format
msgid "As explained before, Seam needs to lookup for session bean as they appear in JNDI. Basically, there are three strategies, in order of complexity:"
msgstr ""
#. Tag: listitem
-#: Websphere.xml:124
+#: Websphere.xml:121
#, no-c-format
-msgid "Specify which JNDI name Seam must use for each session bean using the <literal>@JndiName</literal> annotation in the java source file"
+msgid "Specify which JNDI name Seam must use for each session bean using the <literal>@JndiName</literal> annotation in the java source file,"
msgstr ""
#. Tag: listitem
-#: Websphere.xml:127
+#: Websphere.xml:123
#, no-c-format
-msgid "Override the default session bean names generated by WebSphere to conform to the <literal>jndi-pattern</literal> attribute"
+msgid "Override the default session bean names generated by WebSphere to conform to the <literal>jndi-pattern</literal> attribute,"
msgstr ""
#. Tag: listitem
-#: Websphere.xml:130
+#: Websphere.xml:126
#, no-c-format
-msgid "Use EJB references"
+msgid "Use EJB references."
msgstr ""
#. Tag: title
-#: Websphere.xml:137
+#: Websphere.xml:133
#, no-c-format
msgid "Strategy 1: Specify which JNDI name Seam must use for each Session Bean"
msgstr ""
#. Tag: para
-#: Websphere.xml:138
+#: Websphere.xml:134
#, no-c-format
msgid "This strategy is the simplest and fastest one regarding development. It uses the WebSphere v7 default binding mechanism. To use this strategy:"
msgstr ""
#. Tag: listitem
-#: Websphere.xml:141
+#: Websphere.xml:137
#, no-c-format
msgid "Add a <literal>@JndiName(\"ejblocal:<package.qualified.local.interface.name>)</literal> annotation to each session bean that is a Seam component."
msgstr ""
#. Tag: para
-#: Websphere.xml:145
-#: Websphere.xml:188
+#: Websphere.xml:141
+#: Websphere.xml:184
#, no-c-format
msgid "<para>In <literal>components.xml</literal>, add the following line:</para>"
msgstr ""
#. Tag: programlisting
-#: Websphere.xml:147
-#: Websphere.xml:220
+#: Websphere.xml:143
+#: Websphere.xml:216
#, no-c-format
msgid "<![CDATA[<core:init jndi-name=\"java:comp/env/#{ejbName}\" />]]>"
msgstr "<![CDATA[<core:init jndi-name=\"java:comp/env/#{ejbName}\" />]]>"
#. Tag: para
-#: Websphere.xml:151
+#: Websphere.xml:147
#, no-c-format
msgid "Add a file named <literal>WEB-INF/classes/seam-jndi.properties</literal> in the web module with the following content:"
msgstr ""
#. Tag: programlisting
-#: Websphere.xml:153
+#: Websphere.xml:149
#, no-c-format
msgid ""
"com.ibm.websphere.naming.hostname.normalizer=com.ibm.ws.naming.util.DefaultHostnameNormalizer\n"
@@ -257,13 +257,13 @@
msgstr ""
#. Tag: para
-#: Websphere.xml:157
+#: Websphere.xml:153
#, fuzzy, no-c-format
msgid "At the end of <literal>web.xml</literal>, add the following lines:"
msgstr "Aggiornamento del file <literal>build.xml</literal>"
#. Tag: programlisting
-#: Websphere.xml:159
+#: Websphere.xml:155
#, no-c-format
msgid ""
"<![CDATA[<ejb-local-ref>\n"
@@ -281,37 +281,37 @@
" </ejb-local-ref>]]>"
#. Tag: para
-#: Websphere.xml:164
+#: Websphere.xml:160
#, no-c-format
msgid "That's all folks! No need to update any file during the development, nor to define any EJB to EJB or web to EJB reference!"
msgstr ""
#. Tag: para
-#: Websphere.xml:167
+#: Websphere.xml:163
#, no-c-format
-msgid "Compared to the other strategies, this strategy has the advantage not to have to manage any EJBs reference and also not to have to maintain extra files. The only drawback is one extra line in the java source code with the <literal>@JndiName</literal> annotation"
+msgid "Compared to the other strategies, this strategy has the advantage to not have to manage any EJBs reference and also to not have to maintain extra files. The only drawback is one extra line in the java source code with the <literal>@JndiName</literal> annotation"
msgstr ""
#. Tag: title
-#: Websphere.xml:174
+#: Websphere.xml:170
#, no-c-format
msgid "Strategy 2: Override the default names generated by WebSphere"
msgstr ""
#. Tag: section
-#: Websphere.xml:174
+#: Websphere.xml:170
#, no-c-format
msgid "There is no simple way to globally override the default naming strategy for session beans in WebSphere. However, WebSphere provides a way to override the name of each bean."
msgstr ""
#. Tag: para
-#: Websphere.xml:177
+#: Websphere.xml:173
#, no-c-format
msgid "To use this strategy:"
msgstr ""
#. Tag: para
-#: Websphere.xml:181
+#: Websphere.xml:177
#, no-c-format
msgid ""
"Add a file named <literal>META-INF/ibm-ejb-jar-ext.xml</literal> in the EJB module and add an entry for each session bean like this: <programlisting role=\"XML\"><![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
@@ -329,25 +329,25 @@
msgstr ""
#. Tag: programlisting
-#: Websphere.xml:190
+#: Websphere.xml:186
#, no-c-format
msgid "<![CDATA[<core:init jndi-name=\"ejblocal:#{ejbName}\" />]]>"
msgstr "<![CDATA[<core:init jndi-name=\"ejblocal:#{ejbName}\" />]]>"
#. Tag: para
-#: Websphere.xml:194
+#: Websphere.xml:190
#, no-c-format
msgid "Add a file named <literal>WEB-INF/classes/seam-jndi.properties</literal> as described in strategy 1"
msgstr ""
#. Tag: para
-#: Websphere.xml:199
+#: Websphere.xml:195
#, no-c-format
msgid "In <literal>web.xml</literal>, add the following lines (Note the different <literal>ejb-ref-name</literal> value):"
msgstr ""
#. Tag: programlisting
-#: Websphere.xml:201
+#: Websphere.xml:197
#, no-c-format
msgid ""
"<![CDATA[<ejb-local-ref>\n"
@@ -365,55 +365,55 @@
" </ejb-local-ref>]]>"
#. Tag: para
-#: Websphere.xml:206
+#: Websphere.xml:202
#, no-c-format
msgid "Compared to the first strategy, this strategy requires to maintain an extra file (<literal>META-INF/ibm-ejb-jar-ext.xml</literal>), where a line must be added each time a new session bean is added to the application), but still does not require to maintain EJB reference between beans."
msgstr ""
#. Tag: title
-#: Websphere.xml:215
+#: Websphere.xml:211
#, no-c-format
msgid "Strategy 3: Use EJB references"
msgstr ""
#. Tag: section
-#: Websphere.xml:215
+#: Websphere.xml:211
#, no-c-format
msgid "This strategy is based on the usage of EJB references, from EJB to EJB and from the web module to EJB. To use it:"
msgstr ""
#. Tag: listitem
-#: Websphere.xml:218
+#: Websphere.xml:214
#, no-c-format
msgid "<listitem>In <literal>components.xml</literal>, add the following line:</listitem>"
msgstr ""
#. Tag: para
-#: Websphere.xml:223
+#: Websphere.xml:219
#, no-c-format
msgid "Follow the instructions in <xref linkend=\"config.integration.ejb.container\"/> to declare the references from web to EJB and from EJB to EJB"
msgstr ""
#. Tag: para
-#: Websphere.xml:228
+#: Websphere.xml:224
#, no-c-format
msgid "This is the most tedious strategy as each session bean referenced by another session bean (i.e. \"injected\") as to be declared in <literal>ejb-jar.xml</literal> file. Also, each new session bean has to be added to the list of referenced bean in <literal>web.xml</literal>"
msgstr ""
#. Tag: title
-#: Websphere.xml:239
+#: Websphere.xml:235
#, no-c-format
msgid "Configuring timeouts for Stateful Session Beans"
msgstr ""
#. Tag: para
-#: Websphere.xml:240
+#: Websphere.xml:236
#, no-c-format
-msgid "A timeout value has to be set for each stateful session bean used in the application because stateful bean must not expire in WebSphere while Seam might still need thenm. At the time of writing this document, WebSphere does not provide a way to configure a global timeout at neither the cluster, server, application nor ejb-jar level. It has to be done for each stateful bean individually. This is done by adding a file named <literal>META-INF/ibm-ejb-jar-ext.xml</literal> in the EJB module, and declare the timeout value for each bean:"
+msgid "A timeout value has to be set for each stateful session bean used in the application because stateful bean must not expire in WebSphere while Seam might still need them. At the time of writing this document, WebSphere does not provide a way to configure a global timeout at neither the cluster, server, application nor ejb-jar level. It has to be done for each stateful bean individually. By default, the default timeout is 10 minutes. This is done by adding a file named <literal>META-INF/ibm-ejb-jar-ext.xml</literal> in the EJB module, and declare the timeout value for each bean:"
msgstr ""
#. Tag: programlisting
-#: Websphere.xml:246
+#: Websphere.xml:242
#, no-c-format
msgid ""
"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
@@ -443,316 +443,327 @@
"</ejb-jar-ext>]]>"
#. Tag: para
-#: Websphere.xml:248
+#: Websphere.xml:244
#, no-c-format
-msgid "The <literal>time-out</literal> is expressed in seconds and must be higher than the Seam conversation expiration timeout and a few minutes higher than the user's HTTP session timeout (The session expiration timeout can trigger a few minutes after the number of minutes declared to expire s for the HTTP session expiration)."
+msgid "The <literal>time-out</literal> is expressed in seconds and must be higher than the Seam conversation expiration timeout and a few minutes higher than the user's HTTP session timeout (The session expiration timeout can trigger a few minutes after the number of minutes declared to expire the HTTP session)."
msgstr ""
#. Tag: title
-#: Websphere.xml:257
+#: Websphere.xml:253
#, no-c-format
msgid "The <literal>jee5/booking</literal> example"
msgstr "L'esempio <literal>jee5/booking</literal>"
#. Tag: para
-#: Websphere.xml:259
+#: Websphere.xml:255
#, fuzzy, no-c-format
msgid "The<literal>jee5/booking</literal>example is based on the Hotel Booking example (which runs on JBoss AS). Out of the box, it is designed to run on Glassfish, but with the following steps, it can be deployed on WebSphere. It is located in the <literal>$SEAM_DIST/examples/jee5/booking</literal> directory."
msgstr "L'esempio <literal>jee5/booking</literal> è basato sull'esempio PrenotazioneHotel (che gira su JBoss AS). E' stato progettato per girare anche su Glassfish, ma con i passi descritti sotto può essere deployato in Websphere. E' collocato nella directory <literal>$SEAM_DIST/examples/jee5/booking</literal>."
#. Tag: para
-#: Websphere.xml:265
+#: Websphere.xml:261
+#, fuzzy, no-c-format
+msgid "The example already has a breakout of configurations and build scripts for WebSphere. First thing, we are going to do is build and deploy this example. Then we'll go over some key changes that we needed."
+msgstr "La prima cosa da fare è costruire e deployare quell'esempio. Poi verranno apportate delle modifiche chiave necessarie."
+
+#. Tag: para
+#: Websphere.xml:266
#, no-c-format
-msgid "For running this example, we'll use the second JNDI mapping strategy (\"Override the default names generated by WebSphere\") as we don't want to change the java code to add the <literal>@JndiName</literal> annotation as in the first strategy."
+msgid "The tailored configuration files for WebSphere use the second JNDI mapping strategy (\"Override the default names generated by WebSphere\") as the goal was to not change any java code to add the <literal>@JndiName</literal> annotation as in the first strategy."
msgstr ""
#. Tag: title
-#: Websphere.xml:271
+#: Websphere.xml:272
#, no-c-format
msgid "Building the <literal>jee5/booking</literal> example"
msgstr "Build dell'esempio <literal>jee5/booking</literal>"
#. Tag: para
-#: Websphere.xml:273
+#: Websphere.xml:274
#, fuzzy, no-c-format
msgid "Building it only requires running the correct ant command: <programlisting>ant -f build-websphere7.xml</programlisting> This will create container specific distribution and exploded archive directories with the <literal>websphere7</literal> label."
msgstr "Il building richiede l'esecuzione del corretto comando ant: <programlisting>ant websphere7</programlisting>. Questo creerà una distribuzione specifica per il container e le directory esplose per l'archivio con etichetta <literal>websphere7</literal>."
#. Tag: title
-#: Websphere.xml:280
+#: Websphere.xml:281
#, fuzzy, no-c-format
msgid "Deploying the <literal>jee5/booking</literal> example"
msgstr "Build dell'esempio <literal>jee5/booking</literal>"
#. Tag: para
-#: Websphere.xml:281
+#: Websphere.xml:282
#, fuzzy, no-c-format
-msgid "The steps below are for the WAS version stated above.The ports are default values, if you changed them, you must substitute the values."
+msgid "The steps below are for the WAS version stated above.The ports are the default values, if you changed them, you must substitute the values."
msgstr "I passi sottostanti riguardano la versione WAS dichiarata all'inizio. Le porte sono ai valori di default, se vengono cambiati occorre sostituire i valori."
#. Tag: listitem
-#: Websphere.xml:284
+#: Websphere.xml:285
#, fuzzy, no-c-format
msgid "Log in to the administration console <programlisting><![CDATA[http://localhost:9060/admin]]></programlisting> Enter your userid annd/or your password if security is enabled for the console."
msgstr "Fare il login nella console di amministrazione <programlisting><![CDATA[https://localhost:9043/admin]]></programlisting> oppure"
#. Tag: para
-#: Websphere.xml:291
+#: Websphere.xml:292
#, fuzzy, no-c-format
msgid "Go to the <literal>WebSphere enterprise applications</literal> menu option under the <literal>Applications --> Application Type</literal> left side menu."
msgstr "Accedere all'opzione menu <literal>Websphere enterprise applications</literal> sotto il menu a sinistra <literal>Applications --> Application Type</literal>."
#. Tag: para
-#: Websphere.xml:298
+#: Websphere.xml:299
#, no-c-format
msgid "At the top of the <literal>Enterprise Applications</literal> table select <literal>Install</literal>. Below are installation wizard pages and what needs to done on each:"
msgstr "In cima alla tabella <literal>Enterprise Applications</literal> selezionare <literal>Install</literal>. Sotto sono visualizzate le pagine del wizard con ciò che va fatto su ciascuna:"
#. Tag: literal
-#: Websphere.xml:304
+#: Websphere.xml:305
#, no-c-format
msgid "Preparing for the application installation"
msgstr "Preparazione per l'installazione dell'applicazione"
#. Tag: para
-#: Websphere.xml:307
+#: Websphere.xml:308
#, fuzzy, no-c-format
msgid "Browse to the <literal>examples/jee5/booking/dist-websphere7/jboss-seam-jee5.ear</literal> file using the file upload widget."
msgstr "Andare fino al file <literal>examples/jee5/booking/dist/jboss-seam-jee5.ear</literal> usando il widget di upload dei file."
#. Tag: para
-#: Websphere.xml:313
-#: Websphere.xml:323
-#: Websphere.xml:341
+#: Websphere.xml:314
+#: Websphere.xml:324
+#: Websphere.xml:342
#, no-c-format
msgid "Select the <literal>Next</literal> button."
msgstr "Selezionare il pulsante <literal>Next</literal>."
#. Tag: para
-#: Websphere.xml:318
+#: Websphere.xml:319
#, no-c-format
msgid "Select the <literal>Fast Path</literal> button."
msgstr "Selezionare il pulsante <literal>Fast Path</literal>."
#. Tag: literal
-#: Websphere.xml:332
+#: Websphere.xml:333
#, no-c-format
msgid "Select installation options"
msgstr "Selezionare le opzioni di installazione"
#. Tag: para
-#: Websphere.xml:335
+#: Websphere.xml:336
#, fuzzy, no-c-format
msgid "Select the <literal>Deploy enterprise beans and Allow EJB reference targets to resolve automatically</literal> check boxes at the bottom of the page. This will let WebSphere use its simplified JNDI reference mapping."
msgstr "Selezionare i check box <literal>Deploy enterprise beans</literal> e <literal>Allow EJB reference targets to resolve automatically</literal>. Queso serve amenoché si usi il tool di Websphere AS per impacchettare l'applicazione."
#. Tag: literal
-#: Websphere.xml:350
+#: Websphere.xml:351
#, no-c-format
msgid "Map modules to servers"
msgstr "Mappare i moduli sul server"
#. Tag: para
-#: Websphere.xml:353
+#: Websphere.xml:354
#, fuzzy, no-c-format
msgid "No changes needed here as we only have one server. Select the <literal>Next</literal>button."
msgstr "Avendo un solo server non sono necessarie modifiche. Selezionare il pulsante <literal>Next</literal>."
#. Tag: literal
-#: Websphere.xml:362
+#: Websphere.xml:363
#, fuzzy, no-c-format
msgid "Map virtual hosts for Web modules"
msgstr "Mappare context roots per i moduli Web"
#. Tag: para
-#: Websphere.xml:365
+#: Websphere.xml:366
#, fuzzy, no-c-format
msgid "No changes needed here as we only have one virtual host. Select the <literal>Next</literal>button."
msgstr "Avendo un solo server non sono necessarie modifiche. Selezionare il pulsante <literal>Next</literal>."
#. Tag: literal
-#: Websphere.xml:374
+#: Websphere.xml:375
#, no-c-format
msgid "Summary"
msgstr "Sommario"
#. Tag: para
-#: Websphere.xml:377
+#: Websphere.xml:378
#, no-c-format
msgid "No changes needed here. Select the <literal>Finish</literal> button."
msgstr "Non sono necessarie modifiche. Selezionare il pulsante <literal>Finish</literal>."
#. Tag: literal
-#: Websphere.xml:384
+#: Websphere.xml:385
#, no-c-format
msgid "Installation"
msgstr "Installazione"
#. Tag: para
-#: Websphere.xml:387
+#: Websphere.xml:388
#, fuzzy, no-c-format
msgid "Now you will see WebSphere installing and deploying your application."
msgstr "Ora si vedra l'installazione ed il deploy dell'applicazione."
#. Tag: para
-#: Websphere.xml:390
+#: Websphere.xml:391
#, fuzzy, no-c-format
msgid "When done, select the <literal>Save</literal> link and you will be returned to the <literal>Enterprise Applications</literal> table."
msgstr "Quando termina selezionare il link <literal>Save</literal> e si verrà reindirizzati alla tabella <literal>Enterprise Applications</literal>."
#. Tag: para
-#: Websphere.xml:399
+#: Websphere.xml:400
#, fuzzy, no-c-format
-msgid "To start the application select our application in the list, then click on the <literal>Start</literal> button at the top of the table."
+msgid "To start the application, select the application in the list, then click on the <literal>Start</literal> button at the top of the table."
msgstr "Per avviare l'applicazione ritornare alla tabella <literal>Enterprise Applications</literal> e selezionare l'applicazione nella lista. Quindi scegliere il pulsante <literal>Start</literal> in cima alla tabella."
#. Tag: para
-#: Websphere.xml:409
+#: Websphere.xml:410
#, fuzzy, no-c-format
msgid "You can now access the application at <literal>http://localhost:9080/seam-jee5-booking</literal>"
msgstr "Ora si può accedere all'applicazione all'indirizzo <literal>http://localhost:9080/seam-jee5-booking/index.html</literal>."
#. Tag: title
-#: Websphere.xml:418
+#: Websphere.xml:419
#, no-c-format
msgid "Deviation from the original base files"
msgstr ""
#. Tag: section
-#: Websphere.xml:418
+#: Websphere.xml:419
#, no-c-format
msgid "Below are the differences between the base configuration files and the WebSphere specific files held in the <literal>resources-websphere7</literal> directory."
msgstr ""
#. Tag: para
-#: Websphere.xml:422
+#: Websphere.xml:423
#, no-c-format
msgid "<literal>META-INF/ejb-jar.xml</literal> — Removed all the EJB references"
msgstr ""
#. Tag: para
-#: Websphere.xml:428
+#: Websphere.xml:429
#, no-c-format
-msgid "<literal>META-INF/ibm-ejb-jar-bnd.xml</literal> — This WebSphere specific file has been added as we use the second JNDI mapping strategy. It defines, for each session bean, the name WebSphere will use to bind it its JNDI name space"
+msgid "<literal>META-INF/ibm-ejb-jar-bnd.xml</literal> — This WebSphere specific file has been added as we use the second JNDI mapping strategy. It defines, for each session bean, the name WebSphere will use to bind it in its JNDI name space"
msgstr ""
#. Tag: para
-#: Websphere.xml:435
+#: Websphere.xml:436
#, no-c-format
-msgid "<literal>META-INF/ibm-ejb-jar-ext.xml</literal> — This WebSphere specific file defines to WebSphere, the timeout value for each stateful bean"
+msgid "<literal>META-INF/ibm-ejb-jar-ext.xml</literal> — This WebSphere specific file defines the timeout value for each stateful bean"
msgstr ""
#. Tag: para
-#: Websphere.xml:441
+#: Websphere.xml:442
#, fuzzy, no-c-format
-msgid "<literal>META-INF/persistence.xml</literal> — The main changes here are for the datasource JNDI path, switching to the WebSphere transaction manager lookup class, turning off the <literal>hibernate.transaction.flush_before_completion</literal> toggle, and forcing the Hibernate dialect to be <literal>GlassfishDerbyDialect</literal> how as using the integrated Derby database"
+msgid "<literal>META-INF/persistence.xml</literal> — The main changes here are for the datasource JNDI path, switching to the WebSphere transaction manager lookup class, turning off the <literal>hibernate.transaction.flush_before_completion</literal> toggle, and forcing the Hibernate dialect to be <literal>GlassfishDerbyDialect</literal> as we are using the integrated Derby database"
msgstr "<literal>META-INF/persistence.xml</literal> — le maggiori modifiche sono per il path JNDI del datasource, passando alla classe di ricerca del gestore di transazioni Websphere e cambiando il dialetto Hibernate a <literal>GlassfishDerbyDialect</literal>."
#. Tag: para
-#: Websphere.xml:451
+#: Websphere.xml:452
#, fuzzy, no-c-format
msgid "<literal>WEB-INF/components.xml</literal> — the change here is <literal>jndi-pattern</literal> to use <literal>ejblocal:#{ejbname}</literal> as using the second JNDI matching strategy"
msgstr "<literal>WEB-INF/components.xml</literal> — qua la modifica è <literal>jndi-pattern</literal> senza la stringa /local."
#. Tag: para
-#: Websphere.xml:459
+#: Websphere.xml:460
#, no-c-format
msgid "<literal>WEB-INF/web.xml</literal> — Remove all the <literal>ejb-local ref</literal> except the one for <literal>EjbSynchronizations</literal> bean. Changed the ref fo this bean to <literal>ejblocal:EjbSynchronizations</literal>"
msgstr ""
#. Tag: para
-#: Websphere.xml:467
-#: Websphere.xml:549
+#: Websphere.xml:468
#, fuzzy, no-c-format
msgid "<literal>import.sql</literal> — due to the cutomized hibernate Derby dialect, the <literal>ID</literal> column can not be populated by this file and was removed."
msgstr "<literal>import.sql</literal> — la colonna <literal>ID</literal> sia del dialetto sia del Derby DB non può essere popolata ed è stata rimossa."
#. Tag: para
-#: Websphere.xml:474
+#: Websphere.xml:475
#, no-c-format
msgid "Also the build procedure has been changed to include the <literal>log4j.jar</literal> file and exclude the <literal>concurrent.jar</literal> and <literal>jboss-common-core.jar</literal> files."
msgstr ""
#. Tag: title
-#: Websphere.xml:486
+#: Websphere.xml:487
#, no-c-format
msgid "The <literal>jpa</literal> booking example"
msgstr "Esempio Prenotazione <literal>jpa</literal>"
#. Tag: para
-#: Websphere.xml:488
+#: Websphere.xml:489
#, fuzzy, no-c-format
msgid "This is the Hotel Booking example implemented in Seam POJOs and using Hibernate JPA with JPA transactions. It does not use EJB3."
msgstr "Fortunatamente far funzionare l'esempio <literal>jpa</literal> è molto più semplice che per l'esempio <literal>jee5</literal>. Questo è l'esempio Prenotazione Hotel implementato in Seam POJOs usando Hibernate JPA con le transazioni JPA. Non usa EJB3."
#. Tag: para
-#: Websphere.xml:493
+#: Websphere.xml:494
#, fuzzy, no-c-format
msgid "The example already has a breakout of configurations and build scripts for many of the common containers including WebSphere."
msgstr "L'esempio ha già un pò di configurazioni e build script per molti comuni container incluso Websphere."
#. Tag: para
-#: Websphere.xml:498
+#: Websphere.xml:499
#, fuzzy, no-c-format
msgid "First thing, we are going to do is build and deploy that example. Then we'll go over some key changes that we needed."
msgstr "La prima cosa da fare è costruire e deployare quell'esempio. Poi verranno apportate delle modifiche chiave necessarie."
#. Tag: title
-#: Websphere.xml:504
+#: Websphere.xml:505
#, no-c-format
msgid "Building the <literal>jpa</literal> example"
msgstr "Build dell'esempio <literal>jpa</literal>"
#. Tag: para
-#: Websphere.xml:505
+#: Websphere.xml:506
#, no-c-format
msgid "Building it only requires running the correct ant command: <programlisting>ant websphere7</programlisting> This will create container specific distribution and exploded archive directories with the <literal>websphere7</literal> label."
msgstr "Il building richiede l'esecuzione del corretto comando ant: <programlisting>ant websphere7</programlisting>. Questo creerà una distribuzione specifica per il container e le directory esplose per l'archivio con etichetta <literal>websphere7</literal>."
#. Tag: title
-#: Websphere.xml:514
+#: Websphere.xml:515
#, no-c-format
msgid "Deploying the <literal>jpa</literal> example"
msgstr "Deploy dell'esempio <literal>jpa</literal>"
#. Tag: para
-#: Websphere.xml:515
+#: Websphere.xml:516
#, no-c-format
msgid "Deploying <literal>jpa</literal> application is very similar to the <literal>jee5/booking</literal> example at <xref linkend=\"jee5-websphere-deploy\"/>. The main difference is, that this time, we will deploy a war file instead of an ear file, and we'll have to manually specify the context root of the application."
msgstr ""
#. Tag: para
-#: Websphere.xml:521
+#: Websphere.xml:522
#, no-c-format
-msgid "Follow the same instructions as for the <literal>jee5/booking</literal> sample. Select the <literal>examples/jpa/dist-websphere7/jboss-seam-jpa.war</literal> file on the first page and on the <literal>Map context roots for Web modules</literal> page (after the <literal>Map virtual host for Web module</literal>), enter the context root you want to use for your application in the <literal>Contect Root</literal> input field."
+msgid "Follow the same instructions as for the <literal>jee5/booking</literal> sample. Select the <literal>examples/jpa/dist-websphere7/jboss-seam-jpa.war</literal> file on the first page and on the <literal>Map context roots for Web modules</literal> page (after the <literal>Map virtual host for Web module</literal>), enter the context root you want to use for your application in the <literal>Context Root</literal> input field."
msgstr ""
#. Tag: para
-#: Websphere.xml:528
+#: Websphere.xml:529
#, fuzzy, no-c-format
msgid "When started, you can now access the application at the <literal>http://localhost:9080/<context root></literal>."
msgstr "Si può ora accedere all'applicazione all'indirizzo <literal>http://localhost:9080/jboss-seam-jpa/index.html</literal>."
#. Tag: title
-#: Websphere.xml:534
+#: Websphere.xml:535
#, no-c-format
msgid "Deviation from the generic base files"
msgstr ""
#. Tag: section
-#: Websphere.xml:534
+#: Websphere.xml:535
#, no-c-format
msgid "Below are the configuration file differences between the base configuration files and the files customized for WebSphere held in the <literal>resources-websphere7</literal> directory."
msgstr ""
#. Tag: para
-#: Websphere.xml:539
+#: Websphere.xml:540
#, fuzzy, no-c-format
msgid "<literal>META-INF/persistence.xml</literal> — The main changes here are for the datasource JNDI path, switching to the WebSphere transaction manager look up class, turning off the <literal>hibernate.transaction.flush_before_completion</literal> toggle, and forcing the Hibernate dialect to be <literal>GlassfishDerbyDialect</literal> how as using the integrated Derby database"
msgstr "<literal>META-INF/persistence.xml</literal> — le maggiori modifiche sono per il path JNDI del datasource, passando alla classe di ricerca del gestore di transazioni Websphere e cambiando il dialetto Hibernate a <literal>GlassfishDerbyDialect</literal>."
#. Tag: para
-#: Websphere.xml:556
+#: Websphere.xml:550
+#, fuzzy, no-c-format
+msgid "<literal>import.sql</literal> — due to the customized hibernate Derby dialect, the <literal>ID</literal> column can not be populated by this file and was removed."
+msgstr "<literal>import.sql</literal> — la colonna <literal>ID</literal> sia del dialetto sia del Derby DB non può essere popolata ed è stata rimossa."
+
+#. Tag: para
+#: Websphere.xml:557
#, no-c-format
msgid "Also the build procedure have been changed to include the <literal>log4j.jar</literal> file and exclude the <literal>concurrent.jar</literal> and <literal>jboss-common-core.jar</literal> files."
msgstr ""
@@ -776,12 +787,6 @@
#~ "installazione."
#~ msgid "<title>Configuration file changes</title>"
#~ msgstr "<title>Cambiamenti al file di configurazione</title>"
-#~ msgid ""
-#~ "Below are the configuration file changes that are need to the base "
-#~ "example."
-#~ msgstr ""
-#~ "Sotto sono riportate le modifiche al file di configurazione necessarie "
-#~ "all'esempio base."
#~ msgid "resources/WEB-INF/components.xml"
#~ msgstr "resources/WEB-INF/components.xml"
#~ msgid ""
More information about the seam-commits
mailing list