An Overview of Marshalers in ServiceMix

Marshalers in ServiceMix are used to convert messages to/from the JBI normalised messages. For example, the JBI spec requires that the payload of a normalized message be XML. So when non-XML messages are sent through a binding component (BC) those messages must be normalized into XML and when a message leave a BC it may need to be denormalized to be compatible with the external service to which it is being sent. For information on this see message normalization.

Because ServiceMix doesn't provide the ability to handle message normalization for every conceivable message format out there, ServiceMix provides classes for implementing your own custom marshalers.

Existing Marshalers in ServiceMix

The MarshalerSupport class is the base class for creating most custom marshalers.

Older stuff

Questions:

• My initial questions about this area were based on the apparent ad-hoc implementations of the marshalers (from the class diagram).
• I thought that the interface Marshaler was intended as a base for all marshalers.
• I was also confused why some marshalers are standalone, while others derive from a common base (MarshalerSupport).
• Yet more have interfaces (eg FileMarshaler), but there is no consistency

– PS

Notes

Notes [19/12]:

• Marshaler (the interface) is really intended for POJO/NM support

• Other transports have own hardwired marshalers with args/helpers appropriate to each transport

• If user wants to write own marshaler for specific binding (eg JMS components) then in general must derive the ServiceMix hardwired marshaler for that binding. eg MyJmsMarshaler extends JmsMarshaler

• Some standalone marshalers don't derive MarshalerSupport base class. No particular reason ; they just preceded it, that's all

• Code base for diagram is SM2.0.2

• See IRC log 19/Dec for more comments

Update [20/12]:

• SM devs refactored interface Marshaler to PojoMarshaler to reduce confusion about purpose of Marshaler

Class diagram showing ServiceMix 2.0.2 marshalers