Are you getting the exception by registering multiple components through the XML configuration?
The way XmlInterpreter works (or used to) was by populating the ConfigurationStore, which then would be used by the Installer to register things. The store would accept duplicate ids, and override the old value. Calls to the AddComponent/Register wont. On Tue, Aug 26, 2008 at 5:23 PM, David Gardiner <[EMAIL PROTECTED]> wrote: > > The last paragraph on this page > http://www.castleproject.org/container/documentation/trunk/usersguide/includes.html > implies that if you register a component with the same ID as an > existing registered component, that the new registration will succeed > and override the old one (without an exception being thrown). > > Which seems to contradict reality: > > Castle.MicroKernel.ComponentRegistrationException: There is a > component already registered for the given key LoggingInterceptor > > Are the docs incorrect, or is there something else I need to be doing? > > -dave > > > -- Cheers, hammett http://hammett.castleproject.org/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
