Guys, Currently as soon as transactional element is in xml config file, even if transactionManagerLookupClass is not specified, it defaults to a certain value. Having these minor semantic rules require special processing of elements during xml reading. Of course, the design accommodates these special rules (case of CacheLoaderManagerConfig where we add individual CacheLoaderConfigs). So far there are only two special processing elements (another is clustering). Can we avoid it for transaction element, and if yes, how? By requiring transactionManagerLookupClass to be mandatory? Cheers, Vladimir