> The Jasper page compiler needs to have access to all of the bean classes
> that you might have placed in WEB-INF/classes and WEB-INF/lib. This could
> be "faked" by setting up yet another class loader that simulates the
> "real" webapp class loader (in terms of what repositories it gives you
> visibility to), or by making the special Jasper class loader a sibling of
> the webapp class loader (rather than a child), and adding the WEB-INF
> repositories to it as well.
>
> This will work as long as you don't create an object in the Jasper class
> loader and then expect it to be visible in the webapp class loader (or
> vice versa) -- you get class cast exceptions at that point.
Craig, can we do this for now - it will solve these problems in the short
term and we can then think about re-writing Jasper?
Kevin Jones
DevelopMentor
www.develop.com
