On 14.02.2015, at 01:39, Carsten Ziegeler <[email protected]> wrote: > A value map can be seen as a copy of the data at the point it was > created. And especially as you know that you're doing a refresh, > why can't you refetch the value map once you did the refresh? > > Transparently handling a session refresh is not that easy, it might work > for your case and the value map. But I guess there are a lot of cases > where this doesn't work - or even is unexpected. Therefore simply > getting resources and representations again after a refresh is the > simplest and cleanest solution
I agree, but the code I was looking at seems to have its API designed based on that, hence it has its own modifying value map implementation... and I'd like to get rid of it. One could have an option in the JcrModifiableValueMap constructor for this - and by default it would not be used. The other approach of connecting a resource resolver refresh() with all value maps is probably not trivial and creates complex link between all the objects... Cheers, Alex
