Spring Transactions disrupted by initialization of SAMLBootstrap bean
I have run into a problem as I integrate Spring SAML into my application. I'm using the sample as a guide, which includes the following bean:
Inclusion of this bean causes Spring to skip transaction processing as it normally does, ie my service interfaces aren't proxied as they normally should be. Has anyone run into this problem before?
I thought it might be something related to class loading, but have been unable to track it down so far.
Simply commenting out this bean allows the transaction handling to proceed as it should
Any thoughts would be appreciated!