Accepted answer

ignore it. eclipse is a jerk. you can tone it by setting window > preferences > web > javaserver faces tools > validation > type assignment problems > method expression signature incompatibility to warning or ignore (it defaults to error).

enter image description here

image borrowed from this blog in all courtesy.

the reason is, eclipse expect the action attribute to always return string, not void. whilst indeed unspecified in jsf action attribute, the el method expressions themselves actually also support void methods. the overzealous message in turn suggests that the underlying logic responsible for this validation is incapable of determining the individual method arguments and thus it tries to compare the raw method signature against a collection of allowed signatures, which ultimately get shown in the message if no match was found. based on the message, this problem may also disappear when the method has 20 or more arguments ;)

this is fixed in eclipse luna sr1, nearly 6 years after the issue was reported. the severity has been decreased from error to warning. you may still want to put it yet lower to ignore.

see also:

Related Query

More Query from same tag