I partially solved my problem doing this ``` bin...

# kodein

[leosan]

I partially solved my problem doing this

bind<Job>(MyJob.TAG) with singleton { MyJob(instance()) }
bind<Job>(MyJob2.TAG) with singleton { MyJob2() }

class JobCreator(private val kodein: Kodein) : JobCreator {
    override fun create(tag: String): Job? {
        return kodein.instance(tag)
    }
}

But I wonder if there’s a way to create this dependency in a transitive way without passing the kodein instance to the job creator…

[Andreas Sinz]

@leosan Are you trying to retrieve the right job from your JobCreator based on a TAG?

[leosan]

yes

[Andreas Sinz]

you can try bind<Job> with factory { tag: String -> kodein.instance<JobCreator>().create(tag) } with kodein.instance<JobCreator>(MyJob.TAG)?

[leosan]

hmm I don’t control the tag passed to the onCreate(tag) it’s handled by the library

[leosan]

I mean I give the Job a tag but the create method is called internally

[Andreas Sinz]

@leosan internally from where?

[leosan]

evernote-job library

[leosan]

basically I have

JobManager.create(this).addJobCreator(MyJobCreator())
class MyJobCreator : JobCreator
class MyJob : Job

So whenever a create a Job the JobManager will call the create as I passed the MyJobCreator to it.

[Andreas Sinz]

and why do you want to bind the jobs then?

[leosan]

yes, at the moment I have

bind<JobCreator>() with singleton { MyJobCreator(this) }
and singletons bindings for different jobs

[leosan]

and my Application extends KodeinAware
so initialize the `JobManager `like this

JobManager.create(this).addJobCreator(instance())
JobManager.instance()

[Andreas Sinz]

yes, but why do you need to bind the different jobs? evernote-job gets your jobs directly from your MyJobCreator

[leosan]

because I’m also passing dependencies to these jobs

[leosan]

the evernote-job will cal the on create but I have to create the instance by myself

[leosan]

without DI is something like this

[leosan]

class MyJobCreator : JobCreator {
    override fun create(tag: String): Job? {
        return when (tag) {
            MyJob1.TAG -> MyJob()
            else -> null
        }
    }
}

[leosan]

I don’t want to instantiate these dependencies on my JobCreator

[Andreas Sinz]

well, your JobCreator must provide the Job and therefore you can either pass in all possible jobs as constructor parameters class MyJobConstructor(val job1: MyJob, val job2: MyJob2) or you give JobCreator an instance of Kodein and it retrieves the instance itself

[leosan]

hmm so what I did passing the kodein instance is right then… good to know 😮

[leosan]

I thought it would be wrong give the Kodein instance to it, but now you saying makes sense

[Andreas Sinz]

the way evernote-job is designed, there is no other way to do it. If you'd use constructor parameters and you have like 20 different jobs it gets messy pretty fast

[Andreas Sinz]

well, you could also create a JobCreator per Job