OSOTrigger Bundle
Once the system is launched OSAMI trigger (OSOTrigger) starts the sequence of calls; Presence is invoked in the first place and when the orchestrator receives the Bluetooth devices immediately request permission to proceed to the XMPP Server. If it denies the execution an informing message is returned but if it doesn’t, then OSO (OSAMI Service Orchestration) is automatically triggered.
The main packages are defined in the following table:
OSOTrigger bundle packages
| Packages
| Description
|
| org.vodafone.osami.osotrigger
| This package contains the bundle activator
|
| org.vodafone.osami.osotrigger.service
| This package contains the service interface
|
| org.vodafone.osami.osotrigger.service.impl
| This package contains the service implementation
|
OSOTrigger bundle class diagram
This package is composed of the next classes:
OSOTrigger bundle classes
| Classes
| Description
|
| org.vodafone.osami.osotrigger.Activator
| The activator registers the service so it can be accessed from other bundles
|
| org.vodafone.osami.osotrigger.service.OSOTrigger
| Service interface
|
| org.vodafone.osami.osotrigger.service.impl.OSOTriggerImpl
| This class implements the request to the Web Service, handles the response and returns it.
|
Manifest Definition
This file just contains the bundle configuration, as well as some other features like dependencies, exports and imports.
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: OSOTrigger
Bundle-SymbolicName: org.vodafone.osami.OSOTrigger
Bundle-Version: 1.0.0.qualifier
Bundle-Activator: org.vodafone.osami.osotrigger.Activator
Import-Package: com.vodafone.google.presence,
org.osgi.framework;version="1.3.0",
org.vodafone.osami.oso.service,
org.vodafone.osami.presence.service,
org.vodafone.osami.xmpp.service
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Export-Package: org.vodafone.osami.osotrigger.service
|
Subscribe to News
