java – 使用Play编写一个简单的Spring示例!骨架
我正在尝试将
Spring 1.0.1模块设置为与Play一起使用! 1.2.1.
首先,我将Spring模块添加到dependencies.yml: - play -> spring 1.0.1 然后我根据application.conf中的documentation添加了以下内容: play.spring.component-scan=true 然后我运行以下代码来下载依赖项并更新我的IntelliJ配置: play deps --sync play idealize 现在当我回到IntelliJ时,我可以看到spring-1.0.1已被添加到我看起来正确的项目模块列表中.但是,如果我查看我的项目的依赖项,它没有位于spring-1.0.1 / lib目录中的jar.如果我尝试用@Component注释我的一个类,它就找不到它.但是,如果我手动添加spring-1.0.1 / lib作为项目依赖项,它会发现@Component很好.我想运行其他东西让我的IntelliJ项目识别模块中的弹簧库吗? 我的问题的第二部分涉及连接一个简单的例子并为它编写测试. 所以,假设我有一个这样的Job类: @Component @Every("10min") public class MyJob extends Job { private @Inject Printer printer; @Override public void doJob() throws Exception { printer.print(); } } Printer类看起来像这样: @Component public class Printer { public void print() { System.out.println("foo"); } } 首先,注释看起来是否正确?其次,我将如何编写一个可以调用MyJob.doJob()的测试但注入一个打印“bar”而不是“foo”的不同打印机? 更新:如Aaron所述,我将@Inject更改为@Autowired.在我的测试课中,我有这样的事情: @Test public void testSomething() { MyJob job = play.modules.spring.Spring.getBeanOfType(MyJob.class); job.doJob(); ... } 它使用以下内容在getBeanOfType语句上失败: play.modules.spring.SpringException at play.modules.spring.Spring.getBean(Spring.java:11) at com.testing.JobTest.testSomething(MyJob.java:20) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at play.test.PlayJUnitRunner$StartPlay$1$1$1.execute(PlayJUnitRunner.java:73) at play.Invoker$Invocation.run(Invoker.java:265) at play.Invoker.invokeInThread(Invoker.java:67) at play.test.PlayJUnitRunner$StartPlay$1$1.evaluate(PlayJUnitRunner.java:68) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at play.test.PlayJUnitRunner.run(PlayJUnitRunner.java:48) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:60) 更新2:好的,我现在真的得到了更多.好像即使我正在进行组件扫描,Spring模块仍然需要conf /目录中的application-context.xml(即使它没有定义bean). 现在我只需要弄清楚如何注入不同版本的Printer对象,它会吐出“bar”而不是“foo”. 更新3:我已使用@Autowired替换@Resource(name =“printer”)并使用@Component(“printer”)注释了我的生产打印机并将其重命名为RealPrinter并提供了一个界面: @Component("printer") public class RealPrinter implements Printer { public void print() { System.out.println("foo"); } } 如果我只有上述打印机,注射工作正常.现在,如果我创建一个TestPrinter,我需要Play的Spring模块来实现我想在执行测试类时使用TestPrinter而不是RealPrinter. @Component("printer") public class TestPrinter implements Printer { public void print() { System.out.println("bar"); } } 但是,因为我有两个名为“printer”的组件,Play的Spring Module会引发以下异常: play.exceptions.UnexpectedException: Unexpected Error at play.Play.start(Play.java:491) at play.test.PlayJUnitRunner.<init>(PlayJUnitRunner.java:31) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31) at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:66) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:192) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:115) Caused by: java.lang.IllegalStateException: Annotation-specified bean name 'printer' for bean class [com.testing.job.RealPrinter] conflicts with existing,non-compatible bean definition of same name and class [com.testing.job.TestPrinter] at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.checkCandidate(ClassPathBeanDefinitionScanner.java:267) at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:208) at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.scan(ClassPathBeanDefinitionScanner.java:180) at play.modules.spring.SpringPlugin.onApplicationStart(SpringPlugin.java:98) at play.plugins.PluginCollection.onApplicationStart(PluginCollection.java:408) at play.Play.start(Play.java:463) ... 19 more 如您所见,异常的原因是现在有两个具有相同名称的打印机. 解决方法
好的,我想出了一个适合我的解决方案.因此,为了编写一个注入bean的模拟/测试版本的测试,我做了以下事情:
@Test public void testSomething() { GenericApplicationContext context = SpringPlugin.applicationContext; GenericBeanDefinition definition = new GenericBeanDefinition(); definition.setBeanClass(TestPrinter.class); definition.setAutowireCandidate(true); context.registerBeanDefinition("printer",definition); MyJob job = new MyJob(); job.doJob(); } 然后我不得不改变MyJob成为它需要的东西的“注入”: public class MyJob extends Job { public void doJob() throws Exception { Printer printer = Spring.getBeanOfType(Printer.class); printer.print(); } } TestPrinter不再需要使用@Component进行注释,因为测试方法是以编程方式注册测试打印机bean,从而覆盖生产打印机bean. 因此,执行testSomething()方法将导致打印出“bar”. 我不确定这是否是使用Play的Spring模块注入测试内容的最整洁的方法,但至少我能够做我想要的. (编辑:李大同) 【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容! |