I am also having this issue. Seems like a bug to me as it is not
possible to successfully call setValue() on a ListEditor once the
edited object has been frozen. It appears that this issue stems from
AbstractEditorDelegate.Chain.detach() trying to flush after the editor
is detached. I don't know what the right behavior is in this case: do
not ever flush when detaching, only flush if the underlying autobean
is not frozen, or make the autobean mutable and flush into that. In
this case, it would make sense not to flush, but there may be other
cases that require it.
Thanks,
Nick
On Dec 11, 10:23 am, Tobias <
thaberm...@gmail.com> wrote:
> Unfortunately I still have the problem with ListEditor's flushing
> behaviour, regardless of using a fresh Request, Driver, etc. I
> currently have to use a newly instantiated editor, which is probably
> not how it's supposed to work. I can't fill a ListEditor with a new
> value once the old has beenfrozen. Has anyone figured out, how to re-
> use ListEditors? Should I file a bug on this?
>
> Regards,
> Tobias
>
> On Dec 11, 4:29 pm, tshalif <
tsha...@gmail.com> wrote:
>
>
>
>
>
>
>
> > So, my case of 'AutoBeanhas beenfrozen' is simply the default mode