Enums with different methods, useful or abuse?
My answer to your main question is you gotta do what you gotta do. Just so you feel more comfortable; this pattern has a name strategy enum. It is even in Effective Java.

But I have a criticism for this bit:

    public static final TextType[] useCase1 = {text1, text2};


Arrays are mutable. You should not implement class constants as final arrays. Use unmodifiable collections instead:

    public static final List&lt;TextType&gt; useCase1 = Collections.unmodifiableList(
         Arrays.asList(text1, text2));


Also each time you add another use case you should not need to modify this enum, that is by adding another useCase. Those should be moved to wherever they are used.