Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316838 - CompositeTagRegistry cache of handlers should have lifecycle
Summary: CompositeTagRegistry cache of handlers should have lifecycle
Status: NEW
Alias: None
Product: Java Server Faces
Classification: WebTools
Component: JSF Tools (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Ian Trimble CLA
QA Contact:
URL: ORACLE_P1
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-14 17:56 EDT by Gerry Kessler CLA
Modified: 2013-02-07 14:05 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gerry Kessler CLA 2010-06-14 17:56:07 EDT 
The map of handlers is keyed by content type and project.   When a project closes, the cache should be cleared of handlers for that project.
Comment 1 Cameron Bateman CLA 2010-06-23 17:19:52 EDT 
This can cause the tag registry to fail to reload things when configurations changed since a close/re-open is ignored.  Furthermore, if the individual tag registries are not disposed on close and external changes (i.e. a SCM sync) happen in the project before the reopen, this can cause these to not get uptaken.
Comment 2 Raghunathan Srinivasan CLA 2010-09-06 12:10:08 EDT 
Deferred due to lack of resources.
Comment 3 Cameron Bateman CLA 2010-12-29 16:34:46 EST 
Recommend addressing in Indigo.