@marc
1.) Let’s see what we can do about this flag. I just see risk of loosing messages if someone forgets to set. As we see there are already some simplifications to set for JMS on factory level but JMS is not the only way we connect to solace.
2.) Exactly like you say. You explicit have to set the values and in my eyes it should be as well done
by following the purpose of a field and not missuse. As ApplicationMessageID => JMSMessageID both fields must follow the defined purpose described here:
=> “The JMSMessageID header field contains a value that uniquely identifies each message sent by a provider.”
Thanks for clarification of the topic.