EnumMap with interfaces

Question

I have bunches of Enums that I want to have a common behavior, so I created an interface, and implement that in each enum:
interface Z {
    int doStuff();
enum X implements Z {
    A, B, C;
    int doStuff(){ ... }
}Now I want to use an EnumMap with keys consisting of enums implementing Z:
MyClass c = ...
EnumMap <Z, MyClass> map = new EnumMap <Z, MyClass>( Z.class );
for ( Z z : X.values()){
    map.put( x, c );
}The compiler does not like the declaration (among other things). If I replace the declaration with:
EnumMap <? extends Z, MyClass> map = new EnumMap <Z, MyClass>( Z.class );then it likes the declaration to the left of the "=", but not the rest.
What am I doing wrong? Note that if I replace the EnumMap declaration with:
HashMap <Z, MyClass> map = new HashMap <Z, MyClass>();Then everything works, but would like to use EnumMap. If I declare:
EnumMap map = new EnumMap( Z.class );then I have to do some casting, and also get unchecked warnings.

Answer 1

Thanks for the response! In my example, I'm only putting enums from one enum class in there; in fact, I thought the whole purpose of having to pass a class object for the Enum to the constructor, was to identify the class.
Oh, well, if it wasn't meant to work, I'll go back to the HashMap.
Another question: Along the same vein, I have the following "awful" utility routine:
    public static Enum getEnum( Object[] enums, String string ){
         return Enum.valueOf( ((Enum) enums[ 0 ]).getClass(), string );
    }I have many groups of enums that are identified by name in external data. When I read the external data, I need to identify them with the actual enum element. The valueOf() method is of course perfect for this. Unfortunately, all I have in the routine that reads the data, is the array of values; eg, X.values() (from my enum X in my original message) is passed in.
The above code works perfectly (and even throws the appropriate exception when there is no match), but gives another unchecked conversion message. Any ideas as to how to get rid of the message? Subclassing each enum to have a lookup() method that just maps to valueOf() would probably work, but it's clumsy and not really practical with about a hundred enum declarations.
I thought the whole point of casting in Java was to in effect say, "Check this at run-time; I know what I'm doing."