CODEWITHSUNDEEP
javaspringspring-mvcdependency-injectionspring-data-jpa
David Moreno García
David Moreno García

Reputation: 4523

Java based dependency injection in Spring

I'm working in a webapp and this is the first time that I'm using Java based configuration. I have a bunch of class to configure all:

Now I'm defining Spring Data repositories and the service layer so I need to inject the repositories there. Normally I would use Autowired but I've read that it is preferable to define the injections manually so the question is, where?

Maybe neither of the previous configuration classes is suitable for such task but, do I have to create a single class to define all the injections or is better to have on for each function? What happens if the project grows too much?

I think that the main question would be what is best way to organize dependencies in a Spring project. What do you do?

I add here an image of the structure of the project as a petition. I'm trying to decouple layers and now I need to inject UserRepository to UserService.

enter image description here

Upvotes: 0

Views: 182

Answers (2)

superbAfterSemperPhi
superbAfterSemperPhi

Reputation: 1292

The article said that he recommends using XML configuration for large projects. This is a very small project at this point. It seems to me that auto wiring with annotations would be fine even by the article's author's words.

Upvotes: 0

duffymo
duffymo

Reputation: 308733

No, I would not define a single class to do all the injections. All your classes are coupled that way.

I don't understand what "define the injections manually" means. You have to specify them in either XML or annotations. There's no other way that I know of.

You don't say if you're using XML or annotation configuration. I find myself using the latter more of the time, with only enough XML configuration to tell the Spring app context to scan for annotations.

The Spring idiom would have you specify your configuration in layers if you're using XML. It's a moot point for annotations, because they go into your source code.

Your application will read the Spring context on start up, instantiate all the beans, and wire together the necessary dependencies. You're good to go from then on.

I disagree with the link you provided. Avoid autowiring? No.

Upvotes: 2

Related Questions