Hi.
I think that Transaction Attribute default in CMT for MDB
should be the same as Session and Entity. Default is
required for Session and Entity. My opinion is that when
somebody selects CMT, it is usually because it wants
to use transactions.
Currently when no transaction attribute is set for
onMessage method of a MDB, BeanMetaData puts
TX_UNKNOWN as transaction type. Then
MessageDrivenBeanMetaData puts
TX_NOT_SUPPORTED for anything else then
TX_REQUIRED including TX_UNKNOWN.
I do not know what this effect could have on the test
suite.
The patch is against latest version of
MessageDrivenMetaData on 2.4 branch but it applies to
all versions of JBoss because the code of
getMethodTransactionType in that class is almost the
same across all jboss versions.
If the patch is needed against another version of jboss, I
will provide with pleasure.
Patch to change transaction attribute default to required instead of not supported.