I think we have 2 scenarios as configured:
1. @Action is mandatory ... then we could allow disable/hide/... prefixes on actions (no need for the validator to discard these cases)
2. @Action is optional ... then we need to preserve the original behavior as you suggested
I have reinstated that code, though something else must have changed because I couldn't reproduce scenario (2) to trigger the "orphaned methods" validation error.
But scenario (1) works fine.
For our own apps, I intend to make @Action mandatory, as per isis.reflector.validator.explication-annotations.action=true
ok, we gonna need to write test cases to check this then
I'll add a ticket
- links to