You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Thomas Andraschko (JIRA)" <ji...@apache.org> on 2016/06/07 15:56:21 UTC
[jira] [Commented] (DELTASPIKE-1169) Separate concerns of
EntityRepository
[ https://issues.apache.org/jira/browse/DELTASPIKE-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318739#comment-15318739 ]
Thomas Andraschko commented on DELTASPIKE-1169:
-----------------------------------------------
Would be great if you would provide a prototype branch/patch - not sure how it will look like and if it's worth to add a new interface for 2-3 methods.
> Separate concerns of EntityRepository
> -------------------------------------
>
> Key: DELTASPIKE-1169
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1169
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Data-Module
> Affects Versions: 1.6.1
> Reporter: John D. Ament
> Assignee: John D. Ament
> Fix For: 1.7.0
>
>
> The current EntityRepository interface is good, but makes some extensions inflexible.
> https://github.com/apache/deltaspike/blob/master/deltaspike/modules/data/api/src/main/java/org/apache/deltaspike/data/api/EntityRepository.java#L34
> There are three categories of methods:
> - Wrappers for low level persistence APIs.
> - Searches
> - Counts
> These three concerns should be broken out into their own interfaces, which {{EntityRepository}} can then extend. This would allow users to leverage persistence and Streaming, without needing to bring in everything.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)