Alternatives to static methods on interfaces for enforcing consistency

Question

In Java, I\'d like to be able to define marker interfaces, that forced implementations to provide static methods. For example, for simple text-serialization/deserialization

Answer 1

Just a different idea. Not applicable for all cases, but maybe help someone else.

You can use an abstract class, as bridge between your interface and your concrete classes. Abstract classes allows static methods as well contract methods definitions. As example, you can check out Collection API, where Sun implemented several abstract classes, instead of brute force coding from zero all concrete classes.

In some cases, you can just replace interfaces by abstract classes.

Answer 2

Just an idea to consider: You can separate the transformation logic from the objects themselves, and then you have a fixed set of transformers, implementing the following interface :

public interface Transformer<T>{ 

  public T fromText(String text); 

  public String toText(T obj); 
}

Your actual data classes can have a method getTransformer() that returns the right transformer for them.

Answer 3

A totally different approach (and an ugly hack, for that matter) is to let the interface have a method that returns a method.

public interface MyInterface{
    Method getConvertMethod();
}

now your client code can do

yourInterface.getConvertMethod().invoke(objectToBeConverted);

This is extremely powerful, but very bad API design

Sean

Answer 4

If you are running in Java 5 or higher, you can use the enum type - all of those are, by definition, singletons. So you could something like:

public enum MyEnumType {
    Type1,
    Type2,
    //....
    TypeN;

    //you can do whatever you want down here
    //including implementing interfaces that the enum conforms to.

}

This way the memory problem goes away, and you can have single instances of behavior implemented.

---

Edit: If you don't have access to enums (1.4 or earlier) or, for some other reason, they don't work for you, I would recommend a Flyweight pattern implementation.

Answer 5

As @aperkins said, you should use enums.

The enum base class, Enum, provides a valueOf method that will convert a string to an instance.

enum MyEnum { A, B, C; }
// Here's your toText
String strVal = MyEnum.A.getName();
// and here's your fromText
MyEnum value = MyEnum.valueOf(MyEnum.class, strVal);

Update: For the ones that are enums, this might do what you need. It uses reflection, so you only need to implement EnumHelper on enums where you have to deal with legacy values.

/** Enums can implement this to provide a method for resolving a string
  * to a proper enum name.
  */
public interface EnumHelp
{
    // Resolve s to a proper enum name that can be processed by Enum.valueOf
    String resolve(String s);
}

/** EnumParser provides methods for resolving symbolic names to enum instances.
  * If the enum in question implements EnumHelp, then the resolve method is
  * called to resolve the token to a proper enum name before calling valueOf.
  */
public class EnumParser
{
    public static <T extends Enum<T>> T fromText(Class<T> cl, String s) {
        if (EnumHelp.class.isAssignableFrom(cl)) {
            try {
                Method resolve = cl.getMethod("resolve", String.class);
                s = (String) resolve.invoke(null, s);
            }
            catch (NoSuchMethodException ex) {}
            catch (SecurityException ex) {}
            catch(IllegalAccessException ex) {}
            catch(IllegalArgumentException ex) {}
            catch(InvocationTargetException ex) {}
        }
        return T.valueOf(cl, s);
    }

    public <T extends Enum<T>> String toText(T value)
    {
        return value.name();
    }
}

Answer 6

This is really appropriate for the Flyweight. That is basically what you are trying to accomplish with the statics. In terms of how to serve the Flyweight object so that you don't create thousands of them, here are some ideas.

One is the factory, which you state you thought about and rejected, although you didn't state why (so any other ideas may suffer from the same problem) so I won't go into it.

Another is to have the value type have a method which can serve its converter. Something like this:

 public class ValueType {
       public static final TextTransformable<ValueType> CONVERT = ....
 }

And then use it like this:

 ValueType value = ValueType.CONVERT.fromText(text);

 String text = ValueType.CONVERT.toText(value);

Now that doesn't enforce that all ValueType's provide their converters via the same mechanism, for that I think you need a factory of some kind.

Edit: I guess I don't know what you find inelegant about a factory, but I think you are focused on callers, so how does this feel to you:

  ValueType value = getTransformer(ValueType.class).fromText(text);

The above can be done with a static import of the factory and a method that has a signature like so:

   public static <T> TextTransformable<T> getTransformer(Class<T> type) {
         ...
   }

The code to find the right transformer isn't necessarily the prettiest, but from the callers perspective everything is nicely presented.

Edit 2: Thinking about this further, what I see is that you want to control object construction. You can't really do that. In other words, in Java you can't force an implementer to use or not use a factory to create their object. They can always expose a public constructor. I think your problem is that you aren't happy with the mechanisms for enforcing construction. If that understanding is right, then the following pattern may be of use.

You create an object with only private constructors which wraps your value type. The object may have a generic type parameter to know what value type it wraps. This object is instantiated with a static factory method which takes a factory interface to create the "real" value object. All framework code that uses the object only takes this object as a parameter. It does not accept the value type directly, and that object cannot be instantiated without a factory for the value type.

The problem with this approach is that it is quite restricting. There is only one way to create objects (those supported by the factory interface) and there is limited ability to use the value objects, as the code processing these text elements has limited interaction only through this object.

I guess they say there isn't a software problem that can't be solved via an extra layer of indirection, but this may be a bridge too far. At least its food for thought.