Interfaces implicitly public?

[Nidhi Sar]

Hi,

As per my understanding, all the methods & variables in an interface are implicitly public, but the interface itself May have public or package access. Is that correct?

So here:

interface Bounceable{
                 int i = 9;
                 void myMethod();
}    

i & myMethod() are implicitly public but Bounceable has package access.

Am I correct?

[Wouter Oet]

You're somewhat correct.

Methods in a interface are implicit public and variables are implicit public static and final!
Non-inner interface may have default or public access. However an inner interfaces may
have all accesslevels.

public class InterfaceTest
{
	private interface Test{}
}    

[Nidhi Sar]

Wouter Oet wrote:However an inner interfaces may
have all accesslevels.

public class InterfaceTest
{
	private interface Test{}
}    

Thanks Wouter!! Glad to know that I was correct on the first part. But... what are inner interfaces used for. I know about the uses of inner classes, but inner inetrfaces???

[Wouter Oet]

An example of an inner interface is the java.util.Map.Entry interface. A public interface.

[Nidhi Sar]

Wow, perfect example! Thanks Wouter

[Wouter Oet]

Glad I could help.

[Muhammad Khojaye]

what are inner interfaces used for. I know about the uses of inner classes, but inner inetrfaces???

They make sense when the interface is only used in conjunction with the class.
Map.Entry point out by Wouter is a good example. The Entry interface is only associated with the Map, therefore they define it as nested interface. If Map.Entry defines as separate interface, then people can refer to Map.Entry outside of the context of a Map. Define Entry as part of a Map provides better understanding of relationship.

Oops... Too late...