Paul,

I would do a clean build of CAS (i.e. ant clean and ant war) and also clean
out the webapps directory (the cas directory and the cas.war) and see if
that works.  That jar file should be fine in the lib directory.

-Scott

On 5/18/07, Paul Ortman <[EMAIL PROTECTED]> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Scott Battaglia wrote:
> This is the one you need:
> ldapbp.jar
>
> The other Spring jars (besides spring LDAP) are not needed as CAS
> includes the whole spring.jar (we should also include commons-logging,
> commons-lang, and commons-collections if I recall correctly).
>
> ldapbp.jar is a Sun jar.  I can't speak for why its separate.  Its
> apparently called the "JNDI/LDAP Booster Pack".

Hmmm.  So I've gotten the jars placed into my build directory like so:

  [EMAIL PROTECTED] localPlugins]# tree
  .
  |-- README.txt
  |-- build.xml
  |-- lib
  |   |-- cas-server-ldap-3.0.7.jar
  |   |-- ldapbp.jar
  |   `-- spring-ldap-1.1.2.jar
  `-- src
      `-- README.txt

I then do the ant war; mv target/cas.war
/usr/share/tomcat5/webapps/; dance, and unfortunately, nothing
changes, I continue to get exceptions being thrown.  I can tell
things are changing in the web app if I remove either of the other
.jar files, but having the ldapbp.jar file in my build doesn't do
anything at all to the behavior I'm seeing.  Is the ldapbp.jar
supposed to go somewhere else?  I'm truly running very short on
ideas...

Thanks for all your patience and help,

- --
Paul Ortman

PGP Key: 55602C81
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGTfYFfw8KGlVgLIERAlQTAJ9TWuMpChRZC2VUCksUTNXvrmIZuwCfeFXD
vYaYcdlxXDX8sx0s6lW13nQ=
=95XP
-----END PGP SIGNATURE-----
_______________________________________________
Yale CAS mailing list
cas@tp.its.yale.edu
http://tp.its.yale.edu/mailman/listinfo/cas




--
-Scott Battaglia

LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________
Yale CAS mailing list
cas@tp.its.yale.edu
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to