[ #303537 ] jotm.properties discovery algorithm is too rigid
Date: 2005-04-30 23:05
Submitted By: Ludovic Orban (lorban)
Assigned To: David A. Egolf (degolf)
Summary: jotm.properties discovery algorithm is too rigid
Detailed description: org.objectweb.jotm.TransactionRecoveryImpl looks for a jotm property file under
some folder which name is built in a too rigid way (jotm.base or jonas.base
system propery + hardcoded conf subfolder).
It should be possible to include jotm.properties in the classpath or in a
folder that would be specified with another system property.
This problem bloats JettyPlus a bit because a conf folder needs to be created
and a command-line system property must be passed-in if TX recovery is wanted.
That's not critical of course but this is a nice to have. I have patched the
TransactionRecoveryImpl class to be able to read the properties from classpath.
I can send you a patch if you want.
Date: 2005-05-01 11:38
Logged In: YES
Here I attached my simplistic patch. It just tries to read a
jtom.properties file from classpath if it could not find it
in the conf folder. I also fixed a small bug: you forgot to
close the file after reading it.
Yes, I'm attempting to implement TX recovery within
JettyPlus. More details about this here:
Thank YOU for being so responsive.
Date: 2005-05-01 09:02
Logged In: YES
Yes! Please send a patch for us to see. We were not
happy with the properties file situation, but we needed
The hardcoded "conf" folder concept came from jonas,
is the first platform which actually supports recovery.
Therefore, for jonas users this was not a problem.
For other users, recovery is not implemented on other
platforms. We didn't expect this to be an issue until May
after we publish the interface for the resource manager
registrations and the administrative reporting.
Meanwhile, please send the patches so that we can consider
Also, please let us know if you are attempting to
implement recovery on some other application platform.