CodeStreet Messaging Framework

 


A White Paper

Author: Jawaid Hakim

Published: January 13, 2006

 

 

 

 

 



Abstract

 

Message oriented middleware, such as TIBCO Rendezvous and JMS, is a popular foundation for distributed systems.  But the advantages of messaging for building such decoupled systems are also weak points: mismatches between message specifications and code can occur, type safety issues arise, and different teams develop varying understanding of message semantics. The CodeStreet Messaging Framework addresses many of these problems by providing transparency (XML message specifications), type-safety (generated message classes), a host of critical features (extended data types, message validation, etc.), and flexibility (converter classes).

 

 


 

1.      Introduction.. 3

2.     The Message Creation Process. 4

3.     XML Message Specification.. 4

3.1.        Field ConstraintsField Constraints. 5

3.2.        Fixed and Default Field Values. 6

3.2.1.     Optional Fields 6

3.3.        Tagged Fields. 7

3.4.        JMS Property Fields. 8

3.5.        ‘Send’ Subject Specification.. 8

3.5.1.     Request/Reply 9

3.5.2.     Request/Reply 9

3.6.        Extended Field Types. 10

3.7.        Inheritance.. 10

3.8.        Containment.. 11

4.     Message Validation.. 11

5.     Converter.. 11

5.1.        ConverterTibrv.. 12

5.2.        ConverterTibaerv..