Many thanks Tomo! I did not notice that you need to use a specific class-a and source field. I was trying to use both classic mapping and expression mapping at the same time. It seems to use expression mapping you need following: - "class-a" element must be exactly "org.apache.camel.component.dozer.ExpressionMapper" you cannot put your custom class here - "custom-converter-id" must be exactly "_expressionMapping" - field "a" should always be "expression"
This brings some limitations, like: - if you set class-a to the ExpressionMapper you are required to use expression mapping for all fields in this mapping - mapping is one-direction because the way it works - you cannot have two mappings with same target class but different expected sources. Correct? Somehow, I can live with this limitations as long as I am aware of them... Many thanks, Marcin -- View this message in context: http://camel.465427.n5.nabble.com/IllegalStateException-Current-exchange-has-not-been-set-for-ExpressionMapper-while-converting-a-CXF-t-tp5789866p5789896.html Sent from the Camel - Users mailing list archive at Nabble.com.
