Container-managed messaging (CMM) allows a Java component to communicate via messaging without having to manage the messaging infrastructure, similarly to how container-managed persistence (CMP) allows an EJB (Enterprise JavaBean) to have persistent data without managing access to a data store. In addition, messaging parameters (such as destinations, mode of interaction, time-outs, etc.) can be defined declaratively in a deployment descriptor. The programming model used in CMM resembles that of CORBA messaging with the exception that it is in an anonymous and declarative fashion.
Index Terms:
electronic messaging; software architecture; Java; subroutines; distributed object management; object-oriented programming; persistent objects; container-managed messaging; Java components; message-oriented applications; software architecture; messaging infrastructure; container-managed persistence; Enterprise JavaBeans; persistent data; messaging parameters; message destinations; interaction mode; time-outs; declarative definition; deployment descriptor; anonymous declarative programming model
Citation:
I. Silva-Lepe, C. Codella, P. Niblett, D. Ferguson, "Container-Managed Messaging: An Architecture for Integrating Java Components and Message-Oriented Applications," tools, pp.228, 37th International Conference on Technology of Object-Oriented Languages and Systems (TOOLS-37'00), 2000