To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=49148


User jb changed the following:

                  What    |Old value                 |New value
================================================================================
                    Status|STARTED                   |RESOLVED
--------------------------------------------------------------------------------
                Resolution|                          |FIXED
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Thu May 19 01:27:54 -0700 
2005 -------
The solution also needs to cater for schema files used indirectly through
<uses>/<import> references.

Because of this, the following solution was chosen:
- The UNO schema supplier may optionally support a new interface to associate
component schemas with version tags.
- Version tag changes cause cache invalidation
- The schema supplier uses a bootstrap setting as global version tag. The value
of this setting has to be changed between versions whenever schemas are changed
- As a defensive solution, the <buildid> from bootstraprc is now used as schema
version tag. As a result of this the cache is invalidated on every version
change. This includes the change from Beta to Final and should still work even
for ProductPatches.

Fixed on CWS nativefixer9.


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to