![]() End Users Developers |
What? The jpos.config/loader (JCL)1 is a very simple loading/configuration API that is based on the now defunct JPS (aka JDDK, JSD/JSL, ...). It tries to abstract the most useful client2 parts of the JPS and exposes a very small API to allow JavaPOS controls to bind with a JavaPOS service. This binding requires configuration information that are place on a in-memory registry. This document serves as a readme for the JCL. It shows examples on how to use the JCL, configure the registry, use the provided reference implementation or how to create your own. This document also contains very simple example service code and shows how to use it. For more information on the JCL architecture and/or design, please refer to the JCL White Paper. Why? The JavaPOS API has been defined and somewhat "ready" since 1998, but it has always lacked a clearly defined mechanism for binding the controls to the services. The JCL aims at defining that missing API and removing any dependency in JavaPOS specification to other API. The JCL defines this binding API with a "plug-in" architecture to allow third-parties to define their own implementation if they want to extend the reference implementation. By whom? Many of the ideas of the JCL should be credited to Sun's original JSD/JSL API. The rest and abstraction idea comes from the JavaPOS technical committee. Legal Stuff The JCL is an OSS (open source software) API that is currently maintained by IBM and the JavaPOS committee. See the header below of each of the Java files for more info on the legality issues... <legal-header> ////////////////////////////////////////////////////////////////// </legal-header> Foonotes: 1 JCL also used to stand for Job Control Language, sometime during the Jurassic-age of computing 2 Client means that the JCL code must execute on the client JVM
|
||||
![]() |