Tapestry IOC configuration happens once, when the app is started. It determines the symbols, constructs services and wires them all together. After that, Tapestry IOC's job is done and all of the services are acting upon the config they were provided during construction after that.
If you want to change values at runtime, it will be via custom events on your services. Changing symbols will have no effect as each service has done it's own custom thing with the symbol (for example connecting to a database or writing a file etc). I think you need to think about exactly what is changing. Perhaps selected services can listen for changes to some configuration object and act appropriately? -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-app-live-console-tp5714144p5714152.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
