jpos.config/loader (JCL) - FAQ
The following is a set of frequently asked questions about the JCL:
The jpos.config/loader (JCL) is a simple binding API (configuration/loading) API for the JavaPOS services.
It exist to allow the JavaPOS controls to bind to the JavaPOS service in a manner independent of the actual configuration mechanism. In other words, the API defines an abstract API with a reference implementation and allows third parties to create their own implementation.
It is currently maintained by IBM and the JavaPOS technical committee.
As of the JavaPOS NY-2K meeting in January 2000. Sun has decided to endorse the JCL for JavaPOS. The JPS will eventually becomes an open source software at Sun once the legal issues can be resolved. For details see the JavaPOS web site for Sun's official position.
You will need the JavaPOS controls 1.4a or later, the JCL JAR files and an understanding on how to configure your services.
As of January 2000, all the JavaPOS technical committee member have pledge to support the JCL with their JavaPOS services.
The "simple" reference implementation is a pure Java implementation of the JCL. It stands as a very robust yet simple implementation of the JCL and also as an example implementation that third parties can use as a starting point to create their own implementation.
See the Simple JCL page for more details.
The JCL has been tested under the following JVM without any problems.
NOTE: the JCL is written all in Java and should run on all compliant JVM.
The JCL is all written in Java.
PS We have not tried to pass the 100% pure Java tests but we may in the future.
The JCL is an "open source" API that is currently maintained by IBM and the JavaPOS committee. See the current header of each of the Java files for more info on the legality issues...