CWA 16008-10:2009

J/eXtensions for Financial Services (J/XFS) for the Java Platform – Release 2009 - Part 10: Check Reader/Scanner Device Class Interface - Programmer's Reference

Scope

This document describes the Check Reader/Scanner class based on the basic architecture of J/XFS which is similar to the JavaPOS architecture. It is event driven and asynchronous.

This specification has been superseded by the new part 13: Scanner Class Interface and it is now deprecated. It is strongly suggested to use the new device class interface for new implementations.

Three basic levels are defined in JavaPOS. For J/XFS this model is extended by a communication layer, which provides device communication that allows distribution of applications and devices within a network. So we have the following layers in J/XFS:

- Application
- Device Control and Device Manager
- Device Communication
- Device Service

Application developers program against control objects and the Device Manager which reside in the Device Control layer. This is the usual interface between applications and J/XFS devices. Device Control objects access the Device Manager to find an associated Device Service. Device Service objects provide the functionality to access the real device (i.e. like a device driver).
During application startup the Device Manager is responsible for locating the desired Device Service object and attaching this to the requesting Device Control object. Location and/or routing information for the Device Manager reside in a central repository.

To support Check Reader/Scanner devices the basic Device Control structure is extended with various properties and methods specific to this device which are described on the following pages.