[jboss-dev-forums] [Design of JBoss ESB] - Re: Overview of Messages in 4.0

[mark.little@jboss.com]

Until Messages need to be transmitted between address spaces, they are internally represented as Java objects. However, at some point, some form of externalisation of the Message is required. Typically this is part of the normalization process for messages.

We don't support a single external format for Messages. Rather, we provide support for an arbitrary number of them and give two specific instances out-of-the-box.

You get a message of a specific type when you need it from a Message Factory. Obviously that type may not be suitable for the service (hopefully you've got that contractual information a priori, but maybe not) and in which case some translation/transformation may be necessary.

Types of Message externalised representations are uniquely identified (URIs). MessagePlugin is used to plug in new message formats dynamically. Each plugin is responsible for returning a message implementation that knows how to externalise its state in a specific manner, e.g., XML or ASN.1.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975451#3975451

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3975451