Abstract: A method provides an annotated language extension for the class of an object, the extension identifying an internal state that may be exposed via simple accessor methods. The extension could apply to an entire object type, or to a specific state within the object. Annotations that can be added to the extension include @Accessable, @Gettable and @Settable. In one embodiment, a method selectively accesses one or more object states. The method includes generating an annotated extension identifying each internal object state to be exposed for access, adding a usage annotation to the extension that defines an accessor method associated with each identified state, and operating a virtual machine to call the accessor method associated with a particular identified state. The particular state may then be accessed, as defined by the called accessor method.

Abstract: A method in a data processing system for attaching an informational dialog to a program. The program is morphed to extend an existing interface to the program to become a dippable program. A dip is created, wherein the dip modifies runtime behavior of the existing interface of the dippable program to include an informational dialog. The dip is added to the dippable program, wherein the informational dialog is attached to the dippable program. The dialog is displayed just before the dippable program is displayed.

Abstract: A method provides an annotated language extension for the class of an object, the extension identifying an internal state that may be exposed via simple accessor methods. The extension could apply to an entire object type, or to a specific state within the object. Annotations that can be added to the extension include @Accessable, @Gettable and @Settable. In one embodiment, a method selectively accesses one or more object states. The method includes generating an annotated extension identifying each internal object state to be exposed for access, adding a usage annotation to the extension that defines an accessor method associated with each identified state, and operating a virtual machine to call the accessor method associated with a particular identified state. The particular state may then be accessed, as defined by the called accessor method.

Abstract: A method, apparatus, and computer implemented instructions for binding object references from a remote name space into a local name space using a Web application. Information is collected to generate a request for an object reference. Information, such as an application server to use as the source, a source name space path, an identification of destination server, and a destination name space path to which the object reference is to be bound, may be used. The request is sent using a communications protocol, such as hypertext transfer protocol to the application server to be used as the source for the object reference. An object reference is located using the name space. The object reference may be serialized into a format, such as a common object request broker architecture format and sent to the destination. The destination will unserialize the object reference and perform binding using the destination name space path.

Abstract: A method and implementing computer system are provided in which route mapping for vehicles is determined between starting and destination points designated by an operator. Selected mapping is determined in accordance with operator selected travel-related criteria and augmented with traffic-related information. In one embodiment, after an initial route is set, the route is automatically updated whenever the vehicle strays from the set course, or whenever there is a change detected in related traffic conditions, or whenever subsequent changed travel points are input by the operator. The travel route and other related messaging may be conveyed to the operator by audio and/or visual devices onboard the vehicle.

Abstract: A process and system for providing name service scoping behavior is implemented. In an object-oriented data processing system, a request is received for an initial context for a namespace from a requesting object. A scoped initial context factory object is constructed, and an initial context is requested from the scoped initial context factory object. A class for the scoped initial context factory object may be determined from a variable in a hash table object passed as an argument. In response to the request for an initial context from the scoped initial context factory object, an initial context is requested from a non-scoped initial context factory object. The scoped initial context factory object may be a subclass of the non-scoped initial context factory object. The initial context returned by the non-scoped initial context factory object is scoped to a partition of the namespace, and the scoped initial context is returned.

Abstract: A method in a data processing system for attaching an informational dialog to a program. The program is morphed to become a dippable program. A dip is created, wherein the dip includes an informational dialog. The dip is added to the dippable program, wherein the informational dialog is attached to the dippable program. The dialog is displayed just before the dippable program is displayed.

Abstract: A method and implementing computer system are provided in which route mapping for vehicles is determined between starting and destination points designated by an operator. Selected mapping is determined in accordance with operator selected travel-related criteria and augmented with traffic-related information. In one embodiment, after an initial route is set, the route is automatically updated whenever the vehicle strays from the set course, or whenever there is a change detected in related traffic conditions, or whenever subsequent changed travel points are input by the operator. The travel route and other related messaging may be conveyed to the operator by audio and/or visual means onboard the vehicle.

Abstract: A method and implementing system are provided in which CORBA (Common Object Request Broker Architecture) Life Cycle Service FactoryFinder capabilities are combined with CORBA Naming Service resolve operations on a Naming Context. The methodology allows EJBHomes in a distributed network to be found using CORBA Life Cycle Services while maintaining support for the EJB (Enterprise Java Bean) programming model of using JNDI (Java Naming and Directory Interface) lookup calls to locate EJBHomes. Usage of Life Cycle Services in an EJB environment for finding EJBHomes by using Naming interfaces is enabled while using Life Cycle Service semantics. An exemplary embodiment is provided to allow deployment in different environments (including environments without Life Cycle support) and reconfiguration of the FactoryFinder being used, without requiring changes to source code.

Abstract: A system, method, and program product, in which a stateful EJB session bean is used as the front end to client calls. In this configuration, a queue is represented by a session bean instance. “Put” and “get” are called on the relevant session bean instances. Thus, for example, a client, instead of first finding a home for a given type of OMs then calling “put” on the home to send out messages, will find a session bean home, create a session bean instance corresponding to a queue, and call “put” on the bean instance to send messages. In this manner, the message queue can be managed using standard EJB techniques.

Abstract: A system, method, and software program for a fastpath redeployment of an Enterprise Java Bean (EJB). When an EJB is deployed, a copy of it is cached on the server. Thereafter, if the EJB is redeployed, it is compared to the cached copy to determine if the deployment descriptors or remote interfaces have changed. If there has been no change, then the previously deployed EJB is installed on the server, without the need to regenerate and recompile the EJB code.

Abstract: A method, apparatus, and computer implemented instructions for binding object references from a remote name space into a local name space using a Web application. Information is collected to generate a request for an object reference. Information, such as an application server to use as the source, a source name space path, an identification of destination server, and a destination name space path to which the object reference is to be bound, may be used. The request is sent using a communications protocol, such as hypertext transfer protocol to the application server to be used as the source for the object reference. An object reference is located using the name space. The object reference may be serialized into a format, such as a common object request broker architecture format and sent to the destination. The destination will unserialize the object reference and perform binding using the destination name space path.

Abstract: A method and apparatus for a general container mechanism for storage of object-oriented Java Beans. A repository is created for a persistent collection of items called ManagedBeans. Each ManagedBean contains a structured collection of code and data that makes up a Java Bean. The structured collection consists of items called ManagedBean Elements (MBE) which correspond to different types of code and data. Each ManagedBean Element is a subclass of the generic ManagedBean Element class. Each subclass identifies the different kinds of Bean sub-elements and contains the data contained in the corresponding file, and method that works on this data.

Abstract: A process and system for providing name service scoping behavior is implemented. In an object-oriented data processing system, a request is received for an initial context for a namespace from a requesting object. A scoped initial context factory object is constructed, and an initial context is requested from the scoped initial context factory object. A class for the scoped initial context factory object may be determined from a variable in a hash table object passed as an argument. In response to the request for an initial context from the scoped initial context factory object, an initial context is requested from a non-scoped initial context factory object. The scoped initial context factory object may be a subclass of the non-scoped initial context factory object. The initial context returned by the non-scoped initial context factory object is scoped to a partition of the namespace, and the scoped initial context is returned.

Abstract: A method and apparatus for extending a Java Beans Archive file. A key/value pair is added to the manifest file specification to allow an application to determine information about the sub-element composition of a Java Bean. The key provides a unique integer “N” which allows the specification of a Java Bean in the archive file. The value pair provides specification for a tag for indicating the type of a specific sub-element file in the archive file.

Abstract: A method and apparatus for extending the capability of uniform Resource Locators (URLs) to access Repositories on local and Internet connected remote machines. A general syntax for a uniform resource locator for a local machine has a protocol of "beans:", followed by an optional entry for a drive letter. The drive letter allows specification of a local device (e.g., A: or C: drive) where a repository is located. In addition, the general syntax contains entries for a file system path, repository name and Java Archive designation. The general syntax for the uniform resource locator for a remote machine has a protocol of "beans:" followed by entries for host name, file system path, repository name, and the Java Archive designation.

Abstract: A method and apparatus for using a Digital Signature Algorithm (DSA) for providing licensing of software. Three steps are required to allow setting up a license, issuing a license and for customer update of the license. An initialization step generates a public and private key pair. A license generation step follows the initialization step and involves feeding the private key and data for the license terms through the DSA to create a digital signature. The digital signature hash value is distributed to the customer as a valid license. The customer performs license verification by running the signature, public key and data for the license through the DSA on the customer's machine.