All, Just to follow up from my post last night, I was able to get past my issues and I wanted to share my findings. The instructions here: http://www.ja-sig.org/wiki/display/CASUM/Configuring are great and are really easy to follow. But like all good example documentation, you can't take it 100% literally, and so the issues I ran into were because of my own copy-and-paste assumptions and not actually thinking about what the code was doing.
1.) The "Cannot load JDBC driver class" error was caused by an incorrect mysql version in my pom.xml. I am using the MySql 5.1.6 JDBC driver, but my pom.xml incorrectly referred to the 3.1.1 dependency. 2.) My QueryDatabaseAuthenticationHandler authenticationHandler wasn't working because I did not include the JDBC support in my cas-server-webapp pom.xml file as explained here: http://www.ja-sig.org/wiki/display/CASUM/Using+JDBC+for+Authentication So ultimately to get my persistent Service Management up and running on Windows, I had to: 1.) re-package the cas-server-webapp by updating the pom.xml following the instructions on BOTH links listed above. 2.) install Tomcat 5.5 on Windows to a non-standard path that does not include any spaces to get Hibernate to work correctly. *I'm still using JDK 1.5, so to my earlier question about the possible dependency on a 1.6 JVM, I don't think its necessary. JDK 1.5 is working fine for me now. Thanks again to Michael & Scott for the help, -Brian ________________________________ From: Pieslak, Brian Sent: Monday, March 09, 2009 8:48 PM To: [email protected] Subject: RE: [cas-user] trouble deploying Service Management for MySql persistence Michael & Scott, Thanks to both of you for the ideas. I setup another Tomcat instance in C:\Programs\Tomcat and it made the difference. Now I'm getting a different error when Tomcat loads: Cannot load JDBC driver class 'com.mysql.jdbc.Driver' java.lang.ClassNotFoundException: com.mysql.jdbc.Driver at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1386) What's odd is I'm using the same "dataSource" definition in my deployerConfigContext.xml for both my QueryDatabaseAuthenticationHandler authenticationHandler and my LocalContainerEntityManagerFactoryBean entityManagerFactory. I'm thinking I can figure this one out tonight. Thanks again for the help, -Brian ________________________________ From: Michael J. Barton [[email protected]] Sent: Monday, March 09, 2009 8:18 PM To: Pieslak, Brian; [email protected] Subject: RE: [cas-user] trouble deploying Service Management for MySql persistence Brian, I have seen this before. I’m running CAS on Tomcat 6 on a couple of Windows servers and received the same error when deploying the war file. I took the quick solution and simply installed Tomcat in a “non-standard” directory, (C:\Programs\Tomcat6) taking all spaces out of the path and shortening it as well. That did the trick. I’ve not investigated further to determine whether it was a JDK issue. I also found that if you modify Tomcat’s server.xml <Host appBase=”webapps”…> tag, and use a path “closer to the root (and without spaces, ie: appBase=”c:\\webapps”) and deploy the war file in that directory that the error goes away and cas is up and running. Hope that helps. -Mike On Mon, Mar 9, 2009 at 4:34 PM, Pieslak, Brian <[email protected]<mailto:[email protected]>> wrote: Hi everyone, I am trying to package and deploy the webapps for CAS Server 3.2.1 based on the following instructions: http://www.ja-sig.org/wiki/display/CASUM/Configuring I have updated my cas-server-webapp pom.xml file and when I deploy my new cas.war with the update deployerContext.xml file, I ultimately run into an issue in my cas.log file: error trying to scan <jar-file>: file:/C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%205.5/webapps/cas/WEB-INF/lib/cas-server-core-3.2.1.jar From what I have read online this appears to possibly be an issue with Hibernate and spaces in the path on Windows, but it also appears that this has been fixed. I've tried wiping out my environment a few times now. I believe I am following the instructions correctly in the CAS wiki, and I am not changing any CAS source code. The only potential issue I think I may have is I'm using a 1.5 JDK and not a 1.6, which I've read could be the issue in a few places, but no one says definitively either way. Has anyone else run into this issue or does anyone have any steps/guidelines for packaging and deploying the Service Management app to persist the data to a MySql database? Thanks, -Brian -- You are currently subscribed to [email protected]<mailto:[email protected]> as: [email protected]<mailto:[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 -- 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
