Hi all,
I doubt many people out there are really aware of Latka right now :).
However, in case anyone out there is experimenting with it right now, I'm
working on improving the methods for configuring Latka, and I want to give
the oppportunity for feedback.
Today I removed Latka's ability to configure its variables from System
properties. I've replaced it with a ThreadLocal reference to a Properties
object, which should make configuration of Latka more threadsafe while still
making it easy to get at Properties anywhere in the application. Now I'm
pondering how best to set those properties from the command-line interface.
Perhaps something like:
java -Dlatka.userProps=<path to prop file> org.apache.commons.latka.Latka
<path to Latka XML file> [<latka property> <latka property> ...]
So you could read a bunch of properties from a file, or pass them on the
command line, or some combination thereof. I think that works well, but I'm
still experimenting.
Also, I'm probably going to take out the magical "latka.defaultHost" and
"latka.defaultPort" properties, because they don't really seem to fit with
the rest of the configuration strategy. If you want to make host and port
variable, I think you should probably just set them as variables in the
suite itself with whatever variable name you want, e.g.
:
<?xml version="1.0" standalone="no"?>
<!DOCTYPE suite SYSTEM "../conf/suite.dtd">
<suite defaultHost="${defaultHost}" label="Taglibs">
...
It's going to take a little while to get all these configuration issues
sorted out, but I think the rewards will make it worthwhile.
- Morgan
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
