You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2011/01/07 00:20:46 UTC

[jira] Resolved: (ISIS-68) Combine JavaSpecification and JavaIntrospector, and make the mechanism for ordering members more explicit.

     [ https://issues.apache.org/jira/browse/ISIS-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood resolved ISIS-68.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 0.1.0-incubating

This was addressed alongside changes for ISIS-64 and ISIS-65.

> Combine JavaSpecification and JavaIntrospector, and make the mechanism for ordering members more explicit.
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-68
>                 URL: https://issues.apache.org/jira/browse/ISIS-68
>             Project: Isis
>          Issue Type: Improvement
>          Components: Core: MetaModel
>            Reporter: Dan Haywood
>            Priority: Minor
>             Fix For: 0.1.0-incubating
>
>
> There is no real separation of responsibilities between JavaSpecification and JavaIntrospector... the responsibility for introspecting is really a responsibility of the FacetFactories that make up the programming model in action.  These two classes should therefore be combined.
> In addition, the JavaIntrospector currently takes responsibility for applying the ordering of members.  In the future we might want to make this a "post-processing" operation, in effect overlaying a UI "schema" for the layout of object members.  (The MetaWidget library does something like this, to good effect).
> As a first step, we should make clear the raw set of associations/actions; and then make clear the transformation of these sets into ordered/laid out sets.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.