One way to implement enum-constant specific behavior is to have the enum class declare an abstract method and then to have each specialized enum constant override the class (specialized enum constants are implemented as anonymous subclasses of the enum class).  Although the method is declared abstract in the enum, it is effectively not abstract since javac ensures that each enum constant provides a concrete implementation of the method.  Therefore, in this situation the generated javadoc should not list the "abstract" modifier on the method.

  xxxxx@xxxxx   2005-06-17 23:29:29 GMT

N/A

  xxxxx@xxxxx  :

This is an issue for the doclet.  We should verify (perhaps Joe has
given this more thought) that the "abstract" is truly not part of the
specification, that it isn't checked by the JCK, etc.  Doing this would
be a bigger step than eliding optional "noise" keywords like the "public"
on an interface member.  It's closer in scope to what we do in 
StringBuffer and StringBuilder to hide all reference to the 
AbstractStringBuilder methods.

  xxxxx@xxxxx  :
I asked Joe about this, and he's convinced me that it's the right
thing to do.

(pasted by Doug from email)
  xxxxx@xxxxx   2005-07-19 17:20:44 GMT