Nilesh Kapadia

As you may already know, Java's generics are just compile-time checking and are not implemented in the JVM, whereas C#'s generics have type-checking implemented in both the compiler and the CLR and is more strongly-typed. However, Java's looser implementation allows the following, whereas C#'s does not:

Lets say we have a generic interface:

public interface GenericInterface<T> {
    public int getSize(T t);
}

And we have interfaces that extend this interface:

public interface StringInterface extends GenericInterface<String> {
}

There are two issues with Axis(Java)/.Net interop that were discovered in a project I am involved in. We are using doc/literal web services as mentioned in my last entry about Java/.Net web services interop.

1. Empty arrays received from Java are interpreted as null objects on the .Net side. I have not fully researched why this happens, but we work around it by checking for null.
   

This entry can be summed up in two statements: