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/04/09 16:07:05 UTC

[jira] [Closed] (ISIS-62) Split out RuntimeContext into separate sub-interfaces, for testability and understanding (ie, the interface separation principle).

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

Dan Haywood closed ISIS-62.
---------------------------


> Split out RuntimeContext into separate sub-interfaces, for testability and understanding (ie, the interface separation principle).
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-62
>                 URL: https://issues.apache.org/jira/browse/ISIS-62
>             Project: Isis
>          Issue Type: Improvement
>          Components: Core: MetaModel
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>             Fix For: 0.1.2-incubating
>
>
> The org.apache.isis.core.metamodel.runtimecontext.RuntimeContext interface is used to decouple the metamodel from the runtime implementations.
> There are a lot of methods in this interface, and it is passed into multiple classes within the metamodel.  This makes it hard to understand which methods are used by which classes.
> This issue is to split the interface out so that dependencies are narrower (interface separation principle).  This should make it easier to write tests, and the codebase easier to understand (I hope).
> This principally impacts the metamodel, but also the progmodel.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira