Error "Missing @Injectable for field" with @Resource annotation

[AlexStasko]

I use JMockit 1.28 (tried 1.29)
Java 1.8.92

I work with @Resource annotation. But with name value my tests not working. Without it tests work fine.
Console output:

java.lang.IllegalStateException: Missing @Injectable for field "by.common.model.DummyDomain dummyDomain" in DummyService

Also if using @Autowired with @Qualifier tests work fine.
Test case is here: jmockit-check.zip

I use something like this as workaround:

    @BeforeMethod
    public void setUp() {
        dummyService = new DummyService();
        ReflectionTestUtils.setField(dummyServie, "dummyDomain", mockDummyDomain);
    }

Might be that is a bug, maybe I 'm doing something wrong. Thank you in advance and hope for your help.

Thank you,
Alex

[rliesenfeld]

The @Injectable field should match the name of the target @resource ("test"). So, name it "test".

[AlexStasko]

@rliesenfeld in my project I use names like "subname1.subname2.name" and in this case I cannot name field with dots.

[rliesenfeld]

The names need to match, otherwise it's not possible to support a scenario where multiple @resource's of the same type are injected into a given object.

Name matching can be made more flexible, though. I am thinking of two possible solutions, when given a resource name composed of multiple parts separated by special characters such as "." (dot) or "-" (hyphen):

1. Use only the last name part. So, if the resource is named "part1.part2.last", then the @Injectable would need to be named "last".
2. Use the full resource name, but replacing separator characters with the underscore "_" character, which can be used in the name of the injectable: "@Injectable Xyz part1_part2_last".

Which solution would you prefer?

[siarhei-usau]

I am tech lead of the project so let me answer.
Var N2 looks definitely better but my previous question is still valid I think.

How possible to support a scenario where multiple @Autowied with @Qualifier the same type are injected into a given object? Because as I mentioned if change in the test case @Resource ("test") to
@Autowired
@Qualifier("test)
(which is same thing from Spring prospective) it works. Might be if multiple @Resource but with different types we can use the same "@Autowired " approach?

[AlexStasko]

Thanks for your suggestions. But if we will use solution with underscore we will face with codestyle problems. In this case can we use camelcase solution? Something like this:
name = "part1.part2.name"
field name = "part1Part2Name"

[siarhei-usau]

codestyle problems

Good catch, I didn't release that. Camelcase is definitely better

[rliesenfeld]

Ok, camel case can be supported too.