I've been further investigating the transaction behaviour I asked for help about yesterday and I've reached some conclusions. They aren't what I would have expected a-priori, so I'd like some conformation of what I'm seeing is indeed what is expected.
What I'm observing is:
Both the cases involve one transactioned method calling another. When the two methods are in different classes the defined transactional behaviour of the second, called, method is taken into account. However, when the two methods are in the same class, the transactional attribute of the second method is ignored. It appears never to be looked up by the TransactionInterceptor.
Can anyone confirm this is expected behaviour, and if not, any suggestions about what I might be doing wrong to observe it.