Client interfaces for packages

• US 20060248544A1
• Filed: 04/29/2005
• Published: 11/02/2006
• Est. Priority Date: 04/29/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Decker, Thomas, Schmitt, Andreas Simon, Frick, Markus, Runte, Martin, Remmel, Juergen, Schneider, Michael, Kluger, Gerd, Benjes, Friederike, Prestel, Helmut, Blumenthal, Andreas, Koch, Ulrich, Faust, Rasmus
• Granted Patent: US 7,669,181 B2
• Time in Patent Office: Days
• US Class Current: 719/328
• CPC Class Codes: G06F 2209/462 Lookup
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

A method and system for employing client interfaces for packages. In one embodiment, an access object associated with a service provided by a first package is located, where the service is seeking to access content residing at a second package. A client interface is then created at the second package using the access object. The client interface is used to provide access to the content by exposing the content to the service via the client interface.

Claims

1. A method comprising:

locating an access object associated with a service provided by a first package, the service to seek an access to content at a second package;

creating a client interface at the second package using the access object; and

providing the access to the content by exposing the content to the service using the client interface.

2. The method of claim 1, further comprising:

assigning the access object to the service; and

exposing the access object using a package interface at the first package.

3. The method of claim 1, wherein the first package comprises a server package including a service package.

4. The method of claim 2, wherein the second package comprises a client package.

5. The method of claim 1, further comprising determining whether the second package includes one or more subpackages, each subpackage having subpackage content, wherein each of the one or more subpackages is capable of granting access permissions declared in the client interface.

6. The method of claim 5, wherein each of the one or more subpackages to inherit a dependency control list of the second package, the second package being a superpackage of the one or more subpackages.

7. The method of claim 1, wherein the content comprises a plurality of objects, the plurality of objects including one or more of the following:

global variables, local classes, structure types, function modules, dynpros, and types from other packages.

8. A system comprising:

a server package having a service package; and

a client package in communication with the service package, the client package to;

locate an access object associated with a service provided by the service package, the service to seek an access to content at the client package;

create a client interface at the client package using the access object; and

provide the access to the content by exposing the content to the service using the client interface.

9. The system of claim 8, wherein the service package to:

assign the access object to the service or to a package; and

expose the access object using a package interface at the service package or using a package interface at the package.

10. The system of claim 8, wherein the client package is further to determine whether the second package includes one or more subpackages, each subpackage having subpackage content, wherein each of the one or more subpackages is capable of granting access permissions declared in the client interface.

11. The system of claim 10, wherein each of the one or more subpackages is to inherit a dependency control list of the client package, the client package being a superpackage of the one or more subpackages.

12. The system of claim 8, wherein the content comprises a plurality of objects, the plurality of objects including one or more of the following:

global variables, local classes, structure types, function modules, dynpros, and types from other packages.

13. A machine-readable medium having stored thereon data representing sets of instructions which, when executed by a machine, cause the machine to:

locate an access object associated with a service provided by a first package, the service to seek an access to content at a second package;

create a client interface at the second package using the access object; and

provide the access to the content by exposing the content to the service using the client interface.

14. The machine-readable medium of claim 13, wherein the sets of instructions which, when executed by the machine, cause the machine to:

assign the access object to the service; and

expose the access object using a package interface at the first package.

15. The machine-readable medium of claim 13, wherein the first package comprises a server package including a service package.

16. The machine-readable medium of claim 14, wherein the second package comprises a client package.

17. The machine-readable medium of claim 13, wherein the sets of instructions which, when executed by the machine, cause the machine to determine whether the second package includes one or more subpackages, each subpackage having subpackage content, wherein each of the one or more subpackages is capable of granting access permissions declared in the client interface.

18. The machine-readable medium of claim 17, wherein each of the one or more subpackages to inherit a dependency control list of the second package, the second package being a superpackage of the one or more subpackages.

19. The machine-readable medium of claim 13, wherein the content comprises a plurality of objects, the plurality of objects including one or more of the following:

global variables, local classes, structure types, function modules, dynpros, and types from other packages.