org.eclipse.core.runtime.IExecutableExtensionFactory Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of aspectjtools Show documentation
Show all versions of aspectjtools Show documentation
AspectJ tools most notably contains the AspectJ compiler (AJC). AJC applies aspects to Java classes during
compilation, fully replacing Javac for plain Java classes and also compiling native AspectJ or annotation-based
@AspectJ syntax. Furthermore, AJC can weave aspects into existing class files in a post-compile binary weaving step.
This library is a superset of AspectJ weaver and hence also of AspectJ runtime.
/*******************************************************************************
* Copyright (c) 2005, 2012 IBM Corporation and others.
*
* This program and the accompanying materials
* are made available under the terms of the Eclipse Public License 2.0
* which accompanies this distribution, and is available at
* https://www.eclipse.org/legal/epl-2.0/
*
* SPDX-License-Identifier: EPL-2.0
*
* Contributors:
* IBM Corporation - initial API and implementation
*******************************************************************************/
package org.eclipse.core.runtime;
/**
* This interface allows extension providers to control how the instances provided to extension-points are being created
* by referring to the factory instead of referring to a class. For example, the following extension to the preference page
* extension-point uses a factory called PreferencePageFactory
.
*
* <extension point="org.eclipse.ui.preferencePages">
* <page name="..." class="org.eclipse.update.ui.PreferencePageFactory:org.eclipse.update.ui.preferences.MainPreferencePage">
* </page>
* </extension>
*
*
*
*
*
* Effectively, factories give full control over the create executable extension process.
*
* The factories are responsible for handling the case where the concrete instance implement {@link IExecutableExtension}.
*
* Given that factories are instantiated as executable extensions, they must provide a 0-argument public constructor.
* Like any other executable extension, they can configured by implementing {@link org.eclipse.core.runtime.IExecutableExtension} interface.
*
* This interface can be used without OSGi running.
*
* @see org.eclipse.core.runtime.IConfigurationElement
*/
public interface IExecutableExtensionFactory {
/**
* Creates and returns a new instance.
*
* @exception CoreException if an instance of the executable extension
* could not be created for any reason
*/
Object create() throws CoreException;
}