Static methods and interfaces in Java

Question

I Have a UserEntity class which implements the IUserEntity interface.

In the UserEntity class I have a static map:

private static Map<IUserEntity.IIdentifiable, IUserEntity> staticUserEntityMap = new HashMap<>();

In the IUserEntity interface I would like to write a method like that:

public Collection<IUserEntity>      getUsers();

And in the class :

public static Collection<IUserEntity> getUsers(){
    return staticUserEntityMap.values();
}

But I can't declare static methods in the interface and I can't change the method signature in the UserEntity class.

How can I do this ?

What's wrong with `public Collection getUsers(){ return staticUserEntityMap.values(); }` — SMA, Dec 26 '15 at 13:32
Just write a non static method calling the static one if you can't change any signature. — Gaël J, Dec 26 '15 at 13:38
Interfaces cannot have static methods without a method body. That's it. In general interface and static dont work well together, which makes sense. — luk2302, Dec 26 '15 at 13:41
Also you might want to look at http://stackoverflow.com/questions/512877/why-cant-i-define-a-static-method-in-a-java-interface (Java 8 allows static methods in interfaces). — Gaël J, Dec 26 '15 at 13:44

score 3 · Accepted Answer · edited Dec 26 '15 at 14:09

3

In Java 8 you can have default implementations in interface but I believe that will not solve your problem. Instead of changing the method signatures you can create a separate static method and call it with the class name within getUsers implementation. e.g.

Create new method:

public static Collection<IUserEntity> getUsersStatic() {
   return staticUserEntityMap.values();
}

Call this method from getUsers:

public Collection<IUserEntity>      getUsers() {
  return UserEntity.getUsersStatic();
}

edited Dec 26 '15 at 14:09

Gaël J

11,274
4
17
32

answered Dec 26 '15 at 13:45

Riaz

104
4

Huummmm, Then i have to do this for all CRUD methods if i want to implements those ? And each UserEntity object have access to those "static" methods isn't bad ? – Maxime Gajovski Dec 26 '15 at 14:13

score 2 · Answer 2 · edited May 23 '17 at 12:04

I'd refer you to this question, and the docs:

In addition to default methods, you can define static methods in interfaces. (A static method is a method that is associated with the class in which it is defined rather than with any object. Every instance of the class shares its static methods.) This makes it easier for you to organize helper methods in your libraries; you can keep static methods specific to an interface in the same interface rather than in a separate class.

You could, however, implement the field in the interface as well, as that would allow you to implement your simple static method. Downside would be that the Map would become public. It'd look like this:

public interface  IUserEntity {
// ...

 static Map<IUserEntity.IIdentifiable, IUserEntity> staticUserEntityMap = new HashMap<>();

 static Collection<IUserEntity> getUsers(){
   return staticUserEntityMap.values();
 }
}

Okay Thanks, I think it's a better structure idea then. – Maxime Gajovski Dec 26 '15 at 14:16 — Maxime Gajovski, Dec 26 '15 at 14:16
There's no way to let the staticMap protected or private ? – Maxime Gajovski Dec 26 '15 at 14:19 — Maxime Gajovski, Dec 26 '15 at 14:19

score 0 · Answer 3 · answered Dec 26 '15 at 13:42

0

you can create abstract SkeletonUserEntity(or AbstractUserEntity) class where you would define this getUser method and all another general methods. All classes have to implemeent IUserEntity you extends from SkeletonUserEntity

answered Dec 26 '15 at 13:42

Serhii Soboliev

820
1
13
21

Static methods and interfaces in Java

3 Answers3