An advanced DI framework for JVM and Android applications based on the Java Reflection API with a specialized implementation for jMonkeyEngine Applications. Jector provides a programming concurrent (order-parallelism/sync) model for best practices by injecting functions' stacks into schedulable tasks, and in turn into their designated threads. Threads can be activated and controlled to achieve either parallelism or synchronicity.

┌─[pavl-machine@pavl-machine]─[/home/twisted/GradleProjects/Jector]
└──╼ $./gradlew :jector:build && \
      ./gradlew :jector:generateSourcesJar && \
      ./gradlew :jector:generateJavadocJar && \
      ./gradlew :jector-monkey build && \
      ./gradlew :jector-monkey generateSourcesJar && \
      ./gradlew :jector-monkey generateJavadocJar

┌─[pavl-machine@pavl-machine]─[/home/twisted/GradleProjects/Jector]
└──╼ $./gradlew :jector-examples:run

• build.gradle:

repositories {
    mavenCentral()
}
dependencies {
    implementation "io.github.software-hardware-codesign:jector:1.0.0-pre-alpha"
    implementation "io.github.software-hardware-codesign:jector-monkey:1.0.0-pre-alpha"
    implementation "org.jmonkeyengine:jme3-core:3.6.1-stable"
    implementation "org.jmonkeyengine:jme3-desktop:3.6.1-stable"
    implementation "org.jmonkeyengine:jme3-lwjgl3:3.6.1-stable"
}

• Jector Dependencies are Functional Java Worker methods tasked in a TaskExecutor instance.
• Multi-threaded async dependency tasking.
• Single-threaded dependency tasking.
• Non-threaded tasking.
• Supports dependency arguments.
• Supports dependency return objects to the caller (the parent task executor).
• Supports OO Polymorphism over the Worker classes (need to add all the workers statically to the TaskExecutorManager).
• Supports Android and jMonkeyEngine Applications.

1. Dependencies are defined by some Method objects as WorkerTasks.
2. Dependencies created from Worker Method objects only.
3. Dependencies are bound to their Executors (threads, states, ...) interfaces via WorkerTasks (which enclose those low-level worker Methods).
4. Dependencies could be only instantiated from Worker Methods (annotated methods inside Worker classes).
5. A Worker interface is a marker interface for the Jector Framework.
6. A Worker implementation signifies a runtime environment for the DI actions.
7. A TaskExecutorManager implementation has a Worker instance and is the injector object that creates WorkerTasks from Worker Methods and injects them into annotated TaskExecutors.
8. A TaskExecutor implementation is a wrapper to a collection of WorkerTasks to be executed, TaskExecutor could be a State, a Thread, a Server Container,...etc.