Author: nico.ben Date: 2009-03-22 08:58:06 -0400 (Sun, 22 Mar 2009) New Revision: 10199 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Webservices.po Log: JBSEAM-3767: Italian translation of Seam guide Modified: trunk/doc/Seam_Reference_Guide/it-IT/Webservices.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Webservices.po 2009-03-22 12:44:10 UTC (rev 10198) +++ trunk/doc/Seam_Reference_Guide/it-IT/Webservices.po 2009-03-22 12:58:06 UTC (rev 10199) @@ -5,8 +5,8 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-03-17 20:35+0000\n" -"PO-Revision-Date: 2009-03-17 21:42+0100\n" +"POT-Creation-Date: 2009-03-22 12:51+0000\n" +"PO-Revision-Date: 2009-03-22 13:57+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -642,7 +642,7 @@ #. Tag: title #: Webservices.xml:324 #, no-c-format -msgid "Mapping exceptions to HTTP response status codes" +msgid "Mapping exceptions to HTTP responses" msgstr "" #. Tag: para @@ -654,13 +654,34 @@ #. Tag: para #: Webservices.xml:334 #, no-c-format -msgid "For example, to convert the unchecked <literal>UnsupportedOperationException</literal> thrown by your resource methods to a <literal>501 Not Implemented</literal> HTTP status response, add the following to your <literal>pages.xml</literal> descriptor:" +msgid "Exception handling within Seam requires that the Seam filter is executed for your HTTP request. Ensure that you do filter <emphasis>all</emphasis> requests in your <literal>web.xml</literal>, not - as some Seam examples might show - a request URI pattern that doesn't cover your REST requests. The following example intercepts <emphasis>all</emphasis> HTTP requests and enables Seam exception handling:" msgstr "" #. Tag: programlisting -#: Webservices.xml:340 +#: Webservices.xml:341 #, no-c-format msgid "" +"<![CDATA[<filter>\n" +" <filter-name>Seam Filter</filter-name>\n" +" <filter-class>org.jboss.seam.servlet.SeamFilter</filter-class>\n" +"</filter>\n" +"\n" +"<filter-mapping>\n" +" <filter-name>Seam Filter</filter-name>\n" +" <url-pattern>/*</url-pattern>\n" +"</filter-mapping>]]>" +msgstr "" + +#. Tag: para +#: Webservices.xml:343 +#, no-c-format +msgid "To convert the unchecked <literal>UnsupportedOperationException</literal> thrown by your resource methods to a <literal>501 Not Implemented</literal> HTTP status response, add the following to your <literal>pages.xml</literal> descriptor:" +msgstr "" + +#. Tag: programlisting +#: Webservices.xml:349 +#, no-c-format +msgid "" "<![CDATA[<exception class=\"java.lang.UnsupportedOperationException\">\n" " <http-error error-code=\"501\">\n" " <message>The request operation is not supported</message>\n" @@ -674,35 +695,35 @@ "</exception>]]>" #. Tag: para -#: Webservices.xml:342 +#: Webservices.xml:351 #, no-c-format msgid "Custom or checked exceptions are handled the same:" msgstr "" #. Tag: programlisting -#: Webservices.xml:346 +#: Webservices.xml:355 #, no-c-format msgid "" -"<![CDATA[<exception class=\"my.CustomException\">\n" +"<![CDATA[<exception class=\"my.CustomException\" log=\"false\">\n" " <http-error error-code=\"503\">\n" -" <message>The service is currently not available</message>\n" +" <message>The service is currently not available: #{org.jboss.seam.handledException.message}</message>\n" " </http-error>\n" "</exception>]]>" msgstr "" -"<![CDATA[<exception class=\"my.CustomException\">\n" +"<![CDATA[<exception class=\"my.CustomException\" log=\"false\">\n" " <http-error error-code=\"503\">\n" -" <message>The service is currently not available</message>\n" +" <message>The service is currently not available: #{org.jboss.seam.handledException.message}</message>\n" " </http-error>\n" "</exception>]]>" #. Tag: para -#: Webservices.xml:348 +#: Webservices.xml:357 #, no-c-format msgid "You do not have to send an HTTP error to the client if an exception occurs. Seam allows you to map the exception as a redirect to a view of your Seam application. As this feature is typically used for human clients (web browsers) and not for REST API remote clients, you should pay extra attention to conflicting exception mappings in <literal>pages.xml</literal>." msgstr "" #. Tag: para -#: Webservices.xml:355 +#: Webservices.xml:364 #, no-c-format msgid "Note that the HTTP response still passes through the servlet container, so an additional mapping might apply if you have <literal>&lt;error-page&gt;</literal> mappings in your <literal>web.xml</literal> configuration. The HTTP status code would then be mapped to a rendered HTML error page with status <literal>200 OK</literal>!" msgstr ""