[ome-devel] Breaking changes in OmeroBlitz for Beta 4

[josh.moore at gmx.de]

OME coders,

As I mentioned recently, the OMERO trunk code is currently undergoing
experimental changes for Beta 4, like moving clients to the blitz
interface. To make that work cleaner and more stable, we're also
looking into fixing some low level issues, which we think it makes
sense to explore now.

One major issue, which we discussed today:
   https://www.openmicroscopy.org/site/community/minutes/conference-calls
was field visibility in the blitz objects.

Prior to Ice-3.2.1, there was no concept of setting class fields to
protected. By the time 3.2.1 came out, the fields had already become
part of the public API by default. We have seen instances, however, of
data corruption due to their misuse, and are sure that moving forward
it is in everyone's best interest to provide robust accessors.

We're painfully aware of the fact that changes such as lowering field
visibility are a burden on all our developers, but would prefer to do
the "right thing" to make this a more usable interface.

So, we're both very interested in any tips or feedback you might have
on any breakage appearing in trunk during the blitz experiment, and
determined, once the dust settles, to minimize the impact on all of
you.

Best wishes,
~Josh.