> Well, my definition of distributed configuration is different: it's the > ability of more than one module class to contribute configuration for a > given service. Granted. And how that works is, what I was trying to explain in my first reply to the question. I wanted to point out, that this feature goes far beyond just having services in a different jar. Admiddetly my explanation was a bit too clumsy or short.
----- http://www.winfonet.eu -- View this message in context: http://tapestry.1045711.n5.nabble.com/IoC-services-can-they-come-from-an-external-jar-tp4688157p4689361.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
