Hi William, Mind if I ask a few questions first? I think there are some cases where you probably do want to specify your own MessageObserver, but this seems opposed to the goal of letting a binding manage how endpoint resolution happens. I would like to unify the two better though - so maybe you can help me figure that out :-)
Why are you specifying a different messageobserver? Where were you previously specifying your own messageobserver - ServerImpl? Thanks - Dan On 4/17/07, William Tam <[EMAIL PROTECTED]> wrote:
Hi Dan, Is it possible to specific my own MessageObserver rather than using the default "ChainInitiationObserver"? Prior to this change, I could name my MessageObserver in the constructor of ServerImpl(). I could no longer do that. The MessageObserver is now hardcorded in AbstractBindingFactory.addListener(). It is not possible for me to override it because I don't have control over the BindingFactories. Thanks, William
-- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
