Apache ACE可以与哪些非OSGI目标一起使用 [英] What are the non-osgi targets with which Apache ACE can work

问题描述

Apache Ace文档指出，它可以对其他类型的目标(非OSGi容器或完全不同的目标")进行软件配置.但是没有有关非OSGi目标的文档.

Apache Ace documentation refers that it can do software provisioning to other types of targets "non-OSGi containers, or something completely different target". But no documentation is available regarding non-OSGi target.

请问有一些非OSGi目标的示例，Apache Ace可以对这些目标进行软件配置.另外，目标与Apache ACE一起使用的最低要求是什么.

Can I have some examples of non-OSGi targets to which Apache Ace can do software provisioning. Also, what are the minimum requirement for a target to work with Apache ACE.

谢谢

推荐答案

我见过人们创建的非OSGi目标的一些示例是:

Some examples of non-OSGi targets that I have seen people create are:

• 使用可以以编程方式安装.APK文件的资源处理器将Android应用程序移动设备上.
• 再次使用资源处理器的Windows桌面应用程序被安装在用户的台式计算机上.
• 内核模块，配置和其他文件，数据库架构等

所有这些都可以通过创建适当的资源处理器来实现.简而言之，资源处理器只是一个OSGi捆绑软件，它与所提供的资源一起提供.两者都到达目标，在该目标处处理器用于以某种方式安装资源.该机制使您可以使用新的文件类型扩展预配置系统.

All of these can be implemented by creating the appropriate resource processor. In short, a resource processor is just an OSGi bundle that gets shipped alongside the resources that are provisioned. Both arrive at the target, where the processor is used to somehow install the resource. The mechanism allows you to extend the provisioning system with new file types.

您可以使用的另一个非OSGi目标是PojoSR.这有点不同.使用特殊的后处理器软件包，ACE可以(而不是交付部署软件包)创建可执行的JAR文件，其中包含PojoSR框架和您配置的软件包.您可以在任何地方获取并运行此jar.主要在通常无法运行OSGi的环境中很有意思.

Another non-OSGi target you can use is PojoSR. This works a bit differently. With a special post processor bundle, ACE can, instead of delivering deployment packages, create an executable JAR file that contains the PojoSR framework and the bundles you configured. You can fetch and run this jar anywhere. Mainly interesting in environments where normally you could not run OSGi.

我看到的另一件事是部署到Apache Celix(这是C中的OSGi实现).他们实际上已经实现了可以与ACE对话的概念验证管理代理，并且可以提供带有C代码的捆绑软件，方式.

Yet another thing I've seen being done is deploying to Apache Celix, which is an OSGi implementation in C. They have actually implemented a proof of concept management agent that can talk to ACE and they can provision bundles with C code that way.

关于最低要求:

我们试图使管理代理与基本的OSGi执行环境兼容，这意味着我们避免使用任何Java 5+功能.它确实需要与R4兼容的OSGi实现，但R3太旧了，因为它不支持DeploymentAdmin(这是我们使用的配置机制的基础).

We try to keep the management agent compatible to the basic OSGi execution environment, meaning we refrain from using any Java 5+ features. It does need an R4 compatible OSGi implementation though, R3 is too old as it does not support DeploymentAdmin (which is the basis for the provisioning mechanism we use).

这篇关于Apache ACE可以与哪些非OSGI目标一起使用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！