From 78286bc0861ac54985befd2e73662dec2337a1bf Mon Sep 17 00:00:00 2001 From: David Dykstal Date: Mon, 7 May 2007 18:55:38 +0000 Subject: [PATCH] [] --- .../core/filters/SystemFilterPoolManager.java | 77 +++---------------- 1 file changed, 12 insertions(+), 65 deletions(-) diff --git a/rse/plugins/org.eclipse.rse.core/src/org/eclipse/rse/core/filters/SystemFilterPoolManager.java b/rse/plugins/org.eclipse.rse.core/src/org/eclipse/rse/core/filters/SystemFilterPoolManager.java index 17fe547ff00..555142eeeca 100644 --- a/rse/plugins/org.eclipse.rse.core/src/org/eclipse/rse/core/filters/SystemFilterPoolManager.java +++ b/rse/plugins/org.eclipse.rse.core/src/org/eclipse/rse/core/filters/SystemFilterPoolManager.java @@ -34,62 +34,20 @@ import org.eclipse.rse.logging.Logger; /** * A filter pool manager manages filter pools. - *

- * Each filter pool that is managed becomes a folder on disk. - *

- * To create a filter pool manager instance, use the factory method - * in SystemFilterPoolManagerImpl in the ...impl package. - * You must pass a folder that represents the anchor point for the - * pools managed by this manager instance. - *

- * Depending on your tools' needs, you have four choices about how - * the filter pools and filters are persisted to disk. The decision is - * made at the time you instantiate the pool manager and is one of the - * following constants from the SystemFilterConstants interface: + * It is used to *

- *

- * With the policy of one file per pool, there are two possibilities regarding - * the folder structure: - *

*

- * With the policy of one file per filter, each filter pool must have its own folder. + * The filter pool manager ensures that + * changes to filters and pools are + * committed and events are fired properly. *

- * With an instantiated filter pool manager (most tools will only need - * one such instance), you now simply call its methods to work with - * filter pools. For example, use it to: - *

- * All the underlying file system work is handled for you. - *

- * Further, this is the front door for working with filters too. By forcing all - * filter related activity through a single point like this, we can ensure that - * all changes are saved to disk, and events are fired properly. - *

- * The filter framework logs to a {@link org.eclipse.rse.logging.Logger Logger} file. - * By default the log in the org.eclipse.rse.core plugin is used, but you can change this - * by calling {@link #setLogger(org.eclipse.rse.logging.Logger)}. - */ -/** - * @lastgen class SystemFilterPoolManagerImpl Impl implements SystemFilterPoolManager {} + * This class is not intended to be subclassed by clients. */ public class SystemFilterPoolManager extends RSEPersistableObject implements ISystemFilterPoolManager { private ISystemFilterPool[] poolArray = null; // cache for performance @@ -192,7 +150,7 @@ public class SystemFilterPoolManager extends RSEPersistableObject implements ISy /** * Constructor */ - protected SystemFilterPoolManager(ISystemProfile profile) { + private SystemFilterPoolManager(ISystemProfile profile) { super(); _profile = profile; } @@ -232,22 +190,11 @@ public class SystemFilterPoolManager extends RSEPersistableObject implements ISy public static ISystemFilterPoolManager createSystemFilterPoolManager(ISystemProfile profile, Logger logger, ISystemFilterPoolManagerProvider caller, String name, boolean allowNestedFilters, int savePolicy, IRSEFilterNamingPolicy namingPolicy) { - SystemFilterPoolManager mgr = SystemFilterPoolManager.createManager(profile); + SystemFilterPoolManager mgr = new SystemFilterPoolManager(profile); mgr.initialize(logger, caller, name, allowNestedFilters); return mgr; } - /* - * Private helper method. - * Uses MOF to create an instance of this class. - */ - public static SystemFilterPoolManager createManager(ISystemProfile profile) { - ISystemFilterPoolManager mgr = new SystemFilterPoolManager(profile); - - //FIXME SystemFilterImpl.initMOF().createSystemFilterPoolManager(); - return (SystemFilterPoolManager) mgr; - } - /* * Private helper method to initialize state */