oracle.jdeveloper.deploy.tk

Interface Toolkit

All Known Subinterfaces:

ApplicationXmlBuilder, DependableFactory, DependableReader, DependableWriter, DeployActionsToolkit, DeployCommandFactory, DeployCommandReader, DeployCommandSummaryBuilder, DeployCommandWriter, DeployShellFactory, DeployToAppServerCommandFactory, DescriptorPackager, FileGroupPackager, FileGroupsPackager, FilesetPathTraversalFilter, FSMWizardBuilder, HashContributorReader, HashContributorWriter, HashDependableReader, HashDependableWriter, HashDeployCommandReader, HashDeployCommandWriter, HashProfileReader, HashProfileWriter, ModuleBuilder, Processor<T>, ProfileFactory, ProfileInfo, ProfileMigrator, ProfileReader, ProfileRecognizer, ProfileWriter, StatefulDescriptorPackager, StatefulFileGroupPackager, StatefulFileGroupsPackager, StatefulProcessor<T>, WizardBuilder, WizardState

All Known Implementing Classes:

AbstractDeployCommandIOProvider.DefaultDeployCommandIO, AbstractDeployToAppServerCommandFactory, AbstractFSMWizardBuilder, AbstractHashDependableIOProvider.DefaultHashDependableIO, AbstractHashDeployCommandIOProvider.DefaultHashDeployCommandIO, AbstractHashProfileIOProvider.DefaultHashProfileIO, AbstractHashProfileMigratorProvider.DefaultHashProfileMigrator, AbstractJLibraryProcessor, AbstractOffsetPathProcessor, AbstractProfileFactoryProvider.DefaultProfileFactory, AbstractProfileInfoProvider, AbstractWizardBuilder, AbstractWizardState, DefaultDeployShellFactory, DefaultProcessor, DefaultStatefulProcessor, DefaultWizardState, DeployActionsToolkitImpl, DeployActionsWizardState, DeploySummaryWizardState, DeployToAppServerWizardState, DeployWizardBuilder, DeployWizardState, DeployWizardStep, ProfileElementInfo, ProfileWizardBuilder, WizardStep

public interface Toolkit

Tagging interface. A Toolkit provides the ability to shape the interaction with a final or immutable object.

For example, to compile a Project, ideally we would want to write:

 Project p = new Project();
 p.compile();
 

But if Project does not already define a compile() method and if it is not sub-classable or has a blackbox implementation, this would not be possible. Even if Project did include a compile() method, downstream extensions may want to change the how 'compile' works, but this is not possible without sub-classing Project or having it expose integration hooks.

Instead a Compilable toolkit can be defined as:

 public interface Compilable extends Toolkit {
   void compile();
 }
 

Now given a Project, a Compilable can be 'built' for it.

    Context context = new Context(project);
    Compilable compilabe = ToolkitRegistry.getToolkit(context, Compilable.class);
    compilable.compile();
 

Extensions can plug in a ToolkitProvider and change how Compilable works for Projects.