blocks|key|1859659|text|您始终可以将它们从数据库(或其他任何位置)下载到某个本地位置，然后将它们动态安装到OSGi框架中。您需要为框架提供的只是包的文件系统路径。当然，你必须自己编写所有的胶水代码。另一方面，如果您使用的是Eclipse+P2，那么得益于自动配置，您可能会有更大的灵活性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1859660|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You could always download them from database (or whatever) into some local location and then install them dynamically into the OSGi Framework. All you need to give to the framework is the filesystem path of the bundle. Of course, you will have to write all the glue code for this yourself. On the other hand, if you are using Eclipse P2, you might have some more flexibility thanks to the automated provisioning.

blocks|key|1994183|text|看看PAX+URL项目：http://wiki.ops4j.org/display/paxurl/Documentation|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1994184|这演示了加载OSGi包的关注点与它的存储方式的分离。从理论上讲，我没有看到使用数据库作为捆绑存储的任何主要障碍，尽管我也没有看到任何明显的优势。|1994185|对于捆绑包版本，您需要一些机制来确定要加载哪些捆绑包(和版本)。您可以将包与版本信息一起存储在数据库中，否则如何存储同一包的不同版本？|1994186|entityMap|0|LINK|mutability|MUTABLE|url|http://wiki.ops4j.org/display/paxurl/Documentation^0|C|1E|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

Have a look at the PAX URL project: <a href="http://wiki.ops4j.org/display/paxurl/Documentation" rel="nofollow noreferrer">http://wiki.ops4j.org/display/paxurl/Documentation</a>

That demonstrates the separation of concerns of loading an OSGi bundle from how it is stored. In theory, I don't see any major impediment to using a database as the bundle store, though I also don't see any obvious advantages.

To your point on the bundle versions, you need some mechanism to identify which bundles (and versions) to load. You would store the bundles in the database with version information, otherwise how would you store different versions of the same bundle?

blocks|key|586079|text|一个简单的解决方案是创建您自己的引导包，它将从数据库(或其他位置)提供所有其他包。OSGi允许您从任意的InputStream安装包，因此将其插入到您想要的任何源(例如JDBC)中应该是相当容易的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|586080|更多详情请参见BundleContext.installBundle()方法。|586081|您不应该寻找“回调”，框架将通过“回调”通知您“何时需要加载所需的依赖项”，因为自动依赖项管理(ala+Maven)不是核心OSGi功能的一部分(尽管可以通过使用OBR等服务来实现)。|586082|entityMap|0|LINK|mutability|MUTABLE|url|http://www.osgi.org/javadoc/r4v42/org/osgi/framework/BundleContext.html#installBundle%2528java.lang.String,%2520java.io.InputStream%2529|1|http://felix.apache.org/site/apache-felix-osgi-bundle-repository.html^0|1G|B|0|7|T|7|T|0|0|29|3|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|H|3|I|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|J|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]|R|$5|M|N|O|E|$P|S]]]]

A simple solution is to create your own bootstrap bundle that will provision all other bundles from a database (or other location). OSGi allows you to install bundles from an arbitrary <code>InputStream</code> so it should be reasonably easy to plug this into whatever source you want (e.g. JDBC). 

See <a href="http://www.osgi.org/javadoc/r4v42/org/osgi/framework/BundleContext.html#installBundle%28java.lang.String,%20java.io.InputStream%29" rel="nofollow noreferrer"><code>BundleContext.installBundle()</code></a> method for more details.

You should not be looking for a "callback" through which the framework would notify you "when it needs to load a required dependency" since automatic dependency management (ala Maven) is not part of the core OSGi functionality (although can be achieved by using services like <a href="http://felix.apache.org/site/apache-felix-osgi-bundle-repository.html" rel="nofollow noreferrer">OBR</a>).

blocks|key|559538|text|鉴于加载机制本质上与URL一起工作，我建议尝试自定义URL处理程序。从逻辑上讲，在使用此处理程序加载任何包之前，您需要加载并激活它，否则我认为它应该可以工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|559539|请参阅R4+OSGi核心规范中的"URL处理程序服务规范“。|559540|Glassfish+is+using+this+approach+to+install+webapp+bundles+btw.|offset|length|559541|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.java.net/blog/2009/06/04/osgi-enabled-web-applications-inglassfish^0|0|0|0|1M|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

Given that the loading mechanism essentially works with an URL, I would suggest to 
try a custom URL handler. Logically you will need to load and activate it before loading any bundles using this handler, otherwise I think it should work.

See the "URL Handlers Service Specification", R4 OSGi Core Specification.

<a href="http://weblogs.java.net/blog/2009/06/04/osgi-enabled-web-applications-inglassfish" rel="nofollow noreferrer">Glassfish is using this approach to install webapp bundles</a> btw.

Do i need to supply a custom ClassLoader ? Thinking out loud this does not appear to be the right approach because inside the classloader one does not know the required version.

I want to load my OSGI jar files from a database or other source

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我需要提供自定义的ClassLoader吗？考虑清楚，这似乎不是正确的方法，因为在类加载器中，一个人不知道所需的版本。

问我想从数据库或其他源加载OSGI jar文件
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我想从数据库或其他源加载OSGI jar文件EN