Does solace spring boot JMS api automatically help to configuration the JNDI object in the backend?

General Discussions
1

when I test solace samples GitHub - SolaceSamples/solace-samples-spring: Developer Samples for using Solace PubSub+ with Spring Framework found that. Seem we do not need the JNDI object configuration when used JMS API depended from solace-jms-spring-boot-starter.
Does solace spring boot JMS api automatically help to configuration the JNDI object in the backend?

2

Hello.
The Spring Cloud Stream samples you are referring to do not use JMS, they use JCSMP (a Solace Java API), as the API underneath the Spring Cloud Stream binder APIs to access PubSub+.
There is no JNDI in this case.

3

Sorry, my answer was not complete… There are 2 samples that use JMS.
In both cases, the DestinationResolver interface is used to resolve if it’s a queue or topic being used to send or receive. The default in this interface is queue.
The send sample references a property called setPubSubDomain which defaults to false, thereby indicating a queue.
Since the destination is resolved to a queue in both cases, a JNDI lookup for destination is not needed and no object is created in JNDI.

4

thanks @amackenzie .
@rayleeustc_ll , To add a little more information here, the Spring Boot JMS Starter does NOT automatically configure JNDI. There is actually an example of how to do that included int he solace-spring-boot repo here which might help.