This is as far down to the bottom as I could get of this NoClassDefFoundError.
java.lang.NoClassDefFoundError
at
org.apache.openejb.test.stateless.EncStatelessBean.lookupEntityBean(EncStatelessBean.java:60)
And that code on line 60 of EncStatelessBean.java is:
BasicBmpHome home = (BasicBmpHome)
javax.rmi.PortableRemoteObject.narrow(
ctx.lookup("java:comp/env/stateless/beanReferences/bmp_entity"),
BasicBmpHome.class );
Unless I'm missing something in the plan, the ejb-refs look alright to me.
The BasicBmpHome and EncStatelessBean are in the same package,
openejb-itests-core-2.3-incubating-SNAPSHOT.jar which is deployed
prior to running the tests.
Yet, we get this NoClassDefFoundError !
Cheers
Prasad
On 12/4/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
David,
The .setup() and .teardown() still continue to show up withour their
testnames prepended. We'll have to go back to using the
DummyTest.java that was in the original patch (391).
Anyways, here is the patch again. Please apply it.
https://issues.apache.org/jira/browse/OPENEJB-397
In the ReuseOpenEJbTest, I changed the database system property from
InstantDB to Derby.
System.setProperty("openejb.test.database",
org.apache.openejb.test.DerbyTestDatabase.class.getName());
We now execute 552 tests out of which 27 fail and 10 throw errors.
All the faillures are due to a NoClassDefFoundError yet the stacktrace
is not all that informative.
All the errors are coming from the CMRMapping tests.
One tiny fix someplace in each will fix them all.
Here are the logs
http://rifers.org/paste/show/2594
Cheers
Prasad
On 12/4/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> Thanx David for taking care of those.
>
> The DummyTest.java didn't go into trunk. Can you please do the needful ?
>
> Thanx
> Prasad
>
> On 12/4/06, David Blevins <[EMAIL PROTECTED]> wrote:
> > Made a couple extra fixes too and published new snapshots of the itests.
> >
> > -David
> >
> > On Dec 4, 2006, at 10:18 AM, David Blevins wrote:
> >
> > >
> > > On Nov 30, 2006, at 9:06 PM, Prasad Kashyap wrote:
> > >
> > >> Hi David,
> > >>
> > >> This is a continuation of the discussion we had in the "Testsuite
> > >> ready for action" thread.
> > >>
> > >> First, the openejb-itests-core would not start. I have submitted a
> > >> patch at https://issues.apache.org/jira/browse/OPENEJB-391 Please
> > >> apply this.
> > >
> > > Applied.
> > >
> > >> Next, openejb itests continued to fail looking for the same getName()
> > >> method. I then "fixed" it in
> > >> https://issues.apache.org/jira/browse/OPENEJB-392. Please apply this
> > >> as well.
> > >
> > > Applied.
> > >
> > > -David
> > >
> > >> Lastly for the "almost" part, after this and other fixes, we now have
> > >> 185 passing tests, 2 failures and 5 errors. The stacktrace for the
> > >> failures and errors can be seen here -
> > >>
> > >> http://rifers.org/paste/show/2527
> > >>
> > >> Please apply the patches in the above JIRAs.
> > >>
> > >> You will notice that the names will show up in the logs as just
> > >> ".setUp". This needs to be fixed too.
> > >>
> > >> Thanx,
> > >> Prasad
> > >>
> > >
> >
> >
>
