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

Bug 316932

Summary:	[sfs] Implement ability to dynamically assign federated content providers
Product:	[Eclipse Project] e4	Reporter:	Eduard Bartsch <eduard.bartsch>
Component:	Resources	Assignee:	Eduard Bartsch <eduard.bartsch>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	mathias.kinzler, Szymon.Brandys
Version:	1.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Eduard Bartsch

2010-06-15 11:38:50 EDT

SFS currently provides a federation capability so that a content provider can delegate responsibility for parts of own resource hierarchy to other content providers. This feature persists the assigment of content providers to resource subtrees and works well only for static use cases where the assigment doesn't change over time. The cases where the assigment may change include refactoring of content provider implementations that may happen during software lifespan (e.g. during development phase or with a new release).

A more flexible and dynamic assigment of content providers is requested that is immune against content provider refactoring.

Requirements:
- The new functionality must coexist with the existing one.
- The new functionality must support recursion where a nested/federated content provider can itself be a federating one for other content providers.
- The new functionality must be able to work lasily without evaluation the whole resource tree.
- For performance and consistency reasons, the assigment must be "stable" during the whole Eclipse session.
- Support for refactoring/migration of file/folder hierarchy is out of scope and has to be tackled separately.

Comment 1 Eduard Bartsch

2010-09-20 11:29:30 EDT

Changes are released with v20100819-1010