5.2.2. Application Context Service Publication
Once the application context creation for a bundle has completed, the application context object is
automatically exported as a service available through the OSGi Service Registry. The context is published
under the interface org.springframework.context.ApplicationContext (and also all of the visible
super-interfaces and types implemented by the context). The published service has a service property named
org.springframework.context.service.name whose value is set to the bundle symbolic name of the bundle
hosting the application context. It is possible to prevent publication of the application context as a service using
a directive in the bundle's manifest. See Section 6.1, “Bundle Format And Manifest Headers” for details.
Note: the application context is published as a service primarily to facilitate testing, administration, and
management. Accessing this context object at runtime and invoking getBean() or similar operations is
discouraged. The preferred way to access a bean defined in another application context is to export that bean as
an OSGi service from the defining context, and then to import a reference to that service in the context that
needs access to the service. Going via the service registry in this way ensures that a bean only sees services
with compatible versions of service types, and that OSGi platform dynamics are respected.
5.3. Bundle Lifecycle
OSGi is a dynamic platform: bundles may be installed, started, updated, stopped, and uninstalled at any time
during the running of the framework.
When an active bundle is stopped, any services it exported during its lifetime are automatically unregistered
and the bundle returns to the resolved state. A stopped bundle should release any resources it has acquired and
terminate any threads. Packages exported by a stopped bundle continue to be available to other bundles.
A bundle in the resolved state may be uninstalled: packages that were exported by an uninstalled bundle
continue to be available to bundles that imported them (but not to newly installed bundles).A bundle in the
resolved state may also be updated. The update process migrates from one version of a bundle to another
version of the same bundle.
Finally of course, a resolved bundle can be started, which transitions it to the active state.
The diagram below represents the bundle states and its transitions:
Bundles and Application Contexts
Spring Dynamic Modules(1.2.1) 11
剩余108页未读，继续阅读
答疑-定制-运维找我
- 粉丝: 42
- 资源: 34
我的内容管理
展开
最新资源
- 最优条件下三次B样条小波边缘检测算子研究
- 深入解析：wav文件格式结构
- JIRA系统配置指南：代理与SSL设置
- 入门必备：电阻电容识别全解析
- U盘制作启动盘：详细教程解决无光驱装系统难题
- Eclipse快捷键大全：提升开发效率的必备秘籍
- C++ Primer Plus中文版：深入学习C++编程必备
- Eclipse常用快捷键汇总与操作指南
- JavaScript作用域解析与面向对象基础
- 软通动力Java笔试题解析
- 自定义标签配置与使用指南
- Android Intent深度解析：组件通信与广播机制
- 增强MyEclipse代码提示功能设置教程
- x86下VMware环境中Openwrt编译与LuCI集成指南
- S3C2440A嵌入式终端电源管理系统设计探讨
- Intel DTCP-IP技术在数字家庭中的内容保护
资源上传下载、课程学习等过程中有任何疑问或建议，欢迎提出宝贵意见哦~我们会及时处理！
点击此处反馈
