In Java, types are declared in their own files. There can be only one type in a single Java source file, and the file name must be the same as the type name.
C# namespaces are mostly equivalent to Java packages. Every type is contained in a package, which is defined at the top of the source file (where the type is declared). Usually, the whole application defines a root package such as "com.mycompany.appname", and all types exist in this package or sub-packages (such as "com.mycompany.appname.subpackage"). The package definitions may also reflect the folder hierarchy in the project. However, there is no aliasing or nesting of packages.
In Java, inheritance is done using the "extends" keyword and interface implementation is done using the "implements" keyword (for example, "class A extends B implements IC, ID")
There is no "readonly" keyword (or equivalent) in Java.
All user-defined types are reference types and only primitive types are value types. Reference types are always passed by reference and value types are always passed by value (copied). There's no equivalent to the "ref" or "out" keyword in Java.
There is no delegate concept in Java. The only way to simulate this is using reflection.
Java’s "synchronized" keyword ensures thread safety before entering a method as does the [MethodImpl(MethodImplOptions.Synchronized)] attribute in C#.
In Java, a programmer cannot implement two interfaces that declare the same method.
Java doesn’t allow static constructors. Instead, there's a static block.
In Java, there is no property construct–properties need to be defined explicitly (declaring set/get methods in the containing class).
In Java, the "protected" access modifier allows access from any other type in the same package, in addition to derived types.
In Java, all methods are virtual by default, and there are no "virtual" or "override" keywords.
In Java, a programmer cannot further restrict access to an override (over the access of the overridden member).
There are no indexers in Java.