Please see my last message where I ask two very specific questions about this. I'm not opposed to delaying creation of a Conduit in some circumstances. I think the threads are getting too conflated (should we *require* a Conduit during dispatch vs. should we be able to lazy init a Conduit), which is partially my fault, so maybe this is part of the confusion going on...
- Dan On 4/2/07, Andrea Smyth < [EMAIL PROTECTED]> wrote:
> > Are we not happy with our ability to select a different Conduit inside > the > MessageSenderInterceptor? I don't see how this could be an issue. Just > set a > new Conduit on the Exchange in a previous interceptor. Hi Dan, Maybe I am missing something here - but doesn't the fact that any interceptor run before the MessageSenderInterceptor can set the conduit prove that the client - conduit coupling is very loose indeed? In the presence of such an interceptor, it makes perfect sense to me to not initialise a conduit upfront if it's possible/certain that this is never going to be used. In that case I don't understand your objections aginst the proposed strategy pattern. Cheers, Andrea.
-- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
