[
https://issues.apache.org/jira/browse/QPIDJMS-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659264#comment-16659264
]
Sebastian T commented on QPIDJMS-422:
-------------------------------------
[~tabish121] The problem we are facing is, that when we set the client ID
programmatically, we cannot use Global Shared Subscriptions because then all
clients would need to have the same client ID but we need to differentiate the
clients. If we do not set the client ID then IDs are generated by the internal
IdGenerator and we can only specify a prefix for the generator but not the
whole format.
So for us the only solution I see in either we have a way to provide our own
IdGenerator or are able to perform global shared subscriptions despite having a
client ID programmatically specified.
> Custom ClientID Generators
> --------------------------
>
> Key: QPIDJMS-422
> URL: https://issues.apache.org/jira/browse/QPIDJMS-422
> Project: Qpid JMS
> Issue Type: New Feature
> Components: qpid-jms-client
> Affects Versions: 0.37.0
> Reporter: Sebastian T
> Priority: Minor
>
> In our application we are using client IDs with a very specific format. We
> would therefore like to register our own IdGenerator with the
> JmsConnectionFactory. Currently the JmsConnectionFactory#setClientIdGenerator
> is protected thus we cannot programmatically set a custom IdGenerator except
> by using (hacky) reflection.
> I would suggest to rename the current IdGenerator class to
> DefaultClientIdGenerator, create an ClientIdGenerator interface and change
> the visiblity of JmsConnectionFactory#setClientIdGenerator to public.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
