-
1. Re: WFLYEJB0006: ActivationConfigProperty clientId will be ignored since it is not allowed by resource adapter: activemq-ra
objectiser Feb 16, 2016 9:57 AM (in response to objectiser)Fixed the problem - I changed "clientId" to "clientID" - based on seeing the configuration used with HornetQ.
However according to this doc (The Message-Driven Bean Class - The Java EE 6 Tutorial) the property name should be "clientId".
Should this be reported as a bug?
-
2. Re: WFLYEJB0006: ActivationConfigProperty clientId will be ignored since it is not allowed by resource adapter: activemq-ra
jbertram Feb 16, 2016 10:50 AM (in response to objectiser)There seems to be some ambiguity here. The tutorial as well as the JMS 2.0 spec references "clientId" for the activation configuration property, but the API is getClientID() and setClientID(String clientID) indicating that the property's name is "clientID". Furthermore, I would expect the JMS TCK to fail if the capitalization was strictly enforced, but I've not seen or heard of any such failures for HornetQ or Artemis. For simplicity's sake the RA should support both "clientId" and "clientID". Please open a JIRA at https://issues.apache.org/jira/browse/ARTEMIS. Thanks!