There are some use cases, where client (or service) needs explicit control on some JMSEndpoint properties (for example durableSubscriptionClientId, durableSubscriptionName) not through the JMS URL, but using jax-ws properties. The reason: URL is often shared between client and service, but they must have different durableSubscriptionClientId for durable subscription.
Currently only EndpointInfo Binding properties are checked. I would apply both EndpointInfo properties and Binding properties having special prefix: "jms.". That prevents potential conflicts with other jax-ws properties and opens the door to explicitly configure JMSEndpoint.