[
https://issues.apache.org/jira/browse/ZEST-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055451#comment-15055451
]
Kent Sølvsten commented on ZEST-132:
------------------------------------
There are 2 motivations for this:
* More consistent semantics are much easier to document and comprehend - and
users will have an easier task 'guessing' the semantics regarding
not-yet-developed persistent features, like messages or improved-eventstore.
* By using the model-is-king approach consistently, we should be able to
implement a larger part of the persistence mechanism as services - opening up
for more pluggability.
> Improve Indexing/Query Semantics
> --------------------------------
>
> Key: ZEST-132
> URL: https://issues.apache.org/jira/browse/ZEST-132
> Project: Zest
> Issue Type: Bug
> Reporter: Kent Sølvsten
> Fix For: 3.0
>
>
> The current Indexer/Query semantics are not consistent with the EntityStore
> semantics and needs to be fixed.
> I can query for an existing entity, IF i can see it's model, AND
> i can see an indexer, AND the entitystore in which the entity is
> persisted can see the same indexer.
> For the EntityStore case, I can get an existing entity if and only if i can
> see it's model (according to visibility rules).
> The latter should be the case for Query as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
