This content has been marked as final.
Show 4 replies
-
1. Re: Unable to call setClientId after getClientId
clebert.suconic Sep 13, 2010 5:34 PM (in response to aengineer) -
2. Re: Unable to call setClientId after getClientId
clebert.suconic Sep 13, 2010 5:38 PM (in response to aengineer)BTW: submitted the JIRA as you being the reporter. (I can do that as I'm one of the admins for HornetQ's JIRA)
-
3. Re: Unable to call setClientId after getClientId
timfox Sep 14, 2010 2:55 AM (in response to clebert.suconic)HornetQ's behaviour is correct in this case. The JMS specification is clear that setClientID() must be the first action that occurs on a connection.
If you want strict JMS compliance to be relaxed we could add an attribute on the connection which allows the more permissive behaviour you require.
-
4. Re: Unable to call setClientId after getClientId
aengineer Sep 15, 2010 9:43 AM (in response to timfox)A attribute/flag on the connection to allow more permissive bahvior would also work.
I would again argue that calling any of the get* API calls (getClientId, getExceptionListener, getMetaData) should not prevent a subsequent call to setClientId