Right now the camel transformer only copies the MESSAGE scoped context property into camel message header, but it only takes effect within a same exchange. Since SY declarative transformer is possibly applied at early phase of the exchange, the application may not have a chance to set a MESSAGE scoped property available for the transformation. The EXCHANGE scoped property should be also accessible from camel transformer for such case.