|Home >> All >> org >> mobicents|
org.mobicents.slee.container.management.jmx: Code for the features described in chapter 14 of the Slee spec reside here.
SbbLocalObjectImpl: This is a SLEE provided interface to the Sbb object. The SLEE uses this interface to allow sbbs to access local methods. The following is excerpted from Slee Spec An SBB may define SBB specific local interface methods in an SBB specific local interface. The SBB specific local interface must be public and must extend, either directly or indirectly, the SbbLocalObject interface. All SBBs have an SBB local interface. If the SBB Developer does not provide an SBB local interface for an SBB, then the SBB local interface of the SBB is the generic SbbLocalObject interface. The names of the SBB specific ...
SbbContextImpl: SBB Context Implementation. The SLEE provides each SBB object with an SbbContext object. The SbbContext object gives the SBB object access to the SBB object’s context maintained by the SLEE, allows the SBB object to invoke functions provided by the SLEE, and obtain information about the SBB entity assigned to the SBB object. The SbbContext object implements the SbbContext interface. The SbbContext interface declares the following methods: · Methods to access information determined at runtime. o A getSbbLocalObject method to get an SBB local object that represents the SBB entity assigned to the ...
Base64: Encodes and decodes to and from Base64 notation. Change Log: v2.1 - Cleaned up javadoc comments and unused variables and methods. Added some convenience methods for reading and writing to and from files. v2.0.2 - Now specifies UTF-8 encoding in places where the code fails on systems with other encodings (like EBCDIC). v2.0.1 - Fixed an error when decoding a single byte, that is, when the encoded data was a single byte. v2.0 - I got rid of methods that used booleans to set options. Now everything is more consolidated and cleaner. The code now detects when data that's being decoded is gzip-compressed ...
ServiceActivityImpl: Service Activity Implementation. The Administrator uses the SLEE’s management interface to activate and deactivate Services. Each Service has an associated Activity. The specific Java type for this Activity is ServiceActivity. The SLEE fires a Service Started Event on a ServiceActivity object after the Service is started. A Service is started after one of the following occurs: The SLEE is in the Running state and a ServiceManagementMBean object is invoked to activate the Service, or The SLEE becomes active when the SLEE transitions from the Starting to the Running state and the SLEE starts the ...
ResourceAdaptorEntityBinding: Zero or more resource-adaptor-entity-binding elements. Each resource-adaptor-entity-binding element binds an object that implements the resource adaptor interface of the resource adaptor type into the JNDI comp onent environment of the SBB (see Section 6.13.3). Each resource-adaptorentity- binding element contains the following sub-elements: A description element. This is an optional informational element. A resource-adaptor-object–name element. This element specifies the location within the JNDI component environment to which the object that implements the resource adaptor interface will be bound. ...
ServiceDeployer: This Deployer is used to deploy services It calls the sbb deployer class to deploy sbbs SLEE specification 1.0 section 2.3.2 : The Service Deployer understands the operational environment. The Service Deployer should know which Services have been or will be deployed into the SLEE and the external resources that are plugged into the SLEE. The Service Deployer creates a deployment descriptor element for each Service. In addition, the Service specifies the default event delivery priority of the Service’s root SBB. The Service Deployer may also have to modify the deployment descriptors of the SBBs ...
ActivityTypeEntry: See Spec Section 15.1.2 (page 240) Resource adaptor type deployment descriptor. This corresponds to the node of the resource adaptor deployment descriptor. Zero or more activity-type elements. The Java types of all the resource adaptor type’s Activity objects must be declared. Each activity-type element declares one of these Java types. Each activity-type element contains the following sub-elements: A description element. This is an optional informational element. This element should document the conditions that end Activity objects of this Java type. An activity-type-name element. This element ...
ResourceAdaptorInterfaceEntry: 15.1.2 Resource adaptor type deployment descriptor A resource-adaptor-interface element. This element is optional. It specifies the Java type of the resource adaptor interface. Each resource adaptor of this resource adaptor type provides an implementation of this resource adaptor interface, An SBB can bind an object of this Java type into its JNDI component environment using a resource-adaptor-entity-binding element in the SBB’s deployment descriptor. The resource-adaptor-interface element contains the following sub-elements: A description element. This is an optional informational element. A resource-adaptor-interface-name ...
TimerFacilityImpl: Implementation of the SLEE timer facility. timer is the timer object currently being examined. timer.scheduleTime is time that the Timer Event is scheduled to fire. timer.timeout is timeout for this timer (from TimerOptions). timer.numRepetitions is the total repetitions for this timer, 0 if infinite, 1 if non-periodic. timer.remainingRepetiton is the remaining repetition count, initially Long.MAX_VALUE for infinite periodic timers, timer.numRepetitions otherwise. timer.period is the timer period (Long.MAX_VALUE if non-periodic). timer.missed is the counter of undelivered late events.
EnvironmentEntry: Environment Entry in the SBB Deployment Descriptor. Zero or more env-entry elements. A description element.This is an optional informational element. o An env-entry–name element. This element specifies the location within the JNDI component environment to which the environment entry value will be bound. o An env-entry-value element. This element specifies the value that will be bound to the location specified by the enventry–name element. o An env-entry–type element. This element specifies the type of the value specified by the environment env-entry element.
SbbVerifier: Verify that a sbb abstract class provided by a sbb developer is following a set of constraints. This verifier checks that the sbb developer developed the Sbb Abstract class following the slee specification requirements. It verifies also that the Sbb Abstract class and the definitions provided by the sbb developer in the deployment descriptor are matching It verifies also the sbb concrete class generated by the slee runtime to check the generated byte code integrity.
ActivityContextInterfaceFactoryInterfaceEntry: 15.1.2 Resource adaptor type deployment descriptor (page 240) An activity-context-interface-factory-interface element. This element is optional. It contains the following sub-elements: A description element. This is an optional informational element. An activity-context-interface-factory-interface-name element. This element identifies the interface name of the Activity Context Interface Factory of the resource adaptor type.
ActivityContextInterfaceImpl: Activity context interface - default implementation. The Sbb deployer has to imbed an instance of this as a proxy object in each sbb ACI. This is the SLEE wrapper data structure for Activity Contexts. The Sbb gets to access this rather than the activity. The reason this exists is because the activity context can be at a different location than the activity context interface (does not need to be co-located in the same jvm. )
DeploymentManager: The DeploymentManager class is where all deployment starts. Using it comes down to calling the deployUnit method by handing it an url pointing to the location of a deployable unit jar. The jar would then be copied to a the location pointed by the value of the system property: org.mobicents.slee.container.management.deployment.DEPLOYMENT_DIRECTORY and would be installed in the SLEE.
ProfileCMPMethod: Declares the presence of the get Profile CMP method and associates the method with a Profile Specification. This SBB Developer specifies the following aspects of the get Profile CMP method using the get-profile-cmp-method element: · - The method name of the get Profile CMP method. · - The Profile Specification of the get Profile CMP method.
InstalledResourceAdaptor: Represents an Installed resource adaptor. Is indexed in the SleeContainer using the ComponentKey of the resource type. Each Resource adaptor type maps to 0 or more resource adaptor IDs Each resource adaptor ID maps to 0 or more installed resource adaptor entities. ResourceAdaptorType ->* ResourceAdaptorID ->* resourceAdaptorEntities.
ResourceAdaptorType: An object that tracks all the resource adaptors for a given resource adaptor type id. There can be multiple resource adaptors given a resource adaptor type. There can be multiple resource adaptor entities for a given resource adaptor. This structure maps a given resource adaptor type to multiple resource adaptor IDs.
ServiceComponent: This represents the service component - the static part of a service including the descriptor and service state. This resides in the deployment cache. The state in this object is persisted to disk and must survive SLEE restarts. This structure includes the UsageMBeans and pointer to the Service Descriptor.
SbbAbstractDecorator: Class decorating the sbb abstract class. The byte code is modified IF necessary to trap SBB code that violates the SLEE 1.0 spec: 1) write access to java:comp/env 2) new Thread() TODO: Currently we check the SBB abstract class itself, but not its ascendands or utility classes it uses.
ServiceUsageMBeanImpl: See SLEE 1.0 #14.9. The ServiceUsageMBean interface defines the management interface used to interact with SBB usage parameter sets for SBBs in a Service. It defines the methods to create, lookup, and remove SBB usage parameter sets from SBBs in the Service.
DeployableUnitDeployer: An instance of this class is created for every deployable unit that is installed in the slee. Use of this class goes through the static deploy . It then creates a UnitDeployer instance that corresponds the jar file passed to deploy .
SbbEntityFactory: SbbEntityFactory -- implements a map from SBB Entity Id to SBB Entity instances. This is the sole place where Sbb Entities are created and destroyed. We keep a map of SBB Entity ID to SBB Entity here and return Sbb Entities that are stored in this map.
ComponentContainer: The ComponentContainer interface represents entity that, based on a ComponentDescriptor, install a component in the slee (e.g. Such an implementation is the SleeContainer for example). This is an implementation interface -- will be removed.