GetJMSCorrelationID Why encode as hex?

[ftcopilot058]

Why encode GetJMSCorrelationID as hex instead of returning the correlationid to the user as is?
@matrober-uk

[matrober-uk]

Hi @ftcopilot058 - thanks for your question.

The approach of encoding the CorrelationID as hex is to maintain consistency with the approach that is taken by the MQ JMS client.

[ftcopilot058]

Hi @ftcopilot058 - thanks for your question.

The approach of encoding the CorrelationID as hex is to maintain consistency with the approach that is taken by the MQ JMS client.

Can you provide a way to get the original correlation id?

[matrober-uk]

Hi @ftcopilot058 - please can you give an/some examples of the type of correlation ID that you are passing to SetJMSCorrelationID, and the string that you get back from GetJMSCorrelationID?

There are some examples in the getbycorrelid_test.go (at the link below) that show text strings being round-tripped successfully (limited to the first 12 characters, which is due to the 24 byte size of the internal MD Message Descriptor (MQMD) header field used to store the correlID when it is sent)
https://github.com/ibm-messaging/mq-golang-jms20/blob/main/getbycorrelid_test.go#L281