Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 316838

Summary:	CompositeTagRegistry cache of handlers should have lifecycle
Product:	[WebTools] Java Server Faces	Reporter:	Gerry Kessler <gerry.kessler>
Component:	JSF Tools	Assignee:	Ian Trimble <ian.trimble>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	cameron.bateman, ian.trimble, raghunathan.srinivasan
Version:	3.2
Target Milestone:	Future
Hardware:	PC
OS:	Windows XP
URL:	ORACLE_P1
Whiteboard:

Description Gerry Kessler

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

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

2010-09-06 12:10:08 EDT

Deferred due to lack of resources.

Comment 3 Cameron Bateman

2010-12-29 16:34:46 EST

Recommend addressing in Indigo.