On 05/23/10 09:50, Patrick Bernard wrote:
Le jeudi 20 mai 2010, Stephan Bergmann a écrit :
On May 20, 2010, at 9:45 AM, Patrick Bernard wrote:
Is it possible design a schema so that configuration data can be migrated
from an older to a newer version of the schema ? What is the best way to
do it ?
When, upon OOo startup, the configmgr implementation encounters any
configuration data items (typically from the user layer, storing the
changes made by the user through the GUI or programmatically through the
UNO API) that do not match a schema, those items are simply ignored. That
pretty much limits how you can migrate such data---do not make incompatible
changes to your schema, only ever add to it.
You say that it is possible to change a schema. On the other hand, the
developer's guide states in
Config/Creating_a_Custom_Configuration_Schema : "An installed schema is
assumed to not change any more." Do I have to conclude that the DevGuide
isn't accurate ?
You really should not change existing schemas, as that causes trouble.
What I described above is what happens if you do change a schema
nonetheless.
Assuming a schema can be modified, under what conditions are the modifications
taken into account (see issue 80296) ?
In current OOo (DEV300_m79), the situation is as follows. If an
extension is updated from within a running OOo instance, the information
from the .xcs files of the old extension version is not discarded
immediately and the information from the .xcs files of the new extension
version is merged with the existing schema information (for details, see
function merge in configmgr/source/xcsparser.cxx). After the next OOo
restart, the information from the .xcs files of the old extension
version is gone, and the information from the .xcs files of the new
extension version is used as is.
(Note that I just updated
<http://qa.openoffice.org/issues/show_bug.cgi?id=80296>.)
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
