Accessing information at object creation

• US 7,353,506 B2
• Filed: 10/23/2003
• Issued: 04/01/2008
• Est. Priority Date: 10/23/2003
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Inventors: Bley, John B.
• Primary Examiner(s): KENDALL, CHUCK O
• Application Number:
  US10/692,250
• Publication Number:
  US 20050091638A1
• Time in Patent Office: 1,622 Days
• Field of Search: None
• US Class Current: 717/158
• CPC Class Codes: G06F 11/3624 by performing operations on the source code, e.g. via a compiler

Abstract

A system is disclosed for accessing information about an object, where such information is available at the time of creation of the object but not necessarily available at all times later. In one embodiment, existing object code is modified to add the ability to access the information. The modified code is then executed.

Claims

1. A method for adding functionality in order to access information, comprising:

automatically modifying a first portion of existing code, said modifying said first portion of existing code includes adding first additional code to said first portion of existing code, said first portion of existing code creates a software entity, said first additional code stores first data relevant to said software entity, said first data is available when said first software entity is created; and

automatically modifying a second portion of existing code, said modifying said second portion of existing code includes adding second additional code to said second portion of existing code, said second portion of existing code uses said software entity, said second additional code accesses second data relevant to said software entity and correlates said second data with said first data.

2. A method according to claim 1, wherein:

said first portion of existing code and said second portion of existing code are part of a single application.

3. A method according to claim 1, wherein:

said second data relevant to said software entity includes information about use of said software entity.

4. A method according to claim 1, wherein:

said software entity is an object.

5. A method according to claim 1, wherein:

said first portion of existing code and said second portion of existing code are object code.

6. A method according to claim 1, wherein:

said first portion of existing code and said second portion of existing code are Java object code.

7. A method according to claim 1, wherein:

said first portion of existing code is part of a larger set of code; and

prior to said step of automatically modifying said first portion of existing code, said first data is not always made available by said larger set of code.

8. A method according to claim 1, further comprising the steps of:

executing said first additional code with said first portion of existing code; and

executing said second additional code with said second portion of existing code.

9. A method according to claim 1, further comprising the steps of:

storing said first additional code with said first portion of existing code; and

storing said second additional code with said second portion of existing code.

10. A method according to claim 1, wherein:

said second additional code traces said software entity in order to produce trace data; and

said second data includes said trace data.

11. A method according to claim 10, wherein:

said software entity is an object;

said first additional code stores said object with said first data;

said second additional code uses said object to correlate said trace data with said first data.

12. A method according to claim 1, wherein:

said software entity is an object that pertains to a connection.

13. A method according to claim 1, wherein:

said first data indicates an SQL statement;

said software entity is an object that pertains to said SQL statement;

said first portion of existing code receives said SQL statement;

said first additional code stores said SQL statement and said object;

said second additional code traces a use of said object and produces resulting trace data, said second additional code stores said trace data with said first data; and

said second portion of existing code causes the execution of said SQL statement.

14. A machine implemented method for adding functionality in order to access information, comprising:

automatically adding first additional object code to a first portion of existing object code, said first portion of said existing object code creates a software entity, said first additional object code stores first data relevant to said software entity, said first data is available to said existing object code when said first software entity is created; and

automatically adding second additional object code to a second portion of said existing object code, said second portion of said existing object code uses said software entity, said second additional object code accesses second data relevant to said software entity and correlates said second data with said first data after said second data is accessed.

15. A method according to claim 14, wherein:

said software entity is an object; and

said first existing code and said second existing code are object code.

16. A method according to claim 14, wherein:

said step of adding second additional code includes adding code that traces said software entity and produces trace data, said second data includes said trace data; and

said step of adding second additional code further includes adding code that stores said trace data with said first data using said first software entity to correlate said trace data with said first data.

17. A method according to claim 14, wherein:

said software entity is an object;

said step of adding first additional code includes adding code that stores said object with said first data; and

said step of adding second additional code includes adding code that uses said object to correlate said second data with said first data.

18. A method according to claim 14, wherein:

said first data indicates an SQL statement;

said software entity is an object that pertains to said SQL statement;

said first existing code receives said SQL statement;

said second existing code causes the execution of said SQL statement;

said step of adding first additional code includes adding code that stores said SQL statement and said object; and

said step of adding second additional code includes adding code that traces a use of said object thereby producing trace data and stores said trace data with said first data.

19. One or more processor readable storage devices, comprising:

processor readable code embodied on said processor readable storage devices, said processor readable code for programming one or more processors automatically adds first additional code to first existing code, said first existing code creates a software entity, said first additional code stores first data relevant to said software entity, said first data is available when said software entity is created, said processor readable code automatically adds second additional code to second existing code, said second existing code uses said software entity, said second additional code accesses second data relevant to said software entity and correlates said second data with said first data after said second data is accessed.

20. One or more processor readable storage devices according to claim 19, wherein:

said software entity is an object; and

said first existing code and said second existing code are object code.

21. One or more processor readable storage devices according to claim 19, wherein:

said step of adding second additional code includes adding code that traces said software entity and produces trace data, said second data includes said trace data; and

said step of adding second additional code further includes adding code that stores said trace data with said first data using said software entity to correlate said trace data with said first data.

22. One or more processor readable storage devices according to claim 19, wherein:

said software entity is an object;

said step of adding first additional code includes adding code that stores said object with said first data; and

said step of adding second additional code includes adding code that uses said object to correlate said second data with said first data.

23. One or more processor readable storage devices according to claim 19, wherein:

said first data indicates an SQL statement;

said software entity is an object that pertains to said SQL statement;

said first existing code receives said SQL statement;

said second existing code causes the execution of said SQL statement;

said step of adding first additional code includes adding code that stores said SQL statement and said object; and

said step of adding second additional code includes adding code that traces a use of said object thereby producing trace data and stores said trace data with said first data.

24. An apparatus for adding functionality in order to access information, comprising:

a communication interface;

a storage device; and

one or more processors, said one or more processors in communication with said communication interface and said storage device, said one or more processors automatically adds first additional code to first existing code, said first existing code creates a software entity, said first additional code stores first data relevant to said first software entity, said first data is available when said software entity is created, said one or more processors automatically adds second additional code to second existing code, said second existing code uses said software entity, said second additional code accesses second data relevant to said software entity and correlates said second data with said first data after said second data is accessed to produce correlation data, said one or more processors reports said correlation data to an output device.

25. An apparatus according to claim 24, wherein:

said software entity is an object; and

said first existing code and said second existing code are object code.

26. An apparatus according to claim 24, wherein:

said step of adding second additional code includes adding code that traces said software entity and produces trace data, said second data includes said trace data; and

said step of adding second additional code further includes adding code that stores said trace data with said first data using said software entity to correlate said trace data with said first data.

27. An apparatus according to claim 24, wherein:

said software entity is an object;

said step of adding first additional code includes adding code that stores said object with said first data; and

said step of adding second additional code includes adding code that uses said object to correlate said second data with said first data.

28. An apparatus according to claim 24, wherein:

said first data indicates an SQL statement;

said software entity is an object that pertains to said SQL statement;

said first existing code receives said SQL statement;

said second existing code causes the execution of said SQL statement;

said step of adding first additional code includes adding code that stores said SQL statement and said object; and

said step of adding second additional code includes adding code that traces a use of said object thereby producing trace data and stores said trace data with said first data.

29. A method for adding functionality in order to access information, comprising:

accessing existing code that creates a software entity and uses said software entity; and

after said accessing, automatically modifying said existing code, said modifying includes adding first additional code and second additional code to said existing code, said first additional code stores first data relevant to said software entity at time of creation of said software entity, said second additional code accesses second data relevant to said software entity and correlates said second data with said first data.

30. A method according to claim 29, wherein:

said software entity is an object;

said object pertains to an SQL statement; and

said first data indicates said SQL statement.

31. A method according to claim 30, wherein:

said modified existing code causes a performance of said SQL statement; and

said second data includes trace data that indicates a time for performing said SQL statement.

32. A method for adding functionality in order to access information, comprising:

accessing existing code that creates a software entity and uses said software entity; and

after said accessing, automatically adding first additional code and second additional code to said existing code, said first additional code stores first data relevant to said software entity at time of creation of said software entity, said second additional code accesses second data relevant to said software entity and correlates said second data with said first data.

33. A method according to claim 32, wherein:

said software entity is an object;

said first data represents an SQL statement;

said object pertains to said SQL statement;

said existing code receives and executes said SQL statement; and

said second data is trace data that includes information about how long said SQL statement executes.