但对于用户加载的问题，这是不是一种选择。
解决了在DSP提供的地址线少于异步存储器地址线的情况下，实现并行加载的问题。
The parallel booting problem, which occurs when the number of the address lines provided by DSP is less than that of the asynchronous memory, is also solved.
所以，剩下的问题就是如何获取这些测试定义、如何将它们加载到DOH的UI 中以及如何执行它们。
So, the question that remains is how do you take these test definitions, load them into the DOH's UI, and execute them.
毫无疑问，如果这个链条中的任何一个插件不能成功加载，那么依赖它的插件就可能会出现问题。
No doubt, then, that if any plug-in in this chain fails to load successfully, the dependent plug-ins may have problems.
这样做，一旦加载了错误的类或错误版本的类，就会出问题。
It will cause problems when you load the wrong class or the wrong version of a class.
类加载被沙箱化到每个捆绑包，因此日志记录框架这样的依赖项在捆绑包之间即使不同也不会导致问题。
Class loading is sandboxed to each bundle, so dependencies such as logging frameworks can be different between bundles without causing problems.
因为每个匿名类都有一个唯一的名称，因此在加载该类是不会有问题的，而这样做的结果是，应用被实时动态地更新了。
As each anonymous class has a unique name there are no issues loading it and as a result the application is updated on-the-fly.
不过，问题是加载证书的函数并没有请求使用加密证书的密码。
The trouble, though, is that the functions that load the certificates do not ask for a password for encrypted certificates.
问题是，您忽略了延迟加载内容（或太过复杂而不能考虑这个选项），特别在构建中包括所有小部件的情况下。
The problem is that you negate (or make it extremely complicated to) lazy load content, especially if you include all your widgets as part of a build.
如果数据是像页面那样被静态加载的，这不成问题。
That's not a problem when the data is loaded in a static way, as this page is.
通过下面的示例代码来了解一下延迟加载所面对的问题及解决办法。
Let us take a sample code to see the issues faced using lazy loading and a solution to overcome it.
JPA允许通过注释来“懒散地”加载属性，但正如我们在后面看到的，当考虑到实体是一个POJO时，此方法自身也有问题。
JPA allows for "lazily" loading the properties through annotation, but as we will see in a later point, this approach creates its own problems when coupled with thinking that the entity is a POJO.
由于can notmount rootfs错误主要是由设备顺序造成的，更改设备顺序或者更改驱动器加载顺序将解决此问题。
Since the cannot mount rootfs error is mostly caused by device order, changing the device order or changing the driver loading sequence will solve this problem.
应用程序试图通过调用带有MAP_ FIXED标志的mmap从绝对地址加载代码时会产生一个相关问题。
A related problem is caused by applications that try to load code at an absolute address by calling mmap with the flag MAP_FIXED.
下列IBM 技术札记（technote）谈到了加载一个表时运行RUNSTATS可能碰到的问题。
The following IBM technote talks about a possible problem that may be encountered with RUNSTATS when loading a table.
之前我们就提到，这通常是由不兼容的Jar文件或其他库以及类加载问题所引起的。
We mentioned earlier that usually this is caused by incompatible Jar files or other library and class loading issues.
这一协议表示一个潜在的安全问题；因此，NFSv4用内部RPC调用替换这一辅助mount 协议，来管理加载点。
This protocol represents a potential security issue; therefore, NFSv4 replaces this ancillary mount protocol with internal RPC calls for managing the mount point.
幸运的是，如果您刚刚开始接触Linux引导加载，使用哪个都不会有太大问题。
Fortunately, if you are new to the world of Linux boot loading, you won't go far wrong with either.
这些影响可能小到只是影响某个页面的加载或表单保存，也可能是产生难以检测的问题，或者产生只在特定条件下才会出现的错误。
The effects may be as simple as a page not loading or a form not saving, or could also be something hard to detect or only shows up under certain circumstances.
当我能够不出任何问题地加载并运行他们的工程时，评分就更简单了。
Grading is much easier when I can load and run their projects without any problems.
延迟抓取的另一个问题就是在获取到请求的数据前要一直打开数据库连接，否则应用就会抛出一个延迟加载异常。
Another issue with lazy fetching is that the database connection has to be retained until all the required data is fetched else the application will throw a lazy loading exception.
这样做的最大问题是新型的处理器很可能加载此DTDURL，而这可能是一种不必要的网络操作。
The biggest problem with this was that a naive processor is likely to load that DTD URL, which might be an unwanted network operation.
我并不会尝试解决所有的核心问题，例如“加载浏览器url”或者“告诉我什么时候我的应用能够运行”。
I'm not trying to solve all the nitty-gritty problems across devices like "launch a browser URL" or "tell me when my app code can start".
这一点，再加上每个应用服务器中的不同类加载器实现，会为迁移带来潜在的问题。
This, combined with the different class loader implementations in each application server, can potentially create problems when migrating.
动态类加载是动态jit编译器面临的一个挑战，也是AOT编译的一个更重要的问题。
Dynamic class loading, which is a challenge for the dynamic JIT compiler, is an even more significant issue for AOT compilation.
如果尚未收到css更新，而使用它们的更新页面已经被加载，那么很可能出现问题。
This can be especially problematic if CSS updates are not received when updated pages that use them are loaded.
不过这种方式重新加载类存在一个普遍问题，即类的新老版本可能同时存在，框架必须小心处理这一问题。
A general problem with reloading classes this way is, that the old and new class versions are available at the same time and have to be carefully handled by the framework.
不过这种方式重新加载类存在一个普遍问题，即类的新老版本可能同时存在，框架必须小心处理这一问题。
A general problem with reloading classes this way is, that the old and new class versions are available at the same time and have to be carefully handled by the framework.
应用推荐