Implementing two generic interfaces

I have a generic interface,
public interface Callback<R> {
   void result(R r);
}Now I want to implement two Callback interfaces, like this
class X implements Callback<Type1>, Callback<Type2> {
   public void result(Type1 r) {};
   public void result(Type2 r) {};
}But Eclipse tells me "The interface Callback cannot be implemented more than once with different arguments".
I don't see the reason why really. The two overloaded result methods have different signatures so there shouldn't be any problem in resolving the correct one based on parameter type in principle.
Does anybody know the reason for this restriction or is it maybe an issue with Eclipse. I'm using Eclipse 3.2M5a and Java 6.0 beta.

mlk has the correct answer, but here's some more explanation:
Generics are only used at compile time. The actual bytecode specifies the base object type (aka type erasure), in this case Object. When you implement a generified interface, the compiler will generate a bridge method from the erased type to the specific type.
Some examples should make this clearer.
First, your interface. If you run javap on the compiled class, you'll see that it only defines a single method, "void result(Object)".
Code that invokes the interface, like this:
    Callback<String> foo = \\
    foo.result("bar");also gets translated to a call on the base type. As far as the compiled class is concerned, there is no type safety. However, the compiler will complain if you pass something other than a String.
The implementation class is where things get interesting:
public class TestCallback implements Callback<String> {
  public void result(String x) {
}If you run javap on this class, you'll see that it contains two implementations of result(): one that takes a String, and one that takes an Object. If you look at the bytecode, the latter performs a cast on the Object and invokes the String variant.

Similar Messages

  • Enum implementing Generic interface

    Is there any way to implement a generic interface and specify the types for each enum
    public interfact IPrimaryKeyType<C extends Object> {
    public enum PrimaryKeyType implements IPrimaryKeyType {
    SINGLE,
    COMPOSITE,
    There is no way to specify the type for each enum element. Though you can specify the type for all enums as below.
    public enum PrimaryKeyType implements IPrimaryKeyType<Object> {
    SINGLE,
    COMPOSITE,
    Any ideas?

    The best way to answer questions like this is to look at the spec: http://java.sun.com/docs/books/jls/third_edition/html/classes.html#8.9
    The answer seems to be that what you're trying to do is impossible.

  • How to implements two interface?

    i have a applet to implement two interface,the actionlistener and the appletcontext.how to do it??
    Thank You!

    with a comma

  • Specialized vs. Generic Interfaces?

    Hi,
    I am new to these forums, please let me know if this is already part of a FAQ or not the appropriate place to ask this question.
    When designing an interface, would you recommend specialized or Generic Interfaces?
    As I am not sure if makes any sense, here are the two thinkings I have to define a myObject.getExportOptions() method that would return the ExportOptions that can be applied (i.e. "setCharacterDelimiter" for CSV export, "setHeader" for PDF, HTML....)
    Option 1:
    the code looks like:
      myObject.setExportMode(MICROSOFT_EXCEL);
      myExportOptions = (ExportOptionsExcel) myObject.getExportOptions();where the getExportOptions() would be defined as
    ExportOptions getExportOptions(); with the ExportOptions interface only defining all the common export options to all the export methods (PDF, Excel, HTML, Text...). And then to get to the export options that are specific to an export format, you would have to cast the object to a specific interface which extends the "generic" interface.
    Option 2:
    the code looks like:
      myObject.setExportMode(MICROSOFT_EXCEL);
      myExportOptions = myObject.getExportOptions();where the getExportOptions() would be defined as
    ExportOptions getExportOptions();with ExportOptions defining all the export options accross all the export methods (PDF, Excel, HTML, Text...). But if you tried to call the ".setExcelFormat(EXCEL_95)" method when the ExportMode is set to "TEXT_ONLY" then an exception would be raised (maybe something like "ExceptionNotApplicableToExportFormat").
    I did not find any document describing the prefered method of building this.... Any idea?
    Thanks,
    MonLand.

    I think I was not clear enough in my first message. Let me try to re-explain with a little bit more details (and more pseudo-code).
    Option 1:
    myReport.setExportMode(MICROSOFT_EXCEL);
    ExportOptions myExportOptions = myObject.getExportOptions();
    myExportOptions.setExportFileName("myReport"); // This would be common to any "export format" Now, for the "Excel" specific parameters, I would have to cast the options:
    ExportOptionsExcel myExcelExportOptions = (ExportOptionsExcel) myExportOptions;
    myExcelExportOptions.setExcelFileFormat(EXCEL_97);From the implementation point of view, I can have one "generic" ExportOption class/interface that contains all the common export properties. In addition, three or more classes that implement the specific export settings (one for Text_ONLY; one for MICROSOFT_EXCEL; one for PDF.....). From the developer point of view, to be able to set the "specific" properties, they have to know what interface to cast the export options to (because in the background, the reportObject class would create/return the "right" export options based on the export format that was set).
    Option 2:
    This time the ExportOptions is a much more generic interface and declares everything. But an exception is raised if I am trying to set parameters that don't make sense:
    myReport.setExportMode(MICROSOFT_EXCEL);
    ExportOptions myExportOptions = myObject.getExportOptions();
    myExportOptions.setExportFileName("myReport"); // This would be common to any "export format"
    myExportOptions.setExcelFileFormat(EXCEL_97);Now, if I was to do:
    myReport.setExportMode(TEXT_ONLY);
    ExportOptions myExportOptions = myObject.getExportOptions();
    myExportOptions.setExportFileName("myReport"); // This would be common to any "export format"
    myExportOptions.setExcelFileFormat(EXCEL_97);This last line would raise an exception (let's say "UnsupportedProperty") because the Text mode does not support the ExcelFileFormat property.
    From the implementation point of view, I can have three or more classes that implement the "ExportSettings" interface (one for Text_ONLY; one for MICROSOFT_EXCEL; one for PDF.....). But from the developer point of view, it does not matter with class gets used.
    Why I am asking: I am currently facing a design that looks like Option 1 and I can not figure out why this has to be that complex to use. Very hard to document if you replicate that design everywhere in a large API with a large number of objects/interfaces; you never know what to cast the object to; you never can guess what method you are looking for because you have to look at the definition of 3 or 4 interface at the minimum to see if you see something that fits your needs. So I am trying to understand if this is because it is much easier to implement that Option 2.
    I see the following drawback for Option 2: If you need to add an extra property to one of the export format, you probably have to update the "generic" interface, the "generic" implementation of that interface, and each "specific" implementation to reflect that new property.
    Thanks a lot for your time!
    MonLand

  • How to refer to genericized interface

    Hi,
    I have the following interface:
    package org.tbiq.gwt.tools.rpcrequest.server;
    import org.tbiq.gwt.tools.rpcrequest.browser.RpcRequest;
    import org.tbiq.gwt.tools.rpcrequest.browser.RpcRequestException;
    import org.tbiq.gwt.tools.rpcrequest.browser.RpcRequestService;
    import org.tbiq.gwt.tools.rpcrequest.browser.RpcResponse;
    public interface RpcRequestHandler<ReqT extends RpcRequest<ResT>, ResT extends RpcResponse>
    public boolean isCompatibleWith(Class<ReqT> rpcRequestClass);
    public ResT execute(ReqT rpcRequest)
    throws RpcRequestException;
    }I also have a dummy implementation of this interface:
    package org.tbiq.gwt.tools.rpcrequest.server;
    import org.tbiq.gwt.tools.rpcrequest.browser.DummyRpcRequest;
    import org.tbiq.gwt.tools.rpcrequest.browser.DummyRpcResponse;
    import org.tbiq.gwt.tools.rpcrequest.browser.RpcRequestException;
    public class NewDummyRequestHandler
    implements RpcRequestHandler<DummyRpcRequest, DummyRpcResponse>
    @Override
    public DummyRpcResponse execute(DummyRpcRequest rpcRequest)
    throws RpcRequestException
    // TODO Auto-generated method stub
    return null;
    @Override
    public boolean isCompatibleWith(Class<DummyRpcRequest> rpcRequestClass)
    if (DummyRpcRequest.class == rpcRequestClass)
    return true;
    return false;
    }This interface refers to 2 dummy objects DummyRpcRequest and DummyRpcResponse. There is nothing special about them. They are just regular beans that implement marker interfaces (RpcResponse and RpcRequest<T extends RpcResponse>).
    DummyRpcResponse:
    package org.tbiq.gwt.tools.rpcrequest.browser;
    @SuppressWarnings("serial")
    public class DummyRpcResponse
    implements RpcResponse
    }DummyRpcRequest:
    package org.tbiq.gwt.tools.rpcrequest.browser;
    @SuppressWarnings("serial")
    public class DummyRpcRequest
    implements RpcRequest<DummyRpcResponse>
    }Somewhere else, I have a class that implements some other interface. Part of implementing that interface is this method:
    @Override
    public <T extends RpcResponse> T execute(RpcRequest<T> rpcRequest)
    throws RpcRequestException
    RpcRequestHandler<??????> handler = new NewDummyRequestHandler();
    return handler.execute(rpcRequest);
    }So, the '?????' is my question. How do I refer to the handler such that it compiles. Right now, now matter what I try in that line, the handler.execute(rpcRequest) doesn't compile.
    Also, it's possible that I messed up my RpcRequestHandler interface and defined it in a wrong way (as far as generics are concerned). I am not sure.
    Any help would be much appreciated!
    Thanks,
    Yaakov.
    P.S. The code in the last method is obviously for testing only. I am planning to have a Map of those handlers and choose the handler dynamically based on the type of the RpcRequest that is passed into the execute method.
    Edited by: ychaikin on Feb 23, 2010 1:10 PM

    Had a play round some more with this to refresh my knowledge, and understand exactly where you're coming from
    I don't know what your RpcRequest and RpcResponse interfaces look like - although since your concrete implementations DummyRpcRequest and DummyRpcResponse don't implement any methods, I guess that means that the two interfaces are blank.
    The fact that the RpcRequest takes a parameter of a subclass of RpcResponse, though, implies that there's some sort of relationship there. Perhaps, in future, you intend to have a method sig in RpcRequest that say, returns a subclass of (the type of RpcResponse you created the concrete implementation of RpcRequest with). It's hard to offer more suggestions without knowing exactly what you intend with this code.
    A handler takes a RpcRequest<RpcResponse>, runs its execute method, and somehow (depending on implementation) returns an RpcResponse.
    So I tested some code which I guess summarises your situation, and which works okay - if you want, you can blat this all into a file Test.java and compile/run it in textpad.
    interface Response {
         String message();
    class SpecificResponse implements Response {
         public String message() { return "Why hello there!"; }
    interface Request<E extends Response> {}
    /* This Request subclass stores a canned, fixed Response object. */
    class StoredResponseRequest<E extends Response> implements Request<E> {
         private E myResponse;
         public StoredResponseRequest(E useThis) {
              myResponse = useThis;
          public E getStoredResponse() {
              return myResponse;
    /* A handler <B, A> is able to take in a B (extends Request<A>), and return an A. */
    interface Handler<B extends Request<A>, A extends Response> {
         public A execute(B request);
    /* A HandlerForStoredResponseRequests works by assuming that all the Request<A>s it gets passed are, in fact,
         StoredResponseRequest<A>s. It therefore extracts the necessary A from the object and returns it.  */
    class HandlerForStoredResponseRequests <B extends Request<A>, A extends Response> implements Handler<B, A> {
         public A execute(B sreq) {
              return ((StoredResponseRequest<A>)sreq).getStoredResponse();
    class Test {
         public static void main(String[] argz) {
              Request<Response> request = new StoredResponseRequest<Response>(new SpecificResponse());
              System.out.println( execute(request).message() );
         public static <T extends Request<E>, E extends Response> E execute(T request) {
              Handler<T, E> stuffHandler = new HandlerForStoredResponseRequests<T, E>();
              return stuffHandler.execute(request);
    }

  • Generic interface in abstract super class

    hello java folks!
    i have a weird problem with a generics implementation of an interface which is implemented in an abstract class.
    if i extend from this abstract class and try to override the method i get this compiler error:
    cannot directly invoke abstract method...
    but in my abstract super class this method is not implemented as abstract!
    do i have an error in my understanding how to work with generics or is this a bug in javac?
    (note: the message is trown by the eclipse ide, but i think it has someting to do with javac...)
    thanks for every hint!
    greetings daniel
    examples:
    public interface MyInterface <T extends Object> {
       public String testMe(T t);
    public abstract class AbstractSuperClass<T extends AbstractSuperClass> implements MyInterface<T> {
       public String testMe(T o) {
          // do something with o...
          // now we have a String str
          return str;
    public final class SubClass extends AbstractSuperClass<SubClass> {
       @Override
       public String testMe(SubClass o)
          return super.testMe(o);
    }

    Hi Wachtda,
    Firstly, T extends Object is redundant as all classes implicitly extend the Object class.
    Therefore :
    public interface MyInterface <T> {
       public String testMe(T t);
    }Secondly, abstract classes may have both abstract and non-abstract instance methods. Also, two methods, one abstract and one non-abstract, must have a different signature.
    The following example will give a compile error because the methods share the same signature :
    abstract class Test {
         public void sayHello() {
              System.out.println("Hello");
         abstract public void sayHello();
    }Therefore, to make an interface method as abstract would simply block the possibility of implementing it.
    BTW, you can do this :
    abstract class Test {
         public void sayHello() {
              System.out.println("Hello");
         abstract public void sayHello(String name);
    }Finally, there's no bug in javac.

  • Writing generic interfaces?

    I would like to write a generic interface for a Factory. The implemented Factory should as minimum contain two methods that returns a List of "something" as seen below.
    But I don't want to put any restrictions on the return type since a user might want to use objects from his or her own API. Is the solution to just specify the interface as:
    public interface IReportFactory {
         List newProducts();
         List newTables();
    }

    Here's a small example to guide you. Good luck my friend...
    import java.util.*;
    public class Test
         public static void main(String... args)
              List<Product> prodList = new ArrayList<Product>();
              prodList.add(new Product("radio", 100)); prodList.add(new Product("Walkman", 50));
              List<Table> tableList = new LinkedList<Table>();
              tableList.add(new Table("customer", 100)); tableList.add(new Table("Product", 1000));
              Report r = new Report(prodList, tableList);
              System.out.println("Products\n----------\n"+r.newProducts());
              System.out.println("Tables\n----------\n"+r.newTables());
              System.out.println("\nChanging Structures to Vector and Stack\n");
              prodList = new Vector<Product>();
              prodList.add(new Product("radio", 100)); prodList.add(new Product("Walkman", 50));
              tableList = new Stack<Table>();
              tableList.add(new Table("customer", 100)); tableList.add(new Table("Product", 1000));
              r = new Report(prodList, tableList);
              System.out.println("Products\n----------\n"+r.newProducts());
              System.out.println("Tables\n----------\n"+r.newTables());
    class Product
         String name; double price;
         Product(String n, int p){ name = n; price = p;}
         public String toString(){ return "\nName = "+name+" & Price = "+price+"\n";}
    class Table
         String name; int numRecs;
         Table(String i, int v){ name = i; numRecs = v;}
         public String toString(){ return "\nName = "+name+" & # of Records = "+numRecs+"\n";}
    class Report<T, V> implements IReportFactory<T, V>
         T prodList;
         V tableList;
         Report(T prodList, V tableList)
              this.prodList = prodList;
              this.tableList = tableList;
         public T newProducts()
              return this.prodList;
         public V newTables()
              return this.tableList;
    interface IReportFactory<T, V>
         T newProducts();
         V newTables();
    }

  • How to name implementation of an interface

    Hi there
    is there any standard for naming concrete implementation of interfaces?
    So if I have an interface
    A
    in package "interfaces"
    is it sensful to call the concrete implementation of the interface interfaces.A A, too?
    class A implements interfaces.A{
    }? Or should it be called ConcreteA, or or or....?
    Thx for your tips.
    Sincerely
    Karlheinz Toni

    JebeDiAH heres a very interesting reading.
    Class and Interface Names
    Class names are always nouns, not verbs. Avoid making a noun out of a verb, example DividerClass. If you are having difficulty naming a class then perhaps it is a bad class.
    Interface names should always be an adjective (wherever possible) describing the enforced behaviors of the class (noun). Preferably, said adjective should end in "able" following an emerging preference in Java. i.e. Clonable, Versionable, Taggable, etc.
    Class, and interface names begin with an uppercase letter, and shoule not be pluralized unless it is a collection class (see below).
        Acceptable:
            class FoodItem
            interface Digestable
        UnAcceptable:
            class fooditem
            class Crackers
            interface Eat
    Naming collection classes (in the generic sense of collection) can be tricky with respect to pluralization. In general each collection should be identified as a plural item, but not redundantly so. If you are a collection type as part of the class name (List, Map, etc.) it is not necessary to use the plural form in the class name. If you are not using the collection type in the name it is necessary to pluralize the name. If you are extending one of the java colletction class (Map, HashMap, List, ArrayList, Collection, etc.) it is good practice to use the name of the collection type in the class name.    
        Acceptable:
            class FoodItems extends Object
            class FoodItemList extends ArrayList
            class FoodItemMap extends HashMap
        UnAcceptable:
            class FoodItem extends ArrayList
            class FoodItemsList extends ArrayList
    Class names should be descriptive in nature without implying implementation. The internal implementation of an object should be encapsulated and not visible outside the object. Since implementation can change, to imply implementation in the name forces the class name and all references to it to change or else the code can become misleading.
        Acceptable:
            AbstractManagedPanel
            LayeredPanel
        UnAcceptable:
            PanelLayerArray
    When using multiple words in a class name, the words should be concatenated with no separating characters between them. The first letter of each word should be capitalized.
        Acceptable:
            InverntoryItem
        UnAcceptable:
            Inverntory_item
            Inventoryitem
    Other than prefixes, no abbreviations should be used unless it is a well known abbreviation.
        Acceptable:
            CD=Compact Disc
            US=United States
        UnAcceptable:
            Cust=Customer
            DLR=Dealer
    I found it at http://www.iwombat.com/standards/JavaStyleGuide.html

  • Implement multiple remote interfaces

    Hi there, I wanted to write an RMI application with an remote object which implement two different remote interfaces, each has its own remote methods.
    eg:
    public class TestImpl implements Test1, Test2 {
    I only want to allow client to call the methods from Test1 remote interface (without Test2.class in the package). But exception NoClassDefFound of Test2 is caught. The reason I want to do like this is because I have a method in Test2 to unexport the remote object, call by server, so I want to hide it from client.
    I implement the system with Activation, but I couldn't unexport the TestImpl from somewhere else on the same activation group by using Activatable.unexportObject(..). I only can unexport it inside TestImpl remote object itself by calling Activatable.unexportObject(this, true); otherwise, NoSuchObjectException is caught.
    Thanks,
    Jax

    If X and A are in the same activation group, X can
    unexport A as long as it has a reference to the actual
    object A not its stub (because unexportObject() takes
    an impl not a stub).Yes, it's true that X can unexport A because there are within the same JVM. But the problem is I can't get the actual object of A.
    For example:
    // assume this code is within X
    ActivationGroupID agi = ActivationGroup.currentGroupID();
    ActivationDesc desc = new ActivationDesc(agi, "A", location, data);
    ActivationID id = ActivationGroup.getSystem().registerObject(desc);
    Remote remote = id.activate(true);
    The code above will only return a stub.
    Even if I use Activatable.register(desc), it returns a stub as well.
    How do I get the actual object?

  • Generic interface methods

    The problem is that I want a generic interface that has a method that returns type T. And concrete implementations specify the type T and the method body.
    Given the interface and class below, why do I get an unchecked conversion warning, and how do I eliminate it? Or is there an alternative?
    Warning displayed by eclipse:
    Type safety: The return type String of the method convert(String) of type AsciiStringConverter needs unchecked conversion to conform to the return type T of inherited method.
    This code compiles...
    public interface StringConverter<T>
        public T convert(String string);
    public class CharacterValueConverter implements StringConverter<int[]>
        public int[] convert(String string) //unchecked conversion warning
            int[] values = new int[string.length()];
            for (int i = 0; i < string.length(); i++)
                values=(int)string.charAt(i);
    return values;
    Thanks,
    C.

    Here is the code that is used to test the CharacterValueConverter...
    public class Test
        public static void main(String[] args)
            int[] values = new CharacterValueConverter().convert("abc");
            for(int i : values)
                System.out.println(i);
    }

  • We are contemplating a Mac for a family Christmas gift -we currently use a windows based laptop.  Do the two systems interface? If a child starts his homework on the pc - can he finish it on the Mac? Can they both be hooked up to the same printer?

    We are Mac beginners, considerin a Mac for a family Christmas gift.  We currently share one windows based pc. Does anyone use a Mac AND a pc in their household?  Would the two systems interface?  (Can you start your homework on one system, but finish it on another?)  Can they both be hooked up to the same printer?  What advice would you give us as we consider this big purchase?

    You may find this useful:
    Switching from Windows to Mac:
    http://support.apple.com/kb/HT2514?viewlocale=en_US
    and
    http://support.apple.com/kb/HT2518?viewlocale=en_US
    and possible even the 'propaganda bits':
    Macs are cheaper to own that PCs:  http://techpatio.com/2010/apple/mac/it-admins-total-cost-ownership-mac-less-pc
    and: http://www.zdnet.com/blog/apple/tco-new-research-finds-macs-in-the-enterprise-ea sier-cheaper-to-manage-than-windows-pcs/6294
    Why will you love Mac? http://www.apple.com/why-mac/
    - Better Hardware http://www.apple.com/why-mac/better-hardware/
    - Better software  http://www.apple.com/why-mac/better-software/
    - Better OS http://www.apple.com/why-mac/better-os/
    - Better Support http://www.apple.com/why-mac/better-support/
    - It's Compatible http://www.apple.com/why-mac/its-compatible/

  • Static NAT with two outside interfaces

    I have a router, which performs NAT on two outside interfaces with load balancing and had a task to allow inbound connection to be forwarded to the specific host inside on a well known port.
    here is example
    interface Fas0/0
    ip nat outside
    interface Fas0/1
    ip nat outside
    interface Vlan1
    ip nat inside
    ip nat inside source route-map rm_isp1 pool pool_isp1
    ip nat inside source route-map rm_isp2 pool pool_isp2
    all worked fine
    then i tried to add static nat
    ip nat inside source static tcp 10.0.0.1 25 interface Fas0/0 25
    ip nat inside source static tcp 10.0.0.1 25 interface Fas0/1 25
    and in result only last static NAT line appeared in config.
    the solution was to use interface's IPs instead of names. that helped but isn't that a bug?

    In this scenario, we are trying to access a mail server located at
    10.0.0.1 from outside and we have two outside IP, let's say, 71.1.1.1 and
    69.1.1.1.
    With CEF Enabled
    Packet comes in to Fa0/0 interface with Source IP 66.x.x.x and
    Destination IP 71.1.1.1. Our NAT rule translates this to 10.0.0.1.
    Packet goes to 10.0.0.1. The return packet goes to the LAN interface
    first and the routing rule is determined *before* the packet is
    translated.
    Packet source IP at this point is 10.0.0.1 and destination is
    66.x.x.x. Now, based on CEF, it will go out via Fa0/0 or Fa0/1,
    irrespective of the way it came in. Because of this, with CEF enabled
    this will not work. CEF is per-destination.
    So, let's say somebody on outside tried to access this server using 71.1.1.1, then he would
    expect a reply from 71.1.1.1 which may or may not be true as the traffic could be Nat'd to 69.1.1.1 or 71.1.1.1.
    If it gets reply packet from 71.1.1.1, it should work.
    If it gets it from 69.1.1.1, it will simply drop it as it never sent a
    packet to 69.1.1.1.
    With CEF and Fast Switching Disabled
    Same steps as above, only that the packet is sent to the process level
    to be routed. At this point, the packets will be sent out in a round
    robin fashion. One packet will go out via the Fa0/0 and the other via the
    Fa0/0. This will have a constant 50% packet loss and is also not a
    viable solution.
    So, what are you trying to achieve is not possible on Cisco router.
    HTH,
    Amit Aneja

  • How to upload records  in two different interface tables through WebADI.

    We have created custom integrator with two different interfaces to insert records in AP_INVOICES_INTERFACES and AP_INVOICE_LINES_INTERFACE. Also defined the custom layout in which we mention the header and lines column info to be displayed in the spreadsheet. When I tried to create document to upload the records into the interface tables, could find two different interface for header and lines , when we select the header and upload records into the AP_INVOICES_INTERFACES table it was successfull. But couldn't upload records inserted in Lines interfaces tables. How do we upload records in both the table do we have constraint with Web ADI can insert records to only one interface tables. Any recommendation highly appreciated.

    Raghu,
    Thanks for the reply,
    I have a concern, But if you are connecting a another database you have to create one more subreport and each time am creating connections across databases we have to create subreport and go for the design to show the record. Is it any way to have a common field or union records approach in crystal report 2008.
    For Example :
    Approach 1 :
    Emp name           Emp salary      (Common Header)
    Variable Field1    Variable field2   ( Iterations to be done here for records)
    Variable field 1 contains ---> emptbl(employee name), b.emptbl(employee name) (A database, b database, c database or any .db)
    Variable field2  contains --->  emptbl (salary info between databases)
    Approach 2:
    getting all the records and union all the records 
    Thanks
    Murali Sri

  • The XElement class explicitly implements the IXmlISerializable interface?

    I see a sentence on a training book.
    "The XElement class explicitly implements the IXmlSerializable
    interface, which contains the GetSchema, ReadXml, and
    WriteXml methods so this object can be serialized."
    I don't understand it. From
    the example, explicitly implements the IXmlSerializable interface is from a custom class rather than XElement class. Is
    MSDN wrong?

    I mean in the stackoverflow example,the class is a customized one "MyCalendar:IXmlSerializable"
    public class MyCalendar : IXmlSerializable
    private string _name;
    private bool _enabled;
    private Color _color;
    private List<MyEvent> _events = new List<MyEvent>();
    public XmlSchema GetSchema() { return null; }
    public void ReadXml(XmlReader reader)
    If XElement is a class that implements IXmlSerializable, what is the detail then?
    public class XElement : IXmlSerializable
    public XmlSchema GetSchema() { *detail*?; }
    public void ReadXml(XmlReader reader){*detail*?}
    Any source code of XElement class?

  • Finding implementations of an interface programmatically

    Hi... would anyone know how to find programmatically all classes that implement an interface?
    Ideally, I would like to query on an interface and end up with a list of Class objects (i.e. the implementations of said interface).
    Thanks
    Message was edited by:
    javaBoy

    can't be done. this gets asked all the time, and it's impossible. Yes - technically correct.
    However, in many contexts where you know what classloaders are at play (and lets face it, many of us do work on projects where we use known classloaders, and dont have some random loading off the net on demand going on), it is possible, useful, and very much do-able - if you accept the limitations and constraints.
    So, OP, do a search and you'll probably find something useful to you.
    ~D

Maybe you are looking for

  • Error while installing Grid Control 12c (ERROR STREAM: *sys-package-mgr*: skipping bad jar)

    Hi all,    OS: OEL 6.3 64 bits    DB: 11.2.0.3    Grid: 12.1    While installing Grid Control 12c, the following error appears to me: INFO: SaveInvWCCE JRE files in Scratch INFO: oracle.installer.mandatorySetup property is set to false, so skipping t

  • Read Only Permissions Error

    Hi Guys I have a major problem with file saving permissions Current setup: - 5 imac (10.6) - 1 mac book pro (10.6) - mac xserver - Direct attached Raid Array Issue: When user "A" creates new files and folders to the shared drive on the raid array it

  • Movement 543 F always take sales order as cost object

    Dear sap expert, I run MTO scenario. In one of my step before a product become finish good, the semi finish good need to sent to subcon vendor (the material need another process outside company production line). The good issue journal is happen when

  • Placeholder for IN condition in database adapter

    I'd like to pass a parameter to a database adapter which will modify the "in condition" portion in a select. For example: select firstname from xxx where lastname in (#arg1) Is this the correct syntax? If so, what values will arg1 take? Something lik

  • Problem with Dual-SIM

    Hi. I have such a problem, that I'm using a dual SIM card in my Nokia E7, but I don't see that they're calling my business or my private number. Is there an app that would show me the number, where to they call?