I have a very strange problem I'm hoping someone can help me with. I have had Spring Transactions (using the regular tx mechanism and AOP) enabled and working fine in my project for quite some time. I'm integrating the extension project SAML into my application, and am running into a strange problem where including this simple bean definition:
causes Spring to no longer proxy my service layer, causing all kinds of problems for Hibernate etc since it cannot find a session for the current thread.
<bean id="parserPool" class="org.opensaml.xml.parse.BasicParserPool" scope="singleton"/>
This bean just sets up the SAML JAXP provider and doesn't do much else. Has anyone seen anything like this or have any suggestions? Simply commenting out the bean allows the app to function correctly.
I am using Spring 3.1.4 and the latest SAML extension code, on Tomcat 7 and Java 1.7.
At first I thought it was some JAXP version problem but I can't confirm this one way or the other.
Anyone ever run into something like this?
Thanks for any help!