Mailing-List: contact dev-help@zest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zest.apache.org
Date: Thu, 17 Dec 2015 12:36:46 +0000 (UTC)
From: "Niclas Hedhman (JIRA)" <jira@apache.org>
To: dev@zest.apache.org
Message-ID: <JIRA.12922696.1450355753000.53643.1450355806617@Atlassian.JIRA>
In-Reply-To: <JIRA.12922696.1450355753000@Atlassian.JIRA>
References: <JIRA.12922696.1450355753000@Atlassian.JIRA>
 <JIRA.12922696.1450355753375@arcas>
Subject: [jira] [Created] (ZEST-136) Refactoring of Models and Instances in
 Runtim
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Niclas Hedhman created ZEST-136:
-----------------------------------

             Summary: Refactoring of Models and Instances in Runtim
                 Key: ZEST-136
                 URL: https://issues.apache.org/jira/browse/ZEST-136
             Project: Zest
          Issue Type: Improvement
            Reporter: Niclas Hedhman
            Assignee: Niclas Hedhman
             Fix For: 3.0


The separation between Model and Instance for Application/Layer/Module is very poor, as everything has ended up in the Instance (mostly ModuleInstance). 
But also similar, but to much lesser degree, situation exist in Composite Models and Instances, for instance the Instance references the Module Instance, although that is totally fine to be in the Model and should reference the Module Model.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)