Basic proof of concept implementation of the IoC container.

This project is distributed via JitPack. Register a JitPack repository at your pom.xml:

<repositories>
    <repository>
        <id>jitpack.io</id>
        <url>https://jitpack.io</url>
    </repository>
</repositories>

And add the following dependency:

<dependency>
    <groupId>com.github.jolice</groupId>
    <artifactId>Grape</artifactId>
    <version>v1.0</version>
</dependency>

Grape grape = new Grape(new GrapeConfiguration()
                        .scan("your.packages.to.scan")
                        .configurations(Collections.singletonList(new TestConfiguration()))
                        .classes(Arrays.asList(Sample.class, Component.class))
);
                        
Context context = grape.createContext();
Sample sample = context.getBean(Sample.class);

There are three ways to register a component in the Grape container.

Annotate a class with @Component so it will be detected by the component scanning

package com.example.beans;

@Component
public class SomeComponent {

And instruct Grape to scan a certain package and its subpackages:

Grape grape = new Grape(new GrapeConfiguration().scan("com.example.beans"));

Context context = grape.createContext();

public class SomeComponent {

Register a class in the configuration

Grape grape = new Grape(new GrapeConfiguration().classes(
     Collections.singletonList(SomeComponent.class)
));

Context context = grape.createContext();

A configuration is intended for defining beans through the factory methods. This is also known as a Java Configuration in Spring Framework.

To define a bean, add an appropriate factory method in the configuration and annotate it with @Produces:

public class SomeConfiguration implements Configuration {

    @Produces
    public Bean bean() {
        return new Bean();
    }

}

Grape supports standard @PostConstruct and @PreDestroy annotations.

@Inject
public YourComponent(DependencyA dependencyA, DependencyB dependencyB) {
    this.dependencyA = dependencyA;
    this.dependencyB = dependencyB;
}

@Inject
public void setDependency(Dependency dependency) {
    this.dependency = dependency;
}

@Inject
private Dependency dependency;

If there are multiple beans of the same type defined, the injection point must qualify the bean to be injected by specifying its name using @Named annotation.

@Inject
public YourComponent(@Named("ImplementationOne") Interface someInterface) {
    this.someInterface = someInterface;
}

This annotations is supported by setters and fields as well.

In turn, the named bean must be defined as follows:

@Named("ImplementationOne")
public class ImplementationOne {

Or add the bean annotation to the configuration method:

@Produces
@Named("ImplementationOne")
public Interface implementationOne() {
    return new ImplementationOne();
}

The named bean may manually obtained from the context as follows:

Interface i = context.getBean(Interface.class, new NamedLookup("ImplementationOne"));

@Primary annotation is another way to resolve the bean ambiguity. If there are multiple bean candidates for the injection point and one of them is defined with this annotation, it should be given a preference. That is, this annotation makes a bean a priority one.

@Produces
public Interface one() {
    return new One();
}

@Primary
@Produces
public Interface two() {
     return new Two();
}

This exception is fired when there are multiple candidates for the injection point and none of them is qualified at this point. Specify a bean to be injected through the @Named mark one of the candidates as a priority one using @Primary annotation.

This exception indicates a circular constructor dependency between two beans. It means that constructor of bean A accepts bean of type B as a parameter and constructor of bean B accepts bean of type A as a parameter. This may be eliminated by injecting one of dependencies involved in a loop through the setter.

This exception is raised when there are no candidates for the injection in the conatiner, i.e Grape is unable to resolve the dependency for some reason. It may happen because there are no beans of the dependency type defined or there is no bean with the specified name. Examine the exception message for more details.

This is a reflection-related exception indicating that an invocation of a reflective component is failed due to some reason. As usual, this exception is caused by insufficient access privileges or by a error raised within the invoked constructor or method.