On Wed, Dec 5, 2018 at 4:37 AM Yasser Zamani <yasserzam...@apache.org> wrote:
> I found dagger2 best when there are limited resources and we need an > urgent performance e.g. in mobile devices. But Struts unfortunately is not > able to be used in mobile app developments so we can postpone dagger 2 to > when Struts will be able. > Dagger seems to be cross-platform; no reason it couldn't be used in a POJ project, but as you say, it seems a replacement for, not an adjunct to, existing DI engines. We could consider using it for internal injection rather than the original Guice, and allowing users to use it, but... I don't know. Would have to think about that and spin some PoCs. I don't see any reason to (or even a reasonable ability to) target S2 at mobile. > @dev wdyt? I thought what about add integration with front-end trends e.g. > React, Angular, Vu.js, Node.js? NodeJS isn't really front-end. I don't know what would be added to S2 to "integrate" it into a front end; it already does JSON reasonably well-ish. Web socket support would be about the only thing "missing" in this regard. > and improve Struts internals with concept trends e.g. microservices, DIs > and etc? IMO w/o some major gutting S2 won't be a (good) microservice framework. uSvcs are more single-function endpoints, while S2 is meant for a collection of endpoints. We could consider Java-based config (again/still) and but I'm not 100% sure what that buys the framework overall. I should poke around a bit in the Java world again and re-familiarize myself with some S2 internals before saying too much, though :/ Dave
