Re: frozen node modifications

[Marco Piovesana <pi...@esteco.com>]

Hi Chetan,
> Note that for one time upgrade work you can still modify the content
> in version store using the NodeStore API directly.

how exactly can I do that? I can use the *NodeStore* to do a *merge*
on a *NodeBuilder,
*and I can get the *NodeBuilder *for the node I need to modify from the
NodeStore itself. But how can I modify a specific FrozenNode starting from
a NodeBuilder? Am I trying to use the wrong method?

On Tue, Aug 8, 2017 at 11:09 AM, Chetan Mehrotra <ch...@gmail.com>
wrote:

> > From my point of view, blocking the modification of the history even for
> > the system that uses Oak as a library, makes its usage far more
> complicated
> > in terms of upgrade without any true benefit in terms of security.
>
> Note that for one time upgrade work you can still modify the content
> in version store using the NodeStore API directly. But then you would
> need to be careful and understand how versioned data is stored
>
> Chetan Mehrotra
>



-- 

marco piovesanA
Enterprise Application



*ESTECO* | EXPLORE DESIGN PERFECTION

AREA Science Park, Padriciano 99 - 34149 Trieste - ITALY
Phone: +39 040 3755548 - Fax: +39 040 3755549
[Website] <http://www.esteco.com> | [Twitter]
<https://twitter.com/esteco_mF> | [Facebook]
<https://www.facebook.com/esteco.spa> | [Linkedin]
<https://www.linkedin.com/company/748217>
Pursuant to Legislative Decree No. 196/2003, you are hereby informed that
this message contains confidential information intended only for the use of
the addressee. If you are not the addressee, and have received this message
by mistake, please delete it and immediately notify us. You may not copy or
disseminate this message to anyone. Thank you. Please consider the
environment before printing this email.