Daniel Keir Haywood created CAUSEWAY-3470:
---------------------------------------------
Summary: Shouldn't contribute actions to mixin object s... cause
new metamodel validation to fail
Key: CAUSEWAY-3470
URL: https://issues.apache.org/jira/browse/CAUSEWAY-3470
Project: Causeway
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0-RC1
Reporter: Daniel Keir Haywood
Fix For: 2.0.0-RC2
For example, if include the commandlog module, this has a mixin
Object_recentCommands, which (of course) is intended to be contributed to all
objects.
It turns out that it is _also_ (seemingly) contributed to mixin objects, which
doesn't make much sense, but there you go.
And then, with the new metamodel validation that requires that a mixin's action
method matches that declared (typically "act"), we find that the _contributed_
action's method - ie "recentCommands" - falls foul of this.
I don't think that the metamodel validation is at fault (though it might be
useful to be able to disable) ... but it's clearly pretty weird for us to
contribute actions to mixins.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
