Nice idea, from my POV.
This could also solve the problem of restoring a version history backup,
or all "protected" values related problems.
But of course, it would go against the initial JSR-170 spec.
This point actually highlights the lack of administrative API in JR,
doesn't it ?
It may be the right time to think to such an API ?
WDYT ?
Regards,
Cédric
Jukka Zitting a écrit :
Hi,
Every now and then I see people running into issues with the current
limitations in modifying node types in Jackrabbit. The recent JCR-954
issue also highlighted a similar problem with referential integrity
checks. For various reasons the strict integrity checks in Jackrabbit
end up hurting valid use cases.
The proper solution to the problem would be to actually implement the
missing node type modification support and to optimize the use cases
in JCR-954, but it seems to me that we are at least a year if not more
away from such solutions.
Thus I would like to float the idea of a "raw mode" in Jackrabbit. The
"raw mode" would be a session-level attribute, enabled during login,
that would disable all node type and reference checks for that
session. The mode would only be available to administrator users,
perhaps even only when no other sessions are accessing the repository.
BR,
Jukka Zitting
--
Cédric Damioli
ANYWARE TECHNOLOGIES
Tel : +33 (0)5 61 00 73 47
Fax : +33 (0)5 61 00 51 46
http://www.anyware-tech.com
