Groovy error in CAS logs

[Scott Battaglia]

Bill,

I believe you are correct.  Spring looks for them but doesn't actually need
them (but notifies you of their absence).   Adding the jars does eliminate
the bug.  Newer versions of Spring may correct this (I haven't checked.  I'm
using 2.0.5 with CAS 3.1 and haven't seen that error.)

-Scott

On 6/13/07, Bill Bailey <Bill.Bailey at northlandchurch.net> wrote:
>
>  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
>
>
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>


-- 
-Scott Battaglia

LinkedIn: http://www.linkedin.com/in/scottbattaglia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20070613/6db9305d/attachment.html