What’s the solace topic endpoint use case?

We know that solace topic is just message property, and there are topic endpoint for JMS compliant, but per my test (VMR 8.10.0.1092):

  1. In Solace Admin UI, it seems we can’t setup topic endpoint’s subscription like queue, is it solace admin UI issue?
    enter image description here
  2. When i use solace JMS API to publish message to topic and if there are no durable subscriptions (queue/topic endpoint) for this topic, it will create one topic endpoint with random name and subscribed topic, for example:
    enter image description here
  3. When i use solace JMS API to subscribe the topic “T/sampleTopic”, it also create one non-durable topic endpoint with random name and subscribed topic named T/sampleTopic.
  4. When i use solace JMS API to subscribe the topic “T/sampleTopic” and specify subscription durable to true, it also create one durable topic endpoint with default name(org.springframework.jms.listener.adapter.MessagingMessageListenerAdapter) and subscribed topic named T/sampleTopic.
  5. When i use solace JMS API to subscribe the topic “T/sampleTopic” and specify subscription durable to true and setup subscription name with “T/sampleTopic”, then it report error: Error Response (400) – Endpoint Property Mismatch, and after i delete the original topic endpoint “T/sampleTopic” and run again, then it create one “expected” topic endpoint:
    enter image description here

So, i do NOT know how to use solace topic endpoint with JMS API.

What’s the solace topic endpoint use case?