Summary: | WTP needs an API on ServerPublishInfo to rebuild the cache for a specific module | ||||||
---|---|---|---|---|---|---|---|
Product: | [WebTools] WTP ServerTools | Reporter: | Troy Bishop <tjbishop> | ||||
Component: | wst.server | Assignee: | Angel Vera <arvera> | ||||
Status: | RESOLVED FIXED | QA Contact: | Angel Vera <arvera> | ||||
Severity: | normal | ||||||
Priority: | P1 | CC: | ccc | ||||
Version: | 3.0.5 | ||||||
Target Milestone: | 3.0.5 P | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Troy Bishop
2010-08-10 13:49:36 EDT
Created attachment 176258 [details]
possible patch to allow adaptors to destroy/rebuild the cache of a specific IModule
Adding hot bug request for including this patch into 305_patches: 1. Affiliation. IBM 2. Be clear on which release you want this bug to be fixed in, or "last workable" date, if requesting a patch. 3.0.5 patches 3. Justify why this is a hotbug. Note that "our users don't like the bug" is not the type of reason that gets much attention. The motivation we are looking for to justify a P1-like priority is, basically, "this bug blocks our adoption of WTP" (explaining why, of course). Introducing this API will allow our WTP adaptor product to selectively destroy the WTP publishing IModule cache when it executes its code-generators added as part of the publishers framework. Without this change we have to destroy the entire cache which means that the publish will need to perform an entire application delta computation for a second time and this can (when the application is very large) introduce significant publishing performance problems. One additional comment: this change does not need to be put into HEAD as the rebuildCache() API already exists there (from bug Bug 319288). Commited to R3_0_5_patches |