Yeah, missing ones would be listed in the exception message and perhaps exposed as custom exception type properties...

On 06/03/2011 3:33 PM, Ken Egozi wrote:
As long as the unresolveable components are clearly listed in the Exception, it could also work. Silently disregarding them makes debugging these scenarios a bitch.


Ken Egozi.
http://www.kenegozi.com/blog
http://www.delver.com
http://www.musicglue.com
http://www.castleproject.org
http://www.idcc.co.il - הכנס הקהילתי הראשון למפתחי דוטנט - בואו בהמוניכם


2011/3/6 Krzysztof Koźmic <[email protected] <mailto:[email protected]>>

    Hi Ken,

    no, we had an option raised to keep ResolveAll as it is and
    introduce ResolveMany in addition to it, but I'm not sure that's
    the best approach.

    If we change to resolving by service, not by assignability I don't
    think I can think of scenario where you would actually want/allow
    some components to stay unresolvable.

    Thoughts?

    Krzysztof


    On 06/03/2011 12:23 PM, Ken Egozi wrote:
    hi Krzysztof. I did not pay attention to this thread (having
    tremendous stress at work lately :(  ), so was changing the
    return value discussed?
    along the lines of
    ResoveResult<IFoo>
       IFoo[] Resolved
       IHandler[] NotResolved



    Ken Egozi.
    http://www.kenegozi.com/blog
    http://www.delver.com
    http://www.musicglue.com
    http://www.castleproject.org
    http://www.idcc.co.il - הכנס הקהילתי הראשון למפתחי דוטנט - בואו
    בהמוניכם


    2011/3/6 Krzysztof Koźmic <[email protected]
    <mailto:[email protected]>>

        I created a poll to gather feedback on the two options
        discussed WRT changes to ResolveAll in Wawel (resolve by
        service, and throw if any missing)

        http://twtpoll.com/p6151o

        Please take a moment to share your opinion.

        Krzysztof

-- 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]
        <mailto:[email protected]>.
        To unsubscribe from this group, send email to
        [email protected]
        <mailto: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.

Reply via email to