You could create a decorator for DefaultComponentModelBuilder and override BuildModel(). I agree with Krzysztof though - it's best to explicitly name things you need named.
-- Mauricio On Tue, Jan 25, 2011 at 2:49 PM, mcintyre321 <[email protected]> wrote: > We do all our registration using the fluent API and conventions, and > occasionally the generated service names conflict and we have to > manually override them. Is there some way to change the strategy used > for when no name is specified (e.g. serviceType.FullName + "#" + > compoentType.FullName or Guid.NewGuid().ToString()) to avoid these > conflicts? > > -- > 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]<castle-project-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/castle-project-users?hl=en. > > -- 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.
