Similar classes wrap BCEL information for existing classes and methods.
类似的类为现有类和方法包装了BCEL信息。
In my own use of BCEL, I've found the HTML disassembler especially useful.
我自己使用BCEL时，发现HTML反汇编程序特别有用。
The JPOX enhancer requires the Apache byte code engineering library (BCEL).
JPOX enhancer需要Apache字节码工程库(byte code engineering library, BCEL)。
Bcel provides the org.apache.bcel.Repository class to handle the parsing for you.
bcel提供了or g . apache . bcel . Repository类用于处理解析。
Many other unlisted projects are also using BCEL, including my own JiBX XML data binding project.
许多其他未列出的项目也使用BCEL，包括我自己的JiBXXML数据绑定项目。
Some of the problems I ran into are specific to BCEL, but others apply to other bytecode frameworks as well.
我遇到的一些问题是bcel特有的，但是其他问题在其他字节码框架中也有。
I'll therefore concentrate on the differences that are likely to confuse you when you start working with BCEL.
因此我将主要介绍在开始使用BCEL时，可能会让您感到迷惑的那些不同之处。
In fact, going back and forth between the two packages is one of the most awkward aspects of working with BCEL.
事实上，在两个包之间来回转是使用BCEL的一个最主要的缺点。
For the JiBX binding compiler, I found it easiest to just hide all the BCEL details within several wrapper classes.
对于JiBX绑定编译器，我发现最容易的方式就是把所有BCEL的细节隐藏在几个包装器类中。
The big advantages of BCEL are its commercial-friendly Apache licensing and its extensive JVM instruction-level support.
BCEL最大的好处是它的商业友好的Apache许可证及其丰富的JVM指令级支持。
In practice, I found the bcel version of this class writing program (org.apache.bcel.util.BCELifier) to be of limited use.
而在实践中，我发现这种类编写程序的bcel版本(or g . apache . bcel . ut il . BCELifier)使用起来有一些限制。
Unfortunately, the documentation on both the BCEL and FindBugs support for taking apart a class is weaker than you might like.
遗憾的是，关于BCEL和FindBugs如何支持类分离的文档并不能满足您的需要。
Although BCEL has worked for this purpose, it's sometimes proven more difficult to use than I'd expected when I began the project.
虽然BCEL可以用于实现这个目的，但是，它有时使用起来要比我开始这个项目时期望的更困难。
Hiding the BCEL details in my wrapper also gave me convenient places to add more functionality, as in the class and method comparison code.
把BCEL细节隐藏在包装器中，也提供了方便地添加更多功能的位置，就像在类和方法比较代码中一样。
The BCEL code for manipulating lists of instructions is complex, and to me the source code generated by BCELifier was too ugly to be usable.
用于操纵指令列表的BCEL代码很复杂，对我来说，BCELifier生成的源代码太难看，无法使用。
The BCEL and FindBugs libraries handle some of this task for you, extracting information from the bytecode and presenting it at a slightly higher level.
BCEL和findbugs库将为您处理此任务，并从字节码中提取信息，在稍高级别上呈现它。
For the method call instructions, you use Bytecode Engineering Library (BCEL) classes to extract the types of checked exceptions the method is declared to throw.
对于方法调用指令，可以使用BytecodeEngineeringLibrary (BCEL)类来提取方法声明抛出的已检查异常的类型。
To try it out, just execute the org.apache.bcel.util.Class2HTML class from the bcel JAR, with the path to the class file you want to disassemble as a command line argument.
要想试用它，只要执行bcelJAR中的or g . apache. bcel . ut il .class2html类，用要反汇编的类文件的路径作为命令行参数。
The duplicate class structures tend to get in the way, so if you're doing much with BCEL, it may be worthwhile to write wrapper classes that can hide some of these differences.
重复的类结构总有些碍手碍脚，所以如果频繁使用BCEL，那么可能需要编写一个包装器类，它可以隐藏其中一些不同之处。
Bcel provides some basic constant definitions in the org.apache.bcel package, but aside from these definitions all the inspection-related code is in the org.apache.bcel.classfile.
bcel在or g . apache . bcel包中提供了一些基本常量定义，但是除了这些定义，所有分析相关的代码都在or g . apache . bcel . classfile包中。
There are some deeper differences under the covers, including the use of two separate hierarchies of components within BCEL — one for inspecting existing code and the other for creating new code.
除了表面上的差别，还有一些更深层的区别，包括在BCEL中组件的两个不同层次结构的使用——一个用于检查现有的代码，另一个用于创建新代码。
There are some deeper differences under the covers, including the use of two separate hierarchies of components within BCEL — one for inspecting existing code and the other for creating new code.
除了表面上的差别，还有一些更深层的区别，包括在BCEL中组件的两个不同层次结构的使用——一个用于检查现有的代码，另一个用于创建新代码。
应用推荐