import "ILoader.idl";
Inheritance diagram for upf::ILoader:
It finds all implementation modules it understands (e.g. all Java implementations) in given directories and registers contained classes in upf's runtime system so that instances of these classes can be created.
Public Types | |
typedef sequence< string > | FilesList |
List of filenames used by loadClasses. | |
typedef sequence< string > | ExtensionsList |
List of extensions. Extensions are strings the begin with ".". | |
Public Methods | |
void | loadClasses (in string path, in FilesList files) |
Loads all classes implemented in modules stored in path. | |
ExtensionsList | getExtensions () |
Returns list of file extensions that the loader can handle. | |
string | getDescription () |
Returns human-readable description of loader type. |
|
Returns human-readable description of loader type. Examples: "native shared library", "Python script" |
|
Returns list of file extensions that the loader can handle. This list will be used by UPF to enumerate files in directories added by upf::IManager::addModulesPath and they will be passed to loadClasses.
|
|
Loads all classes implemented in modules stored in path.
Loading consists of two steps: loading the modules and registering upf::IClassInfo objects for all classes contained withing the modules. The meaning of "load" and "module" is implementation-dependent. Standard implementation of ILoader interface,
|