Jetspeed Login Module fails to load on Windows in directories with spaces in the path
It appears that we are breaking the Login Module on Windows when there are spaces in the path to the login module configuration file that Jetspeed provides, and is put into the work area of the application server. The problem is the Java class loader encodes the space, but then the file system does not understand the encoding (%20). If we do not encode the space, the file system correctly finds the resource. This change should be tested on all major file systems before committing.