Transparent message definitions

Development and management of your messages is controlled by creating XML message definitions. These XML definitions are used by the framework's code generator to create JAVA (C#) classes.


A new message definition can inherit from an existing message definition by specifying the extends keyword. This is true inheritance.


A message can include sets of common fields. These common fields are defined in separate XML files. This facility will be familiar to C++ developers where a header file can be included into a compilation module.

Flexible field types

Messages can have primitive fields (String, int, float, etc.), collections of primitive fields, nested messages, and collections of nested messages.The framework also provides full support for data types supported by JMS and TIBCO/RV . Finally, any application bean clas may be used as a field.

Field level constraints

Message fields can have constraints . Currently, simple min/max and enumeration constraints are supported. Constraints are enforced at at run time each time a field is set.

Send subject specification

The send subject (topic) of a message can be specified within the message definition. The subject specification can either be fixed or parameterized.

Automatic code generation

Code generator processes all message definitions and generates JAVA (C#) classes.


For more details see the whitepaper .