Hi Jacek...
Yeah this error appears to me too, this is why I created this JIRA
http://jira.codehaus.org/browse/OPENEJB-264, but the itests run successfully
when using spring.xml .
On 9/14/06, Jacek Laskowski <[EMAIL PROTECTED]> wrote:
On 9/14/06, Jacek Laskowski <[EMAIL PROTECTED]> wrote:
> On 9/14/06, David Blevins <[EMAIL PROTECTED]> wrote:
>
> > I'm rebuilding gbuild today and will be working on moving the svn
> > tomorrow. Is there someone who can look at this patch today?
>
> But of course! ;-) I'm doing it now...
When I run the itests after the patch had been applied, I got a tests
failure:
$ less
container/openejb-core/target/surefire-reports/org.openejb.SpringAssembler2Test.txt
-------------------------------------------------------------------------------
Test set: org.openejb.SpringAssembler2Test
-------------------------------------------------------------------------------
Tests run: 398, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
5.796 sec <<< FAILURE!
Stateless.PojoLocalHomeIntfc..setUp() Time elapsed: 0 sec <<< ERROR!
javax.naming.NameNotFoundException: Name
"client/tests/stateless/BasicStatelessPojoLocalHome" not found.
at org.openejb.core.ivm.naming.IvmContext.federate(IvmContext.java
:138)
at org.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java
:101)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at
org.openejb.test.stateless.StatelessPojoLocalHomeIntfcTests.setUp(
StatelessPojoLocalHomeIntfcTests.java:19)
at org.openejb.test.NumberedTestCase.run(NumberedTestCase.java:77)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at org.openejb.test.TestSuite.run(TestSuite.java:29)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.junit.JUnitTestSet.execute(
JUnitTestSet.java:210)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(
AbstractDirectoryTestSuite.java:135)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(
AbstractDirectoryTestSuite.java:160)
at org.apache.maven.surefire.Surefire.run(Surefire.java:81)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(
SurefireBooter.java:182)
at org.apache.maven.surefire.booter.SurefireBooter.main(
SurefireBooter.java:743)
I wonder whether or not spring.xml
(container\openejb-core\src\main\resources\META-INF\org.openejb\spring.xml)
needs to be updated so that the JNDI name is available. It looks to me
that spring2.xml is used instead and don't know how to get rid of the
above test failure.
Jacek
--
Jacek Laskowski
http://www.laskowski.net.pl
