Abstract: Methods for producing and validating RFID transponders (e.g., ISO 11784/11785 compliant transponders) with identification number authentication capabilities. A signature indicator and a partial-signature trailer are introduced to the ISO telegram. An encrypted signature or partial signature is introduced to the internal memory of ISO compliant transponders. The encrypted signature can prevent fraudulent duplications of ISO 11784/11785 transponders by allowing users to securely validate the transponders' authenticity.

Abstract: A virtual runtime module that omits an internal functional implementation of an associated executable module and that includes a runtime-resolvable public interface of the associated executable module is obtained using a processor within a module-based system. The virtual runtime module within the module-based system is resolved, using the runtime-resolvable public interface of the virtual runtime module, to satisfy dependencies associated with the executable module within the module-based system. At least a portion of the internal functional implementation of the associated executable module within the module-based system is installed during runtime using the resolved virtual runtime module.

Abstract: A virtual runtime module that omits an internal functional implementation of an associated executable module and that includes a runtime-resolvable public interface of the associated executable module is obtained using a processor within a module-based system. The virtual runtime module within the module-based system is resolved, using the runtime-resolvable public interface of the virtual runtime module, to satisfy dependencies associated with the executable module within the module-based system. At least a portion of the internal functional implementation of the associated executable module within the module-based system is installed during runtime using the resolved virtual runtime module.

Abstract: A virtual runtime module that omits an internal functional implementation of an associated executable module and that includes a runtime-resolvable public interface of the associated executable module is obtained using a processor within a module-based system. The virtual runtime module within the module-based system is resolved, using the runtime-resolvable public interface of the virtual runtime module, to satisfy dependencies associated with the executable module within the module-based system. At least a portion of the internal functional implementation of the associated executable module within the module-based system is installed during runtime using the resolved virtual runtime module.

Abstract: A method, computer apparatus and computer program product for bytecode weaving is described herein. The method includes determining when a code module such as an OSGi bundle that requires bytecode weaving becomes available for loading into a system. Code associated with the code module is loaded. This code may be part of the module itself or part of a separate entity, such as an OSGI bundle fragment, but does not require weaving. Responsive to loading the code associated with the code module, a reference is received to the entity responsible for loading the code associated with the code module. A code entity (which does require weaving) within the code module is identified and a woven set of bytes are provided to the code loading entity identified via the returned reference. Consequently, the woven set of bytes represents a transformed version of the identified code entity.

Abstract: A virtual runtime module that omits an internal functional implementation of an associated executable module and that includes a runtime-resolvable public interface of the associated executable module is obtained using a processor within a module-based system. The virtual runtime module within the module-based system is resolved, using the runtime-resolvable public interface of the virtual runtime module, to satisfy dependencies associated with the executable module within the module-based system. At least a portion of the internal functional implementation of the associated executable module within the module-based system is installed during runtime using the resolved virtual runtime module.

Abstract: A virtual runtime module that omits an internal functional implementation of an associated executable module and that includes a runtime-resolvable public interface of the associated executable module is obtained using a processor within a module-based system. The virtual runtime module within the module-based system is resolved, using the runtime-resolvable public interface of the virtual runtime module, to satisfy dependencies associated with the executable module within the module-based system. At least a portion of the internal functional implementation of the associated executable module within the module-based system is installed during runtime using the resolved virtual runtime module.

Abstract: A method, system, and/or computer program product manages a set of software modules in a software runtime environment, where the set of software modules has one or more dynamic dependencies and one or more static dependencies. Each software module having a static dependency on another software module in a set of software modules is identified. Each subset of the set of software modules that is interdependent with another subset due to static dependencies between subsets is identified. In response to a change in state of a module in an identified subset, the change in state is applied to all modules in the identified subset.

Abstract: A mechanism is provided for deciding whether to install a first application within one of a plurality of candidate environments. An environment comprising one or more other applications. The first application and a candidate environment are analyzed to determine whether there is the potential for the first application to interact in an unintended manner with an application in the candidate environment. If there is no such potential, then the environment is identified as a suitable environment into which to install the first application. An unintended interaction is when a rule would be broken by an interaction between the first application and an application in the candidate environment.

Abstract: A first request for a bundle resource can be sent to a first location. A first response can be received that identifies a second location. The first response can be analyzed to identify the second location. A second request and a third request can be created for a metadata resource and for an artifact resource. The second request can be sent to the second location. The third request can be sent to a third location. A second response and a third response can be received. The second response can comprise the metadata resource. The third response can comprise the artifact resource. The second response can be evaluated to determine the metadata resource. The third response can be evaluated to determine the artifact resource. The bundle resource can be created.

Abstract: Methods, computer program products, and systems for installing an application at a runtime instance. A method includes receiving a request to install an application and accessing data defining shared resources required by the application. Data that defines shared resources already installed at existing runtime instances is accessed. An existing runtime instance with the greatest number of installed shared resources common to the shared resources required by the application is selected. The application is installed at the selected runtime instance.

Abstract: A virtual runtime module that omits an internal functional implementation of an associated executable module and that includes a runtime-resolvable public interface of the associated executable module is obtained using a processor within a module-based system. The virtual runtime module within the module-based system is resolved, using the runtime-resolvable public interface of the virtual runtime module, to satisfy dependencies associated with the executable module within the module-based system. At least a portion of the internal functional implementation of the associated executable module within the module-based system is installed during runtime using the resolved virtual runtime module.

Abstract: A method, system, and/or computer program product manages a set of software modules in a software runtime environment, where the set of software modules has one or more dynamic dependencies and one or more static dependencies. Each software module having a static dependency on another software module in a set of software modules is identified. Each subset of the set of software modules that is interdependent with another subset due to static dependencies between subsets is identified. In response to a change in state of a module in an identified subset, the change in state is applied to all modules in the identified subset.

Abstract: A method, apparatus and computer program are disclosed for modifying an application comprising a plurality of modules. A user is presented with a list of modules. The user is able to specify input regarding any permitted version modifications for the modules listed. It is then determined whether the requested modifications are possible with one or more failure messages being output when any of the requested modifications are not possible. At least one of the failure messages is used to enable modification of the initial input provided by the user. In one embodiment, information is provided to the user based on one or more failure messages in order to enable the user to modify their choices. In another embodiment, the initial input is automatically modified. A permitted version modification may be, for example, a version upgrade, a version downgrade, and an indication that there is no preference.

Abstract: A method, apparatus and computer program are disclosed for modifying an application comprising a plurality of modules. A user is presented with a list of modules. The user is able to specify input regarding any permitted version modifications for the modules listed. It is then determined whether the requested modifications are possible with one or more failure messages being output when any of the requested modifications are not possible. At least one of the failure messages is used to enable modification of the initial input provided by the user. In one embodiment, information is provided to the user based on one or more failure messages in order to enable the user to modify their choices. In another embodiment, the initial input is automatically modified. A permitted version modification may be, for example, a version upgrade, a version downgrade, and an indication that there is no preference.

Abstract: Methods, computer program products, and systems for installing an application at a runtime instance. A method includes receiving a request to install an application and accessing data defining shared resources required by the application. Data that defines shared resources already installed at existing runtime instances is accessed. An existing runtime instance with the greatest number of installed shared resources common to the shared resources required by the application is selected. The application is installed at the selected runtime instance.

Abstract: A first instance of the application can be executed. While the first instance of the application is executing, at least one request to access the application (first access request) can be processed by directing the first access request to the first instance of the application. Further, a request to update the application can be received. Responsive to the request to update the application, at least one new application component corresponding to the update request can be installed. A second instance of the application can be executed. The second instance can include at least one new application component.

Abstract: A mechanism is provided for deciding whether to install a first application within one of a plurality of candidate environments. An environment comprising one or more other applications. The first application and a candidate environment are analysed to determine whether there is the potential for the first application to interact in an unintended manner with an application in the candidate environment. If there is no such potential, then the environment is identified as a suitable environment into which to install the first application. An unintended interaction is when a rule would be broken by an interaction between the first application and an application in the candidate environment.

Abstract: A first request for a bundle resource can be sent to a first location. A first response can be received that identifies a second location. The first response can be analyzed to identify the second location. A second request and a third request can be created for a metadata resource and for an artifact resource. The second request can be sent to the second location. The third request can be sent to a third location. A second response and a third response can be received. The second response can comprise the metadata resource. The third response can comprise the artifact resource. The second response can be evaluated to determine the metadata resource. The third response can be evaluated to determine the artifact resource. The bundle resource can be created.

Abstract: A method, apparatus and computer program are disclosed for modifying an application comprising a plurality of modules. A user is presented with a list of modules. The user is able to specify input regarding any permitted version modifications for the modules listed. It is then determined whether the requested modifications are possible with one or more failure messages being output when any of the requested modifications are not possible. At least one of the failure messages is used to enable modification of the initial input provided by the user. In one embodiment, information is provided to the user based on one or more failure messages in order to enable the user to modify their choices. In another embodiment, the initial input is automatically modified. A permitted version modification may be, for example, a version upgrade, a version downgrade, and an indication that there is no preference.