[
https://issues.apache.org/jira/browse/ISIS-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935809#comment-16935809
]
ASF subversion and git services commented on ISIS-2161:
-------------------------------------------------------
Commit 89b49816894a1a92f12259215c3fb97e974b180c in isis's branch refs/heads/v2
from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=89b4981 ]
ISIS-2161: adds a new annotation: Model
- new validation: SupportingMethodValidatorRefinerFactory
- replaces validation via MethodPrefixBasedFacetFactoryAbstract
> Remove domain-object member naming restrictions (reserved prefixes)
> -------------------------------------------------------------------
>
> Key: ISIS-2161
> URL: https://issues.apache.org/jira/browse/ISIS-2161
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0
>
>
> Currently the prefixes 'hide', 'validate', 'disable', etc are reserved for
> supporting-methods and may not be used for Actions and Properties.
> We can lift this restriction:
> * If a member is annotated Action/Property/Collection, then we allow any
> names for this member, even if these collide with the 'reserved' prefixes!
> It is inconvenient, when misspelling support-methods eg. using 'verify'
> instead of 'validate', that one has to troubleshoot the application later,
> only to find out that one made a sloppy mistake.
> * We can improve on this by introducing a new annotation eg. 'Model' to
> enforce a meta-model check on the correct naming of supporting-methods.
> {code:java}
> @Action
> void placeOrder(X x, Y y, Z z) {...}
> @Model // <-- enforces a meta-model check on this supporting-method
> boolean hidePlaceOrder() {...}
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
