If you define a vdb in a cr, the generated vdb will just use the platformtransactionmanager.
Since the materialization procedures use transaction blocks, we need a full transaction manager. By default with the platformtransactionmanager it will throw an exception - only spring managed transactions ...

The workaround would be to add snowdrop to the cr dependencies, but it would be nice to either always use that in the generated, or detect materialization is being used, or address TEIIDSB-109