Transactional object container

• US 9,092,216 B2
• Filed: 04/19/2013
• Issued: 07/28/2015
• 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
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Nguyen, Mongbao
• Application Number:
  US13/866,929
• Publication Number:
  US 20130239088A1
• Time in Patent Office: 830 Days
• US Class Current: 1/1
• 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 a first transactional logic;

monitoring behavior of the transactional object;

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 a 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 in view of the monitoring; and

passing, by the processing device, the transactional proxy to the compiled application, wherein the compiled 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 in view of the received command;

setting the lock for the transactional object; and

forwarding the received command to the transactional object.

4. The method of claim 3, wherein the received 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 received 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. A computing apparatus, comprising:

a memory; and

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

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

monitor behavior of the transactional object;

determine a locking strategy to use for transactional object;

generate a transactional proxy for the transactional object, the transactional proxy comprises a transactional marker, a pointer to the transactional object, and a second transactional logic that supersedes the first transactional logic, the second transactional logic comprises the determined locking strategy to implement by the transactional proxy in view of the monitored behavior; and

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

8. The computing apparatus of claim 7, wherein the second transactional logic comprises logic to generate locks, to create transaction logs, and to commit and abort transactions, and wherein the transactional marker is to identify to a transaction system that the transactional proxy is to be managed transactionally.

9. The computing apparatus of claim 7, the processing device further to:

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

determine a lock to use for the transactional object in view of the received command;

set the lock for the transactional object; and

forward the received command to the transactional object.

10. The computing apparatus of claim 9, wherein the received command is a command to modify a state of the transactional object and the determined lock is a write lock, the processing device further 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.

11. The computing apparatus of claim 7, the processing device further 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.

12. A non-transitory computer readable storage medium comprising instructions to cause a processing device to:

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

monitor behavior of the transactional object;

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

generate, by the processing device, a transactional proxy for the transactional object, the transactional proxy comprises a transactional marker, a pointer to the transactional object, and a second transactional logic that supersedes the first transactional logic, the second transactional logic comprises the determined locking strategy to implement by the transactional proxy in view of the monitored behavior; and

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

13. The non-transitory computer readable storage medium of claim 12, wherein the second transactional logic comprises logic to generate locks, to create transaction logs, and to commit and abort transactions, and wherein the transactional marker is to identify to a transaction system that the transactional proxy is to be managed transactionally.

14. The non-transitory computer readable storage medium of claim 13, the processing device further to:

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

determine a lock to use for the transactional object in view of the received command;

set the lock for the transactional object; and

forward the received command to the transactional object.

15. The non-transitory computer readable storage medium of claim 14, wherein the received command is a command to modify a state of the transactional object and the determined lock is a write lock, the processing device further 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.

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

set the read lock for the transactional object.

17. The non-transitory computer readable storage medium of claim 12, the processing device further 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.