Re: [Exist-development] security refactoring

[Dannes W. <da...@ex...>]

if the dbx format is changed,  you should update a 'magic number', identifying a dbx-model update. Exist refuses to startup  when there is a difference between javacode and the code stored in the dbx files.

The only way to pass this, is a backup-restore.

These kind of changes are acceptable for trunk (not too often), but should be announced on the mailing list and in the commit message. Between versions (1.4.0 1.4.1) these changes are acceptable as well.

D.

On 21 Jul 2010, at 19:53 , Dmitriy Shabanov wrote:

> The trunk is POSSIBLE UNSTABLE, please let me know if any problem.
> 
> Should I change storage version (.dbx file) to force backup/restore,
> because of new security storage structure?
> 
> Should it be converted automatic or manual? (I think of manual way,
> pluggable realms will be turned off and only internal one (users.xml)
> will operate)

Kind regards

Dannes

--
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624