[jboss-cvs] JBossAS SVN: r89586 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Jun 1 02:59:01 EDT 2009
Author: ldelima at redhat.com
Date: 2009-06-01 02:59:01 -0400 (Mon, 01 Jun 2009)
New Revision: 89586
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/J2EE_Additional_Services.po
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/Web_Services.po
Log:
translation ongoing
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/J2EE_Additional_Services.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/J2EE_Additional_Services.po 2009-06-01 06:06:38 UTC (rev 89585)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/J2EE_Additional_Services.po 2009-06-01 06:59:01 UTC (rev 89586)
@@ -9,7 +9,7 @@
"Project-Id-Version: J2EE_Additional_Services\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-05-29 14:47+1000\n"
+"PO-Revision-Date: 2009-06-01 16:58+1000\n"
"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
"Language-Team: Brazilian Portuguese <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -180,7 +180,7 @@
"between checks for changes in the log4 configuration specified by the "
"<literal>ConfigurationURL</literal> attribute. The default value is 60 "
"seconds."
-msgstr ""
+msgstr "<emphasis role=\"bold\">RefreshPeriod</emphasis>: O período em segundos entre checagens para alterações na configuração log4 especificada pelo atributo <literal>ConfigurationURL</literal>. O valor padrão é 60 segundos."
#. Tag: para
#: J2EE_Additional_Services.xml:89
@@ -219,6 +219,8 @@
"literal>. As of log4j1.2.8 this needs to be set to avoid a possible deadlock "
"on exception at the appender level. See bug#696819."
msgstr ""
+"<emphasis role=\"bold\">Log4jQuietMode</emphasis>: caso este aviso booleano seja verdadeiro, ele configurará o <literal>org.apache.log4j.helpers.LogLog.setQuiteMode</"
+"literal>. Conforme a partir do log4j1.2.8 isto precisa ser configurado para evitar um congelamento na exceção de nível appender. Consulte o bug#696819."
#. Tag: title
#: J2EE_Additional_Services.xml:107
@@ -417,7 +419,7 @@
#: J2EE_Additional_Services.xml:161
#, no-c-format
msgid "Services Binding Management"
-msgstr ""
+msgstr "Gerenciamento Binding de Serviços"
#. Tag: para
#: J2EE_Additional_Services.xml:162
@@ -464,6 +466,8 @@
"literal> instance to load the server configuration sets from. For the XML "
"store, this is a simple service binding file."
msgstr ""
+"<emphasis role=\"bold\">StoreURL</emphasis>: Este é o URL dos conteúdos do armazenamento da configuração que é passado à instância <literal>ServicesStore</"
+"literal> para carregar os conjuntos de configuração do servidor. A partir do armazenamento XML, este é um arquivo de binding de serviço simples."
#. Tag: para
#: J2EE_Additional_Services.xml:182
@@ -473,6 +477,8 @@
"the <literal>ports-01</literal> configuration from the <literal>sample-"
"bindings.xml</literal> file provided in the JBoss examples directory."
msgstr ""
+"Segue abaixo uma configuração do gerenciador do binding de serviço que usa a configuração <literal>ports-01</literal> a partir do arquivo <literal>sample-"
+"bindings.xml</literal> fornecido no diretório das amostras do JBoss."
#. Tag: programlisting
#: J2EE_Additional_Services.xml:185
@@ -507,29 +513,28 @@
"The structure of the binding file is shown in <xref linkend="
"\"Services_Binding_Management-The_binding_service_file_structure\"/>."
msgstr ""
+"A estrutura do arquivo binding é apresentado no <xref linkend="
+"\"Services_Binding_Management-The_binding_service_file_structure\"/>."
#. Tag: title
#: J2EE_Additional_Services.xml:190
#, no-c-format
msgid "The binding service file structure"
-msgstr ""
+msgstr "Estrutura do arquivo de serviço binding"
#. Tag: para
#: J2EE_Additional_Services.xml:197
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The elements are:"
-msgstr "O elemento Host"
+msgstr "Os elementos são:"
#. Tag: para
#: J2EE_Additional_Services.xml:202
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"<emphasis role=\"bold\">service-bindings</emphasis>: The root element of the "
"configuration file. It contains one or more server elements."
-msgstr ""
-"<emphasis role=\"bold\">DiscoveryDisabled</emphasis> é um sinalizador "
-"booleano que desabilita a configuração de ouvintes multicast do recurso auto "
-"descoberta."
+msgstr "<emphasis role=\"bold\">service-bindings</emphasis>: O elemento raiz do arquivo de configuração. Ele contém um ou mais elementos do servidor."
#. Tag: para
#: J2EE_Additional_Services.xml:207
@@ -542,6 +547,8 @@
"literal><literal>ServerName</literal> attribute value. The server element "
"content consists of one or more <literal>service-config</literal> elements."
msgstr ""
+"<emphasis role=\"bold\">server</emphasis>: Este é a base da configuração da instância do servidor do JBoss. Isto possui um atributo <literal>name</literal> solicitado que define o nome da instância do JBoss pelo qual isto é aplicado. Este é o nome que correlaciona o valor do atributo <literal>ServiceBindingManager</"
+"literal><literal>ServerName</literal>. O conteúdo do elemento consiste de um ou mais elementos <literal>service-config</literal>."
#. Tag: para
#: J2EE_Additional_Services.xml:212
@@ -556,7 +563,7 @@
"knows how to handle bindings for the target service. Its contents consists "
"of an optional <literal>delegate-config</literal> element and one or more "
"binding elements."
-msgstr ""
+msgstr "<emphasis role=\"bold\">service-config</emphasis>: Este elemento representa uma substituição da configuração para um serviço MBean. Isto solicita o nome do atributo que é uma seqüência JMX <literal>ObjectName</literal> do serviço MBean que a configuração aplica. Isto também requer o atributo do nome <literal>delegateClass</literal> que especifica o nome da classe da implementação <literal>ServicesConfigDelegate</literal> que sabe como manusear bindings para o serviço alvo. Seu conteúdo consiste num elemento <literal>delegate-config</literal> opcional e um ou mais elementos binding."
#. Tag: para
#: J2EE_Additional_Services.xml:217
@@ -571,6 +578,8 @@
"specified it defaults to 0 meaning choose an anonymous port. If the host is "
"not specified it defaults to null meaning any address."
msgstr ""
+"<emphasis role=\"bold\">binding</emphasis>: O elemento <literal>binding</literal> especifica um portal nomeado e um par de endereços. Ele possui um <literal>name</literal> opcional que pode ser usado para fornecer o bindibg múltiplo para um serviço. Um exemplo pode ser os hospedeiros virtuais múltiplos para um container da web. O portal e o endereço são especificados através dos atributos <literal>port</literal> e "
+"<literal>host</literal> respectivamente. Caso o portal não seja especificado ele padronizará para 0, significando a escolha de um portal anônimo. Caso o hospedeiro não seja especificado ele padronizará para nulo significando qualquer endereço."
#. Tag: para
#: J2EE_Additional_Services.xml:222
@@ -587,6 +596,9 @@
"literal> are arbitrary, but there is no way to specify and a element can "
"have any number of attributes with a DTD."
msgstr ""
+"<emphasis role=\"bold\">delegate-config</emphasis>: O elemento <literal>delegate-"
+"config</literal> é um fragmento XML arbitrário para uso pela implementação <literal>ServicesConfigDelegate</literal>. Os atributos <literal>hostName</literal> e <literal>portName</literal> apenas aplicam ao <literal>AttributeMappingDelegate</literal> do exemplo estarão presentes para previnir os editores cientes do DTD de reclamarem de sua existência nas configurações <literal>AttributeMappingDelegate</literal>. Normalmente, ambos os atributos e conteúdo do <literal>delegate-config</"
+"literal> são arbritários, mas não existe maneira para especificar e um elemento pode possuir qualquer número de atributos com um DTD."
#. Tag: para
#: J2EE_Additional_Services.xml:227
@@ -596,6 +608,8 @@
"<literal>AttributeMappingDelegate</literal>, <literal>XSLTConfigDelegate</"
"literal>, and <literal>XSLTFileDelegate</literal>."
msgstr ""
+"As três implementações de <literal>ServicesConfigDelegate</literal> são <literal>AttributeMappingDelegate</literal>, <literal>XSLTConfigDelegate</"
+"literal> e <literal>XSLTFileDelegate</literal>."
#. Tag: title
#: J2EE_Additional_Services.xml:231
@@ -610,7 +624,7 @@
"The <literal>AttributeMappingDelegate</literal> class is an implementation "
"of the <literal>ServicesConfigDelegate</literal> that expects a "
"<literal>delegate-config</literal> element of the form:"
-msgstr ""
+msgstr "A classe <literal>AttributeMappingDelegate</literal> é uma implementação dos <literal>ServicesConfigDelegate</literal> que espera um elemento<literal>delegate-config</literal> de forma:"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:235
@@ -648,6 +662,9 @@
"<literal>${x}</literal> syntax that is supported by the JBoss services "
"descriptor."
msgstr ""
+"O <literal>portAttrName</literal> é um nome de atributo do serviço MBean pelo qual o valor do portal de binding deve ser aplicado e o <literal>hostAttrName</literal> é o nome do atributo do serviço pelo qual o valor do hospedeiro de binding deve ser aplicadp. Caso o atributo <literal>portName</"
+"literal> não seja especificado o portal do binding não é aplicado. Por outro lado, se o atributo <literal>hostName</literal> não seja especificado, então o hospedeiro binding não será aplicado. O(s) elemento(s) do atributo opcional especificam os nomes do atributo do MBean arbitrário em que os valores são uma função do hospedeiro e/ou configurações do portal. Qualquer referência ao <literal>${host}</literal> no conteúdo do atributo é substituído com o binding do hospedeiro e qualquer referência <literal>${port}"
+"</literal> é substituída com o binding do portal. Os valores do atributo <literal>portName</literal>, <literal>hostName</literal> e conteúdo do elemento do atributo podem referenciar as propriedades do sistema usando a sintaxe <literal>${x}</literal> que é suportada pelo descritor dos serviços do JBoss."
#. Tag: para
#: J2EE_Additional_Services.xml:239
@@ -656,6 +673,8 @@
"The sample listing illustrates the usage of "
"<literal>AttributeMappingDelegate</literal>."
msgstr ""
+"The sample listing illustrates the usage of "
+"<literal>AttributeMappingDelegate</literal>."
#. Tag: programlisting
#: J2EE_Additional_Services.xml:242
@@ -684,6 +703,10 @@
"corresponding setting from the jboss1 server configuration overrides the "
"port to 1199."
msgstr ""
+"Here the <literal>jboss:service=Naming</literal> MBean service has its "
+"<literal>Port</literal> attribute value overridden to 1099. The "
+"corresponding setting from the jboss1 server configuration overrides the "
+"port to 1199."
#. Tag: title
#: J2EE_Additional_Services.xml:249
@@ -699,6 +722,9 @@
"<literal>ServicesConfigDelegate</literal> that expects a <literal>delegate-"
"config</literal> element of the form:"
msgstr ""
+"The <literal>XSLTConfigDelegate</literal> class is an implementation of the "
+"<literal>ServicesConfigDelegate</literal> that expects a <literal>delegate-"
+"config</literal> element of the form:"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:253 J2EE_Additional_Services.xml:268
@@ -736,6 +762,15 @@
"literal>, and their values are set to the configuration host and port "
"bindings."
msgstr ""
+"The <literal>xslt-config</literal> child element content specifies an "
+"arbitrary XSL script fragment that is to be applied to the MBean service "
+"attribute named by the <literal>configName</literal> attribute. The named "
+"attribute must be of type <literal>org.w3c.dom.Element</literal>. The "
+"optional <literal>xslt-param</literal> elements specify XSL script parameter "
+"values for parameters used in the script. There are two XSL parameters "
+"defined by default called <literal>host</literal> and <literal>port</"
+"literal>, and their values are set to the configuration host and port "
+"bindings."
#. Tag: para
#: J2EE_Additional_Services.xml:257
@@ -746,6 +781,10 @@
"nested XML fragment. The following example maps the port number on "
"hypersonic datasource:"
msgstr ""
+"The <literal>XSLTConfigDelegate</literal> is used to transform services "
+"whose <literal>port/interface</literal> configuration is specified using a "
+"nested XML fragment. The following example maps the port number on "
+"hypersonic datasource:"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:260
@@ -847,6 +886,11 @@
"file system. The <literal>delegate-config</literal> takes exactly the same "
"form:"
msgstr ""
+"The <literal>XSLTFileDelegate</literal> class works similarly to the "
+"<literal>XSLTConfigDelegate</literal> except that instead of transforming an "
+"embedded XML fragment, the XSLT script transforms a file read in from the "
+"file system. The <literal>delegate-config</literal> takes exactly the same "
+"form:"
#. Tag: para
#: J2EE_Additional_Services.xml:269
@@ -862,6 +906,15 @@
"<literal>port</literal>, and their values are set to the configuration "
"<literal>host</literal> and <literal>port</literal> bindings."
msgstr ""
+"The <literal>xslt-config</literal> child element content specifies an "
+"arbitrary XSL script fragment that is to be applied to the MBean service "
+"attribute named by the <literal>configName</literal> attribute. The named "
+"attribute must be a String value corresponding to an XML file that will be "
+"transformed. The optional <literal>xslt-param</literal> elements specify XSL "
+"script parameter values for parameters used in the script. There are two XSL "
+"parameters defined by default called <literal>host</literal> and "
+"<literal>port</literal>, and their values are set to the configuration "
+"<literal>host</literal> and <literal>port</literal> bindings."
#. Tag: para
#: J2EE_Additional_Services.xml:272
@@ -870,6 +923,8 @@
"The following example maps the host and port values for the Tomcat "
"connectors:"
msgstr ""
+"The following example maps the host and port values for the Tomcat "
+"connectors:"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:275
@@ -1015,7 +1070,7 @@
#: J2EE_Additional_Services.xml:279
#, no-c-format
msgid "The Sample Bindings File"
-msgstr ""
+msgstr "The Sample Bindings File"
#. Tag: para
#: J2EE_Additional_Services.xml:280
@@ -1028,6 +1083,10 @@
"and <literal>jboss1</literal> by running the following command from the book "
"examples directory:"
msgstr ""
+"JBoss ships with service binding configuration file for starting up to three "
+"separate JBoss instances on one host. Here we will walk through the steps to "
+"bring up the two instances and look at the sample configuration. Start by "
+"making two server configuration file sets called <literal>jboss0</literal> "
#. Tag: programlisting
#: J2EE_Additional_Services.xml:283
@@ -1045,6 +1104,11 @@
"service.xml</literal> descriptor with one that has the "
"<literal>ServiceBindingManager</literal> configuration enabled as follows:"
msgstr ""
+"This creates duplicates of the <literal>server/default</literal> "
+"configuration file sets as <literal>server/jboss0</literal> and "
+"<literal>server/jboss1</literal>, and then replaces the <literal>conf/jboss-"
+"service.xml</literal> descriptor with one that has the "
+"<literal>ServiceBindingManager</literal> configuration enabled as follows:"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:287
@@ -1087,6 +1151,16 @@
"ports, while the <literal>jboss1</literal> configuration adds 100 to each "
"port number."
msgstr ""
+"Here the configuration name is <literal>${jboss.server.name}</literal>. "
+"JBoss will replace that with name of the actual JBoss server configuration "
+"that we pass to the run script with the <literal>-c</literal> option. That "
+"will be either <literal>jboss0</literal> or <literal>jboss1</literal>, "
+"depending on which configuration is being run. The binding manager will find "
+"the corresponding server configuration section from the <literal>misc-ex1-"
+"bindings.xml</literal> and apply the configured overrides. The "
+"<literal>jboss0</literal> configuration uses the default settings for the "
+"ports, while the <literal>jboss1</literal> configuration adds 100 to each "
+"port number."
#. Tag: para
#: J2EE_Additional_Services.xml:291
@@ -1099,12 +1173,18 @@
"out that both instances work correctly, try accessing the web server of the "
"first JBoss on port 8080 and then try the second JBoss instance on port 8180."
msgstr ""
+"To test the sample configuration, start two JBoss instances using the "
+"<literal>jboss0</literal> and <literal>jboss1</literal> configuration file "
+"sets created previously. You can observe that the port numbers in the "
+"console log are different for the <literal>jboss1</literal> server. To test "
+"out that both instances work correctly, try accessing the web server of the "
+"first JBoss on port 8080 and then try the second JBoss instance on port 8180."
#. Tag: title
#: J2EE_Additional_Services.xml:299
#, no-c-format
msgid "RMI Dynamic Class Loading"
-msgstr ""
+msgstr "RMI Dynamic Class Loading"
#. Tag: para
#: J2EE_Additional_Services.xml:300
@@ -1114,6 +1194,9 @@
"RMI access to the server EJBs. The configurable attributes for the service "
"are as follows:"
msgstr ""
+"The <literal>WebService</literal> MBean provides dynamic class loading for "
+"RMI access to the server EJBs. The configurable attributes for the service "
+"are as follows:"
#. Tag: para
#: J2EE_Additional_Services.xml:305
@@ -1122,6 +1205,8 @@
"<emphasis role=\"bold\">Port</emphasis>: the <literal>WebService</literal> "
"listening port number. A port of 0 will use any available port."
msgstr ""
+"<emphasis role=\"bold\">Port</emphasis>: the <literal>WebService</literal> "
+"listening port number. A port of 0 will use any available port."
#. Tag: para
#: J2EE_Additional_Services.xml:310
@@ -1142,6 +1227,10 @@
"host for a <literal>java.net.ServerSocket</literal> that will only accept "
"connect requests to one of its addresses."
msgstr ""
+"<emphasis role=\"bold\">BindAddress</emphasis>: the specific address the "
+"<literal>WebService</literal> listens on. This can be used on a multi-homed "
+"host for a <literal>java.net.ServerSocket</literal> that will only accept "
+"connect requests to one of its addresses."
#. Tag: para
#: J2EE_Additional_Services.xml:320
@@ -1166,6 +1255,9 @@
"if the server should attempt to download classes from thread context class "
"loader when a request arrives that does not have a class loader key prefix."
msgstr ""
+"<emphasis role=\"bold\">DownloadServerClasses</emphasis>: A flag indicating "
+"if the server should attempt to download classes from thread context class "
+"loader when a request arrives that does not have a class loader key prefix."
#. Tag: para
#: J2EE_Additional_Services.xml:330
@@ -1186,12 +1278,15 @@
"threadpool.BasicThreadPoolMBean</literal> instance thread pool used for the "
"class loading."
msgstr ""
+"<emphasis role=\"bold\">ThreadPool</emphasis>: The <literal>org.jboss.util."
+"threadpool.BasicThreadPoolMBean</literal> instance thread pool used for the "
+"class loading."
#. Tag: title
#: J2EE_Additional_Services.xml:343
#, no-c-format
msgid "Scheduling Tasks"
-msgstr ""
+msgstr "Scheduling Tasks"
#. Tag: para
#: J2EE_Additional_Services.xml:344
@@ -1203,6 +1298,11 @@
"time with an optional repeat interval as the <literal>javax.management.timer."
"TimerMBean</literal> agent service."
msgstr ""
+"Java includes a simple timer based capability through the <literal>java.util."
+"Timer</literal> and <literal>java.util.TimerTask</literal> utility classes. "
+"JMX also includes a mechanism for scheduling JMX notifications at a given "
+"time with an optional repeat interval as the <literal>javax.management.timer."
+"TimerMBean</literal> agent service."
#. Tag: para
#: J2EE_Additional_Services.xml:347
@@ -1214,6 +1314,11 @@
"timer service for the basic scheduling. They extend the behavior of the "
"timer service as described in the following sections."
msgstr ""
+"JBoss includes two variations of the JMX timer service in the <literal>org."
+"jboss.varia.scheduler.Scheduler</literal> and <literal>org.jboss.varia."
+"scheduler.ScheduleManager</literal> MBeans. Both MBeans rely on the JMX "
+"timer service for the basic scheduling. They extend the behavior of the "
+"timer service as described in the following sections."
#. Tag: title
#: J2EE_Additional_Services.xml:351
@@ -1229,6 +1334,9 @@
"<literal>Scheduler</literal> directly invokes a callback on an instance of a "
"user defined class, or an operation of a user specified MBean."
msgstr ""
+"The Scheduler differs from the <literal>TimerMBean</literal> in that the "
+"<literal>Scheduler</literal> directly invokes a callback on an instance of a "
+"user defined class, or an operation of a user specified MBean."
#. Tag: para
#: J2EE_Additional_Services.xml:357
@@ -1244,13 +1352,13 @@
#: J2EE_Additional_Services.xml:362
#, no-c-format
msgid "<literal>NOW</literal>: date will be the current time plus 1 seconds"
-msgstr ""
+msgstr "<literal>NOW</literal>: date will be the current time plus 1 seconds"
#. Tag: para
#: J2EE_Additional_Services.xml:367
#, no-c-format
msgid "A number representing the milliseconds since 1/1/1970"
-msgstr ""
+msgstr "A number representing the milliseconds since 1/1/1970"
#. Tag: para
#: J2EE_Additional_Services.xml:372
@@ -1264,6 +1372,13 @@
"start at the next scheduled time. When no start date is available in the "
"future the <literal>Scheduler</literal> will not start."
msgstr ""
+"Date as String able to be parsed by <literal>SimpleDateFormat</literal> with "
+"default format pattern \"<literal>M/d/yy h:mm a</literal>\". If the date is "
+"in the past the <literal>Scheduler</literal> will search a start date in the "
+"future with respect to the initial repetitions and the period between calls. "
+"This means that when you restart the MBean (restarting JBoss etc.) it will "
+"start at the next scheduled time. When no start date is available in the "
+"future the <literal>Scheduler</literal> will not start."
#. Tag: para
#: J2EE_Additional_Services.xml:377
@@ -1273,6 +1388,9 @@
"Noon and you restart your JBoss server then it will start at the next Noon "
"(the same if started before Noon or the next day if start after Noon)."
msgstr ""
+"For example, if you start your <literal>Schedulable</literal> everyday at "
+"Noon and you restart your JBoss server then it will start at the next Noon "
+"(the same if started before Noon or the next day if start after Noon)."
#. Tag: para
#: J2EE_Additional_Services.xml:382
@@ -1282,6 +1400,9 @@
"the scheduler will invoke the target's callback. If -1 then the callback "
"will be repeated until the server is stopped."
msgstr ""
+"<emphasis role=\"bold\">InitialRepetitions</emphasis>: The number of times "
+"the scheduler will invoke the target's callback. If -1 then the callback "
+"will be repeated until the server is stopped."
#. Tag: para
#: J2EE_Additional_Services.xml:387
@@ -1294,6 +1415,12 @@
"<literal>startSchedule</literal> operation must be invoked on the "
"<literal>Scheduler</literal> to begin."
msgstr ""
+"<emphasis role=\"bold\">StartAtStartup</emphasis>: A flag that determines if "
+"the <literal>Scheduler</literal> will start when it receives its "
+"startService life cycle notification. If true the <literal>Scheduler</"
+"literal> starts on its startup. If false, an explicit "
+"<literal>startSchedule</literal> operation must be invoked on the "
+"<literal>Scheduler</literal> to begin."
#. Tag: para
#: J2EE_Additional_Services.xml:392
@@ -1302,6 +1429,8 @@
"<emphasis role=\"bold\">SchedulePeriod</emphasis>: The interval between "
"scheduled calls in milliseconds. This value must be bigger than 0."
msgstr ""
+"<emphasis role=\"bold\">SchedulePeriod</emphasis>: The interval between "
+"scheduled calls in milliseconds. This value must be bigger than 0."
#. Tag: para
#: J2EE_Additional_Services.xml:397
@@ -1314,6 +1443,12 @@
"<literal>SchedulableArgumentTypes</literal> must be populated to correspond "
"to the constructor of the <literal>Schedulable</literal> implementation."
msgstr ""
+"<emphasis role=\"bold\">SchedulableClass</emphasis>: The fully qualified "
+"class name of the <literal>org.jboss.varia.scheduler.Schedulable</literal> "
+"interface implementation that is to be used by the <literal>Scheduler</"
+"literal> . The <literal>SchedulableArguments</literal> and "
+"<literal>SchedulableArgumentTypes</literal> must be populated to correspond "
+"to the constructor of the <literal>Schedulable</literal> implementation."
#. Tag: para
#: J2EE_Additional_Services.xml:402
@@ -1325,6 +1460,11 @@
"classes with a constructor that accepts a <literal>String</literal> as its "
"sole argument are supported."
msgstr ""
+"<emphasis role=\"bold\">SchedulableArguments</emphasis>: A comma separated "
+"list of arguments for the <literal>Schedulable</literal> implementation "
+"class constructor. Only primitive data types, <literal>String</literal> and "
+"classes with a constructor that accepts a <literal>String</literal> as its "
+"sole argument are supported."
#. Tag: para
#: J2EE_Additional_Services.xml:407
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/Web_Services.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/Web_Services.po 2009-06-01 06:06:38 UTC (rev 89585)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/Web_Services.po 2009-06-01 06:59:01 UTC (rev 89586)
@@ -9,7 +9,7 @@
"Project-Id-Version: Web_Services\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-05-29 10:38+1000\n"
+"PO-Revision-Date: 2009-06-01 11:31+1000\n"
"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
"Language-Team: Brazilian Portuguese <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -4073,7 +4073,7 @@
"is packaging of standard JSR-109 deployment archive that includes the event "
"source specific WSDL and points to the JBossWS-Eventing endpoint "
"implementations."
-msgstr "è responsabilidade dos usuários suprir os pontos finais do serviço da web (EventSourceEndpoint, SubscriptionManagerEndpoint) que são solicitados pela implementação da fonte do evento completo. Felizmente, o JBossWS-Eventing já lança a implementação que pode ser usada diretamente. "
+msgstr "É responsabilidade dos usuários suprir os pontos finais do serviço da web (EventSourceEndpoint, SubscriptionManagerEndpoint) que são solicitados pela implementação da fonte do evento completo. Felizmente, o JBossWS-Eventing já lança a implementação que pode ser usada diretamente. "
#. Tag: para
#: Web_Services.xml:1165
More information about the jboss-cvs-commits
mailing list