mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-07-15 21:15:23 +02:00
[150368] moved the implementation of the createDefaultFilterPool method from ServiceSubSystemConfiguration to SubSystemConfiguration
This commit is contained in:
parent
78f489ac1c
commit
dc366d4233
2 changed files with 30 additions and 37 deletions
|
@ -183,36 +183,6 @@ public abstract class ServiceSubSystemConfiguration extends SubSystemConfigurati
|
||||||
{
|
{
|
||||||
super.initializeSubSystem(subsys, yourNewConnectionWizardPages);
|
super.initializeSubSystem(subsys, yourNewConnectionWizardPages);
|
||||||
}
|
}
|
||||||
/**
|
|
||||||
* <i>Overridable lifecycle method. Typically overridden to supply a default filter.</i><br>
|
|
||||||
* When the user creates a new profile in the RSE (which is mapped to a SystemFilterPoolManager
|
|
||||||
* by our parent class), each subsystem factory that supports filters is asked if it wants to
|
|
||||||
* create a default system filter pool in that profile. <br>
|
|
||||||
* This is the method that is called to do that default filter pool creation in the new profile.
|
|
||||||
* <p>
|
|
||||||
* By default we create an <i>empty</i> filter pool with a generated name, and no pre-defined filters.
|
|
||||||
* If you don't want that behaviour, override this method and do one of the following:</p>
|
|
||||||
* <ul>
|
|
||||||
* <li>nothing if you don't want your subsystem factory to have a default filter pool in the new profile</li>.
|
|
||||||
* <li>call super.createDefaultFilterPool(mgr) to get the default pool, and then than call <samp>mgr.createSystemFilter(pool,...)</samp> to create
|
|
||||||
* each filter and add it to the filter pool, if you want to pre-populate the default pool with
|
|
||||||
* default filters.
|
|
||||||
* </ul>
|
|
||||||
*/
|
|
||||||
protected ISystemFilterPool createDefaultFilterPool(ISystemFilterPoolManager mgr)
|
|
||||||
{
|
|
||||||
ISystemFilterPool pool = null;
|
|
||||||
try {
|
|
||||||
// -----------------------------------------------------
|
|
||||||
// create a pool named filters
|
|
||||||
// -----------------------------------------------------
|
|
||||||
pool = mgr.createSystemFilterPool(getDefaultFilterPoolName(mgr.getName(), getId()), true); // true=>is deletable by user
|
|
||||||
} catch (Exception exc)
|
|
||||||
{
|
|
||||||
SystemBasePlugin.logError("Error creating default filter pool in default subsystem factory",exc); //$NON-NLS-1$
|
|
||||||
}
|
|
||||||
return pool;
|
|
||||||
}
|
|
||||||
|
|
||||||
// --------------------------------
|
// --------------------------------
|
||||||
// METHODS FOR SUPPLYING ACTIONS...
|
// METHODS FOR SUPPLYING ACTIONS...
|
||||||
|
|
|
@ -1754,15 +1754,38 @@ public abstract class SubSystemConfiguration implements ISubSystemConfiguration
|
||||||
// ---------------------------------
|
// ---------------------------------
|
||||||
|
|
||||||
/**
|
/**
|
||||||
* OVERRIDABLE METHOD FOR CHILD CLASSES TO ENABLE THEM TO CREATE A DEFAULT POOL
|
* <i>Overridable lifecycle method. Typically overridden to supply a default filter.</i><br>
|
||||||
* WHENEVER A NEW FILTER POOL MANAGER IS CREATED (EG, WHEN PROFILE CREATED).
|
* When the user creates a new profile in the RSE (which is mapped to a SystemFilterPoolManager
|
||||||
|
* by our parent class), each subsystem factory that supports filters is asked if it wants to
|
||||||
|
* create a default system filter pool in that profile. <br>
|
||||||
|
* This is the method that is called to do that default filter pool creation in the new profile.
|
||||||
* <p>
|
* <p>
|
||||||
* You should only pre-populate your default filter pool if this new manager
|
* By default we create an <i>empty</i> filter pool with a generated name, and no pre-defined filters.
|
||||||
* (eg, its really a profile) is the user's private own. Call {@link #isUserPrivateProfile(ISystemFilterPoolManager)}
|
* If you don't want that behaviour, override this method and do one of the following:</p>
|
||||||
* to find out if it is.
|
* <ul>
|
||||||
|
* <li>nothing if you don't want your subsystem factory to have a default filter pool in the new profile</li>.
|
||||||
|
* <li>call super.createDefaultFilterPool(mgr) to get the default pool, and then than call <samp>mgr.createSystemFilter(pool,...)</samp> to create
|
||||||
|
* each filter and add it to the filter pool, if you want to pre-populate the default pool with
|
||||||
|
* default filters.
|
||||||
|
* </ul>
|
||||||
*/
|
*/
|
||||||
protected abstract ISystemFilterPool createDefaultFilterPool(ISystemFilterPoolManager mgr);
|
protected ISystemFilterPool createDefaultFilterPool(ISystemFilterPoolManager mgr)
|
||||||
|
{
|
||||||
|
ISystemFilterPool pool = null;
|
||||||
|
try {
|
||||||
|
// -----------------------------------------------------
|
||||||
|
// create a pool named filters
|
||||||
|
// -----------------------------------------------------
|
||||||
|
pool = mgr.createSystemFilterPool(getDefaultFilterPoolName(mgr.getName(), getId()), true); // true=>is deletable by user
|
||||||
|
} catch (Exception exc)
|
||||||
|
{
|
||||||
|
SystemBasePlugin.logError("Error creating default filter pool in default subsystem factory",exc); //$NON-NLS-1$
|
||||||
|
}
|
||||||
|
return pool;
|
||||||
|
}
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
/**
|
/**
|
||||||
* Return true if the given filter pool manager maps to the private profile for this user.
|
* Return true if the given filter pool manager maps to the private profile for this user.
|
||||||
*/
|
*/
|
||||||
|
|
Loading…
Add table
Reference in a new issue