Bug: NPE in QuantumManager

[jamoore]

Traceback (most recent call last):
  File "/Users/moore/code/git/dist/lib/python/omero/gateway/__init__.py", line 3552, in getThumbnail
    rv = thumb(*args)
  File "/Users/moore/code/git/dist/lib/python/omero/gateway/__init__.py", line 2283, in wrapped
    return inner(*args, **kwargs)
  File "/Users/moore/code/git/dist/lib/python/omero/gateway/__init__.py", line 2244, in inner
    return f(*args, **kwargs)
  File "/Users/moore/code/git/dist/lib/python/omero_api_ThumbnailStore_ice.py", line 129, in getThumbnailByLongestSideDirect
    return _M_omero.api.ThumbnailStore._op_getThumbnailByLongestSideDirect.invoke(self, ((size, ), _ctx))
InternalException: exception ::omero::InternalException
{
    serverStackTrace = ome.conditions.InternalException:  Wrapped Exception: (java.lang.NullPointerException):
null
	at omeis.providers.re.QuantumManager.initStrategies(QuantumManager.java:101)
	at omeis.providers.re.Renderer.<init>(Renderer.java:322)
	at ome.services.ThumbnailBean.load(ThumbnailBean.java:316)
	at ome.services.ThumbnailBean.errorIfInvalidState(ThumbnailBean.java:570)
	at ome.services.ThumbnailBean.createScaledImage(ThumbnailBean.java:492)
	at ome.services.ThumbnailBean.retrieveThumbnailDirect(ThumbnailBean.java:962)
	at ome.services.ThumbnailBean._getThumbnailByLongestSideDirect(ThumbnailBean.java:1002)
	at ome.services.ThumbnailBean.getThumbnailByLongestSideDirect(ThumbnailBean.java:1017)

[jburel]

This is related to #2753 i.e. channel w/o stats info

[cxallan]

(In [8288]) Reverting r7441 and adding some more sanity checks to the Renderer. With r7441 it's possible that Images without channel statistics will get to the Renderer via the ThumbnailBean? and/or RenderingBean?. This can cause problems and the previous strategy of assigning min/max PixelType? range also causes the user to have to trigger a "resetDefaults()" if he/she attempted to view the Image while it was importing. We're sure that Jean-Marie made the changes for a good reason and we may need to review this again if there are further bugs that expose the issue outlined in #2545. (See #2545 and #2753; Fixes #3011)