fixing tests

Normally I'm a fan of constants, but I'm not sure how I feel about using constants in action mapping definitions.  I don't think they save any time or provide much clarity,  and in this case they obfuscated a mistake that would have been otherwise easy to catch.
logging namespace/action/result
Trying to fix the ScheduledProcessITCase test; adding some null checks, and making sure that the queue is empty

--HG--
extra : rebase_source : 916370ebbcbaeeced497204dd421b615a1d456d8
fixing double-encoding issue on login urls (TDAR-3396)

--HG--
branch : stable
TDAR-4176

--HG--
branch : stable
cleanup of keyword type
browse keyword rewrite
fixing redirect to allow removal of static parameters [http://stackoverflow.com/questions/9773295/struts2-convention-and-redirect-parameters]
removing google objects reference
fixing tests; renaming test case

--HG--
rename : src/test/java/org/tdar/struts/action/KewordActionITCase.java => src/test/java/org/tdar/struts/action/KeywordActionITCase.java
Merge
fixing test, returning second static params
removing dependency on JettyClient using ApacheHttp client like the rest of the app
fixing DOI bug

--HG--
branch : stable
Merge
fixing DOI

--HG--
branch : stable
Merge
pom updates
updating Rome RSS/ATOM toolkit
tracing out narstats