Personally, i'm looking for something to test my slsb using a
lightweight/embeded framework as oppose to our current setup using
cactus (fairly cumbersome and time consuming to run tests starting a wls
server). I also need a DataSource available for my beans to get a db
connection and the examples give something to follow on that
respect. I've also taken a look at axion and started to use it to
test our db access layer. both openejb and axion are awesome projects!!
Thanks again for all the help on this.
N. Alex Rupp wrote:
The part that is still severely lacking, both in my article and in
general, is documentation on how to set up CMP entity beans. OpenEJB
uses Castor JDO for CMP, and references the Castor JDO page for
documentation, but in my opinion the docs are too scarce and
scattered. I've thought of writing an article or blog entry on
setting up CMP in OpenEJB, in part because the process confuses the
hell out of me and in part because I'm certain I'm not alone. So, if
anyone gets that impression when working with the examples, please
understand that we're in agreement and don't think I skipped CMP out
of mere neglect.
As the autumn progresses, I'll hopefully be able to contribute some
more documentation to the project. David's encouraged me to go hog
wild on the Confluence site. I'll return to it once things settle
down a bit with my job.
Guten abend,
--
Alex
Jacek Laskowski wrote:
Mark Lybarger wrote:
Jacek,
Thanks a lot for the tips, this solved the problem for me. The tests
are
now passing! What a cool server this thing is.
Nice we're on the same track. Now, move on to the chapter 3. Note
that in "2. Start the server and fire off the tests" there's a wrong
directory where maven is executed. Before issuing 'maven' change the
working directory to 'example_03'.
Also, in addition to what example_02 required (in regards to
openejb.home) and so does example_03 do the following:
o Rename example_03/conf/logging.conf to
example_03/conf/default.logging.conf
or add 'log4j.configuration' with the value 'conf/logging.conf' to
project.properties as it's done for openejb.home.
It's not really required, but let you see OpenEJB logs in logs
directory and prevent OpenEJB from complaining about log4j
misconfiguration.
It's very important to keep in mind that when 'maven db:teardown' has
been executed, you will need to execute 'maven db:setup' before
proceeding. Otherwise, you'll see errors like 'Table EMPLOYEE not
found'.
I must admit the exceptions were introduced to the article because of
the changes regarding OpenEJB environment properties handling. At the
time, the article was writing OpenEJB behave well. Now, after the
changes, it refuses to run smoothly. I'll take a look at the
procedure of setting openejb.home environment variable again.
Have fun! Despite the (already-sorted-out) exceptions, you'll find
EJBs pretty easy to understand mostly because of the article (and the
simplicity of OpenEJB). An awesome work, Alex!
~mark
Jacek
