I'm really sorry everyone I've flooded your Mailing List - I'm new.
The spring library that I needed wasn't being shared either - which caused a
*very* silent error when running Class.forName.
I have it working now.
Sorry again,
Branden
MrVisser wrote:
>
> Hello,
>
> I'm using spring, and
Umm.. I fixed my directories and I'm getting the same problem :(
Now both A.jar and B.jar are in shared/lib, and the same problem occurs.
loadClass will find spring.B, but Class.forName crashes when trying to
initialize it..
Any thoughts?
Thanks,
Branden
MrVisser wrote:
>
> Hello,
>
> I'm
I just solved my problem. Unfortunately 4hrs after I encountered it :) It's
very silly.
For whoever may run into this:
I did not use "scope provided" in the Maven POM file in the servlet webapp,
therefore 'A.jar' in my example below was being deployed into the webapps
WEB-INF/lib and over-riding
