Major Description
When multiple StringResourceLoaders are initialized, the later ones are blowing up. StringResourceLoader uses a static RepositoryFactory. Unfortunately, this means that you can really only have one StringResourceLoader per classloader. This poses significant issues for anyone using multiple engines w/StringResourceLoader and could be come a major issue if any other frameworks or components adopt use of the StringResourceLoader (e.g. i'm planning to use this for a VelocityViewTag in Tools 2.x). They'll stomp all over each other in many ways. This is bad. 