Also.. that will be an issue when a customer is upgrading his version.. A customer would need to define the ClientID or the ConnectionFactory won't work, but we will have an exception clearing that. We could take the action of using a sequence case clientID is null (something we will have to think about later).
Please, scratch that.. I was so tired that I didn't realized that the clientID defined on ConnectionFactory was being used to automatically define clientIDs (connection.setClientID).
I'm now using a different String for that. I'm using the ConnectionFactory's MBean name. If we don't want to use that string we will have to ellect another string for that.
You don't want to use client id.
That's not a unique id for the connection factory, it's an identifier for the user.
Also the mbean name won't work. How does the client know this?
The existing unique id is the jndi name.
I don't understand what you're trying to do, the whole point of using the connection factory name when creating the connection was to avoid passing through the object id.
But if you're going to pass through the connection factory name instead, what's the point?
The objectID is a sequence generated ID. The JNDI name is unique for a connection factory.