Groovy error in CAS logs

[Bill Bailey]

Hi again,

 

Ok ... I think I have resolved the problem myself. It appears that it is
not CAS that needs Groovy per se, but rather the Spring Framework. When
I added the groovy jar, it went away and a JRuby error appeared in its
place ... adding the jruby jar fixed that error and then a BeanShell
error replaced it ... finally after adding the beanshell jar, I no
longer see any errors in the log file.

 

As nearly as I can tell the absence of these jars doesn't hurt anything
(unless you actually intend to use Groovy, JRuby, or BeanShell
functionality, I suppose), but the exceptions still get dumped to the
log. I am not a big fan of logging things as errors that aren't really
errors, but it appears that may be the case here. If anyone knows
different, let me know just for my own interest.

 

Bill Bailey

Senior Developer / DBA
Northland, A Church Distributed

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20070613/42505a4d/attachment.html