Changes to the Blether persistence configuration.
Blether持久性配置的更改。
Moving the Blether service into the persistence bundle.
将Blether服务迁移到持久性捆绑包中。
Migration Stage 1: Packaging Blether as an OSGi application
迁移阶段1：将Blether 打包为一个OSGi应用程序
Listing 18 shows a sample manifest for the Blether application.
清单18显示Blether应用程序的一个样例清单。
In their place, you want a single lookup for the Blether service as shown in Listing 10.
在其位置中，您希望为Blether服务执行一个查询，如清单10所示。
HttpRequestHandlerServlet represents the only servlet used by Blether from the perspective of the Web descriptor.
从Web描述符的角度来看，HttpRequestHandlerServlet代表Blether使用的惟一servlet。
This lookup is unambiguous because OSGi applications are isolated and Blether defines only a single persistence unit.
该查询不含糊，因为OSGi应用程序是孤立的且Blether仅定义单一持久性单元。
In the case of the Blether persistence JAR, the conversion is straightforward and so it is not necessary to use the tool.
对于Blether持久性JAR，转换简单明了，因此没必要使用工具。
Describing the changes to the files necessary to refactor the Blether code would add no value to this article, as the IDE takes care of them for you.
描述重构Blether代码所需的文件更改对于本文来说没有任何价值，因为IDE会为您料理这一切。
However, the Blether service actually exists in the OSGi service registry and Blueprint defines a more direct way to use a service from OSGi service registry with the reference element.
但是Blether服务实际上存在于osgi服务注册表，且Blueprint定义了一种更直接的方式，通过引用元素使用来自osgi服务注册表的服务。
However, the Blether service actually exists in the OSGi service registry and Blueprint defines a more direct way to use a service from OSGi service registry with the reference element.
但是Blether服务实际上存在于osgi服务注册表，且Blueprint定义了一种更直接的方式，通过引用元素使用来自osgi服务注册表的服务。
应用推荐