cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to understand Component Interface Definition

Former Member
0 Kudos

Hi All,

I am working with the component usage. In component we have Component Interface ,then why we go for Component Interface Definition instead of using the component interface of a component.Can anybody explain me the advantage of Component Interface Definition.

Thanks in Advance.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

[http://help.sap.com/saphelp_nw70ehp1/helpdata/en/6c/bd896e6661f04b9c8b2916aed3aadc/frameset.htm]

Former Member
0 Kudos

Component Interface Definition is analogous to a Interface in Se24. If you know what a SE24 Interface means, its just a skeleton with method names . As compared to a SE24 class which has logic inside the methods..

Similarly a component interface definition is a skeleton of a Component Interface. It has Interface Controller Methods (just the method name.....no logic inside) and Interface Views.

Now lests say you have 3 componenents which need the similar kind of functionality for a particular Controller method but the actual logic of functionality is different. In that case, instead of creating the same method 3 times each in individual component, you create a COmponent Interface and put the method in it.

Each of the 3 component then implements this Component Interface and hance gets the method. Now the actual logic in the method can be coded independently for each component.

Similar to Se24 Interface, a Component Interface Definition can take the Component usage instance of the Component implementing it. SO now, we can create dynamically component usage instance of any component that is implementing the component interface definitiaon.