[
https://issues.apache.org/jira/browse/QPIDJMS-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660429#comment-16660429
]
Sebastian T commented on QPIDJMS-422:
-------------------------------------
We are evaluating the Stomp client IDs, Artemis Core Client IDs, AMQP container
IDs, etc of incoming connections in Artemis and ensure it follows a predefined
format and provides certain information we need for e.g. logging.
Using plain AMQP clients (node.js) we can programmatically set the container ID
in our format and specify the cababilities "global" and "shared" on the AMQP
link to have a global shared subscription while being able to specify a client
ID in our custom ID format.
With QPIDJMS we currently can't do it thus we cannot subscribe to the multicast
addresses in the same way. For us this is now an interoperability problem.
What we would need in QPID JMS is:
- the ability to specify the unique AMQP container ID for JMS connections where
we are not setting a JMS Client ID via Connection#setClientId() or
- the ability to specify a custom AMQP Container IdGenerator (which I would
prefer)
Our workaround at the moment is to create a connection with a JMS clientID and
then - before starting the connection - access the private field
{{connection.connectionInfo.explicitClientID}} and set it to {{false}} - which
I don't feel comfortable with. However, then we can use that connection to
create global shared subscriptions and the AMQP connection ID sent to the
server is in the format we require.
> 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]
