Community
Participate
Working Groups
SystemFilterPoolManager seems to be an implementation class only. All client access happens through ISystemFilterPoolManager, and it is not intended to be extended. The instance creation method SystemFilterPoolManager.createSystemFilterPoolManager() should be moved somewhere else, I would propose into RSECorePlugin or into IRSEPersistenceManager. Javadoc of SystemFilterPoolManager should be cleaned up from references like "every filter maps to a folder" -- with the new persistence scheme this is not necessarily true any more. Also, Javadoc should say "This class is not intended to be subclassed by clients".
Agreed.
In preparation for moving the class to org.eclipse.rse.internal.core.filters we will remove the unused static public factory method that was commented as private and change the class comments to remove all persistence policy language. I recommend that we leave the static factory method as is for now. Neither of the suggested places appear to be a good place for it. Moving the class to internal makes finding a home for this a bit less of a problem. At some point in the future the using class SubSystemConfiguration should be moved into the core plugin as well so the use of an internal class does not pose a problem at this time.
[api][refactor] Move SystemFilterPoolManager to org.eclipse.rse.internal.core.filters.
[target cleanup] 2.0 M7 was the original target milestone for this bug