When I say absolute I mean in the connection parameters. That's the only
thing that Derby specific. I'm using Toplink with JPA.
Stanley Bradbury wrote:
Hi Paul -
Sounds like you have a lot of experience in the area. Your
architecture seems beyond my experience but I did notice something I
missed in my first read that might be of help. You wrote:
"..I have an absolute path set, but it still does it. Shouldn't it
write everything to that path and not just start writing to where ever
it decides home is? .."
Derby writes the logfile to derby.system.home (this also serves as the
ROOT directory for any relative path references). If this is not
explicitly set prior to loading the Derby driver the value defaults to
the default directory for the JVM. Derby's view of the world is from
the JVM perspective, not the server or application that starts it. I
assume the 'absolute path' you set is an application or server property?
Anyway, a possible solution for you might be to set derby.system.home
to an appropriate location (the absolute path?) prior to loading the
Derby driver.
HTH
--
Justin Stanczak
Stanczak Group
812-735-3600
"All that is necessary for the triumph of evil is that good men do nothing."
Edmund Burke
..________...............__.................
./ _____/..____..._____/..|_..____...____....
/...\..____/.__.\./....\...__\/.._.\./._..\....
\....\_\..\..___/|...|..\..|.(..<_>.|.<_>..)....
.\______../\___.._\__|../__|..\____/.\____/......
........\/.....\/.....\/..........................
