Abstract: A system receives notification that at least one user interested in acquiring desired information is within a predefined area. The system receives the desired information from a client located within the predefined area, and electronically transmits the desired information to the at least one user. The desired information is received by the at least one user via a wireless device.

Abstract: A system receives notification that at least one user interested in acquiring desired information is within a predefined area. The system receives the desired information from a client located within the predefined area, and electronically transmits the desired information to the at least one user. The desired information is received by the at least one user via a wireless device.

Abstract: A Java code directive automatically defines the fields declaring methods in delegation objects such that the compiler generates the corresponding delegation signatures and/or headers. The configurations define a predetermined sequence, or annotation, of compiler interpreted instructions to identify a class as a delegation class from an invoking object, and generate the required signature, or header in the invoking object. The resulting signature satisfies the compiler restriction to implement each method in the delegation class. Particular methods for which a specific implementation is desired may then be superceded or supplemented by specific coded instructions in the invoking object. In this manner, a developer need not manually code the implementation, or signature (so-called “boilerplate code), for each method in a delegated object (class).

Abstract: A software compliance test is typically directed only at particular classes in the inheritance hierarchy. Inherited APIs (classes), which are not the focus of the test, may cause the application under test (AUT) to fail the compliance test since some of the underlying classes differ from a reference implementation. Accordingly, a verification tool employs the same version and implementation of inherited APIs in the reference implementation of these inherited APIs as the application under test. A dynamic class loader examines class inheritance references made by the application under test to determine if the class is included in the API to be tested, or if the class is outside the scope of the API to be tested. If the class corresponds to the API to be tested, then the dynamic loader uses the reference implementation of the API for comparison. Otherwise, the reference implementation employs the same inherited class references as the application under test.

Abstract: A method of verifying the identity of a user by comparing a biomorphic sample from the user with a stored biomorphic pattern of the user, without access to an online database of encoded biomorphic patterns. An authorization process receives an encoded biomorphic pattern from the user, the encoded biomorphic pattern stored on a storage device containing a processor. The processor is powered by a device capable of reading the storage device. The authorization process verifies the encoded biomorphic pattern is a valid biomorphic pattern with a valid expiration date, and compares the encoded biomorphic pattern on the storage device to a biomorphic sample provided by the user, in order to grant access to the user. If an online database is available, authorization process transmits the result to the online database and receives, in return, an updated expiration date. The authorization process updates the storage device with the updated expiration date.

Abstract: A method of automatically performing a component test at any number of locations in a distributed environment is disclosed. In general, in order to assure compatibility of the various components in an enterprise computing system, a service test is created as part of a compatibility test suite and passed to a test application server having a test application program. The test application program includes a generic vehicle class that includes a plurality of vehicle class invokers each of which is used to implement each of the object types that are run in each of a plurality of containers. During the build process of the CTS, each service test is automatically packaged with each of the appropriate vehicle classes so that each can be deployed into and run within the associated container.

Abstract: A method of automatically performing a component test at any number of locations in a distributed environment is disclosed. In general, in order to assure compatibility of the various components in an enterprise computing system, a service test is created as part of a compatibility test suite and passed to a test application server having a test application program. The test application program includes a generic vehicle class that includes a plurality of vehicle class invokers each of which is used to implement each of the object types that are run in each of a plurality of containers. During the build process of the CTS, each service test is automatically packaged with each of the appropriate vehicle classes so that each can be deployed into and run within the associated container.

Abstract: A method of automatically performing a component test at any number of locations in a distributed environment is disclosed. In general, in order to assure compatibility of the various components in an enterprise computing system, a service test is created as part of a compatibility test suite and passed to a test application server having a test application program. The test application program includes a generic vehicle class that includes a plurality of vehicle class invokers each of which is used to implement each of the object types that are run in each of a plurality of containers. During the build process of the CTS, each service test is automatically packaged with each of the appropriate vehicle classes so that each can be deployed into and run within the associated container.

Abstract: A method of concurrently performing a component test with returning test result data in a distributed environment is disclosed. In general, in order to assure compatibility of the various components in an enterprise computing system, a service test is created as part of a compatibility test suite and passed to a test application server having a test application program. The test application program makes an initial connection to the component being tested that, in response, creates a connection to a logging listener. The logging listener spawns an acceptor corresponding to the component being tested. Once spawned, the component returns test data to its corresponding acceptor concurrently with the execution of the test.