Messaging Middleware
Messaging Middleware:
A messaging server is a middleware program that handles messages that are sent for use by other programs using a messaging application program interface (API). A messaging server can usually queue and prioritize messages as needed and saves each of the client programs from having to perform these services. Messaging and messaging servers usually are organized in one or both of two models: point-to-point messaging and subscribe/publish messaging.
From: http://searchwinit.techtarget.com/gDefinition/0,294236,sid1_gci214556,00.html
MessageForge
The framework dramatically enhances the productivity of development teams by providing an open XML-based message definition and code generation facility. The transparency of XML message definitions allows all participants - technical and business - to participate in a development effort. A well-defined XML-Schema is provided to aid the development team in the construction of message definitions.
Since code is automatically generated from the XML message definitions, all team members are guaranteed to have a package of type-safe message classs. Any changes to the XML message definitions can be easily propagated throughout the application by simply re-running the code-generator.
A field within a message can be any valid Java (C#) primitive data type. In addition, the framework supports collections (arrays and hashtables), and nested messages. A nested message can be any other valid message. Field level constrains are also supported. Currently, the framework allows min/max and enumeration constraints to be set of fields.
The framework provides a number of converters in order to marshall/unmarshall to/from other message representations. Currently, the framework provides converters for TIBCO/RV , XML, and JMS .
Loading .....