I have made omega design for this issue[1], please feel free to give me some advice.
[1] https://cwiki.apache.org/confluence/display/SERVICECOMB/refactor+design+of+service-comb+pack+omega ------------------ Zhao Jun Apache Sharding-Sphere & ServiceComb > On Jan 14, 2019, at 5:27 PM, zhaojun <zhaoju...@126.com> wrote: > > I have created SCB-1113[1] to track this issue. > > [1] https://issues.apache.org/jira/browse/SCB-1113 > > ------------------ > Zhao Jun > Apache Sharding-Sphere & ServiceComb > >> On Jan 14, 2019, at 5:21 PM, zhaojun <zhaoju...@126.com> wrote: >> >> OK, let me create a JIRA, and try to refactor it >> >> ------------------ >> Zhao Jun >> Apache Sharding-Sphere & ServiceComb >> >> >>> On Jan 14, 2019, at 4:50 PM, Willem Jiang <willem.ji...@gmail.com> wrote: >>> >>> Yeah, we just need to think about starting the Omega context by wiring >>> the components through Spring API, then wrap it with Spring Boot >>> Starter API. >>> In this way we could support to inject the Omega context not only to >>> the Spring Boot Application but also Spring Application. >>> >>> Willem Jiang >>> >>> Twitter: willemjiang >>> Weibo: 姜宁willem >>> >>> On Mon, Jan 14, 2019 at 3:09 PM zhaojun <zhaoju...@126.com> wrote: >>>> >>>> Hi, all >>>> >>>> I think we should provide api way to bootstrap omega and alpha. >>>> Now our code was tightly coupled with spring-boot, it is not possible for >>>> integrated with other middleware. >>>> We should provide Omega.init(), Alpha.init() api, spring-boot was just one >>>> implementation for Pack. >>>> >>>> Any thought? >>>> >>>> ------------------ >>>> Zhao Jun >>>> Apache Sharding-Sphere & ServiceComb >>>> >> >
