I don't know if I am not getting it, whether I am trying to do things in an inefficient manner, or that the api was never designed to do such things, but I have difficulties every time I try to do anything moderately complex with confiugration.
One of the things I am doing is creating a properties file from a hibernate configuration (expressed in the hibernate xml format) embedded in my module definition as a contribution. I have a custom rule which takes the name attribute and the element body off the stack, gets a proeprties object off the stack (or creates a new one), sets the property and puts everything back. This would be easier if you could define parameters to custom rules, or an initializer. I had to write another custom rule that basically does an invokeParent on everything left on the stack at the end of parsing (in end method). I guess a possible solution to this is to make the final list accessible to rules... The reasons I am using properties are: 1. Cheap and easy to merge, load and save. 2. Universally used and understood for simple configuration (most java libraries utilize it) 3. Legacy reasons I have a DatabaseManager service, and it needs to know about the oscache properties file, a hibernate properties file and our applications properties. Steve Gibson Software Engineer COWWW Software --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
