Yes, I'd read some forum posts where people had that issue.
But I guess I must be doing something fundamentally wrong, because the JMS Headers that I'm trying to preserve through Fuse4 ESB, are the standard headers such as Priority, Reply To, Correlation Id etc.
I send the messages to my JMS consumer endpoint via Active MQ's admin web interface. This eliminates Spring issues, if any.
So, the form that is presented when you click "Send To"? That's what I'm filling out for populating my headers.
Those should be transported transparently by Camel if I'm not mistaken.
Well that's Spring JMX (camel-jms uses Spring JMS) wacky API where you need to enable preserveMessageQos=true to tell it to preserve the QoS headers.
Read about the option at the Camel JMS documentation