[jboss-cvs] JBossAS SVN: r85660 - 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 Mar 9 23:29:06 EDT 2009
Author: ldelima at redhat.com
Date: 2009-03-09 23:29:06 -0400 (Mon, 09 Mar 2009)
New Revision: 85660
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/Naming.po
Log:
translation ongoing
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/Naming.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/Naming.po 2009-03-10 03:27:21 UTC (rev 85659)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/Naming.po 2009-03-10 03:29:06 UTC (rev 85660)
@@ -9,7 +9,7 @@
"Project-Id-Version: Naming\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-03-09 16:07+1000\n"
+"PO-Revision-Date: 2009-03-10 13:28+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"
@@ -47,7 +47,7 @@
"Whether it is a big clustered service, a local resource or just a simple "
"application component that is needed, the JNDI naming service provides the "
"glue that lets code find the objects in the system by name."
-msgstr "O serviço de nomeação executa a função principal nos aplicativos Java empresarial, fornece uma infraestrutura principal que é usado para localizar objetos num servidor do aplicativo. Este é também o mecanismo que os clientes externos para o servidor do aplicativo usa para localizar os serviços dentro do servidor do aplicativo. O código do aplicativo, independente disto ser inteno ou externo à instância JBoss, precisa apenas saber que isto precisa comunicar-se a nomeada fila de mensagem <literal>queue/IncomingOrders</literal> e não precisará preocupar-se com quaisquer detalhes de como a fila é configurada. Num ambiente com cluster, os serviços de nomeação são ainda mais valorizados. Um cliente de um ser"
+msgstr "O serviço de nomeação executa a função principal nos aplicativos Java empresarial, fornece uma infraestrutura principal que é usado para localizar objetos num servidor do aplicativo. Este é também o mecanismo que os clientes externos para o servidor do aplicativo usa para localizar os serviços dentro do servidor do aplicativo. O código do aplicativo, independente disto ser interno ou externo à instância JBoss, precisa apenas saber que isto precisa comunicar-se a nomeada fila de mensagem <literal>queue/IncomingOrders</literal> e não precisará preocupar-se com quaisquer detalhes de como a fila é configurada. Num ambiente com cluster, os serviços de nomeação são ainda mais valorizados. Um cliente de um serviço preferiria observar o bean de sessão <literal>ProductCatalog</literal> a partir do cluster sem se preocupar qual máquina o serviço está residindo. Independente disto ser um serviço grande com cluster, um recurso local ou apenas um compone!
nte de aplicativo simples que é necessário, o serviço de nomeação JNDI fornece a dica pela qual permite que o código encontre os objetos no sistema pelo nome."
#. Tag: title
#: Naming.xml:12
@@ -294,7 +294,7 @@
"which allows your code to externalize the JNDI provider specific information "
"so that changing JNDI providers will not require changes to your code or "
"recompilation."
-msgstr "Para cada propriedade encontrada nas duas fontes, o valor da propriedade é determinado conforme abaizo. Caso a propriedade é uma das propriedades JNDI padrão que especifica uma lista de criações JNDI, todos os valores serão conacatenizados numa única lista de ponto-e-vírgula-separado. Para as demais propriedades, apenas o primeiro valor encontrado será usado. O método preferido de especificação das propriedades do ambiente é através do arquivo <literal>jndi.properties</literal>, do qual permite que seu código externalizar a informação específica do fornecedor JNDI, de forma que a alteração dos fornecedores JNDI não solicitarão alterações em seu código ou re-compilação."
+msgstr "Para cada propriedade encontrada nas duas fontes, o valor da propriedade é determinado conforme abaixo. Caso a propriedade é uma das propriedades JNDI padrão que especifica uma lista de criações JNDI, todos os valores serão concatenizados numa única lista de ponto-e-vírgula-separado. Para as demais propriedades, apenas o primeiro valor encontrado será usado. O método preferido de especificação das propriedades do ambiente é através do arquivo <literal>jndi.properties</literal>, do qual permite que seu código externalizar a informação específica do fornecedor JNDI, de forma que a alteração dos fornecedores JNDI não solicitarão alterações em seu código ou re-compilação."
#. Tag: para
#: Naming.xml:76
@@ -323,6 +323,8 @@
"the properties that the JBossNS JNDI implementation requires. Other JNDI "
"providers will have different properties and values."
msgstr ""
+"Fornece uma amostra do arquivo de <literal>jndi.properties</literal> que um aplicativo de cliente usaria para conectar a um serviço JBossNS rodando no hospedeiro local no portal 1099. O aplicativo do cliente necessitaria possuir o arquivo <literal>jndi."
+"properties</literal> disponível na classpath do aplicativo. Estas são as propriedades que a implementação do JBossNS JNDI solicita. Outros provedores JNDI terão diferentes propriedades e valores."
#. Tag: title
#: Naming.xml:82
@@ -410,11 +412,7 @@
"<literal>NamingService</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 on one of its addresses."
-msgstr ""
-"<emphasis role=\"bold\">BindAddress</emphasis>: The specific address the "
-"<literal>NamingService</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 on one of its addresses."
+msgstr "<emphasis role=\"bold\">BindAddress</emphasis>: O endereço específico que o <literal>NamingService</literal> escuta. Isto pode ser usado num hospedeiro multi-homed para um <literal>java.net.ServerSocket</literal> que apenas aceitará conectar as solicitações em um destes endereços."
#. Tag: para
#: Naming.xml:124
@@ -427,14 +425,7 @@
"this is not specified and the <literal>BindAddress</literal> is, the "
"<literal>RmiBindAddress</literal> defaults to the <literal>BindAddress</"
"literal> value."
-msgstr ""
-"<emphasis role=\"bold\">RmiBindAddress</emphasis>: The specific address the "
-"RMI server portion of the <literal>NamingService</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 on one of its addresses. If "
-"this is not specified and the <literal>BindAddress</literal> is, the "
-"<literal>RmiBindAddress</literal> defaults to the <literal>BindAddress</"
-"literal> value."
+msgstr "<emphasis role=\"bold\">RmiBindAddress</emphasis>: O endereço específico a porção do servidor RMI do "
#. Tag: para
#: Naming.xml:129
@@ -558,6 +549,19 @@
"<literal>NamingService</literal> is started, it starts the contained "
"<literal>Main</literal> MBean to activate the JNDI naming service."
msgstr ""
+"The <literal>NamingService</literal> delegates its functionality to an "
+"<literal>org.jnp.server.Main</literal> MBean. The reason for the duplicate "
+"MBeans is because JBossNS started out as a stand-alone JNDI implementation, "
+"and can still be run as such. The <literal>NamingService</literal> MBean "
+"embeds the <literal>Main</literal> instance into the JBoss server so that "
+"usage of JNDI with the same VM as the JBoss server does not incur any socket "
+"overhead. The configurable attributes of the NamingService are really the "
+"configurable attributes of the JBossNS <literal>Main</literal> MBean. The "
+"setting of any attributes on the <literal>NamingService</literal> MBean "
+"simply set the corresponding attributes on the <literal>Main</literal> MBean "
+"the <literal>NamingService</literal> contains. When the "
+"<literal>NamingService</literal> is started, it starts the contained "
+"<literal>Main</literal> MBean to activate the JNDI naming service."
#. Tag: para
#: Naming.xml:158
@@ -570,6 +574,12 @@
"to access the naming service using the invoke operation later in this "
"chapter."
msgstr ""
+"In addition, the <literal>NamingService</literal> exposes the "
+"<literal>Naming</literal> interface operations through a JMX detyped invoke "
+"operation. This allows the naming service to be accessed via JMX adaptors "
+"for arbitrary protocols. We will look at an example of how HTTP can be used "
+"to access the naming service using the invoke operation later in this "
+"chapter."
#. Tag: para
#: Naming.xml:161
@@ -580,6 +590,10 @@
"applicable. See <ulink url=\"http://java.sun.com/products/jndi/tutorial/"
"beyond/misc/classloader.html\"></ulink> for the details."
msgstr ""
+"The details of threads and the thread context class loader won't be "
+"explored here, but the JNDI tutorial provides a concise discussion that is "
+"applicable. See <ulink url=\"http://java.sun.com/products/jndi/tutorial/"
+"beyond/misc/classloader.html\"></ulink> for the details."
#. Tag: para
#: Naming.xml:164
@@ -588,6 +602,8 @@
"When the <literal>Main</literal> MBean is started, it performs the following "
"tasks:"
msgstr ""
+"When the <literal>Main</literal> MBean is started, it performs the following "
+"tasks:"
#. Tag: para
#: Naming.xml:169
@@ -598,6 +614,10 @@
"jnp.interfaces.NamingContext</literal> instances that are created within the "
"JBoss server VM to avoid RMI calls over TCP/IP."
msgstr ""
+"Instantiates an <literal>org.jnp.naming.NamingService</literal> instance and "
+"sets this as the local VM server instance. This is used by any <literal>org."
+"jnp.interfaces.NamingContext</literal> instances that are created within the "
+"JBoss server VM to avoid RMI calls over TCP/IP."
#. Tag: para
#: Naming.xml:174
@@ -608,6 +628,10 @@
"<literal>RmiPort</literal>, <literal>ClientSocketFactory</literal>, "
"<literal>ServerSocketFactory</literal>attributes."
msgstr ""
+"Exports the <literal>NamingServer</literal> instance's <literal>org.jnp."
+"naming.interfaces.Naming</literal> RMI interface using the configured "
+"<literal>RmiPort</literal>, <literal>ClientSocketFactory</literal>, "
+"<literal>ServerSocketFactory</literal>attributes."
#. Tag: para
#: Naming.xml:179
@@ -616,18 +640,20 @@
"Creates a socket that listens on the interface given by the "
"<literal>BindAddress</literal> and <literal>Port</literal> attributes."
msgstr ""
+"Creates a socket that listens on the interface given by the "
+"<literal>BindAddress</literal> and <literal>Port</literal> attributes."
#. Tag: para
#: Naming.xml:184
#, no-c-format
msgid "Spawns a thread to accept connections on the socket."
-msgstr ""
+msgstr "Spawns a thread to accept connections on the socket."
#. Tag: title
#: Naming.xml:192
#, no-c-format
msgid "The Naming InitialContext Factories"
-msgstr ""
+msgstr "The Naming InitialContext Factories"
#. Tag: para
#: Naming.xml:193
@@ -636,12 +662,14 @@
"The JBoss JNDI provider currently supports several different "
"<literal>InitialContext</literal> factory implementations."
msgstr ""
+"The JBoss JNDI provider currently supports several different "
+"<literal>InitialContext</literal> factory implementations."
#. Tag: title
#: Naming.xml:197
#, no-c-format
msgid "The standard naming context factory"
-msgstr ""
+msgstr "The standard naming context factory"
#. Tag: para
#: Naming.xml:198
@@ -650,6 +678,8 @@
"The most commonly used factory is the <literal>org.jnp.interfaces."
"NamingContextFactory</literal> implementation. Its properties include:"
msgstr ""
+"The most commonly used factory is the <literal>org.jnp.interfaces."
+"NamingContextFactory</literal> implementation. Its properties include:"
#. Tag: para
#: Naming.xml:203
@@ -662,6 +692,12 @@
"<literal>javax.naming.NoInitialContextException</literal> will be thrown "
"when an <literal>InitialContext</literal> object is created."
msgstr ""
+"<emphasis role=\"bold\">java.naming.factory.initial</emphasis>: The name of "
+"the environment property for specifying the initial context factory to use. "
+"The value of the property should be the fully qualified class name of the "
+"factory class that will create an initial context. If it is not specified, a "
+"<literal>javax.naming.NoInitialContextException</literal> will be thrown "
+"when an <literal>InitialContext</literal> object is created."
#. Tag: para
#: Naming.xml:208
@@ -680,6 +716,18 @@
"host component is optional. The following examples are equivalent because "
"the default port value is 1099."
msgstr ""
+"<emphasis role=\"bold\">java.naming.provider.url</emphasis>: The name of the "
+"environment property for specifying the location of the JBoss JNDI service "
+"provider the client will use. The <literal>NamingContextFactory</literal> "
+"class uses this information to know which JBossNS server to connect to. The "
+"value of the property should be a URL string. For JBossNS the URL format is "
+"<literal>jnp://host:port/[jndi_path]</literal>. The <literal>jnp:</literal> "
+"portion of the URL is the protocol and refers to the socket/RMI based "
+"protocol used by JBoss. The <literal>jndi_path</literal> portion of the URL "
+"is an optional JNDI name relative to the root context, for example, "
+"<literal>apps</literal> or <literal>apps/tmp</literal>. Everything but the "
+"host component is optional. The following examples are equivalent because "
+"the default port value is 1099."
#. Tag: literal
#: Naming.xml:214
@@ -712,6 +760,14 @@
"property is essential for locating the <literal>jnp:</literal> and "
"<literal>java:</literal> URL context factories of the JBoss JNDI provider."
msgstr ""
+"<emphasis role=\"bold\">java.naming.factory.url.pkgs</emphasis>: The name of "
+"the environment property for specifying the list of package prefixes to use "
+"when loading in URL context factories. The value of the property should be a "
+"colon-separated list of package prefixes for the class name of the factory "
+"class that will create a URL context factory. For the JBoss JNDI provider "
+"this must be <literal>org.jboss.naming:org.jnp.interfaces</literal>. This "
+"property is essential for locating the <literal>jnp:</literal> and "
+"<literal>java:</literal> URL context factories of the JBoss JNDI provider."
#. Tag: para
#: Naming.xml:235
@@ -725,6 +781,13 @@
"supports the specification of a connection and read timeout. These two "
"properties are specified by:"
msgstr ""
+"<emphasis role=\"bold\">jnp.socketFactory</emphasis>: The fully qualified "
+"class name of the <literal>javax.net.SocketFactory</literal> implementation "
+"to use to create the bootstrap socket. The default value is <literal>org.jnp."
+"interfaces.TimedSocketFactory</literal>. The <literal>TimedSocketFactory</"
+"literal> is a simple <literal>SocketFactory</literal> implementation that "
+"supports the specification of a connection and read timeout. These two "
+"properties are specified by:"
#. Tag: para
#: Naming.xml:240
@@ -771,6 +834,21 @@
"PROVIDER_URL</literal> information from the environment indicates from which "
"server to obtain a <literal>NamingServer</literal> RMI reference."
msgstr ""
+"When a client creates an <literal>InitialContext</literal> with these "
+"JBossNS properties available, the <literal>org.jnp.interfaces."
+"NamingContextFactory</literal> object is used to create the "
+"<literal>Context</literal> instance that will be used in subsequent "
+"operations. The <literal>NamingContextFactory</literal> is the JBossNS "
+"implementation of the <literal>javax.naming.spi.InitialContextFactory</"
+"literal> interface. When the <literal>NamingContextFactory</literal> class "
+"is asked to create a <literal>Context</literal>, it creates an <literal>org."
+"jnp.interfaces.NamingContext</literal> instance with the "
+"<literal>InitialContext</literal> environment and name of the context in the "
+"global JNDI namespace. It is the <literal>NamingContext</literal> instance "
+"that actually performs the task of connecting to the JBossNS server, and "
+"implements the <literal>Context</literal> interface. The <literal>Context."
+"PROVIDER_URL</literal> information from the environment indicates from which "
+"server to obtain a <literal>NamingServer</literal> RMI reference."
#. Tag: para
#: Naming.xml:253
@@ -801,6 +879,30 @@
"<literal>NamingContext</literal> simply uses the in VM Naming instance set "
"by the <literal>Main</literal> MBean."
msgstr ""
+"The association of the <literal>NamingContext</literal> instance to a "
+"<literal>NamingServer</literal> instance is done in a lazy fashion on the "
+"first <literal>Context</literal> operation that is performed. When a "
+"<literal>Context</literal> operation is performed and the "
+"<literal>NamingContext</literal> has no <literal>NamingServer</literal> "
+"associated with it, it looks to see if its environment properties define a "
+"<literal>Context.PROVIDER_URL</literal>. A <literal>Context.PROVIDER_URL</"
+"literal> defines the host and port of the JBossNS server the "
+"<literal>Context</literal> is to use. If there is a provider URL, the "
+"<literal>NamingContext</literal> first checks to see if a <literal>Naming</"
+"literal> instance keyed by the host and port pair has already been created "
+"by checking a <literal>NamingContext</literal> class static map. It simply "
+"uses the existing <literal>Naming</literal> instance if one for the host "
+"port pair has already been obtained. If no <literal>Naming</literal> "
+"instance has been created for the given host and port, the "
+"<literal>NamingContext</literal> connects to the host and port using a "
+"<literal>java.net.Socket</literal>, and retrieves a <literal>Naming</"
+"literal> RMI stub from the server by reading a <literal>java.rmi."
+"MarshalledObject</literal> from the socket and invoking its get method. The "
+"newly obtained Naming instance is cached in the <literal>NamingContext</"
+"literal> server map under the host and port pair. If no provider URL was "
+"specified in the JNDI environment associated with the context, the "
+"<literal>NamingContext</literal> simply uses the in VM Naming instance set "
+"by the <literal>Main</literal> MBean."
#. Tag: para
#: Naming.xml:256
More information about the jboss-cvs-commits
mailing list