Sorry for spamming you. But I found where the problem was. After I changed in my test class service's reference to interface type instead of concrete realisation the problem has been disappeared.
Sorry, -Petr 2015-05-31 16:07 GMT+03:00 Petr Shypila <[email protected]>: > Hello everyone, > > > Currently I'm working on the issue SLING-4757 and I faced with problems > during creation integration tests for these classes. > > I try to inject test service into my test using @javax.inject.Inject > annotation. However it doesn't work for me and every time my test throws > ClassNotFoundException: > > > java.lang.ClassNotFoundException: >> org.apache.sling.commons.contentdetection.internal.FileNameExtractorImpl >> not found by PAXEXAM-PROBE-6b612ff1-07dd-4f13-b793-3b6c6c19d132 >> > > But injection of standard org.osgi.framework.BundleContext looks like > works fine. > > I did everything very same with > org.apache.sling.i18n.it.ResourceBundleProviderIT but it still doesn't work. > I have also attached a patch[1] with this test. More detailed stack trace > is also available in comments of SLING-4757 issue. Could you please help me > to find where the problem is? > > > [1] > https://issues.apache.org/jira/secure/attachment/12736426/FileNameExtractorImpl_Injection_failed__ClassNotFoundException.patch > > Thank you, > > -Petr >
