Bug: resetDefaults called in read-only group

[jamoore]

Found this in the log from Amanda Miotto. Either a check should be in place to prevent the call, or if it's being handled, then there's no reason for it to be logged with the full stack trace (see #7826)

Wed, 18 Jan 2012 04:07:21 blitz_gateway WARNING  ApiUsageException on <class 'webclient.webclient_gateway.OmeroWebSafeCallWrapper'> to <7f:0:0:1:455586e:134eefd9653:
-7ff4omero.api.ThumbnailStore> resetDefaults((), {})
Traceback (most recent call last):
  File "/opt/omero2/lib/python/omero/gateway/__init__.py", line 2954, in __call__
    return self.f(*args, **kwargs)
  File "/opt/omero2/lib/python/omero_api_ThumbnailStore_ice.py", line 184, in resetDefaults
    return _M_omero.api.ThumbnailStore._op_resetDefaults.invoke(self, ((), _ctx))
ApiUsageException: exception ::omero::ApiUsageException
{
    serverStackTrace = ome.conditions.ApiUsageException: Unable to reset rendering settings in a read-only group for Pixels set id:8
        at ome.services.ThumbnailBean.resetDefaults(ThumbnailBean.java:1236)

Two per image for several images:

    message = Unable to reset rendering settings in a read-only group for Pixels set id:51
    message = Unable to reset rendering settings in a read-only group for Pixels set id:51
    message = Unable to reset rendering settings in a read-only group for Pixels set id:11
    message = Unable to reset rendering settings in a read-only group for Pixels set id:11
    message = Unable to reset rendering settings in a read-only group for Pixels set id:7
    message = Unable to reset rendering settings in a read-only group for Pixels set id:7
    message = Unable to reset rendering settings in a read-only group for Pixels set id:9
    message = Unable to reset rendering settings in a read-only group for Pixels set id:9
    message = Unable to reset rendering settings in a read-only group for Pixels set id:8
    message = Unable to reset rendering settings in a read-only group for Pixels set id:8

[cxallan]

In milestone:OMERO-Beta4.4 this operation is visually dis-allowed in the full viewer for read-only group members, allowed for read-annotate group members (tested with user-1, user-2 and user-3 from the permissions list). Seems to have all been cleaned up by the permissions work and user interface work. Closing.