[
https://jira.jboss.org/jira/browse/WELDX-58?page=com.atlassian.jira.plugi...
]
Chris Pheby commented on WELDX-58:
----------------------------------
Just to elaborate the error. Running model-test-case from a separate Maven module,
resulted in the following error:
java.util.NoSuchElementException
at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:340)
at java.util.ServiceLoader$1.next(ServiceLoader.java:421)
at org.jboss.weld.test.core.BootstrapResolver.resolve(BootstrapResolver.java:35)
at org.jboss.weld.test.core.TestCore.start(TestCore.java:20)
at org.jboss.weld.test.junit.CDIRunner.initialize(CDIRunner.java:33)
at org.jboss.weld.test.junit.CDIRunner.<init>(CDIRunner.java:22)
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
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.<init>(JUnit4TestReference.java:29)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestClassReference.<init>(JUnit4TestClassReference.java:25)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.createTest(JUnit4TestLoader.java:40)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.loadTests(JUnit4TestLoader.java:30)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:452)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Modification to Weld Test to use SE Bootstrap
---------------------------------------------
Key: WELDX-58
URL:
https://jira.jboss.org/jira/browse/WELDX-58
Project: Weld Extensions
Issue Type: Patch
Components: CDI Test, Java SE
Affects Versions: Java SE 1.0.0.CR2, CDI Test 1.0.0.Beta1, CDI Test 1.0.0.Beta2
Environment: Windows Vista, Eclipse / Maven
Reporter: Chris Pheby
Fix For: CDI Test 1.0.0.Beta2
Attachments: weld-test-se.diff
Thanks very much for Weld which is a great runtime evolved from the Seam framework, and
thanks for Weld Test which brings JUnit testing in an elegant manner to the framework.
My initial attempts to run Weld Test runtime were unsuccessful. Digging into the
framework, I found it was very similar to the bootstrapping found in the SE runtime. Since
the test framework runs out of container, it makes sense to reuse the SE runtime directly
to benefit from the work going on there and reduce duplication. This patch is an effort to
do that, and builds and executes the test using the SE runtime rather the Weld Test's
own runtime.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira