David Blevins wrote:
OpenEJB init-params:
param-name: openejb.home, param-value: C:\xsite2\openejb-1.0-SNAPSHOT
log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: C:\xsite2\jakarta-tomcat-5.0.25\bin\logs\server.log: The system cannot find the path specified
at jrockit.io.FileNativeIO.open0(Ljava.lang.String;I)I(Unknown Source)
Ick, old problem back again. Looks like you are starting tomcat from "C:\xsite2\jakarta-tomcat-5.0.25\bin" so all relative paths are getting resolved from there. This was fixed sometime in the 0.9.x branch, but must have been rebroken with all Jacek's property changes for the one openejb per tomcat webapp support.
Whoops, did I do it again (as the songs goes :))? I'm looking into it.
Fortunatelly, the exception showed that computing openejb.home worked well (as I guess you didn't change anything in WebAdmin webapp).
We'll have to look into it, but for now you should be able to start tomcat in the tomcat.home directory and things should workout.
Yes, tested and verified.
should openejb.base be defined? where do i define it? inside the web.xml, just like openejb.home?
You only need to define openejb.base if you want it to be different from openejb.home. Say for example you want several openejb setups but don't want to copy the lib and dist directories all over the place. We look in openejb.home for lib/ and dist/ and look in openejb.base for beans/ and logs/ and conf/. If openejb.base isn't defined it is set to openejb.home.
Just to add to Dave's response. You can define different OpenEJB configuration settings (openejb.home, openejb.base, openejb.configuration, etc.) in WEB-INF/web.xml of the web application you're deploying OpenEJB with (or WebAdmin if it's the default integration webapp).
-David
Best, Jacek
