[ https://issues.apache.org/jira/browse/DELTASPIKE-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036121#comment-16036121 ]
ASF subversion and git services commented on DELTASPIKE-1070: ------------------------------------------------------------- Commit 46a3b6759fabb55fd2b913b9f7b4635687d0c5d7 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=46a3b67 ] DELTASPIKE-1070 Refactor RepositoryComponent/s > 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.8.1 > > > 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.15#6346)