-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JMS_IBM_Feedback, JMS_IBM_Report_COA and JMS_IBM_Report_COD int properties #70
Comments
Hi @lucasmfarias1 - thanks for your question; those fields aren't currently handled by the Golang JMS client (see Special header properties supported for details of those that are) - but I should be able to add them. Is it just those three specifically that you need, or are there any other related fields that you need as well?
|
Hi, @matrober-uk. Thanks for the swift reply. Right now, it really is only those three that I need. |
ok, thanks - I'll take a look and aim to share back an update by the end of the week. |
Add support for Feedback, COA, COD - #70
Hi @lucasmfarias1 - turned out to be quicker to implement than I expected (I started looking at it yesterday), I've merged a commit to add in support for those three properties here: matrober-uk@ed6afe3 If you're able to pull down that specific commit to test it out that would be great please, after which I can generate a release release to make it easier to consume. Please let me know how you get on! |
Hi @matrober-uk I've just tried it out and it seems to work perfectly. All the |
Great - my pleasure to be able to get this turned around in a couple of days! I've created a new release v1.12.0 to package this change for easier consumption. Regards, Matt. |
Notes from implementation, for reference if needed in future
|
Implemented in v1.12.0 |
Can we not set/get the
JMS_IBM_Feedback
,JMS_IBM_Report_COA
andJMS_IBM_Report_COD
int properties? I'm rebuilding and old application that used JMS and I cannot seem to be able to trigger COA and COD anymore.The text was updated successfully, but these errors were encountered: