About interface and Inheritance

First I start a project called Person which contain a person's name, SIN
number and year of birth
import java.io.*;
public class Person implements Create{
String name, sin;
int year;
public void Person(String inName, String inSin, int inYear){
name = inName;
sin = inSin;
year = inYear;
public void setName(String inName){
name = inName;
public void setSin(String inSin){
sin = inSin;
public void setYear(int inYear){
year = inYear;
public String getName(){
return name;
public String getSin(){
return sin;
public int getYear(){
return year;
public String toString(){
return getClass().getName() + name + " " + sin + " " + year;
then I create a class name student
public class Student extends Person{
String major;
double gpa;
public void student(String inMajor, double inGpa){
major = inMajor;
gpa = inGpa;
public void setMajor(String inMajor){
major = inMajor;
public void setGpa(double inGpa){
gpa = inGpa;
public String getMajor(){
return major;
public double getGpa(){
return gpa;
public String toString(){
return super.toString() + " " + major + " " + gpa;
3) Third I create a class name Instructor
import java.io.*;
public class Instructor extends Person{
double salary;
public void Instructor(double inSalary){
salary = inSalary;
public void setSalary(double inSalary){
salary = inSalary;
public double getSalary(){
return salary;
public String toString(){
return super.toString() + " " + salary;
last, I have to create an interface for the person's class...but the
complier dont let me put main or init into the interface class..what is my
problem..how can I fix it?....What am I miss so that I can use the person + student and person +
instructor class..I know I should ask too specificly because it's my
work...but I'm stuck in this area for a long time and the note I have it's
not clear enough...Thank you all...
import java.io.*;
public interface Create{

Thx for the help guys!!
1)..ok.. I have correct the void thingy...
2) ..I want to create and interface class called create which creates a person, a student and an instructor and write out their properties....
something like
Person
Name: Alan
Sin: 1212112
Year of bitrh: 1990
Student
Name: Linda
Sin:121212121
year of birth: 1988
Major: Com. Sci.
Gpa: 4.0
etc..
again...thx for all the help!!! ^^

Similar Messages

Need information about interfaces and namespaces in actionscript 3.0

Hi,
I need information about actionscript interfaces and
namespaces, I'm preparing for ACE for Flash CS3 and I need to learn
about this subjects and I can not find resources or simple examples
that make these subjects understandable.
Anybody can help me!
Thanks a lot.

Interfaces (cont.)
Perhaps the most useful feature of interfaces is that you not
only can define the data type but also method signature of the
class that implements this interface. In other words, interface can
define and enforce what methods class MUST implement. This is very
useful when classes are branching in packages and team of
developers works on a large application among others.
The general syntax for an Interface with method signatures is
written the following way:
package{
public interface InterfaceName {
// here we specify the methods that will heave to be
implemented
function method1 (var1:dataType,
var2:datType,…):returnType;
function method2 (var1:dataType,
var2:datType,…):returnType;
To the previous example:
package{
public interface IQualified {
function method1 ():void;
function method2 ():int;
Let’s write a class that implements it.
If I just write:
package{
public class ClassOne extends DisplayObject implements
IQualified {
public function ClassOne(){}
I will get a compilation error that states that I did not
implement required by the interface methods.
Now let’s implement only one method:
package{
public class ClassOne extends DisplayObject implements
IQualified {
private function method1():void{
return;
public function ClassOne(){}
I will get the error again because I implemented only one out
of two required methods.
Now let’s implement all of them:
package{
public class ClassOne extends DisplayObject implements
IQualified {
private function method1():void{
return;
private function method2():int{
return 4;
public function ClassOne(){}
Now everything works OK.
Now let’s screw with return datatypes. I attempt to
return String instead of void in method1 in ClassOne:
private function method1():String{
return “blah”;
I am getting an error again – Interface requires that
the method1 returns void.
Now let’s attempt to pass something into the method1:
private function method1(obj:MovieClip):void{
return;
Oops! An error again. Interface specified that the function
doesn’t accept any parameters.
Now rewrite the interface:
package{
public interface IQualified {
function method1 (obj:MovieClip):void;
function method2 ():int;
Now compiler stops complaining.
But, if we revert the class back to:
private function method1():void{
return;
compiler starts complaining again because we don’t pass
any parameters into the function.
The point is that interface is sort of a set of rules. In a
simple language, if it is stated:
public class ClassOne implements IQualified
it says: “I, class ClassOne, pledge to abide by all the
rules that IQualified has established and I will not function
correctly if I fail to do so in any way. (IMPORTANT) I can do more,
of course, but NOT LESS.”
Of course the class that implements an interface can have
more that number of methods the corresponding interface requires
– but never less.
MORE means that in addition to any number of functions it can
implement as many interfaces as it is desired.
For instance, I have three interfaces:
package{
public interface InterfaceOne {
function method1 ():void;
function method2 ():int;
package{
public interface InterfaceTwo {
function method3 ():void;
package{
public interface InterfaceThree{
function method4 ():void;
If our class promises to implement all three interface it
must have all four classes in it’s signature:
package{
public class ClassOne extends DisplayObject implements
InterfaceOne, InterfaceTwi, InterfaceThree{
private function method1():void{return;}
private function method2():int{return 4;}
private function method3():void{return;}
private function method4():void{return;}
public function ClassOne(){}
Hope it helps.

About classes and Inheritance

hi every one,
i want use class with object in data block and i want know how i can use inheritance with objects.
becouse i have interview in this two subjects, can any body support my.
thanks,,,,,,,

Hello,
Start Forms Builder, the press F1 to display the online help.
In the search tab, you can type "Class Property" or "Object Library" to find documentation on those topics:
About Property Classes A property class is a named object that contains a list of properties and their settings. Once you create a property class you can base other objects on it. An object based on a property class can inherit the setting of any property in the class that makes sense for that object. Property class inheritance is an instance of subclassing. Conceptually, you can consider a property class as a universal subclassing parent. There can be any number of properties in a property class, and the properties in a class can apply to different types of objects. For example, a property class might contain some properties that are common to all types of items, some that apply only to text items, and some that apply only to check boxes. When you base an object on a property class, you have complete control over which properties the object should inherit from the class, and which should be overridden locally. Property classes are separate objects, and, as such, can be copied between modules as needed. Perhaps more importantly, property classes can be subclassed in any number of modules.
or
Using the Object Library These topics contain information about using the Object Library in Oracle Forms: About the Object Library Removing an Object from the Object Library Creating a tab in the Object Library Deleting a Tab in the Object Library Saving an Object in the Object Library Opening an Object Library Module Displaying the Object Library Closing the Object Library Commenting Objects in the Object Library
Francois

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

About interface and class[Please read this]

I writing what I found out:
myinterface.java
interface myinterface
class A
A()
{System.out.println("A()
of interface");}
A.java
class A implements
myinterface
A(){System.out.println("A()
of A.java");}
public static void main
(String args[])
A a=new A();
//this calls A() of interface
//myinterface.java
//how come the output of
// this code is like this

how come this is possible?Well, it had to pick one or the other, since they
have the same symbol name. Why are you choosing to
make up goofy names that collide in the first place?
If you want to explicitly use one or the other, you
need to also choose a package name, and fully-qualify
the class name that you are trying to instantiate.For example:
package test;
interface MyInterface // renamed to follow standard naming convention
class A
    A() { System.out.println("A() of interface"); }
class A implements MyInterface
A() {System.out.println("A() of A.java"); }
public static void main(String args[])
    test.A a = new test.A(); // prints A() of A.java
    MyInterface.A a1 = new MyInterface.A(); // prints the other one
}

Question about casting and inheritances

Hi everyone!
I have a class dog which extends the class animal. Apart from that, there is a method called dogsFarm which returns a collection of animals (this method corresponds to another class, let's say farm). I can't touch the inside of that method since I just have the interface but I need a collection of dogs instead of a collection of animals. I tried to cast:
Collection<dog> dogs = (collection<dog>) dogsFarm();But it says that it cannot cast that. Is it any way to solve this without having to change the method?
Thanks

Strictly speaking if the method returns a Collection<Animal>, then no amount of casting will turn it into a Collection<Dog> while still being type safe.
The problem is that a Collection<Animal> could contain a Cat and if you cast it to a Collection<Dog>, it would contain an invalid value.
You could use raw types (i.e. simply "Collection") to "forget" the generic type information and provide new one after that, but that's just an ugly hack that provides no real check.
You could also use Collections.checkedCollection() to provide explicit checks.
You can combine those two techniques to get code that's still ugly, but does at least some error checking:
Collection rawFarm = dogFarm();
Collection<Dog> = Collections.checkedCollection(rawFarm, Dog.class);

Question about constructors and inheritance

Hello:
I have these classes:
public class TIntP4
    protected int val=0;
    public TIntP4(){val=0;}
    public TIntP4(int var)throws Exception
        if(var<0){throw new Exception("TIntP4: value must be positive: "+var);}
        val=var;
    public TIntP4(String var)throws Exception
        this(Integer.parseInt(var));
    public String toString()
        return val+"";
public class TVF extends TIntP4
}Using those clases, if I try to compile this:
TVF inst=new TVF("12");I get a compiler error: TVF(String) constructor can not be found. I wonder why constructor is not inherited, or if there is a way to avoid this problem without having to add the constructor to the subclass:
public class TVF extends TIntP4
     public TVF (String var)throws Exception
          super(var);
}Thanks!!

I guess that it would not help adding the default constructor:
public class TVF extends TIntP4
     public TVF ()
           super();
     public TVF (String var)throws Exception
          super(var);
}The point is that if I had in my super class 4 constructors, should I implement them all in the subclass although I just call the super class constructors?
Thanks again!

First Try with JE BDB - Indexes and Inheritance troubles... (FIXED)

Hi Mark,
Mark wrote:
Hi, I'm a newbie here trying some stuff on JE BDB. And now I'm having
I am happy to help you with this, but I'll have to ask you to re-post this question to the BDB JE forum, which is...
Sorry for the mistake. I know now that here is the place to post my doubts.
I'm really interested in JE BDB product. I think it is fantastic!
Regarding my first post about "Indexes and Inheritance" on JE BDB, I found out the fix for that and actually, it wasn't about "Indexes and Inheritance" but "*Inheritance and Sequence*" because I have my "@Persistent public abstract class AbstractEntity" with a "@PrimaryKey(sequence = "ID_SEQ") private Long id" property.
This class is extended by all my business classes (@Entity Employee and @Entity Department) so that my business classes have their PrimaryKey autoincremented by the sequence.
But, all my business classes have the same Sequence Name: "ID_SEQ" then, when I start running my JE BDB at first time, I start saving 3 new Department objects and the sequence for these department objects star with "#1" and finishes with #3.
Then I continue saving Employee objects (here was the problem) I thought that my next Sequence number could be #4 but actually it was #101 so when I tried to save my very first Employee, I set the property "managerId=null" since this employee is the Manager, then, when I tried to save my second Employee who is working under the first one (the manager employee), I got the following exception message:
TryingJEBDBApp DatabaseExcaption: com.sleepycat.je.ForeignConstraintException: (JE 4.0.71) Secondary persist#EntityStoreName#com.dmp.gamblit.persistence.BDB.store.eployee.Employee#*managerId*
foreign key not allowed: it is not present in the foreign database
persist#EntityStoreName#com.dmp.gamblit.persistence.BDB.store.eployee.Employee
The solution:
I fixed it modifying the managerId value from "4" to "101" and it works now!
At this moment I'm trying to understand the Sequence mechanism and refining concerns about Cursors manipulation...
Have you any good material about these topics, perhaps a link where I can find more detailed information on these?
Thanks in advance Mark, thanks for your attention on this and I will post more doubts in the future for sure ;0)
Regards,
Diego

Hi Diego,
I fixed it modifying the managerId value from "4" to "101" and it works now!I'm glad you found the problem. It is usually best to get the assigned ID from the entity object after you call put(), and then use that value to fill in related fields in other entities. The primary key field (assigned from the sequence) is set by the put() method.
At this moment I'm trying to understand the Sequence mechanism and refining concerns about Cursors manipulation...Have you any good material about these topics, perhaps a link where I can find more detailed information on these? >
To find documentation, start at the first message in the forum, the Welcome message:
http://forums.oracle.com/forums/ann.jspa?annID=250
This refers to the main JE doc page, the JE FAQ and a white paper on DPL queries. The FAQ has a section on the DPL, which refers to the javadoc. The DPL javadoc has lots of info on using cursors along with indexes (see EntityIndex, PrimaryIndex, SecondaryIndex). The white paper will be useful to you if you're accustomed to using SQL.
I don't know of any doc on sequences other than the javadoc:
http://www.oracle.com/technology/documentation/berkeley-db/je/java/com/sleepycat/persist/model/PrimaryKey.html#sequence()
This doc will point you to info on configuring the sequence, if that's what you're interested in.
--mark

Suggestions about interface: graph, directed and undirected graph

Hello all,
I'm having some doubts about the right 'choice' of interfaces. I'm designing a little library for graphs and I was thinking about the difference between directed and undirected graphs, and how I should reflect this in the library. My apologies for my bad English.
There is a small, but elegant, difference between directed and undirected graphs. Therefor, I don't know if it's worth to distuingish this difference in interfaces or not. I'll explain the difference by example. Usually, you can ask a directed graph the following queries:
- all out-edges of a node + the total of such edges (outdegree)
- all in-edges of a node + indegree
- the successors of a node
- the predecessors of a node
The same questions can be asked to a undirected graph, but the in-edges and the out-edges of a node are equal, the successors and the predecessors are equal, etc... Thats basically the only difference between directed and undirected graphs.
I found some solutions to define graphs, directed graphs and undirected graphs by means of interfaces.
[1] one interface, duplicate methods, no tagging interfaces
public interface Graph {
    Set getOutEdges(Node node);
    int getOutDegree(Node node);
    Set getinEdges(Node node);
    int getinDegree(Node node);
    Set getSuccessors(Node node);
    Set getPredecessor(Node node);
    boolean isDirected(); // no tagging interface
}[2] one interface, duplicate methods, tagging interfaces
public interface Graph {
    Set getOutEdges(Node node);
    int getOutDegree(Node node);
    Set getinEdges(Node node);
    int getinDegree(Node node);
    Set getSuccessors(Node node);
    Set getPredecessor(Node node);
public DirectedGraph extends Graph { } // tagging interface
public UndirectedGraph extends Graph { } // tagging interface[3] three interfaces
public interface Graph {
public interface DirectedGraph extends Graph {
    Set getOutEdges(Node node);
    int getOutDegree(Node node);
    Set getinEdges(Node node);
    int getinDegree(Node node);
    Set getSuccessors(Node node);
    Set getPredecessor(Node node);
public interface UndirectedGraph extends Graph {
    Set getTouchingEdges(Node node);
    int getdegree(Node node);
    Set getNeighbors(Node node);
}In the first solution, you dont know at compile time whether a graph is directed or undirected. However, it is very elegant for algorithms, since a lot of algorithms work for directed and undirected graphs. The main disadvantage of this solution is that you have duplicate functions in case of of undirected graphs: getOutEdges and getInEdges return the same set, etc.
The difference between the first and the second solution is that the second solutions gives a way to detect whether a graph is directed or undirected at compile-time.
The third solution has two seperate interfaces. This is much logical, and you know the graphtype at compile-time. However, this approach might lead to bloated code, as the algoritms for undirected and directed graphs now have two graphtypes (this can ofcourse be fixed by itroducing some kind of decorator, which in fact simulates the first solution).
As I don't have much experience in design, I can't forsee any big problems or disadvantes of one of the approaches. Therefor, I would like to ask for your opinion. What approach is most common and best practice?
Thanks in advance.

I would tend to go with true inheritance for this case. There is a strong ISA relationship between a graph and uni-directional and bi-directional graphs. Programming to an interface (as in the Lyskov substitution principle) will give you a parallel heirachy of interfaces and implementations. This can become a problem if you start out not knowing what interface needs to be published, but in the case of graphs this should not be a problem. With a heirachy all the shared code can be written once. In this case the specialized code will just simplify calling more general code in the parent class.
If all your graphs fit into memory then the implemenation should not be a problem. I used to work with map data where the graph does not fit into memory. Then you have to be careful about your interface or you will be getting calls that cannot be properly optimized "behind the scenes". Another specialization is in game programming where nodes are not actually expanded until they are "arrived at". Then you have to keep information about what parts of the structure are fleshed out and which are provisional.

Docs about Interfaces between CO and BW/BI

Hi all Gurus,
I am just looking for documents about Interfaces between FI/CO and BW/BI. Can any body provide me the required documents. It is very urgent.... [email protected]
Thanks in advance
SIM
Edited by: SIM on Feb 22, 2008 12:19 PM

Hi
You are right. I meant the interfaces between FI/CO and BW/BI. Namely how do we build the Interfaces such as IDOC and other interfaces between them. I need practice oriented docs with all steps towards building interfaces.
Thanks
SIM

Interfaces and final variables

So I understand that I am not supposed to put my final variables or constants into an interface, but then where?
I have 2 classes that implement an interface, and they both allow listerners to be added to them, through that interface. They both fire property events on the listener with the same property. Currently I just put the property id constants into one class and reference it from the other. But it appears to me the best place for the definition of these common properties is in the interface!?

So If you read over all the postings, you'll know exactly why they say, never to create classes for the purpose of grouping constants, it is confusing.
More explicitly, it is lazy. The reason you are grouping the constants has nothing to do with the relationship between the constants and their use within the program, you are grouping them because you are tired of typing a long declaration everytime you want to use them within the program. So, the overall design of your program is being warped by design decisions that are based on laziness.
The reason people put them in interfaces, "public interface Globals...", is so that importing that namespace through inheritance doesn't suck up that "valuable" superclass (which I will have to remember to rant about on some other thread). It is probably the case that the most efficient way to do this is to use static getters: getPI(), getOrigin(), getNewYears(), whatever. You will see an awful lot of constants that have been replaced over the years with getters. As the code matures, it isn't peculiar to see the flexibility of the programme being reduced or impeded by the constraints and constants implicit in the codesbase.
Andrew

Interface and Inheritence Differences

Hi, I'm new to java and have only a little experience with programming languages.
I can't seem to figure out what the differences and uses are for Inherited classes and interfaces.
I understand Interfaces set a list of methods and variables that must exist in implemented classes and that Super classes can define a default method.
What i want to understand is why I would use an interface rather than just extending a Super class.
Thanks.

oneplatformtorulethemall wrote:
What i want to understand is why I would use an interface rather than just extending a Super class.Two important reasons:
* completely unrelated classes (from different class hierarchies) can implement the same interface and need not have the same super class
* a class can implement more than one interface at once, while it can have only one super class
I might suggest that you don't care too much about that right now. Real understanding of the "why" can only come after you've used it for a while. Trying to understand the exact reasoning of this decision while you haven't used it a lot is probably pretty hard.

A question about grub and USB

Hi All
I have a quick question about grub and USB that I can't quite find the answer to by searching. Most of the FAQs discuss booting a full linux dristribution from USB. My situation is this. I am getting a new computer with two drives, the second will be arch and the first will be Vista (for my wife). I want the computer to boot the same way that my wife's machine boots at work so I don't want to install grub on the MBR. So, is there a way to have all of the grub config files and kernels installed on the second drive and simply install to grub boot loader to the MBR of a USB stick? My goal would be to simply plug the USB stick into the new PC and boot arch from the second drive.
Thanks
Kev

i cant say for hp's
havent worked on any in a while
recent machines have been coupleof dell's , vaio & emachine
which dells do offer it at least the ones i tried , my laptop does(dell)
all home pc's are built by me which do offer to boot individual drives
what hp you getting it may tell in specs
are both discs sata? if so it might not offer this option with 2 drives of same interface
check your power supply alot of these preconfigured machines put cheap under reated power supplies in there
& will burn your motherboard i just replaced PS(250 watt) & mobo(845gvsr) in an emachines <cheap stuff<
i hope you researched the pc before buying ie : mobo, power supply are the biggest concerns
i find it much more benificial to build my own machine gives me peace at mind. the cost is sometimes more in $ but not always , your biggest expense is time researching hardware
if you live in usa the best places to start looking are bensbargains.net & pricewatch.com
i am not affiliated with either & niether sell the hardware they are just advertisers a place to buy
for costomized machines that i would trust is unitedmicro.com theyll asemble & test before shipping
i have gotten 2 machines so far from them with NO PROBLEMS with hardware (knock knock)
you may want to consider this in your next venture for pc

About interface mapping

what are there case about interface mapping?
i knew that the following:
outbound to inbound
abstract to abstract.
what else the case?

Hi joy zheng ,
These r the details about interface mapping :
Interface Mappings
You can define mappings for an interface pair (source and target interface) by using message interfaces and message types in the Integration Repository.You can also define the corresponding mappings when the source or target interface is an IDoc, an RFC, or another interface connected by an adapter.
When defining mapping programs for request, response, or fault messages, the definition is first separated from the interfaces that reference the corresponding message types. Furthermore, you can reuse a message type for multiple interfaces. This means that the simple definition of a mapping program is not sufficient to establish a connection (that is based on the assignment of outbound and inbound interfaces).
This role is undertaken by the interface mapping:
●     An interface mapping specifies the corresponding mapping programs for request, response, or fault messages for a selected interface pair. You use an interface mapping to register mappings for an interface pair.
●     You can also specify multiple mapping programs to be executed one after the other in the case of requests and responses for an interface mapping.
You can also define multiple interface mappings for the same interface pair, to provide multiple variants in the Integration Repository. At configuration time, the customer can select the appropriate mapping in an interface determination and save it in the Integration Directory
Use :
Interface mappings register your mapping program for an interface pair in the Integration Repository. If you require a mapping at runtime, it is sufficient to select the interface mapping for the interface pair at configuration time . The Integration Server uses the interface mapping to identify associated mapping programs for request messages, response messages, fault messages, or all three.
Features
Executing Multiple Mapping Programs for One Direction
By using an interface mapping you can execute multiple mapping programs consecutively for the transformation of a request or response message. In such cases, an interface mapping comprises multiple steps for which the following applies:
●     The steps are executed in the sequence specified (from top to bottom). The result of the mapping program from the previous step is forwarded to the mapping program of the subsequent step.
●     Each step can reference a mapping program that executes a 1:1, 1:n, n:1, or an m:n transformation. In the case of multi-mappings (1:n, n:1, or m:n), the previous step must create the same number of messages that the subsequent step expects.
●     Multi-mappings use one envelope to put all messages in one structure. If one of the steps references a multi-mapping program, all subsequent steps must use the same envelope.
The mapping for a request message comprises two message mapping programs: one 1:1 transformation and one 1:n transformation. Since the latter message mapping uses the multi-mapping envelope for both the target message and the source message, the message mapping for the 1:1 transformation must also create a transformation result with a multi-mapping envelope.
You do not strictly need to divide up one direction of the whole mapping into different steps. However, this enables all the message formats in one system landscape to be mapped to a central message format, for example. This results in less mapping programs being required because you no longer need to be able to map all the different message formats to each other.
Activities
       1.      Create your interface mapping on the design maintenance screen of the Integration Builder (see also: Creating an Object).
You can also create multiple interface mappings for the same interface pair.
       2.      Enter the source and target interfaces that require a mapping of the request message, the response message, the fault message, or all three, in the table of the same name. The following restrictions apply:
○     If you want to use the interface mapping in a transformation step in an integration process, you must only specify abstract message interfaces. Furthermore, all objects (integration process, interface mapping, and all objects referenced by the interface mapping) must be in the same software component version. If you want to reference objects from underlying software component versions, you must access the objects from the Basis Objects branch (in the navigation tree or using an input help) (see also: Underlying Software Component Versions).
○     If you want to map multiple messages to each other by using a multi-mapping, you can only specify asynchronous interfaces (for further restrictions, see: Multi-Mappings). If any message interfaces are missing, you can also create them by using the functionCreate New Object ().
If the interface cannot be imported or cannot be created in the Integration Repository (in the case of an external adapter, for example), you must enter the interface names manually. However, it is not possible to check the technical name in this case.
       3.      To import the properties of the interfaces, choose Read Interfaces. The table in the lower area displays tab pages for the request message, response message, and if available, for the fault message, for each mode of the interfaces (either synchronous or asynchronous).
       4.      To develop an external mapping program, export the XSD schema of the respective request or response message as a zip file after you have imported the interfaces. The zip file can contain multiple schema files that reference each other, for example in a multi-mapping. In this case, the schema with the global message element has the name MainSchema.
       5.      To reference a mapping program for the respective message, you have the following options:
○     Select an existing mapping program from the Integration Repository by using the input help (). If this is a message mapping, the default setting of the input help only displays those message mappings that are found using the source and target message in the Integration Repository (in multi-mappings, the first source and target messages are used as the search criteria). However, you can also display any number of message mappings, for example, because you are constructing a mapping from several mapping programs with intermediate instances which have no message types.
○     You can create message mappings directly from the interface mapping. To do this, select the mapping type Message Mapping in the Type column. Position the cursor in the Name column and choose the function Create New Message Mapping () in the Mapping Program frame. The Integration Builder copies the specifications of the messages and their occurrence directly from the interface mapping.
An interface mapping can only reference mapping programs that belong to the same or an underlying software component version of the interface mapping. This ensures that the mapping program can be shipped together with the interface mapping (see: Software Logistics).
       6.      If you are not using a mapping for a fault message, you can execute multiple mapping programs in succession for request and response messages:
○     To insert an additional line for a mapping program, choose .
○     To delete the registration for a mapping program, choose .
At runtime, the mapping programs are executed from top to bottom.
       7.      Save the interface mapping.
The following web-site gives complete details about interface mapping :
http://help.sap.com/saphelp_nw2004s/helpdata/en/12/05731a10264057badc32d3d3957015/content.htm
**********Please reward points if u find this useful
cheers,
gyanaraj

BadRequest: Virtual machines with secondary network interfaces and virtual machines with no secondary network

I'm trying to create an "ExtraLarge" VM with multiple NICs. The New-AzureVM returns the following error:
BadRequest: Virtual machines with secondary network interfaces and virtual machines with no secondary network
interfaces are not supported in the same deployment, also a virtual machine having no secondary network interfaces
cannot be updated to have secondary network interfaces and vice-versa.
But I have no other VMs. Or at least I did and then deleted them and all their disks. The service has no deployments (either staging or production).
Why is New-AzureVM complaining about a mismatch of VMs with and without secondary network interfaces when no other VMs exist?
I have tried many things to fix this, including the deletion of ALL of my resources. I have deleted and created the service many times, both with an affinity group and without. I have a screen print of the -debug output if your interested.
Thanks for the outstanding help.

Hi Ron,
IMPORTANT NOTE: Please do not post the CONFIDENTIAL DETAILS ever on the public forums, this is HIGH RISK action.
Please send an email with your contact details to my email
[email protected] so that I guide you on steps which help you come out of the current scenario. Thank you for understanding.
I suggest you to create a new VNET and new VM with cloud services. Create Multiple NIC VM. Let us know the results.
Ref:
http://azure.microsoft.com/blog/2014/10/30/multiple-vm-nics-and-network-virtual-appliances-in-azure/
http://blogs.technet.com/b/canitpro/archive/2014/11/04/step-by-step-create-a-vm-with-multiple-nics-in-azure.aspx
If you are unable to create a VM with multiple NIC, please open a support case as it requires more confidential information which is out of scope of FORUM support offerings.
Regards,
Girish

About interface and Inheritance

Similar Messages

Maybe you are looking for