Seam SVN: r9842 - trunk/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2008-12-26 21:11:25 -0500 (Fri, 26 Dec 2008)
New Revision: 9842
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Cache.po
trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Cache.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Cache.po 2008-12-25 14:16:54 UTC (rev 9841)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Cache.po 2008-12-27 02:11:25 UTC (rev 9842)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-11-06 00:22+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-27 03:10+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,128 +17,72 @@
#: Cache.xml:5
#, no-c-format
msgid "Caching"
-msgstr ""
+msgstr "Caching"
#. Tag: para
#: Cache.xml:7
#, no-c-format
-msgid ""
-"In almost all enterprise applications, the database is the primary "
-"bottleneck, and the least scalable tier of the runtime environment. People "
-"from a PHP/Ruby environment will try to tell you that so-called \"shared "
-"nothing\" architectures scale well. While that may be literally true, I "
-"don't know of many interesting multi-user applications which can be "
-"implemented with no sharing of resources between different nodes of the "
-"cluster. What these silly people are really thinking of is a \"share nothing "
-"except for the database\" architecture. Of course, sharing the database is "
-"the primary problem with scaling a multi-user application—so the claim "
-"that this architecture is highly scalable is absurd, and tells you a lot "
-"about the kind of applications that these folks spend most of their time "
-"working on."
+msgid "In almost all enterprise applications, the database is the primary bottleneck, and the least scalable tier of the runtime environment. People from a PHP/Ruby environment will try to tell you that so-called \"shared nothing\" architectures scale well. While that may be literally true, I don't know of many interesting multi-user applications which can be implemented with no sharing of resources between different nodes of the cluster. What these silly people are really thinking of is a \"share nothing except for the database\" architecture. Of course, sharing the database is the primary problem with scaling a multi-user application—so the claim that this architecture is highly scalable is absurd, and tells you a lot about the kind of applications that these folks spend most of their time working on."
msgstr ""
#. Tag: para
#: Cache.xml:22
#, no-c-format
-msgid ""
-"Almost anything we can possibly do to share the database <emphasis>less "
-"often</emphasis> is worth doing."
+msgid "Almost anything we can possibly do to share the database <emphasis>less often</emphasis> is worth doing."
msgstr ""
#. Tag: para
#: Cache.xml:27
#, no-c-format
-msgid ""
-"This calls for a cache. Well, not just one cache. A well designed Seam "
-"application will feature a rich, multi-layered caching strategy that impacts "
-"every layer of the application:"
+msgid "This calls for a cache. Well, not just one cache. A well designed Seam application will feature a rich, multi-layered caching strategy that impacts every layer of the application:"
msgstr ""
#. Tag: para
#: Cache.xml:35
#, no-c-format
-msgid ""
-"The database, of course, has its own cache. This is super-important, but "
-"can't scale like a cache in the application tier."
+msgid "The database, of course, has its own cache. This is super-important, but can't scale like a cache in the application tier."
msgstr ""
#. Tag: para
#: Cache.xml:41
#, no-c-format
-msgid ""
-"Your ORM solution (Hibernate, or some other JPA implementation) has a second-"
-"level cache of data from the database. This is a very powerful capability, "
-"but is often misused. In a clustered environment, keeping the data in the "
-"cache transactionally consistent across the whole cluster, and with the "
-"database, is quite expensive. It makes most sense for data which is shared "
-"between many users, and is updated rarely. In traditional stateless "
-"architectures, people often try to use the second-level cache for "
-"conversational state. This is always bad, and is especially wrong in Seam."
+msgid "Your ORM solution (Hibernate, or some other JPA implementation) has a second-level cache of data from the database. This is a very powerful capability, but is often misused. In a clustered environment, keeping the data in the cache transactionally consistent across the whole cluster, and with the database, is quite expensive. It makes most sense for data which is shared between many users, and is updated rarely. In traditional stateless architectures, people often try to use the second-level cache for conversational state. This is always bad, and is especially wrong in Seam."
msgstr ""
#. Tag: para
#: Cache.xml:55
#, no-c-format
-msgid ""
-"The Seam conversation context is a cache of conversational state. Components "
-"you put into the conversation context can hold and cache state relating to "
-"the current user interaction."
+msgid "The Seam conversation context is a cache of conversational state. Components you put into the conversation context can hold and cache state relating to the current user interaction."
msgstr ""
#. Tag: para
#: Cache.xml:62
#, no-c-format
-msgid ""
-"In particular, the Seam-managed persistence context (or an extended EJB "
-"container-managed persistence context associated with a conversation-scoped "
-"stateful session bean) acts as a cache of data that has been read in the "
-"current conversation. This cache tends to have a pretty high hitrate! Seam "
-"optimizes the replication of Seam-managed persistence contexts in a "
-"clustered environment, and there is no requirement for transactional "
-"consistency with the database (optimistic locking is sufficient) so you "
-"don't need to worry too much about the performance implications of this "
-"cache, unless you read thousands of objects into a single persistence "
-"context."
+msgid "In particular, the Seam-managed persistence context (or an extended EJB container-managed persistence context associated with a conversation-scoped stateful session bean) acts as a cache of data that has been read in the current conversation. This cache tends to have a pretty high hitrate! Seam optimizes the replication of Seam-managed persistence contexts in a clustered environment, and there is no requirement for transactional consistency with the database (optimistic locking is sufficient) so you don't need to worry too much about the performance implications of this cache, unless you read thousands of objects into a single persistence context."
msgstr ""
#. Tag: para
#: Cache.xml:77
#, no-c-format
-msgid ""
-"The application can cache non-transactional state in the Seam application "
-"context. State kept in the application context is of course not visible to "
-"other nodes in the cluster."
+msgid "The application can cache non-transactional state in the Seam application context. State kept in the application context is of course not visible to other nodes in the cluster."
msgstr ""
#. Tag: para
#: Cache.xml:84
#, no-c-format
-msgid ""
-"The application can cache transactional state using the Seam "
-"<literal>cacheProvider</literal> component, which integrates JBossCache, "
-"JBoss POJO Cache or EHCache into the Seam environment. This state will be "
-"visible to other nodes if your cache supports running in a clustered mode."
+msgid "The application can cache transactional state using the Seam <literal>cacheProvider</literal> component, which integrates JBossCache, JBoss POJO Cache or EHCache into the Seam environment. This state will be visible to other nodes if your cache supports running in a clustered mode."
msgstr ""
#. Tag: para
#: Cache.xml:93
#, no-c-format
-msgid ""
-"Finally, Seam lets you cache rendered fragments of a JSF page. Unlike the "
-"ORM second-level cache, this cache is not automatically invalidated when "
-"data changes, so you need to write application code to perform explicit "
-"invalidation, or set appropriate expiration policies."
+msgid "Finally, Seam lets you cache rendered fragments of a JSF page. Unlike the ORM second-level cache, this cache is not automatically invalidated when data changes, so you need to write application code to perform explicit invalidation, or set appropriate expiration policies."
msgstr ""
#. Tag: para
#: Cache.xml:103
#, no-c-format
-msgid ""
-"For more information about the second-level cache, you'll need to refer to "
-"the documentation of your ORM solution, since this is an extremely complex "
-"topic. In this section we'll discuss the use of caching directly, via the "
-"<literal>cacheProvider</literal> component, or as the page fragment cache, "
-"via the <literal><s:cache></literal> control."
+msgid "For more information about the second-level cache, you'll need to refer to the documentation of your ORM solution, since this is an extremely complex topic. In this section we'll discuss the use of caching directly, via the <literal>cacheProvider</literal> component, or as the page fragment cache, via the <literal><s:cache></literal> control."
msgstr ""
#. Tag: title
@@ -150,9 +94,7 @@
#. Tag: para
#: Cache.xml:114
#, no-c-format
-msgid ""
-"The built-in <literal>cacheProvider</literal> component manages an instance "
-"of:"
+msgid "The built-in <literal>cacheProvider</literal> component manages an instance of:"
msgstr ""
#. Tag: term
@@ -165,7 +107,7 @@
#: Cache.xml:127
#, no-c-format
msgid "org.jboss.cache.TreeCache"
-msgstr ""
+msgstr "org.jboss.cache.TreeCache"
#. Tag: term
#: Cache.xml:132
@@ -177,20 +119,19 @@
#: Cache.xml:138
#, no-c-format
msgid "org.jboss.cache.Cache"
-msgstr ""
+msgstr "org.jboss.cache.Cache"
#. Tag: term
#: Cache.xml:143
#, no-c-format
-msgid ""
-"JBoss POJO Cache 1.x (suitable for use in JBoss 4.2.x and other containers)"
+msgid "JBoss POJO Cache 1.x (suitable for use in JBoss 4.2.x and other containers)"
msgstr ""
#. Tag: literal
#: Cache.xml:149
#, no-c-format
msgid "org.jboss.cache.aop.PojoCache"
-msgstr ""
+msgstr "org.jboss.cache.aop.PojoCache"
#. Tag: term
#: Cache.xml:154
@@ -202,137 +143,116 @@
#: Cache.xml:159
#, no-c-format
msgid "net.sf.ehcache.CacheManager"
-msgstr ""
+msgstr "net.sf.ehcache.CacheManager"
#. Tag: para
#: Cache.xml:165
#, no-c-format
-msgid ""
-"You can safely put any immutable Java object in the cache, and it will be "
-"stored in the cache and replicated across the cluster (assuming that "
-"replication is supported and enabled). If you want to keep mutable objects "
-"in the cache read the documentation of the underling caching project "
-"documentation to discover how to notify the cache of changes to the cache."
+msgid "You can safely put any immutable Java object in the cache, and it will be stored in the cache and replicated across the cluster (assuming that replication is supported and enabled). If you want to keep mutable objects in the cache read the documentation of the underling caching project documentation to discover how to notify the cache of changes to the cache."
msgstr ""
#. Tag: para
#: Cache.xml:174
#, no-c-format
-msgid ""
-"To use <literal>cacheProvider</literal>, you need to include the jars of the "
-"cache implementation in your project:"
+msgid "To use <literal>cacheProvider</literal>, you need to include the jars of the cache implementation in your project:"
msgstr ""
#. Tag: term
#: Cache.xml:181
#, no-c-format
msgid "JBoss Cache 1.x"
-msgstr ""
+msgstr "JBoss Cache 1.x"
#. Tag: para
-#: Cache.xml:187 Cache.xml:225
+#: Cache.xml:187
+#: Cache.xml:225
#, no-c-format
msgid "<literal>jboss-cache.jar</literal> - JBoss Cache 1.4.1"
-msgstr ""
+msgstr "<literal>jboss-cache.jar</literal> - JBoss Cache 1.4.1"
#. Tag: para
-#: Cache.xml:192 Cache.xml:230
+#: Cache.xml:192
+#: Cache.xml:230
#, no-c-format
msgid "<literal>jgroups.jar</literal> - JGroups 2.4.1"
-msgstr ""
+msgstr "<literal>jgroups.jar</literal> - JGroups 2.4.1"
#. Tag: term
#: Cache.xml:200
#, no-c-format
msgid "JBoss Cache 2.x"
-msgstr ""
+msgstr "JBoss Cache 2.x"
#. Tag: para
#: Cache.xml:206
#, no-c-format
msgid "<literal>jboss-cache.jar</literal> - JBoss Cache 2.2.0"
-msgstr ""
+msgstr "<literal>jboss-cache.jar</literal> - JBoss Cache 2.2.0"
#. Tag: para
#: Cache.xml:211
#, no-c-format
msgid "<literal>jgroups.jar</literal> - JGroups 2.6.2"
-msgstr ""
+msgstr "<literal>jgroups.jar</literal> - JGroups 2.6.2"
#. Tag: term
#: Cache.xml:219
#, no-c-format
msgid "JBoss POJO Cache 1.x"
-msgstr ""
+msgstr "JBoss POJO Cache 1.x"
#. Tag: para
#: Cache.xml:235
#, no-c-format
msgid "<literal>jboss-aop.jar</literal> - JBoss AOP 1.5.0"
-msgstr ""
+msgstr "<literal>jboss-aop.jar</literal> - JBoss AOP 1.5.0"
#. Tag: term
#: Cache.xml:243
#, no-c-format
msgid "EHCache"
-msgstr ""
+msgstr "EHCache"
#. Tag: para
#: Cache.xml:249
#, no-c-format
msgid "<literal>ehcache.jar</literal> - EHCache 1.2.3"
-msgstr ""
+msgstr "<literal>ehcache.jar</literal> - EHCache 1.2.3"
#. Tag: para
#: Cache.xml:259
#, no-c-format
-msgid ""
-"If you are using JBoss Cache in containers other than JBoss Application "
-"Server, look at the JBoss Cache <ulink url=\"http://wiki.jboss.org/wiki/"
-"JBossCache\">wiki</ulink> page for more dependencies."
+msgid "If you are using JBoss Cache in containers other than JBoss Application Server, look at the JBoss Cache <ulink url=\"http://wiki.jboss.org/wiki/JBossCache\">wiki</ulink> page for more dependencies."
msgstr ""
#. Tag: para
#: Cache.xml:267
#, no-c-format
-msgid ""
-"For an EAR depoyment of Seam, we recommend that the cache jars and "
-"configuration go directly into the EAR."
+msgid "For an EAR depoyment of Seam, we recommend that the cache jars and configuration go directly into the EAR."
msgstr ""
#. Tag: para
#: Cache.xml:272
#, no-c-format
-msgid ""
-"You'll also need to provide a configuration file for JBossCache. Place "
-"<literal>treecache.xml</literal> with an appropriate cache configuration "
-"into the classpath (e.g. the ejb jar or <literal>WEB-INF/classes</literal>). "
-"JBossCache has many scary and confusing configuration settings, so we won't "
-"discuss them here. Please refer to the JBossCache documentation for more "
-"information."
+msgid "You'll also need to provide a configuration file for JBossCache. Place <literal>treecache.xml</literal> with an appropriate cache configuration into the classpath (e.g. the ejb jar or <literal>WEB-INF/classes</literal>). JBossCache has many scary and confusing configuration settings, so we won't discuss them here. Please refer to the JBossCache documentation for more information."
msgstr ""
#. Tag: para
#: Cache.xml:281
#, no-c-format
-msgid ""
-"You can find a sample <literal>treecache.xml</literal> in <literal>examples/"
-"blog/resources/treecache.xml</literal>."
+msgid "You can find a sample <literal>treecache.xml</literal> in <literal>examples/blog/resources/treecache.xml</literal>."
msgstr ""
#. Tag: para
#: Cache.xml:286
#, no-c-format
-msgid ""
-"EHCache will run in it's default configuration without a configuration file"
+msgid "EHCache will run in it's default configuration without a configuration file"
msgstr ""
#. Tag: para
#: Cache.xml:291
#, no-c-format
-msgid ""
-"To alter the configuration file in use, configure your cache in "
-"<literal>components.xml</literal>:"
+msgid "To alter the configuration file in use, configure your cache in <literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -341,10 +261,13 @@
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
" xmlns:cache=\"http://jboss.com/products/seam/cache\">\n"
-" <cache:jboss-cache-provider configuration=\"META-INF/cache/treecache.xml"
-"\" />\n"
+" <cache:jboss-cache-provider configuration=\"META-INF/cache/treecache.xml\" />\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:cache=\"http://jboss.com/products/seam/cache\">\n"
+" <cache:jboss-cache-provider configuration=\"META-INF/cache/treecache.xml\" />\n"
+"</components>]]>"
#. Tag: para
#: Cache.xml:298
@@ -364,8 +287,7 @@
"\n"
" @Unwrap\n"
" public Set<String> getUsers() throws CacheException {\n"
-" Set<String> userList = (Set<String>) cacheProvider.get(\"chatroom\", "
-"\"userList\");\n"
+" Set<String> userList = (Set<String>) cacheProvider.get(\"chatroom\", \"userList\");\n"
" if (userList==null) {\n"
" userList = new HashSet<String>();\n"
" cacheProvider.put(\"chatroom\", \"userList\", userList);\n"
@@ -374,13 +296,27 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"chatroomUsers\")\n"
+"@Scope(ScopeType.STATELESS)\n"
+"public class ChatroomUsers\n"
+"{\n"
+" @In CacheProvider cacheProvider;\n"
+"\n"
+" @Unwrap\n"
+" public Set<String> getUsers() throws CacheException {\n"
+" Set<String> userList = (Set<String>) cacheProvider.get(\"chatroom\", \"userList\");\n"
+" if (userList==null) {\n"
+" userList = new HashSet<String>();\n"
+" cacheProvider.put(\"chatroom\", \"userList\", userList);\n"
+" }\n"
+" return userList;\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Cache.xml:302
#, no-c-format
-msgid ""
-"If you want to have multiple cache configurations in your application, use "
-"<literal>components.xml</literal> to configure multiple cache providers:"
+msgid "If you want to have multiple cache configurations in your application, use <literal>components.xml</literal> to configure multiple cache providers:"
msgstr ""
#. Tag: programlisting
@@ -389,12 +325,15 @@
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
" xmlns:cache=\"http://jboss.com/products/seam/cache\">\n"
-" <cache:jboss-cache-provider name=\"myCache\" configuration=\"myown/cache."
-"xml\"/>\n"
-" <cache:jboss-cache-provider name=\"myOtherCache\" configuration=\"myother/"
-"cache.xml\"/>\n"
+" <cache:jboss-cache-provider name=\"myCache\" configuration=\"myown/cache.xml\"/>\n"
+" <cache:jboss-cache-provider name=\"myOtherCache\" configuration=\"myother/cache.xml\"/>\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:cache=\"http://jboss.com/products/seam/cache\">\n"
+" <cache:jboss-cache-provider name=\"myCache\" configuration=\"myown/cache.xml\"/>\n"
+" <cache:jboss-cache-provider name=\"myOtherCache\" configuration=\"myother/cache.xml\"/>\n"
+"</components>]]>"
#. Tag: title
#: Cache.xml:313
@@ -405,30 +344,20 @@
#. Tag: para
#: Cache.xml:315
#, no-c-format
-msgid ""
-"The most interesting use of caching in Seam is the <literal><s:cache></"
-"literal> tag, Seam's solution to the problem of page fragment caching in "
-"JSF. <literal><s:cache></literal> uses <literal>pojoCache</literal> "
-"internally, so you need to follow the steps listed above before you can use "
-"it. (Put the jars in the EAR, wade through the scary configuration options, "
-"etc.)"
+msgid "The most interesting use of caching in Seam is the <literal><s:cache></literal> tag, Seam's solution to the problem of page fragment caching in JSF. <literal><s:cache></literal> uses <literal>pojoCache</literal> internally, so you need to follow the steps listed above before you can use it. (Put the jars in the EAR, wade through the scary configuration options, etc.)"
msgstr ""
#. Tag: para
#: Cache.xml:324
#, no-c-format
-msgid ""
-"<literal><s:cache></literal> is used for caching some rendered content "
-"which changes rarely. For example, the welcome page of our blog displays the "
-"recent blog entries:"
+msgid "<literal><s:cache></literal> is used for caching some rendered content which changes rarely. For example, the welcome page of our blog displays the recent blog entries:"
msgstr ""
#. Tag: programlisting
#: Cache.xml:330
#, no-c-format
msgid ""
-"<![CDATA[<s:cache key=\"recentEntries-#{blog.id}\" region="
-"\"welcomePageFragments\">\n"
+"<![CDATA[<s:cache key=\"recentEntries-#{blog.id}\" region=\"welcomePageFragments\">\n"
" <h:dataTable value=\"#{blog.recentEntries}\" var=\"blogEntry\">\n"
" <h:column>\n"
" <h3>#{blogEntry.title}</h3>\n"
@@ -439,27 +368,27 @@
" </h:dataTable>\n"
"</s:cache>]]>"
msgstr ""
+"<![CDATA[<s:cache key=\"recentEntries-#{blog.id}\" region=\"welcomePageFragments\">\n"
+" <h:dataTable value=\"#{blog.recentEntries}\" var=\"blogEntry\">\n"
+" <h:column>\n"
+" <h3>#{blogEntry.title}</h3>\n"
+" <div>\n"
+" <s:formattedText value=\"#{blogEntry.body}\"/>\n"
+" </div>\n"
+" </h:column>\n"
+" </h:dataTable>\n"
+"</s:cache>]]>"
#. Tag: para
#: Cache.xml:332
#, no-c-format
-msgid ""
-"The <literal>key</literal> let's you have multiple cached versions of each "
-"page fragment. In this case, there is one cached version per blog. The "
-"<literal>region</literal> determines the cache or region node that all "
-"version will be stored in. Different nodes may have different expiry "
-"policies. (That's the stuff you set up using the aforementioned scary "
-"configuration options.)"
+msgid "The <literal>key</literal> let's you have multiple cached versions of each page fragment. In this case, there is one cached version per blog. The <literal>region</literal> determines the cache or region node that all version will be stored in. Different nodes may have different expiry policies. (That's the stuff you set up using the aforementioned scary configuration options.)"
msgstr ""
#. Tag: para
#: Cache.xml:341
#, no-c-format
-msgid ""
-"Of course, the big problem with <literal><s:cache></literal> is that "
-"it is too stupid to know when the underlying data changes (for example, when "
-"the blogger posts a new entry). So you need to evict the cached fragment "
-"manually:"
+msgid "Of course, the big problem with <literal><s:cache></literal> is that it is too stupid to know when the underlying data changes (for example, when the blogger posts a new entry). So you need to evict the cached fragment manually:"
msgstr ""
#. Tag: programlisting
@@ -469,15 +398,18 @@
"<![CDATA[public void post() {\n"
" ...\n"
" entityManager.persist(blogEntry);\n"
-" cacheProvider.remove(\"welcomePageFragments\", \"recentEntries-\" + blog."
-"getId() );\n"
+" cacheProvider.remove(\"welcomePageFragments\", \"recentEntries-\" + blog.getId() );\n"
"}]]>"
msgstr ""
+"<![CDATA[public void post() {\n"
+" ...\n"
+" entityManager.persist(blogEntry);\n"
+" cacheProvider.remove(\"welcomePageFragments\", \"recentEntries-\" + blog.getId() );\n"
+"}]]>"
#. Tag: para
#: Cache.xml:350
#, no-c-format
-msgid ""
-"Alternatively, if it is not critical that changes are immediately visible to "
-"the user, you could set a short expiry time on the cache node."
+msgid "Alternatively, if it is not critical that changes are immediately visible to the user, you could set a short expiry time on the cache node."
msgstr ""
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po 2008-12-25 14:16:54 UTC (rev 9841)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po 2008-12-27 02:11:25 UTC (rev 9842)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:38+0000\n"
-"PO-Revision-Date: 2008-12-17 21:46+0100\n"
+"PO-Revision-Date: 2008-12-27 03:08+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -25,17 +25,19 @@
msgid "Introduction"
msgstr "Introduzione"
+# mismatch = irregolarità ??? dal contesto sembrerebbe vada bene.
+# querying mismatch = ?
#. Tag: para
#: Hsearch.xml:10
#, no-c-format
msgid "Full text search engines like Apache Lucene™ are a very powerful technology that bring full text and efficient queries to applications. Hibernate Search, which uses Apache Lucene under the covers, indexes your domain model with the addition of a few annotations, takes care of the database / index synchronization and returns regular managed objects that are matched by full text queries. Keep in mind, thought, that there are mismatches that arise when dealing with an object domain model over a text index (keeping the index up to date, mismatch between the index structure and the domain model, and querying mismatch). But the benefits of speed and efficiency far outweigh these limitations."
-msgstr ""
+msgstr "Motori di ricerca full text come Apache Lucene™ sono un potentissima tecnologia che apporta alle applicazioni query full text ed efficienti. Hibernate Search, che utilizza Apache Lucene al suo interno, indicizza il modello di dominio con l'aggiunta di alcune annotazioni, si prende cura del database, della sincronizzazione degli indici e restituisce oggetti regolari gestiti che corrispondono alle query full text. Tuttavia si tenga presente che ci sono delle irregolarità quando si ha a che fare con un modello di dominio a oggetti sopra ad un indice di testo (mantenere l'indice aggiornato, irregolarità tra la struttura dell'indice ed il modello di dominio, e irregolarità di query). Ma i benefici di velocità ed efficienza superano di gran lunga queste limitazioni."
#. Tag: para
#: Hsearch.xml:21
#, no-c-format
msgid "Hibernate Search has been designed to integrates nicely and as naturally as possible with JPA and Hibernate. As a natural extension, JBoss Seam provides an Hibernate Search integration."
-msgstr ""
+msgstr "Hibernate Search è stato progettato per integrarsi nel modo pià naturale possibile con JPA ed Hibernate. Come naturale estensione, JBoss Seam fornisce l'integrazione con Hibernate Search."
#. Tag: para
#: Hsearch.xml:25
@@ -53,13 +55,13 @@
#: Hsearch.xml:35
#, no-c-format
msgid "Hibernate Search is configured either in the <filename>META-INF/persistence.xml</filename> or <filename>hibernate.cfg.xml</filename> file."
-msgstr ""
+msgstr "Hibernate Search è configurato in uno dei file <filename>META-INF/persistence.xml</filename> o <filename>hibernate.cfg.xml</filename>."
#. Tag: para
#: Hsearch.xml:39
#, no-c-format
msgid "Hibernate Search configuration has sensible defaults for most configuration parameters. Here is a minimal persistence unit configuration to get started."
-msgstr ""
+msgstr "La configurazione di Hibernate Search ha dei valori di default impostati per la maggior parte dei parametri di configurazione. Ecco qua una configurazione minimale di persistence unit per poter iniziare."
#. Tag: programlisting
#: Hsearch.xml:43
15 years, 12 months
- 1
- 0
Seam SVN: r9841 - trunk/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2008-12-25 09:16:54 -0500 (Thu, 25 Dec 2008)
New Revision: 9841
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Drools.po
trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po
trunk/doc/Seam_Reference_Guide/it-IT/Validation.po
trunk/doc/Seam_Reference_Guide/it-IT/Xml.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Drools.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Drools.po 2008-12-24 17:57:31 UTC (rev 9840)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Drools.po 2008-12-25 14:16:54 UTC (rev 9841)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:38+0000\n"
-"PO-Revision-Date: 2008-12-16 12:44+0100\n"
+"PO-Revision-Date: 2008-12-25 15:04+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -157,7 +157,7 @@
#: Drools.xml:67
#, no-c-format
msgid "Notice that we gave the <literal>policyPricingWorkingMemory</literal> a reference back to our rule base via the <literal>ruleBase</literal> configuration property."
-msgstr "Notare che abbiamo dato a <literal>policyPricingWorkingMemory</literal> un riferimento alla base di regole tramite la proprietà di configurazione <literal>ruleBase</literal>."
+msgstr "Notare che è stato dato a <literal>policyPricingWorkingMemory</literal> un riferimento alla base di regole tramite la proprietà di configurazione <literal>ruleBase</literal>."
#. Tag: title
#: Drools.xml:76
@@ -169,7 +169,7 @@
#: Drools.xml:78
#, no-c-format
msgid "We can now inject our <literal>WorkingMemory</literal> into any Seam component, assert facts, and fire rules:"
-msgstr "Ora possiamo iniettare la <literal>WorkingMemory</literal> in un qualsiasi componente di Seam, asserire i fatti e lanciare le regole:"
+msgstr "Ora è possibile iniettare la <literal>WorkingMemory</literal> in un qualsiasi componente di Seam, asserire i fatti e lanciare le regole:"
#. Tag: programlisting
#: Drools.xml:83
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-24 17:57:31 UTC (rev 9840)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-25 14:16:54 UTC (rev 9841)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:38+0000\n"
-"PO-Revision-Date: 2008-12-16 11:18+0100\n"
+"PO-Revision-Date: 2008-12-25 15:16+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -53,7 +53,7 @@
#: Jbpm.xml:51
#, no-c-format
msgid "You don't have to know jDPL to use Seam. If you're perfectly happy defining pageflow using JSF or Seam navigation rules, and if your application is more data-driven that process-driven, you probably don't need jBPM. But we're finding that thinking of user interaction in terms of a well-defined graphical representation is helping us build more robust applications."
-msgstr "Non serve che tu conosca jPDL per usare Seam. Se ti trovi bene nel definire un pageflow con JSF o con le regole di navigazione di Seam, e se l'applicazione è guida più dai dati che dal processo, probabilmente non ti serve usare jBPM. Ma noi pensiamo che strutturare l'interazione dell'utente in termini di rappresentazione grafical ben definita aiuti a costruire applicazioni più robuste."
+msgstr "Non serve conoscere jPDL per usare Seam. Se ci si trova bene nel definire un pageflow con JSF o con le regole di navigazione di Seam, e se l'applicazione è guida più dai dati che dal processo, probabilmente non serve usare jBPM. Ma noi pensiamo che strutturare l'interazione dell'utente in termini di rappresentazione grafical ben definita aiuti a costruire applicazioni più robuste."
#. Tag: title
#: Jbpm.xml:60
@@ -473,7 +473,7 @@
#: Jbpm.xml:287
#, no-c-format
msgid "We can also explicitly tell Seam where to find our pageflow definition. We specify this in <literal>components.xml</literal>:"
-msgstr "Possiamo anche comunicare esplicitamente a Seam dove trovare le definizioni dei pageflow. Questo viene specificato dentro <literal>components.xml</literal>:"
+msgstr "Si può anche comunicare esplicitamente a Seam dove trovare le definizioni dei pageflow. Questo viene specificato dentro <literal>components.xml</literal>:"
#. Tag: programlisting
#: Jbpm.xml:292
@@ -501,7 +501,7 @@
#: Jbpm.xml:299
#, no-c-format
msgid "We \"start\" a jPDL-based pageflow by specifying the name of the process definition using a <literal>@Begin</literal>, <literal>@BeginTask</literal> or <literal>@StartTask</literal> annotation:"
-msgstr ""
+msgstr "Si \"inizia\" un pageflow basato su jPDLspecificando il nome della definizione del processo usando un'annotazione <literal>@Begin</literal>, <literal>@BeginTask</literal> oppure <literal>@StartTask</literal>:"
#. Tag: programlisting
#: Jbpm.xml:306
@@ -517,7 +517,7 @@
#: Jbpm.xml:308
#, no-c-format
msgid "Alternatively we can start a pageflow using pages.xml:"
-msgstr "In alternativa possiamo iniziare un pageflow usando pages.xml:"
+msgstr "In alternativa si può iniziare un pageflow usando pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:310
@@ -535,13 +535,13 @@
#: Jbpm.xml:312
#, no-c-format
msgid "If we are beginning the pageflow during the <literal>RENDER_RESPONSE</literal> phase—during a <literal>@Factory</literal> or <literal>@Create</literal> method, for example—we consider ourselves to be already at the page being rendered, and use a <literal><start-page></literal> node as the first node in the pageflow, as in the example above."
-msgstr ""
+msgstr "Se il pageflow viene iniziato durante la fase <literal>RENDER_RESPONSE</literal>—durante un metodo <literal>@Factory</literal> o <literal>@Create</literal>, per esempio—si presume di essere già nella pagina da generare, e si usa un nodo <literal><start-page></literal> come primo nodo nel pageflow, come nell'esempio sopra."
#. Tag: para
#: Jbpm.xml:320
#, no-c-format
msgid "But if the pageflow is begun as the result of an action listener invocation, the outcome of the action listener determines which is the first page to be rendered. In this case, we use a <literal><start-state></literal> as the first node in the pageflow, and declare a transition for each possible outcome:"
-msgstr ""
+msgstr "Ma se il pageflow viene iniziato come risultato di un'invocazione di un action listener, l'esito dell'action listener determina quale è la prima pagina da generare. In questo caso si usa un <literal><start-state></literal> come primo nodo del pageflow, e si dichiara una transizione per ogni possibile esito:"
#. Tag: programlisting
#: Jbpm.xml:328
@@ -772,7 +772,7 @@
#: Jbpm.xml:428
#, no-c-format
msgid "Optionally, we can end a task, specify a jBPM <literal>transition</literal> name. In this case, Seam will signal the end of the current task in the overarching business process."
-msgstr "Opzionalmente possiamo terminare un task specificando un nome alla <literal>transition</literal> jBPM. In questo modo Seam segnalerà la fine del task corrente al processo di business sottostante."
+msgstr "Opzionalmente è possibile terminare un task specificando un nome alla <literal>transition</literal> jBPM. In questo modo Seam segnalerà la fine del task corrente al processo di business sottostante."
#. Tag: programlisting
#: Jbpm.xml:434
@@ -966,7 +966,7 @@
#: Jbpm.xml:549
#, no-c-format
msgid "To initiate a business process instance, we use the <literal>@CreateProcess</literal> annotation:"
-msgstr "Per iniziare un'istanza di processo di business, usiamo l'annotazione <literal>@CreateProcess</literal>:"
+msgstr "Per iniziare un'istanza di processo di business, si usa l'annotazione <literal>@CreateProcess</literal>:"
#. Tag: programlisting
#: Jbpm.xml:554
@@ -982,7 +982,7 @@
#: Jbpm.xml:556
#, no-c-format
msgid "Alternatively we can initiate a business process using pages.xml:"
-msgstr "In alternativa possiamo iniziare un processo di business usando pages.xml:"
+msgstr "In alternativa è possibile iniziare un processo di business usando pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:558
@@ -1006,7 +1006,7 @@
#: Jbpm.xml:565
#, no-c-format
msgid "When a process reaches a task node, task instances are created. These must be assigned to users or user groups. We can either hardcode our actor ids, or delegate to a Seam component:"
-msgstr "Quando un processo raggiunge un task node, vengono create istante di compiti. Queste devono essere assegnate a utenti o gruppi di utenti. Possiamo codificare gli id degli attori (actor id) o delegare ad un componente Seam:"
+msgstr "Quando un processo raggiunge un task node, vengono create istante di compiti. Queste devono essere assegnate a utenti o gruppi di utenti. Si può codificare gli id degli attori (actor id) o delegare ad un componente Seam:"
#. Tag: programlisting
#: Jbpm.xml:571
@@ -1025,7 +1025,7 @@
#: Jbpm.xml:573
#, no-c-format
msgid "In this case, we have simply assigned the task to the current user. We can also assign tasks to a pool:"
-msgstr "In questo caso abbiamo semplicemente assegnato il task all'utente corrente. Possiamo anche assegnare compiti ad un pool (gruppo):"
+msgstr "In questo caso si è semplicemente assegnato il task all'utente corrente. Possiamo anche assegnare compiti ad un pool (gruppo):"
#. Tag: programlisting
#: Jbpm.xml:578
@@ -1156,7 +1156,7 @@
#: Jbpm.xml:624
#, no-c-format
msgid "Alternatively we can begin work on a task using pages.xml:"
-msgstr "In alternativa possiamo iniziare a lavorare su un task usando pages.xml:"
+msgstr "In alternativa si può iniziare a lavorare su un task usando pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:626
@@ -1180,7 +1180,7 @@
#: Jbpm.xml:635
#, no-c-format
msgid "If we end the conversation using <literal>@EndTask</literal>, Seam will signal the completion of the task:"
-msgstr "Se terminiamo un conversazione usando <literal>@EndTask</literal>, Seam segnalerà il completamento del task:"
+msgstr "Se si termina una conversazione usando <literal>@EndTask</literal>, Seam segnalerà il completamento del task:"
#. Tag: programlisting
#: Jbpm.xml:640
@@ -1196,7 +1196,7 @@
#: Jbpm.xml:642
#, no-c-format
msgid "Alternatively we can use pages.xml:"
-msgstr "In alternativa usiamo pages.xml:"
+msgstr "In alternativa si usa pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:644
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-24 17:57:31 UTC (rev 9840)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-25 14:16:54 UTC (rev 9841)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-12-13 17:58+0000\n"
-"PO-Revision-Date: 2008-12-21 14:58+0100\n"
+"PO-Revision-Date: 2008-12-25 14:54+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -164,7 +164,7 @@
#: Tutorial.xml:136
#, no-c-format
msgid "The example is implemented with two Facelets templates, one entity bean and one stateless session bean. Let's take a look at the code, starting from the \"bottom\"."
-msgstr "Questo esempio è implementato con due template Facelets, un entity bean e un session bean stateless. Guardiamo ora il codice, partendo dal \"basso\"."
+msgstr "Questo esempio è implementato con due template Facelets, un entity bean e un session bean stateless. Si guardi ora il codice, partendo dal \"basso\"."
#. Tag: title
#: Tutorial.xml:141
@@ -5223,7 +5223,7 @@
#: Tutorial.xml:1907
#, no-c-format
msgid "If the blog entry is not found in the database, the <literal>EntryNotFoundException</literal> exception is thrown. We want this exception to result in a 404 error, not a 505, so we annotate the exception class:"
-msgstr "Se l'entry del blog non viene trovata nel database, viene lanciata l'eccezione <literal>EntryNotFoundException</literal>. Vogliamo che quest'eccezione venga evidenziata come errore 404, non 505, e quindi annotiamo la classe dell'eccezione:"
+msgstr "Se l'entry del blog non viene trovata nel database, viene lanciata l'eccezione <literal>EntryNotFoundException</literal>. Si vuole che quest'eccezione venga evidenziata come errore 404, non 505, e quindi viene annotata la classe dell'eccezione:"
#. Tag: programlisting
#: Tutorial.xml:1911
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Validation.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Validation.po 2008-12-24 17:57:31 UTC (rev 9840)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Validation.po 2008-12-25 14:16:54 UTC (rev 9841)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:39+0000\n"
-"PO-Revision-Date: 2008-12-13 20:44+0100\n"
+"PO-Revision-Date: 2008-12-25 14:52+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -81,7 +81,7 @@
#: Validation.xml:17
#, no-c-format
msgid "Let's start by defining our constraints, on our <literal>Location</literal> class:"
-msgstr "Iniziamo definendo i vincoli sulla classe <literal>Location</literal>: "
+msgstr "Si cominci col definire i vincoli sulla classe <literal>Location</literal>: "
#. Tag: programlisting
#: Validation.xml:22
@@ -123,7 +123,7 @@
#: Validation.xml:24
#, no-c-format
msgid "Well, that's a decent first cut, but in practice it might be more elegant to use custom constraints instead of the ones built into Hibernate Validator:"
-msgstr "Bene, questo è una buona riduzione, ma in pratica è possibile essere più elegante utilizzando dei vincoli personalizzati invece di quelli interni a Hibernate Validator:"
+msgstr "Bene, questa è una prima buona riduzione, ma in pratica è possibile essere più eleganti utilizzando dei vincoli personalizzati invece di quelli interni a Hibernate Validator:"
#. Tag: programlisting
#: Validation.xml:30
@@ -163,7 +163,7 @@
#: Validation.xml:32
#, no-c-format
msgid "Whichever route we take, we no longer need to specify the type of validation to be used in the JSF page. Instead, we can use <literal><s:validate></literal> to validate against the constraint defined on the model object."
-msgstr "Qualsiasi strada prendiamo non dobbiamo più specificare il tipo di validazione da usare nelle pagine JSF. Invece possiamo usare <literal><s:validate></literal> per validare il vincolo definito nell'oggetto modello."
+msgstr "Qualsiasi strada si prenda non occorre più specificare il tipo di validazione da usare nelle pagine JSF. Invece è possibile usare <literal><s:validate></literal> per validare il vincolo definito nell'oggetto modello."
#. Tag: programlisting
#: Validation.xml:39
@@ -317,13 +317,13 @@
#: Validation.xml:85
#, no-c-format
msgid "What we would really like to do, though, is display the message next to the field with the error (this is possible in plain JSF), highlight the field and label (this is not possible) and, for good measure, display some image next to the field (also not possible). We also want to display a little colored asterisk next to the label for each required form field. Using this approach, the identifying label is not necessary."
-msgstr "Ciò che vorremmo fare, tuttavia, è mostrare il messaggio vicino al campo con l'errore (questo è possibile nel semplice JSF), ed evidenziare il campo e l'etichetta (questo non è possibile) ed, eventualmente, mostrare un'immagine vicino al campo (anche questo non è possibile). Vogliamo anche mostrare un piccolo asterisco colorato vicino all'etichetta per ciascun campo richiesto. Utilizzando quest'approccio non è più necessario identificare l'etichetta."
+msgstr "Ciò che si vuole fare, tuttavia, è mostrare il messaggio vicino al campo con l'errore (questo è possibile nel semplice JSF), ed evidenziare il campo e l'etichetta (questo non è possibile) ed, eventualmente, mostrare un'immagine vicino al campo (anche questo non è possibile). Si vuole anche mostrare un piccolo asterisco colorato vicino all'etichetta per ciascun campo richiesto. Utilizzando quest'approccio non è più necessario identificare l'etichetta."
#. Tag: para
#: Validation.xml:95
#, no-c-format
msgid "That's quite a lot of functionality we need for each field of our form. We wouldn't want to have to specify higlighting and the layout of the image, message and input field for every field on the form. So, instead, we'll specify the common layout in a facelets template:"
-msgstr "Abbiamo quindi bisogno di parecchia funzionalità per ogni singolo campo della form. Ma non vogliamo essere costretti a specificare per ogni campo della form come evidenziare, come disporre l'immagine, quale messaggio scrivere e quale è il campo d'input da associare."
+msgstr "Si ha quindi bisogno di parecchia funzionalità per ogni singolo campo della form. Ma non si vuole essere costretti a specificare per ogni campo della form come evidenziare, come disporre l'immagine, quale messaggio scrivere e quale è il campo d'input da associare."
#. Tag: programlisting
#: Validation.xml:103
@@ -385,7 +385,7 @@
#: Validation.xml:105
#, no-c-format
msgid "We can include this template for each of our form fields using <literal><s:decorate></literal>."
-msgstr "Possiamo includere questo template per ciascuna campo della form utilizzando <literal><s:decorate></literal>."
+msgstr "Si può includere questo template per ciascuna campo della form utilizzando <literal><s:decorate></literal>."
#. Tag: programlisting
#: Validation.xml:110
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Xml.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Xml.po 2008-12-24 17:57:31 UTC (rev 9840)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Xml.po 2008-12-25 14:16:54 UTC (rev 9841)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-12-04 00:59+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-25 15:03+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,61 +17,36 @@
#: Xml.xml:6
#, no-c-format
msgid "Configuring Seam components"
-msgstr ""
+msgstr "Configurare i componenti Seam"
#. Tag: para
#: Xml.xml:8
#, no-c-format
-msgid ""
-"The philosophy of minimizing XML-based configuration is extremely strong in "
-"Seam. Nevertheless, there are various reasons why we might want to configure "
-"a Seam component using XML: to isolate deployment-specific information from "
-"the Java code, to enable the creation of re-usable frameworks, to configure "
-"Seam's built-in functionality, etc. Seam provides two basic approaches to "
-"configuring components: configuration via property settings in a properties "
-"file or in <literal>web.xml</literal>, and configuration via "
-"<literal>components.xml</literal>."
-msgstr ""
+msgid "The philosophy of minimizing XML-based configuration is extremely strong in Seam. Nevertheless, there are various reasons why we might want to configure a Seam component using XML: to isolate deployment-specific information from the Java code, to enable the creation of re-usable frameworks, to configure Seam's built-in functionality, etc. Seam provides two basic approaches to configuring components: configuration via property settings in a properties file or in <literal>web.xml</literal>, and configuration via <literal>components.xml</literal>."
+msgstr "La filosofia di minimizzare la configurazione basata su XML è estremamente forte in Seam. Tuttavia ci sono varie ragioni per voler configurare i componente Seam tramite XML: per isolare le informazioni specifiche del deploy dal codice Java, per abilitare la creazione di framework riutilizzabili, per configurare le funzionalità predefinite di Seam, ecc. Seam fornisce due approcci base per configurare i componenti: configurazione tramire impostazioni di proprietà in un file di proprietà o in <literal>web.xml</literal>, e configurazione tramite <literal>components.xml</literal>."
#. Tag: title
#: Xml.xml:18
#, no-c-format
msgid "Configuring components via property settings"
-msgstr ""
+msgstr "Configurare i componenti tramire impostazioni di proprietà"
#. Tag: para
#: Xml.xml:19
#, no-c-format
-msgid ""
-"Seam components may be provided with configuration properties either via "
-"servlet context parameters, or via a properties file named <literal>seam."
-"properties</literal> in the root of the classpath."
+msgid "Seam components may be provided with configuration properties either via servlet context parameters, or via a properties file named <literal>seam.properties</literal> in the root of the classpath."
msgstr ""
#. Tag: para
#: Xml.xml:23
#, no-c-format
-msgid ""
-"The configurable Seam component must expose JavaBeans-style property setter "
-"methods for the configurable attributes. If a Seam component named "
-"<literal>com.jboss.myapp.settings</literal> has a setter method named "
-"<literal>setLocale()</literal>, we can provide a property named <literal>com."
-"jboss.myapp.settings.locale</literal> in the <literal>seam.properties</"
-"literal> file or as a servlet context parameter, and Seam will set the value "
-"of the <literal>locale</literal> attribute whenever it instantiates the "
-"component."
+msgid "The configurable Seam component must expose JavaBeans-style property setter methods for the configurable attributes. If a Seam component named <literal>com.jboss.myapp.settings</literal> has a setter method named <literal>setLocale()</literal>, we can provide a property named <literal>com.jboss.myapp.settings.locale</literal> in the <literal>seam.properties</literal> file or as a servlet context parameter, and Seam will set the value of the <literal>locale</literal> attribute whenever it instantiates the component."
msgstr ""
#. Tag: para
#: Xml.xml:31
#, no-c-format
-msgid ""
-"The same mechanism is used to configure Seam itself. For example, to set the "
-"conversation timeout, we provide a value for <literal>org.jboss.seam.core."
-"manager.conversationTimeout</literal> in <literal>web.xml</literal> or "
-"<literal>seam.properties</literal>. (There is a built-in Seam component "
-"named <literal>org.jboss.seam.core.manager</literal> with a setter method "
-"named <literal>setConversationTimeout()</literal>.)"
+msgid "The same mechanism is used to configure Seam itself. For example, to set the conversation timeout, we provide a value for <literal>org.jboss.seam.core.manager.conversationTimeout</literal> in <literal>web.xml</literal> or <literal>seam.properties</literal>. (There is a built-in Seam component named <literal>org.jboss.seam.core.manager</literal> with a setter method named <literal>setConversationTimeout()</literal>.)"
msgstr ""
#. Tag: title
@@ -83,53 +58,37 @@
#. Tag: para
#: Xml.xml:43
#, no-c-format
-msgid ""
-"The <literal>components.xml</literal> file is a bit more powerful than "
-"property settings. It lets you:"
+msgid "The <literal>components.xml</literal> file is a bit more powerful than property settings. It lets you:"
msgstr ""
#. Tag: para
#: Xml.xml:50
#, no-c-format
-msgid ""
-"Configure components that have been installed automatically—including "
-"both built-in components, and application components that have been "
-"annotated with the <literal>@Name</literal> annotation and picked up by "
-"Seam's deployment scanner."
+msgid "Configure components that have been installed automatically—including both built-in components, and application components that have been annotated with the <literal>@Name</literal> annotation and picked up by Seam's deployment scanner."
msgstr ""
#. Tag: para
#: Xml.xml:55
#, no-c-format
-msgid ""
-"Install classes with no <literal>@Name</literal> annotation as Seam "
-"components—this is most useful for certain kinds of infrastructural "
-"components which can be installed multiple times different names (for "
-"example Seam-managed persistence contexts)."
+msgid "Install classes with no <literal>@Name</literal> annotation as Seam components—this is most useful for certain kinds of infrastructural components which can be installed multiple times different names (for example Seam-managed persistence contexts)."
msgstr ""
#. Tag: para
#: Xml.xml:60
#, no-c-format
-msgid ""
-"Install components that <emphasis>do</emphasis> have a <literal>@Name</"
-"literal> annotation but are not installed by default because of an "
-"<literal>@Install</literal> annotation that indicates the component should "
-"not be installed."
+msgid "Install components that <emphasis>do</emphasis> have a <literal>@Name</literal> annotation but are not installed by default because of an <literal>@Install</literal> annotation that indicates the component should not be installed."
msgstr ""
#. Tag: para
#: Xml.xml:65
#, no-c-format
msgid "Override the scope of a component."
-msgstr ""
+msgstr "Override dello scope di un componente"
#. Tag: para
#: Xml.xml:69
#, no-c-format
-msgid ""
-"A <literal>components.xml</literal> file may appear in one of three "
-"different places:"
+msgid "A <literal>components.xml</literal> file may appear in one of three different places:"
msgstr ""
#. Tag: para
@@ -147,30 +106,19 @@
#. Tag: para
#: Xml.xml:81
#, no-c-format
-msgid ""
-"Any directory of a <literal>jar</literal> that contains classes with an "
-"<literal>@Name</literal> annotation."
+msgid "Any directory of a <literal>jar</literal> that contains classes with an <literal>@Name</literal> annotation."
msgstr ""
#. Tag: para
#: Xml.xml:88
#, no-c-format
-msgid ""
-"Usually, Seam components are installed when the deployment scanner discovers "
-"a class with a <literal>@Name</literal> annotation sitting in an archive "
-"with a <literal>seam.properties</literal> file or a <literal>META-INF/"
-"components.xml</literal> file. (Unless the component has an "
-"<literal>@Install</literal> annotation indicating it should not be installed "
-"by default.) The <literal>components.xml</literal> file lets us handle "
-"special cases where we need to override the annotations."
+msgid "Usually, Seam components are installed when the deployment scanner discovers a class with a <literal>@Name</literal> annotation sitting in an archive with a <literal>seam.properties</literal> file or a <literal>META-INF/components.xml</literal> file. (Unless the component has an <literal>@Install</literal> annotation indicating it should not be installed by default.) The <literal>components.xml</literal> file lets us handle special cases where we need to override the annotations."
msgstr ""
#. Tag: para
#: Xml.xml:97
#, no-c-format
-msgid ""
-"For example, the following <literal>components.xml</literal> file installs "
-"jBPM:"
+msgid "For example, the following <literal>components.xml</literal> file installs jBPM:"
msgstr ""
#. Tag: programlisting
@@ -183,6 +131,11 @@
" <bpm:jbpm/>\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xmlns:bpm=\"http://jboss.com/products/seam/bpm\">\n"
+" <bpm:jbpm/>\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:103
@@ -198,13 +151,14 @@
" <component class=\"org.jboss.seam.bpm.Jbpm\"/>\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+" <component class=\"org.jboss.seam.bpm.Jbpm\"/>\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:109
#, no-c-format
-msgid ""
-"This one installs and configures two different Seam-managed persistence "
-"contexts:"
+msgid "This one installs and configures two different Seam-managed persistence contexts:"
msgstr ""
#. Tag: programlisting
@@ -212,19 +166,26 @@
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
-" xmlns:persistence=\"http://jboss.com/products/seam/persistence"
-"\"\n"
+" xmlns:persistence=\"http://jboss.com/products/seam/persistence\"\n"
"\n"
" <persistence:managed-persistence-context name=\"customerDatabase\"\n"
-" persistence-unit-jndi-name=\"java:/"
-"customerEntityManagerFactory\"/>\n"
+" persistence-unit-jndi-name=\"java:/customerEntityManagerFactory\"/>\n"
" \n"
" <persistence:managed-persistence-context name=\"accountingDatabase\"\n"
-" persistence-unit-jndi-name=\"java:/"
-"accountingEntityManagerFactory\"/> \n"
+" persistence-unit-jndi-name=\"java:/accountingEntityManagerFactory\"/> \n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
+" xmlns:persistence=\"http://jboss.com/products/seam/persistence\"\n"
+"\n"
+" <persistence:managed-persistence-context name=\"customerDatabase\"\n"
+" persistence-unit-jndi-name=\"java:/customerEntityManagerFactory\"/>\n"
+" \n"
+" <persistence:managed-persistence-context name=\"accountingDatabase\"\n"
+" persistence-unit-jndi-name=\"java:/accountingEntityManagerFactory\"/> \n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:115
@@ -238,27 +199,32 @@
msgid ""
"<![CDATA[<components>\n"
" <component name=\"customerDatabase\" \n"
-" class=\"org.jboss.seam.persistence.ManagedPersistenceContext"
-"\">\n"
-" <property name=\"persistenceUnitJndiName\">java:/"
-"customerEntityManagerFactory</property>\n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/customerEntityManagerFactory</property>\n"
" </component>\n"
" \n"
" <component name=\"accountingDatabase\"\n"
-" class=\"org.jboss.seam.persistence.ManagedPersistenceContext"
-"\">\n"
-" <property name=\"persistenceUnitJndiName\">java:/"
-"accountingEntityManagerFactory</property>\n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/accountingEntityManagerFactory</property>\n"
" </component>\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+" <component name=\"customerDatabase\" \n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/customerEntityManagerFactory</property>\n"
+" </component>\n"
+" \n"
+" <component name=\"accountingDatabase\"\n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/accountingEntityManagerFactory</property>\n"
+" </component>\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:121
#, no-c-format
-msgid ""
-"This example creates a session-scoped Seam-managed persistence context (this "
-"is not recommended in practice):"
+msgid "This example creates a session-scoped Seam-managed persistence context (this is not recommended in practice):"
msgstr ""
#. Tag: programlisting
@@ -266,16 +232,22 @@
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
-" xmlns:persistence=\"http://jboss.com/products/seam/persistence"
-"\"\n"
+" xmlns:persistence=\"http://jboss.com/products/seam/persistence\"\n"
"\n"
" <persistence:managed-persistence-context name=\"productDatabase\" \n"
" scope=\"session\"\n"
-" persistence-unit-jndi-name=\"java:/"
-"productEntityManagerFactory\"/> \n"
+" persistence-unit-jndi-name=\"java:/productEntityManagerFactory\"/> \n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
+" xmlns:persistence=\"http://jboss.com/products/seam/persistence\"\n"
+"\n"
+" <persistence:managed-persistence-context name=\"productDatabase\" \n"
+" scope=\"session\"\n"
+" persistence-unit-jndi-name=\"java:/productEntityManagerFactory\"/> \n"
+"\n"
+"</components>]]>"
#. Tag: programlisting
#: Xml.xml:128
@@ -285,23 +257,26 @@
" \n"
" <component name=\"productDatabase\"\n"
" scope=\"session\"\n"
-" class=\"org.jboss.seam.persistence.ManagedPersistenceContext"
-"\">\n"
-" <property name=\"persistenceUnitJndiName\">java:/"
-"productEntityManagerFactory</property>\n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/productEntityManagerFactory</property>\n"
" </component>\n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+" \n"
+" <component name=\"productDatabase\"\n"
+" scope=\"session\"\n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/productEntityManagerFactory</property>\n"
+" </component>\n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:130
#, no-c-format
-msgid ""
-"It is common to use the <literal>auto-create</literal> option for "
-"infrastructural objects like persistence contexts, which saves you from "
-"having to explicitly specify <literal>create=true</literal> when you use the "
-"<literal>@In</literal> annotation."
+msgid "It is common to use the <literal>auto-create</literal> option for infrastructural objects like persistence contexts, which saves you from having to explicitly specify <literal>create=true</literal> when you use the <literal>@In</literal> annotation."
msgstr ""
#. Tag: programlisting
@@ -309,16 +284,22 @@
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
-" xmlns:persistence=\"http://jboss.com/products/seam/persistence"
-"\"\n"
+" xmlns:persistence=\"http://jboss.com/products/seam/persistence\"\n"
"\n"
" <persistence:managed-persistence-context name=\"productDatabase\" \n"
" auto-create=\"true\"\n"
-" persistence-unit-jndi-name=\"java:/"
-"productEntityManagerFactory\"/> \n"
+" persistence-unit-jndi-name=\"java:/productEntityManagerFactory\"/> \n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
+" xmlns:persistence=\"http://jboss.com/products/seam/persistence\"\n"
+"\n"
+" <persistence:managed-persistence-context name=\"productDatabase\" \n"
+" auto-create=\"true\"\n"
+" persistence-unit-jndi-name=\"java:/productEntityManagerFactory\"/> \n"
+"\n"
+"</components>]]>"
#. Tag: programlisting
#: Xml.xml:139
@@ -328,22 +309,26 @@
" \n"
" <component name=\"productDatabase\"\n"
" auto-create=\"true\"\n"
-" class=\"org.jboss.seam.persistence.ManagedPersistenceContext"
-"\">\n"
-" <property name=\"persistenceUnitJndiName\">java:/"
-"productEntityManagerFactory</property>\n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/productEntityManagerFactory</property>\n"
" </component>\n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+" \n"
+" <component name=\"productDatabase\"\n"
+" auto-create=\"true\"\n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/productEntityManagerFactory</property>\n"
+" </component>\n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:141
#, no-c-format
-msgid ""
-"The <literal><factory></literal> declaration lets you specify a value "
-"or method binding expression that will be evaluated to initialize the value "
-"of a context variable when it is first referenced."
+msgid "The <literal><factory></literal> declaration lets you specify a value or method binding expression that will be evaluated to initialize the value of a context variable when it is first referenced."
msgstr ""
#. Tag: programlisting
@@ -352,17 +337,20 @@
msgid ""
"<![CDATA[<components>\n"
"\n"
-" <factory name=\"contact\" method=\"#{contactManager.loadContact}\" scope="
-"\"CONVERSATION\"/>\n"
+" <factory name=\"contact\" method=\"#{contactManager.loadContact}\" scope=\"CONVERSATION\"/>\n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+"\n"
+" <factory name=\"contact\" method=\"#{contactManager.loadContact}\" scope=\"CONVERSATION\"/>\n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:149
#, no-c-format
-msgid ""
-"You can create an \"alias\" (a second name) for a Seam component like so:"
+msgid "You can create an \"alias\" (a second name) for a Seam component like so:"
msgstr ""
#. Tag: programlisting
@@ -375,6 +363,11 @@
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+"\n"
+" <factory name=\"user\" value=\"#{actor}\" scope=\"STATELESS\"/>\n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:155
@@ -388,18 +381,20 @@
msgid ""
"<![CDATA[<components>\n"
"\n"
-" <factory name=\"contact\" value=\"#{contactManager.contact}\" scope="
-"\"STATELESS\"/>\n"
+" <factory name=\"contact\" value=\"#{contactManager.contact}\" scope=\"STATELESS\"/>\n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+"\n"
+" <factory name=\"contact\" value=\"#{contactManager.contact}\" scope=\"STATELESS\"/>\n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:161
#, no-c-format
-msgid ""
-"It is especially common to see the use of <literal>auto-create=\"true\"</"
-"literal> with the <literal><factory></literal> declaration:"
+msgid "It is especially common to see the use of <literal>auto-create=\"true\"</literal> with the <literal><factory></literal> declaration:"
msgstr ""
#. Tag: programlisting
@@ -408,23 +403,20 @@
msgid ""
"<![CDATA[<components>\n"
"\n"
-" <factory name=\"session\" value=\"#{entityManager.delegate}\" scope="
-"\"STATELESS\" auto-create=\"true\"/>\n"
+" <factory name=\"session\" value=\"#{entityManager.delegate}\" scope=\"STATELESS\" auto-create=\"true\"/>\n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+"\n"
+" <factory name=\"session\" value=\"#{entityManager.delegate}\" scope=\"STATELESS\" auto-create=\"true\"/>\n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:168
#, no-c-format
-msgid ""
-"Sometimes we want to reuse the same <literal>components.xml</literal> file "
-"with minor changes during both deployment and testing. Seam lets you place "
-"wildcards of the form <literal>@wildcard@</literal> in the "
-"<literal>components.xml</literal> file which can be replaced either by your "
-"Ant build script (at deployment time) or by providing a file named "
-"<literal>components.properties</literal> in the classpath (at development "
-"time). You'll see this approach used in the Seam examples."
+msgid "Sometimes we want to reuse the same <literal>components.xml</literal> file with minor changes during both deployment and testing. Seam lets you place wildcards of the form <literal>@wildcard@</literal> in the <literal>components.xml</literal> file which can be replaced either by your Ant build script (at deployment time) or by providing a file named <literal>components.properties</literal> in the classpath (at development time). You'll see this approach used in the Seam examples."
msgstr ""
#. Tag: title
@@ -436,15 +428,7 @@
#. Tag: para
#: Xml.xml:180
#, no-c-format
-msgid ""
-"If you have a large number of components that need to be configured in XML, "
-"it makes much more sense to split up the information in <literal>components."
-"xml</literal> into many small files. Seam lets you put configuration for a "
-"class named, for example, <literal>com.helloworld.Hello</literal> in a "
-"resource named <literal>com/helloworld/Hello.component.xml</literal>. (You "
-"might be familiar with this pattern, since it is the same one we use in "
-"Hibernate.) The root element of the file may be either a <literal><"
-"components></literal> or <literal><component></literal> element."
+msgid "If you have a large number of components that need to be configured in XML, it makes much more sense to split up the information in <literal>components.xml</literal> into many small files. Seam lets you put configuration for a class named, for example, <literal>com.helloworld.Hello</literal> in a resource named <literal>com/helloworld/Hello.component.xml</literal>. (You might be familiar with this pattern, since it is the same one we use in Hibernate.) The root element of the file may be either a <literal><components></literal> or <literal><component></literal> element."
msgstr ""
#. Tag: para
@@ -464,13 +448,17 @@
" <factory name=\"message\" value=\"#{hello.message}\"/>\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+" <component class=\"com.helloworld.Hello\" name=\"hello\">\n"
+" <property name=\"name\">#{user.name}</property>\n"
+" </component>\n"
+" <factory name=\"message\" value=\"#{hello.message}\"/>\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:195
#, no-c-format
-msgid ""
-"The second option only lets you define or configure one component, but is "
-"less noisy:"
+msgid "The second option only lets you define or configure one component, but is less noisy:"
msgstr ""
#. Tag: programlisting
@@ -481,22 +469,20 @@
" <property name=\"name\">#{user.name}</property>\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"hello\">\n"
+" <property name=\"name\">#{user.name}</property>\n"
+"</component>]]>"
#. Tag: para
#: Xml.xml:201
#, no-c-format
-msgid ""
-"In the second option, the class name is implied by the file in which the "
-"component definition appears."
+msgid "In the second option, the class name is implied by the file in which the component definition appears."
msgstr ""
#. Tag: para
#: Xml.xml:206
#, no-c-format
-msgid ""
-"Alternatively, you may put configuration for all classes in the <literal>com."
-"helloworld</literal> package in <literal>com/helloworld/components.xml</"
-"literal>."
+msgid "Alternatively, you may put configuration for all classes in the <literal>com.helloworld</literal> package in <literal>com/helloworld/components.xml</literal>."
msgstr ""
#. Tag: title
@@ -508,22 +494,20 @@
#. Tag: para
#: Xml.xml:214
#, no-c-format
-msgid ""
-"Properties of string, primitive or primitive wrapper type may be configured "
-"just as you would expect:"
+msgid "Properties of string, primitive or primitive wrapper type may be configured just as you would expect:"
msgstr ""
#. Tag: programlisting
#: Xml.xml:218
#, no-c-format
msgid "<![CDATA[org.jboss.seam.core.manager.conversationTimeout 60000]]>"
-msgstr ""
+msgstr "<![CDATA[org.jboss.seam.core.manager.conversationTimeout 60000]]>"
#. Tag: programlisting
#: Xml.xml:220
#, no-c-format
msgid "<![CDATA[<core:manager conversation-timeout=\"60000\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<core:manager conversation-timeout=\"60000\"/>]]>"
#. Tag: programlisting
#: Xml.xml:222
@@ -533,6 +517,9 @@
" <property name=\"conversationTimeout\">60000</property>\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"org.jboss.seam.core.manager\">\n"
+" <property name=\"conversationTimeout\">60000</property>\n"
+"</component>]]>"
#. Tag: para
#: Xml.xml:224
@@ -543,10 +530,8 @@
#. Tag: programlisting
#: Xml.xml:228
#, no-c-format
-msgid ""
-"<![CDATA[org.jboss.seam.bpm.jbpm.processDefinitions order.jpdl.xml, return."
-"jpdl.xml, inventory.jpdl.xml]]>"
-msgstr ""
+msgid "<![CDATA[org.jboss.seam.bpm.jbpm.processDefinitions order.jpdl.xml, return.jpdl.xml, inventory.jpdl.xml]]>"
+msgstr "<![CDATA[org.jboss.seam.bpm.jbpm.processDefinitions order.jpdl.xml, return.jpdl.xml, inventory.jpdl.xml]]>"
#. Tag: programlisting
#: Xml.xml:230
@@ -560,6 +545,13 @@
" </bpm:process-definitions>\n"
"</bpm:jbpm>]]>"
msgstr ""
+"<![CDATA[<bpm:jbpm>\n"
+" <bpm:process-definitions>\n"
+" <value>order.jpdl.xml</value>\n"
+" <value>return.jpdl.xml</value>\n"
+" <value>inventory.jpdl.xml</value>\n"
+" </bpm:process-definitions>\n"
+"</bpm:jbpm>]]>"
#. Tag: programlisting
#: Xml.xml:232
@@ -573,13 +565,18 @@
" </property>\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"org.jboss.seam.bpm.jbpm\">\n"
+" <property name=\"processDefinitions\">\n"
+" <value>order.jpdl.xml</value>\n"
+" <value>return.jpdl.xml</value>\n"
+" <value>inventory.jpdl.xml</value>\n"
+" </property>\n"
+"</component>]]>"
#. Tag: para
#: Xml.xml:234
#, no-c-format
-msgid ""
-"Even maps with String-valued keys and string or primitive values are "
-"supported:"
+msgid "Even maps with String-valued keys and string or primitive values are supported:"
msgstr ""
#. Tag: programlisting
@@ -594,24 +591,24 @@
" </property>\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"issueEditor\">\n"
+" <property name=\"issueStatuses\">\n"
+" <key>open</key> <value>open issue</value>\n"
+" <key>resolved</key> <value>issue resolved by developer</value>\n"
+" <key>closed</key> <value>resolution accepted by user</value>\n"
+" </property>\n"
+"</component>]]>"
#. Tag: para
#: Xml.xml:240
#, no-c-format
-msgid ""
-"When configuring multi-valued properties, by default, Seam will preserve the "
-"order in which you place the attributes in <literal>components.xml</literal> "
-"(unless you use a <literal>SortedSet</literal>/<literal>SortedMap</literal> "
-"then Seam will use <literal>TreeMap</literal>/<literal>TreeSet</literal>). "
-"If the property has a concrete type (for example <literal>LinkedList</"
-"literal> Seam will use that type."
+msgid "When configuring multi-valued properties, by default, Seam will preserve the order in which you place the attributes in <literal>components.xml</literal> (unless you use a <literal>SortedSet</literal>/<literal>SortedMap</literal> then Seam will use <literal>TreeMap</literal>/<literal>TreeSet</literal>). If the property has a concrete type (for example <literal>LinkedList</literal> Seam will use that type."
msgstr ""
#. Tag: para
#: Xml.xml:246
#, no-c-format
-msgid ""
-"You can also override the type by specifying a fully qualified class name:"
+msgid "You can also override the type by specifying a fully qualified class name:"
msgstr ""
#. Tag: programlisting
@@ -626,16 +623,18 @@
" </property>\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"issueEditor\">\n"
+" <property name=\"issueStatusOptions\" type=\"java.util.LinkedHashMap\">\n"
+" <key>open</key> <value>open issue</value>\n"
+" <key>resolved</key> <value>issue resolved by developer</value>\n"
+" <key>closed</key> <value>resolution accepted by user</value>\n"
+" </property>\n"
+"</component>]]>"
#. Tag: para
#: Xml.xml:252
#, no-c-format
-msgid ""
-"Finally, you may wire together components using a value-binding expression. "
-"Note that this is quite different to injection using <literal>@In</literal>, "
-"since it happens at component instantiation time instead of invocation time. "
-"It is therefore much more similar to the dependency injection facilities "
-"offered by traditional IoC containers like JSF or Spring."
+msgid "Finally, you may wire together components using a value-binding expression. Note that this is quite different to injection using <literal>@In</literal>, since it happens at component instantiation time instead of invocation time. It is therefore much more similar to the dependency injection facilities offered by traditional IoC containers like JSF or Spring."
msgstr ""
#. Tag: programlisting
@@ -645,6 +644,8 @@
"<![CDATA[<drools:managed-working-memory name=\"policyPricingWorkingMemory\"\n"
" rule-base=\"#{policyPricingRules}\"/>]]>"
msgstr ""
+"<![CDATA[<drools:managed-working-memory name=\"policyPricingWorkingMemory\"\n"
+" rule-base=\"#{policyPricingRules}\"/>]]>"
#. Tag: programlisting
#: Xml.xml:262
@@ -655,14 +656,15 @@
" <property name=\"ruleBase\">#{policyPricingRules}</property>\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"policyPricingWorkingMemory\"\n"
+" class=\"org.jboss.seam.drools.ManagedWorkingMemory\">\n"
+" <property name=\"ruleBase\">#{policyPricingRules}</property>\n"
+"</component>]]>"
#. Tag: para
#: Xml.xml:264
#, no-c-format
-msgid ""
-"Seam also resolves an EL expression string prior to assigning the initial "
-"value to the bean property of the component. So you can inject some "
-"contextual data into your components."
+msgid "Seam also resolves an EL expression string prior to assigning the initial value to the bean property of the component. So you can inject some contextual data into your components."
msgstr ""
#. Tag: programlisting
@@ -670,22 +672,17 @@
#, no-c-format
msgid ""
"<![CDATA[<component name=\"greeter\" class=\"com.example.action.Greeter\">\n"
-" <property name=\"message\">Nice to see you, #{identity.username}!</"
-"property>\n"
+" <property name=\"message\">Nice to see you, #{identity.username}!</property>\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"greeter\" class=\"com.example.action.Greeter\">\n"
+" <property name=\"message\">Nice to see you, #{identity.username}!</property>\n"
+"</component>]]>"
#. Tag: para
#: Xml.xml:271
#, no-c-format
-msgid ""
-"However, there is one important exception. If the type of the property to "
-"which the initial value is being assigned is either a Seam "
-"<literal>ValueExpression</literal> or <literal>MethodExpression</literal>, "
-"then the evaluation of the EL is deferred. Instead, the appropriate "
-"expression wrapper is created and assigned to the property. The message "
-"templates on the Home component from the Seam Application Framework serve as "
-"an example."
+msgid "However, there is one important exception. If the type of the property to which the initial value is being assigned is either a Seam <literal>ValueExpression</literal> or <literal>MethodExpression</literal>, then the evaluation of the EL is deferred. Instead, the appropriate expression wrapper is created and assigned to the property. The message templates on the Home component from the Seam Application Framework serve as an example."
msgstr ""
#. Tag: programlisting
@@ -693,40 +690,29 @@
#, no-c-format
msgid ""
"<![CDATA[<framework:entity-home name=\"myEntityHome\"\n"
-" class=\"com.example.action.MyEntityHome\" entity-class=\"com.example."
-"model.MyEntity\"\n"
-" created-message=\"'#{myEntityHome.instance.name}' has been successfully "
-"added.\"/>]]>"
+" class=\"com.example.action.MyEntityHome\" entity-class=\"com.example.model.MyEntity\"\n"
+" created-message=\"'#{myEntityHome.instance.name}' has been successfully added.\"/>]]>"
msgstr ""
+"<![CDATA[<framework:entity-home name=\"myEntityHome\"\n"
+" class=\"com.example.action.MyEntityHome\" entity-class=\"com.example.model.MyEntity\"\n"
+" created-message=\"'#{myEntityHome.instance.name}' has been successfully added.\"/>]]>"
#. Tag: para
#: Xml.xml:281
#, no-c-format
-msgid ""
-"Inside the component, you can access the expression string by calling "
-"<literal>getExpressionString()</literal> on the <literal>ValueExpression</"
-"literal> or <literal>MethodExpression</literal>. If the property is a "
-"<literal>ValueExpression</literal>, you can resolve the value using "
-"<literal>getValue()</literal> and if the property is a "
-"<literal>MethodExpression</literal>, you can invoke the method using "
-"<literal>invoke(Object args...)</literal>. Obviously, to assign a value to a "
-"<literal>MethodExpression</literal> property, the entire initial value must "
-"be a single EL expression."
+msgid "Inside the component, you can access the expression string by calling <literal>getExpressionString()</literal> on the <literal>ValueExpression</literal> or <literal>MethodExpression</literal>. If the property is a <literal>ValueExpression</literal>, you can resolve the value using <literal>getValue()</literal> and if the property is a <literal>MethodExpression</literal>, you can invoke the method using <literal>invoke(Object args...)</literal>. Obviously, to assign a value to a <literal>MethodExpression</literal> property, the entire initial value must be a single EL expression."
msgstr ""
#. Tag: title
#: Xml.xml:294
#, no-c-format
msgid "Using XML Namespaces"
-msgstr ""
+msgstr "Uso dei namespace XML"
#. Tag: para
#: Xml.xml:295
#, no-c-format
-msgid ""
-"Throughout the examples, there have been two competing ways of declaring "
-"components: with and without the use of XML namespaces. The following shows "
-"a typical <literal>components.xml</literal> file without namespaces:"
+msgid "Throughout the examples, there have been two competing ways of declaring components: with and without the use of XML namespaces. The following shows a typical <literal>components.xml</literal> file without namespaces:"
msgstr ""
#. Tag: programlisting
@@ -735,8 +721,7 @@
msgid ""
"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
"<components xmlns=\"http://jboss.com/products/seam/components\"\n"
-" xsi:schemaLocation=\"http://jboss.com/products/seam/components "
-"http://jboss.com/products/seam/components-2.1.xsd\">\n"
+" xsi:schemaLocation=\"http://jboss.com/products/seam/components http://jboss.com/products/seam/components-2.1.xsd\">\n"
"\n"
" <component class=\"org.jboss.seam.core.init\">\n"
" <property name=\"debug\">true</property>\n"
@@ -745,13 +730,21 @@
" \n"
"</components>]]>"
msgstr ""
+"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xsi:schemaLocation=\"http://jboss.com/products/seam/components http://jboss.com/products/seam/components-2.1.xsd\">\n"
+"\n"
+" <component class=\"org.jboss.seam.core.init\">\n"
+" <property name=\"debug\">true</property>\n"
+" <property name=\"jndiPattern\">@jndiPattern@</property>\n"
+" </component>\n"
+" \n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:303
#, no-c-format
-msgid ""
-"As you can see, this is somewhat verbose. Even worse, the component and "
-"attribute names cannot be validated at development time."
+msgid "As you can see, this is somewhat verbose. Even worse, the component and attribute names cannot be validated at development time."
msgstr ""
#. Tag: para
@@ -769,47 +762,41 @@
" xmlns:core=\"http://jboss.com/products/seam/core\"\n"
" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
" xsi:schemaLocation=\n"
-" \"http://jboss.com/products/seam/core http://jboss.com/"
-"products/seam/core-2.1.xsd \n"
-" http://jboss.com/products/seam/components http://jboss.com/"
-"products/seam/components-2.1.xsd\">\n"
+" \"http://jboss.com/products/seam/core http://jboss.com/products/seam/core-2.1.xsd \n"
+" http://jboss.com/products/seam/components http://jboss.com/products/seam/components-2.1.xsd\">\n"
"\n"
" <core:init debug=\"true\" jndi-pattern=\"@jndiPattern@\"/>\n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:core=\"http://jboss.com/products/seam/core\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\n"
+" \"http://jboss.com/products/seam/core http://jboss.com/products/seam/core-2.1.xsd \n"
+" http://jboss.com/products/seam/components http://jboss.com/products/seam/components-2.1.xsd\">\n"
+"\n"
+" <core:init debug=\"true\" jndi-pattern=\"@jndiPattern@\"/>\n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:312
#, no-c-format
-msgid ""
-"Even though the schema declarations are verbose, the actual XML content is "
-"lean and easy to understand. The schemas provide detailed information about "
-"each component and the attributes available, allowing XML editors to offer "
-"intelligent autocomplete. The use of namespaced elements makes generating "
-"and maintaining correct <literal>components.xml</literal> files much simpler."
+msgid "Even though the schema declarations are verbose, the actual XML content is lean and easy to understand. The schemas provide detailed information about each component and the attributes available, allowing XML editors to offer intelligent autocomplete. The use of namespaced elements makes generating and maintaining correct <literal>components.xml</literal> files much simpler."
msgstr ""
#. Tag: para
#: Xml.xml:319
#, no-c-format
-msgid ""
-"Now, this works great for the built-in Seam components, but what about user "
-"components? There are two options. First, Seam supports mixing the two "
-"models, allowing the use of the generic <literal><component></literal> "
-"declarations for user components, along with namespaced declarations for "
-"built-in components. But even better, Seam allows you to quickly declare "
-"namespaces for your own components."
+msgid "Now, this works great for the built-in Seam components, but what about user components? There are two options. First, Seam supports mixing the two models, allowing the use of the generic <literal><component></literal> declarations for user components, along with namespaced declarations for built-in components. But even better, Seam allows you to quickly declare namespaces for your own components."
msgstr ""
#. Tag: para
#: Xml.xml:326
#, no-c-format
-msgid ""
-"Any Java package can be associated with an XML namespace by annotating the "
-"package with the <literal>@Namespace</literal> annotation. (Package-level "
-"annotations are declared in a file named <literal>package-info.java</"
-"literal> in the package directory.) Here is an example from the seampay demo:"
+msgid "Any Java package can be associated with an XML namespace by annotating the package with the <literal>@Namespace</literal> annotation. (Package-level annotations are declared in a file named <literal>package-info.java</literal> in the package directory.) Here is an example from the seampay demo:"
msgstr ""
#. Tag: programlisting
@@ -821,13 +808,15 @@
"\n"
"import org.jboss.seam.annotations.Namespace;"
msgstr ""
+"@Namespace(value=\"http://jboss.com/products/seam/examples/seampay\")\n"
+"package org.jboss.seam.example.seampay;\n"
+"\n"
+"import org.jboss.seam.annotations.Namespace;"
#. Tag: para
#: Xml.xml:334
#, no-c-format
-msgid ""
-"That is all you need to do to use the namespaced style in "
-"<literal>components.xml</literal>! Now we can write:"
+msgid "That is all you need to do to use the namespaced style in <literal>components.xml</literal>! Now we can write:"
msgstr ""
#. Tag: programlisting
@@ -839,8 +828,7 @@
" ... >\n"
"\n"
" <pay:payment-home new-instance=\"#{newPayment}\"\n"
-" created-message=\"Created a new payment to #"
-"{newPayment.payee}\" />\n"
+" created-message=\"Created a new payment to #{newPayment.payee}\" />\n"
"\n"
" <pay:payment name=\"newPayment\"\n"
" payee=\"Somebody\"\n"
@@ -850,12 +838,26 @@
" ...\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:pay=\"http://jboss.com/products/seam/examples/seampay\"\n"
+" ... >\n"
+"\n"
+" <pay:payment-home new-instance=\"#{newPayment}\"\n"
+" created-message=\"Created a new payment to #{newPayment.payee}\" />\n"
+"\n"
+" <pay:payment name=\"newPayment\"\n"
+" payee=\"Somebody\"\n"
+" account=\"#{selectedAccount}\"\n"
+" payment-date=\"#{currentDatetime}\"\n"
+" created-date=\"#{currentDatetime}\" />\n"
+" ...\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:341
#, no-c-format
msgid "<para>Or:</para>"
-msgstr ""
+msgstr "<para>Oppure:</para>"
#. Tag: programlisting
#: Xml.xml:343
@@ -867,8 +869,7 @@
"\n"
" <pay:payment-home>\n"
" <pay:new-instance>\"#{newPayment}\"</pay:new-instance>\n"
-" <pay:created-message>Created a new payment to #{newPayment.payee}</"
-"pay:created-message>\n"
+" <pay:created-message>Created a new payment to #{newPayment.payee}</pay:created-message>\n"
" </pay:payment-home>\n"
" \n"
" <pay:payment name=\"newPayment\">\n"
@@ -880,14 +881,28 @@
" ...\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:pay=\"http://jboss.com/products/seam/examples/seampay\"\n"
+" ... >\n"
+"\n"
+" <pay:payment-home>\n"
+" <pay:new-instance>\"#{newPayment}\"</pay:new-instance>\n"
+" <pay:created-message>Created a new payment to #{newPayment.payee}</pay:created-message>\n"
+" </pay:payment-home>\n"
+" \n"
+" <pay:payment name=\"newPayment\">\n"
+" <pay:payee>Somebody\"</pay:payee>\n"
+" <pay:account>#{selectedAccount}</pay:account>\n"
+" <pay:payment-date>#{currentDatetime}</pay:payment-date>\n"
+" <pay:created-date>#{currentDatetime}</pay:created-date>\n"
+" </pay:payment>\n"
+" ...\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:345
#, no-c-format
-msgid ""
-"These examples illustrate the two usage models of a namespaced element. In "
-"the first declaration, the <literal><pay:payment-home></literal> "
-"references the <literal>paymentHome</literal> component:"
+msgid "These examples illustrate the two usage models of a namespaced element. In the first declaration, the <literal><pay:payment-home></literal> references the <literal>paymentHome</literal> component:"
msgstr ""
#. Tag: programlisting
@@ -903,23 +918,25 @@
" ... \n"
"}]]>"
msgstr ""
+"<![CDATA[package org.jboss.seam.example.seampay;\n"
+"...\n"
+"@Name(\"paymentHome\")\n"
+"public class PaymentController\n"
+" extends EntityHome<Payment>\n"
+"{\n"
+" ... \n"
+"}]]>"
#. Tag: para
#: Xml.xml:353
#, no-c-format
-msgid ""
-"The element name is the hyphenated form of the component name. The "
-"attributes of the element are the hyphenated form of the property names."
+msgid "The element name is the hyphenated form of the component name. The attributes of the element are the hyphenated form of the property names."
msgstr ""
#. Tag: para
#: Xml.xml:358
#, no-c-format
-msgid ""
-"In the second declaration, the <literal><pay:payment></literal> "
-"element refers to the <literal>Payment</literal> class in the <literal>org."
-"jboss.seam.example.seampay</literal> package. In this case <literal>Payment</"
-"literal> is an entity that is being declared as a Seam component:"
+msgid "In the second declaration, the <literal><pay:payment></literal> element refers to the <literal>Payment</literal> class in the <literal>org.jboss.seam.example.seampay</literal> package. In this case <literal>Payment</literal> is an entity that is being declared as a Seam component:"
msgstr ""
#. Tag: programlisting
@@ -935,97 +952,96 @@
" ...\n"
"}]]>"
msgstr ""
+"<![CDATA[package org.jboss.seam.example.seampay;\n"
+"...\n"
+"@Name(\"paymentHome\")\n"
+"public class PaymentController\n"
+" extends EntityHome<Payment>\n"
+"{\n"
+" ... \n"
+"}]]>"
#. Tag: para
#: Xml.xml:366
#, no-c-format
-msgid ""
-"If we want validation and autocompletion to work for user-defined "
-"components, we will need a schema. Seam does not yet provide a mechanism to "
-"automatically generate a schema for a set of components, so it is necessary "
-"to generate one manually. The schema definitions for the standard Seam "
-"packages can be used for guidance."
+msgid "If we want validation and autocompletion to work for user-defined components, we will need a schema. Seam does not yet provide a mechanism to automatically generate a schema for a set of components, so it is necessary to generate one manually. The schema definitions for the standard Seam packages can be used for guidance."
msgstr ""
#. Tag: para
#: Xml.xml:373
#, no-c-format
msgid "The following are the the namespaces used by Seam:"
-msgstr ""
+msgstr "Seam utilizza i seguenti namespace:"
#. Tag: para
#: Xml.xml:377
#, no-c-format
-msgid ""
-"components — <literal>http://jboss.com/products/seam/components</"
-"literal>"
-msgstr ""
+msgid "components — <literal>http://jboss.com/products/seam/components</literal>"
+msgstr "components — <literal>http://jboss.com/products/seam/components</literal>"
#. Tag: para
#: Xml.xml:380
#, no-c-format
msgid "core — <literal>http://jboss.com/products/seam/core</literal>"
-msgstr ""
+msgstr "core — <literal>http://jboss.com/products/seam/core</literal>"
#. Tag: para
#: Xml.xml:383
#, no-c-format
msgid "drools — <literal>http://jboss.com/products/seam/drools</literal>"
-msgstr ""
+msgstr "drools — <literal>http://jboss.com/products/seam/drools</literal>"
#. Tag: para
#: Xml.xml:386
#, no-c-format
-msgid ""
-"framework — <literal>http://jboss.com/products/seam/framework</literal>"
-msgstr ""
+msgid "framework — <literal>http://jboss.com/products/seam/framework</literal>"
+msgstr "framework — <literal>http://jboss.com/products/seam/framework</literal>"
#. Tag: para
#: Xml.xml:389
#, no-c-format
msgid "jms — <literal>http://jboss.com/products/seam/jms</literal>"
-msgstr ""
+msgstr "jms — <literal>http://jboss.com/products/seam/jms</literal>"
#. Tag: para
#: Xml.xml:392
#, no-c-format
-msgid ""
-"remoting — <literal>http://jboss.com/products/seam/remoting</literal>"
-msgstr ""
+msgid "remoting — <literal>http://jboss.com/products/seam/remoting</literal>"
+msgstr "remoting — <literal>http://jboss.com/products/seam/remoting</literal>"
#. Tag: para
#: Xml.xml:395
#, no-c-format
msgid "theme — <literal>http://jboss.com/products/seam/theme</literal>"
-msgstr ""
+msgstr "theme — <literal>http://jboss.com/products/seam/theme</literal>"
#. Tag: para
#: Xml.xml:398
#, no-c-format
-msgid ""
-"security — <literal>http://jboss.com/products/seam/security</literal>"
-msgstr ""
+msgid "security — <literal>http://jboss.com/products/seam/security</literal>"
+msgstr "security — <literal>http://jboss.com/products/seam/security</literal>"
#. Tag: para
#: Xml.xml:401
#, no-c-format
msgid "mail — <literal>http://jboss.com/products/seam/mail</literal>"
-msgstr ""
+msgstr "mail — <literal>http://jboss.com/products/seam/mail</literal>"
#. Tag: para
#: Xml.xml:404
#, no-c-format
msgid "web — <literal>http://jboss.com/products/seam/web</literal>"
-msgstr ""
+msgstr "web — <literal>http://jboss.com/products/seam/web</literal>"
#. Tag: para
#: Xml.xml:407
#, no-c-format
msgid "pdf — <literal>http://jboss.com/products/seam/pdf</literal>"
-msgstr ""
+msgstr "pdf — <literal>http://jboss.com/products/seam/pdf</literal>"
#. Tag: para
#: Xml.xml:410
#, no-c-format
msgid "spring — <literal>http://jboss.com/products/seam/spring</literal>"
-msgstr ""
+msgstr "spring — <literal>http://jboss.com/products/seam/spring</literal>"
+
15 years, 12 months
- 1
- 0
Seam SVN: r9839 - trunk/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2008-12-24 03:35:24 -0500 (Wed, 24 Dec 2008)
New Revision: 9839
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/I18n.po
trunk/doc/Seam_Reference_Guide/it-IT/Wicket.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/I18n.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/I18n.po 2008-12-24 00:03:02 UTC (rev 9838)
+++ trunk/doc/Seam_Reference_Guide/it-IT/I18n.po 2008-12-24 08:35:24 UTC (rev 9839)
@@ -6,7 +6,7 @@
"Project-Id-Version: I18n\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:38+0000\n"
-"PO-Revision-Date: 2008-12-23 16:08+0100\n"
+"PO-Revision-Date: 2008-12-24 09:28+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: Italian <stefano.travelli(a)gmail.com>\n"
"MIME-Version: 1.0\n"
@@ -181,7 +181,7 @@
#: I18n.xml:153
#, no-c-format
msgid "It is <emphasis>possible</emphasis> to set the locale manually via the Seam configuration properties <literal> org.jboss.seam.international.localeSelector.language</literal>, <literal> org.jboss.seam.international.localeSelector.country</literal> and <literal> org.jboss.seam.international.localeSelector.variant</literal>, but we can't think of any good reason to ever do this."
-msgstr "E' <emphasis>possibile</emphasis> impostare la lingua manualmente tramite le proprietà di configurazione di Seam <litera>org.jboss.seam.international.localeSelector.language</literal>, <literal>org.jboss.seam.international.localeSelector.country</literal> e <literal>org.jboss.seam.internationale.localeSelector.variant</literal>, ma non c'è una vera buona ragione per farlo."
+msgstr "E' <emphasis>possibile</emphasis> impostare la lingua manualmente tramite le proprietà di configurazione di Seam <literal>org.jboss.seam.international.localeSelector.language</literal>, <literal>org.jboss.seam.international.localeSelector.country</literal> e <literal>org.jboss.seam.internationale.localeSelector.variant</literal>, ma non c'è una vera buona ragione per farlo."
#. Tag: para
#: I18n.xml:160
@@ -214,7 +214,7 @@
#: I18n.xml:168
#, no-c-format
msgid "Or, if you want a list of all supported locales from <literal> faces-config.xml</literal>, just use:"
-msgstr "Oppure, se si vuole mostrare una lista delle lingue gestite da <litera>faces-config.xml</literal>, si può usare:"
+msgstr "Oppure, se si vuole mostrare una lista delle lingue gestite da <literal>faces-config.xml</literal>, si può usare:"
#. Tag: programlisting
#: I18n.xml:171
@@ -458,7 +458,7 @@
#: I18n.xml:290
#, no-c-format
msgid "This will display <literal>Hello, Gavin King</literal> or <literal>G'day, Gavin</literal>, depending upon the user's locale."
-msgstr "Questo mostrerà <literal>Hello, Gavin King</litera> oppure <literal>G'day, Gavin</literal>, a seconda della lingua dell'utente."
+msgstr "Questo mostrerà <literal>Hello, Gavin King</literal> oppure <literal>G'day, Gavin</literal>, a seconda della lingua dell'utente."
#. Tag: title
#: I18n.xml:297
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Wicket.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Wicket.po 2008-12-24 00:03:02 UTC (rev 9838)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Wicket.po 2008-12-24 08:35:24 UTC (rev 9839)
@@ -1,113 +1,91 @@
# Language it-IT translations for Seam_Reference_Guide package.
-# Automatically generated, 2008.
#
+# Automatically generated, 2008.
msgid ""
msgstr ""
-"Project-Id-Version: Seam_Reference_Guide \n"
+"Project-Id-Version: Seam_Reference_Guide\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-11-06 00:24+0000\n"
-"PO-Revision-Date: 2008-10-14 11:39+0000\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"PO-Revision-Date: 2008-12-24 09:35+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
+"Language-Team: Italian <stefano.travelli(a)gmail.com>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: Lokalize 0.2\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. Tag: title
#: Wicket.xml:6
#, no-c-format
msgid "Writing your presentation layer using Apache Wicket"
-msgstr ""
+msgstr "Scrivere la parte di presentazione usando Apache Wicket"
#. Tag: para
#: Wicket.xml:8
#, no-c-format
-msgid ""
-"Seam supports Wicket as an alternative presentation layer to JSF. Take a "
-"look at the <code>wicket</code> example in Seam which shows the Booking "
-"Example ported to Wicket."
-msgstr ""
+msgid "Seam supports Wicket as an alternative presentation layer to JSF. Take a look at the <code>wicket</code> example in Seam which shows the Booking Example ported to Wicket."
+msgstr "Seam supporta Wicket come uno strato di presentazione alternativo a JSF. Si guardi l'esempio <code>wicket</code> in Seam che illustra l'esempio Booking riscritto per Wicket."
#. Tag: para
#: Wicket.xml:15
#, no-c-format
-msgid ""
-"Wicket support is new to Seam, so some features which are available in JSF "
-"are not yet available when you use Wicket (e.g. pageflow). You'll also "
-"notice that the documentation is very JSF-centric and needs reorganization "
-"to reflect the first class support for Wicket."
-msgstr ""
+msgid "Wicket support is new to Seam, so some features which are available in JSF are not yet available when you use Wicket (e.g. pageflow). You'll also notice that the documentation is very JSF-centric and needs reorganization to reflect the first class support for Wicket."
+msgstr "Il supporto Wicket è nuovo in Seam, perciò alcune caratteristiche che sono disponibili in JSF non sono ancora disponibili quando viene usato Wicket (ad esempio il pageflow). Si potrà notare inoltre che la documentazione è molto centrata su JSF e necessita di una riorganizzazione per riflettere il supporto di prima categoria per Wicket."
#. Tag: title
#: Wicket.xml:25
#, no-c-format
msgid "Adding Seam to your wicket application"
-msgstr ""
+msgstr "Aggiungere Seam ad un'applicazione Wicket"
#. Tag: para
#: Wicket.xml:27
#, no-c-format
-msgid ""
-"The features added to your Wicket application can be split into two "
-"categories: bijection and orchestration; these are discussed in detail below."
-msgstr ""
+msgid "The features added to your Wicket application can be split into two categories: bijection and orchestration; these are discussed in detail below."
+msgstr "Le caratteristiche aggiunte ad un'applicazione Wicket possono essere divise in due categorie: la bijection e l'orchestrazione. Esse vengono discusse in dettaglio di seguito."
#. Tag: para
#: Wicket.xml:33
#, no-c-format
-msgid ""
-"Extensive use of inner classes is common when building Wicket applications, "
-"with the component tree being built in the constructor. Seam fully supports "
-"the use of annotation based control in inner classes and constructors "
-"(unlike regular Seam components)."
-msgstr ""
+msgid "Extensive use of inner classes is common when building Wicket applications, with the component tree being built in the constructor. Seam fully supports the use of annotation based control in inner classes and constructors (unlike regular Seam components)."
+msgstr "E' comune un uso intensivo di classi interne (inner class) quando si costruisce un'applicazione Wicket, in cui l'albero dei componenti viene generato nel costruttore. Seam gestisce pienamente l'uso di annotazioni di controllo nelle inner class e nei costruttori (a differenza che nei componenti Seam normali)."
#. Tag: para
#: Wicket.xml:40
#, no-c-format
-msgid ""
-"Annotations are processed <emphasis>after</emphasis> any call to a "
-"superclass. This mean's that any injected attributes cannot be passed as an "
-"argument in a call to <code>this()</code> or <code>super()</code>."
-msgstr ""
+msgid "Annotations are processed <emphasis>after</emphasis> any call to a superclass. This mean's that any injected attributes cannot be passed as an argument in a call to <code>this()</code> or <code>super()</code>."
+msgstr "Le annotazioni sono elaborate <emphasis>dopo</emphasis> ogni chiamata alla superclasse. Ciò significa che qualsiasi attributo iniettato non può essere passato come argomento in una chiamata a <code>this()</code> o <code>super()</code>."
#. Tag: para
#: Wicket.xml:48
#, no-c-format
msgid "We are working to improve this."
-msgstr ""
+msgstr "Stiamo lavorando per migliorare questo aspetto."
#. Tag: para
#: Wicket.xml:53
#, no-c-format
-msgid ""
-"When a method is called in an inner class, bijection occurs for any class "
-"which encloses it. This allows you to place your bijected variables in the "
-"outer class, and refer to them in any inner class."
-msgstr ""
+msgid "When a method is called in an inner class, bijection occurs for any class which encloses it. This allows you to place your bijected variables in the outer class, and refer to them in any inner class."
+msgstr "Quando un metodo è chiamato in una inner class, la bijection avviene per ogni classe che la contiene. Ciò consente di posizionare le variabili bi-iniettabili nella classe esterna e riferirsi ad esse in qualsiasi inner class."
#. Tag: title
#: Wicket.xml:60
#, no-c-format
msgid "Bijection"
-msgstr ""
+msgstr "Bijection"
#. Tag: para
#: Wicket.xml:62
#, no-c-format
-msgid ""
-"A Seam enabled Wicket application has full access to the all the standard "
-"Seam contexts (<code>EVENT</code>, <code>CONVERSATION</code>, <code>SESSION</"
-"code>, <code>APPLICATION</code> and <code>BUSINESS_PROCESS</code>)."
-msgstr ""
+msgid "A Seam enabled Wicket application has full access to the all the standard Seam contexts (<code>EVENT</code>, <code>CONVERSATION</code>, <code>SESSION</code>, <code>APPLICATION</code> and <code>BUSINESS_PROCESS</code>)."
+msgstr "Un'applicazione Wicket abilitata per Seam ha accesso completo a tutti i contesti Seam standard (<code>EVENT</code>, <code>CONVERSATION</code>, <code>SESSION</code>, <code>APPLICATION</code> e <code>BUSINESS_PROCESS</code>)."
#. Tag: para
#: Wicket.xml:69
#, no-c-format
-msgid ""
-"To access Seam component's from Wicket, you just need to inject it using "
-"<code>@In</code>:"
-msgstr ""
+msgid "To access Seam component's from Wicket, you just need to inject it using <code>@In</code>:"
+msgstr "Per accedere ai componenti Seam da Wicket basta iniettarli usando <code>@In</code>:"
#. Tag: programlisting
#: Wicket.xml:74
@@ -116,22 +94,20 @@
"<![CDATA[@In(create=true)\n"
"private HotelBooking hotelBooking;]]>"
msgstr ""
+"<![CDATA[@In(create=true)\n"
+"private HotelBooking hotelBooking;]]>"
#. Tag: para
#: Wicket.xml:77
#, no-c-format
-msgid ""
-"As your Wicket class isn't a full Seam component, there is no need to "
-"annotate it <code>@Name</code>."
-msgstr ""
+msgid "As your Wicket class isn't a full Seam component, there is no need to annotate it <code>@Name</code>."
+msgstr "Poiché la classe Wicket non è un componente Seam completo, non c'è bisogno di annotarla con <code>@Name</code>."
#. Tag: para
#: Wicket.xml:83
#, no-c-format
-msgid ""
-"You can also outject an object into the Seam contexts from a Wicket "
-"component:"
-msgstr ""
+msgid "You can also outject an object into the Seam contexts from a Wicket component:"
+msgstr "E' anche possibile fare l'outject di un oggetto da un componente Wicket nei contesti Seam:"
#. Tag: programlisting
#: Wicket.xml:88
@@ -140,36 +116,34 @@
"<![CDATA[(a)Out(scope=ScopeType.EVENT, required=false)\n"
"private String verify;]]>"
msgstr ""
+"<![CDATA[(a)Out(scope=ScopeType.EVENT, required=false)\n"
+"private String verify;]]>"
#. Tag: para
#: Wicket.xml:90
#, no-c-format
msgid "TODO Make this more use case driven"
-msgstr ""
+msgstr "TODO Rendere questa parte più orientata allo use case"
#. Tag: title
#: Wicket.xml:97
#, no-c-format
msgid "Orchestration"
-msgstr ""
+msgstr "Orchestrazione"
#. Tag: para
#: Wicket.xml:99
#, no-c-format
-msgid ""
-"You can secure a Wicket component by using the <code>@Restrict</code> "
-"annotation. This can be placed on the outer component or any inner "
-"components. If <code>@Restrict</code> is specified, the component will "
-"automatically be restricted to logged in users. You can optionally use an EL "
-"expression in the <code>value</code> attribute to specify a restriction to "
-"be applied. For more refer to the <xref linkend=\"security\"/>."
-msgstr ""
+msgid "You can secure a Wicket component by using the <code>@Restrict</code> annotation. This can be placed on the outer component or any inner components. If <code>@Restrict</code> is specified, the component will automatically be restricted to logged in users. You can optionally use an EL expression in the <code>value</code> attribute to specify a restriction to be applied. For more refer to the <xref linkend=\"security\"/>."
+msgstr "E' possibile abilitare la sicurezza di un componente Wicket usando l'annotazione <code>@Restrict</code>. Questa può essere messa nel componente più esterno o in qualsiasi componente interno. Se viene indicato <code>@Restrict</code>, l'accesso al componente verrà automaticamente limitato agli utenti registrati. Facoltativamente è possibile usare un'espressione EL nell'attributo <code>value</code> per specificare la restrizione da applicare. Per maggiori dettagli vedi <xref linkend=\"security\"/>."
#. Tag: para
-#: Wicket.xml:109 Wicket.xml:136 Wicket.xml:211
+#: Wicket.xml:109
+#: Wicket.xml:136
+#: Wicket.xml:211
#, no-c-format
msgid "For example:"
-msgstr ""
+msgstr "Ad esempio:"
#. Tag: programlisting
#: Wicket.xml:113
@@ -180,28 +154,28 @@
"\n"
" ...]]>"
msgstr ""
+"<![CDATA[@Restrict\n"
+"public class Main extends WebPage {\n"
+"\n"
+" ...]]>"
#. Tag: para
#: Wicket.xml:116
#, no-c-format
msgid "Seam will automatically apply the restriction to any nested classes."
-msgstr ""
+msgstr "Seam applicherà automaticamente la restrizione ad ogni classe interna."
#. Tag: para
#: Wicket.xml:122
#, no-c-format
-msgid ""
-"You can demarcate conversations from within a Wicket component through the "
-"use of <code>@Begin</code> and <code>@End</code>. The semantics for these "
-"annotations are the same as when used in a Seam component. You can place "
-"<code>@Begin</code> and <code>@End</code> on any method."
-msgstr ""
+msgid "You can demarcate conversations from within a Wicket component through the use of <code>@Begin</code> and <code>@End</code>. The semantics for these annotations are the same as when used in a Seam component. You can place <code>@Begin</code> and <code>@End</code> on any method."
+msgstr "E' possibile demarcare le conversazioni da un componente Wicket attraverso l'uso di <code>@Begin</code> e <code>@End</code>. La semantica di queste annotazioni è la stessa di quando sono usate nei componenti Seam. E' possibile mettere <code>@Begin</code> e <code>@End</code> in qualsiasi metodo."
#. Tag: para
#: Wicket.xml:131
#, no-c-format
msgid "The deprecated <code>ifOutcome</code> attribute is not supported."
-msgstr ""
+msgstr "L'attributo deprecato <code>ifOutcome</code> non è gestito."
#. Tag: programlisting
#: Wicket.xml:140
@@ -217,15 +191,21 @@
" }\n"
"};]]>"
msgstr ""
+"<![CDATA[item.add(new Link(\"viewHotel\") {\n"
+"\n"
+" @Override\n"
+" @Begin\n"
+" public void onClick() {\n"
+" hotelBooking.selectHotel(hotel);\n"
+" setResponsePage(org.jboss.seam.example.wicket.Hotel.class);\n"
+" }\n"
+"};]]>"
#. Tag: para
#: Wicket.xml:142
#, no-c-format
-msgid ""
-"You may have pages in your application which can only be accessed when the "
-"user has a long-running conversation active. To enforce this you can use the "
-"<code>@NoConversationPage</code> annotation:"
-msgstr ""
+msgid "You may have pages in your application which can only be accessed when the user has a long-running conversation active. To enforce this you can use the <code>@NoConversationPage</code> annotation:"
+msgstr "E' possibile che l'applicazione abbia delle pagine che possono essere visitate solo quando l'utente ha una conversazione lunga (long-running conversation) attiva. Per imporre questo criterio è possibile usare l'annotazione <code>@NoConversationPage</code>:"
#. Tag: programlisting
#: Wicket.xml:148
@@ -235,53 +215,39 @@
"@NoConversationPage(Main.class)\n"
"public class Hotel extends WebPage {]]>"
msgstr ""
+"<![CDATA[@Restrict\n"
+"@NoConversationPage(Main.class)\n"
+"public class Hotel extends WebPage {]]>"
#. Tag: para
#: Wicket.xml:150
#, no-c-format
-msgid ""
-"If you want to further decouple your application classes, you can use Seam "
-"events. Of course, you can raise an event using <code>Events.instance()."
-"raiseEvent(\"foo\")</code>. Alternatively, you can annotate a method "
-"<code>@RaiseEvent(\"foo\")</code>; if the method returns a non-null outcome "
-"without exception, the event will be raised."
-msgstr ""
+msgid "If you want to further decouple your application classes, you can use Seam events. Of course, you can raise an event using <code>Events.instance().raiseEvent(\"foo\")</code>. Alternatively, you can annotate a method <code>@RaiseEvent(\"foo\")</code>; if the method returns a non-null outcome without exception, the event will be raised."
+msgstr "Se si vogliono ulteriormente disaccoppiare le classi dell'applicazione è possibile usare gli eventi Seam. Naturalmente è possibile lanciare un evento usando <code>Events.instance().raiseEvent(\"pippo\")</code>. In alternativa è possibile annotare un metodo con <code>@RaiseEvent(\"pippo\")</code>; se il metodo restituisce un valore non nullo senza eccezioni, l'evento verrà lanciato."
#. Tag: para
#: Wicket.xml:159
#, no-c-format
-msgid ""
-"You can also control tasks and processes in Wicket classes through the use "
-"of <code>@CreateProcess</code>, <code>@ResumeTask</code>, <code>@BeginTask</"
-"code>, <code>@EndTask</code>, <code>@StartTask</code> and <code>@Transition</"
-"code>."
-msgstr ""
+msgid "You can also control tasks and processes in Wicket classes through the use of <code>@CreateProcess</code>, <code>@ResumeTask</code>, <code>@BeginTask</code>, <code>@EndTask</code>, <code>@StartTask</code> and <code>@Transition</code>."
+msgstr "E' anche possibile controllare task e processi nelle classi Wicket attraverso l'uso di <code>@CreateProcess</code>, <code>@ResumeTask</code>, <code>@BeginTask</code>, <code>@EndTask</code>, <code>@StartTask</code> e <code>@Transition</code>."
#. Tag: para
#: Wicket.xml:166
#, no-c-format
msgid "TODO - Implement BPM control - JBSEAM-3194"
-msgstr ""
+msgstr "TODO - Realizzare il controllo BPM - JBSEAM-3194"
#. Tag: title
#: Wicket.xml:174
#, no-c-format
msgid "Setting up your project"
-msgstr ""
+msgstr "Impostare il progetto"
#. Tag: para
#: Wicket.xml:176
#, no-c-format
-msgid ""
-"Seam needs to instrument the bytecode of your Wicket classes to be able to "
-"intercept the annotations you use. Seam provides two ways to do this.The "
-"first is to place your classes in <code>WEB-INF/wicket</code>. Seam will "
-"look for classes placed in this directory at startup and instrument them. An "
-"alternative approach, which can be used alongside the first, is to use an "
-"ant task for instrumention. Seam provides such a task; it is packaged in "
-"<literal>jboss-seam-wicket-ant.jar </literal>, and can be used in the "
-"following manner:"
-msgstr ""
+msgid "Seam needs to instrument the bytecode of your Wicket classes to be able to intercept the annotations you use. Seam provides two ways to do this.The first is to place your classes in <code>WEB-INF/wicket</code>. Seam will look for classes placed in this directory at startup and instrument them. An alternative approach, which can be used alongside the first, is to use an ant task for instrumention. Seam provides such a task; it is packaged in <literal>jboss-seam-wicket-ant.jar </literal>, and can be used in the following manner:"
+msgstr "Seam ha bisogno di intervenire sul bytecode delle classi Wicket in modo da poter intercettare le annotazioni usate. Seam fornisce due modi per fare questo. Il primo è di mettere le classi in <code>WEB-INF/wicket</code>. Seam cercherà le classi messe in questa cartella durante l'avvio e interverrà sul loro bytecode. Un approccio alternativo, che può essere utilizzato insieme al primo, è di usare un task ant per modificare il bytecode. Seam fornisce questo task: è contenuto in <literal>jboss-seam-wicket-ant.jar</literal> e può essere usato nel seguento modo: "
#. Tag: programlisting
#: Wicket.xml:186
@@ -302,55 +268,50 @@
" <fileset dir=\"${build.classes}\" includes=\"**/*.class\"/>\n"
"</instrumentWicket>]]>"
msgstr ""
+"<![CDATA[<taskdef name=\"instrumentWicket\" \n"
+" classname=\"org.jboss.seam.wicket.ioc.WicketInstrumentationTask\">\n"
+" <classpath>\n"
+" <pathelement location=\"lib/jboss-seam-wicket-ant.jar\"/>\n"
+" <pathelement location=\"web/WEB-INF/lib/jboss-seam-wicket.jar\"/>\n"
+" <pathelement location=\"lib/javassist.jar\"/>\n"
+" <pathelement location=\"lib/jboss-seam.jar\"/>\n"
+" </classpath>\n"
+"</taskdef>\n"
+"\n"
+"<instrumentWicket outputDirectory=\"${build.instrumented}\">\n"
+" <classpath refid=\"build.classpath\"/>\n"
+" <fileset dir=\"${build.classes}\" includes=\"**/*.class\"/>\n"
+"</instrumentWicket>]]>"
#. Tag: para
#: Wicket.xml:187
#, no-c-format
-msgid ""
-"Then have ant copy the instrumented classes in <literal>${build.instrumented}"
-"</literal> into <literal>WEB-INF/classes</literal>. If you want to hot "
-"deploy the Wicket components, you can copy the instrumented classes to "
-"<literal>WEB-INF/dev</literal>; if you use hot deploy, make sure that your "
-"<literal>WicketApplication</literal> class is also hot-deployed. Upon a "
-"reload of hot-deployed classes, the entire WicketApplication instance has to "
-"be re-initialized, in order to pick up new references to the classes of "
-"mounted pages."
-msgstr ""
+msgid "Then have ant copy the instrumented classes in <literal>${build.instrumented}</literal> into <literal>WEB-INF/classes</literal>. If you want to hot deploy the Wicket components, you can copy the instrumented classes to <literal>WEB-INF/dev</literal>; if you use hot deploy, make sure that your <literal>WicketApplication</literal> class is also hot-deployed. Upon a reload of hot-deployed classes, the entire WicketApplication instance has to be re-initialized, in order to pick up new references to the classes of mounted pages."
+msgstr "Dopo bisogna fare in modo che Ant copi le classi alterate da <literal>${build.instrumented}</literal> a <literal>WEB-INF/classes</literal>. Se si vuole attivare l'esecuzione a caldo dei componenti Wicket è possibile copiare le classi alterate in <literal>WEB-INF/hot</literal>. Se si usa l'esecuzione a caldo, accertarsi che anche la classe <literal>WicketApplication</literal> sia eseguita nello stesso modo. Dopo che le classi eseguite a caldo vengono ricaricate, l'intera istanza di WicketApplication deve essere reinizializzata allo scopo di recuperare tutti i nuovi riferimenti alle classi delle pagine montate."
#. Tag: title
#: Wicket.xml:202
#, no-c-format
msgid "Defining the Application"
-msgstr ""
+msgstr "Definire l'applicazione"
#. Tag: para
#: Wicket.xml:204
#, no-c-format
-msgid ""
-"A Wicket web application which uses Seam should use "
-"<code>SeamWebApplication</code> as the base class; this creates hooks into "
-"the Wicket lifecycle allowing Seam to automagically propagate the "
-"conversation as needed. It also adds status messages to the page."
-msgstr ""
+msgid "A Wicket web application which uses Seam should use <code>SeamWebApplication</code> as the base class; this creates hooks into the Wicket lifecycle allowing Seam to automagically propagate the conversation as needed. It also adds status messages to the page."
+msgstr "Un'applicazione web Wicket che usa Seam deve usare <code>SeamWebApplication</code> come classe base. Questa crea gli agganci nel ciclo Wicket che consentono a Seam di propagare auto-magicamente la conversazione quando necessario. Aggiunge pure i messaggi di stato alla pagina."
#. Tag: para
#: Wicket.xml:215
#, no-c-format
-msgid ""
-"The <code>SeamAuthorizationStrategy</code> delegates authorization to Seam "
-"Security, allowing the use of <code>@Restrict</code> on Wicket components. "
-"<code>SeamWebApplication</code> installs the authorization strategy for you. "
-"You can specify the login page by implementing the <code>getLoginPage()</"
-"code> method."
-msgstr ""
+msgid "The <code>SeamAuthorizationStrategy</code> delegates authorization to Seam Security, allowing the use of <code>@Restrict</code> on Wicket components. <code>SeamWebApplication</code> installs the authorization strategy for you. You can specify the login page by implementing the <code>getLoginPage()</code> method."
+msgstr "La <code>SeamAuthorizationStrategy</code> delega le autorizzazioni a Seam Security, consentendo l'uso di <code>@Restrict</code> nei componenti Wicket. <code>SeamWebApplication</code> provvede ad installare la strategia di autorizzazioni. E' possibile specificare una pagina di login implementando il metodo <code>getLoginPage()</code>."
#. Tag: para
#: Wicket.xml:223
#, no-c-format
-msgid ""
-"You'll also need to set the home page of the application by implementing the "
-"<code>getHomePage()</code> method."
-msgstr ""
+msgid "You'll also need to set the home page of the application by implementing the <code>getHomePage()</code> method."
+msgstr "C'è poi bisogno di impostare la home page dell'applicazione implementando il metodo <code>getHomePage()</code>."
#. Tag: programlisting
#: Wicket.xml:228
@@ -371,15 +332,26 @@
"}\n"
"]]>"
msgstr ""
+"<![CDATA[public class WicketBookingApplication extends SeamWebApplication {\n"
+"\n"
+" @Override\n"
+" public Class getHomePage() {\n"
+" return Home.class;\n"
+" }\n"
+"\n"
+" @Override\n"
+" protected Class getLoginPage() {\n"
+" return Home.class;\n"
+" }\n"
+" \n"
+"}\n"
+"]]>"
#. Tag: para
#: Wicket.xml:230
#, no-c-format
-msgid ""
-"Seam automatically installs the Wicket filter for you (ensuring that it is "
-"inserted in the correct place for you). But you still need to tell Wicket "
-"which <code>WebApplication</code> class to use:"
-msgstr ""
+msgid "Seam automatically installs the Wicket filter for you (ensuring that it is inserted in the correct place for you). But you still need to tell Wicket which <code>WebApplication</code> class to use:"
+msgstr "Seam installa automaticamente il filtro Wicket (assicurando che sia inserito nella posizione corretta), ma è ancora necessario dire a Wicket quale classe <code>WebApplication</code> usare:"
#. Tag: programlisting
#: Wicket.xml:236
@@ -388,15 +360,18 @@
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
" xmlns:wicket=\"http://jboss.com/products/seam/wicket\">\n"
" \n"
-" <wicket:web-application application-class=\"org.jboss.seam.example.wicket."
-"WicketBookingApplication\" />\n"
+" <wicket:web-application application-class=\"org.jboss.seam.example.wicket.WicketBookingApplication\" />\n"
"</components]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:wicket=\"http://jboss.com/products/seam/wicket\">\n"
+" \n"
+" <wicket:web-application application-class=\"org.jboss.seam.example.wicket.WicketBookingApplication\" />\n"
+"</components]]>"
#. Tag: para
#: Wicket.xml:239
#, no-c-format
-msgid ""
-"Take a look at the Wicket documentation for more on authorization strategies "
-"and other methods you can override on the <code>Application</code> class."
-msgstr ""
+msgid "Take a look at the Wicket documentation for more on authorization strategies and other methods you can override on the <code>Application</code> class."
+msgstr "Per maggiori informazioni sulle strategie di autorizzazione e gli altri metodi che possono essere implementati sulla classe <code>Application</code> fare riferimento alla documentazione Wicket."
+
16 years
- 1
- 0
Seam SVN: r9838 - trunk/examples/dvdstore/resources.
by seam-commits＠lists.jboss.org
Author: norman.richards(a)jboss.com
Date: 2008-12-23 19:03:02 -0500 (Tue, 23 Dec 2008)
New Revision: 9838
Modified:
trunk/examples/dvdstore/resources/ordermanagement2.jpdl.xml
trunk/examples/dvdstore/resources/ordermanagement3.jpdl.xml
Log:
JBSEAM-3266
Modified: trunk/examples/dvdstore/resources/ordermanagement2.jpdl.xml
===================================================================
--- trunk/examples/dvdstore/resources/ordermanagement2.jpdl.xml 2008-12-23 23:35:30 UTC (rev 9837)
+++ trunk/examples/dvdstore/resources/ordermanagement2.jpdl.xml 2008-12-24 00:03:02 UTC (rev 9838)
@@ -32,6 +32,7 @@
<transition name="shipped" to="complete">
<action expression="#{afterShipping.log}"/>
</transition>
+ <transition name="cancel" to="cancelled"/>
</task-node>
<end-state name="complete"/>
Modified: trunk/examples/dvdstore/resources/ordermanagement3.jpdl.xml
===================================================================
--- trunk/examples/dvdstore/resources/ordermanagement3.jpdl.xml 2008-12-23 23:35:30 UTC (rev 9837)
+++ trunk/examples/dvdstore/resources/ordermanagement3.jpdl.xml 2008-12-24 00:03:02 UTC (rev 9838)
@@ -32,6 +32,7 @@
<transition name="shipped" to="complete">
<action expression="#{afterShipping.log}"/>
</transition>
+ <transition name="cancel" to="cancelled"/>
</task-node>
<end-state name="complete"/>
16 years
- 1
- 0
Seam SVN: r9837 - trunk/doc/Seam_Reference_Guide/en-US.
by seam-commits＠lists.jboss.org
Author: norman.richards(a)jboss.com
Date: 2008-12-23 18:35:30 -0500 (Tue, 23 Dec 2008)
New Revision: 9837
Modified:
trunk/doc/Seam_Reference_Guide/en-US/Glassfish.xml
Log:
JBSEAM-3755
Modified: trunk/doc/Seam_Reference_Guide/en-US/Glassfish.xml
===================================================================
--- trunk/doc/Seam_Reference_Guide/en-US/Glassfish.xml 2008-12-23 20:30:44 UTC (rev 9836)
+++ trunk/doc/Seam_Reference_Guide/en-US/Glassfish.xml 2008-12-23 23:35:30 UTC (rev 9837)
@@ -257,7 +257,7 @@
In order for the app to work out of the box with GlassFish, we have
used the Derby (aka JavaDB) database in GlassFish. However, we
strongly recommend that you use another database (e.g. HSQL).
- <literal>examples/jpa/resources-glassfish/WEB-INF/classes/GlassFishDerbyDialect.class</literal>
+ <literal>examples/jpa/resources-glassfish/WEB-INF/classes/GlassfishDerbyDialect.class</literal>
is a hack to get around a Derby bug in GlassFish server. You must
use it as your Hibernate dialect if you use Derby with GlassFish.
</note>
@@ -278,14 +278,14 @@
changes needed are the datasource JNDI, switching to the
GlassFish transaction manager lookup class, and
changing the hibernate dialect to be
- <literal>GlassFishDerbyDialect</literal>.
+ <literal>GlassfishDerbyDialect</literal>.
</para>
</listitem>
<listitem>
<para>
- <literal>WEB-INF/classes/GlassFishDerbyDialect.class</literal>
+ <literal>WEB-INF/classes/GlassfishDerbyDialect.class</literal>
— this class is needed for the Hibernate dialect change
- to <literal>GlassFishDerbyDialect</literal>
+ to <literal>GlassfishDerbyDialect</literal>
</para>
</listitem>
<listitem>
@@ -439,7 +439,7 @@
The key differences are briefly described in
<xref linkend="glassfish_jpa_diff" />:
</para>
- <programlisting role="XML"><![CDATA[<property name="hibernate.dialect" value="GlassFishDerbyDialect"/>
+ <programlisting role="XML"><![CDATA[<property name="hibernate.dialect" value="GlassfishDerbyDialect"/>
<property name="hibernate.hbm2ddl.auto" value="update"/>
<property name="hibernate.show_sql" value="true"/>
<property name="hibernate.format_sql" value="true"/>
@@ -459,7 +459,7 @@
</varlistentry>
<varlistentry>
<term>
- <literal>resources/GlassFishDerbyDialect.class</literal>
+ <literal>resources/GlassfishDerbyDialect.class</literal>
</term>
<listitem>
<para>
@@ -469,7 +469,7 @@
<literal>seamgen_example/resources</literal> directory.
</para>
<programlisting>$ cp \
-$SEAM_DIST/examples/jpa/resources-glassfish/WEB-INF/classes/GlassFishDerbyDialect.class \
+$SEAM_DIST/examples/jpa/resources-glassfish/WEB-INF/classes/GlassfishDerbyDialect.class \
./resources
</programlisting>
</listitem>
@@ -651,9 +651,9 @@
</listitem>
<listitem>
<para>
- We need to get the <literal>GlassFishDerbyDialect.class</literal>
+ We need to get the <literal>GlassfishDerbyDialect.class</literal>
into our application jar. To do that find the <literal>jar</literal>
- task and add the <literal>GlassFishDerbyDialect.class</literal>
+ task and add the <literal>GlassfishDerbyDialect.class</literal>
line as shown below:
</para>
@@ -662,7 +662,7 @@
<fileset dir="${basedir}/resources">
<include name="seam.properties" />
<include name="*.drl" />
- <include name="GlassFishDerbyDialect.class" />
+ <include name="GlassfishDerbyDialect.class" />
</fileset>
</copy>
...]]></programlisting>
16 years
- 1
- 0
Seam SVN: r9836 - trunk/src/main/org/jboss/seam/security/openid.
by seam-commits＠lists.jboss.org
Author: norman.richards(a)jboss.com
Date: 2008-12-23 15:30:44 -0500 (Tue, 23 Dec 2008)
New Revision: 9836
Modified:
trunk/src/main/org/jboss/seam/security/openid/OpenId.java
trunk/src/main/org/jboss/seam/security/openid/OpenIdPhaseListener.java
Log:
fix logging
Modified: trunk/src/main/org/jboss/seam/security/openid/OpenId.java
===================================================================
--- trunk/src/main/org/jboss/seam/security/openid/OpenId.java 2008-12-23 20:00:11 UTC (rev 9835)
+++ trunk/src/main/org/jboss/seam/security/openid/OpenId.java 2008-12-23 20:30:44 UTC (rev 9836)
@@ -8,6 +8,8 @@
import javax.faces.context.FacesContext;
import javax.servlet.http.HttpServletRequest;
+import org.jboss.seam.log.*;
+
import org.jboss.seam.ScopeType;
import org.jboss.seam.annotations.Create;
import org.jboss.seam.annotations.Install;
@@ -35,6 +37,8 @@
public class OpenId
implements Serializable
{
+ private transient LogProvider log = Logging.getLogProvider(OpenId.class);
+
String id;
String validatedId;
@@ -113,7 +117,7 @@
return authReq.getDestinationUrl(true);
} catch (OpenIDException e) {
- e.printStackTrace();
+ log.error(e);
}
return null;
@@ -172,14 +176,12 @@
AuthSuccess authSuccess =
(AuthSuccess) verification.getAuthResponse();
- System.out.println("*** EXT: " + authSuccess.getExtensions());
if (authSuccess.hasExtension(AxMessage.OPENID_NS_AX)) {
FetchResponse fetchResp = (FetchResponse) authSuccess
.getExtension(AxMessage.OPENID_NS_AX);
List emails = fetchResp.getAttributeValues("email");
String email = (String) emails.get(0);
- System.out.println("XXX email is " + email);
}
return verified.getIdentifier();
Modified: trunk/src/main/org/jboss/seam/security/openid/OpenIdPhaseListener.java
===================================================================
--- trunk/src/main/org/jboss/seam/security/openid/OpenIdPhaseListener.java 2008-12-23 20:00:11 UTC (rev 9835)
+++ trunk/src/main/org/jboss/seam/security/openid/OpenIdPhaseListener.java 2008-12-23 20:30:44 UTC (rev 9836)
@@ -13,11 +13,13 @@
import org.jboss.seam.Component;
import org.jboss.seam.navigation.Pages;
+import org.jboss.seam.log.*;
@SuppressWarnings("serial")
public class OpenIdPhaseListener
implements PhaseListener
{
+ private transient LogProvider log = Logging.getLogProvider(OpenIdPhaseListener.class);
@SuppressWarnings("unchecked")
public void beforePhase(PhaseEvent event)
@@ -33,8 +35,7 @@
try {
sendXRDS();
} catch (IOException e) {
- // TODO Auto-generated catch block
- e.printStackTrace();
+ log.error(e);
}
return;
}
16 years
- 1
- 0
Seam SVN: r9835 - trunk/examples/itext/view.
by seam-commits＠lists.jboss.org
Author: norman.richards(a)jboss.com
Date: 2008-12-23 15:00:11 -0500 (Tue, 23 Dec 2008)
New Revision: 9835
Modified:
trunk/examples/itext/view/index.xhtml
Log:
JBSEAM-3733
Modified: trunk/examples/itext/view/index.xhtml
===================================================================
--- trunk/examples/itext/view/index.xhtml 2008-12-23 19:46:52 UTC (rev 9834)
+++ trunk/examples/itext/view/index.xhtml 2008-12-23 20:00:11 UTC (rev 9835)
@@ -34,8 +34,6 @@
<li><s:link view="/table.xhtml" value="Tables" /></li>
<li><s:link view="/nested.xhtml" value="Nested Tables" /></li>
<li><s:link view="/html.xhtml" value="HTML Conversion" /></li>
- <li><s:link view="/swing.xhtml" value="Swing Component" /></li>
-
<li><s:link view="/chart.xhtml" value="JFreeChart" />
[<s:link view="/chartimage.xhtml" value="HTML" />]
</li>
16 years
- 1
- 0
Seam SVN: r9834 - in trunk/examples/itext: view and 1 other directory.
by seam-commits＠lists.jboss.org
Author: norman.richards(a)jboss.com
Date: 2008-12-23 14:46:52 -0500 (Tue, 23 Dec 2008)
New Revision: 9834
Modified:
trunk/examples/itext/src/org/jboss/seam/example/pdf/FillInForms.java
trunk/examples/itext/view/form.xhtml
Log:
JBSEAM-3808
Modified: trunk/examples/itext/src/org/jboss/seam/example/pdf/FillInForms.java
===================================================================
--- trunk/examples/itext/src/org/jboss/seam/example/pdf/FillInForms.java 2008-12-23 19:46:35 UTC (rev 9833)
+++ trunk/examples/itext/src/org/jboss/seam/example/pdf/FillInForms.java 2008-12-23 19:46:52 UTC (rev 9834)
@@ -11,134 +11,133 @@
import org.jboss.seam.annotations.Scope;
@Name("fillInForms")
-(a)Scope(ScopeType.SESSION)
+(a)Scope(ScopeType.CONVERSATION)
public class FillInForms {
- private String name;
- private String address;
- private String postalCode;
- private String email;
- private String[] programming;
- private String language;
- private String preferred;
- private List<String> knowledge;
- private List<SelectItem> programmingLanguages;
- private List<SelectItem> languages;
-
-
- public List<String> getKnowledge() {
- return knowledge;
- }
+ private String name;
+ private String address;
+ private String postalCode;
+ private String email;
+ private String[] programming;
+ private String language;
+ private String preferred;
+ private List<String> knowledge;
+ private List<SelectItem> programmingLanguages;
+ private List<SelectItem> languages;
+
+
+ public List<String> getKnowledge() {
+ return knowledge;
+ }
+
+ public void setKnowledge(List<String> knowledge) {
+ this.knowledge = knowledge;
+ }
+
+
+ public List<SelectItem> getLanguages() {
+ return languages;
+ }
+
+ public void setLanguages(List<SelectItem> languages) {
+ this.languages = languages;
+ }
+
+ public List<SelectItem> getProgrammingLanguages() {
+ return programmingLanguages;
+ }
+
+ public void setProgrammingLanguages(List<SelectItem> programmingLanguages) {
+ this.programmingLanguages = programmingLanguages;
+ }
+
+ @Create
+ public void init() {
+ knowledge = new ArrayList<String>();
+ programmingLanguages = new ArrayList<SelectItem>();
+ programmingLanguages.add(new SelectItem("JAVA", "Java"));
+ programmingLanguages.add(new SelectItem("C", "C/C++"));
+ programmingLanguages.add(new SelectItem("CS", "C#"));
+ programmingLanguages.add(new SelectItem("VB", "VB"));
+ languages = new ArrayList<SelectItem>();
+ languages.add(new SelectItem("EN", "English"));
+ languages.add(new SelectItem("FR", "French"));
+ languages.add(new SelectItem("NL", "Dutch"));
+ knowledge.add("FR");
+ language = "FR";
+ preferred = "FR";
+ }
+
+ public String getName() {
+ return name;
+ }
+
+ public void setName(String name) {
+ this.name = name;
+ }
+
+ public String getAddress() {
+ return address;
+ }
+
+ public void setAddress(String address) {
+ this.address = address;
+ }
+
+ public String getPostalCode() {
+ return postalCode;
+ }
+
+ public void setPostalCode(String postalCode) {
+ this.postalCode = postalCode;
+ }
+
+ public String getEmail() {
+ return email;
+ }
+
+ public void setEmail(String email) {
+ this.email = email;
+ }
+
+ public String[] getProgramming() {
+ return programming;
+ }
- public void setKnowledge(List<String> knowledge) {
- this.knowledge = knowledge;
- }
-
-
- public List<SelectItem> getLanguages() {
- return languages;
- }
-
- public void setLanguages(List<SelectItem> languages) {
- this.languages = languages;
- }
-
- public List<SelectItem> getProgrammingLanguages() {
- return programmingLanguages;
- }
-
- public void setProgrammingLanguages(List<SelectItem> programmingLanguages) {
- this.programmingLanguages = programmingLanguages;
- }
-
- @Create
- public void init() {
- knowledge = new ArrayList<String>();
- programmingLanguages = new ArrayList<SelectItem>();
- programmingLanguages.add(new SelectItem("JAVA", "Java"));
- programmingLanguages.add(new SelectItem("C", "C/C++"));
- programmingLanguages.add(new SelectItem("CS", "C#"));
- programmingLanguages.add(new SelectItem("VB", "VB"));
- languages = new ArrayList<SelectItem>();
- languages.add(new SelectItem("EN", "English"));
- languages.add(new SelectItem("FR", "French"));
- languages.add(new SelectItem("NL", "Dutch"));
- knowledge.add("FR");
- language = "FR";
- preferred = "FR";
- }
-
- public String getName() {
- return name;
- }
-
- public void setName(String name) {
- this.name = name;
- }
-
- public String getAddress() {
- return address;
- }
-
- public void setAddress(String address) {
- this.address = address;
- }
-
- public String getPostalCode() {
- return postalCode;
- }
-
- public void setPostalCode(String postalCode) {
- this.postalCode = postalCode;
- }
-
- public String getEmail() {
- return email;
- }
-
- public void setEmail(String email) {
- this.email = email;
- }
-
- public String[] getProgramming() {
- return programming;
- }
-
- public void setProgramming(String[] programming) {
- this.programming = programming;
- }
-
- public String getLanguage() {
- return language;
- }
-
- public void setLanguage(String language) {
- this.language = language;
- }
-
- public String getPreferred() {
- return preferred;
- }
-
- public void setPreferred(String preferred) {
- this.preferred = preferred;
- }
-
- public String submit() {
- return "/form.xhtml";
- }
-
- public boolean isKnowsEnglish() {
- boolean knows = knowledge.contains("EN");
- System.out.println("Retuning " + knows);
- return knows;
- }
-
- public boolean isKnowsFrench() {
- return knowledge.contains("FR");
- }
-
- public boolean isKnowsDutch() {
- return knowledge.contains("NL");
- }
-
+ public void setProgramming(String[] programming) {
+ this.programming = programming;
+ }
+
+ public String getLanguage() {
+ return language;
+ }
+
+ public void setLanguage(String language) {
+ this.language = language;
+ }
+
+ public String getPreferred() {
+ return preferred;
+ }
+
+ public void setPreferred(String preferred) {
+ this.preferred = preferred;
+ }
+
+ public String submit() {
+ return "/form.xhtml";
+ }
+
+ public boolean isKnowsEnglish() {
+ boolean knows = knowledge.contains("EN");
+ return knows;
+ }
+
+ public boolean isKnowsFrench() {
+ return knowledge.contains("FR");
+ }
+
+ public boolean isKnowsDutch() {
+ return knowledge.contains("NL");
+ }
+
}
Modified: trunk/examples/itext/view/form.xhtml
===================================================================
--- trunk/examples/itext/view/form.xhtml 2008-12-23 19:46:35 UTC (rev 9833)
+++ trunk/examples/itext/view/form.xhtml 2008-12-23 19:46:52 UTC (rev 9834)
@@ -1,6 +1,6 @@
<p:form
xmlns:p="http://jboss.com/products/seam/pdf"
- URL="form.pdf">
+ URL="/form.pdf">
<p:field name="person.name" value="#{fillInForms.name}"/>
<p:field name="person.address" value="#{fillInForms.address}"/>
<p:field name="person.postal_code" value="#{fillInForms.postalCode}"/>
16 years
- 1
- 0
Seam SVN: r9833 - trunk/src/pdf/org/jboss/seam/pdf/ui.
by seam-commits＠lists.jboss.org
Author: norman.richards(a)jboss.com
Date: 2008-12-23 14:46:35 -0500 (Tue, 23 Dec 2008)
New Revision: 9833
Modified:
trunk/src/pdf/org/jboss/seam/pdf/ui/UIField.java
trunk/src/pdf/org/jboss/seam/pdf/ui/UIForm.java
Log:
JBSEAM-3808
Modified: trunk/src/pdf/org/jboss/seam/pdf/ui/UIField.java
===================================================================
--- trunk/src/pdf/org/jboss/seam/pdf/ui/UIField.java 2008-12-23 15:45:36 UTC (rev 9832)
+++ trunk/src/pdf/org/jboss/seam/pdf/ui/UIField.java 2008-12-23 19:46:35 UTC (rev 9833)
@@ -42,7 +42,12 @@
if (theValue instanceof String) {
success = fields.setField(theName, (String) theValue);
} else if (theValue instanceof String[]){
- success = fields.setField(theName, ((String[])theValue)[0]);
+ String[] stringValue = (String[])theValue;
+ if (stringValue.length>0) {
+ success = fields.setField(theName, stringValue[0]);
+ } else {
+ success = true;
+ }
} else {
String message = Interpolator.instance().interpolate("Field #0 expected String or String[] but got #0", getName(), theValue.getClass().getName());
throw new IllegalArgumentException(message);
Modified: trunk/src/pdf/org/jboss/seam/pdf/ui/UIForm.java
===================================================================
--- trunk/src/pdf/org/jboss/seam/pdf/ui/UIForm.java 2008-12-23 15:45:36 UTC (rev 9832)
+++ trunk/src/pdf/org/jboss/seam/pdf/ui/UIForm.java 2008-12-23 19:46:35 UTC (rev 9833)
@@ -17,6 +17,7 @@
import org.jboss.seam.log.Log;
import org.jboss.seam.log.Logging;
import org.jboss.seam.navigation.Pages;
+import org.jboss.seam.core.ResourceLoader;
import com.lowagie.text.DocumentException;
import com.lowagie.text.pdf.AcroFields;
@@ -47,13 +48,12 @@
@Override
public void encodeBegin(FacesContext facesContext) throws IOException {
+ log.info("Loading template #0", getURL());
if (getURL().indexOf("://") < 0) {
- reader = new PdfReader(getClass().getClassLoader()
- .getResourceAsStream(getURL()));
+ reader = new PdfReader(ResourceLoader.instance().getResourceAsStream(getURL()));
} else {
reader = new PdfReader(new URL(getURL()));
}
- log.debug("Loading template #0", getURL());
buffer = new ByteArrayOutputStream();
try {
stamper = new PdfStamper(reader, buffer);
16 years
- 1
- 0
Seam SVN: r9832 - in trunk/seam-gen: icefaces/build-scripts and 1 other directory.
by seam-commits＠lists.jboss.org
Author: dan.j.allen
Date: 2008-12-23 10:45:36 -0500 (Tue, 23 Dec 2008)
New Revision: 9832
Modified:
trunk/seam-gen/build-scripts/build-war.xml
trunk/seam-gen/build-scripts/build.xml
trunk/seam-gen/icefaces/build-scripts/build-war.xml
trunk/seam-gen/icefaces/build-scripts/build.xml
Log:
JBSEAM-3866
Modified: trunk/seam-gen/build-scripts/build-war.xml
===================================================================
--- trunk/seam-gen/build-scripts/build-war.xml 2008-12-23 15:36:20 UTC (rev 9831)
+++ trunk/seam-gen/build-scripts/build-war.xml 2008-12-23 15:45:36 UTC (rev 9832)
@@ -254,8 +254,7 @@
<target name="datasource">
<fail unless="jboss.home">jboss.home not set</fail>
<copy file="${basedir}/resources/${project.name}-${profile}-ds.xml"
- tofile="${deploy.dir}/${project.name}-ds.xml"
- overwrite="true"/>
+ tofile="${deploy.dir}/${project.name}-ds.xml"/>
</target>
<target name="explode" depends="stage,datasource"
Modified: trunk/seam-gen/build-scripts/build.xml
===================================================================
--- trunk/seam-gen/build-scripts/build.xml 2008-12-23 15:36:20 UTC (rev 9831)
+++ trunk/seam-gen/build-scripts/build.xml 2008-12-23 15:45:36 UTC (rev 9832)
@@ -255,8 +255,7 @@
<target name="datasource">
<fail unless="jboss.home">jboss.home not set</fail>
<copy file="${basedir}/resources/${project.name}-${profile}-ds.xml"
- tofile="${deploy.dir}/${project.name}-ds.xml"
- overwrite="true"/>
+ tofile="${deploy.dir}/${project.name}-ds.xml"/>
</target>
<target name="explode" depends="stage,datasource"
Modified: trunk/seam-gen/icefaces/build-scripts/build-war.xml
===================================================================
--- trunk/seam-gen/icefaces/build-scripts/build-war.xml 2008-12-23 15:36:20 UTC (rev 9831)
+++ trunk/seam-gen/icefaces/build-scripts/build-war.xml 2008-12-23 15:45:36 UTC (rev 9832)
@@ -243,8 +243,7 @@
<target name="datasource">
<fail unless="jboss.home">jboss.home not set</fail>
<copy file="${basedir}/resources/${project.name}-${profile}-ds.xml"
- tofile="${deploy.dir}/${project.name}-ds.xml"
- overwrite="true"/>
+ tofile="${deploy.dir}/${project.name}-ds.xml"/>
</target>
<target name="explode" depends="stage,datasource"
Modified: trunk/seam-gen/icefaces/build-scripts/build.xml
===================================================================
--- trunk/seam-gen/icefaces/build-scripts/build.xml 2008-12-23 15:36:20 UTC (rev 9831)
+++ trunk/seam-gen/icefaces/build-scripts/build.xml 2008-12-23 15:45:36 UTC (rev 9832)
@@ -245,8 +245,7 @@
<target name="datasource">
<fail unless="jboss.home">jboss.home not set</fail>
<copy file="${basedir}/resources/${project.name}-${profile}-ds.xml"
- tofile="${deploy.dir}/${project.name}-ds.xml"
- overwrite="true"/>
+ tofile="${deploy.dir}/${project.name}-ds.xml"/>
</target>
<target name="explode" depends="stage,datasource"
16 years
- 1
- 0