> > Static singletons and avalon are not a very good match. One could say > "Static Singletons are Considered Evil" in the multi-application > multi-classloader universe. See
I agree with you. I am trying to move away from using Singletons all-together. Part of the problem for me is that I have many classes created in a hierarchy starting with the Avalon Component that creates the root class. These classes themselves are not compoments hence don't have access to Configuration object unless passed in to them. Hence the convinience of a Singleton that already had all these parameters. I don't know of a less painfull way of doing this and yet abide by OO best practices. For my initial problem, I decided the Class that needed the configuration node information, is better suited as a Component. So Configurable interface came to rescue there. I still had to add the 10's of attribute=value pairs to config.xml though. I saw a Parameterise interface in the docs that I think should help with attribute=values. > > you're probably using a wrong URL. You need to provide more information > (which version of phoenix are you using, stacktrace, error log) for a > more specific answer. However, there's a better solution in Phoenix... You are right. I was trying to load "myprops.properties" where as I should have been using "SAR/myprops.properties". --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
