![]() ![]() This includes inline comments or references to documents bundled with the plug-in. ![]() Plug-ins are self-documenting Plug-in developers may include documentation in the plug-in manifest. Built-in integrity check Registered plug-ins are checked for consistency during JPF start up and a detailed report of results is available. Clear and consistent API design The JPF API has been carefully designed in order to reduce the the time developers need to become familiar with it. "Standard" or default implementations are provided by JPF so developers can start using the framework quickly and easily. Developers can choose to implement their own "vision" of plug-ins and Framework runtime behavior. Main features Open framework architecture The framework API is designed as a set of Java interfaces and abstract classes. Plug-ins are added to the registry at application start-up or while the application is running but they are not loaded until they are called. ![]() One major goal of JPF is that the application (and its end-user) should not pay any memory or performance penalty for plug-ins that are installed, but not used. JPF maintains a registry of available plug-ins and the functions they provide (via extension points and A plug-in is a structured component that describes itself to JPF using a "manifest". JPF provides a runtime engine that dynamically discovers and loads "plug-ins". JPF can greatly improve the modularity and extensibility of your Java systems and minimize support and maintenance costs. Welcome to the Java Plug-in Framework project, the open source, LGPL licensed plug-in infrastructure library for new or existing Java projects. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |