[
https://issues.apache.org/jira/browse/ISIS-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood resolved ISIS-59.
-----------------------------
Resolution: Fixed
Fix Version/s: 0.1.0-incubating
Assignee: Dan Haywood
Further work on combining these hierarchies:
- ObjectMemberPeer is now called FacetMethod
- ObjectActionParamPeer is now called FacetMethodParameter
I think we've gone as far as we can go on this; although we still have two sets
of classes, their responsibilities are more clear:
- FacetedMethod is basically a java.lang.reflect.Method + FacetHolder +
featureType
- the OneToOneAssociation / OneToManyAssociation / ObjectActionImpl all "wrap"
an underlying FacetedMethod, and provide additional methods to interact with it.
Also, both share a FeatureType enum (powertype) which distinguishes properties
vs collections vs actions vs action params. This enum is also used to drive
which FacetFactories apply to which levels, so also defines an object.
> Combine the ObjectMember and ObjectMemberPeer hierarchies.
> ----------------------------------------------------------
>
> Key: ISIS-59
> URL: https://issues.apache.org/jira/browse/ISIS-59
> Project: Isis
> Issue Type: Improvement
> Components: Core: MetaModel
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: 0.1.0-incubating
>
>
> The reason for these being separated out is historical. The FacetFactory
> design now gives us everything that this earlier design gave us, so we should
> merge the two hierarchies back together.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
