Skip to content

Release 2.0.1

Martin edited this page Mar 9, 2023 · 3 revisions

This is a replacement for version 2.0.0, which is basically buggy and has been replaced by this maintenance release.

This version supports UPOS 1.15.

Since Log4j version 1.2.7 (and all other Log4j versions 1.x as well) is out of date and version 2 is not fully compatible to version 1, JavaPOS-SPF has been changed to use Log4pos instead, a nearly source code compatible logging framework based on java.util.logging, that implements a very brief but sufficient subset of Apache log4j. Using of org.apache.log4j.Level constants is therefore deprecated, but use of the constants OFF, FATAL, ERROR, WARN, INFO, DEBUG, TRACE and ALL remains supported (but of cause requires any log4j jar file in addition to the Log4jpos jar file).

Asynchronous handling for Scale methods and asynchronous common methods have been changed to be handled the same way as for other asynchronous methods. Class OkException and method throwRequest have been removed from JposOutputRequest because they are no longer needed. All deprecated methods have been removed as well.

New method postDirectIOProcessing defined in JposBaseDevice can be overwritten in device service implementations to get feedback after the corresponding event has been fired. This is important whenever it is necessary to access the data and / or object component of the event after the event has been processed and perhaps changed by the application. In addition, JposDirectIOEvent objects become write protected after the event has been processed by the application.

Support for device class ElectronicValueRW has been added. This is important because it can be used as a replacement for the CAT device class with some important enhancements:

  • Due to support of the TransitionEvent in ElectronicValueRW, much more feed back from service to application and vice versa is possible during execution of authorization methods
  • Further service types can be integrated to support additional functionality, e.g. support for point cards or cash cards.

The ElectronicValueRW sample implementation shows only a possible CAT integration. It does not demonstrate how a service for other types as CAT should be implemented.

Clone this wiki locally