I have all my beans in one ejbjar.jar file. This includes 20+ slsb and a handfull of mdbs. I may be able to separate those out, but we'll see.
Hopefully one day soon our team will be able to use eclipse or netbeans to debug our test suites which test our ejb's quickly and painlessly.
contain any
dtd's, just the DTDResolver.
This is an old (that was fixed) back again. The DTDResolver will do it's job provided the dtds are packed in the jar. In the switch from ant to maven and sourceforge to codehaus, we seem to have overlooked that detail.
I've patched that up and it should be ok now.
i've also decided to give the 2.0-SNAPSHOT a whirl since my beans use the 2.o dtd. that jar seems to give the same issue (it requires a bit more dependancy jars though). the 2.0 data source configuration seems a bit different than that of 1.0. once i get the issue of dtd resolution resolved, i'll need to see how to properly configure an axion datasource.
any ideas?
The OpenEJB 2.0 code-line doesn't do any of the neat testing stuff yet. It will, but basic compliance is first priority in that code-line.
I've just added local interface support to the 1.0 code so that people
can test beans which would otherwise be 1.1 beans sans the local
interface.
This means OpenEJB 1.0 can now deploy ejb 2.0 deployment descriptors that contain only session beans, BMP entities, or CMP 1.1 entities with either remote or local interfaces. MDBs or CMP 2.0 entities will still not deploy or run.
Hopefully this will tide people over till we can get closer to completion on the OpenEJB 2.0 code.
Should work out great for you if you don't have any CMP 2.0 or MDBs.
I've also updated the snapshot jars in our maven repository, so you should get the new jars next time you build.
Let us know how it works out or if you have any troubles.
-David
