[
https://issues.apache.org/jira/browse/DELTASPIKE-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036217#comment-16036217
]
ASF subversion and git services commented on DELTASPIKE-1070:
-------------------------------------------------------------
Commit 96c6ba2af7a16368c66a8326e0a474e9d1ded2c0 in deltaspike's branch
refs/heads/master from [~tandraschko]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=96c6ba2 ]
DELTASPIKE-1070 removed unused class
> 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)
