| Home >> All >> org >> mobicents >> slee >> [ container Javadoc ] |
• org.mobicents.slee.container: Javadoc index of package org.mobicents.slee.container.
Package Samples:
• org.mobicents.slee.container.management.jmx: Code for the features described in chapter 14 of the Slee spec reside here.
• org.mobicents.slee.container.xml
• org.mobicents.slee.container.service
• org.mobicents.slee.container.profile
• org.mobicents.slee.container.management.xml
• org.mobicents.slee.container.management
• org.mobicents.slee.container.deployment
• org.mobicents.slee.container.deployment.interceptors
Classes:
• 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 ...
• 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.
• 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.
• 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 .
• 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.
• SbbIDImpl: SBB Component Identifier. This the key to located the loaded Sbb class in the service container. Note that an SBB may be referenced by multiple services. We cannot remove an Sbb until all services no longer reference the sbb.
• XMLConstants: Contains all strings used when parsing xml. I'm using a simple naming convention for variable names which is as follows: _ND - for node names _AT - for attribute names
• SbbDescriptorImpl: This class contains the information about the Sbb Component extracted from the deployement descriptor. This is the class that gets filled in by the Sbb deployment descriptor parser.
• Service: Service implementation. This is the run-time representation of the service Represents an instance of a Slee Service. Note that in the SLEE, the Service is a management artifact.
• MappingManager: Read an xml file to provide the managers (method call interceptors) that will be used to handle calls done on methods on sbb concrete class generated by the slee.
• SleeContainer: Implements the SleeContainer. The SleeContainer is the anchor for the Slee. It is the central location from where all other major data structures are accessible.
• ServiceDeployer: Instances of this class represent DU components or in other words - JAR file entries contained in a deployable unit jar such as SBBs, Profiles, RA Types and etc.
• AbstractComponentDeployer: Instances of this class represent DU components or in other words - JAR file entries contained in a deployable unit jar such as SBBs, Profiles, RA Types and etc.
• ServiceDescriptorImpl: Implements the Deployment descriptor information parsed from the service.xml file. Note that the set methods of this class are to be ivoked by the XML parser.
• SleeLifecycleMonitorMBean: Helper MBean for Slee Lifecycle control. Used by SleeManagementMBean to distinguish between external request for SLEE stop() vs. mobicents.sar redeployment.
• ServiceShutdown: ServiceShutdown task. This waits and cleans up the service state and removes sbb entities from the cache when the service shuts down.
• SleeProfileManager: This class is used by the SLEE to manage Profiles. It calls out to the jboss-cache that put everything into the backend storage
• ConcreteActivityContextInterfaceGenerator: Class generating the concrete activity context interface class from the activity context interface provided by a sbb developer
• DeployableUnitDescriptorImpl: The DeployableUnitDescriptor interface defines the interface of a Java object that describes an installed deployable unit.
| Home | Contact Us | Privacy Policy | Terms of Service |