hey,

nice one :)

I looked through the load code and it turns out that when a component
configuration is deserialized it's configuration is stored under the
key that is loaded from the XmlNode, not from the parsed
configuration. This XmlAttribute gets trimmed, while the configuration
parser doesn't trim.

I'll commit a patch later.

thanks!
Ernst

On Mon, Oct 13, 2008 at 5:30 AM, codemonkey <[EMAIL PROTECTED]> wrote:
>
> Hey,
>
> I have the following in my config for Windsor:
>
> <component id="nullLogger" service="WindsorBugTest.ILogger,
> WindsorBugTest" type="WindsorBugTest.NullLogger, WindsorBugTest"
> lifestyle="transient" />
>
> If I resolve it will be fine and I will get a new instance for each
> resolve. In my initial config I accidently put a space after the id
> i.e.
>
> <component id="nullLogger " With this space I would get the singleton
> instance, is this known behaviour? Although it was just a space which
> shouldn't be there it still had me running in circles.
>
>
>
> Cheers
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to