Cardvalidator Configuration
The bean accepts one or more of the following
configuration settings.
Configuration settings are similar in functionality to properties,
but they are rarely used. In order to avoid "polluting" the property
namespace of the bean, access to these
internal properties
is provided through the
Config method.
CardValidator Configuration Settings
| |
| NameOnCard: The name encoded in the track data on the credit card.If the TrackData you're parsing is Track1 data, it contains the customer's name, and should be identical
to the name printed on the face of the card. Track2 data does not contain this name. This field will be filled
after a call to ValidateCard.
|
Base Configuration Settings
| |
| GUIAvailable: Tells the bean whether or not a message loop is available for processing events.
In a GUI-based application, long-running blocking operations may cause the application to stop responding to input until the operation returns. The bean will attempt to discover whether or not the application has a message loop and, if one is discovered, it will process events in that message loop during any such blocking operation.
In some non-GUI applications an invalid message loop may be discovered that will result in errant behavior. In these cases, setting GuiAvailable to false will ensure that the bean does not attempt to process external events.
|
| UseDaemonThreads: Whether threads created by the bean are daemon threads.If set to True, when the bean creates a thread the thread's Daemon property will be explicitly set to True.
By default this setting is False and the bean will not set the Daemon property on the created thread.
|