Add MapContext to output CreateMapProcessor object so that data like scale and bounds can be accessed in the jasper template
ImageIO.read will return null if input is not an image.  Added checks to make sure that an image is correctly returned and if not then the correct response is made
Make image resolver use the http client factory that is put in the values object.  This allows it to load from config directory
table processor will output the number of rows in the table.  this allows the number or rows to be accessed in jasper reports.
Remove main object from spring configuration because it is in another spring config file.
Add output value prefix to simplify fixing output mapping conflicts.

Consider the case where there are 2 CreateMapProcessors in a configuration.  CreateMapProcessors have 2 (at the moment) output values.  2 processors are not permitted to have output values with the same name.  So before this process each of the output values would have to have a mapping in the outputMapper.  This is fragile, because if a new output value is added in the future to CreateMapProcessor, then it will break the configuration because there will be 2 output values with the same name.

This PR adds an option to set a prefix for all output values with a given name.  This prefix will be applied to all output value names making them unique for the two maps.  Additionally it will be resistant to future API changes of CreateMapProcessors.
Merge pull request #131 from jesseeichar/fixes-required-for-basel

Fixes required for basel