[jboss-cvs] JBossAS SVN: r85807 - 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
Fri Mar 13 01:17:03 EDT 2009
Author: ldelima at redhat.com
Date: 2009-03-13 01:17:02 -0400 (Fri, 13 Mar 2009)
New Revision: 85807
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-13 05:16:00 UTC (rev 85806)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/Naming.po 2009-03-13 05:17:02 UTC (rev 85807)
@@ -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-13 15:11+1000\n"
+"PO-Revision-Date: 2009-03-13 15:16+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"
@@ -2696,6 +2696,10 @@
"literal> from an external properties file. This is either a URL, string or a "
"classpath resource name. Examples are as follows:"
msgstr ""
+"<emphasis role=\"bold\">PropertiesURL</emphasis>: This set the <literal>jndi."
+"properties</literal> information for the external <literal>InitialContext</"
+"literal> from an external properties file. This is either a URL, string or a "
+"classpath resource name. Examples are as follows:"
#. Tag: para
#: Naming.xml:711
@@ -2778,6 +2782,9 @@
"<literal>ldap://ldaphost.jboss.org:389/o=jboss.org</literal> from within the "
"JBoss VM using the following code fragment:"
msgstr ""
+"With this configuration, you can access the external LDAP context located at "
+"<literal>ldap://ldaphost.jboss.org:389/o=jboss.org</literal> from within the "
+"JBoss VM using the following code fragment:"
#. Tag: programlisting
#: Naming.xml:740
@@ -2800,6 +2807,12 @@
"<literal>ObjectFactory</literal> that would not be able to recreate the "
"external <literal>InitialContext</literal>"
msgstr ""
+"Using the same code fragment outside of the JBoss server VM will work in "
+"this case because the <literal>RemoteAccess</literal> property was set to "
+"true. If it were set to false, it would not work because the remote client "
+"would receive a <literal>Reference</literal> object with an "
+"<literal>ObjectFactory</literal> that would not be able to recreate the "
+"external <literal>InitialContext</literal>"
#. Tag: programlisting
#: Naming.xml:744
@@ -2843,6 +2856,9 @@
"usr/local</literal> into the JBoss JNDI namespace under the name "
"<literal>external/fs/usr/local</literal>."
msgstr ""
+"This configuration describes binding a local file system directory <literal>/"
+"usr/local</literal> into the JBoss JNDI namespace under the name "
+"<literal>external/fs/usr/local</literal>."
#. Tag: para
#: Naming.xml:748
@@ -2852,6 +2868,9 @@
"located at <literal>file:///usr/local</literal> from within the JBoss VM "
"using the following code fragment:"
msgstr ""
+"With this configuration, you can access the external file system context "
+"located at <literal>file:///usr/local</literal> from within the JBoss VM "
+"using the following code fragment:"
#. Tag: programlisting
#: Naming.xml:751
@@ -2872,6 +2891,10 @@
"\"></ulink>. The provider JARs should be placed in the server configuration "
"<literal>lib</literal> directory."
msgstr ""
+"Note that the use the Sun JNDI service providers, which must be downloaded "
+"from <ulink url=\"http://java.sun.com/products/jndi/serviceproviders.html"
+"\"></ulink>. The provider JARs should be placed in the server configuration "
+"<literal>lib</literal> directory."
#. Tag: title
#: Naming.xml:758
@@ -2892,12 +2915,20 @@
"look something like that shown in <xref linkend=\"The_org.jboss.naming."
"JNDIView_MBean-The_JMX_Console_view_of_the_configured_JBoss_MBeans\"/>."
msgstr ""
+"The JNDIView MBean allows the user to view the JNDI namespace tree as it "
+"exists in the JBoss server using the JMX agent view interface. To view the "
+"JBoss JNDI namespace using the JNDIView MBean, you connect to the JMX Agent "
+"View using the http interface. The default settings put this at "
+"<literal>http://localhost:8080/jmx-console/</literal>. On this page you will "
+"see a section that lists the registered MBeans sorted by domain. It should "
+"look something like that shown in <xref linkend=\"The_org.jboss.naming."
+"JNDIView_MBean-The_JMX_Console_view_of_the_configured_JBoss_MBeans\"/>."
#. Tag: title
#: Naming.xml:763
#, no-c-format
msgid "The JMX Console view of the configured JBoss MBeans"
-msgstr ""
+msgstr "The JMX Console view of the configured JBoss MBeans"
#. Tag: para
#: Naming.xml:770
@@ -2908,12 +2939,16 @@
"to that shown in <xref linkend=\"The_org.jboss.naming.JNDIView_MBean-"
"The_JMX_Console_view_of_the_JNDIView_MBean\"/>."
msgstr ""
+"Selecting the JNDIView link takes you to the JNDIView MBean view, which will "
+"have a list of the JNDIView MBean operations. This view should look similar "
+"to that shown in <xref linkend=\"The_org.jboss.naming.JNDIView_MBean-"
+"The_JMX_Console_view_of_the_JNDIView_MBean\"/>."
#. Tag: title
#: Naming.xml:774
#, no-c-format
msgid "The JMX Console view of the JNDIView MBean"
-msgstr ""
+msgstr "The JMX Console view of the JNDIView MBean"
#. Tag: para
#: Naming.xml:781
@@ -2925,18 +2960,23 @@
"JNDIView_MBean-The_JMX_Console_view_of_the_JNDIView_list_operation_output\"/"
">."
msgstr ""
+"The list operation dumps out the JBoss server JNDI namespace as an HTML page "
+"using a simple text view. As an example, invoking the list operation "
+"produces the view shown in <xref linkend=\"The_org.jboss.naming."
+"JNDIView_MBean-The_JMX_Console_view_of_the_JNDIView_list_operation_output\"/"
+">."
#. Tag: title
#: Naming.xml:785
#, no-c-format
msgid "The JMX Console view of the JNDIView list operation output"
-msgstr ""
+msgstr "The JMX Console view of the JNDIView list operation output"
#. Tag: title
#: Naming.xml:797
#, no-c-format
msgid "J2EE and JNDI - The Application Component Environment"
-msgstr ""
+msgstr "J2EE and JNDI - The Application Component Environment"
#. Tag: para
#: Naming.xml:798
@@ -2953,6 +2993,16 @@
"is utilized by the participants involved in the life cycle of a J2EE "
"component in the following ways."
msgstr ""
+"JNDI is a fundamental aspect of the J2EE specifications. One key usage is "
+"the isolation of J2EE component code from the environment in which the code "
+"is deployed. Use of the application component's environment allows the "
+"application component to be customized without the need to access or change "
+"the application component's source code. The application component "
+"environment is referred to as the ENC, the enterprise naming context. It is "
+"the responsibility of the application component container to make an ENC "
+"available to the container components in the form of JNDI Context. The ENC "
+"is utilized by the participants involved in the life cycle of a J2EE "
+"component in the following ways."
#. Tag: para
#: Naming.xml:803
@@ -2964,6 +3014,11 @@
"declarations of the information and resources the component requires at "
"runtime."
msgstr ""
+"Application component business logic should be coded to access information "
+"from its ENC. The component provider uses the standard deployment descriptor "
+"for the component to specify the required ENC entries. The entries are "
+"declarations of the information and resources the component requires at "
+"runtime."
#. Tag: para
#: Naming.xml:808
@@ -2973,6 +3028,9 @@
"ENC references made by the component developer to the deployment environment "
"entity that satisfies the reference."
msgstr ""
+"The container provides tools that allow a deployer of a component to map the "
+"ENC references made by the component developer to the deployment environment "
+"entity that satisfies the reference."
#. Tag: para
#: Naming.xml:813
@@ -2981,6 +3039,8 @@
"The component deployer utilizes the container tools to ready a component for "
"final deployment."
msgstr ""
+"The component deployer utilizes the container tools to ready a component for "
+"final deployment."
#. Tag: para
#: Naming.xml:818
@@ -2989,6 +3049,8 @@
"The component container uses the deployment package information to build the "
"complete component ENC at runtime"
msgstr ""
+"The component container uses the deployment package information to build the "
+"complete component ENC at runtime"
#. Tag: para
#: Naming.xml:823
@@ -2999,6 +3061,10 @@
"specification is available at <ulink url=\"http://java.sun.com/j2ee/download."
"html\"></ulink>."
msgstr ""
+"The complete specification regarding the use of JNDI in the J2EE platform "
+"can be found in section 5 of the J2EE 1.4 specification. The J2EE "
+"specification is available at <ulink url=\"http://java.sun.com/j2ee/download."
+"html\"></ulink>."
#. Tag: para
#: Naming.xml:826
@@ -3014,6 +3080,15 @@
"ENC_access_sample_code\"/> illustrates the prototypical lines of code a "
"component uses to access its ENC."
msgstr ""
+"An application component instance locates the ENC using the JNDI API. An "
+"application component instance creates a <literal>javax.naming."
+"InitialContext</literal> object by using the no argument constructor and "
+"then looks up the naming environment under the name <literal>java:comp/env</"
+"literal>. The application component's environment entries are stored "
+"directly in the ENC, or in its subcontexts. <xref linkend="
+"\"J2EE_and_JNDI___The_Application_Component_Environment-"
+"ENC_access_sample_code\"/> illustrates the prototypical lines of code a "
+"component uses to access its ENC."
#. Tag: title
#: Naming.xml:829
@@ -3058,6 +3133,26 @@
"<literal>Web1</literal> may bind the same name to the deployment environment "
"language locale representation of red."
msgstr ""
+"An application component environment is a local environment that is "
+"accessible only by the component when the application server container "
+"thread of control is interacting with the application component. This means "
+"that an EJB <literal>Bean1</literal> cannot access the ENC elements of EJB "
+"<literal>Bean2</literal>, and vice versa. Similarly, Web application "
+"<literal>Web1</literal> cannot access the ENC elements of Web application "
+"<literal>Web2</literal> or <literal>Bean1</literal> or <literal>Bean2</"
+"literal> for that matter. Also, arbitrary client code, whether it is "
+"executing inside of the application server VM or externally cannot access a "
+"component's <literal>java:comp</literal> JNDI context. The purpose of "
+"the ENC is to provide an isolated, read-only namespace that the application "
+"component can rely on regardless of the type of environment in which the "
+"component is deployed. The ENC must be isolated from other components "
+"because each component defines its own ENC content. Components <literal>A</"
+"literal> and <literal>B</literal>, for example, may define the same name to "
+"refer to different objects. For example, EJB <literal>Bean1</literal> may "
+"define an environment entry <literal>java:comp/env/red</literal> to refer to "
+"the hexadecimal value for the RGB color for red, while Web application "
+"<literal>Web1</literal> may bind the same name to the deployment environment "
+"language locale representation of red."
#. Tag: para
#: Naming.xml:834
@@ -3939,6 +4034,9 @@
"Context ejbCtx = (Context) iniCtx.lookup(\"java:comp/env/ejb\");\n"
"ProbeLocalHome home = (ProbeLocalHome) ejbCtx.lookup(\"ProbeLocalHome\");"
msgstr ""
+"InitialContext iniCtx = new InitialContext();\n"
+"Context ejbCtx = (Context) iniCtx.lookup(\"java:comp/env/ejb\");\n"
+"ProbeLocalHome home = (ProbeLocalHome) ejbCtx.lookup(\"ProbeLocalHome\");"
#. Tag: title
#: Naming.xml:1103
More information about the jboss-cvs-commits
mailing list