Just for clarification.
An indicator that we need to enhance the meta model would be when one adapter (ie the UI viewer) needs information about other adapter to properly function (such as the validation rules or the ORM annotations). El 08/09/2013, a las 11:37, GESCONSULTOR - Óscar Bou <[email protected]> escribió: > > I must admit that was one of our expectations when we firstly approximated > Isis, perhaps because we were following the email list or saw the SQL > Objectstore, etc. > > In fact, seems that recently we have taken the opposite path (by requiring > nearly all Entity properties to be annotated with > @Column(allowsTrue="true|false"), instead of improving the JDO Object Store > usage of the Isis meta-model. > > It would also have another advantage: it would be the way to also support JPA > implementations (or lessen the effort required). > > But we cannot expected to map/solve all ORM requirements on the Isis > metamodel, so the end situation will be some inferred, some explicited for > sure. > > > I think that perhaps we must clarify Apache Isis responsibilities, and > concentrate on them. > So let me do a "quick-and-dirty" Envisionning exercise (it's Sunday...). > > > > VISION STATEMENT: > Apache Isis intend to provide programmers with the best framework for > implementing Domain-Driven Applications that interact with its environment > without compromising business logic. > > For that, I would say (for debating) the following (quick) responsibilities: > - The core responsibilities are: > 1. to ease on Domain implementation (Entities, their relationships, and > behavior / business rules / actions). > 2. to ease on Domain interaction with the environment (establishing ways to > securely "share" that Domain Rules with the environment - applications or > humans -). > 3. to ease on Business Logic "protection" against "business-logic thieves > such as UIs and ORMs" (by having all "contextual" info needed for the domain, > and also for the actors interacting with the Domain).
