Details
Major Description
If a client sends an AMQP that cannot be transformed using the configured transformer the broker shouldn't drop the message, instead it should attempt to fall-back to a less aggressive transformer.
An example would be a broker configured to use the JMS transformer and the incoming message contains a body consisting of a DescribedType. The JMS Transformer would fail as there is no direct way to map that into a JMS message type. We could in this case fallback to the Native transformer and still process the message. An OpenWire client for instance would just receive a BytesMessage while other AMQP clients would get the message in the form it was sent.
This allows the message to round-trip for instance from AMQP -> OpenWire -> OpenWire -> AMQP (Broker network bridge) without losing its original payload or message properties.