Providing external access to service versions via a bundle framework

• US 8,738,755 B2
• Filed: 09/09/2011
• Issued: 05/27/2014
• Est. Priority Date: 09/09/2011
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bohm, Fraser P., Cox, Benjamin D., Hargreaves, Ivan D.
• Primary Examiner(s): JACOBS, LASHONDA T
• Application Number:
  US13/229,295
• Publication Number:
  US 20130067058A1
• Time in Patent Office: 991 Days
• Field of Search: 709/224, 709/223, 709/217, 709/219, 709/220, 709/221
• US Class Current: 709/223
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators

Abstract

A bundle entering a set of starting and active bundles within a bundle framework is detected by a controller bundle executed by a processor. It is determined whether a manifest of the bundle includes an extension header that identifies an application and an aliased additional version of the application. It is determined whether an active application proxy object that represents the application as an active service registered from a previously-started bundle already exists within a service registry. An inactive application proxy object that represents a defined entry point class of the application and an additional active application proxy object that represents a defined entry point class of the aliased additional version of the application are created. The created additional active application proxy object is registered as an additional service within the service registry of the bundle framework.

Claims

1. A method, comprising:

detecting, via a controller bundle executed by a processor, a bundle entering a set of starting and active bundles within a bundle framework;

determining that a manifest of the bundle comprises an extension header that identifies an application and an aliased additional version of the application;

determining that an active application proxy object that represents the application as an active service registered from a previously-started bundle already exists within a service registry;

creating an inactive application proxy object that represents a defined entry point class of the application and an additional active application proxy object that represents a defined entry point class of the aliased additional version of the application; and

registering the created additional active application proxy object as an additional active service within the service registry of the bundle framework.

2. The method of claim 1, further comprising registering the created inactive application proxy object as an inactive service within the service registry of the bundle framework.

3. The method of claim 1, where determining that the manifest of the bundle comprises the extension header that identifies the application and the aliased additional version of the application comprises:

retrieving the manifest of the bundle;

parsing the manifest of the bundle; and

determining that the extension header comprises an executable binary of the application and the aliased additional version of the application.

4. The method of claim 1, where determining that the active application proxy object that represents the application as the active service registered from the previously-started bundle already exists within the service registry comprises:

searching the service registry of registered application proxy objects; and

identifying the active application proxy object that represents the application as an active service registered from the previously-started bundle as one of the registered application proxy objects.

5. The method of claim 1, where creating the inactive application proxy object that represents the defined entry point class of the application and the additional active application proxy object that represents the defined entry point class of the aliased additional version of the application comprises:

storing an entry point class name of the defined entry point class within the additional active application proxy object;

storing a reference to the bundle within the additional active application proxy object;

storing an entry point class name of the defined entry point class within the inactive application proxy object; and

storing the reference to the bundle within the inactive application proxy object.

6. The method of claim 5, where the active application proxy object that represents the application as the active service registered from the previously-started bundle comprises a stored reference to the previously-started bundle and a stored entry point class name of the application within the previously-started bundle and further comprising:

detecting, via the controller bundle executed by the processor, a request to execute the application;

identifying the active application proxy object that represents the application within the service registry;

retrieving, from the service registry, the reference to the previously-started bundle and the entry point class name stored within the active application proxy object that represents the application as the active registered service;

loading the defined entry point class of the application from the previously-started bundle using the retrieved reference to the previously-started bundle and the retrieved entry point class name; and

calling an entry method of the defined entry point class of the application within the previously-started bundle.

7. The method of claim 5, further comprising:

detecting, via the controller bundle executed by the processor, a request to execute the aliased additional version of the application;

identifying the additional active application proxy object that represents the aliased version of the application within the service registry;

retrieving, from the service registry, the reference to the bundle and the entry point class name stored within the additional active application proxy object that represents the aliased additional version of application as the additional active registered service;

loading the defined entry point class of the aliased additional version of the application from the bundle using the retrieved reference to the bundle and the retrieved entry point class name; and

calling an entry method of the defined entry point class of the aliased additional version of the application within the bundle.

8. A system, comprising:

a memory that stores a bundle framework; and

a processor programmed to;

detect, via a controller bundle executed by the processor, a bundle entering a set of starting and active bundles within a bundle framework;

determine that a manifest of the bundle comprises an extension header that identifies an application and an aliased additional version of the application;

determine that an active application proxy object that represents the application as an active service registered from a previously-started bundle already exists within a service registry;

create an inactive application proxy object that represents a defined entry point class of the application and an additional active application proxy object that represents a defined entry point class of the aliased additional version of the application; and

register the created additional active application proxy object as an additional active service within the service registry of the bundle framework.

9. The system of claim 8, where the processor is further programmed to register the created inactive application proxy object as an inactive service within the service registry of the bundle framework.

10. The system of claim 8, where in being programmed to determine that the manifest of the bundle comprises the extension header that identifies the application and the aliased additional version of the application, the processor is programmed to:

retrieve the manifest of the bundle;

parse the manifest of the bundle; and

determine that the extension header comprises an executable binary of the application and the aliased additional version of the application.

11. The system of claim 8, where in being programmed to determine that the active application proxy object that represents the application as the active service registered from the previously-started bundle already exists within the service registry, the processor is programmed to:

search the service registry of registered application proxy objects; and

identify the active application proxy object that represents the application as an active service registered from the previously-started bundle as one of the registered application proxy objects.

12. The system of claim 8, where in being programmed to create the inactive application proxy object that represents the defined entry point class of the application and the additional active application proxy object that represents the defined entry point class of the aliased additional version of the application, the processor is programmed to:

store an entry point class name of the defined entry point class within the additional active application proxy object in the service registry;

store a reference to the bundle within the additional active application proxy object in the service registry;

store an entry point class name of the defined entry point class within the inactive application proxy object in the service registry; and

store the reference to the bundle within the inactive application proxy object in the service registry.

13. The system of claim 12, where the active application proxy object that represents the application as the active service registered from the previously-started bundle comprises a stored reference to the previously-started bundle and a stored entry point class name of the application within the previously-started bundle and where the processor is further programmed to:

detect, via the controller bundle executed by the processor, a request to execute the application;

identify the active application proxy object that represents the application within the service registry;

retrieve, from the service registry, the reference to the previously-started bundle and the entry point class name stored within the active application proxy object that represents the application as the active registered service;

load the defined entry point class of the application from the previously-started bundle using the retrieved reference to the previously-started bundle and the retrieved entry point class name; and

call an entry method of the defined entry point class of the application within the previously-started bundle.

14. The system of claim 12, where the processor is further programmed to:

detect, via the controller bundle executed by the processor, a request to execute the aliased additional version of the application;

identify the additional active application proxy object that represents the aliased version of the application within the service registry;

retrieve, from the service registry, the reference to the bundle and the entry point class name stored within the additional active application proxy object that represents the aliased additional version of application as the additional active registered service;

load the defined entry point class of the aliased additional version of the application from the bundle using the retrieved reference to the bundle and the retrieved entry point class name; and

call an entry method of the defined entry point class of the aliased additional version of the application within the bundle.

15. A computer program product comprising a computer readable storage medium including computer readable program code, where the computer readable program code when executed on a computer causes the computer to:

detect a bundle entering a set of starting and active bundles within a bundle framework;

determine that a manifest of the bundle comprises an extension header that identifies an application and an aliased additional version of the application;

determine that an active application proxy object that represents the application as an active service registered from a previously-started bundle already exists within a service registry;

create an inactive application proxy object that represents a defined entry point class of the application and an additional active application proxy object that represents a defined entry point class of the aliased additional version of the application; and

register the created additional active application proxy object as an additional active service within the service registry of the bundle framework.

16. The computer program product of claim 15, where the computer readable program code when executed on the computer further causes the computer to register the created inactive application proxy object as an inactive service within the service registry of the bundle framework.

17. The computer program product of claim 15, where in causing the computer to determine that the manifest of the bundle comprises the extension header that identifies the application and the aliased additional version of the application the computer readable program code when executed on the computer causes the computer to:

retrieve the manifest of the bundle;

parse the manifest of the bundle; and

determine that the extension header comprises an executable binary of the application and the aliased additional version of the application.

18. The computer program product of claim 15, where in causing the computer to determine that the active application proxy object that represents the application as the active service registered from the previously-started bundle already exists within the service registry the computer readable program code when executed on the computer causes the computer to:

search the service registry of registered application proxy objects; and

identify the active application proxy object that represents the application as an active service registered from the previously-started bundle as one of the registered application proxy objects.

19. The computer program product of claim 15, where in causing the computer to create the inactive application proxy object that represents the defined entry point class of the application and the additional active application proxy object that represents the defined entry point class of the aliased additional version of the application the computer readable program code when executed on the computer causes the computer to:

store an entry point class name of the defined entry point class within the additional active application proxy object;

store a reference to the bundle within the additional active application proxy object;

store an entry point class name of the defined entry point class within the inactive application proxy object; and

store the reference to the bundle within the inactive application proxy object.

20. The computer program product of claim 19, where the active application proxy object that represents the application as the active service registered from the previously-started bundle comprises a stored reference to the previously-started bundle and a stored entry point class name of the application within the previously-started bundle and where the computer readable program code when executed on the computer further causes the computer to:

detect a request to execute the application;

identify the active application proxy object that represents the application within the service registry;

retrieve, from the service registry, the reference to the previously-started bundle and the entry point class name stored within the active application proxy object that represents the application as the active registered service;

load the defined entry point class of the application from the previously-started bundle using the retrieved reference to the previously-started bundle and the retrieved entry point class name; and

call an entry method of the defined entry point class of the application within the previously-started bundle.

21. The computer program product of claim 19, where the computer readable program code when executed on the computer further causes the computer to:

detect a request to execute the aliased additional version of the application;

identify the additional active application proxy object that represents the aliased version of the application within the service registry;

retrieve, from the service registry, the reference to the bundle and the entry point class name stored within the additional active application proxy object that represents the aliased additional version of application as the additional active registered service;

load the defined entry point class of the aliased additional version of the application from the bundle using the retrieved reference to the bundle and the retrieved entry point class name; and

call an entry method of the defined entry point class of the aliased additional version of the application within the bundle.