Java Plugin Framework (JPF) 1.0 Released


News: Java Plugin Framework (JPF) 1.0 Released

  1. Java Plugin Framework (JPF) 1.0 Released (9 messages)

    JPF, an open source, LGPL licensed library intended to provide standard plug-in infrastructure Java projects, has reached version 1.0. It's been influenced by, but not derived from, Eclipse' plugin structure. It's designed to help improve modularity and extensibility of Java systems and decrease their support and maintenance cost. The framework implements the runtime engine that dynamically discovers and runs plug-ins. A plug-in is a structured component that describes itself to the Framework using a manifest file. The Framework maintains a registry of available plug-ins and the function they provide (via extension points and extensions). To simplify deployment and distribution, plug-in may be packaged as "single ZIP file" that will be un-packed transparently in runtime when needed. JPF package includes core runtime library, application boot utility and set of Ant tasks to automate common development routines (plug-ins versioning, packaging, documenting, integrity checks etc.) The major changes since previous release are: * Plug-in manifest DTD version number changed to 1.0 All references to previous versions are mapped to this one now. * Previously deprecated API has been removed from code. * Improved Splash Screen API in JPF-Boot library. It is now allows more flexible handling of splash screen behavior and configuration. * ShadingPathResolver may now filter files to be shadowed. This is regulated by includes/excludes configuration parameters. * Added black/white lists support to all batch plug-ins processing Ant tasks in JPF-Tools library. Visit the project home page for further details, documentation and tutorial. Message was edited by:

    Threaded Messages (9)

  2. How does this framework compare to OSGI?
  3. JPF is an alternative to OSGi that has similar set of features but much simple in learn and use. I'm not an expert in OSGi and thus can't give you side-by-side comparison. You may find several discussions on this theme at JPF forum: //Dmitry
  4. And what about JSR 277[ Go to top ]

    How does JPF position relative to JSR 277 Java Module system?
  5. Re: And what about JSR 277[ Go to top ]

    JPF is the complete ready to use solution to add modularity to any Java application. It is very flexible and extensible. Possibly it will be later adapted to JSR 277. //Dmitry
  6. How does it compare with?[ Go to top ]

    JMX and JBI?
  7. Eclipse and OSGi[ Go to top ]

    Eclipse abandoned their plug-in model in favor of OSGi... I think in the 3.2 timeframe. Spring is also working on support for OSGi. Does this project have a class loader similar to an EJB container that would let you run different versions of the same jar?
  8. Re: Eclipse and OSGi[ Go to top ]

    Their DTD seemed to allow you to specify version numbers, so I would guess so. But I don't see how it is supposed to be simpler than OSGI especially given the tooling support for OSGI in eclipse.
  9. Re: Eclipse and OSGi[ Go to top ]

    JPF implements plug-in classloaders isolation approach (like in Eclipse or Java EE containers). This allows you to run different versions of the same Java library in different plug-ins. //Dmitry
  10. How does it compare to SCA?[ Go to top ]

    How does JPF compares to Service Component Architecture (SCA)? Is it SCA complaint? Looks like it is yet another non-standards complaint component framework... :(