You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@eagle.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2018/02/01 10:01:00 UTC

[jira] [Updated] (EAGLE-487) use guice module better in app framework

     [ https://issues.apache.org/jira/browse/EAGLE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh updated EAGLE-487:
--------------------------------------
    Fix Version/s:     (was: v0.5.1)
                   v0.5.0

> use guice module better in app framework
> ----------------------------------------
>
>                 Key: EAGLE-487
>                 URL: https://issues.apache.org/jira/browse/EAGLE-487
>             Project: Eagle
>          Issue Type: Improvement
>    Affects Versions: v0.5.0
>            Reporter: Edward Zhang
>            Assignee: Edward Zhang
>            Priority: Major
>             Fix For: v0.5.0
>
>
> There are multiple issues with using guice module in app framework.
> 1. ApplicationProviderServiceImpl is instantiated twice
> 2. the interface between application and eagle server is not clear. It is not correct to only let application to register submodules,, instead it should includes some state inherited from eagle server, for example metadata storage type.
> 3. not necessary to use module scope, it is pretty over-engineering when application only want to register some module.
> 4. MemoryMetadataStore should use singleton



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)