GithubHelp home page GithubHelp logo

Issue-Import-Test about rico HOT 5 CLOSED

rico-projects avatar rico-projects commented on July 18, 2024
Issue-Import-Test

from rico.

Comments (5)

hendrikebbers avatar hendrikebbers commented on July 18, 2024

Comment by hendrikebbers
Wednesday Feb 17, 2016 at 23:47 GMT

@aalmiray Is this issue still relevant?
I think that we could use @Inject at the controller constructors now (never tried it). What would not work is using the model (@dolphinmodel) as a injectable constructor param. This is more or less related to CDI (would work in Spring).

from rico.

hendrikebbers avatar hendrikebbers commented on July 18, 2024

Comment by aalmiray
Thursday Feb 18, 2016 at 08:19 GMT

Very much relevant. I'd like to see an API that's friendly to DI. This doesn't mean core DP classes must be annotated with @Inject for this to work, however it wouldn't hurt, given that classes can still be instantiated in a non-DI environment even if their constructor are annotated with @Inject.

from rico.

hendrikebbers avatar hendrikebbers commented on July 18, 2024

Comment by hendrikebbers
Friday Mar 11, 2016 at 10:49 GMT

@aalmiray I think we should close this issue and maybe open more specific ones. Since this issue was opened we defined several factories and more will comme (see Pull Requests for server refactoring). Based on this I think that we should not have a general "provide factories" issue anymore. I think it would be better to create a specific issue if you are missing a factory.
About the DI support: For this we can create a separate issue. Here my idea is to private an implementation of DP server that simply runs in a tomcat. Here the controllers will be created "by hand" or with the help of a DI framework like Guice. I think the current code is well prepared for such a third implementation next to Spring and JavaEE.

from rico.

hendrikebbers avatar hendrikebbers commented on July 18, 2024

Comment by aalmiray
Friday Mar 11, 2016 at 10:53 GMT

Well, this issue already discusses the usage of @Inject. It mentions a factory to exemplify why the use of DI would be a good idea. I don't see the need to close this issue and open another one.

from rico.

hendrikebbers avatar hendrikebbers commented on July 18, 2024

Comment by hendrikebbers
Friday Mar 11, 2016 at 10:56 GMT

ok, then just link this one with #42 that contains the need of factories. This issue will then define the need for low level DI. Ok

from rico.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.