Publish/subscribe to topics on Solace brokers without requiring JNDI setup

[domule]

Hello there,

I have been trying to find a way in JTB to interact with topics on Solace brokers without having to first configure JNDI destinations on the broker. I am used to being able to flexibly publish/subscribe to JMS topics ad-hoc in pure Java, SDKPerf, or the Try Me client that comes with Solace brokers (uses WSS and not JMS, but same principle), same also with SonicMQ. I was therefore wondering if I was possibly overlooking something or looking in the wrong place?

If this is really not possible with JTB at the moment, then is this intentional?

If not, then would there be scope for adding this functionality?

Doing so would make the feature set of JTB complete for all our testing needs.

Cheers
Dom

[titou10titou10]

This has been discussed a few times before, including with people from Solace when the plugin has been created.
JTB must use public "proprietary" API to discover queues/topics as the JMS specification does not defines an API to "discover/list" destinations (like JDBC does for example to list tables/views etc..) .
This is by design
AFAIK the only way a client can discover/list topics from a Solace PubSub+ server is to define them as "JMS JNDI Topics"
If there is another way (like WSS..), please let me know and point me to the doc and if possible a working example for listing queues/topics and retrieve destination information (like queue depth etc.). Or better, push a PR

[domule]

Thanks for the super quick response!

I was more thinking of allowing users of JTB to configure topics within the JTB front-end, and perhaps persisting these in the corresponding session config. I'm not looking for a way to query a broker to perform topic discovery. Topics are ephemeral by nature, so it would be good to just let a user send/subscribe to any topic without any upfront broker configuration/querying being required. Happy to have a go at a PR.

[titou10titou10]

I was more thinking of allowing users of JTB to configure topics within the JTB front-end, and perhaps persisting these in the corresponding session config.

Again, this is by design that JTB does not offer that feature

Again PR are welcome if you want to change this. Do not forget that JTB is "universal" JMS client, not only for solace