Yeah okay, that makes a ton of sense why the documentation wasn't ending the quote around the xsi:schemaLocation in the opening beans tag.
So I got some new Tomcat messages now. First one I came across is this. 2011-09-12 14:02:16,308 ERROR [org.jasig.cas.web.init.SafeContextLoaderListener] - <SafeContextLoaderListener: The Spring ContextLoaderListener we wrap threw on contextInitialized. But for our having caught this error, the web application context would not have initialized.> org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'cleanerLock' defined in ServletContext resource [/WEB-INF/spring-configuration/ticketRegistry.xml]: Could not resolve placeholder 'ticket.cleaner.database.platform' I assume this was once a variable in cas.properties. So I took a stab in the dark and I changed "ticket.cleaner.database.platform" to "database.hibernate.dialect". This got me some new complaints from Tomcat. 2011-09-12 14:11:48,717 ERROR [org.springframework.web.context.ContextLoader] - <Context initialization failed> org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ticketRegistry' defined in ServletContext resource [/WEB-INF/spring-configuration/ticketRegistry.xml]: Cannot resolve reference to bean 'entityManagerFactory' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in ServletContext resource [/WEB-INF/spring-configuration/ticketRegistry.xml]: Invocation of init method failed; nested exception is java.lang.IncompatibleClassChangeError: Implementing class I'm not sure what's going on here with this one. Thanks, Jonathan ________________________________________ From: Marvin Addison [[email protected]] Sent: Monday, September 12, 2011 13:48 To: [email protected] Subject: Re: [cas-user] JpaTicketRegistry > A second set of eyes would be much appreciated. Apparently I needed to take a careful look as well. Turns out the documentation indeed appears wrong -- the location of the tx namespace is missing. But here's the strange part -- the wiki source is correct. It took several attempts to get it to render correctly, but I believe it's fixed now: https://wiki.jasig.org/display/CASUM/JpaTicketRegistry Looks like there is some bug in the Confluence XML formatter that produced this one. Go figure. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
