Replies: 7 comments 8 replies
-
Adding message selector should not be a problem As for returning data from the message post, JTB performs a |
Beta Was this translation helpful? Give feedback.
-
our posts crossed..lol |
Beta Was this translation helpful? Give feedback.
-
For your error, nothing also in the |
Beta Was this translation helpful? Give feedback.
-
I've reproduced the HTTP 500 on my side. I guess the bug came from the newer version of eclipse RCP |
Beta Was this translation helpful? Give feedback.
-
I've committed a fix for the HTTP 500 when posting a message from template |
Beta Was this translation helpful? Give feedback.
-
I've committed the change to receive all info from the freshly pushed message. Now the "Message" received in return looks like this:
I've also updated the wiki |
Beta Was this translation helpful? Give feedback.
-
I've publishes v5.15.0 with the 2 new features |
Beta Was this translation helpful? Give feedback.
-
@titou10titou10 This seems like a very promising Open source program for MQ interactions. I especially think the rest API is great for integration testing purposes.
There are couple of things that could be added towards REST API
Message selector support for message browsing
Currently it is only possible to select all messages within a queue. You can only pass a query parameter to limit amount of retrieved messages. When there is a test case that requires obtaining a specific message it would be very beneficial if the REST API offered a way to pass a message selector to the JMSToolBox. With message selector it would be possible to filter messages that are retrieved.
Message information in POST message response payload
Request:
POST http://localhost:9998/rest/message/{QueueManager}/{Queue}
{
"deliveryMode" : "PERSISTENT",
"priority" : "1",
"deliveryDelay" : "",
"timeToLive" : "",
"jmsCorrelationID" : "9af59e05-4c2f-4dd6-b358-38fad6402074",
"jmsType" : "SomeType",
"type" : "TEXT",
"replyTo" : "",
"payloadText" : "Some example text"
}
This will yield a response:
HTTP/1.1 201 Created
Date: Thu, 11 Aug 2022 20:08:21 GMT
Content-Length: 0
Server: Jetty(10.0.6)
The response itself does not contain other information than the MQ sending was a success or a failure. It would be good to also have updated message information and message header information in the response payload. This way client would be able to obtain for example a JMSMessageID that could be used for test validation purposes. These updated message information set by the JMS Provider should be able to get from Message object after successful message sending.
Beta Was this translation helpful? Give feedback.
All reactions