Data processing apparatus, method and system

• US 20040055005A1
• Filed: 09/02/2003
• Published: 03/18/2004
• Est. Priority Date: 05/31/2000
• Status: Abandoned Application

• Current Assignee: Intamission Ltd.
• Original Assignee: Intamission Ltd.
• Inventors: Warren, Nigel, Creswell, Dan
• Application Number:
  US10/297,044
• Publication Number:
  US 20040055005A1
• Time in Patent Office: Days
• US Class Current: 719/315
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44536 Selecting among different versions
• CPC Class Codes: G06F 9/44552 Conflict resolution, i.e. enabling coexistence of conflicting executables
• CPC Class Codes: G06F 9/4488 Object-oriented

Abstract

A data processing apparatus for providing an object-oriented execution environment, such as a virtual machine operable for first and second versions of the same class is disclosed. The data processing apparatus communicates with first and second services respectively operative for first and second versions of the same class. However, the first service is allowed to communicate only with a first version execution environment, and the second service is allowed to communicate only with a second version execution environment. The data processing apparatus is configured so that different versions of a class can share data or information between them.

Claims

1. A method of operating a data processing apparatus to provide an object-oriented execution environment operable for first and second versions of the same lass, said method comprising:

configuring said object-oriented execution environment to communicate with first and second services, said first service operative in accordance with said first version of the same class and said second service operative in accordance with said second version of the same class; and

further configuring said object-oriented execution environment to permit said first service to communicate only with a first version execution environment operative in accordance with said first version of the same class, and to permit said second service to communicate only with a second version execution environment operative in accordance with said second version of the same class.

2. A method according to claim 1, further comprising configuring said object-oriented execution environment to permit a third service operative in accordance with said first version of the same class to communicate only with said first version execution environment.

3. A method acording to claim 1 or 2, further comprising configuring said object-oriented execution environment to instantiate a first class context object including a first versioned class loader corresponding to said first version of the same class for establishing said first version execution environment, and to instantiate a second class context object including a second versioned class loader corresponding to said second version of the same class for establishing said second version execution environment.

4. A method according to claim 3, wherein said first versioned class loader comprises a method for implementing said first version of said same class to establish said first version execution environment in said object-oriented execution environment, and said second versioned class loader comprises a method for implementing said second version of said same class to establish said second version execution environment in said object-oriented execution environment.

5. A method according to claim 3 or 4, wherein said first version class loader includes a method for establishing an entry interface for said first version of the same class, said second version class loader includes a method for establishing an entry interface for said second version of the same class.

6. A method according to any one of claims 3 to 5, wherein said first and second version class loaders are operable to configure respective said first and second version execution environments to implement respective first and second versioned object input streams, said first versioned object input stream operable to receive a bit stream representative of a corresponding object in accordance with said first version of the same class and to output an object of said first version of the same class, and said second versioned object input stream operable to receive a bit stream representative of an object in accordance with said second version of the same class and to output a corresponding object of said second version of the same class.

7. A method according to any preceding claim, comprising configuring said object-oriented execution environment to keep a record of first and second version execution environments operable for said object-oriented execution environment, and to check a service call on said object-oriented execution environment against said record to determine which of said first or second service is making said call and to arrange for communication between a service originating said service call and one of said first or second version execution environments in dependence on a result of said check.

8. A method according to claim 3 or any one of claims 4 to 7 dependent on claim 3, further comprising configuring said object-oriented execution environment to load said first versioned class loader responsive to a service call from said first service.

9. A method according to claim 8, further comprising configuring said object-oriented execution environment to load said second versioned class loader responsive to a service call from said second service.

10. A method according to any preceding claim, further comprising configuring said object-oriented execution environment to provide first and second connection points, said first connection point arranged to permit said communication between said first service and said first version execution environment, and said second connection point arranged to permit said communication between said second service and said second version execution environment.

11. A method according to claim 10 dependent on claim 2, further comprising configuring said object-oriented execution environment to provide a third connection point corresponding to said third service, said third connection point arranged to permit said communication between said third service and said first version execution environment.

12. A method according to claim 10 or claim 11, wherein said first service is configured to communicate with only said first connection point of said first and second connection points, and said second service is configured to communicate with only said second connection point of said first and second connection points.

13. A method acording to claim 11 or claim 12 dependent on claim 11, wherein said third service is configured to communicate with only said third connection point of said first, second and third connection points,

14. A method according to any preceding claim, further comprising configuring said object-oriented execution environment to be responsive to a service call associated with a class version identifier.

15. A method according to claim 14, further comprising configuring said object-oriented execution environment to determine if a service call corresponds to said first or second version of said same class by inspection of said class version identifier associated with said service call.

16. A method according to claim 14 or claim 15, further comprising configuring said object-oriented execution environment to form said class version identifier from a hash of the byte code defining a corresponding version of the same class.

17. A method according to any one of claims 3 to 16 dependent on claim 3 wherein said first and second version class loaders are operable to configure said first and second version execution environments to remove class structure from an object instantiated in respective said first or second version execution environments to form a class version neutral object, and to associate an object identifier and a class version identifier with said class version neutral object.

18. A method according to claim 17, wherein said first and second version class loaders are operable to configure respective said first and second version execution environments to associate a class identifier with said class version neutral object.

19. A method according to claim 17 or 18, wherein said first and second version class loaders are operable to configure respective said first and second version execution environments to remove said class structure to form said class version neutral object by forming a bit or byte stream representative of said object.

20. A method according to any one of claims 3 to 19 dependent on claim 3, wherein said first and second version class loaders are operable to configure respective said first and second version execution environments to implement respective first and second versioned object output streams, said first versioned object output stream operable to receive an object of said first version of the same class and to output a bit or byte stream representative of said object of said first version of the same class and a first version identifier, and said second versioned object output stream operable to receive an object of said second version of the same class and to output a bit or byte stream representative of said object of said second version of the same class and a second version identifier, thereby to create a class version neutral object.

21. A method according to claim 19 or 20, wherein said first and second version class loaders are operable to configure said first and second version execution environments to include said class version identifier in said bit or byte stream.

22. A method according to any one of claims 19 to 21, said first and second version class loaders are operable to configure said first and second version execution environments to create said class version neutral object comprising an object identifier field, a class version identifier field and a field including said bit or byte stream.

23. A method according to claim 22, said first and second version class loaders are operable to configure said first and second version execution environments to create said class version neutral object further comprising a class name field indicative of the class of said object.

24. A method according to any one of claims 17 to 23, further comprising storing said class version neutral object.

25. A method according to claim 24, further comprising associating an index key with said class version neutral object indicative of the contents thereof.

26. A method of operating a data processing apparatus configured in accordance with claim 24 or 25, further comprising retrieving said class version neutral object from storage and converting said class version neutral object into a different class version object corresponding to a different class version to that class version from which said class version neutral object was formed.

27. A method according to claim 26, wherein said converting comprises populating a field of said different class version object with data from a corresponding field derived from said class version neutral object in accordance with said object identifier and class version identifier associated with said class version neutral object.

28. A method according to any one of claim 26 or 27, wherein said converting further comprises populating a field of said different class version object having no corresponding field in said class version neutral object with a default value.

29. A method according to any one of claims 26 to 28, wherein said first and second versioned object input streams are operable to recognise a version identifier in an input bit or byte stream, said method further comprising:

receiving a request from said first service to retrieve a stored object corresponding to an object identifier included in said request;

communicating said request to said first version execution environment;

retrieving a stored class version neutral object corresponding to said object identifier and placing it in said first version execution environment;

inputting said retrieved class version neutral object to said first versioned object input stream and identifying the class version associated with said retrieved class version neutral object as said second version of said same class; and

converting said class version neutral object into an object in accordance with said first version.

30. A method according to claim 29, further comprising said first versioned object input stream instantiating and populating the fields of an object of said first version of the same class with data corresponding to data held in corresponding fields of said retrieved class version neutral object as identified in accordance with said class version identifier.

31. A method according to claim 30, further comprising said first versioned object input stream populating fields of said object of said first version of the same class with null data for said retrieved class version neutral object comprising no corresponding field.

33. A computer program product comprising machine or computer-readable program element for configuring a data processing apparatus or computer to implement a method according to any one of claims 1 to 32.

34. A computer program product comprising machine or computer-readable program elements translatable to configure a data processing apparatus or computer to implement a method according to any one of claims 1 to 32.

35. A computer carrier medium carryig a computer program product according to claim 33 or 34.

32. A method according to claim 31, further comprising inputting said object in accordance with said first version converted from said second version to said first versioned object output stream to form a class version neutral object comprising a bit or byte stream representative of said first version object, and storing said class version neutral object.

32-1. A method for configuring a data processing apparatus for processing a class typed object in accordance with a class type version structure, comprising:

configuring said data processing apparatus with a versioned class loader for loading said class type version to provide a class type version execution environment;

providing said class type version execution environment corresponding to said class typed object;

receiving said class typed object;

removing class type structure from said class typed object to form an object independent of said class type version; and

associating a class typed object identifier and a class type version identifier with said class type version independent object.

36. A data processing apparatus for providing an object-oriented execution environment operable for first and second versions of the same class, said data processing apparatus configured to:

communicate with first and second services, said first service operative in accordance with said first version of the same class and said second service operative in accordance with said second version of the same class;

to permit said first service to communicate only with a first version execution environment operative in accordance with said first version of the same class; and

to permit said second service to communicate only with a second version execution environment operative in accordance with said second version of the same class.

37. Apparatus according to claim 36, further configured to permit a third service operative in accordance with said first version of the same class to communicate only with said first version execution environment.

38. Apparatus according to claim 36 or 37, further configured to instantiate a first class context object including a first versioned class loader corresponding to said first version of the same class for establishing said first version execution environment, and to instantiate a second class context object including a second versioned class loader corresponding to said second version of the same class for establishing said second version execution environment.

39. Apparatus according to claim 38, wherein said first versioned class loader is configured to implement said first version of said same class to establish said first version execution environments in said object-oriented execution environment, and said second versioned class loader is configured to implement said second version of said same class to establish said second version execution environments in said object-oriented execution environment.

40. Apparatus according to claim 38 or 39, wherein said first version class loader is configured to establish an entry interface for said first version of the same class, said second version class loader is configured to establish an entry interface for said second version of the same class.

41. Apparatus according to any one of claims 38 to 40, wherein said first and second version class loaders configure respective said first and second version execution environments to implement respective first and second versioned object input streams, said first versioned object input stream operable to receive a bit stream representative of a corresponding object in accordance with said first version of the same class and to output an object of said first version of the same class, and said second versioned object input stream operable to receive a bit stream representative of an object in accordance with said second version of the same class and to output a corresponding object of said second version of the same class.

42. Apparatus according to any one of claims 36 to 41, wherein said object-oriented execution environment is configured to keep a record of first and second version execution environments operable for said object-oriented execution environment, and to check a service call on said object-oriented execution environment against said record to determine which of said first or second service is making said call and to arrange for communication between a service originating said service call and one of said first or second version execution environments in dependence on a result of said check.

43. Apparatus according to claim 38 or any one of claims 39 to 42 dependent on claim 38, wherein said object-oriented execution environment is further configured to load said first versioned class loader responsive to a service call from said first service.

44. Apparatus according to claim 43, further comprising configuring said object-oriented execution environment to load said second versioned class loader responsive to a service call from said second service.

45. Apparatus according to any one of claims 36 to 44, wherein said object-oriented execution environment is further configured to provide first and second connection points, said first connection point arranged to permit said communication between said first service and said first version execution environment, and said second connection point arranged to permit said communication between said second service and said second version execution environment.

46. Apparatus according to claim 45 dependent on claim 37, wherein said object-oriented execution environment is configured to provide a third connection point corresponding to said third service, said third connection point arranged to permit said comunication between said third service and said first version execution environment.

47. Apparatus according to claim 45 or claim 46, wherein said first service is configured to communicate with only said first connection point of said first and second connection points, and said second service is configured to communicate with only said second connection point of said first and second connection points.

48. Apparatus according to claim 46 or claim 47 dependent on claim 46, wherein said third service is configured to communicate with only said third connection point of said first, second and third connection points,

49. Apparatus according to any one of claims 36 to 48, wherein said object-oriented execution environment is configured to be responsive to a service call associated with a class version identifier.

50. Apparatus according to claim 48, wherein said object-oriented execution environment is configured to determine if a service call corresponds to said first or second version of said same class by inspection of said class version identifier associated with said service call.

51. Apparatus according to claim 49 or claim 50, wherein said object-oriented execution environment is configured to form said class version identifier from a hash of the byte code defining a corresponding version of the same class.

52. Apparatus according to any one of claims 39 to 51 dependent on claim 39 wherein said first and second version class loaders are operable to configure said first and second version execution environments to remove class structure from an object instantiated in respective said first or second version execution environments to form a class version neutral object, and to associate an object identifier and a class version identifier with said class version neutral object.

53. Apparatus according to claim 52, wherein said first and second version class loaders are operable to configure respective said first and second version execution environments to associate a class identifier with said class version neutral object.

54. Apparatus according to claim 52 or 53, wherein said first and second version class loaders are operable to configure respective said first and second version execution environments to remove said class structure to form said class version neutral object by forming a bit or byte stream representative of said object.

55. Apparatus according to any one of claims 39 to 54 dependent on claim 39, wherein said first and second version class loaders are operable to configure respective said first and second version execution environments to implement respective first and second versioned object output streams, said first versioned object output stream operable to receive an object of said first version of the same class and to output a bit stream representative of said object of said first version of the same class and a first version identifier, and said second versioned object output stream operable to receive an object of said second version of the same class and to output a bit stream representative of said object of said second version of the same class and a second version identifier, thereby to create a class version neutral object.

56. Apparatus according to claim 54 or 55, wherein said first and second version class loaders are operable to configure said first and second version execution environments to include said class version identifier in said bit or byte stream.

57. Apparatus according to any one of claims 52 to 56, wherein said first and second version class loaders are operable to configure said first and second version execution environments to create said class version neutral object comprising an object identifier field, a class version identifier field and a field including said bit or byte stream.

58. Apparatus according to claim 57, wherein said first and second version class loaders are operable to configure said first and second version execution environments to create said class version neutral object further comprising a class name field indicative of the class of said object.

59. Apparatus according to any one of claims 52 to 58, further configured to store said class version neutral object.

60. Apparatus according to claim 59, further configured to associate an index key with said class version neutral object indicative of the contents thereof.

61. Apparatus configured in accordance with claim 59 or 60, and further configured to retrieve said class version neutral object from storage and to convert said class version neutral object into a different class version object corresponding to a different class version to that class version from which said class version neutral object was formed.

62. Apparatus according to claim 61, further configured to populate a field of said different class version object with data from a corresponding field derived from said class version neutral object in accordance with said object identifier and class version identifier associated with said class version neutral object.

63. Apparatus according to any one of claim 61 or 62, further configured to populate a field of said different class version object having no corresponding field in said class version neutral object with a default value.

64. Apparatus according to any one of claims 61 to 63, wherein said first and second versioned object input streams are operable to recognise a version identifier in an input bit or byte stream, said apparatus further configured to:

receive a request from said first service to retrieve a stored object coresponding to an object identifier included in said request;

communicate said request to said first version execution environment;

retrieve a stored class version neutral object corresponding to said object identifier and place it in said first version execution environment;

input said retrieved class version neutral object to said first versioned object input stream and identify the class version associated with said retrieved class version neutral object as said second version of said same class; and

convert said class version neutral object into an object in accordance with said first version.

65. Apparatus according to claim 64, said first versioned object input stream configured to instantiate and populate the fields of an object of said first version of the same class with data corresponding to data held in corresponding fields of said retrieved class version neutral object as identified in accordance with said class version identifier.

66. Apparatus according to claim 65, said first versioned object input stream further configured to populate fields of said object of said first version of the same class with null data for said retrieved class version neutral object comprising no corresponding field.

67. Apparatus according to claim 66, further configured to input said object in accordance with said first version converted from said second version to said first versioned object output stream to form a class version neutral object comprising a bit or byte stream representative of said first version object, and to store said class version neutral object.

69. A computer system network, comprising:

data processing apparatus according to any one of claims 36 to 68 for providing a server computer system; and

a client computer system operable to communicate with said server computer system;

said client computer system comprising means for establishing communication with said server computer system for operation in a first or second class version defined by said client computer system.

70. A computer system network according to claim 69, said server computer system responsive to a communication with said client computer system to load said first or second class version in dependence on said client computer system from a class version storage medium.

71. A computer system network according to claim 70 and operable for an Internet, said class version storage medium corresponding to a URL communicated to said server from said client.

68. A data processing apparatus for processing a class typed object in accordance with a class type version structure, configured to:

include a versioned class loader for loading said class type version to provide a class type version execution environment;

provide said class type version execution environment corresponding to said class typed object;

receive said class typed object;

remove class type structure from said class typed object to form an object independent of said class type version; and

associate a class typed object identifier and a class type version identifier with said class type version independent object.

72. A method substantially as hereinbefore described for respective embodiments and with reference to respective Figures of the Drawings.

73. A computer program substantially as hereinbefore described for respective embodiments and with reference to respective Figures of the Drawings.

74. Data processing apparatus substantially as hereinbefore described for respective embodiments and with reference to respective Figures of the Drawings.

75. A computer system substantially as hereinbefore described for respective embodiments and with reference to respective Figures of the Drawings.