How CCM event model is related to Notification Service?
CCM event model can be integrated with Notification Service to provide highly scalable and available asynchronous messaging infrastructure to CORBA components. The event sources known as emitter and publisher port may use notification channel as explained in previous FAQ to produce events. The consumer port can be configured to be proxy consumer to receive event from arbitrary number of event sources. Container uses subset of Notification Service APIs to integrate with Notification Service and generates context APIs to push or receive events. The container may provide required configuration for setting up shared event channels and event filters if necessary.
Related Questions
- What are the advantages to have four types of components (Service, Entity, Session, Process) in CCM model instead of only two in EJB model (Entity, Session)?
- What is the difference between TAOs Real-Time Event Service and the OMG Notification Service?
- How CCM event model is related to Notification Service?
