System and method for delegating a dependent business object

Abstract

Disclosed is a system and a method for delegating the object requests to a service provider class. For each request received at an object, the node identity of a node of the object is retrieved from the request. Based on this retrieved node identity, an instance of an object from the service provider class factory is fetched. If the retrieved node identity is regarding a dependent object then the request is delegated to a dependent business object service provider class. An instance of a service provider class of a node is fetched from a service provider class factory based on the node identity. The request is processed at the dependent business object by accessing a method in the service provider class of the object.

Description

FIELD OF THE INVENTION[0001]Embodiments of the invention generally relate to the field of data processing system, more particularly to a way of providing centralized access to a business object of an enterprise software application.BACKGROUND OF THE INVENTION[0002]A business object is a representation of a type of uniquely identifiable business entities described by a structural model, an internal process model, and one or more service interfaces. A business entity operates on the business objects. Examples of such business objects are “Sales Order” or “Purchase Order”. The development for the business objects is subdivided in the three phases; a design phase, a modeling phase and an implementation phase. During the design phase, the business objects are identified and named. During the modeling phase, a model editor is used to determine the structure of the business object. During the implementation phase, the service provider class uses generated proxy elements for inter business ...

AI Technical Summary

Problems solved by technology

Maintaining a single service provider class for all the business object nodes is typically tedious and not efficient.

It would be very time consuming for the developers of the service provider class to debug a problem in the service provider class with so many lines of code and if the problem is not debugged properly, the chances of a programming error being left out in the code may increase.

Also, having a single service provider class that performs different operations on different nodes in different ways may not be a good object oriented design.

At implementation time, a dependent object association results in an extensive and error-prone implementation of the business object service provider class.

The known method of LCP delegation is expensive and error-prone and hence this extensive LCP delegation work must be implemented in a generic way.

Images