Java – using dependency injection in Libraries

I am writing a Java library that will be used by existing applications I'm using dependency injection, so testing is easier. I'm familiar with spring, so I plan to use it to manage dependency injection during testing The application that will eventually use the library is not spring based, but it does not currently use any IOC / di container of any type My question is, what is the best way to inject dependencies without using spring or Guice? Should I consider instantiating and connecting objects like factory methods? Dependencies are in the library, so it seems inappropriate for an application to instantiate each dependency to create a master object

Solution

If your library is written in di friendly idioms It should be fairly easy to use as a straitforward Java API Think about your past spring experience There are several libraries that exactly match the spring model, but they were written before spring I didn't see any bad new heels of several setXX, and then called the real work method. Just be careful because, among other things, your client may forget to call the thouse init methods, which are called reliably

Let the client application decide You are providing a library Let API clients connect to their own objects for instance. Later, you can use the same example to create factory methods on the client's domain Perhaps the client application has its own configuration method, and if the API provided by your library is flexible enough, you can take advantage of it

Maybe you can include Guice The license is Apache Just like the whole Java itself