On Mon, 2009-03-16 at 17:00 +0100, Alexey Loubyansky wrote:
Do we have any tests with mdb-client-id? In the AS testsuite I
can't
find any.
I don't see any.
All the tests seem to either use the john/needle login
to get the preconfigured one or they use the
activation-config-property.
Like the bug report says, this is just a typo in the
JBossJMSMessageEndpointFactory, that is supposed to
map old configs to the new one.
It has nothing to do with MessageDrivenMetaData AFAICS?
It is setClientId() on the activation spec. And thats what
the JCA spec recommends it be called.
B.2 JMS ActivationSpec JavaBean
"
The recommended properties for JMS ActivationSpec JavaBean are:
destination (required), destinationType (required), messageSelector,
acknowledgeMode, subscriptionDurability, clientId, subscriptionName.
"
So the fix should be here:
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/server/src/main/...
- checkActivationConfig("clientID", metaData.getClientId());
+ checkActivationConfig("clientId", metaData.getClientId());
But its also wrong on the WIKI page and so I guess it is probably
wrong in the docs?
http://www.jboss.org/community/docs/DOC-9352/version/13
This is regarding
"Specifying mdb-client-id in jboss.xml causes mdb deployments to fail"
https://jira.jboss.org/jira/browse/JBAS-6606
Thanks,
Alexey
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development --
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx