There's a couple of layers of indirection getting in your way.
You can see tapestry.ioc.ApplicationDefaults and tapestry.ioc.FactoryDefaults. Those are two (of three) built-in contributions to the tapestry.ioc.SymbolSource service configuration. To pull that type of configuration data, data that ends up as symbols, out of an external file, you'll need to create an object or service that implements SymbolProvider and contribute it into that configuration. On 3/1/07, Terry <[EMAIL PROTECTED]> wrote:
I've been through all the IoC docs a couple of times now, but I haven't seen a simple way to inject config parameters from a configuration file into a service. Obviously I could just load a properties file from the classpath manually, but I'm sure there must be a more elegant way to do that within the IoC framework. All I want to do is have a set of deployment parameters for tweaking things like filepaths. Many thanks, Terry -- View this message in context: http://www.nabble.com/T5-Injection-of-config-properties-tf3330688.html#a9261163 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
