Proxy Object

• US 20100235459A1
• Filed: 05/26/2010
• Published: 09/16/2010
• Est. Priority Date: 10/28/2004
• Status: Active Grant

• Current Assignee: Callahan Cellular LLC (Intellectual Ventures LLC)
• Original Assignee: Curen Software Enterprises LLC (Intellectual Ventures LLC)
• Inventors: Wheeler, Thomas T.
• Granted Patent: US 8,307,380 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449

Abstract

Embodiments are discussed for methods, systems, and computer readable media for creating a proxy object, comprising calling a second functionality in a proxy class, creating a proxy object by the second functionality, calling a third functionality by the second functionality, calling a fourth functionality by the third functionality, creating a reference object by the fourth functionality, returning the reference object to the third functionality, associating the reference object to the proxy object by the third functionality, and returning the associated proxy object by the second functionality to a first functionality.

Claims

1. A device-implemented method comprising:

utilizing a lookup address to access a directory;

retrieving business object information from the directory, the business object information including a business object address and a business object ID; and

communicating the business object information effective to enable construction of a proxy object that is configured to enable access to a business object and one or more invokable functionalities of the business object.

2. The device-implemented method of claim 1, wherein utilizing the lookup address to access the directory comprises using one of a local lookup uniform resource locator (URL) or a remote lookup URL.

3. The device-implemented method of claim 1, wherein utilizing the lookup address to access the directory comprises utilizing a scheme-specific portion of the lookup address to determine a messaging protocol.

4. The device-implemented method of claim 1, wherein utilizing the lookup address to access the directory comprises determining a messaging protocol to be used in communicating the business object information.

5. The device-implemented method of claim 1, wherein communicating the business object information comprises communicating the business object information from a first resource to a second resource that is remote from the first resource and that hosts the business object.

6. The device-implemented method of claim 1, further comprising:

receiving a request from a resource to invoke the one or more functionalities of the business object, the request including the business object ID and one or more arguments to be passed to the business object;

causing one or more of the functionalities of the business object to be performed using the one or more arguments;

communicating a response for receipt by the resource based on the performing of the one or more functionalities by the business object.

7. A device-implemented method comprising:

associating an address with an adapter for a business object at a first resource;

performing a lookup using the address to determine a proxy object for the adapter; and

communicating the proxy object for receipt at a second resource that is remote from the first resource, the proxy object being configured to enable the second resource to invoke one or more functionalities of the business object via the adapter.

8. The device-implemented method of claim 7, wherein associating the address with the adapter comprises associating a uniform resource locator (URL) and an ID for the business object with the address.

9. The device-implemented method of claim 7, wherein performing the lookup using the address to determine the proxy object for the adapter comprises associating a proxy method with the proxy object.

10. The device-implemented method of claim 7, wherein performing the lookup using the address to determine the proxy object for the adapter comprises determining a messaging protocol associated with the address.

11. The device-implemented method of claim 7, wherein performing the lookup using the address to determine the proxy object for the adapter comprises:

determining a URL associated with the address; and

inspecting the URL to determine a directory location associated with the proxy object.

12. The device-implemented method of claim 7, further comprising:

receiving a request to invoke a method associated with the business object;

processing the request to determine one or more arguments included with the request; and

passing the one or more arguments to the business object for processing.

13. A device-implemented method comprising:

causing communication of a request for a proxy object to a resource from which the proxy object can be obtained, the request including a uniform resource locator (URL) that identifies the proxy object;

responsive to causing communication, receiving the proxy object from the resource, the proxy object including at least one proxy method; and

invoking, via the proxy method, one or more functionalities of a business object.

14. The device-implemented method of claim 13, wherein causing communication of the request for the proxy object comprises causing communication of the request to the resource from a different resource, and wherein the business object is located at the resource and the resource is remote from the different resource.

15. The device-implemented method of claim 13, wherein causing communication of the request for the proxy object comprises communicating, as part of the URL, a messaging protocol to be used in returning the proxy object.

16. The device-implemented method of claim 13, wherein causing communication of the request for the proxy object comprises communicating, as part of the URL, a directory location for the proxy object.

17. The device-implemented method of claim 13, wherein causing communication of the request for the proxy object comprises calling a lookup method to acquire the proxy object.

18. The device-implemented method of claim 13, wherein invoking via the proxy method the one or more functionalities of the business object comprises communicating one or more arguments for receipt by the business object.

19. The device-implemented method of claim 13, wherein invoking via the proxy method the one or more functionalities of the business object comprises invoking a business method of the business object.

20. The device-implemented method of claim 13, further comprising:

causing communication of one or more arguments to the resource for processing by the business object; and

receiving at the different resource one or more values that result from the processing of the one or more arguments.