From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.9 (X11; Linux i686; U;) Gecko/20030314 Description of problem: The XML content type loader re-creates the authoring kit on every startup of the server, even if nothing has changed since the last restart. This imposes a noticable overhead on startup, of about 9 seconds, out of total startup time of 36 seconds (25%). It should be made intelligent enough to only drop the authoring kit if it has changed. To reduce code duplication, this functionality should probably be added to c.a.cms.installer.ContentTypeSetup & the XML loader refactored to use this API for actual creation. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Examine contents of authoring_steps & authoring_kits tables 2. Restart a server 3. Examine contents of authoring_steps & authoring_kits tables Actual Results: All the object ids are different, indicating authoring kit has been recreated. Expected Results: All the object ids are the same in step 1 & 3, except when there has been an *actual* change to the Content type XML file. Additional info:
Closing old tickets