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
