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/03/31 22:16:25 UTC
[jira] [Updated] (DELTASPIKE-1070) Refactor RepositoryComponent/s
[ https://issues.apache.org/jira/browse/DELTASPIKE-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Andraschko updated DELTASPIKE-1070:
------------------------------------------
Fix Version/s: (was: 1.6.0)
1.7.0
> Refactor RepositoryComponent/s
> ------------------------------
>
> Key: DELTASPIKE-1070
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1070
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Data-Module
> Reporter: Thomas Andraschko
> Assignee: Thomas Andraschko
> Fix For: 1.7.0
>
>
> Currently a RepositoryComponent is initialized during PAT. Therefore RepositoryComponent requires a lazyInit.
> If we move the actual creation of the RepositoryComponent's to AfterBeanDiscovery, we don't need such lazy init "hacks".
> IMO we should also split the RepositoryComponent into a data object and a initializer as it currently feels very unstructured.
> Same applies for the RepositoryMethod and RepositoryEntity.
> We could also allign the naming a little bit:
> RepositoryComponents -> something MetadataStore or MetadataManager
> RepositoryComponent -> RepositoryMetadata
> RepositoryMethod -> RepositoryMethodMetadata
> RepositoryEntity -> EntityMetadata
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)