Instrumentation code within service implementation detects and logs system - and application-level exceptions.
服务实现中的工具代码用于检测和记录系统级和应用级异常。
The instrumentation code can be added at any stage of the compilation process by system tools such as the compiler or linker or by external tools that are part of a measurement system.
这种插装能够在程序编译过程的各阶段进行,通过诸如编译器、链接器、或者是测试系统所包含的外部工具。
After you add animation, you can regenerate code without using the animation instrumentation in the code.
在您添加图形化之后,您可以重新生成代码,而无需在代码中使用图形化工具。
Source code instrumentation: the most basic technique is to add instrumentation at the source code phase so that the compiled and deployed classes already contain the instrumentation at run time.
源代码插装:最基本的技巧是在源代码阶段添加插装,这样编译和部署后的类就已经在运行时包含了插装。
Even when an application is only for local use, write clean code, and have lots of instrumentation and debugging output available.
即使在应用程序只供本地使用的情况下,也应该编写干净的代码,并提供足够的测试和调试输出。
This section addresses the subject of implementing source level instrumentation and provides some best practices and example source code.
本节将讨论如何实现源代码级插装,并将提供一些最佳实践和示例代码。
It also introduces some new tracing constructs that I'll detail in the context of source code instrumentation to clarify their actions and their implementation patterns.
文章还介绍了一些新的跟踪结构,我将在源代码插装的上下文中阐明它们的操作和它们的插装模式。
This reinstrumentation step removes the instrumentation from code that's already been covered, only leaving it in place for code that wasn't executed by the initial tests.
重新插装步骤会将已经覆盖过的插装从代码中去掉,只留下在开始的测试中没有执行的插装。
Here in Part 1, I address only source code based instrumentation; you'll read more about interception, bytecode instrumentation, and class wrapping in Part 2.
在本文的第1部分中,我只讨论基于源代码的插装;您将在第2部分中了解更多关于截取、字节码插装和类包装的信息。
Despite the prevalence of alternatives, instrumentation of source code is unavoidable in some instances; in some cases it's the only solution.
虽然其他选择已经流行,但源代码插装在某些实例中是无法避免的;在某些情况下,它是惟一的解决方案。
Writing compliant code to these well-specified interfaces ensures our instrumentation and agent logic will work with any JMX 1.1-compatible implementation.
按照这些良好规定的接口编写符合规定的代码,确保了我们的工具和代理逻辑可以与任何兼容JMX 1.1的实现一起使用。
One mechanism that is widely used is known as byte-code instrumentation.
一种广泛应用的机制称为字节码测试。
Source code instrumentation: manually adding instrumentation to your application.
源码工具:手动将其加入应用中。
We use official APIs where they exist and we complement this data with byte code instrumentation to gather deep information that enables rapid troubleshooting.
我们使用官方API并通过字节码instrumentation的方式来补充这些数据,从而获得了能够快速解决问题的深层次信息。
They all typically use some form of instrumentation of the code under test, which inserts hooks into the product code.
它们都典型地使用被测代码的某种形式的装置,这将钩子(hooks)加入了产品代码中。
You start by using Gretel to instrument your code, next running one or more tests with the Gretel instrumentation saving execution data to files, then using Gretel again to view the saved data.
首先使用Gretel插装代码,接着用Gretel插装(instrumentation)运行一个或多个测试,将执行数据保存到文件中,然后再次使用Gretel来查看所保存的数据。
You can integrate the Rational Code Coverage feature into your environment by performing the following three steps: instrumentation, execution, and report generation.
通过执行以下的三个步骤:评价,执行以及生成报告,您可以将RationalCodeCoverage特性集成到您的环境之中。
If you examine the actual source code, you will find that the Tomcat 4 instrumentation makes extensive use of the Model MBean template supplied by the JMX implementation.
如果您研究实际的源代码,您将发现Tomcat4工具广泛利用了JMX实现提供的模型MBean模板。
The running environment supports protecting code instrumentation to execute protection strategies.
运行环境支持对程序插装保护代码,执行保护策略。
Dynamic code instrumentation, combined with hybrid code generation and source breakpoint identification, provides a well-suited solution to those problems.
并针对上述问题,提出了预编译与运行时编译结合的代码生成方式、动态代码插装、源断点标识技术等解决方案。
Not available for native code or for profiling data that was collected by using the instrumentation method.
不可用于本机代码或分析数据,该数据通过使用检测方法收集。
The instrumentation process adds code to the assembly so that code coverage data can be generated.
检测程序会将程序码加入至组件,以便产生程序码涵盖范围资料。
The instrumentation process adds code to the assembly so that code coverage data can be generated.
检测程序会将程序码加入至组件,以便产生程序码涵盖范围资料。
应用推荐