This implementation will be presented in the next section.
该实现将在下一小节中介绍。
Details about the component are described in the next section.
下一部分将描述关于该组件的详细信息。
That requires a clustered solution as described in the next section.
需要一个集群解决方案,详见下一节描述。
Leave the interface attribute blank; you create it in the next section.
将interface属性保留空白;您将在下一个部分中创建该属性。
Some of the other attributes in an inode are discussed in the next section.
下一个部分将介绍 inode 中的其他一些属性。
This is as expected and those objects will be created in the next section.
这在预料之中,这些对象将在下一小节中创建。
The XML data management choices are briefly reviewed in the next section.
下一节将简要回顾XML数据管理方式。
This message can be ignored - we're taking care of it in the next section.
可以忽略这条提示——我们将在下一环节关注它。
For now, we'll omit the more advanced features (discussed in the next section).
目前,我们将省略许多比较高级的特性(将在下一节中讨论)。
The backward compatibility assessment, stage 1, is examined in the next section.
第1阶段(向后兼容性评估)将在下一部分中进行讨论。
The sample application described in the next section will demonstrate this capability.
下一节介绍的示例应用程序将展示这种能力。
I'll also come back to this in more detail in the next section, focused on attributes.
下一节介绍属性时还将进一步讨论。
This process is called "de-sugaring" and will dig into how it works in the next section.
这个过程可以被称作“反语法糖(de-sugaring)”,我们将在下一节重点讲述它的工作原理。
The optimal heap settings will depend on the GC policy, described in the next section.
最佳的堆设置取决于GC策略,这将在下一小节进行讨论。
The query examples in the next section are based off of the sample data shown in Table 1.
下一节中的查询示例将以表1中展示的样例数据为基础。
Configuration information, such as JNDI names, is described in detail in the next section.
下一部分将对各种配置(如JNDI名称)进行描述。
We cover the use of the IBM JVM trace to provide startup statistics in the next section.
我们将在下一节中讨论如何使用IBMJVM跟踪提供启动统计数据。
Instead, a federation layer is involved, as explained in more detail in the next section.
相反,正如接下来的小节中要详细解释的那样,这里使用一个联邦层。
You can then analyze the heap data using the jhat utility described in the next section.
然后您可以采用下一部分中描述的jhat实用程序分析堆数据。
The manager component is an EJB3 session bean and we will discuss it in the next section.
名为manager的组件是一个EJB3的会话bean,我们将在下节讨论该话题。
This is usually done on your behalf by the DASes, which we will meet in the next section.
DAS通常会替您完成这些任务,我们将在下一节介绍相关内容。
The second part of the connector is the formatter, which you'll look at in the next section.
连接器的第二个部分是formatter,我们将在下一节 介绍它。
You look at the logs in the next section, which offer some clues as to where the problem lies.
您可以查看下一节将要介绍的日志,其中就问题所在提供了一些线索。
The other governors have additional Settings available which we discuss in the next section.
其他调控器有更多设置可用,我们在下一节中讨论。
Another way to search for a class using the sysinfo utility is described in the next section.
另一种方法是通过sysinfo实用程序来搜索类,这将在下一节中进行描述。
The WI_COUNT column is often used with the historical tables, as described in the next section.
WI_COUNT列通常与历史表格一起使用,如下面的章节中所描述的那样。
The listener and channel configurations to run the sample code are provided in the next section.
在下一部分中提供了运行示例代码的侦听器和通道配置。
As you'll see in the next section, they can in fact benefit from a more lightweight methodology.
正如您将在下面的部分中看到的,实际上,他们可以从一个更为轻量级的方法中获益。
These bindings will be reused in the next section for the creation of additional service methods.
这些绑定将在下一部分创建其他服务方法中重用。
The four example scenarios in the next section demonstrate the drawbacks of today's static portals.
下一部分中的四种示例情形将演示当今静态门户存在的一些缺陷。
应用推荐