Read logback configuraton from a file specified in JNDI.

This addresses issue issue 79 (https://github.com/TeamDewberry/jmxdatamart/issues/79)
Use the same logback configuration file for the fitnesse tests (fitnesse VM) as the extractor web application uses so logging is consistent.
Merge pull request #1 from DavidWhitlock/master

Merge fixes for TeamDewberry/jmxdatamart#77 into TripwireInc repository from DavidWhitlock repository.
Merge remote-tracking branch 'upstream/master' into fix-issue-79
Merge pull request #2 from DavidWhitlock/fix-issue-79

Fixes TeamDewberry/jmxdatamart#79 by having the JMX Extractor web application read the logback configuration file from the logback/configuration-file entry in JNDI.  I also changed the fitnesse tests to use the same logback configuration as the web app so that the output looks consistent.