2009
DOI: 10.1007/978-1-4302-1613-1
|View full text |Cite
|
Sign up to set email alerts
|

Pro Spring Dynamic Modules for OSGi™ Service Platforms

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
10
0

Year Published

2011
2011
2017
2017

Publication Types

Select...
5
3

Relationship

0
8

Authors

Journals

citations
Cited by 10 publications
(10 citation statements)
references
References 0 publications
0
10
0
Order By: Relevance
“…The dynamic nature of the OSGi means that the bundles can be installed, started, stopped, and uninstalled without the necessity to restart the OSGi framework [4]. For this purpose, the OSGi framework runtime provides standard methods [2] for the exploration of the bundle's context (i.e., environment) and the control of its life cycle.…”
Section: A Basic Notionsmentioning
confidence: 99%
“…The dynamic nature of the OSGi means that the bundles can be installed, started, stopped, and uninstalled without the necessity to restart the OSGi framework [4]. For this purpose, the OSGi framework runtime provides standard methods [2] for the exploration of the bundle's context (i.e., environment) and the control of its life cycle.…”
Section: A Basic Notionsmentioning
confidence: 99%
“…In case we use Equinox 5 as the target execution platform, all components (business logic components and proxy components) are implemented as OSGi bundles (Spring Dynamic Modules) [30]. In OSGi service platforms, there are two ways to declare and bind services via interfaces (ports): declaring/binding exported services in Spring osgi-context.xml files, or in the source code by overriding the method start of BundleActivator class of OSGi bundle.…”
Section: Osgi (Equinox) As the Target Adaptive Execution Platformmentioning
confidence: 99%
“…These are clouds whose infrastructure is open for the general public. Google AppEngine (Zahariev, 2009), Microsoft Windows Azure (Hill et al, 2010) and Amazon's Beanstalk (van Vliet, Paganelli, van Wel and Dowd, 2011) are the most well-known and used representatives of this kind of PaaS. Although public clouds are widely used, they present some drawbacks: the developer must adapt every application deployed onto them to their APIs and special requirements, and security and privacy data concerns can render those solutions unfeasible in some contexts.…”
Section: Paas Solutionsmentioning
confidence: 99%
“…For the logical components (following the OSGi and Spring DM (Rubio, 2009) specifications) we have defined a virtual appliance containing the JVM (Java Virtual Machine), the OSGi framework and all required libraries. The repository components can be directly deployed on top of this platform.…”
Section: Repository Architecturementioning
confidence: 99%