Glyph Jini Annotations and Utilities 0.2 released

Discussions

News: Glyph Jini Annotations and Utilities 0.2 released

  1. The Glyph project is proud to announce its 0.2 release. Glyph is a set of utilities and annotations to speed up development for Jini-enabled applications. J2SE5.0 annotations are used for automatic service creation and creation of smart proxies for remote objects, and generation of associated Jini configuration files. A number of utilities have been written to help manage exported objects, and ease service initialization. This release adds a number of features such as ServiceUI annotations for binding Java GUIs to Services, pack200 jars for compressing mobile code and 3rd party libraries, and a first cut of a dependency injection engine that uses Jini configuration files. This release factors in a number of changes including:
    • No need to specify administrable on the @Service implementation class
    • Moved packages from net.java.dev.glyph to org.jini.glyph
    Additions
    • @LocalService for Fully Local Services
    • @ServiceUI - automatic creation of UIFactories and binding directly into the Service creation, by adding Annotation to a GUI component
    • @Injection - Dependency Injection engine (still under development)
    • AttributeBuilder - new class for dealing with Entries added on to service creation in code.
    • Integration with classdepandjar (which resolves class dependencies at build time)
    • Creation of classdepandjar buildfile for automatically creating the service dl file
    • Clean up processor for aggregating entities at the end of Apt processing
    • HyperJars (hjars) - reduces and combines jars and 3rd party libraries down to a single file of about 20% of total size of originaljars
    • hjar: and pack: URL handlers
    • PatchInstaller to patch hjar: and pack: handlers into jsk-resources.
    • HyperJarBuilderTask - Ant task automated to take classdep output and generate the hjar
  2. Nice to see activity in the JINI asrea, personally I believe that JINI is severely underutilized and deserves much more attention than it has these days.
  3. Documentation must be IMPROVED!!!!!!