配置文件类和列举在这个释放中是不被支持的；因此，它们不会显示在这个向导中。
Profile class and enumerations are not supported in this release; therefore, they do not show up in the wizard.
指定*。类将包括所有的文件类的扩展。 你应该使用这个只有当你知道你需要的一切。
The . jar file need only the . class needed EDIT: In this case, the * include all . class files.
首先，创建一个RequisitePro项目中的RequisitePro文件类的元素种类。
First, an element type for the RequisitePro document types in the RequisitePro project is created. The element type will.
编译器接受每一个方面，并建立包含通知代码的类文件。
The compiler takes each aspect and creates class files that contain the advice code.
如果您选择复制这个结构，可以重用稍后提到的批处理文件和类路径，也可以选择使用您自己的策略。
If you choose to replicate this structure, you can re-use the batch file and class paths mentioned later or choose to go with your own strategy.
只要映射文件在类路径中存在，那么它们就可以打包在任何JAR中(甚至松散打包)。
Mapping files can be packaged in any JAR (or even packaged loosely) as long as they are available in the classpath.
该提供程序配置属性文件包含实现类。
This provider configuration properties file includes the implementation classes.
成功编译之后将产生类文件。
使TLD文件和处理程序类可访问。
IBMi消息、消息队列和消息文件通过消息类访问。
IBM I messages, message queues, and message files are accessed using the message classes.
JAAS配置文件指定这个类使用的登录模块。
The JAAS configuration file specifies the login module to use for this class.
不必重新编译类文件。
第一步是手动地确认所有类文件的位置。
The first and foremost step is to manually validate the locations of all of your class files.
每次您更改文件、类或方法，Eclipse 都会在其本地历史记录中记录更改。
Each time you change a file, class, or method, Eclipse records the change in its local history.
它们可以是对文件系统、类路径、源代码管理系统或WebURL的引用。
These can be references to the file system, class path, source code control system, or Web URLs.
这个基于JSFPhaseListener接口的特性会使得所有的配置文件和类被重载。
This feature, based on JSF PhaseListener interface, causes all the configuration files and classes to be reloaded.
IntegratedFileSystem中的文件通过文件系统类访问。
Files in the Integrated file system are accessed using the file system classes.
根据plugin .xml文件，transformeditorplugin类提供插件编辑功能。
As specified in the plugin.xml file, the TransformEditorPlugin class provides the plug-in editing function.
此时应该看到添加的文件(域类和对应的集成测试)。
You should see the files added (both the domain class and the corresponding integration test).
但是，如果类装入器为它所装入的每个类查找现有类文件，那么它会如何工作呢？
But how can that work if the class loader looks for existing class files for each class it loads?
对于这些层次，个别的工具能够提供某种粒度上的一系列变更，不论是文件、包、类或某些更细粒度的类别。
For these levels, the respective tool is able to provide a list of changes at some granularity, whether that is file, package, class, or some finer category.
因为代码可以在任何环境中执行，所以类文件可能与代码编译时不同。
Because the code can execute in any environment, the class files might not be the same as when the code was compiled.
必须手动将所有这些依赖JAR文件和属性文件放入类路径中。
You have to put all those dependent JAR files and property files into the class path manually.
在默认源代码中使用类路径的地方，可以用查询类文件的其他路径或者其他访问类信息的方法替换。
You can substitute other paths for looking up class files, or other ways of accessing class information, in place of the default source that USES the classpath.
它们三个的源文件和类文件可以在本文中附带的代码包中找到。
The source and class files for all three can be found in the code package that accompanies this article.
您可以将JAR文件或实际的包文件夹和类文件放到这个目录下。
You can place either the JAR file or the actual package folders and class files into this directory.
您可以在这一视图上进行大多数开发工作，而资源视图更便于处理文件而不是源代码和类文件。
This perspective is where you'll do most of your development, although the Resource perspective comes in handy for dealing with files other than source and class files.
如果在创建之后更改名称，则可能需要重新生成强类型数据集的类文件，因为类和方法不会更新它们的名字以反映新的名称。
If you change the name after you create it, you may want to regenerate the strongly typed DataSet's class file as the classes and methods will not update their names to reflect the new names.
用于存储AOT代码的JXE 文件通常要比存放类文件的JAR 文件大很多，这是因为本地代码一般要比存储在类文件中的字节码密度小。
The JXEs used to store AOT code are generally much larger than the JAR files that hold the class files because native code is generally less dense than the bytecodes stored in class files.
用于存储AOT代码的JXE 文件通常要比存放类文件的JAR 文件大很多，这是因为本地代码一般要比存储在类文件中的字节码密度小。
The JXEs used to store AOT code are generally much larger than the JAR files that hold the class files because native code is generally less dense than the bytecodes stored in class files.
应用推荐