Concept Of Interface

Hi,
As per my understanding interfaces have only method signatures but not code for the methods.And the class implementing the interface needs to define the method.
Now my doubt is, we use registerOutParameter() method of interface CallableStatement directly.
How's this possible.
Thanks.

Hi,
First: Your code isn't correct regarding several points.
See inline:
Hi,
Take This is code for example
DB = new DBConnectionWrapper();What is this DBConnectionWrapper()? I don't know such an element of the standard APIs.
conn = DB.getConnection();
CallableStatement conn = DB.getConnection();A callable statement is not returned by getConnection(), but by prepareCall() as you are doing it below.
strPrepareString = DB.getStrPrepareString("PRC",66);
csmt = conn.prepareCall(strPrepareString);
Here we have made an object of interface
CallableStatement, then we are calling prepare call
method.
But as per my understanding the interface contains
only method signature and no code.Then how this
works.Coming to your question: It's quite simple - prepareCall() returns a complete object which implements (!) the Interface CallableStatement.
All things we are executing is always in objects of some classes, but we are accessing the objects via an interface.
From this point of view the class definition of a class not implementing a specific interface is an interface itsself.
(I left out static methods in this description, because static methods are breaking the the concept of Interface based programming.)
Hope this helps
Martin

Similar Messages

Authorization Concepts on Interface Level

Hello!
I have a scenario, where a couple of Services are published as SOAP Web Service throug SAP XI 3.0 which are defined by an Outbound Interface published as a WebService (via SOAP Adapter).
From reading the documentation i figured out it is possible to define a technical user in the User Management for an external system to authenticate and use this Web Services.
Is there any possibility to ensure one technical user can only acess a defined count of interfaces.
This could be important if some services (= outbound interfaces) should not be accesible for other technical users.
I didn't find any way how to do this in the documentation
Thanks!
Greets
Sebastian

Hi
As per SP13 Release Document it is possible to restrict access of certain users, for this go thru this link
http://help.sap.com/saphelp_nw04/helpdata/en/ff/42ad423442c611e10000000a1550b0/content.htm
Hope it helps.
Regards
Arpit Seth

When to use abstract classes instead of interfaces with extension methods in C#?

"Abstract class" and "interface" are similar concepts, with interface being the more abstract of the two. One differentiating factor is that abstract classes provide method implementations for derived classes when needed. In C#, however,
this differentiating factor has been reduced by the recent introduction of extension methods, which enable implementations to be provided for interface methods. Another differentiating factor is that a class can inherit only one abstract class (i.e., there
is no multiple inheritance), but it can implement multiple interfaces. This makes interfaces less restrictive and more flexible. So, in C#, when should we use abstract classes
instead of interfaces with extension methods?
A notable example of the interface + extension method model is LINQ, where query functionality is provided for any type that implements IEnumerable via
a multitude of extension methods.

Hi
Well I believe Interfaces have more uses in software design. You could decouple your component implementing against interfaces so that
you have more flexibility on changing your code with less risk. Like Inversion of Control patterns where you can use interfaces and then when you decide you can change the concrete implementation that you want to use. Or other uses for interfaces is you could
use Interceptors using interfaces (Unity
Interceptor) to do different things where not all of these is feasible or at least as straightforward using abstract classes.
Regards
Aram

Bank Interface in XML format

Hi All,
I need to send a payment file to file bank in MT100 XML format and in return i will get a confirmation message from the bank in the XML format. Can any one pls tell me how to configure this using Idoc's.
I am new to Idoc's and have no idea in configuring the Idoc. Are are any standard Idoc for this and how to develop and configure this.
Thanks,
Raju

Hi Raju,
Hearty Welcome to SCN.
My suggestion is first make sure you understand the concept of interfaces completely and then you start working otherwise there might be lot of issues. And you are saying new to IDOCs do follow my suggestion.
Check the following links may help you
Re: How can i transfer IDOC to XML format?
R/3 IDoc --> Create a File containing IDoc XML
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Cheers!!
Balu

What are interfaces

sir,
plz explain me about interfaces, whare are they where r used in ABAP and explain with example.

Hi Sandeep,
Interfaces
Classes, their instances (objects), and access to objects using reference variables form the basics of ABAP Objects. These means already allow you to model typical business applications, such as customers, orders, order items, invoices, and so on, using objects, and to implement solutions using ABAP Objects.
However, it is often necessary for similar classes to provide similar functions that are coded differently in each class but which should provide a uniform point of contact for the user. For example, you might have two similar classes, savings account and check account, both of which have a method for calculating end of year charges. The interfaces and names of the methods are the same, but the actual implementation is different. The user of the classes and their instances must also be able to run the end of year method for all accounts, without having to worry about the actual type of each individual account.
ABAP Objects makes this possible by using interfaces. Interfaces are independent structures that you can implement in a class to extend the scope of that class. The class-specific scope of a class is defined by its components and visibility sections. The public components of a class define its public scope, since all of its attributes and method parameters can be addressed by all users.
Interfaces extend the scope of a class by adding their own components to its public section. This allows users to address different classes across different inheritance trees via a universal point of contact. Interface references allow users to address and use different classes in exactly the same way. Interfaces, along with inheritance, provide one of the pillars of polymorphism, since they allow a single method within an interface to behave differently in different classes.
Defining Interfaces
Like classes, you can define interfaces either globally in the Repository or locally in an ABAP program. For information about how to define local interfaces, refer to the Class Builder section of the ABAP Workbench Tools documentation. The definition of a local interface intf is enclosed in the statements:
INTERFACE intf.
ENDINTERFACE.
The definition contains the declaration for all components (attributes, methods, events) of the interface. You can define the same components in an interface as in a class. The components of interfaces do not have to be assigned individually to a visibility section, since they automatically belong to the public section of the class in which the interface is implemented. Interfaces do not have an implementation part, since their methods are implemented in the class that implements the interface.
Implementing Interfaces
Unlike classes, interfaces do not have instances. Instead, interfaces are implemented by classes. To implement an interface in a class, use the statement
INTERFACES intf.
in the declaration part of the class. This statement may only appear in the public section of the class.
When you implement an interface in a class, the components of the interface are added to the other components in the public section. A component icomp of an interface intf can be addressed as though it were a member of the class under the name intf~icomp.
The class must implement the methods of all interfaces implemented in it. The implementation part of the class must contain a method implementation for each interface method imeth:
METHOD intf~imeth.
ENDMETHOD.
Interfaces can be implemented by different classes. Each of these classes is extended by the same set of components. The methods of the interface can be implemented differently in each class. However, each class should keep the semantics of the interface. A method implementation should provide precisely that functionality which is required by the interface.
Interfaces allow you to use different classes in a uniform way using interface references (polymorphism). For example, interfaces that are implemented in different classes extend the public scope of each class by the same set of components. If a class does not have any class-specific public components, the interfaces define the entire public face of the class.
Interface References
Reference variables allow you to access objects (refer to Working with Objects). Instead of creating reference variables with reference to a class, you can also define them with reference to an interface. This kind of reference variable can contain references to objects of classes that implement the corresponding interface.
To define an interface reference, use the addition TYPE REF TO intf in the TYPES or DATA statement. intf must be an interface that has been declared to the program before the actual reference declaration occurs. A reference variable with the type interface reference is called an interface reference variable, or interface reference for short.
An interface reference iref allows a user to use the form iref->icomp to address all visible interface components icomp of the object to which the object reference is pointing. It allows the user to access all of the components of the object that were added to its definition by the implementation of the interface.
Addressing Objects Using Interface References
If a class class implements an interface intf, you can use the following assignment between the class reference variable crefand an interface reference irefto make the interface reference in irefpoint to the same object as the class reference in cref:
iref = cref
If a class class implements an interface intf, you do not need to create a class reference variable cref with reference to the class first in order to create an object of the class class. Instead, you can use the TYPE addition in the CREATE OBJECT statement to create an instance of the class with an interface reference variable.
CREATE OBJECT iref TYPE class.
This creates an instance of the class classto which the reference in irefpoints.
If the interface intf contains an instance attribute attr and an instance method meth, you can address the interface components as follows:
Using the class reference variable cref:
·        To access an attribute attr: cref->intf~attr
·        To call a method meth: CALL METHOD cref->intf~meth
Using the interface reference variable iref:
·        To access an attribute attr: iref->attr
·        To call a method meth: CALL METHOD iref->meth
As far as the static components of interfaces are concerned, you can only use the interface name to access constants:
To access a constant const: intf=>const
For all other static components of an interface, you can only use object references or the class class that implements the interface:
To access a static attribute attr: class=>intf~attr
To call a static method meth: CALL METHOD class=>intf~meth
Nesting Interfaces
You can nest interfaces. An interface can contain one or more interfaces as its components, and these interfaces can, in turn, themselves contain interfaces. An interface which contains another interface is called a nested or a compound interface. An interface which is contained in another interface is referred to as the component interface. An interface which does not contain any nested interfaces is called an elementary interface.
All interface components of a nested interface are on the same level. If a nested interface i3 contains the interface components i2 which are themselves nested and contain the interface components i1, then the components i1 become interface components of i3. Generally, a nested interface contains each interface component exactly once. Even if a component interface is used a second time as the component of another component interface, it still exists only once.
If you want to nest interfaces, use the statement INTERFACES in an interface definition:
INTERFACE i3.
INTERFACES: i1, i2 ...
ENDINTERFACE.
Here, the interface i3 consists of its components as well as of the interfaces i1 and i2. The components of the component interfaces are not directly visible in the nested interface. In the above definition of i3, expressions like i1comp or i2compcannot be used, with the exception of the ALIAS statement.
There are several ways how you can use the components of component interfaces:
Using Alias Names
You can use the ALIAS statement in interface definitions to assign alias names to the components of component interfaces. This makes these components visible in the interface definition.
INTERFACE i2.
INTERFACES i1.
ALIASES alias21 FOR i1~comp1.
ENDINTERFACE.
INTERFACE i3.
INTERFACES i2.
ALIASES alias31 FOR i2~alias21.
ALIASES alias32 FOR i2~comp2.
ENDINTERFACE.
Assigning Interface References
You can assign interface references typed with reference to one of the component interfaces to interface references typed with reference to a nested interface. You can then use the interface references typed with reference to a component interface to address the components of the component interfaces.
INTERFACE i2.
INTERFACES i1.
ENDINTERFACE.
INTERFACE i3.
    INTERFACES i2.
ENDINTERFACE.
DATA: iref1 TYPE REF TO i1,
      iref2 TYPE REF TO i2,
      iref3 TYPE REF TO i3.
iref2 = iref3.
iref1 = iref2.
... iref1->comp1 ...
... iref2->comp2 ...
The following expressions are not possible:
... iref2->i1~comp1 ...
... iref3->i2~comp2 ...
Implementing Nested Interfaces in Classes
When you implement a nested interface in a class, then all interfaces contained are implemented in the class at the same level, whatever their nesting depth. The class must then implement all methods.
INTERFACE i2.
INTERFACES i1.
ENDINTERFACE.
INTERFACE i3.
INTERFACES i2.
ENDINTERFACE.
CLASS class DEFINITION.
INTERFACES i3.
ENDCLASS.
CLASS class IMPLEMENTATION.
METHOD i1~meth.
ENDMETHOD.
ENDCLASS.
Use:
DATA: cref TYPE REF TO class.
... cref->i1~comp1 ...
... cref->i2~comp2 ...
... cref->i3~comp3 ...
Nested expressions such as cref->i3i2comp2 or cref->i3i2i3~comp3 are not possible. The nesting hierarchy is only important when you assign interface references to each other. You can assign class references for classes which implement a nested interface to all interface references typed with reference to an interface component contained. The interface references only know the components of their interface within the class.
Interfaces and Inheritance
As far as interfaces are concerned, polymorphism is based on the fact that each class implementing an interface can implement its methods in a different way. To the outside, however, all interface components look the same. As a result, interface references can point to objects of all classes which implement the associated interface.
The concepts of interfaces and of inheritance are completely orthogonal. In the classes of an inheritance tree you can implement as many interfaces as required. However, you must pay attention to the fact that each interface can be implemented only once per inheritance tree. This ensures that each interface component has a unique name intf~icomp across the entire inheritance tree and is contained in all subclasses starting with the class that implements the interface. Interface references that can point to a class of an inheritance tree can also point to all subclasses. Once they have been implemented, interface methods are fully-fledged components of a class and can be redefined in subclasses. However, you cannot declare interface methods as abstract or final in the definition of the interface.
Reward points, if useful.
Regards,
Nitin.

Interface WD ABAP.

Dear Experts.
I am new with WD ABAP. In this moment I am reading the documentation "NET310 ABAP Web Dynpro".
I never have understand the concept of Interface in Object-Oriented Programming (OOP).
Please anyone can help me to understandad this concept?
Regards

Hi Carmen,
it is a huge subject itself to explain and i am afraid that it is not a right forum to discus.
To understand interface, you need to understand what is Polymorphism.
Polymorphism in a nutshell is that the objects receives same message definition but behaves in a different manner.
example calculate_fuel method in different classes has the same importing parameter and returning parameters but the calculations could be implemented differently in different classes.
Interface has only definitions, you need to implement them. in this way interface concept enables to achieve Polymorphism.
ABAP Objects does not support multiple inheritance. Therefore you can only have a single super-class. However a class can implement multiple interfaces to have kind of multiple inheritance.

Interfaces IDOC's

Hi Sap friends,
Could somebody help me understand the concept of interfaces specifically using thru Idocs. Say for example i want to use delvry03 idoc to transmit some info for 3rd party shipment software. Please explain with an sceanrio as how the Idoc and segments are identified to suit 3rd party. also, how idoc is initiated automatically to do the intended job, that is whether on document save or if any other config is required.
Thanks in advance!
Ranga Reddy

Hi Ranga reddy,
Please go through this link it will help you about IDOC process,
http://help.sap.com/saphelp_47x200/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
I hope it will help you,
Regards,
Murali.

Component interface question

Is the concept "component interface" related to the business methods of the bean or to the callback methods (that inform the bean about state events) of SessionBean/EntityBean interface?
if "component interface" related to the callBack methods then how the interface with the business methods is called (in 3.0 i know it's "business interface" but what about 2.1)?
thanks in advanced

The component interface refers to a particular client view exposed from the bean. It contains the business methods available to the callers.
The callback methods are a separate contract between the bean class and the container. In EJB 2.x, they are expressed via strongly-typed javax.ejb interfaces that the bean class was required to implement.
In EJB 3.0, all callbacks are optional and the bean class uses annotations such as @PostConstruct to annotate the methods it wants to be called back. These methods are typically not exposed through the client (component interface) view.
--ken

Interface and Inheritance

Hi,
I am basically looking for why these 2 different concepts are there in Java. Interface concept is possible to achieve using inheritance as well. So why we need 2 different concepts here?? Can anybody please throw light giving some scenarios???
Jounty

Hi,
Another way to look at this is,
Concept of Interface is common behaviors (not common data), thus avoids the complexities with multiple inheritance
An abstract class with out any state definition can as well achieve the concept of an Interface.
However there are certain differences between these two approaches,
An interface by concept, does not have its own state, only declares behaviors,
This makes an interface be a gateway to any kind of objects with entirely different state and different behavior, but common in certain behavior.
The same true interface concept cannot be achieved with classes, as an abstract class is not restricted to define its own state.
There comes the requirement for either a new concept in abstract classes to achieve this or the separate terminology Interface.
There is another supporting reason for going to Interface terminology, since java does not support multiple Inheritance, an object to be comply with multiple interfaces that are defined by abstract classes is not possible , it will then violate the rule

Why name "Interface"?

hi all,
can anybody tell me why name "interface" in java. I was asked this question in an interview.. pls help..
thanx

Here is a link to the java tutorial where the word
interface is explained in non-computer terms. It
gives you a good idea why the word interface was
chosen.
http://java.sun.com/docs/books/tutorial/java/concepts/interface.html
And if u want the difference in concept of Interface in Java and other progarmmining languages more detailed look @
http://en.wikipedia.org/wiki/Interface_%28computer_science%29
http://en.wikipedia.org/wiki/Interface_%28Java%29

Interfaces that extend other interfaces

I am trying to get a handle on the concept of interfaces extending other interfaces, and I just want to bounce my thoughts off the board and see where it goes. The Sun tutorial doesn't provide a lot of detail that I can see.
Suppose we have interface A which has 3 methods (signatures), and interface B which extends interface A and adds two methods of its own. Suppose also we have a class C which can implement A or B or both.
1. Having B extend A provides a heirarchy of types, with A above B
2. If class C implements interface B, then the extends relationship B has with A forces C to provide implementations for the methods of A as well as B. On this point I am not certain.
3. Having B extend A allows us to essentially add methods to the interface defined by A without forcing those changes on owners of the classes that already extend A.
Sound OK? Anywone have anything to add?
Edited by: Fguy on Aug 27, 2009 7:07 PM

jverd wrote:
Fguy wrote:
>
3. Having B extend A allows us to essentially add methods to the interface defined by A without forcing those >>changes on owners of the classes that already extend A.Huh? Not sure what you're saying, here, but extending A means we're defining a type that's a specialized or >enhanced type of A. Implementors can implement A if all they need is a run of the mill A, or B if they need the >specialized/enhanced version.Thanks.
What I meant was that class C implements interface A, and interface B is not a part of the picture yet. Then, by creating a new interface B that extends A, rather than just adding the new methods to A, then you are not forced to add new method implementation to class C right away.That would be one situation in which one might do that. Of course, it's also not uncommon to design the two distinct interfaces from the start
Ok I'll pick up on that, the situation that led to this thread was me trying to understand why the List interface extends the Collection interface, and why the ArrayList class implements both interfaces. And I eventually decided that designing kind of an arrangement makes sense from the start as you say, because there are probably reasons why you'd want that type heirarchy, or higher level abstraction. with different levels of functionality in the respective implementations. I can't really think of any other reason.

How can we acess the data of one component into othr compnent in webdynpro?

How can we acess the data of one component into other component in webdynpro....
I need an Field input from one webdynpro component(comp1) which is away from the line of process to the other component(comp2) we need that data........I mean i need the field info of comp1 where we doesn't navigate through the Comp1 in the portal & directly access the component comp2.........kindly share your ideas.....and possible ways .........
any doughts do post.....
thanks in advance!

Hi Reddy,
You can do it in multiple ways. One way would be to try transfer the parameters through URL & the other would be to work with the concept of interface nodes. Please try go through these 2 threads ( [Thread 1|Call view of another WDA Component and pass the value to it; & [Thread 2|navigation from one program to another; )where I have explained about working with Interface node in detail. You can refer to this [thread |receving parameters between two standard webdynpro applications;to see as to how you can do the same via parameters in URL. Hope it would help resolve your problem.
Regards,
Uday

Student needs help with database planning

Preliminary Plan
I work at the headquarters of a small company of 8 offices and 26 employees. I am the central database system. Right now, information is only accessible through me, by me, from me, and to me via fax, phone, mail, or email. I have several spreadsheets with different information resulting from personal information, cell phone information, laptop information, government vehicle information, contract information, and training information.
I want to develop a database that will automatically keep track of this information as entered by the user. Whenever there is a change or update, the system will be able to automatically accept this information into the system. Information will come from each workstation in the office that only the managers and I can see. The managers will however only have access to their individual employee information, but I will have access to ALL the employee information. All information created, provided, and maintained between me and the managers will be conducted through RDBMS. Triggers will be used so that information can be updated or inserted through SQL. LAN-to-LAN connections are already in place so that information on the network can be accessible. Preliminary plan is as follows:
WEEK 2: January 15-21, 2007
Develop preliminary plan for two sentence concept of BPS
WEEK 3: January 22-28, 2007
Finalization of preliminary plan
Creating the database i.e., connecting, granting privileges, adding systems
Designing and creating tables, databases which are already in spreadsheet format
WEEK 4: January 29-February 4, 2007
Designing and creating tables, databases which are already in spreadsheet format
Installing, configuring, and securing the database;
WEEK 5: February 5-11, 2007
Develop triggers using SQL; test database
WEEK 6: February 12-18, 2007
Design, develop, and test user interface application
WEEK 7: February 19-25, 2007
Test application again. Test database again. Test project application and database together.
WEEK 8: February 26-March 4, 2007
Finalize project details to incorporate into a PowerPoint presentation for submission.
WEEK 9: March 5-11, 2007
Demonstrate and present project. Evaluations due.

My major is information system. I want to be able to
access information from all 8 stations where the user
inputs the information, but only have access to their
employees and I will have access to all 26 employees.
I being the central database system.Still quite vague, if you ask me. If it's just an entry formular with user authentification, your time schedule may work. Installing XE and developing with APEX could just be the right tool for this job, but without any further information (data structures, authentification concept, user interface) it will remain pure speculation from my side. Why not ask your teacher if he/she thinks your plan is reasonable?
C.

Issue in Extension of ARTMAS05 IDoc

Hi Experts,
We need to extend the standard IDoc ARTMAS05 to add 70 user specific fields.
when i'm doing the extension in WE30, i'm getting the below error.
" Action is not possible for generated IDoctypes"
in SAP Note 913901 , it says that we can't extend the genarated IDoc types.
" The extension concept for interfaces in Transactions BDBG and BDFG does not
work with extensions for the IDoc types created using Transaction WE30.
When you create extensions in Transaction WE30, the system does not check
whether the IDoc type for which you are creating the extension has been
generated.
You cannot create an extension for a generated IDoc type."
Please suggest what is the alternative way to extend.
thanks in advance
Rahul
Edited by: Rahul Gautam on Feb 18, 2010 12:01 PM
Edited by: Rahul Gautam on Feb 19, 2010 3:59 AM

Hi Anup,
Thanks for replying. But as per my requirement i have to extend the standard Idoc type ARTMAS05. And as per my understanding BAPI_IDOC_INPUT1 will works and it will trigger another inbound FM inside it. And my requirement will not allowing me to copy the standard IDoc to ZIDoc
Please reply is there any other option to Extension ARTMAS05.
Thanks
Rahul

Urgent help MPLS needed

guys we have 4 sites A,B,C,D all are connected via dark fiber (ethernet).
connection is
A --->C
C---> D
D--->B
B--->A
now A is also connected with ---D
A---->D
ISIS is the routing protocol
all routers have loopbacks as well
now all physical interfaces should be in area 43.0010 and shd run level 1
now site BC loopback interfaces should be in same area as above and should run level 1 as well.
site A and D loopback should be in different area 47.2010 and should run level 2
the problem is its poretty straight forward but i am nnot allowed to use seperate instance of ISIS i m going nuts is it possible if yes how....thanks for your help guys.....

Hi,
It looks to me as there might be a misunderstanding of the area concept or NSAP address in ISIS. ISIS has -no- concept of interfaces being in a specific area. This is an OSPF concept not used in ISIS at all.
In ISIS a router (not an interface) gets an address and a whole router will be in an area. Note: an ISIS router can have more than one ISIS NSAP address and thus can be in more than one area. But this feature was mainly introduced to allow for migration scenarios. Again, this feature does not mean an interface coul be assigned to an area in ISIS.
The requirements of interfaces being in an ISIS area you describe cannot be fulfilled with ISIS. Please calm down and do not go nuts over a problem impossible to solve :-)
This brings me to a question: who came up with the impossible requirements and why?
With 4 routers involved I would assume having a single ISIS area would be preferable unless there are hidden requirements/issues to be solved.
Hope this helps! Please use the rating system.
Regards,
Martin

Concept Of Interface

Similar Messages

Maybe you are looking for