TRANSACTIONAL OBJECT CONTAINER

• US 20130239088A1
• Filed: 04/19/2013
• Published: 09/12/2013
• Est. Priority Date: 05/29/2009
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: LITTLE, MARK CAMERON
• Granted Patent: US 9,092,216 B2
• Time in Patent Office: Days
• US Class Current: 717/116
• CPC Class Codes: G06F 8/315 Object-oriented languages
• CPC Class Codes: G06F 8/41 Compilation
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/526 Mutual exclusion algorithms

Abstract

A processing device receives a transactional object at runtime of a compiled application, the transactional object comprising first transactional logic. The processing device determines a locking strategy to use for the transactional object. The processing device generates a transactional proxy for the transactional object, the transactional proxy comprising a transactional marker, a pointer to the transactional object, and second transactional logic that supersedes the first transactional logic. The processing device passes the transactional proxy to the application, wherein the application is to make calls on the transactional proxy instead of on the transactional object.

Claims

1. A method, comprising:

receiving, by a processing device, a transactional object at runtime of a compiled application, the transactional object comprising first transactional logic;

determining, by the processing device, a locking strategy to use for the transactional object;

generating, by the processing device, a transactional proxy for the transactional object, the transactional proxy comprising a transactional marker, a pointer to the transactional object, and second transactional logic that supersedes the first transactional logic, the second transactional logic comprising the determined locking strategy to be implemented by the transactional proxy; and

passing, by the processing device, the transactional proxy to the application, wherein the application is to make calls on the transactional proxy instead of on the transactional object.

2. The method of claim 1, wherein the second transactional logic comprises logic for generating locks, for creating transaction logs, and for committing and aborting transactions, and wherein the transactional marker identifies to a transaction system that the transactional proxy is to be managed transactionally.

3. The method of claim 1, further comprising:

receiving a command by the transactional proxy to perform an action;

determining a lock to use for the transactional object based on the received command;

setting the lock for the transactional object; and

forwarding the command to the transactional object.

4. The method of claim 3, wherein the command is a command to modify a state of the transactional object and the determined lock is a write lock, the method further comprising:

saving the state of the transactional object;

setting the write lock for the transactional object; and

enrolling in an active transaction for the transactional object.

5. The method of claim 3, wherein the command is a command to read a state of the transactional object and the determined lock is a read lock, the method further comprising:

setting the read lock for the transactional object.

6. The method of claim 1, further comprising:

receiving a command to generate the transactional object;

generating the transactional object using a first factory object; and

generating the transactional proxy for the transactional object using a second factory object that wraps the first factory object.

7. The method of claim 1, further comprising:

monitoring the transactional object, including monitoring a behavior of the transactional object; and

determining the second locking strategy for the transactional object based on the monitoring.

8. A computing apparatus, comprising:

a memory; and

a processing device, connected with the memory, the processing device to;

receive a transactional object at runtime of a compiled application, the transactional object comprising first transactional logic;

determine a locking strategy to use for transactional object;

generate a transactional proxy for the transactional object, the transactional proxy comprising a transactional marker, a pointer to the transactional object, and second transactional logic that supersedes the first transactional logic, the second transactional logic comprising the determined locking strategy to be implemented by the transactional proxy; and

pass the transactional proxy to the application, wherein the application is to make calls on the transactional proxy instead of on the transactional object.

9. The computing apparatus of claim 8, wherein the second transactional logic comprises logic for generating locks, for creating transaction logs, and for committing and aborting transactions, and wherein the transactional marker identifies to a transaction system that the transactional proxy is to be managed transactionally.

10. The computing apparatus of claim 8, the processing device being further configured to:

receive a command by the transactional proxy to perform an action;

determine a lock to use for the transactional object based on the received command;

set the lock for the transactional object; and

forward the command to the transactional object.

11. The computing apparatus of claim 10, wherein the command is a command to modify a state of the transactional object and the determined lock is a write lock, the processing device being further configured to:

save the state of the transactional object;

set the write lock for the transactional object; and

enroll in an active transaction for the transactional object.

12. The computing apparatus of claim 8, the processing device being further configured to:

receive a command to generate the transactional object;

generate the transactional object using a first factory object; and

generate the transactional proxy for the transactional object using a second factory object that wraps the first factory object.

13. The computing apparatus of claim 8, the processing device being further configured to:

monitor the transactional object, including monitoring a behavior of the transactional object; and

determine the second locking strategy for the transactional object based on the monitoring.

14. A non-transitory computer readable storage medium including instructions that, when executed by a processing device, cause the processing device to perform operations comprising:

receiving, by the processing device, transactional object at runtime of a compiled application, the transactional object comprising first transactional logic;

determining, by the processing device, a locking strategy to use for the transactional object;

generating, by the processing device, a transactional proxy for the transactional object, the transactional proxy comprising a transactional marker, a pointer to the transactional object, and second transactional logic that supersedes the first transactional logic, the second transactional logic comprising the determined locking strategy to be implemented by the transactional proxy; and

passing, by the processing device, the transactional proxy to the application, wherein the application is to make calls on the transactional proxy instead of on the transactional object.

15. The non-transitory computer readable storage medium of claim 14, wherein the second transactional logic comprises logic for generating locks, for creating transaction logs, and for committing and aborting transactions, and wherein the transactional marker identifies to a transaction system that the transactional proxy is to be managed transactionally.

16. The non-transitory computer readable storage medium of claim 15, the operations further comprising:

receiving a command by the transactional proxy to perform an action;

determining a lock to use for the transactional object based on the received command;

setting the lock for the transactional object; and

forwarding the command to the transactional object.

17. The non-transitory computer readable storage medium of claim 16, wherein the command is a command to modify a state of the transactional object and the determined lock is a write lock, the operations further comprising:

saving the state of the transactional object;

setting the write lock for the transactional object; and

enrolling in an active transaction for the transactional object.

18. The non-transitory computer readable storage medium of claim 16, wherein the command is a command to read a state of the transactional object and the determined lock is a read lock, the operations further comprising:

setting the read lock for the non-transactional object.

19. The non-transitory computer readable storage medium of claim 14, the operations further comprising:

receiving a command to generate the transactional object;

generating the transactional object using a first factory object; and

generating the transactional proxy for the transactional object using a second factory object that wraps the first factory object.

20. The non-transitory computer readable storage medium of claim 15, the operations further comprising:

monitoring the transactional object, including monitoring a behavior of the transactional object; and

determining the second locking strategy for the transactional object based on the monitoring.