It is possible to specify transaction attributes for BMT beans. I believe when Container encounters following in ejb-jar.xml for a particular Bean:
It ignores <container-transaction> attribute for the particular Bean.
I know it is of no use to specify transaction attribute for a method of Bean which is BMT. But this can happen just in case an application is in maintenance stage and where decision is taken to make Bean BMT from CMT. But Application Assembler forgets to remove <container-transaction> attribute for the particular Bean from deployment descriptor.
Any thoughts on above?
[ November 03, 2004: Message edited by: Sandesh Tathare ]
[ November 03, 2004: Message edited by: Sandesh Tathare ] [ November 04, 2004: Message edited by: Sandesh Tathare ]
Regards,<br />Sandesh<br />(SCJCP, SCWCD, SCBCD - 99%, OCP-1)<br /> <br />Either find a way or create one.
If you are looking along the lines that the container provider needs to do some sort of validation to ensure that such discrepancies don't exist during deployment, that certainly seems reasonable. Less scope for confusion if its implemented I guess.
How about choice A for question above. I think its right too. A bean-started transaction can propagate out to other beans (for instance, a CMP bean), but no transaction can be propagated into a bean using BMT. Which would imply that a transaction in a BMT bean must be started by the bean itself.